Ambit3 Peak: How to Delete Routes?
I have several routes created with Movescount (and tranfered via Suuntolink) on my watch. Now I want to delete some of them, because they take up space. Unchecking “use in watch”, and even deleting the route in Movescount, then a subsequent snyc with Suuntolink does nothing: they remain on the watch.
These routes are not present in the Suunto App on my phone (I figure because they were created with Movescount), so I can’t uncheck the there.
Is there any way to delete them, perhaps on the watch directly? I can’t find any such thing.
PS. I run the newest versions of Suuntolink and Suunto App.
Thanks for any help!
@phiomega , adding a route in Suunto app and marking it to be used in the watch there will trigger route sync in Suuntolink - all your current routes in watch will be erased and replaced with the one in Suunto app. You can just create a dummy one with few meters in length, but there must be something to trigger that route sync.
Regarding space, memory area for routes can only be used for routes, you have a fixed limit for maximum number of routepoints, waypoints and route entries your watch can handle, you will not get more space for your activities if you decide to to use 0% instead of 99% of your route storage.
@margusl , thanks, it worked! When syncing the first route from the Suunto App, all routes on the watch were deleted, as you stated. Now I have to export the ones I want to keep from Movescount and import them into the app manually. I’m glad I did that before Movescount will finally close down; I wonder why Suunto leaves that process as a burden to the user instead of doing it automatically, but whatever works I guess.
I have some routes renamed in SA and erased, they stayed on my A3P, do I have to create dummiy route with same name and sync and erase to get rid of old routes inside Ambit?
@lexterm77 , I don’t think names play a role, you can even use the name for all you routes if you choose to.
I’m quite sure someone reported that you must have at least one (changed) use-in-watch route to trigger the route sync. If you just deleted active routes from the app and those remained in the watch, I can actually see some (flawed) logic - route sync was just not triggered.
But if you then created a dummy route, activated it and it got synced to the watch while those deleted ones also remained, I believe you stumbled on a bug that you might be able to work around yourself (if it is what I think it is, then those phantom-routes will probably crawl back even after you reset the watch)
It triggered sync and erased old routes when I connected it to new version of Suunto Link. So all is good now, I will try same on my Traverse Alpha.