Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo)
-
@Jordi-C my race s tracked sleep just fine after the fail the other day. After the fail I did soft reset. Did you do soft reset?
-
@dulko79 Yes, yesterday I did a soft reset.
This morning my sleep tracking was detected as a nap, followed by a short period of sleep, I have to say that the battery was very low, around 6%, when I woke up, I don’t know if that had anything to do with it.
I charged the watch to 100% and went for a walk, after the first kilometer I realised that my watch was not detecting my HR.
I had to stop the activity and do another soft reset to make everything work properly.The truth is that the last 2 updates are being quite messed up.
-
@Jordi-C said in Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):
@dulko79 Yes, yesterday I did a soft reset.
This morning my sleep tracking was detected as a nap, followed by a short period of sleep, I have to say that the battery was very low, around 6%, when I woke up, I don’t know if that had anything to do with it.
I charged the watch to 100% and went for a walk, after the first kilometer I realised that my watch was not detecting my HR.
I had to stop the activity and do another soft reset to make everything work properly.The truth is that the last 2 updates are being quite messed up.
The issue with the hr being stoped it is really bad . I have had it twice already . -
As other users, for the second night in a row my Race detected a few hours of sleep followed by a couple of hours of nap. This is the first time I have issues after this update (which seemed to have solved the previous one I had, where sleep tracking wasn’t working at all)
-
@Devis I confirm. In my recent training, it is clear that the watch did not recognize a single length in the backstroke style. There must be something in that. Swimming in the pool is, in my opinion, the Suunto’s weakest point. Despite the many advantages of the watch for those for whom swimming is an integral part of training, the unresolved accuracy problem must be a major disappointment.
-
After attempting many different fixes, sleep tracking, HRV, and resources have become too ‘hit and miss’ on the Race for me. I am downgrading to the previous firmware.
Have others done the same?
-
@althaea35 I stopped updating firmware. My SV is at version 2.33.16 and works great for me.
-
I have absolutely no issues at all with both my SRs and SV, with latest fw.
Suunto’s devices at home :
Vertical titanium solar
Suunto Race S
S9pp titanium sand
Suunto Wing
S9B titanium Ambassador edition, A3P, X6 -
Hello mates.
I already got the reading error last night, a nap reading was recorded (1:13), no Vfc…
The usual setting in RACE is not to disturb, the night before I installed the vertical week screen, nothing more. Another detail, but I don’t think it’s decisive, is that the battery is at 36%…
I will wait another night in case the failure occurs before the software degradation…I like to have information from Vfc daily, I imagine like you
…Hi, something very strange. At 1:30’ after getting up, the reading for last night’s sleep appeared…other times it had been within minutes but this time I had time to publish the lack of readings… -
@Tieutieu almost the same here, sleep tracking works and worked before the update and afterwards as does workout tracking on the Race S. I had one occasion when OHR stopped working after I started a workout (green light was on, but HR stayed at some value and never changed). Restarted three times and in the pre-workout screen HR was shown but then got locked immediately after starting. Took down the watch, cleaned sensors and wore it at the inside if the wrist which suddenly fixed the problem
-
Coming back to battery drain with the firmware .
I do observe much higher battery consumption . It is similar to the pre previous firmware when the big issue was reported .So far this version has strange oHR behavior (losing hr measurements during activities with no apparent reason) and the battery is really not that great despite leaving the watch to do this calibration with running out battery and recharging
Anyone with similar results ?
Thanks
-
@thanasis I think you are right… it seems that the battery consumption of my SV is to high now…
-
@thanasis said in Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):
Coming back to battery drain with the firmware .
I do observe much higher battery consumption . It is similar to the pre previous firmware when the big issue was reported .So far this version has strange oHR behavior (losing hr measurements during activities with no apparent reason) and the battery is really not that great despite leaving the watch to do this calibration with running out battery and recharging
Anyone with similar results ?
Thanks
My observations after second and third battery charge cycle after updating to latest firmware and have done a recalibration.
Yes, I’m too observing higher battery consumption compared to two firmware versions back.
The ohr stopped once during sleep tracking since updating to latest firmware. This same behavior was experienced during last firmware too. It seems a bit better than previous firmware as it happened more during last time but this issue didn’t at least for me happen two firmware versions back. The behavior seemed to happen at random.
There was a week where 4 days the ohr just measured the lowest zone no matter how fast I ran. I washed the watch and cleaned it and the measurement started working again. My conclusion here is that there might been dirt or something interfering, so this one I’m not blaming the update.
The watch froze once during a long run (30km). Must have run 20km and it froze completely. Half of the screen was black and I had to soft reset. The distans up until 20km however got recorded on the Suunto App but the next 10km I manually entered as I didn’t have time to stop and fiddle with the watch. Have been on long runs after and it has not frozen up and everything seems ok as of now. This happened so randomly too.
So yes, I’m too having some hiccups regarding the ohr and battery consumption on the latest firmware.
-
-
@VoiGAS said in Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):
@Arju-Ambin You are not alone https://forum.suunto.com/topic/12602/watch-stopped-measuring-mid-run
Thank you! Have posted my experience regarding that specific issue there too now.
-
I’m on 2.39.20 on 9PP and I was suspecting a higher battery drain too.
Today I’ve checked in my little app the battery drain after my 1+ hour long walk and the estimate is around 20 hours instead the typical 38 - 39 hours.
There’s nothing fancy running on the watch, one face and a sun s+ app.
-
Today I did my swimming training and the watch counted almost perfectly - I swam all swimming strokes + medley + sprinting.
Again, with structured workout the watch didn’t count how much distance left for the current step of the training program. I explained this problem in my previous post here.
But today I would like to point out on another problem. For some reason the watch didn’t count the average pace. It is not the first time. Previous I was thinking it is because specific of those trainings (moving time was small).
But now it wasn’t that small. And still:
And I also checked what is uploaded to strava:
Look at moving time and pace. There is definitely a bug there.
-
@Александр-Даниленко do you happen to have (at least) one lap with a very long duration? (As shown here: https://forum.suunto.com/topic/12593/pool-swim-interval-duration-totally-wrong )
-
@pavel-samokha said in Software Update 2.39.44 (2024 Q4 Hotfix + new pool swim algo):
Staged update starting on February 10th 2025 for Race S, Race and Vertical
This update brings improvements and bug fixes.
Improvements and bug fixes:- Pool swim distance accuracy improved
- Daily HR and sleep tracking problems fixed
- Stability improvements and bug fixes
- One WiFi connection problem fixed
Not yet for Suunto 9 Peak Pro, still being tested
Hi, I would like to know if there is any news regarding a firmware update for the 9pp. Since version 2.37.48 last October, several bugs have been introduced that have certainly not been resolved with the downgrade to version 2.39.34. So it’s been more than 5 months that the watch has not worked properly…
thanks in advance
-
@t-Dox considering that the latest fix didn’t fix - I suppose we have to wait for a little longer…
