Bring on support for more devices, and I'll likely switch with my next phone.
this post was submitted on 21 Feb 2026
431 points (97.6% liked)
Privacy
47966 readers
921 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
founded 6 years ago
MODERATORS
They're working on an alternative device with a large OEM they've not disclosed yet. They're aiming at releasing it in 2027.
The smart money is they're going to go with Motorola, honestly idc who they go with it'll likely be my next phone
Same here, i can't wait to ditch my old xiaomi 10 full of bloatwares and ads
load more comments
(5 replies)
Its not up to grapheneos devs which devices support bootloader relocking with different keys, literally only pixels allow this and without it you cant properly secure the phone.
..without it you cant properly secure the phone.
My understanding is that a locked bootloader helps protect against evil maid attacks and bootloader-level malware persistence. I find this a security risk that I would absolutely take for Google independence. "Properly secure" is subjective.
GrapheneOS do decide what phones they support. It is exactly their choice to support only Google Pixels, rather than taking a security hit for hardware independence (whether you agree with the decision or not).
Exactly, seems like this should be up to the consumer. The devs can say: pixels have best security, here's a 2nd and 3rd option, here's their pros and cons.
Because as much as I approve of privacy measures and security, my phone doesn't have any lock screen. No pin, no biometrics, nothing.
I work from home, I don't really travel, I have 4 children. Physical security is annoying. I want grapheneos for data security. I don't have people trying to steal my phone, I do have people constantly stealing my data.
And without a non-pixel option (fuck google), I'm likely to go for to a competitor because, while their data security might not be as good as graphene, it is better than what I currently have.
load more comments
(1 replies)
GrapeneOS have a specific goal related to security. You can install one of the others, like LineageOS, if you are happy with the tradeoff.
load more comments
(1 replies)
load more comments
(3 replies)
not true, fairphones support that too. calyxos makes use of it, it's proven to be working
load more comments
(1 replies)
load more comments
(1 replies)
As an alternative, if you wanted something less secure, and more ethical, consider buying a Fairphone. However GrapheneOS does not support Fairphone at this moment.
load more comments
(1 replies)
Ok, a few things :
- I dislike her pronunciation of GrapheneOS really emphasizing the "ene" part
- For anyone not wanting to be stuck buying a Pixel, new or used (still kind of pricey), look into LineageOS /e/, or CalyxOS (though CalyxOS is paused for an interal audit or something)
- What about other data being sent over your carrier network outside of just Google? You're better off buying a plan for a mobile hotspot so it limits data that IDs you with your IMSI and IMEI info. Carriers otherwise still monetize your data, even though Google isn't getting it.
My next phone will be whatever I want that'll run LineageOS (sure, no "Titan chip") but will run F-Droid store, and only run on a hotspot I'll have with me (for work, goes in my work bag), anywhere else can sit in my car or pocket, etc. It'll help as I use private/FOSS apps, randomized MAC for WiFi, VPN services, etc. Hushed or done 2nd phone nine for WiFi calling, etc
I also have been social media free for over a decade now. No Amazon, no streaming services, and self-host anything I can
Technically you're posting to social media right here, but I think we all got what you meant.
(though CalyxOS is paused for an interal audit or something)
More like "Nick Merrill (the guy who fought NSL letters in court and started the project) and the lead developer departed without a single word and took the project's signing keys with them". You draw your own conclusions, but for me (a long-time CalyxOS user) those were huge red flags and caused me to settle on iodéOS for my new home.
load more comments
(11 replies)
What do you compromise these days going to something like graphene versus a stock pixel? I know the advantages obviously, just wanting clarity on trade offs. Features that become unusable, vulnerabilities, etc.
The loss of most banking apps and Google Wallet (tap and pay). For me, those are the killer features you lose. And the reason I gave up on custom ROM's on a FairPhone 3+ after many years.
I think "most banking apps" depends on your location. I never had any problems with them.
Yeah Google Wallet not working is annoying, but for me it's a good tradeoff.
It's not a location thing . . it's a per-banking app thing. And specifically it's a "does your banking app use Google Play integrity API" thing. On LineageOS running on my FairPhone 3 . . my banking apps all worked . . . until the day they didn't. Here is a table reporting the current state of banking app comparability around the world . . but the next update from any specific bank could (and in my case did) break it -
PS. In the UK I did actually find an alternative to Google Wallet. . . Curve Pay. Not open source, but not dependent on Play Services. And enabled tap and pay on LineageOS.
load more comments
(4 replies)
load more comments
(3 replies)
view more: next ›