* microG fails to register applications to GCM/FCM (Cloud Messaging) if they were installed **before** microG, but the apps keep trying to register and that causes the battery drain, all apps installed **after** microG are properly registered, to fix the battery drain issue the following command as root on your device (or via adb shell):
* if you use AppOps, PrivacyGuard or the like you have to grant microG GmsCore **all** permissions, if you prevent some permissions, some apps or features might not work as expected or not at all. Note: some APIs/features are stubs in microG GmsCore, meaning they exist that apps don't complain, but they do nothing - thus blocking microG GmsCore is pretty much of no benefit.
* You can't get past the first page of the microG login wizard on KitKat
* updating microG to (at least) 0.2.7.17455 will fix the issue
## Updating Play support libraries
* Play Store tries to update itself or the Play Services, both updates fail because you have microG and a modified Play Store installed
* you can disable the `GMSCoreUpdateService` service of the Play Store to prevent it from updating
## Google Account
* Can't login to Google Account
* there's an issue where logging in with version 74.x of Chrome/Chromium/Bromite or WebView derived from them fails
* the fix is to update microG to (at least) version 0.2.7.17455
## Google Play Services are missing
* This misleading error message actually means 'Something is wrong with Play Store'
* ensure as mentioned above you properly [setup microG](#microg-setup) and reboot
* install either Fake Store or Play Store
* grant signature spoofing permission to Fake Store or Play Store
* go to System Settings > Apps > Permissions > Signature Spoofing for that
* on some ROMs you have to tap on the 3-dot-menu `Show System Apps` to see Fake Store
* or manually using `pm grant com.google.gms android.permission.FAKE_PACKAGE_SIGNATURE` as root on-device
* likewise `pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE` for Phonesky
## SafetyNet
**Note:** microG's Droid Guard Helper is currently _not_ able to perform SafetyNet Attestation.
* SafetyNet check complain with `Google Play Services are missing`
* see [Google Play Services are missing](#google-play-services-are-missing) above
* SafetyNet check fails after upgrading Magisk to version 18.0
* go to Magisk Manager > Magisk Hide and activate it for `microG DroidGuard Helper`
* Applications crash during SafetyNet check
* install microG DroidGuard Helper as user-app (required on some ROMs), as root, on-device, issue:
* Play Store not installing split APKs / extra data
* several huge applications (mostly games) have a rather small base APK and additional addon-data downloaded, if Play Store fails to install those
* go to Settings > Apps > Play Store > Permissions and grant at least the `Phone` and `Storage` permission
* force close Play Store and open it again
* Play Store does not show bought apps as bought
* this is a rare corner-case that sometimes happens on Android 10 (onwards), it's ususally fixed by issueing the following command as root on your device (or via adb shell):
* when using Titanium Backup or OAndBackupX first install the app only (without data) and start it, this will register the app, afterwards restore it's data
* when restoring the ROM from a TWRP backup GCM registration for apps is sometimes broken. You may use the following command to reset GCM/FCM connection(s). App(s) will re-register when launched afterwards:
*`nutl -r APPID` (eg.: APPID = `com.nianticlabs.pokemongo`) or `nutl -r` (for all applications)
* if you can't make any app registering for Google Cloud Messaging, try the following
* open the Phone app and dial the following: `*#*#2432546#*#*` (or ` *#*#CHECKIN#*#*`)
## Unified Nlp
**Note:** unified Nlp has known issues on Android 10.
* unified Nlp is not registered in the system
* some ROMs with native signature spoofing don't look for `com.google.android.gms` as location provider
* tell the developer (or maintainer) of the ROM to fix this
* some versions of `com.qualcomm.location` conflict with uNlp, if it's installed and unified Nlp doesn't work, try the following command to get rid of it, as root, on-device:
*`novl -a com.qualcomm.location`
* unified Nlp is registered in the system, but fails to get location
* issue the following commands as root, on-device:
*`pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION`
*`pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION`
* some versions of `com.qualcomm.location` conflict with uNlp, if it's installed and unified Nlp doesn't work, try the following command to get rid of it, as root, on-device:
*`novl -a com.qualcomm.location`
* Ichnaea (Mozilla) location backend doesn't provide location
* if you use Blockada, add the location backend to the whitelist
* for any other ad-blocker, whitelist the following domain:
*`https://location.services.mozilla.com`
## F-Droid
* On some ROMs (most noticeably MIUI ROMs) F-Droid can't install applications
* this is because F-Droid's Priviledged Extension is not compatible with those ROMs, disable it from
* Some Stock ROMs do not properly work after first boot since their SetupWizard is disabled by NanoDroid (because it's incompatible with microG)
* check `/system/build.prop` or `/vendor/build.prop` if they contain the property `ro.setupwizard.mode` and change it to (you can do this from TWRP via ADB, with the builtin `vi` editor)
*`ro.setupwizard.mode=DISABLED`
* in Magisk Mode NanoDroid will do this on it's own using Magisk's `resetprop`
* if you can access your device via ADB, you can also issue the following command as root, on-device:
*`nanodroid-util --fix-update`
* Applications crash when using WebView (BromiteWebView package)
* install Bromite WebView as user-app, as root, on-device, issue:
