Data loss / crash when OS alarm rings

[GoogleCodeExporter]

Any time an alarm pops up while I'm surveying, the program does and my 
tracks are lost.

With the program not being obscured (stopped) only put on pause with a 
transparent popup from the alarm program in foreground, the program 
shouldn't need to die anyway, but it always does. After I stop or snooze the 
alarm the program is gone and I'm back at the home screen.

Track data really needs to be saved incrementally! I've lost several good 
tracks because I left early for somewhere so I could survey on my way only 
to have it clobbered when the alarm for the event I was enroute top pops up. 
Several other program crashes have caused the same thing. While some of 
those bugs have gotten fixed, the data lose problem is pretty much the same.

Original issue reported on code.google.com by alerque on 9 Apr 2010 at 7:31

[GoogleCodeExporter]

Interesting ! Will have a look at it.

Sorry for the data loss :-( Concerning incremental save it's the next big step I
think: Keep track of all recorded tracks in a database, and allow user to 
re-export
previous ones.

Original comment by nguillau...@gmail.com on 10 Apr 2010 at 5:29

• Changed state: Accepted
• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

It works on my 1.6 device. Can you remind me which device and Android version 
you're
using please ?

Original comment by nguillau...@gmail.com on 10 Apr 2010 at 5:35

• Changed title: Data loss / crash when OS alarm rings

[GoogleCodeExporter]

Just tested on Android 2.1 and seems to work too.

Original comment by nguillau...@gmail.com on 10 Apr 2010 at 5:47

[GoogleCodeExporter]

My weapon is an ADP1 with CyanogenMod 4.2.15.1 which is Android-1.6 based but 
has some 
apps and interfaces back-ported from newer AOSP code.

I have not seen this problem with any other app, including ones that play audio 
and 
get interrupted by an alarm and those that use the gps and get interrupted. For 
example Vespuci ticks right along saving my track even when hit with a 
foreground 
alarm going off.

Original comment by alerque on 10 Apr 2010 at 7:45

[GoogleCodeExporter]

Do you know if CyanogenMod is shipped with the default Alarm Clock, or a 
replacement
program ? I read some things about that, but I'm not sure:
  * http://forum.cyanogenmod.com/index.php?/topic/459-alarm-clock-42141-or-later/
  * http://forum.xda-developers.com/showthread.php?t=567610 (See "Music and DeskClock
apps from Eclair")
  * http://www.cyanogenmod.com/home/cyanogenmod-4-2-14

Original comment by nguillau...@gmail.com on 10 Apr 2010 at 1:00

[GoogleCodeExporter]

It is neither the "default" alarm clock nor a "replacement program" -- it is a 
back-
port of the stock android alarm clock but a newer version than originally 
shipped 
with the core rom. This arrangement is generally quite stable, I have had 
absolutely 
no other FC's or even minor hiccups with anything else besides a task killer 
program 
that everybody has problems with. The alarms themselves run like clockwork 
(excuse 
the pun) and no other programs react badly to the popup snooze/end window.

The only other thing that comes to mind is that I do run the Turkish locale. I 
haven't had trouble recently but using alternate locales does have a long 
history of 
causing problems, esp with newly developed apps -- but I've seen mentions of a 
couple 
translations of osmtracker so I don't know what specifically this would be.

Original comment by alerque on 10 Apr 2010 at 8:27

[GoogleCodeExporter]

One more thing I just noticed. Apparently it is only a problem if the program 
is tracking. Having an alarm 
pop up up with just the program up with no active track has no adverse effect.

Original comment by alerque on 11 Apr 2010 at 5:21

[GoogleCodeExporter]

I've lost data too, but not for an alarm. I spent an hour making a detailed 
track 
with the map view on the whole time (with phone display locked). When I was 
nearly 
finished, I unlocked the phone and found the map display blank. OSMTracker 
refused to 
respond. I left the phone as is hoping it would recover.

Five minutes later, I received a call. When I went back to OSMTracker, the map 
display was working again, but OSMTracker was no longer tracking (it had 
apparently 
been shutdown and restarted again by Android). I could see the map, but the 
"Save & 
Exit" menu option had reverted to "Start Tracking", which was disabled pending 
a GPS 
fix.

As I had no option, I went back outdoors, waited for a GPS fix, clicked "Start 
Tracking", and found my entire detailed track gone.

My SD card has a folder for both traces, but the first one, which should have 
had the 
detailed trace, is blank. OSMTracker crashed without saving.

Original comment by jackerhack on 25 Apr 2010 at 4:21

[GoogleCodeExporter]

Sorry for the data loss :-( I still don't know exactly what is causing that, I 
can't
reproduce it. However I'll try to find a workaround... Can you tell me which 
device
and Android version you have ? Thanks.

Original comment by nguillau...@gmail.com on 26 Apr 2010 at 8:35

[GoogleCodeExporter]

The "data lost" shouldn't occur again now that v0.5.x has the ability to 
re-export previous tracks.

Original comment by nguillau...@gmail.com on 4 Oct 2010 at 5:12

[GoogleCodeExporter]

Original comment by nicolas@guillaumin.me on 29 Jul 2012 at 8:41

• Changed state: Fixed