Closed GoogleCodeExporter closed 9 years ago
This seems to be related to bug #1443.
Original comment by tda...@gmail.com
on 1 Feb 2014 at 12:48
Similar if not the same issue here.
I use Nexus 4 KitKat 4.4.2.
Latest version of the app:
1) Moving time graph is completely messed up, as in there is no real data in
it. It shows as if it is randomly generated each time.
2) Average moving speed for walking appears as 40-50 km/h everytime. This is
obviously impossible.
3) Elevation data is also choppy and unreliable.
Also, as a side note, since the last update the direction of moving according
to the compass is always wrong, so it could be that the app cannot cope with
the wrong compass direction.
Original comment by kgiz...@gmail.com
on 27 Feb 2014 at 8:37
I'm having a related issue. Whenever I take a bike ride, I find that my moving
time and total time are always the same (or are the same to within a few
seconds), even though I know I've stopped at a bunch of stoplights and also
taken a 15-min break during the ride. (e.g., on a typical 40-mile ride, my
cycle computer will give 2:25 min riding time, whereas MyTracks is giving close
to 3 hours, that is, the total time). The distance recorded by MyTracks is
spot on with my cycle computer (and agrees within 0.2 miles out of 40 compared
to tracing the route out on GoogleMaps). Elevation data also is appropriate
(although it puts me 150 ft below sea level when riding along the Pacific Coast
Hwy, but the relative elevation profile and integrated climbing look good).
Avg moving speed is way too low because the software clearly is diving the
distance by what it thinks is the moving time. If I use MyTracks while
walking, I also get a similar issue with there being no difference between
moving and total time.
I'm currently using a Nexus 5 with KitKat 4.4.2, and running MyTracks 2.0.6. I
only recently upgrade from a Nexus One running an older version of MyTracks,
and never had this problem, so it makes sense to me that this is a software bug
since the hardware in the Nexus 5 otherwise seems to perform much better than
the Nexus One. I'd be happy to post a GPX file from one of my rides if it
would help (there are clearly places in the speed profile where the speed drops
to zero at stop lights or break points, but nothing is taken off the moving
time).
Original comment by Benjamin...@gmail.com
on 17 Mar 2014 at 7:08
Original comment by jshih@google.com
on 2 Apr 2014 at 12:52
... my moving time and total time are always the same ...
I have the same problem.
I noticed that when I stop -
The "Moving Time" stops - as it should
But as soon as I move
The "Moving Time" becomes the "Total Time"
Original comment by oridani...@gmail.com
on 31 Aug 2014 at 8:08
Hi guys,
I just wanted to let you know that I resolved my problems by upgrading to
Google Play services v5.
Currently on Android 4.4.4 with Play Services 5.0.89(1307510-038), there are no
issues with MyTracks, Maps or overall performance of the GPS.
If you did not get the update automatically, you can upgrade by manually
downloading the latest version of the app from here -
https://play.google.com/store/apps/details?id=com.google.android.gms&hl=en_GB
or alternative source.
I believe this issue can be labelled as resolved.
Original comment by kgiz...@gmail.com
on 2 Sep 2014 at 1:48
Original issue reported on code.google.com by
doile...@gmail.com
on 27 Jan 2014 at 3:29Attachments: