I am a Tasker enthusiast and when I can automate something simple on my phone I like to. I set a simple task to turn off WiFi when my home network is not detected so my phone doesn’t scan and report my location to businesses. However, this functionality is now nonexistent and the developer has to ask people not to one-star their app because it doesn’t work. My phone is my phone and killing my ability to use it as such for whatever security theater Google is playing at is why I root my device. Anyone else still rooting for similar reasons?

  • 𝒍𝒆𝒎𝒂𝒏𝒏@lemmy.dbzer0.com
    83·
    4 months ago

    I’m rooted to…

    • backup & restore my apps as I please (as well as scheduled backups to my SD card)
    • BMS control to keep my battery in good health
    • Automation app for automating stuff (like Tasker)
    • revoking typically unrevokable permissions from system and Google apps
    • To actually feel like I own my device.

    If I wanted a heavily curated (and somewhat locked down) experience, I’d be in the Apple ecosystem - don’t know why Google thinks it’s a great idea to force this ideology onto practically all Android users…

    Similar situation with that additional warning for sideloading apps - there’s already two warnings and Play Protect typically uninstalls these apps anyway, without the user’s consent - in one case deleting KDE Connect from users’ devices if installed with F-Droid

    Uhh I definitely went off on a tangent, oops.

    • Peffse@lemmy.world
      25·
      4 months ago

      I went into a near seething rage when I found out Android 12 let OEMs decide bloatware was completely immune to ADB disable commands. root’s the only method to get to the non-disable xml files and remove that “functionality”.