UnifiedNlp icon indicating copy to clipboard operation
UnifiedNlp copied to clipboard

No data in "UnifuedNlp has known location:"

Open rerbin opened this issue 8 years ago • 6 comments

screenshot_20160309-125132

rerbin avatar Mar 09 '16 04:03 rerbin

I see the same here, also when checking with the Xposed module I get an error (UnifiedNLP (GApps) on a Wilefox Swift running CyanogenOS 12.1 / Android 5.1.1). Logcat reports "Ignoring location update as it's older than other provider". I ask myself: What other provider should that be? Google Location should be disabled by the XPosed module.

More from Logcat:

Selfcheck:

V/NlpLocationProvider(19516): onSetRequest: ProviderRequest[ON interval=+10m0s0ms] by WorkSource{10120 org.microg.nlp}
V/NlpLocationProvider(19516): using autoUpdate=true autoTime=600000
V/NlpLocationBackendFuser(19516): Ignoring location update as it's older than other provider.

Check from XposedUnifiedNLP:

I/CheckStep(24919): UnifiedNlp packages state changed to RUNNING
I/CheckStep(24919): UnifiedNlp packages state changed to SUCCESS
I/CheckStep(24919): Network-based geolocations state changed to RUNNING
D/CheckWorkingTask(24919): UnifiedNlp package: SUCCESS
I/CheckStep(24919): Network-based geolocations state changed to SUCCESS
I/CheckStep(24919): UnifiedNlp locations state changed to RUNNING
D/CheckWorkingTask(24919): Network-based geolocation: SUCCESS
V/NlpLocationProvider(19516): onSetRequest: ProviderRequest[ON interval=0] by WorkSource{10123 de.r3w6.xposedunifiednlp}
V/NlpLocationProvider(19516): using autoUpdate=true autoTime=2500
V/NlpLocationBackendFuser(19516): Ignoring location update as it's older than other provider.
V/NlpLocationBackendFuser(19516): Ignoring location update as it's older than other provider.
V/NlpLocationBackendFuser(19516): Ignoring location update as it's older than other provider.
V/NlpLocationBackendFuser(19516): Ignoring location update as it's older than other provider.
V/NlpLocationBackendFuser(19516): Ignoring location update as it's older than other provider.
V/NlpLocationProvider(19516): onSetRequest: ProviderRequest[ON interval=+10m0s0ms] by WorkSource{10120 org.microg.nlp}
V/NlpLocationProvider(19516): using autoUpdate=true autoTime=600000
I/CheckStep(24919): UnifiedNlp locations state changed to FAIL
V/NlpLocationBackendFuser(19516): Ignoring location update as it's older than other provider.
D/CheckWorkingTask(24919): UnifiedNlp location: FAIL

PS: I can confirm #88 – apps receive a location nevertheless. So I'm curious where that location comes from (I hope not from Google).

IzzySoft avatar May 19 '16 19:05 IzzySoft

@IzzySoft What backend(s) are you using?

mar-v-in avatar May 23 '16 20:05 mar-v-in

I can get that Ignoring location update as it's older than other provider. message from either my GSM backend or from the Mozilla backend (more frequent on the Mozilla if I disable the WiFi on it). SatStat will show a greyed out position and uncertainty when this happens rather than its typical blue point and circle used for displaying network location.

It occurs when UnifiedNLP attempts to make an update() call to the backend and either the backend does not implement it (Mozilla backend) or returns the most recent location with the time it was first calculated (my GMS backend). In both of those backends the position calculation is driven off a change reported by (for GMS) the TelephonyManager.

That message does not occur on my local WiFi backend as it triggers a scan and calculates the location on each update() invocation.

FWIW, in the last day I've altered my GSM backend to avoid that issue.

n76 avatar May 23 '16 21:05 n76

@mar-v-in LocalGSM (looks like @n76 just confirmed that).

@n76 can you confirm my last question on the other issue (that updating from e.g. v1.0.1 to the latest version keeps the database directory originally configured)? Then I'd apply the pending update (1.4.2 is shown from F-Droid) and report back if your alteration fixes it for me.

IzzySoft avatar May 23 '16 21:05 IzzySoft

If you first update to v1.3.3 it should automatically move the existing database from the /sdcard/.nogapps/ directory then you can update to the latest.

Or you can just upgrade to v1.4.3 (not yet on F-Droid) and then use a file manager or adb shell to move the lacells.db file:

adb shell
su
mv /sdcard/.nogapps/lacells.db /sdcard/Android/data/org.fitchfamily.android.gsmlocation/files/lacells.db.new

Edit: It looks like the logic to check for database files at /sdcard/.nogapps is still in the code and the backend should look for them and move them when it is started. So for your scripted application, you could continue to put files in that location and then force stop the backend. When UnifiedNlp restarts it, you should have you most recent database file.

Edit 2: This discussion is not relevant to this issue, you should open an issue on my backend and we can discuss how to suit your needs there.

n76 avatar May 23 '16 21:05 n76

@n76 this one, open since January? :) OK, let's continue there :+1:

IzzySoft avatar May 23 '16 22:05 IzzySoft