Doesn't work well ?

[jeremy447]

Hello,

I don't know if it's UnifiedNlp or the backend (IchnaeaNlpBackend) that doesn't work well but often my map apps can't find my location. I use maps.me and osmand. Here are the problems I have :

• Sometimes the location is never found
• Sometimes the location is totally wrong (100+ km)
• Sometimes the location is quite imprecise (200+ km radius)
• Sometimes the location is wrong and correspond to the location where the last time I used the map apps

Here is a log that show that osmand find me, then lost the location, and find me again. I will provide more logs if needed when problems appears.

2016-12-13-07-25-14.txt

Thanks !

[jeremy447]

Here is some more logs

• maps.me show my previous location
  2016-12-14-12-41-51.txt
• osmand can't find the location
  2016-12-14-12-43-06.txt

[jeremy447]

By the way I'm on CM11 (Razr i) with UnifiedNlp 1.6.7 from Fdroid

[jeremy447]

It seem that UnifiedNlp 1.6.6 works much better. I will make more tests.

[jeremy447]

Ok v1.6.6 worked well this morning but failed this afternoon.

• osmand and maps.me found me in the middle of water 7 kms away from my real location
  2016-12-15-12-34-54.txt
  2016-12-15-12-36-44.txt

[n76]

FWIW, the backend(s) are the real provider of location. UnifiedNLP pulls together the location estimates for all installed and enabled backends and then gives you the one with the smallest estimated error.

So this bug should be placed against the IchnaeaNlpBackend backend instead of UnifiedNLP.

And there are other backends that you can install and use which might give better results for you.

Also, several of the backends use open source mobile/cell tower location estimates. You can improve the accuracy of most of the backends by contributing to projects like Open Cell ID or Mozilla Location Services.

[jeremy447]

The last time it was UnifiedNLP that wasn't working #80

I live in Bordeaux, France and there is plenty of wifi and 2G, 3G around. The thing is that at a given location sometimes that work, sometimes not.

[jeremy447]

Is there something I can do to found if the problem is in UnifiedNLP ?
It happen too with OpenBmapNlpBackend.

[n76]

Use an app like SatStat that shows both the GPS location and the "network" location. Then try different backends. You may find that different backends perform differently.

FWIW, I've played with all the backends and they do return different results. And when writing my own backends I've never noticed UnifiedNLP corrupting the data my backends created: If there was a position problem it was with the backend not UnifiedNLP.

[jeremy447]

By the way I meant that doesn't work well with GPS disabled (disabled or in buildings). With GPS the location is found quickly. When GPS is not available UnifiedNLP should locate me, not accurately but I think in a range of 100m to 1km based on wifi and gsm, and that often not the case. As I said in the first post and I repeat without GPS:

• Sometimes the location is never found
• Sometimes the location is totally wrong (100+ km) (only OpenBmapNlpBackend)
• Sometimes the location is quite imprecise (200+ km radius)
• Sometimes the location is wrong, not updated, and correspond to the location where the last time I used the map apps

Here is the backend I tried:

• IchnaeaNlpBackend: work very well sometimes, but don't update the location sometimes. Rarely quite imprecise (200+ km radius)
• OpenBmapNlpBackend: imprecise and not reliable for me (found me in Paris ~500km away with wifi)
• LocalGsmNlpBackend: not very precise (10km radius) so I don't know if it update the location correctly

[jeremy447]

As I said there microg/IchnaeaNlpBackend#27

Well I don't know if it's the problem lies in the backend or in UnifiedNlp because it kind of happened too with LocalGsmNlpBackend when I was in Andernos, France yesterday. I tried 3 or 4 times to see if I was correctly located and that was not the case until maybe the 5th time. There was plenty of GSM antennas available and I didn't move at all when I was located.

Here is a log when that didn't worked with LocalGsmNlpBackend
2016-12-24-17-50-00.txt

[n76]

@Paviluf I'd expect to see at least a log message from NlpLocationBackendFuser that will show what backend(s) were called and what the various backend(s) returned. I don't see that in your log so it is not possible to say what is happening.

Perhaps another log file captured using something like:

adb logcat | grep NlpLocationBackendFuser

would help.

[jeremy447]

For me it look like that NlpLocationBackendFuser doesn't show up because UnifiedNlp or LocalGsmNlpBackend kind of hanged or crashed.

[n76]

Maybe. While I haven't seen LocalGsmNlpBackend crash on a version I've released, I would not rule it out. But I've never seen UnifiedNlp crash so that would surprise me a lot.

[jeremy447]

I don't know if it can be related but my phone is a x86 (Motorola Razr i).

[n76]

LocalGsmNlpBackend or Local-GSM-Backend?

I can't help much on LocalGsmNlpBackend which looks like it was last updated three years ago and probably does not have current mobile/cell tower information. The Local-GSM-Backend is the one I support and allows you to download current data from a couple of different sources.

[jeremy447]

I use the more recent one Local-GSM-Backend with the data for France.

[n76]

And what is the output from the logcat command I suggested earlier. I would expect something like

12-25 13:24:51.405 1568 2030 V NlpLocationBackendFuser: location=Location[network 33.000000,-117.000000 acc=19 et=+1h2m21s719ms {Bundle[{noGPSLocation=Location[network 33.000000,-117.000000 acc=19 et=+1h2m21s719ms], AVERAGED_OF=7, SERVICE_BACKEND_PROVIDER=wifi, SERVICE_BACKEND_COMPONENT=org.fitchfamily.android.wifi_backend/.backend.BackendService_}]}]

(I've munged the lat/lon for privacy. I don't have a SIM card in the phone I've got microG installed on so I don't get any mobile/cell towers but NlpLocationBackendFuser should still show something just different than what mine is showing).

[jeremy447]

Here is the output of adb logcat | grep NlpLocationBackendFuser

V/NlpLocationBackendFuser( 3942): location=Location[network 44,865632,-0,592449 acc=1655 et=+1d16h36m4s518ms {Bundle[{noGPSLocation=Location[network 44,865632,-0,592449 acc=1655 et=+1d16h36m4s518ms], AVERAGED_OF=8, SERVICE_BACKEND_PROVIDER=gsm, SERVICE_BACKEND_COMPONENT=org.fitchfamily.android.gsmlocation/.GsmService_}]}]

[jeremy447]

It seem the problem is in IchnaeaNlpBackend. microg/IchnaeaNlpBackend#27 (comment)

[jeremy447]

If I use LocalGsmNlpBackend for 2G/3G and IchnaeaNlpBackend for wifi it work very well. So it really don't seem to be a UnifiedNlp problem but more a IchnaeaNlpBackend one.