Unable to connect / sync vertical with suunto app since last update

[freeheeler]

@ortles
why don’t they simply fix this bug?
maybe the bug isn’t that simple to find and fix?
I’m a mechanical guy with some high level and passive insights in software … sometimes the rootcause for a bug isn’t where you would expect it.
the same applies for mechanics, by the way

[Dimitrios Kanellopoulos]

Hi all again. I need a user that has tried multiple phones (more than one) and his activities won’t sync.

Before anyone asks why I ask this so late, I have asked this a couple of times , and the people that have been identified with the issue are not replying in the chat or providing a contact so we can investigate this issue.

[Sami Turunen]

@Dimitrios-Kanellopoulos Maby you can ask this your customer support :D. I tried tell them lot off time my problems, no help. I tried 3 iphone (7, 12 mini and 15) and android. But i already change my Vertical to Garmin so i dont have watch anymore.

[Charles]

@Dimitrios-Kanellopoulos I tried with 3 phones, sync always failed. I can help you with any of your questions (but quickly because the watch is being send tomorrow to repair)

[Lukáš Blažek]

@Dimitrios-Kanellopoulos hi, I also tried with my Pixel and with two types of Samsung phones. Still with the same problem.

[ortles]

@freeheeler

OK, I see and I can understand that in general, but my point was slightly different.

They have changed the sync process in 2.33.12 to speed it up. This led to the sync issue.

If it’s not possible to fix this (or at least very difficult and time consuming) a simple but straightforward solution would be to take back the changes they have made with the sync process as before no one had any issues with that.

So why not do that?

[freeheeler]

@ortles
just thinking out loud… if it would be that easy, wouldn’t they have tried already?

several others, and I would assume the majority of users, do not experience this (unfortunate) issue. what if it is related but not the reason?

[laurent92m]

Hello,

I tried with 2 Samsung phones without success. I tried with 2 wifi networks (home & work) and I thought it was the cause… but it is not …
On 30th April at work, I was able to synchronize 2 activities , 2 hours after arrival and after lunch, a 20 minutes walk in less than 30 seconds. Back at home, my 40 minutes cycling trip was synchonized in the evening. But running, walking of 1st May could not be synchronized at home. Today at work, after 3 hours, nothing happened ( for 3 activities). So synchronization is done or not at random …
(Hard re-set of the watch, new Suunto Apps download on 2 mobiles, new Bluetooth setting done, 2 different Internet providers tested). My conclusion, there is something wrong in Suunto coding and nothing else…
Update @ 16h47 this 2nd May. 3 activities (of yesterday & this morning) in the end transferred few minutes ago, at my work place…
Update @21h00. Back home, I managed to synchronize cycle back home activity with the transfer of a new map. So it is very bizarre and for sure something wrong in the Suunto code.

[ortles]

@freeheeler

OK, I see, it can be complicated!

In the end it’s not under all circumstances necessary to know why 2.33.12 does not work.

One thing is certain: Under 2.30.38 there were no issues with sync.

So I think if I could downgrade to 2.30.38 everything should work again. At least there’s a high probability (given that they didn’t change other things as well).

[freeheeler]

@ortles
I am very sure they are on it.
I didn’t check if we have previous firmware available here to downgrade, but yes that could be an option.

[sartoric]

If something has changed in the data structure (so how data are sent to the app) very probably downgrade isn’t a possibility

[Matze]

@Dimitrios-Kanellopoulos I have tried on an iPhone and an iPad. Would also be able to try on an Android phone, if needed.

[Ivan Vasilev]

An update (also to keep the topic on top): reinstalling the Suunto app on Pixel 7a didn’t help. The behavior is still the same - whenever the watch attempts to sync the activities to the app, the connection drops almost immediately. I hope a fix is found soon, as the issue is really frustrating.

[Charles]

Hey guys, after a month of having a non-able-to-sync watch, I’ve decided to send it back for a warranty exchange/repair.
I’ll let you know how the procedure is going

Cheers

[ortles]

@Charles

Yeah keep us updated, that would be great

Weren‘t they looking for one of the non working watches here? I have in mind that you offered to send yours.

Does anybody of you know if this has led to any specific consequences?

I am still keeping my watch (oh my god, I must be a real suunto fan then ;-)), but have to admit that I am close to give up…

[Charles]

@ortles
@Dimitrios-Kanellopoulos asked for my logs, email and phone so that the repair team from suunto know that my watch is affected.

[Stefano M64]

Yesterday, I had the idea to delete all the activities but the last one (all already synced to the SA) from the watch (Race), to check if the sync issue could be caused by the old activities stored in the watch and recorded before the firmware update (2.33.12). After deleting, the “basic syncing” (that is: gps performance, weather, etc … without new activities) performed without problems. This morning I recorded a short activity and the sync performed again with no problem. Then, I recorded another short activity and the sync was OK again.
Before deleting the old activities (from the watch) I had problem also with the “basic syncing”: the BT connection dropped often and sync restarted several times before completing the operation.

[rokkenrolli]

@Stefano-M64

Interested to see how it continues for you, although I’m not confident based on past experiences. Many people here, including myself, have done a hard reset which wipes everything off the watch. It has however not fixed the sync issues.

[Stefano M64]

@rokkenrolli

I don’t know how SA manages the sync process, however, other synching programs, as for example FreeFileSync, or cloud-based ones, as Google Drive, Dropbox, Owncloud, etc …, create and update an hidden database file that records the status of the synching process, if that file at same point became corrupt the whole synching process can be affected, because there are conflicts between the database copies on the client and on the server.
IF this is the case (I’m guessing), maybe that the hard reset by itself isn’t able to solve such conflict(s), since SA should be able repair/re-create the database and realign the activities.

[Stefano M64]

Made another Hiking activity, for about 30 minutes, while driving back home from work (Race advised me about anomalous high speed ).
Then synced again without problem in few seconds.
Let’s see if tomorrow if things continue to be OK