Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo)

Olaf Gottschalk

@Brad_Olwin sure, Brad! The problem is that if somebody wakes me up in the middle of the night for the second time, I tend to lose my temper easily. Would you be nice and gentle if somebody rings at your door in the middle of the night for no reason?

You asked this in the other thread that you locked:
No, I did not defer anything, or have any strange setting or whatsoever.
The last two updates (December and now February) did the same thing: during my sleep and DND enabled just like every night, the screen turned up, bright and shiny and woke me up.

It stated “There is a firmware update available. Install now?”

I can assure you, if this is a known bug, no it’s not fixed.

Btw: I reported this in December as well…

nhojb

@Devis exactly the same for me. Distance accuracy was previously very good. Now it is underestimating my swim distance by 20% or so, making it pretty much useless

Jussi Vaihia

Sleep tracking broke on Race after update. On the night of the auto-update no sleep recorded, then on following nights it records me falling asleep at 04ish losing half of my sleep.

GiPFELKiND

@Jussi-Vaihia oh nooooooo again? Sorry to hear this bad thing. Make a downgrade to previous Firmware and NEVER update it again

racsox

Another one here with problems with sleep tracking with a Race.
In my case, I installed the update on Tuesday and until tonight (Thursday to Friday) it was working correctly.

We will have to go back to 2 previous versions, again.

GiPFELKiND

@racsox time to Stay goodbeye

nhojb

Another data point on pool distance accuracy with the 2.39.44 update:

Today I swam breast-stroke for 1240m in a 20m pool. The Race S tracked this as only 680m - so very, very inaccurate. Previously it was more or less spot on.

Ars Vitae

Also, I report no significant change in terms of the measuring accuracy in swimming. Since for the past 2 years (and judging by the comments before that as well) none of the updates have tried to solve this problem I have accepted the errors (style recognition, distance confusion) and apply the corrections myself after training.
Reading now the reported bugs in the context of the new update, which should solve the problem of measuring distance in pool swimming, I checked the results from today’s workout and confirm that the watch (SV) still makes errors in recognizing styles, there was one mistake in counting the distance and completely fails to recognize the exercises for butterfly style and leg exercises.

Brad_Olwin

@Olaf-Gottschalk next time this happens send logs and PM me with time and date logs sent plus the email you use for SA. Has not happened to me in a long time. Auto -DND prevents the watch from buzzing and waking me up.

thanasis

My observations of the firmware

-WiFi issue sold
-synching weather is better
-no oHR so far (didn’t have before either)
But

I have seen increased battery drainage… it’s quite a lot now with overnight losing over3% and 8% on idle days

Unfortunately …

Kaiphi

I’ve been watching the clock for several days now and I’ve noticed two points. I have the vertical and never had any problems with an update before. The battery consumption has gone up. Not as high as others reported in the old updates, but 3-10% per activity or per night.
The heart rate measurement takes longer to display a value when I click on the widget and is usually too high. But then it quickly goes down to the correct value. As if it has a mismeasurement and has to adapt first. It’s not bad but will probably downgrade

thanasis

@thanasis said in Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):

My observations of the firmware

-WiFi issue sold
-synching weather is better
-no oHR so far (didn’t have before either)
But

I have seen increased battery drainage… it’s quite a lot now with overnight losing over3% and 8% on idle days

Unfortunately …

Rebooted and testing . It seems as high as when the battery issues were reported … it’s actually quite bad as it stands

Mff73

@thanasis after a FW update you should wait for a complete discharge charge before any meaningful complain .

Arju Ambin

A friendly reminder regarding battery life, check out the first question in this FAQ: https://forum.suunto.com/topic/9960/more-faq?_=1734438665530

So basically don’t judge the battery life directly after the update.

thanasis

@Arju-Ambin said in Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):

A friendly reminder regarding battery life, check out the first question in this FAQ: https://forum.suunto.com/topic/9960/more-faq?_=1734438665530

So basically don’t judge the battery life directly after the update.
@Mff73

Well … the previous time it was suggested as such and turned out to be a firmware issue … so waiting for a battery deplete before mentioning it and going through a similar circle of events seems a bit off at least .

Mff73

@thanasis
You do what you want, you can mention a potential issue, and it will be considered as potential due to the fact that it is mentioned right after FW update.
So basically, useless except posting.
Just my feeling, there are so many buzz nowadays in this forum, maybe worth waiting little bit more for reasonable proof before.

Ars Vitae

@Mff73 In my case, the complete discharge of the watch never mattered, it did not affect the the battery performance. The only thing that affected it was restarting the watch.

Tieutieu

Don’t forget that battery life is directly related to settings.
Backlight, notifcations…

For me update went very well on both my SV and SRs ; no particular issues.
(Battery life seems even slightly better on my SRs since update.)

But, that’s with my settings :

mainbacklight off
no vibrations, button tonalities off, alarm “both”
backlight to low
raise to wake low
notifications off
24h OHR on, sleep tracking ON, HRV tracking ON

I only had wifi issue, it’s corrected. I had no OHR issues, it still works fine on both.

Arju Ambin

@thanasis said in Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):

@Arju-Ambin said in Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):

A friendly reminder regarding battery life, check out the first question in this FAQ: https://forum.suunto.com/topic/9960/more-faq?_=1734438665530

So basically don’t judge the battery life directly after the update.
@Mff73

Well … the previous time it was suggested as such and turned out to be a firmware issue … so waiting for a battery deplete before mentioning it and going through a similar circle of events seems a bit off at least .

Well going on past experience prior to following the instructions in the FAQ might not give same results due to you not trying to give it one cycle this time around. If we were to try some kind of exclusion method then you’d have to go through some steps before concluding it’s the firmware. No one’s stopping you from jumping to conclusions but it makes life easier and your findings will be taken more serious if you have troubleshooted prior to posting. I’m not saying you’re wrong, I’m just saying time will tell and test what the FAQ says, I’m sure many others will also report if it turns out to be draining badly later on.

thanasis

@Arju-Ambin said in Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):

@thanasis said in Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):

@Arju-Ambin said in Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):

A friendly reminder regarding battery life, check out the first question in this FAQ: https://forum.suunto.com/topic/9960/more-faq?_=1734438665530

So basically don’t judge the battery life directly after the update.
@Mff73

Well … the previous time it was suggested as such and turned out to be a firmware issue … so waiting for a battery deplete before mentioning it and going through a similar circle of events seems a bit off at least .

Well going on past experience prior to following the instructions in the FAQ might not give same results due to you not trying to give it one cycle this time around. If we were to try some kind of exclusion method then you’d have to go through some steps before concluding it’s the firmware. No one’s stopping you from jumping to conclusions but it makes life easier and your findings will be taken more serious if you have troubleshooted prior to posting. I’m not saying you’re wrong, I’m just saying time will tell and test what the FAQ says, I’m sure many others will also report if it turns out to be draining badly later on.

I am not running into conclusions . I am just reporting my observations as I clearly mention . If the team here wants to investigate it , fine and good for all of us … if not it will be evident in the future .

I really cannot understand the defensiveness of some members considering that everyone reporting or mentioning things related to not that positive experience or iffy sentiment is an offensive action .

In any case … I did mention my observation with a positive objective to try to assist .