-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
UnifiedNLP not working on Oneplus 7T Pro with LineageOS 17.1 #1420
Comments
https://github.com/microg/GmsCore/wiki/Installation
|
Thanks, now I seem to get a location, but it's from time to time. In other words, I can't use navigation, it shows me in one place, than maybe after a minute in the new place. Is this supposed to happen? |
This might be related to microg/UnifiedNlp#211, but yeah, that would be an issue. I don't really use location stuff so I can't really confirm anything, but I guess we'd have to wait for it to be noticed and acknowledged. |
@mar-v-in Last time I found this thread and sent to ROM maintainer. Few day ago, I saw LineageOS committed this thing: Yesterday I update the LineageOS included above enhancement. After disable the xposed module "XposedGsmCoreUnifiedNlp", I still not able to get the Network Based Location. Is it really need a set the "config_enableNetworkLocationOverlay", "config_enableFusedLocationOverlay" in-order to solve this problem? |
Sorry, I am not a very technical person and I am not really understanding. |
The LineageOS commit only adds UnifiedNLP to the whitelist of allowed location providers. The linked comment explains that if This means that yes, in your case, at least |
Thank you so much, I will talk to ROM maintainer again. |
Yes, I recommend that. They may have declined last time, but now that their change actively prevents a LineageOS feature from working, hopefully they'll reconsider. |
@codepayne wrote:
I'm seeing similar network location timing issues on a lineage-17.1 + latest micro-G config. I've run several tests and the amount of time between updates (and the amount of time when only a "stale" location is available) seems to depend on which Nlp providers are used:
If you have no objection against using the Apple Wifi webAPIs (and thus sending some data to Apple) then using the Apple Wifi NLP provider from F-Droid is a good workaround for the timings issues. At least this seems to work well for me. |
A quick update on this, I just retried this on a fresh install and for the apple backend to work properly I also need to disable the "throttle wifi scanning" option under developer options and then disable + re-enable the apple wifi backend in the microg location settings. Without this the apple backend was behaving quite similar to the mozilla NLP (IchnaeaNlpBackend) version 1.3.3 case, where Networklocation works with 5 seconds ok + 10 seconds stale data. Unfortunately disabling "throttle wifi scanning" does not help for the 1.3.3 mozilla NLP backend. |
I'm closing it since it isn't a microG issue:
If you want an easier way to setup everything you can use my microG unofficial installer |
Describe the bug
I have some problems with location services. All the other microg features work, but not location.
I can get geo coordinates(in SatStat) but any application that uses maps doesn't work, complains that location service doesn't work.
I installed the 4 microg apps through the microg f-droid repo. I have the f-droid privileged extension installed in magisk.
What seems different to other people is that I don't have a unifiedNLP status menu entry in the self-check page of microg. So this would indicate that I didn't install something correctly.
To Reproduce
Steps to reproduce the behavior:
Open any maps app
Expected behavior
Phone location is shown on the map
Screenshots
System
Custom ROM: LineageOS 17.1 + manually applied patch for signature spoofing
Additional context
The text was updated successfully, but these errors were encountered: