Very often does not record track on Android 2.2.1 on LG Optimus V

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start MyTracks
2. Press record button
3. run

What is the expected output?
I expect it to record a track.

What do you see instead?
Instead nothing is recorded. Stats show (for example) total time: 00:02, min 
elevation same as max elevation, all other values are 0.

I did turn on GPS before recording.

This happens pretty often, about 50% of times. This did not happen with 
previous versions. MyTracks is generally unstable on my phone though, and 
crashes frequently.

What version of MyTracks are you using?
2.0.2
On what version of Android?
2.2.1
On what phone?
LG Optimus V

If possible please provide a log by uploading here.
Detailed instructions can be found here:
http://code.google.com/p/mytracks/wiki/HowToReportErrors

Please provide any additional information here:

Original issue reported on code.google.com by oku...@gmail.com on 20 Oct 2012 at 5:06

[GoogleCodeExporter]

Some questions:

In the map view, do you see the orange warning message? Does it say waiting for 
GPS or waiting for a better signal?

In your system notification bar, the bar above the application title, is there 
a gps icon when you press the record button in My Tracks? Does the icon say gps 
is available or searching for gps?

Original comment by jshih@google.com on 2 Nov 2012 at 8:10

[GoogleCodeExporter]

I am not sure if the orange warning message is always there when this happens. 
I am currently in a building and have bad GPS reception, so I tested this again:
- start GPS (in MyTracks)
- wait until the GPS symbol in the status bar is not blinking any more
- press record button

I see the orange message after a while. So it's entirely possible that the 
message was popping up when I already stuffed the phone back in my pocket. I 
don't look at it all the time, otherwise I might face plant when running. 
However, when I use it for tracking, I am outside, and usually with good GPS 
reception.

In the system notification bar, under 'Ongoing'/'My Tracks', I see 'Recording 
your track'.

I can test this again when I am outside.

Original comment by oku...@gmail.com on 2 Nov 2012 at 8:35

[GoogleCodeExporter]

So I tested this outside.

It's very hard to test, because it crashes frequently, and I don't know whether 
that is related. Also, the issue does not always look the same.

So once, when I started recording, I did not see the orange message. I looked 
at the 'Stats' page while walking, and although it displayed my speed, the 
distance remained the same. I recorded for 1:42 minutes while walking, the 
distance stayed at 0. Min elevation is the same as max elevation (164.04), and 
although the trail was about level, I would expect some noise.

Another time I pressed the record button, and the application seemed to have 
crashed (the dialog to send a report popped up), but it was recording a track 
anyway, including voice announcements (which surprised me, because actually I 
had given up). But that doesn't always work that way, and it records nothing at 
all, not even the time. The date then is often set to 12/31/1969 3pm.

Original comment by oku...@gmail.com on 5 Nov 2012 at 8:36

[GoogleCodeExporter]

I want to confirm whether the problem is with the phone GPS.
When you press the record button
1. Does the GPS symbol in the system status bar turn full?
2. In My Tracks, does the orange message on the map view disappear?

If the above two are true, then you should be able to record your GPS tracks.

When it crashes, can you capture the log.
http://code.google.com/p/mytracks/wiki/HowToReportErrors

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

• Changed title: Very often does not record track on Android 2.2.1 on LG Optimus V

[GoogleCodeExporter]

The symbol does get full, and I don't see the orange message.

I have reset the settings to factory defaults, and the problem seems to happen 
a lot less often now, but it recently happened again. I observed that it 
displayed the speed but did not increase the distance.

Sorry for not capturing the log _ I will do that next time.

Original comment by oku...@gmail.com on 27 Nov 2012 at 1:47

[GoogleCodeExporter]

Attached are two log files.

Original comment by oku...@gmail.com on 27 Nov 2012 at 6:50

Attachments:

• android1.log
• android2.log

[GoogleCodeExporter]

In both logs, the error is:

android.view.ViewRoot$CalledFromWrongThreadException: Only the original thread 
that created a view hierarchy can touch its views.

This has been fixed in 2.0.4.

Thanks for reporting this.
Jimmy

Original comment by jshih@google.com on 12 Jun 2013 at 7:00

• Changed state: Fixed