Another more important angle: GrapheneOS creates an appliance, where the user has no freedoms, in that freedom aspect not better than stock Android: The users c

Another more important angle: GrapheneOS creates an appliance, where the user has no freedoms, in that freedom aspect not better than stock Android: The users cannot realistically change any aspect of the OS. Sure, technically they could edit the source, but then they need to compile the whole system, reset their device and lose all data, be cut off from easy updates, and additionally lose remote attestation (which GrapheneOS devs call anti-competitive when used against them, but then gladly provide a variant that inevitably will be used against users.) Users cannot wield any more power over their apps than the apps admit. They cannot patch a binary app that misbehaves. They cannot reroute the environment of that app. And so on. With AOSPs and Graphenes "security model" there is nothing in-between "dumbest user" and "full-blown developer who cannot even be a proper user of that development system". The user to "advanced user" to "power user" to "tinkerer" to dev pipeline is kept dry. Most of power-user's potential self-defense mechanisms against abusive and monopolist app and service providers are intentionally neutered by Android as well as GrapheneOS. And hopefully less so by "Linux Phones"