> rather than taking away the power from the user for the device they purchased
I disagree with that. Not having root doesn't mean it's inherently anti-user. I use GrapheneOS without root and am still in total control of my device.
I don't know anything about Android permission system is built atop linux, what does it mean when you say giving an app 'root permissions'?
I'd rather have the ability to enroll my own keys so I can boot my own signed OS and maintain a root of trust that I own much like what can be done on desktop Linux with a TPM. IIRC Google's Pixel phones have this ability (and are one of the few phones that have this ability if I'm not mistaken).
That would not be the correct usage of the term "rooting". "Rooting" on Android systems generally means to install a `su` binary (like Magisk) that you can use to give apps root permissions, thus completely circumventing the normal android app permission system.
> I'd rather have the ability to enroll my own keys so I can boot my own signed OS and maintain a root of trust that I own much like what can be done on desktop Linux with a TPM. IIRC Google's Pixel phones have this ability (and are one of the few phones that have this ability if I'm not mistaken).
I agree completely. I have a Google Pixel and use this with GrapheneOS.
This feature is `called avb_custom_key`, and yeah, unfortunately only some devices support it.
WarOnPrivacy•5mo ago
Meanwhile, it's non-rooted phones that get endlessly compromised
All that said, the article really does go into detail. I know enough to follow along but probably not enough to spot issues (if there are any).ThePowerOfFuet•5mo ago
With the notable exclusion of GrapheneOS. (It's also Cellebrite-proof going on three years now.)
diogenes_atx•5mo ago
hulitu•5mo ago
Does Whatsup run on GrapheneOS ? Asking for a friend /s
preisschild•5mo ago
You can install GrapheneOS/Lineageos without root. And you can install a su binary on the stock OS, not improving privacy at all.