Software Update 2.48.16 (2025 November Rain release)

jjpaz

I was just joking about Amazfit, now that they’re “signing” runners and investing in marketing. It was a lame joke.

Much has already been said, all vendors and devices have pros and cons, Suunto, Amazfit, Coros, Garmin. If you search on forums, all of them show advantages and disadvantages. In the end, we can choose the device wich suits better for us and for our needs.
In my case, my SVTS and SRS are sufficient for me even with the excessive battery consumption

I’ve survived Black Friday deals without buying a Coros or a Garmin so I look forward to continuing to enjoy my Suunto watches with fresh and bug_free/bug_fixed software updates.

Kraisun Tunta

@jjpaz Honestly, knowing Suunto…
waiting for bug fixes is probably faster than waiting for a new watch face

cosme.costa

From what I have read, we won’t get Q4 til January…

GiPFELKiND

@cosme.costa whaaaaaaat??? Come on, are they working at new bugs? Or why we have so long to wait for it?

Kramble

@cosme.costa said in Software Update 2.48.16 (2025 November Rain release):

From what I have read, we won’t get Q4 til January…

Later are better if bugs will be fixed !

Josaiplu

@GiPFELKiND maybe they prefer delaying it to be sure to ensure software quality rather than rushing a release and having again people disappointed
At least it’s what I hope

The_77

@GiPFELKiND given that either this year or the year before the Q4 release wasn’t fixed despite the no HR bug for over a month on 9PP - always better to wait

mabe2k

@Josaiplu Beta release for testing before Christmas and final release in January would be perfect.

SuperFlo75

@Josaiplu Hope dies last

Josaiplu

@mabe2k open beta phases would be the best addition to avoid bug released to the mass imho, already explained this here and there but if suunto conduct such they are only opened to field testers, sound easier to collect valuable feedback rather than complains but lack of large test samples

OutdoorMan

@Josaiplu there was one attempt for an open beta some time ago, not sure why this was dismissed. I think it would help Suunto massively, as a lot of bugs are reported by users, and not by testers.

Egika

I don’t know the internal discussion about open beta tests, but I do know that it requires more than just providing s firmware to the public.
You need to make sure to have the tools and processes to gather feedback from the public. It needs to be reviewed, sorted, reproduced, etc. And if reports don’t contain full logs and a minimum set of needed information it is a hell lot of work to finally find out that there probably is no bug, but a user error…

Just saying, not arguing. Not everything is done in seconds. Also not sure what conclusions Suunto has drawn from the last open beta. But I bet they do have some.

enriqueescoms

@cosme.costa uppsss (vaya por dios)

2b2bff

@OutdoorMan said in Software Update 2.48.16 (2025 November Rain release):

there was one attempt for an open beta some time ago, not sure why this was dismissed.

This has been a day before the official release, I seem to remember. Not really that helpful, if you want to incorporate feedback…

Brad_Olwin

@Josaiplu said in Software Update 2.48.16 (2025 November Rain release):

@mabe2k open beta phases would be the best addition to avoid bug released to the mass imho, already explained this here and there but if suunto conduct such they are only opened to field testers, sound easier to collect valuable feedback rather than complains but lack of large test samples

Be careful what you wish for as Suunto open betas need to be much more stable than the beta versions the field testers use. You would not be happy with the versions we test as there are often significant issues. Several of us post here to help the community and help clarify issues. When firmware is released there are likely minor bugs that no one else caught but the major ones are typically found.
It takes time and resources to post open betas and these likely delay firmware releases so you cannot have it all.
I keep the watches that I purchase on production firmware to follow up on bugs reported by the community. Some issues I can replicate, some I cannot.

Francesco Pagano

With this firmware for me the battery drain is the worst ever, unless I unpair the HR monitor after each activity where I use it. So I’ll probably move back to the previous one, and stop bothering with unpair / pair every time I need (without phantom notifications), while suffering from the same battery drain issue I had until November, waiting to see what the next update brings.

Josaiplu

@Brad_Olwin it could be an opt in, when you sign for a beta you must be aware that it can cause software instability or even make your device unusable in some aspect
But yes most of the people see beta as a way to have the software features before the others that’s why I say it is difficult to gather valuable feedback from open beta

Btw if they release in January it won’t be a q4 update

2b2bff

@Brad_Olwin it doesn’t need to be Beta quality open betas. But I think RCs could be open, so that more bugs could be found and potentially be fixed before the real public release.
Usually a day or two after a release there are bug listed here in the forum. Some easy to fix, some severe.

Some of the bugs found here just hours after release could have been prevented that way.

And for the record I’d rather have bug fixes for all releases and new features just every 6 months, if this could improve software quality and stability of the watch. And possibly of the features…

OutdoorMan

@Brad_Olwin and yet there are people willing to participate in order to help the community. Not sure why other brands don’t have a problem with it. I am pretty sure beta testers understand it’s not stable.

AYHAN YILDIZ

With this update, battery consumption has almost doubled, while manual SpO₂ measurement has been restricted or effectively disabled.

In short, this was a poorly executed update.

Suunto needs to stop allowing software decisions to undermine the hardware excellence and engineering effort that clearly exists in these devices.

At this point, it feels as though Suunto is actively working against its own loyal customers.

Updates like this do not improve trust — they destroy customer loyalty.

A flagship device should not lose functionality, efficiency, and reliability with software updates.

If this direction continues, Suunto risks turning strong engineering achievements into wasted potential due to software mismanagement.