Beta firmware for sync issues 2.33.16
-
But if I understand you correctly, you successfully updatet to 2.33.16 already - so it’s a different situation, I have to admit.
-
@ortles well, that’s the issue. I can’t download 2.33.16 onto the app in order to update the watch. The app keeps showing ‘checking for updates’ or ‘your software is up to date’ @ 2.33.14
I’ve now deleted all the activities from the watch, removed and reestablished bluetooth connections, restarted the watch and the phone. Not sure what else to do. I really don’t want to be doing another hard reset if that’s not going to do the trick. -
@Zoltan
did you follow exactly the linked instruction? -
@freeheeler yes, I did.
-
I’m using 2.33.16. Yesterday I encountered a possible bug - the backlight was constantly turned on, outside of an activity. After restarting the watch, the issue was resolved. The normal behavior is that the backlight turns on only with specific wrist movement. Hope this helps.
-
OK, I understand, the problem is that, for some reason, you can’t download the update in Suunto App. SA starts searching for the update but doesn’t find it, right?
Unfortunately, I have no idea, what you could do then. Maybe do a hard reset as last resort, and then give it another try? But that’s just a vague idea from my side.
I did exactly the steps 1-7 as described in the instructions and could update doing so. The process that I went through is described prescisely with these steps. Finding / downloading the update in Suunto App took quite a while, I guess around 10-15 mins. I didn’t use my mobile during that time and just let it work.
I hope that you somehow successfully manage to update, even though I can imagine you have already tried a lot in the meantime…
-
@Zoltan
I didn’t have sync issues but do the update process anyway to maybe get an idea what issues you might be facingedit: worked flawlessly (iOS)
-
@Zoltan
did you try logging out and in again in SA? -
I just updated, although I haven’t experienced any issues so far. A curious experience, which (in the end) resulted in losing connection altogether. The remedy was removing the watch (S9PP) from my (IOS) phone settings and vice versa in the watch, followed by logging out of SA and then back in again.
The update in now complete!
-
@freeheeler I’ve managed to get the update/transfer going on my phone (android). that’s the good news. the not so good news is that after 10hrs it’s only at 13%
-
@Zoltan
just recharge and to be sure restart the watch and it should be fine -
Hello, more than 4 days had passed since I installed the beta update, during that period I recorded about ten activities (2/3 per day) and all of them synchronised without any problem.
From my side I would say that firmware 2.33.16 solved the sync bug on my Race. -
Installed on day of release. Had intermittent sync issues before - none since. Thank you!
-
Installed beta fw today on my Race and since then 4 activities have synced pretty much instantaneously. Looks like we might be out of the woods. Good to have it working after 2 months of constant battles.
As a precautionary measure, I’ll keep automatic updates off to avoid a similar risk of ending up as a beta tester in the future.
-
Ditto here. I’ve finally managed to install the latest patch and things have so far been working as they should with activities syncing almost instantaneously. Thank you!
-
Hello,
Relase installed yesterday and my two activites sync perfectly well. Thank you Suunto for the hotfix !
-
Hello,
Good news ! with the latest version of Suunto Apps available, synchronization of SV is now back to normal at last.
Have a nice week ahead
Laurent -
F freeheeler referenced this topic on
-
now that the synchronisation is working again as expected, I’m quite curious, is it possible to know what was the origin of the problem?
Suunto Vector . Vector HR . Core . Race & Race S
-
@Stefano-M64 a bug
-
@Stefano-M64 I guess there is no simple logical (to a user at least) answer. Some combination of recorded workouts and maybe device hardware and BLE firmware version led to BLE stack issues.
So only some random users were affected and hence it was hard to identify while testing, then reproduce and fix.
