Unable to connect / sync vertical with suunto app since last update
-
@Brad_Olwin said in Unable to connect / sync vertical with suunto app since last update:
This may be difficult to solve and implement. It is not affecting everyone. I have no issues whatsoever syncing nor do any of my friends using Suunto on Android or iOS.
Yes, I’m (we are) aware that this does not affect everyone - that’s obvious!
Likewise, I understand that bugs can be difficult to fix.
What I don’t understand is that Suunto does not give us clear information. As you see above I got different information from email support and support chat. I have not received any reply to my last mail to Suunto support (see above). This is most disappointing and frustrating. -
Hi all,
over the weekend I did a hard reset of the watch, i.e. a factory reset via the watch settings menu. It is quite annoying, as I lost a couple of activities. Also you have to re-adjust your settings and re-program the customised sport modes and download the offline maps again.
Nevertheless, the hard reset did it for me. Now I can sync the activities as usual. I used pre-defined sport modes as well as my own customised sport mode. Activities with both sport modes synched as expected.
The SA is running on an iPhone and I haven’t done any changes w.r.t. the app.
Maybe this is a solution for some of you…
EDIT: I have Suunto Race.
Cheers
-
@Brad_Olwin said in Unable to connect / sync vertical with suunto app since last update:
I do not think Suunto is sitting on their hands here
So you don’t really know that they are working on it …?
We are juste really frustrated of
- Clearly the update was released without proper bêta testing
- Sunnto does not communicate about the problem et how/when they think it will be fixed
-
I run daily and have only had one instance of the watch not connecting to sync - turning BT off then back on resolved it. Latest iOS beta and watch firmware.
-
-
@Brad_Olwin
Thanks you! -
I don‘t think it‘s a problem with the app.
Took my old ambit peak 3 for some longer trips in the alps the last days and sync with it worked fine as always.
So it must be the new firmware of vertical. Maybe it doesn’t interact with different variations of the hardware as it should (hardware may differ in detail even if it is the same product).
For suunto, this clearly is a disaster, if an update makes one of their products inusable - even if only a minority of users is affected (what makes it probably difficult to figure out what the problem is). Never experienced something like that before.
As suunto is responsible for their products, in my eyes they should admit that something has gone wrong and clearly communicate what we can expect. The problem is not that something has gone wrong. This might happen. The problem is that everything is left unclear and we don’t know what we can expect.
I don‘t want to rant about that, but again, the bug should be fixed as soon as possible - even if the price would be to temporarily return to the old firmware as far as sync is concerned (a new version free of bugs could then be delivered with the next update). In the end we all would be happy if we could use our watches again.
-
@ortles said in Unable to connect / sync vertical with suunto app since last update:
I don‘t think it‘s a problem with the app.
Took my old ambit peak 3 for some longer trips in the alps the last days and sync with it worked fine as always.
So it must be the new firmware of vertical. Maybe it doesn’t interact with different variations of the hardware as it should (hardware may differ in detail even if it is the same product).not specific to your comment, but …
It is said somewhere that it might be an app issue (i don’t know, just reading here and there): app is not managing properly the new FW, thus only for new watches.We can debate eternally, it is known at Suunto, and they will fix.
-
Maybe the sync performance/speed “improvements” brought by the last firmware do not work well with the SA, possibly depending also on the BT hardware/software installed on the various smartphones. It’s frustrating, but errors occur. I’m confident a solution will be found soon and a new firmware will be released, but this need the time it needs, such kind of things can’t be done in hurry.
-
Synchronisation problem is back after five activities. The last one is not able to be uploaded to the SA again. So a hard reset did not help.
-
@Matze same for me, i tried the hard reset to solve the issue but it didn’t work after two activities uploaded.
More than 3 weeks since the update, i really like Suunto, but it is unacceptable, the watch is useless during this time. I can understand it is a big issue and the software team has to work on it, but 3 weeks…
It will bring a loss of trustworthy for the next updates.
Come on Suunto team
-
Posted a couple of times on here since the update, having the same issues as others, I’ve tried everything suggested by Suunto but not done a hard reset as of yet. I’m managing with plenty of frustration to sink activities but sometimes it can take days of trying multiple times to sink an activity whereas before update minutes at most. When contacting Suunto I’ve only had messages of, reset Bluetooth, unpair the watch, etc, etc, no information of any problems regarding the update!
-
Hello, i have the same issue with the vertical solar after the new update… i do a lot of trekking with GPS ON and some gym activity with the GPS OFF so, if i do a trekking activity with GPS ON the watch don’t sync, if i do a gym activity with GPS OFF the watch sync with no problem at all.
In my experience the problem is when the activity have the GPS ON somehow the GPX file weighs everything and doesn’t make it sync.
Anyone can try this? or is my experience only?
-
@Riccardo-Roselli I will try this tomorrow.
-
@Riccardo-Roselli I do Both, sync both without issues.
Considering that we are a lot of users to have same watches, same phones, some with issues and others without, It also could be a SA issue more than a watch issue.
Anyway let’s hope that Suunto guys find the correction the sooner. -
I just hope that the issue isn’t a bug in the Bluetooth functionality of the watch causing longer data transfers between watch and Suunto App to be unstable.
Because how are we going to get our firmware updated if that’s the case?!
-
The solution then would be to downgrade to the old version of firmware which worked perfectly fine for everybody.
It‘s now 3 1/2 weeks since the update made my vertical unusable. Had to get back to my ambit for the latest 4000m ski peaks. Very annoying, as the improved battery life of vertical was one of the main reasons to purchase it (it’s always difficult to recharge when staying at huts).
As a customer I feel a little bit left behind.
When the problem is too complex to be solved within a short period of time, please give us the opportunity to downgrade. Then we could use our watches again.
-
@ortles I totally agree with you! I now totally regret switching from garmin to suunto
-
Hello,
here the results of my last communication with Suunto Assistance:Suunto: “I’m sorry this happened, but this is an ongoing technical issue with the app that most of our customers have reported, but don’t worry, our team found a technical issue with this app, you will slowly be able to use this feature I apologize for the inconvenience.”
Suunto: “Unfortunately, I am unable to tell you the date. Our dedicated team is working on it. You will be notified, Once new update for the app release.”
I hope, it will come very soon (issue since the 25th of march)
-
First time the watch couldn’t connect to sync. Generally, I connect only when I want to sync as I don’t use notifications.
It went like this:
- Connect the watch, sync to optimise GPS
- Go out for a run
- End the activity
- Try to connect to sync, couldn’t connect, restarted phone, didn’t help
- Turned off the watch from the menu, then long press upper button to turn on
- The watch connected and synced
- Everything seems ok after some time and a couple of syncs except for resources
On the app, it seems that the time during the run got stored/processed as sleep/replenishing time, see below:
The high HR data is the run, but resources went up during this time.
