Software Update 2.48.16 (2025 November Rain release)
-
Since the last update, I haven’t noticed any difference in battery life on the Vertical 1. It’s no better, but no worse.
Without any activity, I still lose 6-7% per 24 hours, which is obviously not in line with Suunto’s specifications, which claim ‘30 days’.
During activities, however, it seems pretty good, around 1/2% per hour without sunlight in performance mode but with a heart rate belt. So I still find it hard to believe the 65-hour battery life.
It would be good if Suunto provided the settings used to achieve these values in its specifications, in the interests of transparency with customers. Instead, we get: ‘Up to 65 hours… Up to 30 days’.
By closing the Suunto app in the background and disabling the watch’s discover mode in the settings, I see that I improve battery consumption by 1/2% per day. I still need to recalibrate the battery, but I admit that I’m not very confident about it, having already done so a few months ago and seen no change.
For me, the big problem I see with these battery issues is a lack of reliability and credibility that I can give to the watch. Indeed, during an ultra trail, if I set off and think to myself, ‘But I don’t know whether or not my watch will last the whole way!’, it could add a kind of psychological pressure that you don’t need at the start of a 100-mile race.
PS: I really like my Suunto though. On the TDS this summer, I ran for 32 hours with the Race in performance mode, in always-on mode, and I still had 30% battery left at the finish line. These are amazing watches!
-
@Kraisun-Tunta you’re the guy always training in the gym? I’m on hiking trips that last up to a week and therefore battery is a critical point for me
-
@Dimitrios-Kanellopoulos said in Software Update 2.48.16 (2025 November Rain release):
@HonzaS if you expect to get bettery life savings out of a background on a sleep report its like what we say here in greece -> Squeezing the fat out of a fly to eat.
I’m satisfied with the battery life. The V2 lasts incredibly long, but it just seems unnecessary to me that the black background is gray when it’s utterly pointless. If there were a colored background with some graphics, then OK, but why make the data unnecessarily less contrasty? -
@Stefan-Kersting Haha true! You’re out there surviving a full week in the mountains, while I’m just doing flat runs in the park four days a week and hoping my watch doesn’t judge me for being slower than a turtle.
A week-long hiking trip definitely makes battery life a serious matter - you probably need a powerbank just to keep everything alive out there.
Meanwhile, my “adventures” usually end at the supermarket near my house.
-
Hello, I noted that right now, it seems the long location names issue has been solved with this update, or it’s just a coincidence?

the same for the weather widget

-
@cheetah694 good luck with your AW
recovery time is not a training ecosystem, it is just a number that barely makes sense most of the time (is it 20h or 3000h with the latest bug) -
@thailon said in Software Update 2.48.16 (2025 November Rain release):
New improved morning report is missing Fell asleep and Wake up time? Why?

They removed the 2 dedicated lines, but the times are still there below the sleep phases graph. It was redundant and making the report longer.
-
@Kraisun-Tunta The point is that we all have watch since about 2,5 years, and battery life was no problem before several firmware updates… it would be too easy to say ‚take a power bank with you‘
-
Just wanted to verify that my battery usage (Race 1) is back to where it was with this update.
Also, I’ve discovered that connecting to my Polar Verity Sense can be facilitated by moving the watch and sensor closer to each other. I also have to perform a manual connection - it isn’t automatic. I have a suspicion that the Vertiy Sense is on the hairy edge of having adequate transmitter power, but I don’t know this for sure.
My only remaining pain points are surrounding route management. Sometimes routes are not taken off the watch when you toggle “Use in Watch” in the app (android). It may take multiple tries - and yes I have verified that these are Suunto generated routes and not from Plotaroute, Komooot, or Strava. I have also had Zombie routes that I’ve been unable to remove from the watch. My workaround has been to duplicate the route and save it, and then delete the old Zombie route from the app. But this is not ideal. It would also be nice to have many more routes stored on the watch. I have some routes that I run nearby that I’d like to retain always, but I also travel frequently and want to add new routes. This has me doing a lot of shuffling of routes on and off the watch (this is why the Zombie route issue is extra problematic) - if we could accommodate storing 50-100 routes on the watch, it would be helpful.
-
@Stefano-M64 I think it was solved with the recent update of the Suunto App (not related to the Watch update)
-
@Kraisun-Tunta yeah right! Keep on Shopping your Protein power

-
@Josaiplu relying to myself on this, today I did exact same run with same setup and no phantom vibration
I kept the belt with the sensor on and not able to reproduce the issue of yesterday, intermittent issues are the worst to troubleshoot
-
@SergioB Thanks, I didn’t spot that info in the SA threads…
so, finally I can enjoy this nice WF
-
Ah, nice to hear some experiencing battery drain solved, I hope with my S9PP too! But that also means, I may don’t have to buy a new one like the Race 2…

-
@aiv4r Not sure what training ecosystem is for you then, since recovery is the most important metric of any fitness building program. Otherwise I could just track my workouts in a spreadsheet.
BTW ZoneSense telling me my AeT being 160 bpm is – although flattering – not a meaningful addition to my program either.
So at this point, if I cannot trust a single figure on this watch, what is it good for then? Telling time and firing off alarms?.. Funny thing is, recently there’s been a bug where even the latter wasn’t working.

-
@cheetah694 I train a lot, and I never look at recovery.
What gives me the best training/recovery indications is training load…tss/ctl…values. That’s way more usable to me.