Software Update 2.48.16 (2025 November Rain release)

[Tieutieu]

@Audaxjoe this I why I find myself less active on the forum lately. Meanwhile I use my watches and keep on trying to maintain fitness during winter time !

[brave_dave]

@Audaxjoe I can see what you are saying and while I am not impacted by the battery drain and other errors, I can understand why the mood and communication changed over the last months.
I feel growing frustration inside the community and especially from those that bought the new, more expensive models. And I can fully understand the frustration as Suunto claimed to have fixed problems when they weren’t and new problems were added. There are people here on this forum that put so much effort into troubleshooting for Suunto and trying to solve bugs. Despite that, no official appreciation, communication or road map from Suunto developers and the forum moderators have to somehow carry the can for that behavior and lack of open communication. Of course, costumers are upset after what happened over the last months…

[Horizontal_2]

@brave_dave I’m one of the new ones, so maybe I’m one of the problems for the negativity on this forum. If so here is my honest apology.

I’m happy with my Vertical 2. I think it’ll last the next 5, maybe 6 years and that’s what I was going for. I think a watch shouldn’t cost more than €100,- per year

It was quite a jump to pay €630,- for a watch. For me that’s not cheap. I was a bit sceptical with the tilted screens and the battery drain. It felt like taking a risk.

On both issues I was affected. The screen tilt was not big enough to send it back and (maybe) get one back with more problems. The battery drain seems to be over, while I don’t use the H10 anymore since it seems to be causing it.

Maybe what sounded negative on the forum was a honest attempt to make the watch work for me and match my expectations. It does now! The only ‘scare’ I have right now is that Suunto will release a new watch in the next 2 or 3 years that will match my wishes on the navigation, without upgrading older models. But the Vertical 2 does the job OK. I think this is not Suunto’s style and I’ll get updates in the future.

If this was negative as well, here are some positives: ++++++

[dankcushions]

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

@dankcushions I took over moderating the sub after this point (an interesting story actually) and have been actively removing obvious AI bot comments and posts. If any still remain, report them and they’ll show up in the mod queue, from which I can handle them from there.

thanks! you know when i was writing that post i tried to scan the front page for AI comments and couldn’t find any, so it appears to be working - nice job!

[Matúš]

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

@Ecki-D. said in Software Update 2.48.16 (2025 November Rain release):

9PP WHR 24/7 stopped working during night again

A shiver runs down my spine…

Currently, @Jaxxdu (https://forum.suunto.com/post/180232) and you had (again) the “pleasure” of this bug… Very very well! So, I’m waiting for it.

Finally (…), after more than a month since this update, the OHR sensor gave up during last night. I’ve managed to switch on the sensor by switching on then off the power saving mode; moreover, I’ve sent logs.

[vinc14]

Hello
it is normal i have to restart the Phone every 2 to 4 days, just because the Watch is not any more connecting/sending data to the phone??

the Problem is just on way.
If call / alerts / message happen on the phone it sends to the watch.
sleep / activity from the watch are not send to the Phone.

have a nice day
vin

[Tomas5]

@vinc14 not normall at all. Contact support, maybe submit logs from suunto app. It can be problem in phone or in watch, only official support will be able to help (hopefully).

[jjpaz]

@vinc14 Not normal, it’s an App bug.
Workaround: force stop and restart Suunto App. You don’t need to restart phone, only app.

[Stavrogin]

Playing with ChatGPT today and asking it about my BT dropout/freeze issues during a run and this is what it said. I will try disconnecting and reconnecting my H10 before each run.

**The Vertical 2’s Bluetooth stack has a background “power-save” process.
Every few runs (it depends on internal timers and battery optimization routines), the firmware will throttle BLE communication intervals — sometimes even mid-activity.

When the watch slows down those polling intervals, your Polar H10 keeps transmitting data packets normally. The Suunto misses a few and then… never properly resynchronizes.

Instead of dropping the connection and reconnecting, it locks onto the last value it received (e.g. 125 bpm).

The Suunto UI still shows the HR icon as “connected,” but it’s a ghost connection — no data flow.

Even with zero other Bluetooth devices nearby, this issue can still trigger because it’s an internal timing bug, not an external interference problem.
(In other words, it’s not your environment — it’s the firmware logic.)**

[duffman19]

@Stavrogin That answer makes 100% sense, but I trust ChatGPT just about 0%.

[Stavrogin]

@duffman19 that’s why I quote it. I agree I don’t totally trust anything on the internet including here. I only offer it because it might offer a solution. I will try disconnecting and reconnecting each run. It only takes a minute and then one of my two issues will be resolved if only until it is fixed via firmware. I can always charge more often. I don’t want to and I am excited to have Vertical-like battery life back, but when my tech poops the bed mid run I start to question if I need that tech.

[duffman19]

@Stavrogin Gotcha. I was just making an easy joke. And I really do think that answer makes total sense, but I know almost nothing about the inner workings of these things.

It’s interesting that some users are experiencing total BT disconnections midway through activities. I’ve only experienced quick disconnects, usually only lasting a second or two. But it’s still really annoying to get those connection notification vibrations throughout an activity.

My big issue remains the inability of the software to correctly connect to whichever external HR sensor I’m trying to use (I alternate between two). One solution I use it to unpair and then newly re-pair the sensor right before using it. And, as you suggested, this usually results in a good BT connection throughout the activity. So there’s that.

Here’s to hoping the Q4/Q1 update(s) will bring BT connection progress!