Suunto 5 - tracks don't override on edits or similar names
-
@Mff73
and tagginator -
Unfortunately I had the same issue again - this time with trying to import GPX (from Strava) and save a track based on it.
It syncs with watch instantly and it seems that the metadata is being correctly displayed (ie. elevation, name or total distance) but track thumbnail is from a recently deleted track that is either in SAâs cache or remaining in the watch memory. Since the track that was erroneously displayed was close to my home, I went to investigate and it wasnât just the thumbnail - the watch was in fact loading older track.
This may lead to unpleasant surprise on a race day.
Iâve tried resetting all SA data (relogin, resync with watch, etc.) but it didnât fix the issue. What fixed the problem was:
- Remove the track that failed to synchronize.
- Create a throwaway track and synchronize it with the watch.
- Confirm that a right track was synchronized by looking at track thumbnail in the watch navigation screen.
- If the right track was synchronized - create and synchronize the final track.
- If the problem persists, repeat step 2 and 3 until track thumbnail on watch matches track shape in SA.
The steps above suggest that itâs some kind of cache issue but itâs hard for me to track it - if itâs watch or SA related. Or perhaps the bug is being triggered by saving track to SA without watch connection, etc.
Once you know that you have to check the track shape in watch and compare it with SA itâs not a big deal but imagine that youâve made some tweaks to an old track and they are so small that you canât see it immediately on small screen and the watch is going to guide you through an old track.
-
@Ćukasz-Szmigiel
As @Dimitrios-Kanellopoulos said, there was a similar issue in the past (probably I reported it) with duplicate routes and strange data mix.
But it was, as far as I remember v3.something.
I use routes very much, and Iâve never faced that issue again.Did you already try to uninstall and reinstall the last app version ?
@Dimitrios-Kanellopoulos Maybe it could be related to Android10 or Pixel XL ?Edit
Found this :https://forum.suunto.com/topic/2174/android-3-64-0-generic-comment/54
but there was even an older similar one -
@sartoric I didnât reinstall the app but cleared all the data (ie. cache + data) which essentially resets it. Also, Iâm on latest betas.
Itâs the first time Iâve stumbled upon this error after last time I was reporting it (September last year I think) so I thought it got fixed.
-
@Ćukasz-Szmigiel
Just for testing purpose, can you try to reinstall it ? Just to avoid that for some unexplicable reason, Android do cache something -
@sartoric Iâll do it next time the bug occurs as it seems to be fine after I finally got the GPX based track on watch.
-
I have reported this, for me it happens if there is only one route. Ca n you verify this. ?
-
@Dimitrios-Kanellopoulos I have several routes in SA, around half of them synchronized with the watch. There were 3 routes in watch memory when the bug occurred this time.