-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Impossible to register UnifiedNIp in system #940
Comments
Same here with AEX. Solved by installation mozilla nlp from f-droid, but i think it's hack, not soluton |
Unfortunately, in my case, MozillaNIpBackend is already installed and UnifiedNIp is still not recognize in system. |
Same issue here. I get "0 backends configured" and clicking "Configure location backends" gives an empty list but I have MozillaNlpBackend and GSM Location installed. Moving their |
On some older ROMs (pre-Pie) you may have to get rid of the included location provider first, for example |
On devices/systems using file based encryption (FBE), which include all devices running Android 10 and many devices that originally shipped with Android 7 or higher, microG/UnifiedNlp currently must be installed on /system (either app or priv-app) so that it can register to the system. UnifiedNlp backends don't need to be installed to /system, though it certainly wouldn't hurt. Some ROMs do not have support for proper network location providers on some devices. That's an upstream issue, caused by the device code setting |
I finally solved my issue by installing the Magisk Microg Installer. Now it works fine. |
Hello everyone,
I am not able to use UnifiedNIp for localisation.
All looks good in microG self-check panel before UnifiedNIp registering.
Additionaly I installed and activated
I restarted the system many times.
Technicals details
Potential probelmatic additional packages
Does anyone have an idea?
If you need any additonal information, please just ask.
Thank you all!
Sorry for the doublon with #925. My previous post was hidden by GitHub.
The text was updated successfully, but these errors were encountered: