anongit / mytracks

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

does not complete the track when screen blanker active #217

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. start a track, lock the screen
2. move to another place
3. unlock device and press "current position"
4. lock the device and move to another place
5. unlock the device and stop recording

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

I expect to see the complete track in drown red on the screen, but I only see 
the first part: from the start untile when I stopped recording.

I see the track ends approximately where I checked che current position.

What version of MyTracks are you using? On what version of Android? On what
phone?

MyTracks 1.0.19
Android 2.1
SAMSUNG Galaxy S

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:

I found quite strange that when I completed my running, I could press "stop 
recording" (i.e., the device was still recording) but the red line was not up 
to my current position. Please note that I was rather quick in unlocking the 
screen and stopping recording.

Current statistics about this track report 48 minutes total but only 38 in 
movement. This is false since I was running all the time. The total length I 
was running is not correct since it only count the first part (the same part 
that is also displayed on screen). Max speed is incredibly high: the average is 
about 10km/h and I was running all the time at the same speed, but max speed 
reported is 36km/h.

Please note that I never stopped the application. I only locked the screen in 
order to keep the device in a bag.

If you need the recorded file, I can attach it to this report. Just let me know 
what format is preferred.

Original issue reported on code.google.com by eppesuig@gmail.com on 15 Nov 2010 at 11:03

GoogleCodeExporter commented 9 years ago
Today I used again MyTracks during a brief running.  The device was locked from 
the start of my running.  At halfway, I stopped my run and had a look at the 
application. I found that my position on the map was correct but the red line 
was not complete.  I waited about 30 seconds and the red line joined to my 
current position.  I started running again and when I arrived to a second point 
the phone was not keeping up.
I found that running up to 7km/h the phone is drowing the line correctly, while 
running faster require that when arriving at the end, I have to wait for the 
phone to slowly complete the track.

Do, my question is: did I bought a slow device? what are the requirement for 
MyTracks?  Would upgrading to Android 2.2 solve this problem?

Thanks,
Giuseppe

Original comment by eppesuig@gmail.com on 17 Nov 2010 at 10:35

GoogleCodeExporter commented 9 years ago
Hi,

Good news is that your phone is perfectly fine.  There was a bug that has been 
recently fixed and the fix will be included in upcoming version, 1.0.20.

To make the long story short, there used to be a lock contention inside the map 
overlay's draw() method.

Thanks for reporting this issue!

Original comment by ba...@google.com on 18 Nov 2010 at 7:17