Unable to connect / sync vertical with suunto app since last update
-
@freeheeler thanks a lot for the information
infos about the red line Problem in the map If it is not visibile on the going track back?If it doesn't challenge you, it doesn't change you. #lifewithasthma #runwithasthma #nevergiveup #pushinglimits #adventurestartshere Suunto D9, 9 Baro, 9 Peak, Vertical Ti, Race , Race s Courtney, SA (Beta) Android🏃🏼🧗⛷️🚵
-
@GiPFELKiND
no info about this issue. it bothered me recently, too and we have reported it, too, of course.
I think the sync issue has a higher priority now -
Thanks for sharing this, we appreciate your help, i am sure this is the best you could do
But in fact this is quite little information - after seven weeks they should be much more ahead then just having enough material to start an investigation… Hope for some more specific updates here in the next days.
With breadcrumb issue, yeah, i agree, a vital function as well, a fix is overdue, since it’s a long known issue.
-
Hi!
I have the same issue as many others on this thread. After long activities with gps I’m unable to synch by bluetooth (android app on Samsung Galaxy s22 ultra). After couple of restarts of watch, app, phone and bluetooth connection it goes back to normal for a while, untill another similar activity (short activities without gps seems not to do any problems, as well as synching without any new activities). The problem started in april after last software update (I have my verticsl since september).
So it’s definitely very common problem. I’m waiting for any information whether we need to wait for bug fix or we need to send our watches back for repair/replacement.
-
Also noticed that this is quit weird issue that we have with the sync.
As former software tester for Suunto, I haven’t found the consistent theory of when the sync failes, and when not. One common thing is the GPS data, so for example indoor trainings have synced without any issues since the update, but the outdoor activities there is this random problem. Allthough 90% of the outdoor trainings will fail on sync, but the sync works if there is just one exercise to sync, but only after re-pairing the BT connection.
I have had 45min training, and 90min training but there is no correlation of sync fail. For me this is very annoying because like everybody is saying, with previous FW this worked ok!
I have managed to sync every exercise with repairing the BT but this is starting to get more frustrated, and I would like to stay with Suunto since I’m Finnish and I have like 1900 exercise in suunto database
And that also makes me wonder, does the number of exercises in suunto DB have anything to do with this?
-
@Pazfet Thanks for this very interesting and informative comment. It is weird issue for sure and I would be very much interested in the root cause (as I work in the IT company :D).
For me it appeared only two times and since the latest update I didn’t have this issue at all. Why is that? I have no idea! And I think that my database is also quite big but the issues somehow disappeared. -
I have an idea to test - at least whoever is willing to (and no - this is not based on any Suunto official procedure, it just came to my mind).
As the issue only affects a few people, but all over the range of mobile phones, and at the same time the FW is identical -> maybe it is a hardware variation.Here’s my idea (totally non-science based):
what happens if you try the sync with the watch at different temperatures? like watch in the fridge/freezer for 1h -> then try to sync.
Or watch in the sun for 30min -> then try to sync.Does it make any difference?
-
@GiPFELKiND In other threads this is acknowledged as known by Suunto. There will be a fix coming. You already know this. This thread is about syncing, let us not hijack the op!
-
Hello,
As said before, with my SV, synchronization of outdoor activities (30 min to 2h00) are sometime possible ( I would said around 20 %) but always 100 % synchronization of outdoors activities when I download a new map to the watch.
My conclusion: Bluetooth transfer works 100 % fine from Samsung mobile to the watch and at random (20 %) from the watch to mobile -
@Egika said in Unable to connect / sync vertical with suunto app since last update:
As the issue only affects a few people, but all over the range of mobile phones, and at the same time the FW is identical -> maybe it is a hardware
I have formulated this theory here already in a post on the 1st of april a few days after the update. Others did this as well.
It is possible that different bt units or other variations of different hardware has been used to build the watches. Not all of them can handle the increased sync speed. This would explain why it seems to depend only on the individual watch if snyc works, if it works only under certain circumstances or if it doesn’t work at all.
Did Suunto check this already?
-
@ortles as communicated here, Suunto has checked and found something.
I bet the forum users are not better embedded watch engineers than the ones who work at Suunto.
I wanted to share my idea - if you have done so before, I am interested what your findings were. Have you checked at different temperatures?
-
@Egika said in Unable to connect / sync vertical with suunto app since last update:
I wanted to share my idea
Yes, and that’s very much appreciated from my side as well, thanks!
To be honest i am reluctant to put my watch in the fridge or in the sun just to try out… How should it have to do something with temperatures?
-
@Egika I don’t think that environmental factors play any role here. It’s more likely related to bluetooth drivers and/or other apps on the phone, which also access bluetooth in the background.
-
@ortles it’s just my experience as an electrical engineer. If there is a variation in quality of a certain component, this often changes with temperature. The watch has a wide operating temperature range from arctic winter to sauna.
-
@halajos said in Unable to connect / sync vertical with suunto app since last update:
@Egika I don’t think that environmental factors play any role here. It’s more likely related to bluetooth drivers and/or other apps on the phone, which also access bluetooth in the background.
You are definitely right, as the BT FW or SW plays a role. As not everyone has the same experience though, there must be an arbitrary factor as well. As the situation seems to be the same even after a hard reset, the arbitrary factor should be somewhere hidden in the hardware.
If noone wants to follow my idea - no problem. I myself would be interested in the outcome if my watch was failing to sync. Unfortunately all my Suunto’s sync just fine… -
Thanks for explaining! I am unsure to do that even though the watch should be built to work under more ‚extreme‘ temperatures as well so there should be no risk of damage.
I have in mind that @Charles said that they have found an issue with the bluetooth unit.
Hope we get some more information about that soon.
-
Well, I can’t speak on behalf of the company, but really sorry for all who experienced the issue and fully understand your frustration. Please have a bit more patience, issue is being worked on.
-
@Charles thanks for your feedback. I followed the process you shared. The Race watch is sent to Suunto Finland for Warranty. lets’ see how it goes
in the common days -
Keep us posted!
A little status update from my side:
It has something to do with the amount of data which is to be transferred (maybe with the use of gps as well, but this might be not specific insofar). Here, small amounts get through, larger amounts fail constantly:
I could sync 2 gym units of 90 mins. (standard sports mode, no gps data recorded).
I couldn’t sync running unit of 60 mins., no matter what I tried, unpair / pair etc. (custom sports mode, gps data recorded).
The watches seem to behave totally different, obviously I got one of the worse (it can get much better, but it could get even worse).
-
@ortles
some hours ago, another guy posted that he thinks it might depend on syncing workouts with or without gps data
