> Users need to regain control over their operating system.
GrapheneOS is not a direction in that, you're just trading one megacorp for different not-yet-megacorp. Both have security-first manifest, which means both insist on making the devices secured from their owners.
In the case of GrapheneOS, this is justified by its security model and is not intended to work against the user but rather to protect them. In addition, the source code is freely available, and it is very easy to create your own versions.
GrapheneOS is a non-profit organization.
IMO Graphene ties a good line between appliance and totally hackable.
They allow you to isolate google-apps - great.
They don't allow root - meh, I guess, but I'm not really trying to do real work on a phone (or I'll just use termux).
The fact you can't change the lowest levels of the operating system might be annoying if you're and Android developer (idk) but as a user its not so bad.
The great thing is they are open source. If a group of like minded people wanted to distrubute GrapheneOS but hackable I'm sure they could if they had the expertise and resources.
And if GrapheneOS somehow becomes malicious I'm sure someone will fork them and form a like minded community around different values.
With Graphene, at least, you can build your own image and strip out restrictions you disagree with. For example, you can restore root or excise enraging limitations like the ability to screenshot your own apps. The Graphene developers probably don't condone such modifications for various reasons, but you don't have to agree with them.
That is very inaccurate. GrapheneOS is open source and people are more than welcome to make their own custom builds. Although we don't support rooting, many do. That's up to them.