600
GrapheneOS is finally ready to break free from Pixels, and it may never look back
(www.androidauthority.com)
very glad to hear this!
this post was submitted on 15 Oct 2025
600 points (99.3% liked)
Privacy
4057 readers
23 users here now
Welcome! This is a community for all those who are interested in protecting their privacy.
Rules
PS: Don't be a smartass and try to game the system, we'll know if you're breaking the rules when we see it!
- Be civil and no prejudice
- Don't promote big-tech software
- No apathy and defeatism for privacy (i.e. "They already have my data, why bother?")
- No reposting of news that was already posted
- No crypto, blockchain, NFTs
- No Xitter links (if absolutely necessary, use xcancel)
Related communities:
Some of these are only vaguely related, but great communities.
- !opensource@programming.dev
- !selfhosting@slrpnk.net / !selfhosted@lemmy.world
- !piracy@lemmy.dbzer0.com
- !drm@lemmy.dbzer0.com
founded 11 months ago
MODERATORS
Glad to know privacy isn't budget friendly.
Unfortunately a lot of "budget" items are being subsidized by your personal information, and the smaller market for privacy-forward goods and services makes economies of scale harder.
Unless governments start passing robust privacy laws, it will just continue to get more and more expensive to live privately with modern conveniences.
load more comments
(12 replies)
Yeah, it would be great if they would support a range of devices from whichever OEM this is, at different price points.
Biggest challenge GOS has is that most hardware vendors do not meet their fairly restrictive hardware security requirements, and those few that do don't typically allow bootloader unlocking. Pixel devices up until now have been unicorns in those regards.
load more comments
(3 replies)
load more comments
(1 replies)
load more comments
(2 replies)
Oh no, won't somebody think of Google's bottom line?!
That’s fantastic. Does this help with the issue of Google releasing AOSP security updates at a slower cadence? Maybe working directly with an OEM resolves this?
I don't really know how this works, but if they have the cooperation of an OEM they should have the same access to AOSP security updates the OEM has, and access to hardware drivers from a company that's not trying to thwart them. I can see how this would be preferable to a basically antagonistic relationship with Google, who are making things difficult because they want all Pixel phones to run their stock OS. The thing I wonder is what motivates the OEM to continue a cooperative relationship with Graphene OS.
load more comments
(3 replies)
They're extremely talented in the security/mobile/os arena, why not contribute to one of the Linux mobile projects and kill two birds?
Because people want to use apps, which unfortunately don't exist on the Linux mobile projects. Banking apps are the biggest issue in fact. Obviously for a lot of other things, anyone can create alternatives.
And the whole issue of not being able to use most modern hardware with mainline Linux kernel because the drivers are closed source binary blobs. You have to use a device-specific kernels.
load more comments
(2 replies)
Everyone out here guessing small OEMs for an official Graphene launch when it's obviously Apple.
Except that they mention Snapdragon, which Apple does not use.
They also mention “major Android OEM” Which does not apply to Apple.
tinfoil hat on It's obviously Apple funding this. They know most android users won't buy apples, they just want to weaken Google.
Could you imagine if apple created a Sub, where they made grapheneos iphones? Google would lose billions
I think you are harshly overestimating how many people use GrapheneOS or even care about what it stands for.
load more comments
(7 replies)
load more comments
(2 replies)
load more comments
(1 replies)
load more comments
(3 replies)
load more comments
(1 replies)
I know it almost certainly isnt, but please god let it be Fairphone.
It will not be Fairphone but OnePlus
Only took like twenty years
I thought Google's plans to kill AOSP effectively put a nail in Graphene's coffin?
Google has made it harder (it may kill AOSP in the long run but not yet) by delaying public release of source trees later than before. To counter that, they partnered with OEM, who in turn are partnered with Google, who are likely to get sources faster.
I still don't how they (and F-Droid) plan to bypass the whole de al with Google killing non-PlayStore aproved© apps, tho. GrapheneOS relies on that as well.
load more comments
(8 replies)
It does make sense it would be Nothing. I feel like the CEO reads the Youtube comments asking for GOS
load more comments
(2 replies)
It's America, it's going to be Samsung.
Nope , Motorola has snapdragon and you can unlock OEM
My $$ was on moto as well - it's already about the closest thing to stock and they probably need the boost.
Whereas Samsung is fucking worlds apart for actual android
load more comments
(5 replies)
load more comments
(3 replies)
I hope so, I love samsung's hardware and having a secure OS option to get out from under their godawful UI / OS stuff would be amazing.
load more comments
(2 replies)
load more comments
(2 replies)
view more: next ›