Replying to an earlier post

I’m pretty sure that custom roms will remove that 24hr wait period from their binaries. Android is still open source and removing a check isn’t going to be very hard for them.

The tech ecosystem is as open as you can. Use linux. Use SearxNG. Use graphene or other custom roms. There’s options out there, you just have to start adopting them instead of just complaining online about having no choice.

Replying to @⁨Duckling5746@lemmy.today⁩

I don’t get it, how tf they gonna stop you on phones that already exist?

A. You can disable any new OS or device updates from Google.

B. You can keep your existing phone on Android 16 or prior (hell, I’m on 12)

C. Use alt OS like Graphene, Lineage, Iodé, /e/OS, CalyxOS (they’re back!!), etc

D. Sign out of Google on your phone, install F-Droid or something from APK package on FF derived browser.

I’m sure on brands new devices with that patch, plus anyone who doesn’t disable the auto updates will be blocked. But no way no how can Google stop us all!! 🖕🖕🏻🖕🏿🖕🏼

Replying to @⁨unitedwithme@lemmy.today⁩

I think the goal is to push it silently as a Google system service, rather than wait for manufacturers to ship an OS or app store update.

There’s a real possibility your phone already has Android Developer Verifier installed and sitting dormant until enforcement begins.

You can check for the package now:

“com.google.android.verifier”

If it’s there…well…

Replying to @⁨shonkyshonky@piefed.blahaj.zone⁩

Nah…we need digital divergence.

Dumbphone + tethering.

Let the phone manufacturers and carriers handle the “phone” part-with all the messy IMEI whitelisting, compliance and VoLTE shit.

The good stuff can live on a small Linux tablet.

No need to wait for the perfect Linux phone OS, working diallers, carrier support and all the rest of it.

The solution is already here. We just need to stop insisting that it all has to be one device.