Failed to check updates
-
In Software Development there is this saying or rule about “don’t release on a Friday”.
For Suunto, I think is more “don’t release on UTMB week’s eve”
I don’t expect any firmware update until after the UTMB.
-
@jjorgemoura Shame Garmin didnt read that memo! I was in the beta program and you’d commonly get beta updates late on a friday … was … interesting
-
@Desdinova then the team has a whole weekend’s worth of data to sift through on Monday. It might be suboptimal for the customer, but they elected to use beta software, and can always roll back and restore their settings.
-
@Ze-Stuart The problem was when the occasional beta was a bit… broken, one example I recall in recent times was one that would reboot the watch when you started an activity.
-
@Desdinova An this was before Garmin had a back/restore option for settings so your only option was a hard reset…
Was …fun
-
@Desdinova That’s why it’s called beta though
-
@EzioAuditore Indeed
-
Anyone find an answer to this problem ? because I also faced it on Android and still haven’t solved it
-
I report The problem solved itself, once again I reconnected the application with the clock and miraculously the update went away. This time, it seemed to me that I quickly clicked the ok button in the application when the software update was offered, maybe this is the reason.
-
here may be the explanation
@pavel-samokha said in Suunto Vertical won’t update from 2.30.38 to recent update:
There was technical issue in the cloud, please try again
