Last active
April 28, 2021 08:37
-
-
Save akc3n/62d629c6abf222ab3a2c6eafa6a3b8b8 to your computer and use it in GitHub Desktop.
AOSP and incorrect assumptions on CalyxOS and microG being 'degoogled'
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AOSP doesn't have proprietary Google apps and services. | |
CalyxOS does have proprietary Google apps and services bundled and not only via microG. | |
CalyxOS takes AOSP, and adds Google services to it (microG) along with not replacing Google | |
as the provider for non-proprietary services. | |
microG is a very small subset of Google play services. | |
What microG does is reimplementing a small subset of Play services in a hacky and incomplete | |
way, with less security, because they don't implement features like certificate pinning for | |
services and apps (TLS and local components), as well security checks. | |
The apps that work can stop working at any time, if they start using more of the APIs, | |
or microG's implementation stops working with Google's servers. | |
microG doesn't offer an alternative push service but rather has an incomplete implementation | |
of Google's push service. The Firebase Cloud Messaging push does not work reliably. | |
Note apps can use FCM when available and still have working push without it. | |
Taking AOSP, which never had Google's services, then adding the same Google's services to it | |
in a different way doesn't make something 'degoogled'. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment