|
- Backend Implementations | microg GmsCore | DeepWiki
HMS (Huawei Mobile Services): Uses Huawei's map SDK for devices with HMS support Mapbox: Uses the Mapbox SDK as an open alternative map provider Both backends implement the same Google Maps API interfaces, making them interchangeable from the client application's perspective The backend is selected at build time via Gradle product flavors
- Signature Spoofing and Self-Check | microg GmsCore | DeepWiki
The Huawei product flavor demonstrates how to pre-configure microG services ROM builders can include metadata in the manifest to enable services without user intervention:
- Build System and Module Structure | microg GmsCore | DeepWiki
This flexible build configuration enables microG to serve multiple use cases: standard devices, Huawei devices without Google services, privacy-focused distributions, and custom ROM integration
- microg GmsCore | DeepWiki
VTM (Vector Tile Map) implementation HMS (Huawei Map Services) implementation Sources: play-services-core build gradle 164-196 build gradle 74-104 Version Naming and Compatibility microG follows Google Play Services version numbers for compatibility, with additional versioning information: Base version (e g , "25 09 32") aligns with Google's
- Configuration and Settings | microg GmsCore | DeepWiki
This Huawei variant enables multiple services by default, allowing the build to work out-of-the-box without user configuration System Configuration File ROM builders can provide system-wide defaults in system etc microg xml (SettingsProvider kt 51-61) This file is read using reflection: Context::class java getDeclaredMethod
- Licensing Verification | microg GmsCore | DeepWiki
The Huawei flavor enables licensing by default because Huawei devices ship with microG preinstalled, and users expect license verification to work out-of-the-box
- Settings Contract | microg GmsCore | DeepWiki
Huawei-specific defaults The Huawei flavor of microG demonstrates how defaults can be customized for specific device variants through manifest meta-data entries:
- SafetyNet Attestation | microg GmsCore | DeepWiki
Force Local Disabled: Forces disabling of local DroidGuard execution Setting key: droidguard_force_local_disabled Default: false Setting key: droidguard_force_local_disabled Default: false In the Huawei build variant, both SafetyNet and DroidGuard are enabled by default through metadata in the AndroidManifest: Sources:
|
|
|