Software update 2.39.20 (2024 Q4)
-
@GiPFELKiND said in Software update 2.39.20 (2024 Q4):
@Łukasz-Szmigiel you can find the NEW device and all things on the fccid Homepage
how can you say there is no new device How to see the new menu ?
I can’t open all the documents on the ffcid…
-
@Mi_chael you’ll have to do some lurking around ffcid to see the leaked documents (if they haven’t been removed already). Mind you, there’s no revolution, though.
-
-
@2b2bff said in Software update 2.39.20 (2024 Q4):
Thanks !
Music in the watch will be available !
Nice to use with my Wing…
-
@Mi_chael i see this too
-
@Mi_chael and as the software likely is the same for Race and others it will come to them as well…
-
@Mi_chael said in Software update 2.39.20 (2024 Q4):
@2b2bff said in Software update 2.39.20 (2024 Q4):
Thanks !
Music in the watch will be available !
Nice to use with my Wing…And Calendar will great also !
-
What is Evaluation Lab ?
And Breathe ? -
-
@Mi_chael looks like a breathing exercise app, where you can perform guided inhalation and exhalation „workouts“
-
My heart rate sensor stopped working while I was sleeping again. Is the new software version coming soon?
-
@Runners-ZoneTP
As soon as possible
-
As soon as possible in ‘SuuntoTime’…
-
@jsuarez
yeah man you are right 
-
Yes, admitting that something is not right after nearly two month seems like a bad joke. But better late than never - so lets see it positive
-
@VoiGAS to be fair the issue was addressed for the 9PP quite early, and development was slowed down by Christmas holidays too. Now a release candidate hotfix is being tested and OHR seems to work, so I’d keep my watch with more than 20% battery.
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@isazi the problem is not in adressing the issue in github repo but the lack of official communication in a sane timing.
-
@Łukasz-Szmigiel isn’t this the first, or one of the few times, that Suunto officially addressed a bug? Maybe it’s a good sign. And it should have been fixed earlier, in Suunto’s plans the hotfix should have come weeks ago, but the big proved tricky to fix. I shouldn’t get involved in the discussion more than this.
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@isazi no hard feelings, we’re just discussing with the intent of giving the consumer feedback that might improve the product and the relations between Suunto and its customers.
Fixing certain bugs is hard. Not all people are developers to understand out of the box that it might take more time to debug, fix, test and deploy. But from my experience of working in e-commerce - people do understand and are OK with delays, but only when they are addressed with dignity and are told the truth.
We had a massive surge of orders during last Christmas, and we didn’t change the shipping times from 24 hours to the real (back then) 5 days, so worried people started writing mails and calling, which disrupted the office. I insisted that we e-mail people the explanation and reassurance that their orders will be shipped before Christmas, regardless of delays.
The effect was that few people came angry and wanted to cancel their order (but they still had time to find another gift elsewhere). However, the vast majority even took their time to write back and acknowledged that they are happy we noticed them and that they are OK with it and understand that everybody wants a gift before Christmas, so the delays are expected. Also, a few people wanted to change their shipping address, because they had their trips scheduled and wouldn’t be able to pick up the order under the previously specified location - so that was a bonus of averting someone’s disaster of missed gift.
In case of Suunto and OHR issues, I’m positive that simply stating: “We know that X may be happening to your device. We’re working on a fix and estimate it may take a few weeks to deliver, because it’s tricky, and we want to test it thoroughly before we ship it to your device. Here’s what you can do to avoid it in the meantime”, would win the respect and trust of many people.
It’s cool that it happened eventually, but days+ before an actual fix after a month+ of the issue being known is a bad timing.
-
@Łukasz-Szmigiel I agree, if I could change something in the current approach is to have the release candidates as open (or semi-open) betas so that serious bugs could be acknowledged earlier, and instead of having release+hotfix, just have a release after 3 weeks of open beta reports (unless major stoppers)
Watch: Suunto Vertical Ti
Blog: isazi's home
