Network-based location not used on LineageOS with MicroG #4158

New issue

Closed

opened 2022-12-26 16:00:15 +00:00 by philipmgrant · 6 comments

philipmgrant commented

2022-12-26 16:00:15 +00:00

(Migrated from github.com)

My setup:
Organic Maps (2022.12.18-12-FDroid.22121812)
Moto G5S+ (sanders)
LineageOS 17.1 (based on Android 10)
MicroG 0.2.24.214816

The problem is that Organic Maps never finds a location when GPS can't get a lock - even when network location providers are active (via MicroG).

Organic Maps does have location permissions, and can successfully get locations from GPS.

I know MicroG's network location can be unreliable, but that doesn't seem to be the problem here: I can see from the MyLocation app that the Apple and Mozilla backends are reporting up-to-date locations, and from logcat that LocationFuser does find a fused location.

I can't see a smoking gun in the logcat, but to be honest I have limited knowledge of what to look for - if anyone can point me to what to look for in the logs, then I can provide it here.

My setup: Organic Maps (2022.12.18-12-FDroid.22121812) Moto G5S+ (sanders) LineageOS 17.1 (based on Android 10) MicroG 0.2.24.214816 The problem is that Organic Maps never finds a location when GPS can't get a lock - even when network location providers are active (via MicroG). Organic Maps does have location permissions, and can successfully get locations from GPS. I know MicroG's network location can be unreliable, but that doesn't seem to be the problem here: I can see from the MyLocation app that the Apple and Mozilla backends are reporting up-to-date locations, and from logcat that LocationFuser does find a fused location. I can't see a smoking gun in the logcat, but to be honest I have limited knowledge of what to look for - if anyone can point me to what to look for in the logs, then I can provide it here.

biodranik commented

2022-12-26 16:05:32 +00:00

(Migrated from github.com)

Can you please enable logs in OM settings, reproduce the location search failure, and then share logs with us via "?" -> Report a bug?

RedAuburn commented

2022-12-26 16:32:23 +00:00

Member

i think i get this issue as well on Lineageos 19.1 w/ UnifiedNLP, i'll try get logs too

i _think_ i get this issue as well on Lineageos 19.1 w/ UnifiedNLP, i'll try get logs too

philipmgrant commented

2022-12-26 16:40:20 +00:00

(Migrated from github.com)

Can you please enable logs in OM settings, reproduce the location search failure, and then share logs with us via "?" -> Report a bug?

Thank you, I've just sent them over!

> Can you please enable logs in OM settings, reproduce the location search failure, and then share logs with us via "?" -> Report a bug? Thank you, I've just sent them over!

philipmgrant commented

2022-12-28 20:29:05 +00:00

(Migrated from github.com)

This turns out not to be a problem on the Github release version of OM, which works fine with MicroG network location. Thanks @biodranik for the assistance!

biodranik commented

2022-12-29 00:20:32 +00:00

(Migrated from github.com)

Let me summarize: FDroid build of OM doesn't have the Google Location services library integrated, and it doesn't detect networking location providers on a de-googled device.

Any other build (web, Huawei, Google) has this Google library, which works properly with Microg.

It could be a Microg issue.

Let me summarize: FDroid build of OM doesn't have the Google Location services library integrated, and it doesn't detect networking location providers on a de-googled device. Any other build (web, Huawei, Google) has this Google library, which works properly with Microg. It could be a Microg issue.

👍 2

RedAuburn commented

2023-01-07 17:33:30 +00:00

Member

I'm looking more into this, it's definitely a MicroG issue, possibly something to do with UnifiedNLP not being used by fusedlocation?

As a workaround, you can force it to use the network location by enabling your phone's battery saver mode. This disables GPS and only uses network and passive location. (use location provider debugger to verify this)

I'm looking more into this, it's definitely a MicroG issue, possibly something to do with UnifiedNLP not being used by fusedlocation? As a workaround, you can force it to use the network location by enabling your phone's battery saver mode. This disables GPS and only uses network and passive location. (use [location provider debugger](https://apt.izzysoft.de/fdroid/index/apk/com.michaelfotiadis.locationmanagerviewer) to verify this)

This repo is archived. You cannot comment on issues.