Synchronization process crashes for >23h activity
-
Ambit 3 Peak
I am trying to sync. a long activity. Process crashes after 10+ minutes in the Suunto as well as movescount app. All other activities got synced. Movelink2 (desktop) does not even recognize watch anymore after this move.I tried to shut down the watch several times. I tried on 5 computers. I tried with android app Ambit connect. I tried to re-install all of these apps several times. Activity is still in the logbook and has never been synced.
Suunto app shows to sync 1/1 activity then crashes after 10 minutes.
-
Have you tried clearing the cache on SA? I had this last week and un-installed SA and replaced it with an earlier version, but SA was updated this week and I believe this removed the long activity bug.
-
Thank you for your help. I re-installed the app. Unfortunately, it keeps disconnecting around 10 minutes after starting the sync. process.
-
Try to look at this thread: https://forum.suunto.com/topic/1853/ambit-3-sport-not-syncing
@sesam BRONZE MEMBER 31 Mar 2019, 20:17
“(…) it’s not just the watch that cannot go into standby mode, you cannot let the iOS app into standby mode either, nay, you cannot let the bloody screen to go to sleep either. Because the sync will fail then. (…)” -
Thank you for the answer. I appreciate your support, community! Again, I payed attention to not let both devices fall asleep. The sync. process ended for another reason. It happens also with the movescount app. The strangest thing is that after the move, my watch cannot be detected by the USB connection cable anymore. It does not happen, either for the movescount desktop app nor on android devices.
-
@Audaxjoe said in Synchronization process crashes for >23h activity:
Have you tried clearing the cache on SA? I had this last week and un-installed SA and replaced it with an earlier version, but SA was updated this week and I believe this removed the long activity bug.
May be it got fixed on iOS, but on Android it still hangs once I try to sync my watch which has a 12 hour activity on it. That reproduces 100% for me.
-
I used A3P for a 20h activity last month, GPS set to best, 1sec recording interval, HR from H10. Didn’t notice much of an issue, meaning that it was synced to SA (Galaxy S9, Android 9) in a background without me poking around.
What I’ve might have done before that race but can’t check anymore - cleared logbook by forcing firmware update. At some point in the past I started to have a feeling that sometimes something might get currupt when a circular memory area is filled up and log pointer jumps back to the beginning, so sometimes before longer races I just clear the logbook in a hope of reducing chances to loose data.
If possible, I’d give Openambit a go, but it requires access to Linux or willingness (or a mate with some) to set it up.
Though if Moveslink2 fails to detect the watch, it doesn’t sound too good …
-
Same problem appeared already in 2016:
Still no official response of Suunto via various channels. What a joke!
-
@I3astinho , that video, description nor comments do not explicitly state that the the cable itself is OK and works with another watch. You may see exact same behaviour when using faulty cable with broken data lines or stuck pogo pins - it may charge just fine but there’s no usb data connection.
-
Just bought a Garmin after 7 years with Suunto. I cannot stand the software solution and lack of support anymore.
-
@I3astinho said in Synchronization process crashes for >23h activity:
Just bought a Garmin after 7 years with Suunto. I cannot stand the software solution and lack of support anymore.
Came to Suunto after a 10+ years with Garmin and couldn’t be happier. Good luck with your Garmin adventure. I just hope you don’t need as many replacement watches, GPS units and Bike computers that I have needed over the years.
-
I am routinely syncing up to 20h with an S9 to iOS without issues, although it does take a long time to sync. I have synced 30h moves with older versions of the iOS app successfully. I am aware that the Android app has some sync issue but I think Dimitirios is on top of these. BTW when MC was first out it refused to sync anything over 24h, they finally fixed that problem. So, these issues do crop up. I have found for long exercises that strong wifi is best for syncing.
-
Thank you Brad for your response. I will keep my Suunto for a while and hope some magic will make it sync. some day.
-
@I3astinho said in Synchronization process crashes for >23h activity:
Thank you Brad for your response. I will keep my Suunto for a while and hope some magic will make it sync. some day.
The A3P may not yet be optimized for SA and you could be better off staying with MC as I know not all the planned functions are yet implemented for A3P. My S9 does not seem to have this issue and unfortunately I do not have an A3P to test.
-
SA was just a last hope after giving it millions of tries on various running systems with moveslink2 and the movescount app.
-
@I3astinho hmmm, I never had issues with SL, my longest with an A3P was 40h. Last fall I had 33h with SA, it synced but kept crashing the app, and that was fixed.
-
New A3P, same issue again.
-
@I3astinho use the cable for A3
