3 ms·

I saw a few negative reviews on Google Play arguing that a turn key solution might let some people not read the detailed instructions, warnings and risks thorou

I saw a few negative reviews on Google Play arguing that a turn key solution might let some people not read the detailed instructions, warnings and risks thoroughly. Being a CM user, I must say I agree with this. Reminds me of a thread in XDA where a post read - If you are asking the question what is root, then you probably don't need it (paraphrasing). Let alone the instructions/warnings/risks, I know many Android users who barely go through the permissions they grant an app during installation. A little off topic, but an instance that I thought impressed the gravity of the risks and partly cracked me up was the warning on Alpharev [1] "Warning: Make sure you have read all the warnings below before attempting to run this utility!" [1] http://alpharev.nl/ http://alpharev.nl/

tracker1 13y ago
I'd have to agree with the sentiment about, "if you are asking what root is" and not needing a custom rom. I rooted my first couple android phones (first being the original G1), and my most recent (Nexus 4) I didn't need to (yet), it's still seeing regular updates, and wifi tethering is in the box. I might once it's no longer receiving updates, but will likely sticking with what I have for another year. I think that for the most part, it's a risk.. the first few years of tablets really needed third party updates, because first party were horrible.. same for some phones. I also find that mfg skins are equally bad. That said, clear warnings, even multiple warnings are important. When I rooted my G1, IIRC, there were several downloads I needed.. downgrade X, upgrade Y, root, upgrade X, install C, then B, then R... then apply GAPPS, etc. It was very unnerving, and that was important for me to triple check everything. I needed the extra functionality... While, as a user, I appreciate a click/next/next/done experience. It just depends on the risks. Note: I have the same paranoia when updating a computer CMOS/BIOS
thaumasiotes 13y ago
> Let alone the instructions/warnings/risks, I know many Android users who barely go through the permissions they grant an app during installation. There's a reason for this. I do go through the permissions that apps ask for, which is why I end up never upgrading any apps. The hugest problem is that the permissions are all ridiculously open-ended. There are apps that ask for permissions there's no reason for them to have; that's not what I'm complaining about here. I've installed apps where every permission they ask for is something they obviously need in order to function at all -- or, I should say, includes something they obviously need in order to function. The permissions are so inclusive that every app is allowed to do terrible things if it's able to function at all. This isn't an improvement over the windows XP model of "everything runs as administrator". And so, if you're going to be installing apps, there is no reason to read the permissions they request. Any permission you give is enough for the app to screw you over 1000 different ways.

tracker1 13y ago

I'd have to agree with the sentiment about, "if you are asking what root is" and not needing a custom rom. I rooted my first couple android phones (first being the original G1), and my most recent (Nexus 4) I didn't need to (yet), it's still seeing regular updates, and wifi tethering is in the box. I might once it's no longer receiving updates, but will likely sticking with what I have for another year. I think that for the most part, it's a risk.. the first few years of tablets really needed third party updates, because first party were horrible.. same for some phones. I also find that mfg skins are equally bad. That said, clear warnings, even multiple warnings are important. When I rooted my G1, IIRC, there were several downloads I needed.. downgrade X, upgrade Y, root, upgrade X, install C, then B, then R... then apply GAPPS, etc. It was very unnerving, and that was important for me to triple check everything. I needed the extra functionality... While, as a user, I appreciate a click/next/next/done experience. It just depends on the risks. Note: I have the same paranoia when updating a computer CMOS/BIOS

thaumasiotes 13y ago

> Let alone the instructions/warnings/risks, I know many Android users who barely go through the permissions they grant an app during installation. There's a reason for this. I do go through the permissions that apps ask for, which is why I end up never upgrading any apps. The hugest problem is that the permissions are all ridiculously open-ended. There are apps that ask for permissions there's no reason for them to have; that's not what I'm complaining about here. I've installed apps where every permission they ask for is something they obviously need in order to function at all -- or, I should say, includes something they obviously need in order to function. The permissions are so inclusive that every app is allowed to do terrible things if it's able to function at all. This isn't an improvement over the windows XP model of "everything runs as administrator". And so, if you're going to be installing apps, there is no reason to read the permissions they request. Any permission you give is enough for the app to screw you over 1000 different ways.