This object is in archive!
Inaccurate tracklog
Answered
I am using Locus for tracklog recording for years and it always worked fine. But recently I found out that tracklog is inaccurate, Locus obviously does not record all the points (screenshot attached), I am using default recording modes (Cycle or Foot). My device is Sony Xperia Z3c, v6.0.1. Locus app is excluded from battery optimisation. I have also Greenify app installed but Locus is excluded also from it. Sony Stamina mode is off.
As you can see in statusbar, now I am running Locus as a service but I don't have this setting tested yet. Can it resolve my problem? 
The same question
Good day Robert,
quite common problem with latest version of Android 6.0+. Firstly I have to ask if you have latest version of Locus Map 3.18.5?
We have FAQ topic because of this here , anyway it looks like you are an experienced user and all basic settings on your device are already correctly set.
I remember I've read somewhere about need to exclude from battery optimization also Google Services or even some location service. Not sure if either of it is installed on your device.
I'm not sure if I helped You. If you find nothing useful, wrote me here and I'll try to search little more on the internet.
Good day Robert,
quite common problem with latest version of Android 6.0+. Firstly I have to ask if you have latest version of Locus Map 3.18.5?
We have FAQ topic because of this here , anyway it looks like you are an experienced user and all basic settings on your device are already correctly set.
I remember I've read somewhere about need to exclude from battery optimization also Google Services or even some location service. Not sure if either of it is installed on your device.
I'm not sure if I helped You. If you find nothing useful, wrote me here and I'll try to search little more on the internet.
Hello Menion, thanks for a really swift response (y)
Actually I've got Locus v3.18.6 :-) (the last from the store). Thanks for the hint, probably you are right that the problem is caused by disabling GPS services when the phone is locked. Locus itself seems working all the time also in background, it appears immediately when I tap on the icon. So I reviewed Battery optimisation settings again, especially system services (under ALL OTHERS tab) and found items LocationServices, Google Play services and Google Services Framework. The first one seems the most promising for me so I excluded it from optimisation. I will test it and let you know.
As for Locus as a service - do you recommend using it or I should rather turn it off when Locus works correctly in background?
Robert
Hello Menion, thanks for a really swift response (y)
Actually I've got Locus v3.18.6 :-) (the last from the store). Thanks for the hint, probably you are right that the problem is caused by disabling GPS services when the phone is locked. Locus itself seems working all the time also in background, it appears immediately when I tap on the icon. So I reviewed Battery optimisation settings again, especially system services (under ALL OTHERS tab) and found items LocationServices, Google Play services and Google Services Framework. The first one seems the most promising for me so I excluded it from optimisation. I will test it and let you know.
As for Locus as a service - do you recommend using it or I should rather turn it off when Locus works correctly in background?
Robert
Hello,
ah 3.18.6 ... there were more versions in row so I've completely forget how many of them I already made last days :).
Yes, please let me know how your tests goes, I'm really curious and we should add positive result into our FAQ as well.
Locus as a service was very useful in days of Android 4.0 and below. Now it's usage is not too high. Anyway if you want to keep Locus enabled and in memory even if you do not use any active service (like track recording, live-tracking etc), then this feature may help. Anyway I've it enabled all the time and it cause no problems, no battery drain etc. It just increase priority of Locus in list of applications in your system, so it should not be the first one killed when there is low of memory.
Hello,
ah 3.18.6 ... there were more versions in row so I've completely forget how many of them I already made last days :).
Yes, please let me know how your tests goes, I'm really curious and we should add positive result into our FAQ as well.
Locus as a service was very useful in days of Android 4.0 and below. Now it's usage is not too high. Anyway if you want to keep Locus enabled and in memory even if you do not use any active service (like track recording, live-tracking etc), then this feature may help. Anyway I've it enabled all the time and it cause no problems, no battery drain etc. It just increase priority of Locus in list of applications in your system, so it should not be the first one killed when there is low of memory.
Hello,
I was thinking about that issue because I was sure that everything worked well also after upgrade to MM and I knew that I didn't changed neither Battery optimization nor Greenify. So I checked all my apps again and recalled that recently I installed Amplify app which saves battery by limiting wakelocks and alarms of system services including location services. Now I froze this app and I will test tracklog recording behavior again. But now I am almost sure that this was the cause.
Hello,
I was thinking about that issue because I was sure that everything worked well also after upgrade to MM and I knew that I didn't changed neither Battery optimization nor Greenify. So I checked all my apps again and recalled that recently I installed Amplify app which saves battery by limiting wakelocks and alarms of system services including location services. Now I froze this app and I will test tracklog recording behavior again. But now I am almost sure that this was the cause.
Hello,
thanks Robert, please let me know after you do some more tests. Hope it will be it.
Hello,
thanks Robert, please let me know after you do some more tests. Hope it will be it.
Hello,
yesterday I had opportunity to do some tests and unfurtunately problem persists :-( Tracklog is accurate for first 5-7 minutes, afterwards it seems that location sevirces are off until yhe moment thhe phone is used (it worked for a while when I take phone from my pocket and made few photos. When I locked it and returned to pocket, tracklog was just straight line again. It is well visible on the screenshot:
So the Amlify app is obviously not to be blamed, I must continue seeking for the cause. Now I reviewed Battery Optimisation settings again and excluded "Google Services Framework"and "Google Play services". If it doesn't help, I will have no idea what else I can do and probably return to Lollipop.
Hello,
yesterday I had opportunity to do some tests and unfurtunately problem persists :-( Tracklog is accurate for first 5-7 minutes, afterwards it seems that location sevirces are off until yhe moment thhe phone is used (it worked for a while when I take phone from my pocket and made few photos. When I locked it and returned to pocket, tracklog was just straight line again. It is well visible on the screenshot:
So the Amlify app is obviously not to be blamed, I must continue seeking for the cause. Now I reviewed Battery Optimisation settings again and excluded "Google Services Framework"and "Google Play services". If it doesn't help, I will have no idea what else I can do and probably return to Lollipop.
Tested and it didn't work anyway. Also I tried to log a track by Endomondo, logging was interrupted after few minutes of phone being locked in my pocket. Below is a screenshot of Endomondo warning message:
I checked FAG in a link but found out nothing new.
Tested and it didn't work anyway. Also I tried to log a track by Endomondo, logging was interrupted after few minutes of phone being locked in my pocket. Below is a screenshot of Endomondo warning message:
I checked FAG in a link but found out nothing new.
I have downgraded my phone to a Lollipop version 5.1.1 (full install from factory default) and re-set power options (exceptions for Locus and Endomondo in Sony Stamina, Greenify, etc.) Afterwards I have tested track logging with both apps and everything worked without any problem.
I have downgraded my phone to a Lollipop version 5.1.1 (full install from factory default) and re-set power options (exceptions for Locus and Endomondo in Sony Stamina, Greenify, etc.) Afterwards I have tested track logging with both apps and everything worked without any problem.
i have the same problem with my android phone after it have upgraded. No matter how i stop the battery saver, its seem to be always-on, and affecting the GPS functions or related somehow.
I'm so tired about it and then i does my first "Flash Rom" to CM13, the result is also perfect.
i have the same problem with my android phone after it have upgraded. No matter how i stop the battery saver, its seem to be always-on, and affecting the GPS functions or related somehow.
I'm so tired about it and then i does my first "Flash Rom" to CM13, the result is also perfect.
Good day guys,
sorry to hear about such troubles. Unfortunately I'm worried I cannot help here.
Please check only this post from one Locus user, maybe it will be useful for you as well: http://forum.locusmap.eu/index.php?topic=5297.msg44500#msg44500
Good day guys,
sorry to hear about such troubles. Unfortunately I'm worried I cannot help here.
Please check only this post from one Locus user, maybe it will be useful for you as well: http://forum.locusmap.eu/index.php?topic=5297.msg44500#msg44500
Hello all,
in one of my comment I mentioned that track logging worked correctly also after upgrade to MM. But when I reviewed my saved tracks, I noticed that all these logs were taken during my jogging exercises when I am also using my phone as a music player. I suppose that player app doesn't allow mobile to switch to a doze mode so GPS is always on during that activity. When riding a bike, I am not listening to a music so track logging is the only activity and GPS was always turned off during it.
Hello all,
in one of my comment I mentioned that track logging worked correctly also after upgrade to MM. But when I reviewed my saved tracks, I noticed that all these logs were taken during my jogging exercises when I am also using my phone as a music player. I suppose that player app doesn't allow mobile to switch to a doze mode so GPS is always on during that activity. When riding a bike, I am not listening to a music so track logging is the only activity and GPS was always turned off during it.
Replies have been locked on this page!