OSMTracker no longer tracks after restart by ActivityManager

[GoogleCodeExporter]

What steps will reproduce the problem?

1. start tracking
2. wait more than one hour WITHOUT using the phone
3. reactivate phone from standby and see that tracking has stopped approx. one 
hour after it was started and will only proceed after phone was reactivated 
from standby

What is the expected output? What do you see instead?

I expect continuous tracking. instead the tracking stops after approx. one hour

What version of the product are you using (See "About" screen)?
0.5.6

Make/model of your device, and Android version?
Motorola Defy+ Android 2.3.4

Please provide any additional information below.

As far as I can see from the logs, Android's ActivityManager stops OSMTracker 
after approx. one hour when display is inactive.
It is then scheduled for restart 5 secs later, but although restarted, it 
tracks no longer.

See attached logfile from CatLog. 

Original issue reported on code.google.com by stsich...@googlemail.com on 7 Nov 2011 at 1:19

Attachments:

• StopsTracking.log

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

just found out one additional thing: OSMtracker must be in the background in 
order to reproduce this problem!

Original comment by stsich...@googlemail.com on 7 Nov 2011 at 2:56

[GoogleCodeExporter]

Hi, sorry for not replying earlier but I stopped getting notifications for new 
issues for some reason.

I'm curious about how you collected this log ? Did you let the phone run for 1H 
and them filter it manually ?

Might be related to http://code.google.com/p/android/issues/detail?id=14340 
maybe ? I've applied the workaround, it will be available on the next release, 
I hope this will help.

Original comment by nicolas@guillaumin.me on 28 Jul 2012 at 8:22

• Changed state: Started
• Added labels: Priority-High, v0.5.8
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Note that I had to bump the API to 7 (Android 2.1) to be able to use the 
workaround, hopefully 1.5/6 is not used anymore.

Original comment by nicolas@guillaumin.me on 28 Jul 2012 at 8:25

[GoogleCodeExporter]

I also made another fix for #182 that should help with this issue too.

Please re-test once the new version is on the market and re-open if needed, 
thanks !

Original comment by nicolas@guillaumin.me on 28 Jul 2012 at 11:35

• Changed state: Fixed

[GoogleCodeExporter]

Yes, this is exactly what I did. I used CatLog for logging in background and 
let OSMTracker record a track for more than one hour when also switched to 
background.

Now I just retried this with the new version 0.5.8 => problem is fixed! :-) 
Thank you!

Original comment by stsich...@googlemail.com on 30 Jul 2012 at 9:41

[GoogleCodeExporter]

Cool, thanks for the thorough testing !

Original comment by nicolas@guillaumin.me on 30 Jul 2012 at 12:43