search

darodriguezalv / mytracks

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

Google Maps Dynamic Track Color not working #1198

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Select Map Settings -> Track Color -> Dynamic Thresholds -> 25%
2. View Stats for track (avg. 41.85 mph)
3. View Track on Map (track is constant 'red' unless stopped 'green')
4. Select Map Settings -> Track Color -> Fixed Thresholds
5. Set static thresholds to 31 (low [25% under 41.85]) and 52 (med [25% over 
41.85])
6 View Track on Map (track now shows colored segments)

What is the expected output? What do you see instead?
Expected to see multiple colored segments on track depending on over/under avg. 
speed by percentage.
Saw single colored track (red) unless speed was very low relative to avg (e.g., 
10mph) which showed 'slow' (green) segment

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

MyTracks 2.0.3
Nexus 7 running Android 4.2.1 (JOP40D)

Please provide any additional information here:

Original issue reported on code.google.com by basile.m...@gmail.com on 6 Dec 2012 at 5:23

GoogleCodeExporter commented 9 years ago 
Is it possible for you to share this track with us?

Save to external storage -> Save as GPX -> Share track file -> Email a copy to 
yourself and attach it here.

Thanks
Jimmy

Original comment by jshih@google.com on 6 Dec 2012 at 6:23

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Here's the full track. I've also checked with past saved tracks (pre-upgrade) 
and am seeing the same behavior

Original comment by basile.m...@gmail.com on 6 Dec 2012 at 7:22

Attachments:

GoogleCodeExporter commented 9 years ago 
It should be a bug,  I can also reproduce it on  my Galaxy Note.

Original comment by youtaol@google.com on 10 Dec 2012 at 10:27

GoogleCodeExporter commented 9 years ago

Original comment by jshih@google.com on 10 Dec 2012 at 5:49

GoogleCodeExporter commented 9 years ago 
Will be fixed in next release.

Original comment by youtaol@google.com on 11 Dec 2012 at 9:40