@DacoTaco @Zak@lemmy.world
@kirk781 @android

Lemmy.world’s cloudflare doesn’t like the content of my reply, so posting from another account.

No doubt offering the user the opportunity to verify they’re running the OS they think they’re running is a Good Thing. I’m more skeptical of giving that ability to app developers, as Google has done.

> Root access also means apps can use and access api’s in android that it normally cant

Yes. That’s what it’s for.

> changing settings and things inside android it shouldnt.

Now there I disagree. AdAway *should* write than a bunch of advertising domains map to 127.0.0.1 in /etc/hosts. AccA *should* write settings that limit battery charge and extend battery service life to /sys/devices/platform/soc. Why should they? Because it’s my device and I want them to.

A more fine-grained mechanism for these system permissions would be very welcome of course. AccA should *not* write to /etc/hosts and does not need permission to do so in order to manage battery charge.

> bootloaders should remain locked but you should be able to somehow, in the bootloader, be able to add the os’ signature/keys to the bootloader’s trusted stuff like how secure boot on a pc keeps os signing keys and verification stuff inside the tpm.

This is pretty much how GrapheneOS recommends doing it, but only a few devices (mostly Pixels) allow unlocking, then relocking the bootloader. Keys can only be added while unlocked.