-
Disabling / enabling doesn’t help. Resyncing in between also. I haven’t tried clearing the cache.
I’ll do some more testing next week. Right now I can only assume this behaviour by checking the overall route shape on watch (despite my today’s experience).
S9PP 2.40.44
-
Did a quick test.
- Created a 3km route with name X, sent to watch
- Previewed the route in watch
- Unchecked the route in watch, run sync
- Route persists in watch despite being set to not sent to watch
- Removed the route from app
- Resynced
- Route persists in watch, got readded to the app with sent to watch checked
- Removed the second copy of route
- Synced
- Route removed from watch
- Created new route with the same name, synced
- Previewed the route in watch, confirmed the new route got synced
- Double (exact copy) route appeared in suunto app
- Removed two copies from app
- Synced, confirmed route got removed from watch.
What’s interesting is that while two identical copies appear in suunto app, there’s only one saved in watch.
Cleaning the app cache seems to temporarily fix the issues, however it’s rather annoying and can’t be relied upon.
Can anyone confirm weird route sync behavior on suunto 5?
-
@Łukasz-Szmigiel
You can try drawing a very strange shape route using the “straight line” mode, so when you update it you can easily check if it gets updatedEDIT:
I’ve seen your last test
Just a note, you shouldn’t need to sync to send the route. It is sent when you “toggle” itThat kind of issue was related to some previous App version (don’t rememeber which one)
-
@sartoric so this is getting even more out of hand.
What I did now was to draw a shape as you suggested (completely new route), named the route differently and checked it to sent to watch. Checked the watch only to see new name but… A recent route from my last post 0_o
-
@Łukasz-Szmigiel
Ok, that’s the issue we’ve already seen in the past.Have you already tried to unistall/reinstall ?
App data needs to be wiped off, to fix that issue.Or maybe the issue is back for new Android version.
Let’s invoke @Dimitrios-Kanellopoulos
-
@sartoric I’ve tried reinstalling last month during temporal problems with strava sync.
Perhaps data should be cleaned whenever a new version is being installed?
-
@Łukasz-Szmigiel
Usually not, but give it a tryOh, try unpair / pair too, from app, phone and watch too
-
@sartoric hm it seems that cleaning app data and setting it up again fixed the issue - for now. Thanks for the info!
I wouldn’t mind doing it every new version (either app or android) if it wasn’t for long first sync due to all activities saved in diary being resynced first time after data reset.
BTW how many activities are stored in watch? Is there any self cleaning mechanism before the watch runs out of memory?
-
@Łukasz-Szmigiel said in Suunto 5 - tracks don't override on edits or similar names:
BTW how many activities are stored in watch? Is there any self cleaning mechanism before the watch runs out of memory?
I don’t remember how many, but the first in, will be the first out
Full activity logs are cleaned after a FW update and only summary kept. -
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)
-
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. -
This issue was fixed with incremental update. I believe it can be closed then.
-
just adding tags for now
-
@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
-
@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.
