This object is in archive!
Dashboard: Current time is not updated
Not a Problem
In v3.0.2 in the dashboard, the field "current time" is not updated except you restart Locus or you hide the dashboard and make it visible again. So it showed me the same time for 3-4 hours...
This is the "normal time" an not any of sections track recording/navigation/guiding.
The same problem 
Hmmm - it works here on 2 devices (rooted and stock)
- android version?
- mod?
The only thing I've noticed: The time "sleeps" in "screen save mode" and was refreshed after wake up the phone. (this make sense - but maybe there is a problem on other devices)
my test-dash attached...
Hmmm - it works here on 2 devices (rooted and stock)
- android version?
- mod?
The only thing I've noticed: The time "sleeps" in "screen save mode" and was refreshed after wake up the phone. (this make sense - but maybe there is a problem on other devices)
my test-dash attached...
FYI: The time is not always "frozen" on my device. This week end, I was hiking and doing a via ferrata (Tälli in Switzerland, very nice landscape) and I did not recognize that the time was "lagging behind". I'll observe this - I've the impression, it is dependent on some circumstances (track recording active? edited the dashboard?). It was frozen when I was at home and fiddling with dashboard etc.
FYI: The time is not always "frozen" on my device. This week end, I was hiking and doing a via ferrata (Tälli in Switzerland, very nice landscape) and I did not recognize that the time was "lagging behind". I'll observe this - I've the impression, it is dependent on some circumstances (track recording active? edited the dashboard?). It was frozen when I was at home and fiddling with dashboard etc.
I'm checking a code and there should be no reason why just time get stuck. Everything or nothing, but just time it's almost impossible.
So please watch it carefuly and if you find any reason for this, write me. Thanks
I'm checking a code and there should be no reason why just time get stuck. Everything or nothing, but just time it's almost impossible.
So please watch it carefuly and if you find any reason for this, write me. Thanks
This seems to have been a single occurrence and can be closed. During the last week, I was not noticing the issue even once despite intensely using Locus v3.1.3 -- daily around 4-8 hours hiking, doing via ferrata etc. in the "Wilder Kaiser" which is especially recommendable for climbers (many sectors and climbing styles) and for people with limited condition (dense infrastructure allows to limit stages as required/desired).
This seems to have been a single occurrence and can be closed. During the last week, I was not noticing the issue even once despite intensely using Locus v3.1.3 -- daily around 4-8 hours hiking, doing via ferrata etc. in the "Wilder Kaiser" which is especially recommendable for climbers (many sectors and climbing styles) and for people with limited condition (dense infrastructure allows to limit stages as required/desired).
If you find any way to simulate this problem, let me know.
And thanks for an information.
If you find any way to simulate this problem, let me know.
And thanks for an information.
Replies have been locked on this page!