-
@benoitg Ok so basically it was not a “bug” in parsing the data (which I personally suspected), but rather something with the connection…
Just out of couriosity, what will happen if you just keep the phone active when syncing, and the watch (meaning dont let it sleep)
-
@Dimitrios-Kanellopoulos Would love to try it… I don’t see the link to the FAQ?
-
Community Manager / Admin @Suunto
Creator of Quantified-Self.io
youtube.com/c/dimitrioskanellopoulos
https://instagram.com/dimitrioskanellopoulos
https://www.strava.com/athletes/7586105 -
@Dimitrios-Kanellopoulos it didn’t seem linked to the activities. In my case the app was showing Syncing with a progress bar progressing very fast and then Sync failed. Every time, for every activities.
It wasn’t a problem with the watch or the phone going in sleep mode, you told us to watch for that and it is explained in the troubleshooting pages too.
With the beta it worked more like in the movescount days: sync failed a few times, app showing « not connected » or sync failed, I turned off and on Bluetooth, start sync from watch, retried the process until it worked
Next activity I’ll try to get you some logs to check. -
@Dimitrios-Kanellopoulos thx. install worked… will do an activity a bit later today, see if it syncs…
-
@benoitg thanks for the explanation. Just making sure.
Community Manager / Admin @Suunto
Creator of Quantified-Self.io
youtube.com/c/dimitrioskanellopoulos
https://instagram.com/dimitrioskanellopoulos
https://www.strava.com/athletes/7586105 -
@livia_Gmelin
Hi
Not just the synch the paiting also failed for me A3 peak via iphone se 2020… -
No luck getting this to pair with the beta… nor could I export the workout from the debug menu. It eventually throws a “Failure: Archive or data fetch failed unknownError” message. It does seem to recognize there are three workouts there…
When I just try and sync from debug, I get a “Header Parsing Failure”
-
@runnr_az said in Syncing problems Ambit3 with iPhone11:
No luck getting this to pair with the beta… nor could I export the workout from the debug menu. It eventually throws a “Failure: Archive or data fetch failed unknownError” message. It does seem to recognize there are three workouts there…
When I just try and sync from debug, I get a “Header Parsing Failure”
Thank you
-
@lkovari you cannot pair the watch ?
-
@runnr_az just to get this right. Did you manage to pair the watch ?
Community Manager / Admin @Suunto
Creator of Quantified-Self.io
youtube.com/c/dimitrioskanellopoulos
https://instagram.com/dimitrioskanellopoulos
https://www.strava.com/athletes/7586105 -
@Dimitrios-Kanellopoulos yeah… the watch has always paired with my iPhone 11, it always seems to begin sync, but can’t seem to close the deal.
-
Hey guys I need your feedback if we need to get this fixed.
@runnr_az I you have a pm
-
@Dimitrios-Kanellopoulos has anyone tried iOS 14?
-
@Fermin-Lopez-Unzu @Dimitrios-Kanellopoulos I tried yesterday with Iphone 11 - IOS 14 same problem !
-
@pcarval said in Syncing problems Ambit3 with iPhone11:
@Dimitrios-Kanellopoulos
I also reset everything (unpair watch, delete from bluetooth…) and then restart from beginning.
Pairing the watch is still working … good news ! but after even the GPS Optimization failed ! Iforgot to add that I have also downloaded the latest Sunnto App. The real question is when you will admit that no one in Sunnto cares about managing this situation. I am wondering if it worths to continue to follow-up this subject on this forum. May be communicating on social Media & networks and explaining that a Sync problem openned in Sept. 2019 is still not solve, we help all people thinking about Suunto will reconsider their choice ! -
@pcarval said in Syncing problems Ambit3 with iPhone11:
@pcarval said in Syncing problems Ambit3 with iPhone11:
@Dimitrios-Kanellopoulos
I also reset everything (unpair watch, delete from bluetooth…) and then restart from beginning.
Pairing the watch is still working … good news ! but after even the GPS Optimization failed ! Iforgot to add that I have also downloaded the latest Sunnto App. The real question is when you will admit that no one in Sunnto cares about managing this situation. I am wondering if it worths to continue to follow-up this subject on this forum. May be communicating on social Media & networks and explaining that a Sync problem openned in Sept. 2019 is still not solve, we help all people thinking about Suunto will reconsider their choice !Wow, someone that works for Suunto is trying to help you, and your answer is a veiled menace to social media blackmailing. Kudos to you sir.
Watch: Suunto Vertical Ti
Blog: isazi's home
-
-
@isazi I do not know what is your role in this suunto based forum. I totaly understand what @pcarval said as i am suffering the same situation for almost a year now. If i were working for suunto i would not dare to argue with an angry customer which is right. I was promised by suunto that i would be able to upload my activities using an app, and when they discontinued the movescount app we thought that the new suunto app would do the job, and it does not and no one is doing anything serious in the company. Otherwise they would have come with a solution long time ago.
The only thing we have had is a “solution based in using a beta version of an app, tapping seven times somewhere in the phone, and entering in “debug” mode to do something I do not understand” every time I need to syncronize. By the way some people already said it does not work, and you say this is acandidate to solve the problem ?. I hope there is a better solution. -
@Fermin-Lopez-Unzu said in Syncing problems Ambit3 with iPhone11:
The only thing we have had is a “solution based in using a beta version of an app, tapping seven times somewhere in the phone, and entering in “debug” mode to do something I do not understand” every time I need to syncronize. By the way some people already said it does not work, and you say this is acandidate to solve the problem ?. I hope there is a better solution.
This is not “the solution”
, it is a way in which Suunto programmers are debugging the issue and looking for a solution that can be rolled into production and finally solve the issue.
