I own 2 bloated proprietary devices and don’t use them for anything important, like banking or dealing with authorities. I also don’t trust the manufactures not selling my data.

Id like to have a working device with no bloatware and completely degoogled. Ironically I’d have to buy something made by google to run GrapheneOS on it. Intended use would be to use as a camera, to run CoMaps on it, pkpass files with foss-wallet, reading epubs, making phone calls and running one aurora app.

I don’t need the device to play games, watch movies, show off or to play loud music, but I’d like a jack port for my headphones (I assume google headphones would cease to work if I degoogle the device, nor would I want to spend more than necessary enriching that data grabber even more.

Is there a pixel device with a jack port?

Are batteries inside pixel devices glued to the frame or can they be easy to change?

My main OS is debian. How easy is to transfer data from GrapheneOS to debian and the other way round?

Overall if you run GrapheneOS on a pixel, how many years running it and what do you think about it?

  • monovergent 🛠️@lemmy.ml
    4·
    26 days ago
    • Buy second-hand or discounted old stock from a reseller to minimize your contribution to Google.
    • Unless one of the apps you are forced to use requires Google Play Integrity, GrapheneOS will be compatible with any Android app, even providing sandboxed Google Play services if needed.
    • For apps so invasive as to require Play Integrity, you might be better off leaving them on a secondary phone with stock Android and powered off when not in use.
    • The Pixel 5a is the last Pixel device with a headphone jack, but no longer receives GrapheneOS updates. You may want to consider USB-C headsets, which are usually also compatible with computers, and require no extra dongles.
    • If the Google headphones work over Bluetooth, they will also work with GrapheneOS. No experience with Google headphones, but I only missed out on customizable shortcuts and device renaming when I opted not to install the companion app for my earbuds.
    • Everybody warns against using out-of-date GrapheneOS devices, but that’s not very satisfying. Yes, they will have open vulnerabilities. But as long as you install apps from reputable sources, the chance of being attacked via outdated Android is very low, provided you are not being targeted by an agency.
    • That said, grab a more recent Pixel if you can for security updates into the 2030s.
    • All Pixel devices have enclosed batteries, most are quite frustrating to remove, particularly the 9a. There’s a decent chance of breaking the screen if it has to be removed in the battery replacement process. Won’t recommend it, but I have considered buying one with a bloated battery just so the adhesives are already removed for me.
    • Transferring files to and from any Linux distro works just fine, as with any Android device, bearing quirks of the mtp protocol in mind. LocalSend can be used for wireless file transfer. rsync requires a workaround.
    • I’ve used GrapheneOS for the past 4-ish years. I’ll admit I had a head start since my workflow wasn’t too smartphone-dependent in the first place and I had already begun pulling myself out from Apple and Google services back then. Everything just works and I would never look back.