This object is in archive!
Frozen position during recording
Solved
Hello Guys,
I have one issue when you are recording your track that your position will get stuck in one point and it's not updated anymore. Position is just frozen on place where I was before and from this time track is not logged however everything seems to be ok (time is counting etc..) I have to stop recording, restart my Locus Pro and run it again. I have seen this issue discussed on our bike forum but I haven't seen any solution for it. There are also other people facing to this issue.
I am using last LocusPro version available on Google Play Store but that won't be an issue of last version only. This happened to me a few months ago as well.
Any ideas?
The same problem 
>I have seen this issue discussed on our bike forum.
what language? :) can we read it too?
>I have seen this issue discussed on our bike forum.
what language? :) can we read it too?
Hmm I'm also interested in this discussion, thanks gynta.
I remember I heard about this issue maybe few years before, but I have no idea, if there is any solution. Does it happen more often? If so, I suggest to test any other application, not just Locus. If this will happen as well, you may send your device to service ...
I'm anyway more then sure, that if such issue will be in Locus, there will be already a full help desk of topic "It do not record!! " :). Good luck
PS: Isn't there any update for your device, new version of Android? I believe it should help if this is not a hardware problem
Hmm I'm also interested in this discussion, thanks gynta.
I remember I heard about this issue maybe few years before, but I have no idea, if there is any solution. Does it happen more often? If so, I suggest to test any other application, not just Locus. If this will happen as well, you may send your device to service ...
I'm anyway more then sure, that if such issue will be in Locus, there will be already a full help desk of topic "It do not record!! " :). Good luck
PS: Isn't there any update for your device, new version of Android? I believe it should help if this is not a hardware problem
At least Menion should be able to read this. Pages 55, 56. I remember there was more from the past, I'll try to find it in the morning.
That most probably won't be an hardware issue as we have diferent cell phones and the same issues. Is there any chance to get some log file from my phone tahat could tell more?
http://www.mtbiker.sk/forum/cyklotrasy-navigacie/locus-turisticka-navigacia-pre-android-aj-pre-geocacherov-t26887-810.html
At least Menion should be able to read this. Pages 55, 56. I remember there was more from the past, I'll try to find it in the morning.
That most probably won't be an hardware issue as we have diferent cell phones and the same issues. Is there any chance to get some log file from my phone tahat could tell more?
http://www.mtbiker.sk/forum/cyklotrasy-navigacie/locus-turisticka-navigacia-pre-android-aj-pre-geocacherov-t26887-810.html
I would like to also mention that this happened to me last year on different cell phone (Samsung Galaxy Nexus), this year on Google Nexus 5, android version and Locus version were always the official latest one (both are google phones).
And how often does it happen? Very rare - for last 12 months 3-4 times, I had about 100 trips so 3-4% of all my trips till now. First I thought that I just lost GPS signal from unknown reason. But when it happened 3rd of 4th time (that was this year) I saw that many satellites were connected to my device without any problem just Locus was not updating that position and counting points during track recording. I think that because of this happens so rare and the problem is with position that is stuck people might thought that they just lost GPS signal.
The worst is that I cannot simulate this issue, happens accidentally. For me on the most important and longest trips I had otherwise I could live with that.
PS: I did not find those issues on forum from the past as I mentioned above - sometimes off topic posts are deleted
I would like to also mention that this happened to me last year on different cell phone (Samsung Galaxy Nexus), this year on Google Nexus 5, android version and Locus version were always the official latest one (both are google phones).
And how often does it happen? Very rare - for last 12 months 3-4 times, I had about 100 trips so 3-4% of all my trips till now. First I thought that I just lost GPS signal from unknown reason. But when it happened 3rd of 4th time (that was this year) I saw that many satellites were connected to my device without any problem just Locus was not updating that position and counting points during track recording. I think that because of this happens so rare and the problem is with position that is stuck people might thought that they just lost GPS signal.
The worst is that I cannot simulate this issue, happens accidentally. For me on the most important and longest trips I had otherwise I could live with that.
PS: I did not find those issues on forum from the past as I mentioned above - sometimes off topic posts are deleted
Hello Peter,
I was reading discussion on SK forum and seems you are not alone with this problem (interesting news for me), but there is also no useful information that may helps here.
I may suggest enable "Locus as a service" in misc settings http://docs.locusmap.eu/doku.php?id=manual:user_guide:settings:misc . Maybe your device is low on free memory and Android decide to terminate running recording service. This should help a little.
Anyway what may help most is to immediately you notice this issue, create a log by this method http://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log . Log has some limits in length and some devices are very very talkative. So it may happen that information why Locus stopped recording will be already lost due to huge amount of newest logs (Samsung mainly), but hope there will be some info.
I see no other way how to helps here, sorry.
Hello Peter,
I was reading discussion on SK forum and seems you are not alone with this problem (interesting news for me), but there is also no useful information that may helps here.
I may suggest enable "Locus as a service" in misc settings http://docs.locusmap.eu/doku.php?id=manual:user_guide:settings:misc . Maybe your device is low on free memory and Android decide to terminate running recording service. This should help a little.
Anyway what may help most is to immediately you notice this issue, create a log by this method http://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log . Log has some limits in length and some devices are very very talkative. So it may happen that information why Locus stopped recording will be already lost due to huge amount of newest logs (Samsung mainly), but hope there will be some info.
I see no other way how to helps here, sorry.
Thank you Menion. I don't think that is an issue of low memory as I have 2GB and almost always there is 800-900MB free. But I have enabled that option to run Locus as service.
I will try to get that log when it happens again - I hope it will help.
You guys did really great job here on this application.
I appreciate it.
Thank you Menion. I don't think that is an issue of low memory as I have 2GB and almost always there is 800-900MB free. But I have enabled that option to run Locus as service.
I will try to get that log when it happens again - I hope it will help.
You guys did really great job here on this application.
I appreciate it.
I observed such a Problem twice this weekend. Actually, when i stopped recording, there was a gap/jump in the track recording. What was in common (and different from all the other recordings I did in the past weeks): I started recording via the widget (and not in the App). And apart from that I did not use locus:
* today I did not even open it during the almost 8 hours of recording - and about the last hour was missing.
* yesterday there were about 20 Mins in the middle missing - but I think I opened Locus once at the time the recording resumed (not sure though).
I also played with 'Locus as a service' in settings - but it seems the Sevice only gets started when I start locus itself, not when I just use the widget. So it might be widget-related, but I'll keep an eye on it.
I observed such a Problem twice this weekend. Actually, when i stopped recording, there was a gap/jump in the track recording. What was in common (and different from all the other recordings I did in the past weeks): I started recording via the widget (and not in the App). And apart from that I did not use locus:
* today I did not even open it during the almost 8 hours of recording - and about the last hour was missing.
* yesterday there were about 20 Mins in the middle missing - but I think I opened Locus once at the time the recording resumed (not sure though).
I also played with 'Locus as a service' in settings - but it seems the Sevice only gets started when I start locus itself, not when I just use the widget. So it might be widget-related, but I'll keep an eye on it.
The issue I have sounds a lot like the one described here: http://stackoverflow.com/questions/33320695/how-does-doze-standby-feature-affect-location-updates
But as I am not into Android Programming, I have no Idea wether there is a solution to that or not.
The issue I have sounds a lot like the one described here: http://stackoverflow.com/questions/33320695/how-does-doze-standby-feature-affect-location-updates
But as I am not into Android Programming, I have no Idea wether there is a solution to that or not.
Hello Ulrich, Viajero,
I have just yesterday found a method, how app may check if "Battery optimization" is enable and offer option to disable it. So this will be in next Locus version. Not sure if it helps here, as you wrote that you already disabled it.
Firstly, this problem really is not a problem in Locus itself. It cannot be solved by any change in code etc. So secondly, I may only suggest to search in settings of your device and check it all possible optimization techniques are disabled for Locus.
What about "GPS auto-off" feature in Locus > settings > GPS & Location? Are you using it? Suggest to disable it as it may have effect here.
Hello Ulrich, Viajero,
I have just yesterday found a method, how app may check if "Battery optimization" is enable and offer option to disable it. So this will be in next Locus version. Not sure if it helps here, as you wrote that you already disabled it.
Firstly, this problem really is not a problem in Locus itself. It cannot be solved by any change in code etc. So secondly, I may only suggest to search in settings of your device and check it all possible optimization techniques are disabled for Locus.
What about "GPS auto-off" feature in Locus > settings > GPS & Location? Are you using it? Suggest to disable it as it may have effect here.
Replies have been locked on this page!