Pixel owners, what are your thoughts about GrapheneOS?
Since GrapheneOS is the standard recommendation for a custom ROM on Pixel devices and comes up very often, I figured we should have a thread about it.
For those who are using it, what Pixel device are you running GrapheneOS on and how is the overall experience? What are the things that you like about GrapheneOS and what are things you miss from the factory Android install?
As for me, my curiosity got the better of me and I finally went and installed GrapheneOS on my Pixel 7a using the web installer on Arch Linux and a USB cable.
So far, nothing unexpected and I'll have to do a bit of exploring of the OS' security features. The OS works just fine and feels obviously way cleaner and less bloated, the annoying search widget finally went away without having to install a custom launcher. The only thing that scared me a bit in the beginning was the contacts not syncing and some purchased apps not transferring over as the sandboxed Google Play saw the device as a different one but that was solved by giving it permission to access contacts and also waiting for Google Play to do its thing. Google Camera and Google Photos also worked fine without network permissions.
I haven't tried Google Wallet's NFC payments yet and I have no hopes for that one to work on GrapheneOS, but that is certainly a feature I will miss.
I have been using GrapheneOS since the Pixel 6 came out and I have no complaints. I get regular updates, the OS is super stable and my phone is free of the pre-installed ad- and spyware.
I also remember the ridiculously easy and straight forward install, something that I wasn't expecting since I used to tinker with LineageOS and CyanogenMod way back. It almost feels like a stock rom.
The additional security features are great, though they come with the tiny inconvenience of not having access to system files (which is obviously by design).
Overall I couldn't be happier with it and I'll continue to use it for as long as I can.
Hardware, firmware and software specific to devices like drivers play a huge role in the overall security of a device.
Non-exhaustive list of requirements for future devices, which are standards met or exceeded by current Pixel devices:
Support for using alternate operating systems including full hardware security functionality
Complete monthly Android Security Bulletin patches without any regular delays longer than a week
At least 4 years of updates from launch (Pixels now have 7)
Vendor code updated to new monthly, quarterly and yearly releases of AOSP within several months to provide new security improvements (Pixels receive these in the month they're released)
Linux 5.15 or Linux 6.1 Generic Kernel Image (GKI) support
Hardware memory tagging (ARM MTE or equivalent)
BTI/PAC, CET or equivalent
PXN, SMEP or equivalent
PAN, SMAP or equivalent
Isolated radios (cellular, Wi-Fi, Bluetooth, NFC, etc.), GPU, SSD, media encode / decode, image processor and other components
Support for A/B updates of both the firmware and OS images with automatic rollback if the initial boot fails one or more times
Verified boot with rollback protection for firmware
Verified boot with rollback protection for the OS (Android Verified Boot)
Verified boot key fingerprint for yellow boot state displayed with a secure hash (non-truncated SHA-256 or better)
StrongBox keystore provided by secure element
Hardware key attestation support for the StrongBox keystore
Attest key support for hardware key attestation to provide pinning support
Weaver disk encryption key derivation throttling provided by secure element
Inline disk encryption acceleration with wrapped key support
64-bit-only device support code
Wi-Fi anonymity support including MAC address randomization, probe sequence number randomization and no other leaked identifiers
GOS's mission is Security and User Agency first. Fuck google doesn't even fit into their vision statement, it just so happens user agency and fuck google align most of the time.
Just like you can have Linux and proprietary stuff like Steam on it. It isn't really contradictory, the whole issue is about choice and controlled privacy. When you install an app through the Sandboxed Google Play, you not only don't have to deal with the Play background services anymore, but as Redoomed mentioned you also get more fine-grained control of what the installed app can and cannot do. Even proprietary stuff should be more secure in theory since among other things they reroute malloc calls to their hardened versions.
With the factory Android install you don't have that much control and you can see that on the first boot as you're from the start stuck with the ugly Google search bar on the home screen with no way to remove it other than installing another launcher.
still using my pixel 3a XL, graphene was great until suddenly it wasnt. As soon as google drops support for the device you're on your own. Most of the apps still get updated but the OS no longer gets security updates, which is understandable but unfortunate.
This is just to give people an opportunity to move off of the device.
Once this happens, and the phone is no longer getting hardware security patches, graphene OS and calyx OS both drop support for the device, with the exception of fair phone.. were they pretend they're getting hardware security patches but they're not. That's a separate discussion
For a device with no hardware security patches, you can run lineage OS, with an unlocked bootloader which isn't great.. or divest OS DOS.. which locks the bootloader, but strips out a lot of the Google services. It might be a more extreme environment than you want, lineage might be the sweet spot of usable but not secure.
True, but the downsides of Calyx could possibly be worse than an unsupported GrapheneOS. If you weren't going to push it too far, I'd just stay on Graphene, but I never let my phones hit EOL either.
I have a pixel 3A as well, and I went through this exact same thing. My only complaint with graphene OS in this scenario is they should have pop-up notifications when support is being discontinued, so that you know you need to start migrating.
I only really noticed when I thought, hey I haven't installed a operating system update in a long time.... That's not great.
Google Pay incompatibility is certainly a tough pill to swallow. Other than that is Google Maps working fine ? What about Android Auto? I'm definately interested to go this route.
I tried it out on my Pixel 8 Pro but I'm back on stock. I'm trying to be more privacy focused, but I use a lot of Google apps still, so I had almost everything enabled from Google anyways, so I might as well stay on stock for now. It was neat, but I didn't notice any battery improvements, which is also what I was looking for
GrapheneOS is amazing. So many privacy and security features. I finally feel in complete control of my phone. It's not only secure and private, it's also smooth and stable too, much more so than the buggy mess that is stock Pixel OS. And did I mention that it updates faster than stock OS!? It's also far more stable than every other alternative OS on every other phone I've had. I loved it so much I sent my first 5$ to a FOSS project ever LOL. This is my endgame OS and I'm never using anything else ever again.
I also like it, but installing apps takes such a long time and auto updates don't always work. When you open aurora store or f-droid you'll get a dialog to allow an app to install.
Battery drain was also higher than on stock. Not sure why that is, even without Google apps.
It takes longer because of the security, which you can disable, but that would be stupid. Unless you constantly install apps all day, hardly an issue.
You could also give play store a bunch of permissions that it doesn't need, and it would update "normally", but again, that would defeat the entire purpose of taking all the per.iaaik s from it in the first place.
I've been running Graphene on my Pixel 6 pro for about a year now and it's been pretty great. I have had a couple bugs here and there but nothing a quick restart wouldn't fix. I can honestly say I don't really miss any of the google stuff, I've switched to FOSS apps for pretty much everything ,except for what's required for work.
pixel 7a - GOS - everything just works, just like stock android. No real change in experience, nothing i miss (gpay doesn't work in my country anyway for tap to pay), running the sandboxed google play and you would never know its not stock.
The network permissions are nice, the multiple accounts are nice. Honestly, I don't see any downside.
Two things would make it even better:
being able to share a vpn with tethered devices (calyxos and lineage can do this) - this is absolutely a killer feature and replaces a travel router
Work profiles for every account (calyxos has this), so that your second account can also have a work profile, not just the owner account.
I use it on Pixel 7 and my partner on Pixel 6a. I miss Android auto sometimes, but I would use it maybe twice a year so it isn't a big deal to me. Otherwise it's great, I had no trouble using NFC paiment and apart from android auto, every single app i've tried worked without issue.
Yes, I saw it too. I guess they still need time for this feature. It doesn't sound like a very trivial fix, at least not without compromizing on security and privacy.
They'll work if they don't have a Google pay dependency. Most banks don't run their own NFC wallets anymore, at least not in the US minus some small banks. My credit unions used to, then they changed it. It's was too easy for them to be a frontend for Google pay than to build their own app from the ground up.
Pixel 5a, been using it for 3 years. It's great. But don't put anything you need to receive notifications from in a different profile or you'll never see them.
The stock Pixel OS is the only one I know of that takes massive steps to screen and block spam calls and texts. For that reason alone, I have no desire to switch.
I think he means Google's anti-spam solution for calls and text messages and he's right, I've also been getting some spam recently that I wasn't getting before moving to GrapheneOS. I'm not sure if there's a good FOSS solution for that? There's also the option of just installing Google's phone and messages apps but that kind of defeats the purpose.
Running it on a 7Pro now, a 6Pro prior as well as a 5a and 4a before those. I wouldn't run a Pixel any other way.
Since we've got the sandboxed play services I've yet to find a single downside running Graphene, which you can't say about almost any other custom OS. Everything works, purchased apps work, and you get all the benefits of Graphene without all the downsides of Google. If I couldn't have a Pixel running Graphene, I'd probably deal with an iPhone. No way I'd run a stock Google ROM.
Android Auto is in the works, theres hacky ways to do it until then, but not recommended. I wouldn't expect Google pay to ever work, definitely not something privacy conscious people would want to have so doubtful it'd get implemented.