I've been on GrapheneOS for 3 years and I'm never going back to stock android. Once my phone stops being supported I'll switch to whatever hardware runs GrapheneOS. If that can't be done I will buy an iPhone with nothing but Signal and my authenticator app on it and turn on lockdown mode.
I am done dealing with built-in adware draining my battery and carrier bloat.
backporting security fixes to the GrapheneOS kernels has become essentially free. if GrapheneOS team doesn't maintain older devices for harm reduction, someone will.
Google seems to loathe all its users across the board. Whether it’s RSS, Gmail, search, Android, Fitbit, Youtube… Google constantly shows its users that the user means nothing to them. I’ve been moving away from Google tools as much as I can, but while I can’t do that with YouTube, my Gmail is now considered my “compromised” account and my logins I will slowly move over to a new email service.
Gmail won’t even save inbox changes on Firefox half the time. It’s wild how far Google products have fallen in quality and trustworthiness.
Graphene really confuses me. They are, in terms of the personalities of people involved, eccentric to say the least. I don’t see a problem with that myself as plenty of security and privacy or even OSS are eccentric people. However it does make understanding their communication a bit of an art.
Also I don’t understand some of their technical choices, and due to the aforementioned eccentricity, it’s not productive to have a conversation with them about it.
The technical issues I don’t understand are: they insist their patched sandboxed GSM is superior to a reimplementation like microG, which is fine. But they can also surely consider a sandboxed microG. There is just no world where i see where grabbing a proprietary binary from a corporation and redistributing it with your own modification is ever gonna fly legally for any hw “partner”. There are many non-Google flavores of android that companies have been shipping just fine. Graphenes issues are entirely self imposed that it just borderlines on odd.
Another is their complete dependency on Google devices because of some self imposed requirement. People got reasonably upset when MS said “next windows requires a tpm”. It’s also just really odd.
> it’s not productive to have a conversation with them about it.
Some of the choices are hard to explain and we have to explain them all the time so that doesn't help either.
Maybe I can help explain the microG thing... microG only makes sense if a user is using apps with Google libraries that rely on Google Play Services. Those libraries are Google code. Some libraries for some functionality have fallback implementations, meaning they can run on their own.
Regular apps have a lot of restrictions compared to system apps and cannot request or obtain certain privileged permissions. The apps with Google libraries are normal apps and the libraries therefore have normal app permissions. On GrapheneOS, Google Play Services is a normal app without special permissions.
microG, on the other hand, needs privileged permissions for signature spoofing. It also doesn't enforce permissions as well as Google Play Services (which has caused leaks), and it needs to download binaries from Google for some functionality, so those binaries run in a privileged context. Finally, microG offers worse app compatibility, which they even admit in their repo's README.
You have to look at the big picture of what Google has access to. The breakdown is like this:
---
App with GMS library = access is restricted, like other regular apps.
App with GMS library + Sandboxed Google Play (unprivileged) = virtually the same access as above
App with GMS library + microG (privileged) = Google has the same access as the situations above, but with worse app compatibility, worse security (especially because of privileged access and possible Google binary running with in a privileged context), and worse privacy (leaks).
---
> Another is their complete dependency on Google devices because of some self imposed requirement.
GrapheneOS's main focus is privacy and security is important for strong privacy. The project doesn't only support Pixels because of some love for them. They were the only supported devices for a long time because they were the only ones that met the hardware requirements. Note 11th gen devices weren't supported for not meeting the requirements (although that has changed). We would have been happy to support more devices, but none met the requirements until our partnership with Motorola. We hope to support more devices in the future.
are you saying there is no way to get microG (or an otherwise a different implementation of play services) to run equally sandboxed? I’m admittedly not as knowledgeable about the topic as you probably are, but it just doesn’t pass the sniff test for me. I know that comparability would suffer, but the alternative is for your project to forever be in an infringing category. As I said, I don’t see a world where redistributing Google’s IP is ever gonna fly, which immediately limits the number of legitimate “partners” you can ever work with. I’m just being a realist here. We can wait for IP laws to get an overhaul globally, or have a solution that works in this century.
I get thr argument that the sandboxed Google play is the technically better solution. But it’s like if WINE went and distributed a copy of MS system32 folder instead. You’d get a better comparability for sure but it’s not a real solution.
As for the self imposed hardware limitation, you basically stated it in another way. It’s self imposed. It’s hard to see Google caring, and paradoxically you are only hurting your own users. I hope there is more choice because I’d like to use graphene at some point, but not if my choices are pixels or a 6.8” $1,500 phone. But maybe my use case is too niche I don’t know.
Bad news in general if true. The motorola phone prices are insane, so only the Pixels are really a viable option atm.
Make it illegal to lock down hardware like phones and cars.
I like GrapheneOS but the rug pull will eventually happen there too-- they're militantly anti-Copyleft, but using GPLv3+ would prevent many from playing those kinds of lockdown games.
All 2026 flagship phone prices are insane. Relative upgraded to an iPhone 18 Pro for almost CAD$2K. Not the foldable iPhone - just the base model of the recently released 2026 iPhone.
Apple only released Pro models and the Duo this fall - no cheap phone in the bunch. Even their vaunted supply chain contracts couldn't withstand the AI datacenter stampede for RAM and SSDs in 2026.
As others have mentioned, the low end of smartphones are going to be hit bad if they even get refreshed at all in 2026/2027.
I know GrapheneOS has very strict requirements for its OS to run, but would it be great to have a "Graphene light" with lower requirements, and which would run on more phones, while telling people what features are not included... At least there would be another alternative to google
This is the use case for Lineage OS, which supports tons of devices. There is also PostmarketOS if you prefer Linux. Graphene has no interest in playing in this area and moving out of its niche would likely drain limited developer resources.
Almost every manufacturer except Google now locks their bootloader.
Google makes money off personalised advertisements and needs to do user tracking to do this properly. It also makes money from Google Play. Graphene threatens both of these streams. I expect Google to kill GrapheneOS in the next few years.
GrapheneOS has a partnership with Motorola. Part of the partnership is that they are meeting our hardware requirements, one of which is allowing the bootloader to be unlocked. So, if Google does stop allowing their devices' bootloaders to be unlocked, then we still have a partnership with Motorola and our partnership doesn't mean we have to work exclusively with them, so the door is open for more partnerships or devices.
My partner just upgraded from a Pixel 6 to a Pixel 10a, and because she needed a smartphone for work to (mandatory for auth, but fully paid for by her employer) she got the same Pixel 10a in a different colour.
The difference in just the user experience between her personal GrapheneOS device and the stock Android is huge. GrapheneOS may focus on security and privacy, but out-of-the-box it just offers a much cleaner install.
It sucks that Google is doing this. The past few years there has been a constant trickle of negative articles about Google locking down AOSP and hindering GrapheneOS. If there was some business case there it might make sense, but I get the impression that all GrapheneOS caused was more security for Android, and letting Google sell more Pixels.
The current state of devices which support GrapheneOS is not so nice. The choice is basically between Pixel 10a (around €400) or 10 pro (around €650) — as GrapheneOS cannot support Pixel 11 due to more Google lameness — or this new Motorola Signature 27 (around €1400).
Come on Google. Stop sucking at least on this front OK?
Mostly the absence of all sorts of preinstalled Google stuff she doesn't want. GMail, 'Home' (whatever that is), YouTube, Wallet, etc. A visual assault of primary colour icons, basically.
With all the reverse engineering capability offered by AI and the agents it is now a great time to start reverse engineering the shit out of these phones and all these other hardware blobs.
Try getting sensitive data from a Fritz Chip (aka Secure Enclave, Samsung Knox, TPM and similar), where it's mathematically impossible to unlock something.
The closest is we got is Yubikeys which requires destruction of the device to read the information via a firmware bug, and that has been fixed in new devices already.
AI is not a silver bullet, not every box can be pried open. E-Fuses are also a reality, when they're blown, they're blown. AI can't fix your nm sized e-fuses as well.
[dupe] Discussion on source: https://news.ycombinator.com/item?id=50570479
I've been on GrapheneOS for 3 years and I'm never going back to stock android. Once my phone stops being supported I'll switch to whatever hardware runs GrapheneOS. If that can't be done I will buy an iPhone with nothing but Signal and my authenticator app on it and turn on lockdown mode.
I am done dealing with built-in adware draining my battery and carrier bloat.
backporting security fixes to the GrapheneOS kernels has become essentially free. if GrapheneOS team doesn't maintain older devices for harm reduction, someone will.
Android enthusiasts are the buyers keeping Google Pixel alive. I cannot for the life of me understand why Google seems to hate Android enthusiasts.
Google seems to loathe all its users across the board. Whether it’s RSS, Gmail, search, Android, Fitbit, Youtube… Google constantly shows its users that the user means nothing to them. I’ve been moving away from Google tools as much as I can, but while I can’t do that with YouTube, my Gmail is now considered my “compromised” account and my logins I will slowly move over to a new email service.
Gmail won’t even save inbox changes on Firefox half the time. It’s wild how far Google products have fallen in quality and trustworthiness.
Because Google makes its money selling info gathered about its customers and GrapheneOS makes that way way harder.
Graphene really confuses me. They are, in terms of the personalities of people involved, eccentric to say the least. I don’t see a problem with that myself as plenty of security and privacy or even OSS are eccentric people. However it does make understanding their communication a bit of an art.
Also I don’t understand some of their technical choices, and due to the aforementioned eccentricity, it’s not productive to have a conversation with them about it.
The technical issues I don’t understand are: they insist their patched sandboxed GSM is superior to a reimplementation like microG, which is fine. But they can also surely consider a sandboxed microG. There is just no world where i see where grabbing a proprietary binary from a corporation and redistributing it with your own modification is ever gonna fly legally for any hw “partner”. There are many non-Google flavores of android that companies have been shipping just fine. Graphenes issues are entirely self imposed that it just borderlines on odd.
Another is their complete dependency on Google devices because of some self imposed requirement. People got reasonably upset when MS said “next windows requires a tpm”. It’s also just really odd.
> it’s not productive to have a conversation with them about it.
Some of the choices are hard to explain and we have to explain them all the time so that doesn't help either.
Maybe I can help explain the microG thing... microG only makes sense if a user is using apps with Google libraries that rely on Google Play Services. Those libraries are Google code. Some libraries for some functionality have fallback implementations, meaning they can run on their own.
Regular apps have a lot of restrictions compared to system apps and cannot request or obtain certain privileged permissions. The apps with Google libraries are normal apps and the libraries therefore have normal app permissions. On GrapheneOS, Google Play Services is a normal app without special permissions.
microG, on the other hand, needs privileged permissions for signature spoofing. It also doesn't enforce permissions as well as Google Play Services (which has caused leaks), and it needs to download binaries from Google for some functionality, so those binaries run in a privileged context. Finally, microG offers worse app compatibility, which they even admit in their repo's README.
You have to look at the big picture of what Google has access to. The breakdown is like this:
---
App with GMS library = access is restricted, like other regular apps.
App with GMS library + Sandboxed Google Play (unprivileged) = virtually the same access as above
App with GMS library + microG (privileged) = Google has the same access as the situations above, but with worse app compatibility, worse security (especially because of privileged access and possible Google binary running with in a privileged context), and worse privacy (leaks).
---
> Another is their complete dependency on Google devices because of some self imposed requirement.
GrapheneOS's main focus is privacy and security is important for strong privacy. The project doesn't only support Pixels because of some love for them. They were the only supported devices for a long time because they were the only ones that met the hardware requirements. Note 11th gen devices weren't supported for not meeting the requirements (although that has changed). We would have been happy to support more devices, but none met the requirements until our partnership with Motorola. We hope to support more devices in the future.
are you saying there is no way to get microG (or an otherwise a different implementation of play services) to run equally sandboxed? I’m admittedly not as knowledgeable about the topic as you probably are, but it just doesn’t pass the sniff test for me. I know that comparability would suffer, but the alternative is for your project to forever be in an infringing category. As I said, I don’t see a world where redistributing Google’s IP is ever gonna fly, which immediately limits the number of legitimate “partners” you can ever work with. I’m just being a realist here. We can wait for IP laws to get an overhaul globally, or have a solution that works in this century.
I get thr argument that the sandboxed Google play is the technically better solution. But it’s like if WINE went and distributed a copy of MS system32 folder instead. You’d get a better comparability for sure but it’s not a real solution.
As for the self imposed hardware limitation, you basically stated it in another way. It’s self imposed. It’s hard to see Google caring, and paradoxically you are only hurting your own users. I hope there is more choice because I’d like to use graphene at some point, but not if my choices are pixels or a 6.8” $1,500 phone. But maybe my use case is too niche I don’t know.
> Some of the choices are hard to explain and we have to explain them all the time so that doesn't help either.
You could maintain a FAQ? Maybe a little more work up front, but you could answer each question once and then refer back to it.
Bad news in general if true. The motorola phone prices are insane, so only the Pixels are really a viable option atm.
Make it illegal to lock down hardware like phones and cars.
I like GrapheneOS but the rug pull will eventually happen there too-- they're militantly anti-Copyleft, but using GPLv3+ would prevent many from playing those kinds of lockdown games.
All 2026 flagship phone prices are insane. Relative upgraded to an iPhone 18 Pro for almost CAD$2K. Not the foldable iPhone - just the base model of the recently released 2026 iPhone.
Apple only released Pro models and the Duo this fall - no cheap phone in the bunch. Even their vaunted supply chain contracts couldn't withstand the AI datacenter stampede for RAM and SSDs in 2026.
As others have mentioned, the low end of smartphones are going to be hit bad if they even get refreshed at all in 2026/2027.
This is why its important for graphene to exsist on non pixels as well.
I know GrapheneOS has very strict requirements for its OS to run, but would it be great to have a "Graphene light" with lower requirements, and which would run on more phones, while telling people what features are not included... At least there would be another alternative to google
This is the use case for Lineage OS, which supports tons of devices. There is also PostmarketOS if you prefer Linux. Graphene has no interest in playing in this area and moving out of its niche would likely drain limited developer resources.
https://lineageos.org/
Almost every manufacturer except Google now locks their bootloader.
Google makes money off personalised advertisements and needs to do user tracking to do this properly. It also makes money from Google Play. Graphene threatens both of these streams. I expect Google to kill GrapheneOS in the next few years.
GrapheneOS has a partnership with Motorola. Part of the partnership is that they are meeting our hardware requirements, one of which is allowing the bootloader to be unlocked. So, if Google does stop allowing their devices' bootloaders to be unlocked, then we still have a partnership with Motorola and our partnership doesn't mean we have to work exclusively with them, so the door is open for more partnerships or devices.
My partner just upgraded from a Pixel 6 to a Pixel 10a, and because she needed a smartphone for work to (mandatory for auth, but fully paid for by her employer) she got the same Pixel 10a in a different colour.
The difference in just the user experience between her personal GrapheneOS device and the stock Android is huge. GrapheneOS may focus on security and privacy, but out-of-the-box it just offers a much cleaner install.
It sucks that Google is doing this. The past few years there has been a constant trickle of negative articles about Google locking down AOSP and hindering GrapheneOS. If there was some business case there it might make sense, but I get the impression that all GrapheneOS caused was more security for Android, and letting Google sell more Pixels.
The current state of devices which support GrapheneOS is not so nice. The choice is basically between Pixel 10a (around €400) or 10 pro (around €650) — as GrapheneOS cannot support Pixel 11 due to more Google lameness — or this new Motorola Signature 27 (around €1400).
Come on Google. Stop sucking at least on this front OK?
Out of curiosity, what are the end user differences when it comes to Pixel Android and graphene os?
Just the play services?
Mostly the absence of all sorts of preinstalled Google stuff she doesn't want. GMail, 'Home' (whatever that is), YouTube, Wallet, etc. A visual assault of primary colour icons, basically.
Should be unlawful to sell a device where the device owner can not fully control the bootloader.
A locked bootloader is a form of grand larceny.
No Problemo.
With all the reverse engineering capability offered by AI and the agents it is now a great time to start reverse engineering the shit out of these phones and all these other hardware blobs.
Someone just did it for an Apple trackpad.
https://www.reddit.com/r/emacs/comments/1xydykw/emacs_in_the...
Try getting sensitive data from a Fritz Chip (aka Secure Enclave, Samsung Knox, TPM and similar), where it's mathematically impossible to unlock something.
The closest is we got is Yubikeys which requires destruction of the device to read the information via a firmware bug, and that has been fixed in new devices already.
AI is not a silver bullet, not every box can be pried open. E-Fuses are also a reality, when they're blown, they're blown. AI can't fix your nm sized e-fuses as well.
This is why I use an iPhone. Apple are well-defined assholes. Google on the other hand are unpredictable assholes.