←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.432s | source
Show context
asimops ◴[31 Oct 25 21:30 UTC] No.45776925[source]▶
While it is technically feasible, it is not a good idea to try and find a technical solution to a people/organisation problem.

Do not accept the premise of assholes.

I hope we can get the EU to fund a truly open Android Fork. Maybe under some organisation similar to NL Labs.

--- edit ---

Furthermore, the need for a trustworthy binary to be auditable to a certain hash or something would make banning this a simple task if Google would want to go that route.

replies(8): >>45777355 #>>45778228 #>>45778511 #>>45779765 #>>45779867 #>>45780458 #>>45780743 #>>45781937 #
1. Lindby ◴[01 Nov 25 14:35 UTC] No.45781937[source]▶
It would be hard to find manufacturers to use it. None of the existing Android phone manufacturers would be able to release phones with this fork without also abandoning the official Android platform on all markets. Google are very strict with this in their tos. You cannot release devices using non official Android builds without losing your right to use GMS and Android Brandice on your other Android devices.
replies(1): >>45789197 #
2. solarkraft ◴[02 Nov 25 10:13 UTC] No.45789197[source]▶
This can also easily be framed as anticompetitive.