Software Update 2.48.16 (2025 November Rain release)
-
Just want to confirm that I’m also still experiencing the same battery behavior as @jjpaz above with no improvements over the previous software. Still have random ghost notifications (buzzes) outside of activities that seem to be BT related and random high battery consumption. Some days are good with normal battery drain, while others have significant drops, up to 10-15% overnight. This is for both 9PP and V1.
-
@Matúš said in Software Update 2.48.16 (2025 November Rain release):
Last Tuesday morning I’ve updated my 9PP to this firmware: during the evening, reached a battery level between 10-20%, I fully recharged the watch.
Today (now), after almost 7 days, the battery level is 64%.
From firmware 2.40.44, the last one stable and used on my watch, to 2.48.16 I’ve not changed anything in my routine and device use: actually, with 2.40.44, a 100% battery lasted more or less 8-10 days.
I will continue monitoring the battery discharge, to 10-20% and for the next battery cycles, but, at the moment, firmware 2.48.16 (for me) it’s doing its work.
For me it behaves like you describe but only until I have any sport mode activated.
Then nothing can stop the drain out of the battery.
3-4 days on 9pp. Factory reset or soft reset didn’t help. -
@Egika very interesting! I wasn’t aware that it’s become that sophisticated. I’m still using flashlights that report voltage levels
-
@jjpaz I have the same problem with SV and Suunto smart belt as I posted yesterday… these beeps appear several uncountable times during training and also after training… yesterday it seemed that the belt won’t disconnect after activity
Suunto Vertical Titanium Forest/Dark Ruby/UTMB/Courtney_Edition
Suunto Wing
Suunto 9 Peak Pro Titanium (owns my wife now)
Suunto Spartan Ultra
SA iOS 3.5.1 (20789)
Instagram @superflo75 -
@Horizontal_2 I’m interested in seeing some of your new graphs.
How did you make the graph? Which software do you use? Maybe I’ll try taking my own measurements with my Suunto Vertical. -
@segi_pn I’ll update in a day or two. I’m trying to turn on the Flight mode for the night, maybe longer. Just to see if the drain comes from connectivity. The graph of previous cycle was more exciting because sometimes it did get the 5% per day easily
It’s just Excel. Everytime I see the battery drop 1% I note the time in my phone. One or two times per day I update the sheet and voilla. Sometimes I skip a percentage
-
@Horizontal_2 said in Software Update 2.48.16 (2025 November Rain release):
I’m trying to turn on the Flight mode for the night, maybe longer.
Make sure you enable flight mode from Settings, not from Control panel. Don’t know if the bug is still there with current firmware, but Airplane mode toggle in Control panel would not disable Bluetooth. 🤨
-
I have tried putting aeroplane mode on from the settings whilst at work, battery drain continues no different to if aeroplane mode is not on, approx 1% every 2 hours on average sitting around.
-
@Matúš
The same attitude for my 9PP after the latest update. Charged last Monday evening, then I updated the firmware and today is 42%…it seems the watch is back to the native performances!
Let’s see how this is going in the future cycles! -
@SuperFlo75 Do you have a ‘ghost sensors’ list in your list of linked sensors? Yesterday I trained with my Race S instead of the Vertical (also with the Coospo armband) and battery drain seems correct and watch doesn´t buzz when I power on the sensor after activities.
Difference between two watches? Race S doesn’t have ‘ghost sensors’, Vertical has 3 or 4 ghost sensors in the sensors list.
Yesterday morning also I charged Vertical, 100% battery, soft reset the watch and keep it in the table (I trained and slept with Race S) . Now battery is still 100% full battery.
-
@jjpaz I don’t have the problem with ghost sensors…
-
@Sergey-Balbir said in Software Update 2.48.16 (2025 November Rain release):
@Matúš said in Software Update 2.48.16 (2025 November Rain release):
Last Tuesday morning I’ve updated my 9PP to this firmware: during the evening, reached a battery level between 10-20%, I fully recharged the watch.
Today (now), after almost 7 days, the battery level is 64%.
From firmware 2.40.44, the last one stable and used on my watch, to 2.48.16 I’ve not changed anything in my routine and device use: actually, with 2.40.44, a 100% battery lasted more or less 8-10 days.
I will continue monitoring the battery discharge, to 10-20% and for the next battery cycles, but, at the moment, firmware 2.48.16 (for me) it’s doing its work.
For me it behaves like you describe but only until I have any sport mode activated.
Then nothing can stop the drain out of the battery.
3-4 days on 9pp.As reference, I always use standard sport modes, with battery sets in “Performance” and HR belt.
-
For your information, I also own the Vertical 1, Race 2 and Run. I use all three regularly and switch between them depending on the sessions and races I’m doing. I have to say one thing, though: the battery life of the Run is pretty impressive. With the battery issues of the V2.XX.XX, it lasts almost as long as the battery of my Race 2, which itself lasts longer than the battery of my Vertical 1.
The Run is V3.XX.XX, which makes it seem even more like there’s a software bug lurking somewhere… Another significant issue with the latest Suunto updates is that some of the bugs described as ‘fixed’ are not actually fixed at all: notably the recovery widget, which is still not synchronised (it is on the Run), and the battery drain (which is undoubtedly the most annoying).
-
Something is definitely not right with battery drain. I’ve updated it when FW was released, I did one full charge/discharge cycle. Last night I charged it to 100% and removed the watch from charger at 23:00, when I went to sleep. Watch was on my hand for sleep tracking, etc. Right now 11.5 hours later I have 94% of battery, that is 6% over night only for sleep tracking, no activity today.
EDIT: before this FW version, battery drain was normal, battery life was about two weeks with activity
-
@OutdoorMan said in Software Update 2.48.16 (2025 November Rain release):
I am happy to see that all data from watch is now in sync with the app. Resources, recovery and hrv range now all match. Also when the hrv range changes it is reflected in the app. Very happy about it. But will still keep an eye on it, on resources especially : )
Well, I have to correct my statement a bit. Recovery is out of sync again. Strangely enough it matched for a few days … this is weird.
-
@GuillaumeA said in Software Update 2.48.16 (2025 November Rain release):
[…with the latest Suunto updates is that some of the bugs described as ‘fixed’ are not actually fixed at all…]g).
that’s really annoying. Fixed , but not fixed and “fixed” without any explanation or follow up. Of course this is just a user forum and Suunto does not bear any liability , but this is the reality
-
After updating my ZoneSense software, I noticed that the color bars don’t match my breathing sensation. Has anyone else had this problem and is there a way to fix it?
-
FWIW, my 9PP showed an immediate reduction in battery drain after I turned off SPO2 measurements during sleep. Currently I’m averaging 10%/day in everyday use, previously it was almost double. I’m using the Vertical watchface with Altitude, sunrise/sunset, and date complications. I don’t know if that coincides with anything else
ON
- Alarm (vibration only)
- Sleep tracking
- HRV
- Low brightness and Low Raise to Wake
OFF
- SPO2
- Notifications
-
@Squirrel Thanks! This was a good suggestion, but not so sure the bug is gone.
The Airplane Mode is helping. It’s even slightly better than the 5%/day (it’s 3,8 %/day!). The last measurement is not even true. I’ve noted the battery is at 66%, but it’s stil at 67 :-). I think tomorrow morning I’ll toggle the Airplane Mode off. Maybe the drain is gone at that moment.
Lines:
- Upper yellow: what is should be according the specs
- Green: the extra drain after the run.
- Orange: expected drain after the run
- Lower yellow: What it should be according the specs
The big drops at day 2 and 4 are runs. The first being 1h 48 min. The second 1h 8 min
If you’d like to help: what is your drain when using the Airplane Mode for a while? And can you verify the drain is normally 5% a day?
Settings: AOD off and Raise to Wake - Display only.
Notfications don’t have a big effect I figured, maybe 1 or 2 %/day extra.
-
@SuperFlo75 said in Software Update 2.48.16 (2025 November Rain release):
Hello guys, I told you some days ago that I noticed that the Suunto HR belt is not working smooth since the last firmware update of my SV… the connection gets lost every minute… and after some minutes, an acoustic signal tells that the connection is back… before my training today, I disconnected the belt and reconnected it… but nothing changed. The belt was bought 10/24 and I renewed the battery about one month ago… after one year of usage. The problem started directly after the last firmware update… what should I do? @Dimitrios-Kanellopoulos @pavel.samokha would it be helpful to send logs? Is it the watch or the belt? The belt should be under warranty, I think?
I think it’s really crazy that no one of the suunto-near volunteers or forum members @pavel.samokha @Dimitrios-Kanellopoulos @isazi answers about these bugs…
but I want to update my observations about the BT belt problem… I just wanted to know if it is the belt or the watch which makes trouble, so it got a new Suunto smart heart rate belt today, and I tried it out. The old belt was disconnected since Monday, if don’t have the ghost problem… and I connected the new one… but there are the same problems as before… during activity, hr is gone every 60 seconds or so, and after a short break, there is the beep when the belt reconnects… that’s the proof that I have a watch problem and not a belt problem.What I don’t understand is why the belt doesn’t the memory data while syncing… I just thought that it is possible to get hr data while not having a BT connection all the time like during swimming?
This is the HR data of my little indoor Test today…So, dears friend of the night, what can we do to solve this bug as soon as possible?
