https://source.android.com/compatibility/8.0/android-8.0-cdd … is the whole thing in HTML, FWIW. Lots of other restrictions forbidding the kind of changes that we make to Android.
-
-
-
It's a blessing and a curse for us: we can't have the option of a CopperheadOS device with Play Services, few of our features are allowed.
-
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.
- 9 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.