Syncing problems Ambit3 with iPhone11
-
@pcarval I wouldn’t expect a quick fix
-
@pcarval I just unpaired with my iPhone 11 iOS 13 and repaired with my iPad iOS 12.4.5 and it synced quickly and totally with my Ambit3V. Solution found.
-
@mbray So apparently iOS 13 is part of the reason of the rusty sync. Unfortunately all my iOS devices are version 13.x now. Like others have reported syncing the A3P with SA is much slower than the more recent models, when it can be successfully paired.
Another observation, unpairing/pairing between different watches for Spartan/S9/S5 is just like a click, but for the A3P I typically had to try many times (unpair from watch, forget device in the phone, blue tooth off and on, and with luck it will pair successfully again), so I ended up leaving a dedicated iPhone 6S (iOS 13.3) to permanently pairing with it. So far it works, including the AGPS/SGEE updates, depite the slow activity sync speed. -
-
@Brad_Olwin thanks and will try the latest SA
-
I own an iPhone 11 and an iPad Air 2. Both on the latest iOS. My Ambit 3 has a lot less (or none) problems syncing with the iPad. Syncing moves over one hour long with the iPhone is almost impossible (shorter moves kind of sync after a couple of tries). There has to be a problem with the iPhone 11 hardware, drivers or a phone specific iOS feature in combination with the SA.
-
@Brad_Olwin all sync issues on iphone are related to latest iphone generation.
-
@Marcin-Byrtek Thanks for the info, that is quite bizarre as the firmware should be very similar.
-
Suunto still does not provide any solution to Ambit3 Peak pairing problem with iPhone 11Pro with IOS13.
Worst of all, it ignores the bracket.
Very disappointed are Suunto. My next watch will not be from this brand. -
@entropia437 what if the solution is that there is no solution, and that Apple changed something in their Bluetooth implementation in new phones that is not compatible with older devices?
-
@isazi said in Syncing problems Ambit3 with iPhone11:
@entropia437 what if the solution is that there is no solution, and that Apple changed something in their Bluetooth implementation in new phones that is not compatible with older devices?
Entirely possible, but has there been an official statement about this from suunto? No? Do they not know or just don’t care? Anyway they are sending bad message to it’s current and possible (or not) future customers.
-
@Prenj yeah I don’t know either. If it’s about the watches, well are the Ambits still getting updates? Could not find recent ones on the website. But if it’s something that can be fixed in software within the app, then let’s hope things will get better in future versions.
-
@isazi no, no updates for almost 3 years now even they have not discontinued a3p officially.
-
Exactly the same issue here - iPhone 11 and Ambit 3 peak.
-
@isazi that is possible but Suunto is not giving any information.
-
… also, if it is a bluetooth problem with iOS13, why does it work perfectly with the Movescount application on the same phone?
I don’t think that’s the problem. What I think is that Suunto is taking advantage of the app change to stop supporting old watches. -
Fortunately, I found this post. Unfortunately, I’ve an iPhone 11 and I just bought a A3P. It was at a good price, I understand why now Don’t know what to think about Suunto yet. I’ve also an old iPhone 5 and it works. But it can only be a temporary solution. Will post a request on Suunto assistance even if there is no real hope. Thanks to all contributors of this post.
-
Chalk me up as another sucker who bought the watch before researching these problems. I’ve never been able to get my Ambit3 Peak to sync correctly with my iPhone 11 Pro, after following instructions on how to forget devices and reset firmware. Been trying over all updates since January.
Hopefully they fix this problem, but Suunto has probably just taken my money and ran. Will be sure to steer away from them in the future unless this is fixed.
-
@JMOppenheim said in Syncing problems Ambit3 with iPhone11:
Pity to hear so many people having the same issue without proper responses from Suunto. Maybe need to change brands.
Not to defend suunto, but if you do a quick search you understand other brands face similar issue.
-
Hopefully this will help, a new Suuntolink version here