Suunto 5 - tracks don't override on edits or similar names

Dimitrios Kanellopoulos

There is an issue with route duplication on current Android release. So that for sure is fixed on 4.11.x that should come to you in the next week(s)

Saketo Nemo

it seems to me that there is no precise number. Not 30, not 100. It simply depends on the watch storage capacity: the longer and more complex a move (gps data, hr, etc …), the more obviously it will take up memory space.
Here, those who record only indoor workouts, no cardio, will probably record hundreds and hundreds.
If instead you do running workouts from 5 hours at a time, they will be a few dozen.

Łukasz Szmigiel · S9PP 2.37.48

This issue was fixed with incremental update. I believe it can be closed then.

sartoric

just adding tags for now

Mff73

@sartoric said in Suunto 5 - tracks don't override on edits or similar names:

just adding tags for now

Give modo powoa to @sartoric and he will put tags everywhere
Searchinator is now Moderator

sartoric

@Mff73
and tagginator

Łukasz Szmigiel · S9PP 2.37.48

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.

sartoric

@Ł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

Łukasz Szmigiel · S9PP 2.37.48

@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.

sartoric

@Łukasz-Szmigiel
Just for testing purpose, can you try to reinstall it ? Just to avoid that for some unexplicable reason, Android do cache something

Łukasz Szmigiel · S9PP 2.37.48

@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.

Dimitrios Kanellopoulos

I have reported this, for me it happens if there is only one route. Ca n you verify this. ?

Łukasz Szmigiel · S9PP 2.37.48

@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.