microg / microg/GmsCore

LineageOS 22.2 update - Location (GNSS) active tracking suffers significant delay

Open
#2,961 6 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Java
Stars
14.6k
Forks
3.2k
Avg merge
12d 11h
Merged PRs (30d)
4

Description

Describe the bug
When using an active tracking application (e.g: OsmAnd~, Organic Maps, Trekarta) the current position shown rapidly falls behind the true position such that after less than 10km it reports as being 2.5km behind. After remaining stationery it can take 5-10 minutes for the current position to 'catch up' and show where I am. This is when driving - it is much harder to see it occurring when walking.
Executing multiple applications at the same time they all report the same way - it isn't specific to one application.

When using GPS Test, My Location, or an application that just asks for the current location, the reported coordinates usually seem to be correct in my tests so far.

This started immediately after updating from LineageOS 22.1 to 22.2 from microG. I report this here since I've scoured the LineageOS issue tracker (both open and closed reports) and can find nothing even remotely similar and location services is part of GMS Core.

It feels like some kind of throttling or rationing but I've ensured battery is at 100% when starting and checked system settings aren't set to, or reporting, throttling.

I've watched Logcat but whilst this is happening there is nothing different reported compared to correct behaviour.

Once in about 25 tests it behaved correctly but I could not identify what, if anything, I may have done to cause that.

Device restarts, clearing caches, etc., do not have any noticeable affect.

One possible clue is if - whilst this is happening - I try to disable Location service from the taskbar toggle button it doesn't show a change in state for a minute or more and feels like it has 'hung', but when I've done it from Settings > Location it seems to take effect immediately (at the times I've thought to try this). Even so, re-enabling doesn't improve the situation.

Assisted GPS is enabled. Wifi/Bluetooth location helpers disabled. 4G cellular network operating most of the time.

To Reproduce
Steps to reproduce the behavior:

  1. Start any application that actively tracks current location
  2. Drive some route and observe the reported location fall behind quite rapidly.

Expected behavior
Active tracking location applications should show the current location accurately and update that as the device moves.

Screenshots
Not going to be much help in this case

System
Android Version: 15
Custom ROM: LineageOS 22.2 from microG
Device: OnePlus 6 (enchilada)

Additional context
22.1 worked correctly.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by reproducing the delay with an active tracking application on a OnePlus 6 running LineageOS 22.2 from microG, compare it with 22.1 behavior, and inspect Location settings and Logcat while tracking. Done means the cause of the delayed updates is identified and active tracking reports the current position accurately.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.