MyTracks stats seem wrong, distance much longer than it should

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Set units to imperial
2. Walk 2.5 miles on streets
3.

What is the expected output? What do you see instead?
Stats should show 2.5 miles (as measured through google maps on computer) but 
show instead 4.12 miles walked. 4.12 would actually be the correct distance in 
km (~2.5m x 1.6 = 4km)

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

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:
It looks as if MyTracks reports the distance in km as being the distance in 
miles, with consequent over-inflated distances and speeds.

Original issue reported on code.google.com by medeis.n...@gmail.com on 15 Dec 2012 at 11:11

[GoogleCodeExporter]

What is the number of miles when you change the unit back to metric?

Original comment by youtaol@google.com on 18 Dec 2012 at 7:51

[GoogleCodeExporter]

Hello, thank you for the reply.
Going to metrics reports the distance as ~6.5Km, reverting to imperial brings 
it back to 4mi.
I forgot to mention, the phone is a Nexus 4 16GB.
I don't know if it's related, and whether it's a bug or not, but in GMaps, the 
distances are reported in miles, but the location accuracy is in meters..

Original comment by medeis.n...@gmail.com on 18 Dec 2012 at 10:48

[GoogleCodeExporter]

I'm also running my tracks v2.03 on android 4.2.1, and I'm seeing a similar 
issue.  My stats are worse than imperial vs. metric confusion - after walking 
just over 5 miles, the stats say I've covered over 28 miles; that my average 
speed is over 9mph, while my maximum speed was just 8 mph!  I tried to upload a 
screen shot but no luck from my phone...

Original comment by BrianMe...@gmail.com on 5 Jan 2013 at 11:30

[GoogleCodeExporter]

I don't think the problem is with the unit conversion.

Can you export your track as kml and use Google Earth to see how long the track 
is? ?

You can also attach the kml file in question in the bug report.

Original comment by jshih@google.com on 27 Feb 2013 at 9:51

[GoogleCodeExporter]

Original comment by jshih@google.com on 27 Feb 2013 at 9:57

• Changed title: MyTracks stats seem wrong, distance much longer than it should

[GoogleCodeExporter]

If someone is also seeing similar issue, wondering if you can either attach the 
gpx file or email it to me.

Menu -> Save to external storage -> Save as GPX, on the result page, click 
share file and email yourself a copy.

Thanks
Jimmy

Original comment by jshih@google.com on 6 Mar 2013 at 11:10

[GoogleCodeExporter]

Jimmy, I missed your comment last month, but noticed the notification today.  I 
emailed the gpx file of the track with the most extreme inaccuracies to you.  

It seems that more recent tracks at more accurate...  

You should know that I'm using an old Samsung Galaxy S Fascinate (Verizon) that 
miraculously is getting nightly builds of cyanogen mod 10.1 (jellybean 4.2.2).  

Also, during these track recordings, I'm typically walking and listening to 
prerecorded streaming audio via the NPR news
App.  So, it's likely that the device is periodically cpu-bound 

Original comment by BrianMe...@gmail.com on 7 Mar 2013 at 6:54

[GoogleCodeExporter]

For the file you shared with me, when I imported it to My Tracks, the distance 
is only 9.27 km, compared to 28.3km. This track was recorded back in January.

Glad to hear it is happening less frequent. Can you let me know if the distance 
still seems wrong in My Tracks 2.0.4.

Original comment by jshih@google.com on 12 Jun 2013 at 10:39

[GoogleCodeExporter]

Issue 1248 has been merged into this issue.

Original comment by jshih@google.com on 12 Jun 2013 at 11:13

[GoogleCodeExporter]

Hi Jimmy,

My trusty old Samsung fascinate was dropped along the trail and the screen 
cracked... while recording a track as a matter of fact.  I seem to recall the 
track was accurate.

I'm now using a GSIII, and use MyTracks all the time.  I've never noticed this 
issue.

Thanks!

Original comment by BrianMe...@gmail.com on 13 Jun 2013 at 2:41

[GoogleCodeExporter]

I have the same issue on my Acer Liquid E 2 with stock 4.2.1. If I record a 
track, a too high total distance is displayed.
Another error I noticed is when I switch between statistics and diagram. The 
traveled distance in the diagram grows. If I turn five times back and forth it 
grows from 1.5 to more than 25 km.

Original comment by gerhardw...@gmail.com on 13 Jun 2013 at 7:51

Attachments:

• myTracks-fehler.jpg

[GoogleCodeExporter]

Hi, I've seen this happen when GPS signal quality is between good and bad. 
Often the device will briefly get a great GPS signal and then lose it, which 
causes the blue dot to move around hundreds of feet in a matter of seconds. The 
"recommended" accuracy for plotting a waypoint is 656ft. I think everyone can 
agree, 656ft is not accurate. I personally set mine to 65ft and that seems to 
take care of the "jumping around" that is often caused by poor GPS reception. I 
have tested & confirmed this on Nexus 7, 4, S, & Galaxy.
Perhaps the GPS accuracy setting needs to default at a lower level to 
accommodate accuracy instead of whatever 656ft is supposed to accommodate.

Original comment by apn...@gmail.com on 2 Jul 2013 at 7:33

[GoogleCodeExporter]

Based on GPS error measurements, we are planning to change the "GPS accuracy" 
default value from 200m (656ft) to 50m (164ft).

Wondering if a few users can confirm independently that changing 
Settings->Recording->GPS accuracy to 50m (164 ft) fixes the distance issue.

Thanks
Jimmy

Original comment by jshih@google.com on 2 Jul 2013 at 8:55

[GoogleCodeExporter]

On next release, the default gpx accurarcy will be 50m or 164 ft.

Original comment by jshih@google.com on 12 Jul 2013 at 11:50

• Changed state: Fixed

[GoogleCodeExporter]

I just bought a samsung 4s and my tracks consistently measures short. 4 mile 
walk now measures from 3.4 to 3.7 miles. Same distance. I live in a rural area 
so tried changing the gps accuracy to a higher number. No change. My tracks 
worked on my old phone just fine

Original comment by mrutte...@gmail.com on 17 Sep 2013 at 3:04

[GoogleCodeExporter]

I have the same problem on my zopo 4.2.1 . walk 30 minutes about 3.2 km at 5.5 
km/h . software show 58.82 KM speed 107 km/h ???

Original comment by apsr...@gmail.com on 2 Dec 2013 at 6:16

[GoogleCodeExporter]

It looks like an 4.2.1 problem. i walked about 8 km and mytracks shows 121 km.
Before I used a htc desire android 2.3. No problem at all.
Now I own a aldi phone with android 4.2.1. No accuracy at all. On the PC it is 
right though.
I will attach the screenshot.

Original comment by nagtegaa...@gmail.com on 7 Dec 2013 at 1:51

Attachments:

• Screenshot_2013-12-07-14-34-21.png

[GoogleCodeExporter]

facing the same issue as others. I am getting similar problem on Strava GPS. My 
Phone is Zen Ultrafone 701 HD, with Android 4.2.1 version.

Original comment by pinak...@gmail.com on 18 Dec 2013 at 5:57

[GoogleCodeExporter]

As an added note, I do have 4 Android devices, and they are showing different 
distance from the same recorded and synced track. I think software in the 
firmware/OS of the device is used to calculate distance, not the program itself.

For example, my HTC Desire S, Nexus7 (2012) and Samsung GalaxyTab2 10.1 (P5110) 
say the track is  about 17.3 km, but my  ALDI AT-AS45qHD phone reports 289.1km 
for the same track, recorded on the nexus7 and synced with Google Drive. so 
this has nothing to do with GPS-accuracy, only something wrong with calculation.

Original comment by broome...@gmail.com on 31 Jan 2014 at 9:16

[GoogleCodeExporter]

Same issue here, with a mytracks version 2.0.6, Android V4.1.2, Kernel 3.4.5. 
The track is correctly represented on the map, but the statistics tab displays 
distance values about a factor of 10 too large (I'm using metric units).

Original comment by gtreutw...@gmail.com on 27 Feb 2014 at 9:48

[GoogleCodeExporter]

Exported the gpx to runtastic which creates statistics correctly. 
How can we fix this app? 

Original comment by gabriele...@gmail.com on 3 May 2014 at 8:20

[GoogleCodeExporter]

I have an Huawei G700 with Android 4.2.1. and I also have this problem. For 
example, yesterday I walked about 8km and it recorded about 100 km. When I 
export it to Google My Maps and look at my maps on a desktop, I see the correct 
distance.

This problem has the status fixed, but how to implement the fix on my device?

Original comment by Gunter.T...@gmail.com on 27 Oct 2014 at 12:53

[GoogleCodeExporter]

I have ZOPO C2 same problem no fix.

change to RUNTASTIC works ok

Original comment by apsr...@gmail.com on 27 Oct 2014 at 1:47

[GoogleCodeExporter]

If you nave a mediatek CPU see if this solves the problem 
http://forum.xda-developers.com/showthread.php?t=2431933

Original comment by gabriele...@gmail.com on 28 Oct 2014 at 9:45