I will be happy to report back if desired.
That would be great. If you could collect and post screenshots of the various data-gathering forms (with PII redacted), that would be very useful for us to assess the scope of the data they will be requiring.
And the Last Page
@amarradi Marcus. I have merged all images to one post & locked it to keep the images there. So that the evil foogle cannot move away with such proofs in place. 
Let me know if you wish to edit the post(s). You can add as new anyway.
Thatâs ok. I no longer wish to edit my post. Thankâs for your work on this post
Well, I donât think Google is going to allow software from unregistered developers to run on AOSP either. Because thanks to a new bill in California (that I donât foresee getting vetoed), that would be ânegligentâ and subject to fines of $2700 per child that the Office of the Attorney General of the State of California finds was installing software without the developer logging it.
I might go as far as to argue that this bill is the reason theyâre doing it.
What nonsense. Seriously!!
What they say: âThis will protect childrenâ
What they mean: âThis will allow us to spy on you and get away with itâ
The Android 16 QPR2 Beta 2 announced at Android Developers Blog: Android 16 QPR2 Beta 2 is Here :
Testing developer verification
To better protect Android users from repeat offenders, Android is introducing developer verification, a new requirement to make app installation safer by preventing the spread of malware and scams. Starting in September 2026 and in specific regions, Android will require apps to be registered by verified developers to be installed on certified Android devices, with an exception made for installs made through the Android Debug Bridge (ADB).
As a developer, you are free to install apps without verification by using ADB, so you can continue to test apps that are not intended or not yet ready to distribute to the wider consumer population.
For apps that enable user-initiated installation of app packages, Android 16 QPR2 Beta 2 contains new APIs that support developer verification during installation, along with a new adb command to let you force a verification outcome for testing purposes.
adb shell pm set-developer-verification-resultBy using this command, (see adb shell pm help for full details) you can now simulate verification failures. This allows you to understand the end-to-end user experience for both successful and unsuccessful verification, so you can prepare accordingly before enforcement begins.
We encourage all developers who distribute apps on certified Android devices to sign up for early access to get ready and stay updated.
It could be interesting to try turning this on and seeing what the experience is for F-Droid when attempting to install apps that are not verified.
Gestern Abend habe ich eine Nachricht erhalten, dass GOOGLE fremde Apps ab dem 27.02.2026 nur noch funktionieren wenn die Entwickler ihre oersönlichen IdentitĂ€tsdaten an Google ĂŒbermitteln. [https://developer.android.com/developer-verification?hl=de](javascript:void(0)
Hallo @AWEG ,
klingt interessant aber woher nimmst Du das Datum 27.02.2027. Aus der Roadmap lese ich das im MÀrz die Verifizierung geöffnet wird.
GrĂŒĂe
Developer blocked: Package Installer
Added in version 36.1
DEVELOPER_VERIFICATION_FAILED_REASON_DEVELOPER_BLOCKED
public static final int DEVELOPER_VERIFICATION_FAILED_REASON_DEVELOPER_BLOCKED
DEVELOPER_VERIFICATION_FAILED_REASON_NETWORK_UNAVAILABLE
public static final int DEVELOPER_VERIFICATION_FAILED_REASON_NETWORK_UNAVAILABLE
what did you do to get that message? Device ? Android version?
Hallo.
Ich habe 2 Android GerÀte. 1x Samsung Galaxy Note 20 Ultra 5G und 1x Samsung Galaxy Tab A9 Plus 5G.
Die Meldung bekomme ich wenn ich WHO BIRD öffne.
ah, right, known thing GitHub - woheller69/FreeDroidWarn the developer is making users aware of the issue 
Dir wird die Meldung angezeigt, weil
Es liegt also bei den App an Entwickler. Wenn Du seinen GitHub Account ansiehst wirst Du mehrere Apps entdecken, die von ihm entwickelt werden und den Hinweis enthalten.
Ich schreibe es noch mal in Englisch vielleicht hilft es den einen Oder anderen
You are seeing this message because:
The developer is not willing to comply with the request.
The developer wants to warn the community.
And the developer of the WhoBird app would stop developing it.
He has written an extension that displays these windows. Here is the source code for it ( GitHub - woheller69/FreeDroidWarn )
So itâs up to the app developer. If you look at his GitHub account, you will find several apps that he has developed that contain the notice.
Even if they add it to AOSP (which I still think is very unlikely) itâs pretty trivial for ROM developers to bypass that. Just remove the check altogether or have the check always return a positive result. I donât think Google will add it to AOSP because itâs already going to be implemented into GMS which every certified Android phone will already ship with and itâs so easy to bypass when you can literally just patch out the check.
I guess all these will get the warning: F-Droid Search: woheller69
Yup. He made changes to his code. Example the browser one 2 days ago: V3.4 · woheller69/browser@b6f5974 · GitHub
@whyorean
Edit/Update: Rahul suggested the following:
Could webapps be an alternate to these censorships?
~30% of apps on FDroid could be a functional web-app. 
/ e.g. All the readers, media players, downloads, games (at least the ones on Fdroid), calculators, dns/proxy (in-browser), news, messengers etc. The community can do a OpenSource webview container, that can be used as dock to these web-apps. We get this webview container verified by Google & then use it as host to all web-apps. One can do a web-to-native API framework, so webapps can communicate to PackageManager (+ other services) & then Utility apps can also be a web-app.
