Discussion
Schon echt übel. Ich habe ein offenes Betriebssystem gewählt, in dem auch selbstgeschriebene Apps laufen – und Google will den Hahn zudrehen und die komplette Macht übernehmen.
Bitte, macht euch selbst schlau!:
https://keepandroidopen.org/de/
Ob die Petition was bringt, werden wir sehen. Bis dahin braucht's auf jeden Fall viel mehr Unterzeichnende:
https://www.change.org/p/keep-android-open-stop-google-from-limiting-apk-file-usage
@Hans @realSiegfried @keepandroidopen No, it doesn't impact GrapheneOS. It's a warning implemented by operating systems building in Google Mobile Services with the standard deep privileged access. Users on those operating systems will need to toggle on installing apps from unverified developers to install those which requires a 24 hour initial wait. It can be bypassed immediately using ADB. It forces developers to do identity verification to avoid the warning. Play Integrity API is much worse.
@Hans @realSiegfried @keepandroidopen Play Integrity API is normally integrated as blocking people using apps/services if they aren't on a Google certified device with the unmodified stock OS. That's a whole lot worse. It isn't simply a warning but rather blocks people using those. It's being heavily promoted to app developers and very few people are pushing back against it.
There's no option to avoid the Play Integrity API blocking by doing verification. Certification isn't an open system.
@GrapheneOS @realSiegfried @keepandroidopen
Also: GrapheneOs-Geräte sind weiterhin vollständig nutzbar.
So interpretiere ich die Antwort. Danke.
@realSiegfried @keepandroidopen
@GrapheneOS
Frage:
Betrifft das auch Goggle-Pixel 7a mit GrapheneOs?