Stopped functioning after battery empties during logging

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start logging
2. Log till battery drained
3. Connect phone to charger
4. Power on
5. Start My Tracks

What is the expected output? What do you see instead?
My Tracks to start with track logged till phone died. My Tracks stops 
responding and logged tracks not available anymore.

What version of MyTracks are you using? On what version of Android? On what
phone?
MyTracks: 1.0.21
Android: 2.2
Phone: HTC HD2

If possible please provide a log.  Either upload here or send to mytracks-
support@google.com.
Detailed instructions can be found here:
http://code.google.com/p/mytracks/wiki/HowToReportErrors

Please provide any additional information here:
Can I still get my tracks from my phone? I installed My Tracks to the SD card.

Original issue reported on code.google.com by q.seg...@gmail.com on 7 Feb 2011 at 4:33

• Merged into: #287

Attachments:

• Log.txt

[GoogleCodeExporter]

This is not the desired behavior and is certainly not what always happens.  If 
possible can you send a log of this behavior so we can debug it?

Original comment by sandordo...@google.com on 7 Feb 2011 at 4:40

• Changed title: Stoped functioning after battery empties durring logging

[GoogleCodeExporter]

I added a log collected by the log collector last time. Now also ran my tracks 
and afterwards ran log collector. See log.txt

Original comment by q.seg...@gmail.com on 8 Feb 2011 at 9:40

Attachments:

• Log.txt

[GoogleCodeExporter]

Hi, I believe a solution is not found that easily. Maybe someone can help me 
extracting previously recorded data from My Tracks. My tracks does not run on 
my phone anymore. I'm a little bit hesitant in reinstalling My Tracks, as I 
think all logs will be lost. Can I still extract the logs without running the 
program on my phone? For example from the .asec file created on my sd-card?

Original comment by q.seg...@gmail.com on 11 Feb 2011 at 12:14

[GoogleCodeExporter]

This looks like another manifestation of the problem that bart is fixing as 
issue 265.  Another user had the same problem (issue 298), and I made a custom 
APK for him to use to try to work around it.  Please install that APK and see 
if it fixes the problem.  Note that that APK doesn't include some of the fixes 
in 1.1.1, so you'll want to install 1.1.1 from the market afterwards.

Do something like this:
1. Install the APK from 298
2. Start up MT, save the track.
3. (Optional) Export the track to GPX, or use the backup functionality under 
Settings
4. Install the 1.1.1 APK from the Android Market.

Original comment by simmonmt@google.com on 11 Feb 2011 at 12:27

• Changed title: Stopped functioning after battery empties during logging

[GoogleCodeExporter]

This has happend twice for me.  Once the battery has drained and i replace the 
battery with a fresh battery and try to start MyTracks, it will ask to force 
close,wait, or report - nothing I can do to get it to start the app running 
again.   

The only way I can get MyTracks to start running again is to uninstall it 
(which wipes out ALL of my previous tracks) and reinstall (then it works fine). 

(I running 1.1.4 - Droid2 2.2)

Original comment by JEMay...@gmail.com on 20 Apr 2011 at 6:03

[GoogleCodeExporter]

I've been using this great app for 6 months but this problem occurred for me 
when recording a long track during which the battery ran out.
Now MyTracks hangs with a black screen while it tries to load the last 
recordeed track which must be corrupt.
I tried the fix APK for issue 298 but this also hangs with a black screen.
I don't want to loose some tracks which I'd not backed up.
Would it be possible to make a custom APK for this issue that doen't read the 
existing track data but just copies it to the SD card. 
Then I can fix the data file manually.
(Running 1.1.4 on LG GT540 1.6)

Original comment by tonym...@gmail.com on 25 Apr 2011 at 10:17

[GoogleCodeExporter]

This appears to be the same issue as 287.

Original comment by tonym...@gmail.com on 25 Apr 2011 at 10:22

[GoogleCodeExporter]

Original comment by rdama...@google.com on 30 Apr 2011 at 10:05

• Changed state: Duplicate