mirror of https://gitlab.com/Nanolx/NanoDroid
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
150 lines
8.5 KiB
Markdown
150 lines
8.5 KiB
Markdown
4 years ago
|
Table of Contents
|
||
|
=================
|
||
|
|
||
|
* [Issues](#issues)
|
||
|
* [microG](#microg)
|
||
|
* [Updating Play support libraries](#updating-play-support-libraries)
|
||
|
* [Google Account](#google-account)
|
||
|
* [Google Play Services are missing](#google-play-services-are-missing)
|
||
|
* [SafetyNet](#safetynet)
|
||
|
* [Play Store](#play-store)
|
||
|
* [Push Messages](#push-messages)
|
||
|
* [Unified Nlp](#unified-nlp)
|
||
|
* [F-Droid](#f-droid)
|
||
|
* [Alarm Clock not ringing](#alarm-clock-not-ringing)
|
||
|
* [Google Software](#google-software)
|
||
|
* [Other](#other)
|
||
|
|
||
|
Created by [gh-md-toc](https://github.com/ekalinin/github-markdown-toc)
|
||
|
|
||
|
# Issues
|
||
|
|
||
|
## microG
|
||
|
|
||
|
* Battery Drain
|
||
|
* microG fails to register applications to GCM (Google 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 either
|
||
|
* do a clean flash of your ROM (, Magisk) and NanoDroid and install your apps after microG setup
|
||
|
* uninstall and re-install all your applications (backup application data if required)
|
||
|
* microG lacks features
|
||
|
* 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:
|
||
|
* `pm install -r /system/app/DroidGuard/DroidGuard.apk`
|
||
|
* this is done automatically in Magisk Mode (as of version 20.5)
|
||
|
|
||
|
## Play Store
|
||
|
|
||
|
* Play Store giving error RH-01
|
||
|
* ensure you rebooted after [microG setup](#microg-setup)
|
||
|
* ensure Play Store has signature spoofing permission
|
||
|
* go to Settings > Apps > Permissions > Signature Spoofing and grant it
|
||
|
* force close Play Store and open it again
|
||
|
* go to Settings > Apps > Play Store > Permissions and grant at least the `Phone` permission
|
||
|
|
||
|
## Push Messages
|
||
|
|
||
|
* Apps are not receiving Push messages
|
||
|
* go to microG Settings / Google Cloud Messaging and check if it is connected
|
||
|
* ensure you don't have an adblocker blocking the domain `mtalk.google.com` it is required for GCM to work
|
||
|
* when using Titanium Backup first install the app only (without data) and start it, this will register the app, after that you can restore the data using Titanium Backup
|
||
|
* if an app is not shown as registered in microG Settings / Google Cloud Messaging, try uninstalling and re-installing it
|
||
|
* when restoring the ROM from a TWRP backup GCM registration for apps is sometimes broken. You may use the following command to reset GMS settings for a given app using it's appname, or if no appname is given for all applications. Apps will re-register when launched afterwards:
|
||
|
* `nutl -r APPNAME` (eg.: APPNAME = `com.nianticlabs.pokemongo`) or `nutl -r`
|
||
|
* 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
|
||
|
* F-Droid > Settings > Expert Settings > Privileged Extension
|
||
|
|
||
|
## Alarm Clock not ringing
|
||
|
|
||
|
* Due to changes in Android, to ensure your Alarm Clock is actually waking you up, you need Android to ignore battery optimization for it, to do so:
|
||
|
* go to System Settings > Apps > Special Access > Battery Optimization > All Apps
|
||
|
* tap on your Alarm Clock, for example `Alarmio` and choose `don't optimize`
|
||
|
|
||
|
## Google Software
|
||
|
|
||
|
* Maps doesn't work when installed a second time
|
||
|
* remove your Google Account and re-add it, that'll make Maps work again
|
||
|
* remove traces from previous insallations, like
|
||
|
* /sdcard/Android/data/com.google.android.apps.maps
|
||
|
* /data/system/graphicsstats/1559520000000/com.google.android.apps.maps
|
||
|
* where `1559520000000` is the Maps version, so may differ
|
||
|
|
||
|
* Hangouts isn't properly working
|
||
|
* as root, on-device, run the following command:
|
||
|
* `pm disable com.google.android.talk/com.google.android.apps.hangouts.service.NetworkConnectionCheckingService`
|
||
|
|
||
|
## Other
|
||
|
|
||
|
* 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:
|
||
|
* `pm install -r /system/app/BromiteWebView/BromiteWebView.apk`
|
||
|
* this is done automatically in Magisk Mode (as of version 20.5)
|
||
|
* ROM lags after applying signature spoofing patch
|
||
|
* some ROMs already have the patch built-in, if you patch those ROMs (again), it results in heavy lags
|
||
|
|
||
|
Additional helpful information in the microG [> Wiki](https://github.com/microg/android_packages_apps_GmsCore/wiki/Helpful-Information).
|