Battery drain after update 2.44.46 (2025 Q3) on Vertical Watch
-
@Stefan-Kersting said in Battery drain after update 2.44.46 (2025 Q3) on Vertical Watch:
@OutdoorMan ok, that is not an option
It won’t work anyway didnt for me
-
Without activities, OHR 24, I have 6 % per day , it was 3 % before the update. I don’t use any belt or other Bluetooth…
-
Anybody knows if Suunto is aware of this battery drain issue ?
-
There is definitely a problem with the algorithm that estimates the battery level. The watch needs to be reset from time to time to recalibrate. The reset itself is not safe and can cause the watch to stuck in a “recovery loop”.
I don’t think it is relevant to some specific version update (but might be related to the update process or even to a simple on/off ) and this also seems to happen on all the Suunto models.
This situation is quite disappointing for me because one of the major pros to go with Suunto was the promised battery life
-
@Sergey-Balbir I think there is an issue lately though. I get significantly higher consumption per day despite trying to deplete the the battery and recalibrate . I even started thinking it may have been some change in the throttling of the the cpu to support the ui smoothness . I don’t believe that it was on purpose to promote the newer generation of the watches as I have read on some other posts in social media
-
@thanasis said in Battery drain after update 2.44.46 (2025 Q3) on Vertical Watch:
. I don’t want to think that it was on purpose to promote the newer generation of the watches as I have read on some other posts in social media
If you don’t want to think, why would not not want to write it?
No specific to you only, but could one really think that (thus write it) “bugs” are introduced on purpose. Come on… -
@Mff73 said in Battery drain after update 2.44.46 (2025 Q3) on Vertical Watch:
@thanasis said in Battery drain after update 2.44.46 (2025 Q3) on Vertical Watch:
. I don’t want to think that it was on purpose to promote the newer generation of the watches as I have read on some other posts in social media
If you don’t want to think, why would not not want to write it?
No specific to you only, but could one really think that (thus write it) “bugs” are introduced on purpose. Come on…(Btw I edited my post prior to your reply , but yet I think I need to clarify )
Since the new watches are currently based on the same platform you could argue that one (the people developing it ) ) does not care on the impact the implementation has on previous models because they want to promote the new ones . Not that you create bugs so that you ruin the experience on purpose . It’s an argument that you can purposely take : we need to have consistent experience hence the old ones need to take a hit on something … aka the battery life . -
Full cycle battery, 20 days with OHR24 and three activities each week (same time as usual since 2 years).
It used to be 30 days before the last update since the precedent fix drain battery issue about one year ago. -
@thanasis The battery issue has already happened a few updates ago, Suunto doesn’t want the battery to last less, they will try to fix it as soon as possible as battery life is one of the strong points of our watches.
-
@MeazzaS9 I hope so, i’m still stuck in 10% day with my vertical solar
-
@fedequei I honestly waited to update (set it to non-automatic) as soon as I read about the problem. They’re definitely already working on it.
Suunto Race S Gravel Gray (2024)
Suunto Vertical Black Lime (2023)
Suunto 7 Graphite Copper (2021)
Suunto 9 Baro Black (2020) sold -
@MeazzaS9 and where is this information coming from?
-
@MeazzaS9 What is your sources about this please ?
-
K Kramble referenced this topic
-
@OutdoorMan @Kramble These are just my considerations, but I repeat, since battery life is a must for Suunto, they cannot ignore this issue.
-
@MeazzaS9 ok, you stated it as fact so I was curious. I am not sure if I share your optimism though, but let’s see…
-
Former long-time Garmin user – I switched to Suunto at the end of last year because Garmin put me off with a lot of messed up updates and among other things the resulting high battery consumption.
And now the same thing is happening with my Suunto Vertical Solar, which I switched to because of its high power efficiency…
As I’m new to the Suunto universe, can someone explain to me if and how I can roll back to the firmware without high battery consumption? Where can I get the firmware (I can only see the last two firmware versions in the watch – and the second to last one is already faulty) and how can I downgrade the firmware of the SV?
Thanks for advice! -
I’m reading through this issue, but I’m not entirely sure I agree with what’s being said here.
Since not everyone is experiencing battery drain, how can we say the drain is deliberate?
I’m raising this issue, but let’s keep things in perspective — it’s not that Suunto wants to drain the battery faster. The Vertical 1 is Suunto’s flagship model for MIPS.
Could you please check whether the battery drain remains the same if you unpair your sensors (under Connectivity)? This was one of the main low-level changes in the latest update, so it would help narrow things down.
Thank you for taking the time to write here and report your findings — it’s appreciated!
-
@Dimitrios-Kanellopoulos I’ve experienced random restarts with my Race v1 every few hours on 2.44.52, which were gone when I reverted to 2.44.46 (hard reset didn’t help on 2.44.52). May the restarts and increased battery drain related? I assume the watch draws more current during startup. Could someone who has battery drain issue check for an error code in the debug menu (mine showed an error code)?
-
@Dimitrios-Kanellopoulos unfortunately yes, power drain is a thing even if I unpaired sensors and disabled Bluetooth visibility.
Something bad happened with the last 2 firmware updates on my SV1 (Finland): footpod does not work, battery drain, and dismissing notifications takes seconds. First time I complain about a FW update in years. First time I reach 4% battery.
I really hope a fix comes out soon and I’m starting to think to go back to previous FWs.
