Closed GoogleCodeExporter closed 9 years ago
Same problem with Samsung S4 Android 4.3, My Tracks V2.0.6. When My Tracks is
started, current elevation is shown as Elevation Gain, move a few feet and
Grade could be over 100%.
Original comment by alanfow...@gmail.com
on 30 Mar 2014 at 7:12
Issue 1460 has been merged into this issue.
Original comment by jshih@google.com
on 31 Mar 2014 at 5:25
Issue 1448 has been merged into this issue.
Original comment by jshih@google.com
on 31 Mar 2014 at 5:27
I have this problem too. If I export as a gpx file, the elevation is missing on
the first trackpoint, as you can see in the following head of a gpx file.
<?xml version="1.0" encoding="UTF-8"?>
<gpx
version="1.1"
creator="Created by Google My Tracks on Android"
xmlns="http://www.topografix.com/GPX/1/1"
xmlns:topografix="http://www.topografix.com/GPX/Private/TopoGrafix/0/1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.topografix.com/GPX/1/1
http://www.topografix.com/GPX/1/1/gpx.xsd
http://www.topografix.com/GPX/Private/TopoGrafix/0/1
http://www.topografix.com/GPX/Private/TopoGrafix/0/1/topografix.xsd">
<metadata>
<name><![CDATA[4/11 15:49]]></name>
<desc><![CDATA[]]></desc>
</metadata>
<trk>
<name><![CDATA[4/11 15:49]]></name>
<desc><![CDATA[]]></desc>
<type><![CDATA[biking]]></type>
<extensions><topografix:color>c0c0c0</topografix:color></extensions>
<trkseg>
<trkpt lat="48.123456" lon="9.123456">
<time>2014-04-11T13:49:35.051Z</time>
</trkpt>
<trkpt lat="48.123455" lon="9.123457">
<ele>314.1</ele>
<time>2014-04-11T13:50:05.423Z</time>
</trkpt>
<trkpt lat="48.123456" lon="9.123456">
<ele>313.9</ele>
<time>2014-04-11T13:50:05.875Z</time>
</trkpt>
Original comment by T.Wartz...@gmail.com
on 12 Apr 2014 at 9:31
Solution - install Runstatic Pro. Check out Amazon apps store for special deal,
I got it for free. No more problem.
Original comment by Davi...@gmail.com
on 16 Apr 2014 at 4:29
[deleted comment]
Samsung Galaxy S4.
Model SCH-1545
Android 4.3
MyTracks v2.0.6
All of my tracks have an elevation gain that is 10 times the expected when
compared to Garmins on the same route.
Most recently, on an 8 mile mtb ride between min 4600' and max 4750', MyTracks
calculated a total elevation gain of 5100'. This is vastly incorrect.
You can download the track either from Google Maps or Google Drive, whatever
format works best for you.
https://www.google.com/maps/ms?msid=203532054742808204898.0004f8bfe23eb632545c8&
msa=0
https://docs.google.com/file/d/0B57vh_xOTbKROEVqQTMxOVdsN0U
2014-05-02 Highline St Park Practice Lap (End)
Updated 17 minutes ago
Created by Google My Tracks on Android
Name: 2014-05-02 Highline St Park Practice Lap
Activity type: Mtn biking
Description: -
Total distance: 12.48 km (7.8 mi)
Total time: 1:04:11
Moving time: 1:01:00
Average speed: 11.66 km/h (7.2 mi/h)
Average moving speed: 12.27 km/h (7.6 mi/h)
Max speed: 23.80 km/h (14.8 mi/h)
Average pace: 5:09 min/km (8:17 min/mi)
Average moving pace: 4:53 min/km (7:52 min/mi)
Fastest pace: 2:31 min/km (4:03 min/mi)
Max elevation: 1449 m (4754 ft)
Min elevation: 1403 m (4603 ft)
Elevation gain: 1545 m (5068 ft)
Max grade: 64 %
Min grade: -12 %
Recorded: 5/2/2014 7:29PM
Original comment by david.ho...@gmail.com
on 6 May 2014 at 7:44
After the last update for me too badly counts increase in elevation :-(
Original comment by banys.to...@gmail.com
on 12 May 2014 at 3:28
After updating to recent version of "My Tracks" at around Feb. 2014, the
elevation gain in "Stats" screen started showing wrong elevation gain numbers.
For example, when I started recording at elevation 1500 ft and stopped the
recording at elevation 3500 ft, the elevation gain would show 3500 ft instead
of 2000 ft.
It seems like the program is ignoring the actual starting elevation and instead
uses elevation of zero for the elevation gain calculation.
Please fix the bug. It used work fine before the update.
I am using Samsung Note 2.
Original comment by hansong...@yahoo.com
on 12 May 2014 at 4:54
All, MyTracks v2.0.6 has the elevation gain bug. Until this is fixed, simply
roll back to 2.0.5 (see
https://code.google.com/p/mytracks/downloads/detail?name=MyTracks-2.0.5.rc4.apk&
can=1&q=). v2.0.5 is working well for me while awaiting fix.
Original comment by MackNa...@gmail.com
on 12 May 2014 at 4:57
Continuation from #7 above.
The track is both 15+ miles too short and has 500,000ft too much elevation gain.
There are large gaps where the route disappears.
At one point it says I rode my bike to 57,000 ft elevation. Wow. I must be
stronger than I thought. ;)
https://www.google.com/maps/ms?msid=203532054742808204898.0004f9a13782ee51c57f2&
msa=0
2014-05-17 Buff Creek (End)
Updated 2 days ago
Created by Google My Tracks on Android
Name: 2014-05-17 Buff Creek
Activity type: Mtn biking
Description: -
Total distance: 47.44 km (29.5 mi)
Total time: 6:07:21
Moving time: 4:36:43
Average speed: 7.75 km/h (4.8 mi/h)
Average moving speed: 10.28 km/h (6.4 mi/h)
Max speed: 46.94 km/h (29.2 mi/h)
Average pace: 7:45 min/km (12:28 min/mi)
Average moving pace: 5:50 min/km (9:23 min/mi)
Fastest pace: 1:17 min/km (2:03 min/mi)
Max elevation: 17342 m (56896 ft)
Min elevation: 1998 m (6554 ft)
Elevation gain: 168524 m (552900 ft)
Max grade: 199 %
Min grade: -149 %
Recorded: 5/17 8:01 AM
Original comment by david.ho...@gmail.com
on 20 May 2014 at 8:53
Attachments:
Which export file type would be most beneficial to a debugger?
Original comment by david.ho...@gmail.com
on 20 May 2014 at 8:57
Attachments:
Same problem to me!
Previous users describe it pretty much well.
Original comment by MyT...@gmail.com
on 27 May 2014 at 1:11
Issue 1518 has been merged into this issue.
Original comment by jshih@google.com
on 11 Jun 2014 at 10:13
This is fixed in version 2.0.7. In the new version, we filter out any wifi
signal (signal with altitude of zero).
Original comment by jshih@google.com
on 13 Jun 2014 at 9:57
[deleted comment]
[deleted comment]
just noticed that 2.0.7 is available on the play store.
Original comment by patrick....@gmail.com
on 18 Jun 2014 at 10:23
This problem remain in the version 2.0.7
Just test it! Will back again to 2.0.5!
Original comment by MyT...@gmail.com
on 19 Jun 2014 at 8:01
Agreed with 19 just did a ride with 2.0.7 and Chart looks correct, Min and max
elevation look correct by gain is about twice the elevation gain.
Please re-open
Original comment by volleyd...@gmail.com
on 21 Jun 2014 at 7:03
Add another user who still has this problem in the new update.
Original comment by dbonb...@gmail.com
on 21 Jun 2014 at 8:08
This problem persists in 2.0.7. If I start the program and immediately
stop it, I am given credit for 5300 feet of elevation gain (climbing).
This is equivalent to my starting elevation. The program needs to be
corrected so that it does not assume all workouts start at sea level. This
should be a simple fix.
Original comment by riptider...@gmail.com
on 21 Jun 2014 at 8:16
Exactly! The older versions to 2.0.5 was good, without this problem.
https://code.google.com/p/mytracks/downloads/list?can=1&q=&colspec=Filename+Summ
ary+Uploaded+ReleaseDate+Size+DownloadCount
Original comment by MyT...@gmail.com
on 21 Jun 2014 at 8:25
I also have been waiting for a fix to the "elevation gain" problem since it
first appeared in 2.0.6 level code. Obviously, some change made between the
2.0.5 version and the 2.0.6 version introduced this error. I have finally
given up and gone back to the 2.0.5 version which provides all the features I
need and gives me an accurate elevation gain for my hikes.
Original comment by dandjkin...@gmail.com
on 21 Jun 2014 at 8:26
I just opened a new ticket on this. Issue 1537. I dont know if this issue is
being monitoered anymore because of its status as fixed.
Original comment by dbonb...@gmail.com
on 21 Jun 2014 at 10:55
Thanks for doing that. Apparently it will be fixed in the next release:
https://code.google.com/p/mytracks/issues/detail?id=1537#c10
Original comment by ed.r.b...@gmail.com
on 12 Jul 2014 at 1:44
Original issue reported on code.google.com by
riptider...@gmail.com
on 9 Feb 2014 at 12:50