Colota cannot get GPS lock anymore

[acidicX]

Describe the bug

"Searching GPS..." forever with tracking enabled

Steps to reproduce

1. Start colota

Expected behavior

GPS lock should work (was working before 1.16.1 and works in other apps)

Screenshots If applicable, add screenshots to help explain the problem.

Device info

• Device: OnePlus 8T
• Android version: 16
• App version: 1.16.1 FOSS (fdroid)

Additional context

I have LineageOS installed with play services (GApps)

[dietrichmax]

Hi, are you in a geofence when this issue occurs or have some active tracking profiles? If so can you please share the config via Share Setup Link.

[acidicX]

@dietrichmax might be, I'm gonna try and update to 1.16.2 while outside a geofence today, so we'll see if I get a lock then.
I don't have active tracking profiles.

[acidicX]

@dietrichmax nope, does not work outside the geofence as well - same behaviour; also with 1.16.2. Even after acquiring lock with other apps like OrganicMaps and switching back to colota, still nothing ("searching for gps").

[dietrichmax]

Could you send a debug log export from a session where it's stuck? Settings > Logging > Persistent file logging - enabled > export.

[dietrichmax]

Saw your LineageOS issue. Since 1.12.1 the FOSS build asks for the platform fused provider on Android 12+ and on a GApps device the network side of that is usually Play Services, so a blocked GMS would leave fused with nothing coming back.

If you haven't already tried this it may be worth a shot:

adb shell appops set --uid com.google.android.gms FINE_LOCATION allow
adb shell appops set --uid com.google.android.gms COARSE_LOCATION allow

If it does work, worth checking whether it survives a reboot.

[acidicX]

Hi @dietrichmax,

already tried that. Sadly does not work. It seems some kind of supervision is resetting the UID permission instantly to ignore. I have shelter installed for a work profile, maybe that gets in the way somehow.

I'm curious if this would also be broken with fused and a disabled network location provider (which I have always set to disabled anyway), even without my uid issue, but I don't have a spare lineageos phone to test that.

[acidicX]

What's also weird is that it is set for FINE_LOCATION to ignore as well, but that works for some reason. But I can see that NLP is getting denied by appops...

[dietrichmax]

Had a quick look at the AOSP fused code. From what I can tell disabling the network provider shouldn't stop it from using GPS.
So I'm not really sure what's going on. Sounds like it comes back to whatever keeps resetting your appops.

[acidicX]

Yeah, at this point I'm probably gonna go for a full reflash of the phone to see if I can fix the permissions and once that is cleared, I'll try to reproduce with NLP disabled.