Serious problems with navigation with GPX routes
-
@martintrail It’s possible that these are similar cases. I usually don’t have time to mess around with changing screens and viewing data on the watch screen during activity. Today, for testing, I started looking at it more closely and changing screens, map zooms and I’ve observed a lot of these types of breadcrumb errors. I usually rarely see this.
-
For the second, if the watch is syncing to the app and the routes have not synced, you need to wait until syncing is stopped then unsync routes.
It seems to me that for a few weeks or months now it works differently and often a previously marked route (Use in watch) after unmarking after a few/dozen seconds marks itself again. I did a test synchronization, waited a minute after the synchronization was finished, unmarked the route and after a while it marked itself again. Fortunately, it is not a serious problem.
For the third, Suunto supports changing a route but the route must be already on the phone. You cannot plan a route on the phone but you can add a planned route to the watch, load and follow the route. There may be something wrong with your route.
This probably explains the behavior. It seemed to me that the newly created routes were technically the same as the existing routes in SuuntoApp before the activity started.
So, no bugs here are these are working for most everyone and certainly me. I agree that route syncing could be more robust but the watch can only sync so many things at once.
Unfortunately, the most serious bug remains - crazy breadcrumbs and freezing of the current location display on the map.
-
@maszop And these routes that cannot be deleted - are they created in SuuntoApp or some other place like Strava or komoot? I had a similar case in the past with a route from Strava and it kept reappearing until I removed it in Strava
-
@kriskus Mostly from Komoot, but it seems to me that the problem also affected several created in SuuntoApp.
I used to have this problem with Strava routes, but now it’s probably something with synchronization because it can be deleted eventually, but it requires many attempts. I’ll keep looking at it. -
I have not seen any of this behavior aside from one time at least a year ago when my location got stuck on an out and back route. Granted I have not used map routes for a few months - but I will give it a test in the next few days.
-
@maszop which battery mode are you using?
-
@Egika Custom: GPS - best, Touch - disabled, Display timeout - off.
Basically all like a Performance mode but with touchscreen disabled.Other options
Custom mode hiking.
Ruler: disabled.
SuuntoPlus (yesterday’s setup): Last km/mile, Weather Insights,
OHR.
-
I’ve done some more tests recently.
It’s possible to add a completely newly designed or imported to SuuntoApp route to the watch during an activity. It doesn’t have to be saved in SuuntoApp beforehand. There are some problems with synchronization during an activity, but it works eventually.
However, there’s a rather annoying bug when changing the route during an activity. During an ascent or descent, you can’t change it on the fly - there’s some conflict with Climb Guidance (black screen with X symbol on the watch). To get around this, you have to completely disable the current route (Breadcrumb option) and only then load a new route.
I hope this gets fixed because I usually don’t have time to mess around in the field with such non-intuitive route changes.
-
@maszop Several months have passed, and of course, nothing has changed. The problems remain.
It’s still impossible to change the route during ascent or descent.
And there are still serious problems with breadcrumb display.
-
@maszop I have the same problem on my Vertical.
-
M maszop referenced this topic on
-
The problem still occurs with the latest software version.
-
The only situation I have had issue was last summer when I had tried to modify the current route I was navigating on.
That made my SV crash.
Only happened once, since then I never tried again. But absolutely no issue to create/sending a new route to the watch while already recording and navigating, and then change the route.
I did it yesterday while walking with my SRs, I had prepared two routes, one with waypoints and the other one without, to test new climb behaviour. I have changed maybe 10 times from one route to the other without any issue -
I also have no issues changing routes mid activity. Or editing and then reloading. Not that that helps.
-
@Tieutieu I just checked to be sure.
It doesn’t work during ascent/descent (red/green) – you have to select the “Breadcrumb” option first and then load a different route (with the same ascent/descent). Directly changing the route in these conditions doesn’t work.
-
@maszop ok I’ll check if I have the same behaviour
-
@maszop said in Serious problems with navigation with GPX routes:
The next problem is some strange things when managing routes in SuuntoApp. When deleting (unchecking) a route from the watch in SuuntoApp, it automatically restores itself during synchronization. Deleting routes from the watch requires multiple attempts in SuuntoApp, and sometimes it is even impossible.
I see this issue regularly. It is very difficult to unselect or delete a route. As @maszop said, it gets selected back right away. Deleting routes just doesn’t work sometimes - I delete a route but it doesn’t get deleted. Then I often end up in a situation where a route that I’ve just planned is not on the watch because it still has old routes that I no longer need and exceeds the 10 route limit. I always have to double check that a new route has been synced to the watch by starting a new activity and checking that the route is on the watch because that isn’t guaranteed at all.
For context, I run Suunto App on 3 devices (Android phone, Android tablet, and iOS app running on MacBook Pro computer) and sync with 2 watches, but only one device is actually paired with the watch.
-
@sky-runner I think the problem is having two (or more) Suunto Apps on two different devices – even when only one is connected to the watch.
-
@maszop That is quite possible. But that also means that Suunto hasn’t designed their synchronization protocol well. These problems are easily solvable - I can tell you that as someone who long time ago has worked on synchronization of bookmarks in Chrome browser between multiple devices and made that work reliably.
Also, to make to make it clear, only the app on my phone ever synchronizes data with watches, and only with one watch at a time. The other two apps are not connected. So this is not a concurrency issue.
