Limitations of microG on Huawei Devices (Contacts Sync, Google One Backup, YouTube Cast) #3270
Description
Hello microG team,
First of all, thank you for maintaining microG. This project is extremely valuable for users who want to reduce dependency on Google services while keeping Android app compatibility.
I would like to share real-world feedback based on daily usage of microG on Huawei devices without Google Mobile Services (GMS). The points below are not bug reports but structural limitations caused by Google’s closed ecosystem. My goal is to document these issues clearly and suggest realistic, open-source–friendly directions.
- Google Account Synchronization (Contacts, Calendar, Drive)
microG does not include proprietary components such as the full Google Account Manager, Google Contacts Sync Adapter, or Google Drive background sync services.
As a result:
Google Contacts are not synchronized at all
Contacts stored in a Google account never appear on the device
Calendar and Drive synchronization is unavailable or application-dependent
This is not a configuration issue or partial malfunction. It is a structural limitation caused by Google restricting account and synchronization services to certified devices.
Suggested direction:
Promote open standards such as CardDAV / CalDAV as first-class alternatives (e.g. DAVx⁵)
Make the lack of Google Contacts sync more explicit to users to avoid confusion - Google One Device Backup
Google One device backup depends on proprietary system-level infrastructure, including Google Backup Transport, Google Cloud Backup Service, and device certification mechanisms.
On Huawei devices using microG:
Google One may appear enabled
Backup settings may look active
No actual device or app data backup is created
Restore functionality does not work
Because there is no clear warning, this can create a false sense of security, where users believe their data is backed up while it is not.
Suggested direction:
Recommend open-source system backup solutions such as Seedvault
Provide clear user-facing warnings when Google One device backup is unsupported - YouTube to TV Direct Casting (Auto Discovery)
YouTube’s direct casting feature relies on Google Cast and proprietary discovery services integrated into licensed Google Play Services components.
On Huawei devices using microG:
TVs are not automatically discovered
Direct “Cast” does not work
Users must rely on TV code pairing
The TV code method permanently associates each television with the user’s Google account, which negatively impacts usability and privacy—especially in shared or public environments.
Suggested direction:
Explore temporary, account-less device discovery mechanisms
Investigate support for open or non-Google-based discovery protocols where possible - Root Cause Clarification
These limitations are not caused by technical shortcomings of microG. They are the direct result of:
Google’s closed and licensed service architecture
Proprietary account, backup, and casting frameworks
Device certification restrictions
microG intentionally avoids proprietary dependencies, which is both a strength and an unavoidable constraint. - Recommended Open-Source Tools for Huawei + microG Users
To mitigate these limitations, the following tools are currently the most practical options:
DAVx⁵ – CardDAV / CalDAV contacts and calendar synchronization
Seedvault – Open-source Android backup solution
Mozilla Location Service (MLS) – Network-based location provider
F-Droid – Open-source app repository
Aurora Store – Anonymous Google Play Store client
NewPipe / PipePipe – YouTube frontends without Google services
Conclusion
Using microG on Huawei devices is a conscious trade-off between openness, privacy, and full compatibility with Google’s proprietary ecosystem. Clear documentation of these limitations and stronger promotion of open standards would help users make informed decisions and strengthen trust in the microG ecosystem.
Thank you for your time and for your work on this important project.