Its best explained by this thread: https://mstdn.jp/@GrapheneOS@grapheneos.social/117645039420648634
TL:DR is that Google’s business side is threatening to revoke android licenses from phones that support GOS and is likely planning to lock the bootloaders on Pixel phones going forward. Important to note is that in GOS own words, the actual Google Android team is seemingly not down with it and has helped GOS work on things like Vanadium. As it stands it seems like Graphene is trying to take legal action against Google.
Edit: apparently they’re also on track to start making new Android feature updates exclusive to the Pixel line of phones. We’re really in for a major shakeup in the phone market it seems.


I love the idea of a Linux phone, I’m not against it, but GrapheneOS already exists, and all it needs is hardware to not be dicks, which a real Linux phone also needs.
If there was one hardware manufacturer that could just put out a respectable handset that wasn’t actively trying to sabotage some kind of community effort, I think it would be a great boon to both Linux phones and GOS users alike.
I think it’s fairer to say that Graphene OS makers AND Hardware makers are both being dicks.
If either side conceded I bet Graphene OS would be far more prevalent, even if it had to be “Graphene OS Basic” rather than the full maximum security version.
How is having hardware requirements being “dicks”? The whole point of GrapheneOS is privacy and security is important for strong privacy. Lowering our standards doesn’t help the project or our users. Having a less secure version of the OS would effectively mean a lot more work for a worse OS. We’d need to hire a lot more people to support that additional OS as well as all the new devices we’d support. It just doesn’t make sense.
It only doesn’t make sense if you’re taking A SIDE.
For anybody looking at it from the outside, the objective of smartphones freed of big-corporation controlled OS is being blocked BOTH by GrapheneOS refusing to have a version of their OS that works without very specific hardware that’s only needed for highly hardenned security AND by phone makers being unwilling to make phones with that hardware.
Either side conceding would solve the problem for the rest of us and any evidence-free claims that it’s easier for one side than the other are just bullshit excuses from those taking sides rather than looking at the big picture.
I don’t understand… Of course I’m taking a side: GrapheneOS’s side… since I’m a member of the project. I don’t try to hide it and even said “we” in my comment. Maybe what I said earlier will make more sense now. The requirements won’t be relaxed. Even the 11th generation Pixels aren’t supported now because, until recently, they didn’t meet the requirements.
I think you may be confused about the purpose of grapheneOS. If what you want is a phone OS that’s free of big corporate control, even if it sacrifices some security, lineageOS is right there.
The whole point of grapheneOS is highly hardened security without compromise. That comes with certain hardware requirements and so far only Google and Motorola meet them. It’s not about corporate control or marketability or being an open source alternative for everyone or whatever. There are people who actually need the security provided by grapheneOS, where a compromise could be the difference between going to prison or not. Those people are graphene’s core userbase and they count on the developers for their literal safety. So it’s no surprise that the developers are not willing to compromise on the core of the product.
I’m sure they would be very happy if pine64 or fair phone or some other less evil corporations started making cheaper phones that include the required hardware, but they aren’t going to step back on security to support more phones because the security is the point.
This whole thread is following down from me answering this in somebody’s post that answered my own point about desiring Linux for Smartphones.
GrapheneOS is focused on heavily hardened security, which is fine.
My Linux suggestion is about freeing people from corporate control and more broadly about having an open ecosystem for smartphones which also further helps with avoiding impositions around such software from governments which are straight authoritarian or have authoritarian tendencies. Part of the point with that is that it doesn’t require different hardware than what we have right now in all smartphones, it just requires software support for Linux from the hardware makers in the form of drivers and device tree configs.
It doesn’t really make sense to dismiss the idea of Linux by saying that we should instead be using a heavily hardened smartphone OS which requires special hardware and it’s really all fault of hardware manufacturers who are being dicks for including in their phones the hardware required only by that specialized OS.
It’s kinda funny that in this merry-go-round we ended up with you making almost the entire opposite point of the post that started all this - that GrapheneOS has a different purpose and thus it’s not meant to do what Linux on smartphones would.
Well, thank you, that’s my point, from which follows that it’s all a bit more complex than hardware makers being dicks by not catering to the needs of a specific highly specialized smartphone OS (though IMHO they ARE being dicks by keeping their hardware locked down and not supporting alternative OSes, something that would not cost them anything per-device since no additional hardware is needed for that).
GrapheneOS is a specialized OS with special hardware requirements so why are general smartphone hardware makers being dicks for not catering to this specialized OS? Seems to me that it’s very much a case of “it takes two to tango” - if GrapheneOS has special needs then it needs to find its very own special partners not expect that everybody should be catering for their needs, and by the way finding appropriate partners is exactly what they’re doing right now with Motorola.
It sounds like we mostly agree, the point I’m responding to in your previous comment is that grapheneOS is not blocking anyone from doing anything. They are not stopping anyone from trying to make a practical Linux phone, even if people misunderstand the purpose of graphene.
Well, if the impression I passed is that I believe that GrapheneOS is somehow blocking Linux on smartphones, then I have expressed myself incorrectly since that’s not at all what I think.
Sure, but GrapheneOS’s main focus isn’t security even if the project is famous for it. Security is important, though.
“GrapheneOS is a privacy and security focused mobile OS with Android app compatibility developed as a non-profit open source project. It’s focused on the research and development of privacy and security technology including substantial improvements to sandboxing, exploit mitigations and the permission model. It was founded in 2014 and was formerly known as CopperheadOS.”
That’s literally the opening paragraph of graphene’s own website.
That’s not how security works though. There are hardware requirements in order for certain software features to work.
To make a less secure phone in both OS and hardware is more marketable, but it defeats the purpose.
Funny your confident proclamations about how security works or not.
Security isn’t an absolute and in fact there is no such thing as absolutely secure - as smart-chip technology long ago showed when attackers started reverse engineering the keys stored in the supposedly secure smart-chip hardware by tracking energy consumption when the chips were using them for encryption or digital signing, even supposedly super secure hardware is only secure against certain kinds of attackers.
(Also don’t get me started on techniques involving liquid nitrogen and electron microscopes)
Security is a range and IT Security design is done on the basis of answering the question “secure against which kind of attackers?”, which is why banking system security is not the same as blog website security.
So the question is, can GrapheneOS make a system which is secure against external attackers whilst not having specific cryptographic hardware?
Because it would be a big fucking leap forward if your smartphones couldn’t be remotely turned into surveillance devices or their contents accessed by Google or by those who can get Google’s cryptographic keys for things like software updates (i.e. state actors), and generally the cryptographic hardware is only needed to secure systems against access by people with physical access to the hardware, not against remote access, especially not against the OS maker themselves.
Sure, some people do worry about the likes of the TSU confiscating and cloning their phones at a border entry and latter hacking its contents - and those people should stick to GrapheneOS and whatever the hardware that team things is needed for it to be safe against that - but most people just want their private data to remain private in everyday life, and everyday life for most people does not involve their smartphone being confiscated by the authorities of authoritarian nations like the US.
Would grapheneos basic == lineageos?
I don’t know.
How independent is the LineageOS software from Google, especially from things like Google Play?
Google apps are an afterthought in LOS. You can install them, or not. By default it’s entirely google-less, afaik.