Software Update 2.48.16 (2025 November Rain release)

Tomas5

@Josaiplu sleep was measured but i didn’t saw any report at morning. Old one was hard to miss, is this new report disapearing by itself in few minutes?

Josaiplu

@Tomas5 Nop it behave the same as the old one but with a new look, météo at the top and new graphs for sleep phases

Tomas5

@Stefan-Kersting i have still hope cause i played with manual blood oxygen measurements to see if it works so i have still hope. If not, i will rollback again. I did it with last update so i hope i will be able to do it with dis one too. For now firmware i got with watch was only one good. Since then battery issues and blood oxygen issues. At least with this one blood oxygen works manually but night measurement was 83%, didn’t see that low value since i rollbacked to original firmware until yesterday update:D

Stefan Kersting

@Josaiplu what is the point with introducing new fancy things when they can’t fix basic bugs

Josaiplu

@Stefan-Kersting I think they try I did not have any issue since I got my race 2 except battery drain, I did rollback and now it seems fixed
It’s hard to bring new features without bugs in software’s development, they miss something like open beta maybe to allow users to test new features and report while the others remain in stable branch released after everything is fixed

Martin Vrska

@pavel.samokha I did a factory reset on my SV2 (paired with a new phone) and after sleep tracking and morning notification, the battery dropped from 100% to 98% and the problem with the middle button not responding after waking up by raising my hand also disappeared. So I’m satisfied (so far).

VoiGAS

@Stefan-Kersting There are not really fancy new features in this update, only the merge of the two software streams and bug fixes.
So I guess they focused on the bugs this time. But as it seems unfortunately with limited sucess

Stefan Kersting

@VoiGAS I agree. thats what it actually makes it worse. If there was some fancy new features…

aiv4r

Updated yesterday without issues, HR and pace zones intact. (did not have custom sport, so cannot tell).
New morning report looks ok. (Race S)

Mads Hintz-Madsen

@Stefan-Kersting said in Software Update 2.48.16 (2025 November Rain release):

@Mads-Hintz-Madsen did you try a factory reset? I have the same trouble but before doing a factory reset and loose all my setting I want to ensure that it works and the the factory reset isn t wastet.

On the previous SW, I did a factory reset and that did naturally remove the ghost sensors as it is a complete reset of the watch.

However, the ghost sensors came back again after some time. So, on the previous SW, this wasn’t a sustainable way to get rid of ghost sensors.

I have also tried re-installing the same SW as is currently on the watch in the hope that this would remove the ghost sensors without having to reconfigure the watch (and wait for the watch to relearn your HRV range). However, this just turned all my existing paired sensors into ghost sensors so the problem got worse.

Only thing I haven’t tried is to factor reset the watch with this new SW and check if the ghost sensor problem would be fully solved. My expectation is that this would not solve the problem as there is no mention of improvements of the multiple sensor support in the change log.

dulko79

Sleep tracking went well. New morning report showed up, data are presented in a nice way.

Milan Šádek

@pavel.samokha there is one more undocumented bug fix - thank you for addressing the alarm clock issue - tested last midnight and it was finally triggered!
https://forum.suunto.com/post/166987

Stefan Kersting

@Mads-Hintz-Madsen which sensors are you using? I can identify my stryd sensor as ghost sensor. Actually is this sensor four times on my watch. The HR chest belt seems to work. I can connect disconect it and the HR chest belt is identified correct. I think these multiple sensor feature fucked it all up

The Lost Alien

Hello everyone.

I updated my SR device last night, and everything is working fine. It used 4% of the battery. It was 2% on version 2.43.12.

I downgraded to version 2.43.12 because of the various sensor issues I was experiencing in recent updates. I’ll be testing the heart rate band and my bike cadence sensor during my next workout to see how it works. I hope the sensors work well with the new update so I don’t have to revert back to the old version.

Jan Van de Velde

@dulko79 Same here. Nice improvement.

VoiGAS

All my zones and custom sports are still here - but the update turned on the Feelings for all sport modes - now I have to disable all again
Please Suunto make them at least configurable for ALL sport modes in one place!

misu763

@dulko79
The same here! No issues (for now) and nice morning welcome!
Do you think this could be considered as major update requiring a complete watch battery discharge?

Dimitrios Kanellopoulos

@Stefan-Kersting

Hi , I see you are a little bit overwhelming here with the posts. Lets take things 1 by 1.

No need to rollback
If need to clean the silly list with the ghost sensors then hard reset unfortunately. But Afaik it wont come back ghostly again.
After an update its usual to not be able to correctly within a few hours expect a normal battery “monitoring”. Run it though the days and see how ti performs.

I am more interested though in your statement about the beeps you have during time mode. are they from sensors ?

Mads Hintz-Madsen

@Dimitrios-Kanellopoulos said in Software Update 2.48.16 (2025 November Rain release):

If need to clean the silly list with the ghost sensors then hard reset unfortunately. But Afaik it wont come back ghostly again.

What do you base this statement on? Has there been some update regarding ghost sensors in the latest SW?

I am asking because on the previous SW, I did a hard reset which removed the ghost sensors but they came back. So on the previous SW, a hard reset was not a permanent solution. If it indeed would be a permanent solution with the new SW, then I would do a hard reset. That is why I would like to know if you actually have some facts on this backing up your “AFAIK statement”?

maszop

@pavel.samokha Is this a Q4 update or just an additional bugfixes update?