>>719142658
>Anything that throws a fit over a rooted phone isn't worth installing
My mandatory work apps don't like the root on my Pixel 6, and I have to keep a tablet around just to check my schedule, this also happened with a friend who couldn't get onto hers either because she wanted to try a root just for adblocking, and the usual fixes and Magisk whitelists didn't help either, meaning this shit's probably demanding STRONG_INTEGRITY at the minimum now that SafetyNet proved useless (hackable)
>inb4 lmao@work
This has honestly been happening for a good decade, kinda slowly, but happening still, and Snapchat of all fucking companies spooked them into getting more hardline on mod hampering because women were throwing bitchfits on Tumblr about the existence of Casper way back when, i.e.
>how could someone save a picture of me on the internet?!??!?!? MODS?!?!?!??
which is why Snapchat is usually the first app to start going
>um your device doesn't look secure! so we logged you out so you can enter a failed-login loop until modders fix this, you rapist :)
after a big Magisk/Safetynet fix update. At first, it was mostly on the app devs on whether or not they wanted to play with a custom ROM, unlocked bootloader, root, or a combo of all 3, but SafetyNet getting unveiled was the first time Google themselves actively stepped-in to help them do it for free
A nuclear option is "pirating" keyboxes until they die for the extreme phonefags (Indians), but only when Azur Lane and Nikke stop working with fixes, only then will I acknowledge that rooting......... has fallen
Also: Google's bad, but in terms of completely fucking-up the Android open gimmick right from the start, that's on Samsung, where the dying breath of modding their recent (western) phones considered "send Galaxy to shady criminals in hopes their stolen Samsung tech enables OEM unlocking", which also trips an eFuse that'll nuke your ability to get updates, worst Korea, worst phones