-
@sartoric Hmm so it was bad values during the activity right?
If you had – that should not SA problem -
@Dimitrios-Kanellopoulos said in Activity - Navigation : "frozen" altimetric profile:
@sartoric Hmm so it was bad values during the activity right?
If you had – that should not SA problemWhat do you mean for bad values ?
-
@sartoric the –
-
@sartoric sorry
-
@Dimitrios-Kanellopoulos
Well, in fact the watch wasn’t able to evaluate ETA/ETE, but it worked using the 1st route and route view was tracking me correctly even if gps was some meters off (had the same problem on my previous activity).
The altimeter was a bit off too (1st time, never had issue before) something around 80 meters.1st route is a gpx import
2nd route was made on the fly on the peak with SA -
@sartoric hmm. Was the route on the fly aka I synced it while on exercise?
-
@Dimitrios-Kanellopoulos
Yep, sync when activity was pause -
@sartoric
1 additional note
I’ve just seen that after I synced the activity all the 3 routes I had on the watch were removed, but in the app I can see the toggle “on”.
Nor Auto-sync or manual sync sent the routes back to the watch -
@sartoric thanks for this info. I have to ask about his. I mark this thread as unread and reply once I gather more info. Add anything you like here
-
-
@Dimitrios-Kanellopoulos @sartoric I tested this yesterday and faithfully replicated this issue. If switching from one route to another the altitude profile locks out and does not change even though the route screen has switched and is working correctly. A fix to this is instead of route to route, if one switches from route to breadcrumb (short time) then to the new route all works as it should. Thought I would let you both know.
-
@Brad_Olwin thanks for validating this! Great.
-
@Brad_Olwin did you sync the route while on one activity (recording) or you had already those 2 routes you switched between already synced to the watch?
-
@Brad_Olwin said in Activity - Navigation : "frozen" altimetric profile:
@Dimitrios-Kanellopoulos @sartoric A fix to this is instead of route to route, if one switches from route to breadcrumb (short time) then to the new route all works as it should. Thought I would let you both know.
Good to know. I usually notice this after a while and I never stop to try some workaround.
-
Hey,
I have also the issue… each time i switch route to another, the graph is updated, but my position is stuck at the end of the graph… I will try the solution mentioned by @Brad_Olwin.
One other things, it could be nice to have zoom and automatic zoom on the altimeter profile view like in track screen.
@++
-
@Brad_Olwin Wow! I experienced this issue two times. I thought it was an issue with the .gpx or something in an specific zone because it happened at the same mountain. I was going down from the top to my car but the altitude graph got stuck in the top of the mountain but I was able to follow the path to my car. Two times happened this to me at the same mountain. And now that you mention it, both times I swithced the route in the middle of the move… so It seem sthe same. Thanks for the trick to fix it on the move.
-
Hi there,
I confirm, @Brad_Olwin solution works fine
Thanks -
@Dimitrios-Kanellopoulos
I guess there’s something we never found before about this issue. So, maybe it’s something new/recent.Today, I started a new trekking activity navigating a route already on watch and selected before starting. At a certain point I’ve seen that the graph was frozen. What a mystery!
While on the summit I decided to switch to a brand new route, so i created it, transferred it to the watch, did the BC trick and resumed the activity.
The graph was working as expected, but when my pal wanted to extend a bit the trip, we took a detour and at that point I’ve got the usual “off route” message and after a bit I’ve noticed that the graph froze.So I reminded that at the beginning we took a shortcut so we went “off route” for a while.
My suspicion is that, if we stay for some time “off route” the altitude graph get stuck even if we go back on track.
The BC trick obviously works
