Suunto 9 Baro crashes / restarts at the beginning of a training

isazi

@Dimitrios-Kanellopoulos said in Suunto 9 Baro crashes / restarts at the beginning of a training:

There is a fix firmware coming out fyi

And thanks so much to all people that joined this forum to report the bug, sent logs, and helped the developers (and Suunto’s project managers) to find a prioritize this bug.
Sometimes there are fights here, but I still think this place is one of the less toxic online communities around. Let’s keep it this way.

ADHDMonkey

@TyreseJ4 do keep us posted please.

ADHDMonkey

@Dimitrios-Kanellopoulos great news, but, genuine advice from an engineering manager if I may: suunto really need to up their game with acknowledging this sort of issue earlier and keeping users regularly updated through official channels. I hope you can relay this sentiment.

Great news. I’m glad it’s fixed. By the way, I have two friends with S9B, they are on the latest fw and so far none of them mentioned about crashes or restarts.

smedberg

@Dimitrios-Kanellopoulos Great news! Do you know a time frame for when the patch can be expected?
I have a race coming up on sunday and is just curious if I should hope for an installed updated before that or not.

Dimitrios Kanellopoulos

If anyone is having issues even after a full factory reset you can pm me for sending you the fixed firmware

chargerunner

@Dimitrios-Kanellopoulos Thank you for the great news. I have two questions though:

Did Suunto team verify that the new firmware won’t cause other troubles? The latest firmware (2.30.20 I think) must have been released with thorough check, but still many users, me included, have faced this “crash” issue, while many others haven’t. So I guess the “crash” issue was an unexpected “feature” only relevant to certain watch models that may be not very popular/common (still S9B though), and ignored/forgotten by the development team.
What is the fixed firmware that you mentioned? Is it a new version, or the same latest firmware with just bug fix? I had a factory hard reset because of the “crash” issues while on the latest firmware, and after that reset I still occasionally had this issue again. I have downgraded my watch’s firmware to the previous version (2.20.xx I think) to get away from the “crash” issue, so I think I’d rather wait for a whole new/clean firmware.

Thanks a lot anyways.

Dimitrios Kanellopoulos

@chargerunner

Same version only fixes in relation to this issue

At the moment it is just produced and smoke tested.

When the FW is tested from many people and for some time the public release will start.

ADHDMonkey

@Dimitrios-Kanellopoulos would be very interesting to know what actuality caused the issue and why it would appear that only certain units have been affected.

TiagoSPM

@skifun To me it only happens - randomly - using Running and walking setups. Never on bikes (with or wo gps), weights, indoors etc.

ADHDMonkey

Started again after a week or so of a hard reset with no significant amount of use. I had been deleting activities from the log book as soon as they are loaded on the app but gave up with that at some point.

Time to downgrade the FW I think…

freeheeler

@ADHDMonkey
did you see the message from Dimitrios?

ADHDMonkey

@freeheeler yep. In touch with him.

bart80

@ADHDMonkey
I do not think we will ever know. I suppose this is a company know-how and they would like to not reveal exact details of the cause of the bug. Also there is probably very narrow set of Suunto users who bothers this information. They just want to have a working sport watch.

This is my assumption based on my experience working in similar company.

TyreseJ4

@bart80 If true this is not acceptable. Sounds more like an excuse.

sartoric

@TyreseJ4

Out of curiosity, did Garmin or others ever explain the sources of the bug they fix ?
I don’t know

freeheeler

@TyreseJ4
@bart80
whatever issue a company faces it is up to the company to deal with it and solve it.
I recall vw cheating purposely and they solved their issue once they were forced to. who knows how they solved it, because physics remain physics.
and my 2 cents again: it came up slowly with a limited number of people effected only. all reported at different locations, how should Suunto become aware about the scope.
but I do not want to re-heat this topic. I understood that @Dimitrios-Kanellopoulos is here to help and that is what counts now

TyreseJ4

@sartoric I’m not sure. However a bug that makes a device/product unusable should warrant some kind of public statement from any brand.

Dimitrios Kanellopoulos

@TyreseJ4 what do you mean it’s not acceptable?

Should Suunto disclose the code stack or so?

That said the fix is not out in public to have any statement attached and not all users are affected from what I understand and is said here as well.

It’s not a railway accident to be honest to right now try to play a blame game in order to avoid future mistakes.

So please let’s not concentrate on negativity, it doesn’t help and only ruins our emotions. .

TyreseJ4

@Dimitrios-Kanellopoulos If my comment was offensive or detrimental to someone else’s “emotions,” feel free to remove them. Honestly I don’t think I need to contribute much more to the topic as I have already moved on which I’ve already said. I wish Suunto the best and hope things get better.