S9 fails to sync after charging
I’m new to Suunto and got a 9 in the black friday sales. All good at first, downloaded app and then pair watch and good to go. No problem syncing activities etc. I plugged into PC with Sunntolink to charge and make sure I was on latest firmware. After that it wouldn’t sync with my Andriod phone. A simple unpair and pair fixed that. 5 days later I needed to charge, this time plugged the cable into my standard charging port. Again the watch didn’t sync after charging. This time I had to delete app, reboot watch before I could pair and sync.
Well, I would have suggested to soft reset the watch, that you already did.
Let’s see if it’ll get stuck again.
@Stevek I am not on Android so I cannot help much but list the phone, version of SA you using and that will help. Also, do you have Movescount app installed on your phone?
@Stevek what app version are you using ?
I’ve not used the Movescount app
App version 4.31.0
Watch software: 2.12.30
I did sign up for the beta app, in case that helped. But I’ve not loaded it yet.
@sartoric Interesting. Although it was on 95% after the last charge, but I recharged anyway to see if it would get stuck again. And it seems OK - maybe that soft reset worked. It’ll probably be 4 or 5 days before it needs charging again. I’ll post an update then. Thanks
@Stevek Did you update the watch while you had not synced an activity ?
@Dimitrios-Kanellopoulos I think there is a small bug with the last firmware of the watch or the combination of the watch and SA. I have suffered it 3 times already, that every now and then the watch and SA are unable to sync. SA is not able to see the watch. In my case soft reset solves the issue, I haven’t tried to reboot the phone or other things.
I’m waiting to this to happen again to get some logs but I have read in the forum that other people has had this issue so I think that is more general. Because it happens from time to time, I couldn’t determine what triggers it, maybe the number of syncs, I do not know.
What I know is when it is going to happen because, after saving the activity, the watch is extremely slow to load the autolaps screen, it loads first one km, then the second, then the third, …. Until the screen shows all the autolaps. Because of that I am more inclined to believe that the issue has been introduced with the last firmware.
@cosmecosta that is known (soft reset that solves the issue).
Android version 4.33.1 should come with a fix .
You are on Android right?
@cosmecosta So just to repeat. For your info:
- Sometimes when the connection is establised and lost many times (eg try to turn BT on/off many times or connect to SL etc) the watch becomes laggy (lost packets) and cannot connect to the app after that. A reboot helps.
This is fixed as said and will come to you I think next week
With a firmware update?
@Mi_chael 4.33.1 is the next Android beta.