>What else should they have done?
Use an AOSP fork like grapheneos or lineageos. Barring that, voting with their wallets and buying a HarmonyOS phone. If for whatever reason they're doing that too, there's probably more powerful forces behind this change (eg. government mandates) that won't be helped by spamming an issue tracker.
Re:Android May Soon Restrict On-Device ADB
by aceazzameen on Saturday July 25, 2026 @10:19AM
(#49047769)
Downside is those specific forks only work on very specific devices, when there's countless great hardware in the wild with shit software.
And apparently a lot of people can't access their savings with grapheneOS. I know eventually I'm going to end up carrying 2 devices.
Re:Android May Soon Restrict On-Device ADB
by Gander5739 on Sunday July 26, 2026 @05:20AM
(#49056207)
Lineageos works on about 300 different phones, and you can flash a GSI for partial support on others.
Re:Android May Soon Restrict On-Device ADB
by NotPractical on Saturday July 25, 2026 @12:41PM
(#49049085)
I have bad news for you if you think GrapheneOS isn't going to accept this patch from upstream if it lands.
Re:Android May Soon Restrict On-Device ADB
by inigyou on Saturday July 25, 2026 @03:09PM
(#49050589)
Graphene would probably make it an option, like how it asks you if apps should be able to access the internet.
That's a non-issue because you can build (or patch+resign) grapheneos yourself.
Re:Android May Soon Restrict On-Device ADB
by matheusmoreira on Saturday July 25, 2026 @04:47PM
(#49051408)
But if you do, it fails attestation which turns the phone into a paperweight.
Apple has had this feature for three years on iOS. What else should they have done?