3 ms·

A ROM being "rooted" in the Android context has a very specific meaning: Namely, apps can simply request root access and, boom!, they will have it after the mer

A ROM being "rooted" in the Android context has a very specific meaning: Namely, apps can simply request root access and, boom!, they will have it after the mere tap of a button. (It should be obvious that for security reasons this is not something that should be available to everyone and their grandpa.) So no, I don't see a contradiction here. For instance, I'm running LineageOS on my one phone and stock Android without GApps on my other, so in both cases I'd say I have full control over what's running on my phone. But neither of my phones is rooted.

nybble41 6y ago
> (It should be obvious that for security reasons this is not something that should be available to everyone and their grandpa.) If they own the phone and that's what they want then it should be available to them. > Namely, apps can simply request root access and, boom!, they will have it after the mere tap of a button. How easy the root account should be to access is debatable. I agree that one-tap-root by default without some kind of authentication beyond physical access is probably not the best idea, but I don't think that is what the OP was proposing. The point is that the owner should have root access to customize the software if they want it, without begging anyone's permission (e.g. phones requiring a code from the manufacturer to unlock) or having key features disabled (e.g. "SafetyNet").
- codethief 6y ago
  > > (It should be obvious that for security reasons this is not something that should be available to everyone and their grandpa.) > If they own the phone and that's what they want then it should be available to them. Not if what they want and don't want entirely depends on how well informed they are. Keep in mind that malicious apps do everything to convince their users to grant them the necessary permissions. > The point is that the owner should have root access to customize the software if they want it, without begging anyone's permission (e.g. phones requiring a code from the manufacturer to unlock) or having key features disabled (e.g. "SafetyNet"). Then we agree. :)

nybble41 6y ago

> (It should be obvious that for security reasons this is not something that should be available to everyone and their grandpa.) If they own the phone and that's what they want then it should be available to them. > Namely, apps can simply request root access and, boom!, they will have it after the mere tap of a button. How easy the root account should be to access is debatable. I agree that one-tap-root by default without some kind of authentication beyond physical access is probably not the best idea, but I don't think that is what the OP was proposing. The point is that the owner should have root access to customize the software if they want it, without begging anyone's permission (e.g. phones requiring a code from the manufacturer to unlock) or having key features disabled (e.g. "SafetyNet").

codethief 6y ago
> > (It should be obvious that for security reasons this is not something that should be available to everyone and their grandpa.) > If they own the phone and that's what they want then it should be available to them. Not if what they want and don't want entirely depends on how well informed they are. Keep in mind that malicious apps do everything to convince their users to grant them the necessary permissions. > The point is that the owner should have root access to customize the software if they want it, without begging anyone's permission (e.g. phones requiring a code from the manufacturer to unlock) or having key features disabled (e.g. "SafetyNet"). Then we agree. :)