←back to thread

A theoretical way to circumvent Android developer verification

(enaix.github.io)
194 points sleirsgoevy | 2 comments | 31 Oct 25 20:20 UTC | HN request time: 0.413s | source
Show context
zb3 ◴[31 Oct 25 22:06 UTC] No.45777208[source]▶
Well, I'd rather verify myself with the government identity than accept a stock OS that literally woke me up with a fake message promoting Gemini despite me spending almost 2 hours turning every possible privacy-invasive setting off.

To me, the attention to these verification changes seems misplaced. We need to defend the ability to unlock the bootloader, pressure Google to revive AOSP and then encourage people to switch to a more user-friendly OS.

You're already unable to install what you want on a stock OS due to Android permission model treating you as a third-class citizen, after Google and OEMs.

replies(2): >>45777629 #>>45780976 #
1. sleirsgoevy ◴[01 Nov 25 11:59 UTC] No.45780976[source]▶
The issue with government IDs is that they are, for all we know, not trustworthy, but everyone treats them like they are. And you know, I am not going to "verify" myself with Google with this kind of toilet paperwork.

If Google decides to pull this off, then I guess reflashing to a custom ROM with this crap patched out will be a very first step I'll be recommending to anyone who cares.

replies(1): >>45785629 #
2. zb3 ◴[01 Nov 25 21:36 UTC] No.45785629[source]▶
It seems you missed my main point - the whole point is to fight for this right to reflash a custom ROM, because they're slowly coming for that too. First Play Integrity, now no AOSP releases and more vendors disabling bootloader unlocking..