This object is in archive! 

Track selection status lost on reboot/crash

joeloc shared this problem 11 years ago
Solved

When I reboot or crash the phone while Locus is up and running, the track selection states are lost. Locus will come up "clean" after reboot and I have to manually enable all the tracks I want displayed again. Thats quite a tedious task sometimes. It would be nice if Locus could conserve the track (&point) selection state even through unintentional reboots.


(tested with latest pro version)

Replies (8)

photo
0

Hi,


how often this happen to you? Because it`s quite un-usual situation.


Locus currently save current visible track/points in time you close Locus or just minimize it (put on background or turn off screen). This is I think enough.


So in case you need to reboot your device, just before put locus to background. In case it crash, suggest to send me a logs, because except OutOfMemory problems (due to visible 1025 tracks), this problem should be fixed!

photo
0

It happens about 2-3 times per week... often enough to be annoying.

photo
0

Your saving strategy sounds reasonable though. And I have no idea how that could ever result in Locus coming up completely "clean", ie with no tracks and no points selected. I certainly never deselected everything manually.


Could there be any other reasons for the selection status being lost? It also happens on my travel buddies phone from time to time. I simply assumed it would be unintentional reboots, because he frequently runs out of battery.

photo
0

It just happened again. Locus came up completely clean after a reboot, all track selection states lost. And they definetely WERE selected before... and saved. So there must be another problem were Locus loses these states.

photo
0

I`m trying to search through code for some possible places why this may happen, but I`m unable to find any. In next test versions will be some debug messages in functions that work with these information, so please create for me a log when this happen again. Thanks

photo
0

Just happened again. Remember that it only happens after a reboot apparently and only very occasionaly. The error log must be written always and automatically, otherwise it wont help.

photo
0

stefan perfect. You`ve got point. Problem was "backup system". Problem found and fixed!

photo
0

My pleasure. Every day with a fixed problem is a good day :)

Replies have been locked on this page!