Unable to connect / sync vertical with suunto app since last update
-
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.
-
@ortles I am very sorry your Vertical is unusuable! It must be frustrating and I do hope Suunto will be able to pinpoint the issue and fix it soon.
I have recently suffered similarly twice. Once after I updated my Macbook Pro to the latest MacOS, something changed and when I used it with my external monitor and camera, the video started blinking green every ten seconds on meetings. Extremely annoying, as an IT guy I went through all workarounds imaginable (including trying to talk to support, compiling configuration software for camera for MacOS, changing settings, streaming via OBS etc.) to no avail. Out of despair, I ended up building my own desktop which cost me a ~$1000 (which just works!). That Macbook still does not work with the most sold Logitech external webcam to this day.
Two weeks ago I suffered the same with iPhone update. After installing, spellcheck for my language stopped working altogether! Tried filing bug and talking to support, resetting keyboard settings etc. Today, in 21st century, I am using phone that has no spellcheck at all and I write either slowly or sound like total doofus
My point is, people see Apple as company which sells extremely polished and well tested products that just work. And yet here I am.
It is OK we get frustrated from time to time - we are humans, but software is hard and I see Suunto is honestly trying, and I appreciate that. I really do hope they fix the sync issue, unlike Apple with my two issues …
-
@Matze same. The hard reset worked for a week. Today it didn’t sync again
-
Thanks for your kind words which I really appreciate
I don‘t want to blame anybody, I am convinced that everyone who works as an engineer or developer individually is doing their best to find out what’s going on and to find a solution.
Nonetheless, imo it’s not enough to just keep on trying.
If you realize as a company that you have launched an update that makes devices completely (!) unusable (even if only a part of the users is affected), and you’re not able to find a solution within a short period of time, the right decision would be to openly communicate and to go back to the status quo ante (which then would give you all the time you need to figure out what was going on and to work on an improved version).
That is what imo a professional reaction would be when you realize that something like that has gone wrong.
Imagine apple would launch an update for their phones and afterwards you are no longer able to make a telephone call for one month (and there’s no communication when this status is about to end). No one would accept this, I am sure.
-
I read one user had this problem and put the phone on airplane mode (no data) and fixed the issue. Is that correct?
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 I can’t confirm the airplane mode, but it happened to me once as well and what helped was probably turning off the bluetooth (and the app) and afterwards it has synced (it still took a long time) after the connection to the watch was re-established.
I am not sure if it’s a causality or just a correlation. -
I did some “test” trying to find a pattern and it seems that toggling airplane and discovery sometimes solves the problem.
I’ve noticed that in some cases disabling gps/position in the phone and restarting the app, let the watch sync.
Forgetting the watch from phone BT never worked by itself
I never reset the watch
I usually clear the cache and force stop the app -
My theory is that the Bluetooth connection with the phone is lost after some time after initiating a sync.
So if you have a short activity (with less data to transfer) then the probability of a successful sync (before the Bluetooth connection is lost) is higher than with a longer activity.
By putting the phone into airplane mode (but keeping Bluetooth active) means that the app will start syncing with the watch faster (as no time is spent on first syncing the app with cloud) and this increases the probability of a successful activity sync before the Bluetooth connection gets lost.
Anyway, just speculation!
-
@Dimitrios-Kanellopoulos, in my case I speculate that the watch didn’t make it to store the HR data from the activity to the 24/7 tracking (resources) after ending the activity (running) and this “fault” maybe also didn’t let the watch connect to the phone app.
See my last post with the app screenshot, but this is what’s displayed now.
