-
@Łukasz-Szmigiel
This is really weird.Do you sync to MC too ? Do you have routes there ?
Have you tried to wipe App cache data ?
Just to be sure try a watch soft reset too. -
@sartoric
S5 cannot connect to MC, if i understand clearly -
@zhang965
oh, right, only s9 was enabledso @Łukasz-Szmigiel disregard the MC comment
-
I’ll do some more testing after I return home but what I’ve observed a route is valid only when fresh. Modifying it or removing, creating a new one with the same name and syncing with watch doesn’t seem to update the route on watch - it seems as if it’s stored in watch and not removed or overwritten when edits are made. In SA everything seems to work fine (I can see all updates ok) so I assume it’s something with S5 firmware.
-
@Łukasz-Szmigiel
Just try to disable/enable the route, to see if something changes.
There is an issue if you sync the route as soon as you’re creating it.Clean the app cache too and maybe try to reinstall
-
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
