I'm rooting to...

Remove Google

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".

shoutout to USAA banking app that detected my root, but just showed a warning and allowed me to continue. that's how it ahould be imho

github.com/daboynb/PlayIntegrityNEXT

It was in response to the Naomi Brockwell post she did on Twitter about businesses using WiFi, Bluetooth and Location Services to track you in public locations. You can Google it directly "NBTV Advice from Defcon" or this link: https://nbtv.substack.com/p/advice-from-defcon-turn-off-bluetooth

It barely works for Android 14+ without root. Macrodroid has much better compatibility for whatever reason.

Unfortunately rooting while passing safetynet verification is very hard or impossible lately depending on the device. If apps didn't unnecessarily check safetynet status this wouldn't be a problem, but since so many now the rooted phone effectively becomes a brick. I really miss the days of custom ROMs and full device automation without stupid workarounds. Unfortunately, I don't think there's any going back without app developers getting on board with an alternative to Google-verified security on Android.

iOS open

So open that you need an app to send a file over Bluetooth....

Well, you need Tasker because that's one of the Android equivalents of the Shortcuts app.

You've misread that. When he leaves his home network, he has it switch off wifi to prevent it being picked up by other networks. Probably has it being switched back on by cell tower / similar location option

Rooting a device is a process that depends on the phone and manufacturer. On some devices it is flat out impossible, on other it is trivial (those tend to be increasingly rare). The steps usually go something like this

1. Put your phone in developer mode
2. Unlock the bootloader (that's the part that is manufacturer/phone dependent)
3. Use fastboot to install a replacement bootloader (I used TWRP in the past, now I use Orangefox)
4. Once you have a good bootloader, youll be able to install apps from outside Android. This will enable you to give those specific app root access.
5. Install Magisk or superSu or whatever app that gives you root access once booted back in android.

Keep in mind that you can 100% brick your phone doing this and that it'll most likely void your warranty. Do not root your device following this post alone. I tried to answer an ELI5, not a Teach Me How To Do It Like I'm 5.

More information:

• bootloader : that's like the BIOS of your phone. It's software that is used right before your OS (android) launches
• fastboot : that's a mode you can set your phone in that will enable you to run commands via a computer to which your phone is plugged by usb. You can upload custom code to it this way (such as a replacement bootloader)
• https://orangefox.download/

Depends on your device

Google has a disproportionate and overwhelming say in AOSP. What do you think Lineage OS is based on?

When Google makes API changes to Android, it hurts AOSP too. Can the devs try to maintain the legacy API on their own? Sure, but it's extra effort, so it's usually not something you can count on.

Security and Privacy are not the same thing.

Stock Google is absolutely a hit to ones privacy, but LineageOS is a often big hit to device security.

If you don't have a Pixel, and therefore can't use GrapheneOS, check and see if your device is compatible with DivestOS.

However, neither will offer root support for reasons that both devs have decent write-ups explaining within each project's documentation.

I do realize that not everyone places security above all other factors when deciding on their smartphone OS, but I think they should be aware of the trade-offs so they can make an informed decision.

Both are based on AOSP, same issue there.