search

fjlopezs / mytracks

Automatically exported from code.google.com/p/mytracks
0 stars 0 forks source link

Blank screen on startup after recording a long track #287

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I was recording a track that ended up lasting about 9 hours, and then 
presumably the battery died.  I tried to turn on the phone again, it shut off 
again just after bootup, battery really was dead.

After that, whenever I went into MyTracks, it just showed a blank screen, and 
after a few seconds, said it wasn't responding and gave me the option to wait 
or force quit.  Waiting hours didn't help, nor did rebooting the phone.

I managed to copy the data files for the app to my computer, and was able to 
recover the data by dumping the trackpoints table.  Not sure if this was the 
problem, but some of the rows were corrupt, e.g.:

good:

"14691","6","-120770355","39221985","1296350687000","1380.0","48.0","29.25","221
.1328125"

bad:

"14692","6","0","100000000","1296350687000","","","",""

While I was there, I tried deleting 
/data/data/com.google.android.maps.mytracks/databases/*.db and after I did 
that, MyTracks worked again.

Since then, I've tried copying the database files back to the phone, but I 
haven't been able to reproduce the bug.  I've also tried that with the tile 
files, no couldn't reproduce with that either.

I'm using MyTracks version 1.0.21, on a Nexus One, Android version 2.2.2 build 
FRG83G

Original issue reported on code.google.com by tomfel...@gmail.com on 31 Jan 2011 at 5:47

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I should mention that I found this procedure helpful, though I do believe it 
requires root:

http://www.melaneum.com/blog/python/saving-data-from-android-sqlite-to-gpx

Original comment by tomfel...@gmail.com on 13 Feb 2011 at 8:32

GoogleCodeExporter commented 9 years ago 
Issue 302 has been merged into this issue.

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

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I have just had this happen to me.  I have pulled the database from my device 
but I don't have any blank entries in the database like the OP.

My route was only about 4 hours and contains 12522 trackpoints.  I have cleared 
the data from my device using the app manager which now allows MyTracks to 
start.

Using MyTracks version 1.1.4 on HTC Desire

Original comment by oliver.h...@googlemail.com on 18 May 2011 at 10:28

GoogleCodeExporter commented 9 years ago 
I have the same problem with version 1.1.7 on HTC Desire.

I'm not sure about the amount of track points cause i cannot access the track 
anymore, but I had it running for the whole day.

I don't want to clear the data because it's kind of important. Is there a 
different way to recover those tracks w/o rooting my device?

Original comment by jiji....@gmail.com on 14 Jul 2011 at 6:45

GoogleCodeExporter commented 9 years ago 
Got it working again. After letting it sit on the black screen for about 3 1/2 
hours while recording the logcat output. I attached parts of it. All 3 tracks 
where still ok and it's running just fine now.

Original comment by jiji....@gmail.com on 15 Jul 2011 at 1:20

Attachments:

GoogleCodeExporter commented 9 years ago 
Same problem here. I've finally gotten around to running through the logging 
process outlined on the mailing list; please find it attached. I was able to 
export the tracks using a process described by one of the list members and they 
seem to be OK. 

I can see the point where it times out trying to run: 

"Timeout executing service: ServiceRecord{40acc208 
com.google.android.maps.mytracks/com.google.android.apps.mytracks.services.Track
RecordingService}"

I realise I can just nuke the data but I'd like to keep it in there if 
possible. 

Hope this helps!

Original comment by davidhar...@gmail.com on 26 Aug 2011 at 3:12

Attachments:

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Issue 460 has been merged into this issue.

Original comment by jshih@google.com on 19 Nov 2011 at 1:58

GoogleCodeExporter commented 9 years ago 
I also ran into this same issue a couple days ago when I was testing prior to a 
long trip I tracked yesterday. The only way I could recover was to run 
Taskiller which terminated the My Tracks process. Then after restarting My 
Tracks, I was able to delete old tracks which had already been Shared (ie track 
data stored elsewhere in Maps, Docs, etc), then resume or recover the 
interrupted Track data... So, unlike the OP in this thread, I <did not> suffer 
corrupted data, I only had to make enough room for the application to function.

As others have noted, this problem is fundamentally related to running out of 
space. 

Besides considering graceful ways to warn about storage space starvation, I 
<highly> recommend simply modifying the data storage path to point to external 
storage (eg SDCARD).  Like camera and the Download folder (which is 
automatically re-directed whenever external storage is detected on my MyTouch 
Slider 3G), this may be the simplest and best solution of all (Just get a 
bigger or additional SDCARDS if you need to collect larger amounts of data)

IMO,
TSU

Original comment by tonysu...@gmail.com on 19 Dec 2011 at 11:58

GoogleCodeExporter commented 9 years ago 
Motorola DroidX; MyTracks version 1.1.16. Very similar happened to me a few 
days ago. After deciding all was lost, I touched Wait and MyTracks came back 
after about four hours. During that time, checking task stattus, I observed 
that it was "deleting temporary files" and "recording data" or words to that 
effect. I did lose what would have been 21 hours of the 24 hours of data I was 
going to record, but the first three hours (before it hung the first time) were 
all there and complete. I did many "Force Close" before deciding I had the time 
to try "Wait"

Original comment by dhloc...@gmail.com on 10 Apr 2012 at 1:09

GoogleCodeExporter commented 9 years ago 
My Tracks 1.1.16 on ICS 4.0.3 Samsung Galaxy S2. While recording a long track 
of more than eight hours when i tried to stop recording then the app came out 
with a black screen, after that it didn't respond at all. I killed the app with 
the task manager but when i tried to start it then again the same black screen 
and app hung. I had to uninstall the app and install it again (what of course 
delete all the data) and then the app works fine again, but i've lost all the 
tracks previously recorded. The data size before the crash was about 26.5Mb, my 
phone has 16Gb USB Storage, 2Gb Memory and a 32Gb SD Card so how could get it 
out of free space? as others argue. Please fix this problem soon because it's a 
great app but if it fails this way in long recordings is useless. Thank you 
very much.

Original comment by alfredo....@gmail.com on 16 Apr 2012 at 11:33

GoogleCodeExporter commented 9 years ago 
The workaround for this does seem to be to run My Tracks and just leave it 
running for a long time (e.g. overnight) with the power connected. Select 
"Wait" if you get the force close message.

I also observed the "skip_rows row NNNNN" message in the logs as shown in 
previous comments. Essentially you have to wait until this has counted down to 
zero before the application will continue as normal.

In my case, after leaving it running overnight, it then came back as normal, 
still recording the track that it was when it originally lost power mid-record.

Original comment by m...@codesimple.net on 11 May 2012 at 9:25

GoogleCodeExporter commented 9 years ago 
sorry ... myTracks is more or less useless:
Day one -> myTracks and Copilot (Navi) 160km o.k. ... out of memory ... corrupt 
myTracks-data -> delete all data
Day two -> myTracks 180km o.k. ... empty battery ... corrupt myTracks-data -> 
delete all data
Day three -> o.k. 150km
Day four -> myTracks 120km o.k. ... myTracks crash ... corrupt myTracks-data -> 
delete all data

myTracks is only usable for short time/distance rides and very unreliable.

Original comment by herrmann...@googlemail.com on 30 May 2012 at 10:49

GoogleCodeExporter commented 9 years ago 
I had this blocked start of this app as well. I hoped to regain access to all 
my tracks allowing an update to occur. Unfortunately this seemed to have 
deleted all tracks by emptying those .db as described by tomfel...@gmail.com in 
the first post in here. Am I right in concluding all tracks not being exported 
are to be lost?

I mean it could be any user's idea to try an update in case this magnificient 
app ever again seems to hang. Is there a slight chance I could get any of those 
tracks back?

Original comment by bruno.vo...@gmail.com on 14 Jun 2012 at 5:06

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
There seems to be several related issues.
1. database corruption
2. out of space
3. hangs after reboot
4. unable to record very long tracks

In My Tracks 2.0.2, we added transaction support when updating the database, 
which should reduce database corruption.

In My Tracks 2.0.2, we also improved the code to resume a track after phone 
reboot.

Going to close this bug for now. But please do reopen if it is happens with My 
Tracks 2.0.2 or higher.

Thanks

Original comment by jshih@google.com on 10 Nov 2012 at 9:11