This object is in archive!
Locus crash and data loss
Not a Problem
Don`t know why (I guess RAM overfill) my Locus Free crashed while displaying my recorded tracks. After I started the application again, all my data with tracks were gone. I tried to find them in my file system, but they are lost. POIs maintained. I run Huawei Ascend G300, Android 4.0, 1GHz one-core processor, 512 MB RAM. Maybe, it can occur on not so powerful devices with ICS.
The same problem 
Shit. I hope you will get them back, mate!
Shit. I hope you will get them back, mate!
Unfortunatelly, they are gone. I tried even a data recovery software, but I found just the empty tracks.db
Unfortunatelly, they are gone. I tried even a data recovery software, but I found just the empty tracks.db
Hello Martin,
Hello Martin,
1. Restart was 1st thing I did. Haven`t worked. (Instead of tracks.db there immediatelly appeared new tracks.db much much much smaller then the original one.)
2. Yes I have. Fortunatelly the last backup is 2 month old (the most important data are earlier), and next backup was planned on next day...
At this point - what is behavior of auromatic backup? - I mean, if e.g. the backup is set to start at 20:00 1.8.2013 and Locus is not running at this time, will the backup process start with the next start of Locus e.g. 2.8.2013 in the morning?
1. Restart was 1st thing I did. Haven`t worked. (Instead of tracks.db there immediatelly appeared new tracks.db much much much smaller then the original one.)
2. Yes I have. Fortunatelly the last backup is 2 month old (the most important data are earlier), and next backup was planned on next day...
At this point - what is behavior of auromatic backup? - I mean, if e.g. the backup is set to start at 20:00 1.8.2013 and Locus is not running at this time, will the backup process start with the next start of Locus e.g. 2.8.2013 in the morning?
In this case, I`m sorry, but there is nothing I can do. At least I have currently no idea.
Automatic backup planned on 1.8.2013 20:00 should be performed in this time +- max 1 or 2 hour. This backup task is planned as automatic task in your system, so your system should wake up (start) locus, locus will do backup and then terminate itself.
by default, backup is set to every three days. In Android documentation is wrote "There is no case, how SQLite database may be corrupted on Android", but as you may see (and you`re not the first one), it`s not true.
So please, keep automatic backup enabled for next time, because it may, rarely, happen and I`m always sorry for that ...
In this case, I`m sorry, but there is nothing I can do. At least I have currently no idea.
Automatic backup planned on 1.8.2013 20:00 should be performed in this time +- max 1 or 2 hour. This backup task is planned as automatic task in your system, so your system should wake up (start) locus, locus will do backup and then terminate itself.
by default, backup is set to every three days. In Android documentation is wrote "There is no case, how SQLite database may be corrupted on Android", but as you may see (and you`re not the first one), it`s not true.
So please, keep automatic backup enabled for next time, because it may, rarely, happen and I`m always sorry for that ...
Replies have been locked on this page!