This is a requirement of the Android "Compatibility Definition" (needed to license Play).https://twitter.com/CopperheadOS/status/905972357570887681 …
Could you just do your own implementation of Play Services? (like microg but I know you don't like microg :-)
-
-
Yes, we could make our own implementation. Our update client is something usually provided by Play and we're going to focus on backup next.
-
Supplementary location services (local cellid db), geocoding, better text-to-speech than AOSP svox, voice to text, etc. are on the table.
-
Those are all done via AOSP APIs where Play Services provides a backend, so there's no ugliness involved in providing alternatives for them.
-
microG is focused on the APIs Play Services exposes directly to apps, which requires tricking their signature checks, which we could do.
-
Except we would do the signature check bypass in a very constrained way and we would want stub APIs for anything requiring a Google service.
-
Yes, I agree the signature check bypass should be hard-coded in the core OS and limited to it, not the way microg wants it done.
-
It should be limited to only faking the Play Services signature, and only for the system app providing the Play Services stubs.
-
No generic permission, and that app shouldn't end up being allowed to fake any signature checks, only the Play Services signature check.
- 6 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.