Closed GoogleCodeExporter closed 9 years ago
Wondering if you can export the track as csv.
Save as CSV, email the CSV file to yourself. Either attach the file here or you
can email it to me directly.
Thanks
Jimmy
Original comment by jshih@google.com
on 6 Mar 2013 at 10:42
This one of my last bike tracks, my bike computer showed a matching distance
and a move time of 1:08:16
Let me know if you need anything else
Brad
Original comment by brad.gia...@gmail.com
on 6 Mar 2013 at 11:18
Attachments:
I recorded a track & noted the distance, stop & restart times (see My
Tracks.xls). I have also attached the csv of the My Tracks file.
Phone: HTC oneX
Android Version: 4.1.1
Software Number: 3.18.401.1
My Tracks Version: 2.0.3
Great App, just needs this little bug fixed
Cheers
Bill Campbell.
Original comment by bcampbel...@gmail.com
on 17 Mar 2013 at 11:39
Attachments:
I'm having similar issues (Motorola Droid Bionic, Android up to date). MyTracks
settings have been all defaults. I go on bike rides and on the stats page the
total distance looks right, but total time and moving time are almost the same,
which is way off on a 50+ mile ride. Moving time should be much less. My Cateye
wheel-sensor computer gives much better moving speed numbers, and almost
exactly the same distance numbers, as MyTracks.
Original comment by revifr...@gmail.com
on 12 Apr 2013 at 8:33
This seems to be happening to me as well, on a Motorola Droid Razr with Android
4.1.2 and MyTracks 2.0.4, recording bicycle rides. My CatEye Velo 7 gives a
more accurate moving time, and almost the same distance as My Tracks, resulting
in a better moving average speed on the cyclocomputer than on the app. On the
app, the total time and moving time are only a few minutes apart, when I know I
have stopped for longer than that at lights and rest stops.
Original comment by PSNancar...@gmail.com
on 19 Apr 2013 at 6:33
Followup: This problem first appeared when MyTracks was updated to allow
pausing the recording of tracks. Prior to this update, Total Time and Moving
Time were properly differentiated. With the Pause feature added, iI is as if
the app no longer bothers to pause itself when I stop moving.
Original comment by PSNancar...@gmail.com
on 26 Apr 2013 at 12:20
I too have noticed that the moving time is not accurate. The other day when
waiting for over 20 minutes for someone I decided to test the issue. It seems
that when I start moving, even a few meters, the moving time jumped up to the
current total time minus a few seconds. To be specific, I stopped moving at
1m50s, I stayed still for about 3 minutes and moved until the moving time
changed. It changed to 10 seconds shorter than the total time of about 4m40s. I
kept testing this for the full 20 minutes and it always did the same thing,
jumping to the total time minus a small amount of time.
Original comment by Renae.Ma...@gmail.com
on 8 May 2013 at 7:00
Thought I would comment again to regain the developers attention.
We now have several people with different devices complaining about this.
i was really hoping comment #6 would give someone an ah ha moment.
Please MyTracks is one of my favorite apps but this bug is killing it for me ...
Original comment by brad.gia...@gmail.com
on 21 Jun 2013 at 2:03
Does anybody could upload a gpx or kml file with such issue? Thanks ahead!
Original comment by youtaol@google.com
on 21 Jun 2013 at 8:03
This track is from a bike ride where my bike computer showed 30.82 miles in
1:48:55 while my tracks shows moving of 2:00:11 and total 2:01:19
I can definitely make you a shorter one but really just walk down the street
with my tracks running stop for a minute then watch the stats as you start
moving
Original comment by brad.gia...@gmail.com
on 21 Jun 2013 at 2:44
Attachments:
Here is a track from a ride I took yesterday. My cyclocomputer says my moving
time was 3:48:31. The MyTracks app says I was moving for 4:24:23. That's a big,
inaccurate difference!
Original comment by PSNancar...@gmail.com
on 22 Jun 2013 at 4:47
Attachments:
Thanks for your uploads, we are looking into this issue.
Original comment by youtaol@google.com
on 24 Jun 2013 at 2:58
As the devs look at some KML files to try to identify the problem with moving
time, I just noticed another strange issue.
I am running My Tracks on two devices: a Moto Droid Razr and a Moto Xoom. I
exported a track to a KML file from the Razr, uploaded it to my Google Drive,
and then synced it from Google Drive to My Tracks on the Xoom. Somehow in that
process the stats were changed. The Xoom-via-KML version had a much better
Moving Time count (although the Max Speed stat went way out of the realm of
possibility). Here are the stats from the same ride, as shown on different
devices:
Moto Droid Razr:
Distance: 24.55 mi
Total time: 1:51:00
Moving time: 1:50:55
Avg speed: 13.27 mi/h
Avg moving speed: 13.28 mi/h
Max speed: 39.93 mi/h
Moto Xoom:
Distance: 24.55 mi
Total time: 1:50:57
Moving time: 1:41:00
Avg speed: 13.28 mi/h
Avg moving speed: 14.58 mi/h
Max speed: 53.44 mi/h
What in the world could make the stats from the same track so very different
when synced through a KML file??
I've attached the KML file itself, in case that's some help.
Original comment by PSNancar...@gmail.com
on 24 Jun 2013 at 5:32
Attachments:
So a friend just pointed out if he exported to GPX or TCX and uploaded to
Garmin Connect then the moving time is spot on.
So to go along with the gpx/kml I posted above
http://connect.garmin.com/activity/332738455
Take a look at the Moving Time stat.
So it would seem the data is gathered properly but the display in stats, voice
prompt and upload to google spreadsheet are using the wrong value.
Original comment by brad.gia...@gmail.com
on 24 Jun 2013 at 6:21
Good observation. I notice on the Garmin site it reports a max speed of 49.3
mph. Is that higher than your actual speed for that ride? The My Tracks rides
I've run through KML show better moving times and avg speeds, but crazy fast
max speeds. I'd love to top out at 58.83 mph on my rides! – but I know I'm
not that fast and will never be. The original track, before I upload it as KML,
shows a pretty accurate max speed but bad moving time and avg speed. I wonder
where that tradeoff is happening...
Original comment by PSNancar...@gmail.com
on 24 Jun 2013 at 6:48
The max was about 29 for that ride, and that jives with the stats in my tracks
but once I send it to garmin it goes crazy
Original comment by brad.gia...@gmail.com
on 24 Jun 2013 at 8:06
[deleted comment]
[deleted comment]
I can copy this. Also it would make sense to get some kind of "stop/start"
function to the SensorManager for speed sensors (cycling). Those sensor tend to
know when the bike is really stopped more accurately than the GPS. Also if I
cycle for like 80Km and take a brake at the 40Km to have a coffee it will
record my walking on the brake etc, which are really tend to mess up the whole
average speed etc.
In contrast if my speed sensor would be able to tell the SensorManager that
.bikeStopped(), bikeResumed() I would probably get more accurate data.
Currently I'm planning to pause the whole recording but it tends to saturate
the whole time statistics.
Just my two cents :)
Original comment by sopsa...@gmail.com
on 5 Aug 2013 at 7:36
I vote for that!
Original comment by revifr...@gmail.com
on 5 Aug 2013 at 7:39
We have improved on the moving time calculation in version 2.0.5. If there are
still issues with moving time, please file a new bug.
Original comment by jshih@google.com
on 12 Aug 2013 at 6:50
[deleted comment]
Thanks for looking into it.
Went on a long ride this morning and the moving time was still a few minutes
off, I'll try and get a few more tracks in to see if I can discern a pattern.
Original comment by brad.gia...@gmail.com
on 13 Aug 2013 at 1:14
Original issue reported on code.google.com by
brad.gia...@gmail.com
on 7 Feb 2013 at 2:03