My pixel 7 is shitting the bed and I am considering upgrading and just installing graphene immediately on the new phone as part of my degoogling journey.
Is there anything I need to know about this? I work in IT, so I’m tech savvy. This is my first time installing graphene, however.
I’d be upgrading to a pixel 10 probably.
My carrier is verizon
Installation was pretty easy. RCS is only available through the Google Messages app, and even then only seems to work with certain carriers. Other things that don’t work are NFC payments,
Android Auto, and any app that uses the the Play Integrity API since it requires access to device identifiers.Some apps can be hit or miss, but there is an option to disable some of the exploit protections on an app by app basis, and that can sometimes get you signed in and then you can re-enable them.
I make use of multiple users to keep certain apps isolated further.
The forum is a good place to check the compatibility of specific apps. Personally I haven’t been very inconvenienced, and the trade off is well worth it.
Edit: Android Auto does work now
Android Auto does work these days
It’s really easy. Graphene has a web flasher with very good instructions, and once flashed, you’re good to go. I haven’t looked back. Once installed you’ll want your apps.
If you want to sign in to the play store and connect your google account to the phone for your apps, you can do that, bu then you’re kinda right back where you started. Not fully, because Graphene, but Google is still gonna google and suck up any and all data it can.
So for apps, look to F-Droid, Obtainium, and Aurora store.
F-Droid and Obtainium for FOSS apps, and Aurora store for play store apps without having to sign in to the play store.
And if you need google play, make a separate container thinghy and install all google BS there, no?
Google Play is sandboxed on GrapheneOS by default, and you can choose which permissions to give it.
Eehhhh I still wouldnt trust it in the same container
Besides, I can be assured that it is 100% not even running if it’s in a different container, right?


