New Topic

Locus Map - help desk Topic Problem Locus Map (Android)

Category Locus Map (Android)

Tags gps, trackrecording, recording, track

Application Locus Map 4

Comments 24

Subscribers 5

Votes 1

Track recording inaccurate despite high accuracy of GPS

Flak shared this problem ago

In Progress

I have an issue with the track recording on my phone:

When I cycle with my bike and record a track and my display from the phone is off then I got very wrong track lines. (Screenshot LocusMap 1.png)

On the Screenshot you can see I have good GPS Signal all the time (max was 5,5m). But the trackpoint is so inaccuracy. I mean it shows an GPS accuracy of 3,3m but my trackline is around 100m away from the real path which I drove.
How is this possible that my GPS accuracy is 3,3m at this trackpoint but my trackline is so much far away from the real path?

I drove the same track again but this time with Display always on. And the Track was perfect in my eyes. (Screenshot LocusMap 2.png)

Now I´m asking you what can I do that my Trackline is always like the Screenshot LocusMap 2.png but with display turned off. I mean I need to save battery for longer trips.

I think it is maybe something with the battery managment of Android (HyperOS)-

My Phone settings and LocusMap 4.29 settings:

Phone: Poco X6 Pro 5G
OS: HyperOS 2.0.104.0 (Android 15)

Track Recording:
distance interval: 8m
time interval: 5s
distance AND time
required GPS accuracy: 20m
Auto Pause: off
recording only during motion: off

GPS Settings:
Location filter: small filtering.
NMEA Recording: only for track recording

I did everything as described in the article:
https://docs.locusmap.app/doku.php?id=manual:faq:gps_lost_fix_android6
Autostart: ON
Battery restriction: OFF
App permission Location: all the time on
every permission for LocusMap is activated/allowed
LocusMap is locked in RAM with the lock
LocusMap runs as Service

In the developer settings of the phone I also activated "force full GNSS measurements"

I tested A-GPS reset many times.

I also tested it with the GPS Locker app. Also this app has all permissions and no battery restrictions. but unfortunately without success.

I googled a lot and also ask ChatGPT a lot for Tipps what I can do to get better accuracy tracks. But without any succes.

maybe someone can help me please?

Files:

The same problem 0

Replies (6)

Michael Bechtold ●

I remember my Huawei Tab M5 was BRUTALLY violating all seetings you mention above, just to be perfect in battery savings - which it was.

Maybe HyperOS is "HYPER" in this regard, too?

With Galaxy (very old, old and latest Androids), LG (older Android) and Moto (older Android) I did not see differences between screen on and off.

Reply URL

Flak ●

Idk. Maybe the OS of Xiaomi phones (HyperOS) is throttling activities when the screen is off.

But thats my question if someone can help me to avoid this throttling?

URL

Michael Bechtold ●

Do you leave LM in the foreground and then turn off the screen?

Or are you back to homescreen when you switch off?

URL

Michael Bechtold ●

Have you tried the auto screen on/off feature?

And have you looked onto this dontkillmyapp lonk in the Locus advisory? Xiaomi received 5 thumbs down for their rogue Android implementation, but there is also some spevific advice.

Files:

URL

Flak ●

Yes I have it in the foreground and than turn the screen off.

URL

Andrew Heard ●

I can see your "Battery restriction" setting is turned off but your inaccuracy sounds exactly like when I forget to turn off "Battery restriction"/ sleep apps/ deep-sleep apps etc.. Find there very detailed Locus knowledge base page on turning off power saving and check twice. It took me a long time to find all the related settings on my phone. Best of luck.

Reply URL

Flak ●

I have under Battery saver: No restrictions (Battery saver doesn´t restrict app´s activity).

I also used the performance mode but without any noticeable improvment.

URL

freischneider ●

Possibly allow background activity.
Battery: Always allow, only during app use is often not enough.

URL

Andrew Heard ●

have you read this page https://docs.locusmap.app/doku.php?id=manual:faq:gps_lost_fix_android6#

URL

Flak ●

yes I read this page and did all.

Read my threat at the top. I also post the same URL as you.

URL

Michal Stupka ●

Hi,

please get Locus Map permission for all-time access to the location and exclude Locus from all means of battery optimization so that the app can run in the background, see http://docs.locusmap.eu/doku.php?id=manual:faq:gps_lost_fix_android6. Also, try switching Google Services assisted location off in Locus settings - GPS&sensors.

Reply URL

Flak ●

I have read this article as described above.

I will try turning off Google services assisted location.

Thanks for your help.

URL

Michal Stupka ●

I also strongly recommend following the instructions in https://dontkillmyapp.com/xiaomi.

URL

Flak ●

I also visited this website before and did the things how it´s descriped but without success. :(

I did some recordings an hour ago with different settings:

mobile Data: on/off
Performance mode: on/off

But the Trackrecording is still very bad. Also the altitude is very unaccurate. (Watch screenshot)

I´m just wondering how it is possible that the tracklinepoint is that much away from my real position. I mean I have "required GPS accuracy: 20m" activ and not 100m+??

Files:

URL

Michal Stupka ●

Have you also tried track recording with another app? E.g. Strava or something?

Reply URL

Flak ●

I will try. Thanks!

URL

Flak ●

Today I tried a few things:

1. I used Komoot to record my track. It is still the same the quality of the trackline is not realy good.
I also disabled all battery optimization things for the Komoot App and give all possible permissions without success.

2. I used my old Poco F1 from 2018 and make with the same record settings a trackrecording. And the quality is much better. This phones has Android 10 (MIUI 12)

I think the problem is with my phone, especially with the Android version 15 (HyperOS 2). One year ago with Android 14 (HyperOS 1). The track quality was perfect. I could see which side of the road I was walking or driving on, the track recording was that accurate.

Now I am disappointed that Android 15 makes everything worse rather than better. :(

URL

Michael Bechtold ●

Compare NMEA log with gpx file might also shed light on that mystery

Reply URL

Flak ●

How can I compare the nmea file with the gpx file?

URL

Michael Bechtold ●

GPS sensors -> Advanced, switch NMEA on

After ride export track gps to file, grab Locus/data/nmea file of the day.

Look up the nmea syntax via Google and look at the time when Locus track goes nuts.

Do similar test with another GPS app running in parallel as Michal has suggested.

URL

Flak ●

I can not really work with this data. Also searching in the NMEA File with Notepad++ isn´t that good.

Maybe you can find some informations in the files?

URL

Michal Stupka ●

Yes, please share the files with us.

URL

Flak ●

https://drive.google.com/drive/folders/1pbppKRTMHM4dGM1pB_HGIVln0NkxChKK

The NMEA file is 5MB I can't upload it here. So I uploaded both files the gpx and the NMEA file from yesterday in my google drive.

Thanks for helping me! :)

URL

Michal Stupka ●

Hi,

unfortunately, the NMEA and GPX comparison didn't reveal any relevant information about the cause of the phone's GPS chip inaccuracy. Could you please test the track recording with another app and compare both results? Thanks.

Reply URL