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
This is a very complex topic that is very hard to draw the line on.
As a technical person who follows hacking and security news i can understand google introduced the api and warnings, as phones are getting hacked and unlocked bootloader or root can be abused to keep your malware going, and has been abused in the past.
But as a user of fairphone/lineageOS, who tells google, apple, meta, ... all of them to fuck off when i can, this scares me. The lockdown of devices can and is going too far. Hell, i even consider samsung's android ui changes to be going too far, as it changes a shit ton of stuff and really is not a stock android experience. It locks users in their environment..
I find it funny that Google and some banks are so worried about security on Android that I have to have up to date system, app and can't be custom ROM, can't be rooted and whatnot. And then they'll allow you to login to their bank from Internet Explorer on XP or some shit.
This. This, this, this, this!
My linux computers are rooted. I can get root any time i need it and nobody is refusing to offer their sevices on linux because it is vulnerable.
Nobody ever points out that when any app wants root, you get a dialog to ask if it can have it. If you don't know why it's asking, say no. It ain't rocket science.
Now, if you are going through customs and you don't want them to copy your phone and read all your personal documents, that is a different situation. Lock your bootloader unrooted and encryped to the nines. Preferably use a phone with almost nothing on it.
That's not quite true, though in that case it's about the service provider being unable to verify that the user isn't running a operating system configured or modified to work against the interests of the service provider.
Written with a slightly more precise wording, they know Linux users have full control of their devices, so cannot keep them from using it in ways the company does not like. In this case, fine. Go away and take someone else's money.
Stated from another angle, they won't support it because they can't hijack it for their own purposes.
Stock android experience is the exception, not the norm, sadly. Some manufactures like Motorola or HMD have a light touch and close to stock but other ones don't. The worst offenders are Chinese brands who twist it so much and without much benefit(Atleast, Samsung's ONE UI is customizable as heck, can't say the same for Realme's).
Can you cite examples of rooted smartphones leading to significant data breaches or financial losses? When the topic comes up, I always see hypotheticals, never examples of it actually happening.
It seems to me a good middle ground would be to make it reasonably easy (i.e. a magic button combination at boot followed by dire warnings and maybe manually typing in a couple dozen characters from a key signature) for users to add keys so that they can have a verified OS of their choice. Of course, there's very little profit motive to do such a thing.
Pre-locked bootloader times ive had multiple android devices be passed to me that were malware infected that changed the rom in a way that even a factory reset would not remove the malware. Locked bootloaders made it so the rom needed to be signed and unaltered on boot, fixing this. Root access also means apps can use and access api's in android that it normally cant, changing settings and things inside android it shouldnt. What do you think happens when malware comes in? :p
Imo, i agree what you said. 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 way you can install lineage os for example, tell bootloader to trust it, and lock bootloader again so nothing can be changed anymore.
I wouldnt take this from user input, as that is controlable by malware, but rather come from the OS itself. Maybe even during installation, idk
@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.