Free implementation of Play Services
Full Changelog: https://github.com/microg/GmsCore/compare/v0.3.0.233515...v0.3.1.240913
<package-name>-<version-code>.apk (e.g. com.google.android.gms-233515000.apk or com.android.vending-83752400.apk).-hw and -lh test builds. Those are currently not meant for use except if explicitly instructed.Full Changelog: https://github.com/microg/GmsCore/compare/v0.2.29.233013...v0.3.0.233515
microG now supports signing into apps and games that use Google as one or their only sign-in options. This features is still experimental and doesn't work for all apps.
microG now supports the SMS retriever API. Apps can use the SMS retriever API to automatically fill confirmation codes received by SMS contains an app specific token or the user confirms that the app shall be allowed to read the SMS content. This API does not requires the app to have access to your SMS (but microG needs such access).
microG now allows to configure various settings, privacy options and manage account links of your Google account. You can open the settings from system settings or directly from various Google Apps.
microG now fully supports opening short dynamic links created for sharing in various apps or statically by the app developer. These links typically end in .page.link or .app.goo.gl. microG will open the corresponding app if installed or fallback to either the corresponding web site (if available) or the app page in the installed app store.
play-services-basement
shorts (#2019). Thanks @chirayudesaiCREATOR at compile-time (rather than using reflection)withVtm has been renamed to vtm, withMapbox was renamed to mapbox. To disable the nearby module one has to set modules.nearby=false via local.properties.android.permission.RECEIVE_SMS permission to access SMS for implementing the SMS retriever API.Full Changelog: https://github.com/microg/GmsCore/compare/v0.2.28.231657...v0.2.29.233013
android.permission.LOCATION_HARDWARE
android.permission.MODIFY_PHONE_STATE
android.permission.NETWORK_SCAN
android.permission.UPDATE_DEVICE_STATS
android.permission.WATCH_APPOPS
Full Changelog: https://github.com/microg/GmsCore/compare/v0.2.27.223616...v0.2.28.231657
-api modules are merged in the corresponding library module.-core-ui packages are merged into the corresponding -core module.safe-parcel library is now bundled into play-services-basement.Full Changelog: https://github.com/microg/GmsCore/compare/v0.2.26.223616...v0.2.27.223616
This maintenance release fixes
Full Changelog: https://github.com/microg/GmsCore/compare/v0.2.25.223616...v0.2.26.223616
nearby-core. Thanks @fynngodaunearby-core to allow using the neverForLocation assertion in apps using it (#1796)play-services-fido, play-services-oss-licenses and play-services-safetynet client libraryThe newly added Fido API allows using U2F and Fido devices via USB or NFC with supported Browsers (Chromium and Firefox) and to sign into your Google Account in microG. Additionally, on supported hardware and when a PIN/password is configured, the secure key storage can be used as a virtual Fido device. Note that some devices are still not fully supported.
Due to lack of open-source client library, open-source variants of browsers (Bromite, Fennec, etc) currently do not support this API. This release also provides an open-source play-services-fido library, which open-source browsers can use instead of the proprietary Google version to add support for microG's Fido API.
Full Changelog: https://github.com/microg/GmsCore/compare/v0.2.24.214816...v0.2.25.223616
This is a maintenance release to fix a few issues slipped into the last release.
Exposure Notifications:
Device profiles:
Location:
The updated SafetyNet implementation runs proprietary DroidGuard code privileged in the com.google.android.gms package name. This is required on at least some devices to pass SafetyNet. However this features is disabled by default. If you don't want to run proprietary code by Google on your device do not enabled SafetyNet.
As of now, microG SafetyNet implementation, once enabled, should work on all devices and ROMs that would pass SafetyNet attestation with original Google Play Services. This means that ROMs that are rooted (= come with a su binary that allow privilege escalation), with unlocked bootloader, or for some other reason do not pass the CTS or trigger the SafetyNet system will fail SafetyNet attestation. Hiding or spoofing such details from DroidGuard/SafetyNet is out of scope for this project, but techniques to allow passing SafetyNet on custom ROMs should equally work with microG.
This features is mostly useful for Huawei devices or other devices that are banned from accessing Google services. Choosing a profile of a non-banned device should allow using the device with Google services.
For now, two device profiles are included with microG (Nexus 5X with Android 8.1.0 and Moto G with LineageOS 14.1).
If you are a developer, you can easily create a device profiles based on data gathered from a device. See this file for a sample device profile. Once created, you can import device profiles in microG settings (under "Device registration") to test the profile.
If you are a custom ROM developer, you can add a custom device profile for your ROM by placing an appropriate device profile in /system/etc/microg_device_profile.xml. This can be useful to spoof the details of the original vendor ROM.
Maintenance release with a few bug fixes.