Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo)
-
@pavel-samokha hoping for the best that all bugs and issues will just be a bad memory
Been with a Suunto on my wrist since Ambit2
Currently alternating between Race titanium & Vertical titanium solar.
Would love a Vertical with amoled display. -
@Ecki-D said in Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):
@AntoniusGaius Mine too! Suddenly after some weeks it did say in the morning - oO I have been updated - this is really weird don’t know what did trigger it suddenly.
I think they can force it in some cases no matter what is set. Othervise this can’t happend. I personaly don’t like it I don’t agree with it and it is all I can do with it
-
@peegee please give us here the first known Firmware from the Vertical, the Race and Race s Back …
-
Dang it… Have to charge up my watch for this update. A huge thanks to the developers and testers! been looking forward for this update.
-
@isazi
I rolled mine back to 2.37.48, before the official rollback was released, because I had a long race coming up.
I’ve done about 90hrs of running since then and battery drain etc is as normal, so I’m just leaving it on 2.37.48 until the update is ready. I’d much rather it takes longer to test the update to be sure the problems are fixed. -
@Brad_Olwin said in Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):
@Niclas-Brundell The OHR issue was difficult to find. I wore my 9PP (the watch affected the most) for a day or two with new firmware release and had no issues. The other watches I tested for sleep tracking and exercise and all day OHR also had not issues. When reported on the forum, I again donned my 9PP and after 3d I had the OHR quit. I had the OHR quit randomly on the Race S as well but never on my Vertical. This happened right at the holidays in December. The field testers had at least 12 firmware variants to test prior to this release. They and I am sure internal testers worked hard to see if the OHR issue was fixed.
So, some issues simply don’t occur and require a combination that may not occur in testing. Believe me that many, many bugs are fixed prior to a release. I had zero syncing issues last year and if I remember that was only Android and may have been again an issue that only affected a few users.
You will miss out on a lot if you do not update the Vertical. I typically run field test firmware on the Vertical I purchased. Rarely do I have serious issues. I know you do not like the UI with different sizing, I and others do, that is a personal issue. I don’t see how it is any less usable.
I really wouldn’t say that you miss out a lot by not updating. I’ve had the watch for a year and the only upgrade that’s made a difference for me is the increased battery life. Which was awesome. Other than that there hasn’t been a single update that makes a difference that I can think of, as the UI speed updates had already been released. But I had to spend a lot of time dealing with the no sync bug. So I’d be happy to just leave it without any more updates unless they can fix the issue with high winds causing elevation gain and loss to go wonky. There’s really nothing I’m missing outside of that. It’s already a great watch. And no risk of introducing new bugs.
Don’t take it as just criticism against suunto. I don’t find the need for any new updates as I already find the vertical to be a great watch. I don’t miss any features
-
@Brad_Olwin this is why, prior to the release, an open beta should be released. Just because the amount of people testing and the amount of combinations exceed wildly what currently testers can do in limited amount of time.
-
Awesome, installing it now. Thanks for the hard work!
-
@TrailEyes said in Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):
@Kramble You rock!!
I had tried going to the upper-button shortcut already, but that hadn’t worked. Yet thanks to your comment, I also tried the middle-button pinned widget, and doing that first did fix the Control Panel display! Thank you so much!
You’re welcome, I had modified my post to precise middle button.
-
@Brad_Olwin
Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):The OHR issue was difficult to find.[…] I had the OHR quit randomly on the Race S as well but never on my Vertical. This happened right at the holidays in December.
nevertheless replaying to my queries (in January) on the many issues on my Race Is my watch failing? you were saying:
@enneo Cannot speak directly to Race but Race S has no issues.
This lack of transparency is discouraging. I appreciate that a bug can occur and how difficult can be to reproduce. But also I took full advantage of my watch after reverting to the previous software and would have preferred to know this in advance rather than trying to debug myself or even have to deal with the customer service.
I would like to thank all the developers for the effort to fix this nasty bug but would recommend some further discussion about the company policy on known issues and workarounds disclosure.
-
@enneo said in Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):
@Brad_Olwin
Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):The OHR issue was difficult to find.[…] I had the OHR quit randomly on the Race S as well but never on my Vertical. This happened right at the holidays in December.
@enneo Cannot speak directly to Race but Race S has no issues.
At the time I answered, I lad no issues with Race S. I did not lose OHR until several versions later, so I cannot say if mine was affected
-
Thank you! Updated without any issues - looking forward to start the first after-update-activity tomorrow.
Up to now (except for the battery bug) all updates brought a steady, welcome, not requested , but very gratefully accepted stream of useful enhancements, that I did not buy the watch for, but (partially and intensively) use
… and I am very happy to still have the beautiful carousel-UI/look … I like it, and received positive comments about it, too.
So, Suunto and Beta-Testers please do not stop to proceed to further improve this great Vertical of mine. -
One post, intended to just try to spread a little good feeling into the forum…
From what I understand, the testers here are ‘just’ that: testers. They don’t work for Suunto, nor are they responsible for the products that the company delivers, the associated bugs or the strategy towards fixing them. Can we all please remember this? I have no beef, or anything to do with the organisation of the forum. However, I’ve found it really helpful on a number of occasions. It would be great if everyone took a positive approach and realises/ accepts that everyone here is doing their best.
Sorry if this is not welcome, but I felt it worth saying.
-
@enneo said in Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):
nevertheless replaying to my queries (in January) on the many issues on my Race Is my watch failing? you were saying:
@enneo Cannot speak directly to Race but Race S has no issues.
My Race S never had any problems. It’s completely possible, that this was the case for him too. I guess that’s what made it take that long to fix things, that the problems didn’t show up everytime on every watch.
-
My SV updated today without any problems… I hope that the firmware is working well for me
because I didn’t have noticed the problems which were fixed no on my watch. I‘m not a software developer, I‘m a orthopedist and chirotherapist, and for me it is clear that I only can test if a new therapy works against a illness if I try it with a person who has this illness… regarding to this I think it would be fine if the users who have an issue with their watch could test if the beta version of a software is useful against this issue? A field tester perhaps can only test if the new software cause any new problems, because his watch was working fine before? -
@SuperFlo75 Same here. Never had any problems like some users say. Yesterday load battery to 99%. After 7 hours sleep it losts no (0%) battery. Perfect work Suunto Team.
-
@Brad_Olwin said in Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):
@Niclas-Brundell The OHR issue was difficult to find. I wore my 9PP (the watch affected the most) for a day or two with new firmware release and had no issues. The other watches I tested for sleep tracking and exercise and all day OHR also had not issues. When reported on the forum, I again donned my 9PP and after 3d I had the OHR quit. I had the OHR quit randomly on the Race S as well but never on my Vertical. This happened right at the holidays in December. The field testers had at least 12 firmware variants to test prior to this release. They and I am sure internal testers worked hard to see if the OHR issue was fixed.
So, some issues simply don’t occur and require a combination that may not occur in testing. Believe me that many, many bugs are fixed prior to a release. I had zero syncing issues last year and if I remember that was only Android and may have been again an issue that only affected a few users.
You will miss out on a lot if you do not update the Vertical. I typically run field test firmware on the Vertical I purchased. Rarely do I have serious issues. I know you do not like the UI with different sizing, I and others do, that is a personal issue. I don’t see how it is any less usable.
Thank you for the insightful post and the testing time. To me it seems the December update was a bit too late and that’s why that problem was aggravated. My judgment about timing is based on the fact that Xmas skins were bundled and the update was too close to Xmas time.
Thankfully the most pressing issues have hopefully been corrected.
-
@jsuarez said in Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):
@Brad_Olwin said in Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):
@Niclas-Brundell The OHR issue was difficult to find. I wore my 9PP (the watch affected the most) for a day or two with new firmware release and had no issues. The other watches I tested for sleep tracking and exercise and all day OHR also had not issues. When reported on the forum, I again donned my 9PP and after 3d I had the OHR quit. I had the OHR quit randomly on the Race S as well but never on my Vertical. This happened right at the holidays in December. The field testers had at least 12 firmware variants to test prior to this release. They and I am sure internal testers worked hard to see if the OHR issue was fixed.
So, some issues simply don’t occur and require a combination that may not occur in testing. Believe me that many, many bugs are fixed prior to a release. I had zero syncing issues last year and if I remember that was only Android and may have been again an issue that only affected a few users.
You will miss out on a lot if you do not update the Vertical. I typically run field test firmware on the Vertical I purchased. Rarely do I have serious issues. I know you do not like the UI with different sizing, I and others do, that is a personal issue. I don’t see how it is any less usable.
Thank you for the insightful post and the testing time. To me it seems the December update was a bit too late and that’s why that problem was aggravated. My judgment about timing is based on the fact that Xmas skins were bundled and the update was too close to Xmas time.
Thankfully the most pressing issues have hopefully been corrected.
I share your view on the timing.
And I think that some people have learned from this, too -
Hi Guys
No excuses on our part, we understand all the frustration and bad experience and we will try to improve in the future, there are no excuses on our side…SORRY
-
@Joaquin I think this must be a problem on hardware. Why do only a few users have problem but the most not?
