Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
@DacoTaco @[email protected]
@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.