Software update 2.37.48
-
@rooldaa Really? I think one of the main reasons buying a vertical solar will be the battery lifetime. Maybe thats ok from a daily usage perspective, but according to the advertised data your battery lifetime should be muuuuuuuuch better.
So battery drain is not completly solved and the devices are not up to the promised performance
Race S
Ambit3 Vertical -
Since the latest update on my Suunto Vertical, I’ve turned off 24/7 HR, sleep tracking, notification. Backlight low. I’m doing a one-hour run and a one-hour cycle every day, using custom mode with good GPS (no dual band) and always using the HR belt. With this setup, the battery lasts around 3 weeks, consuming a little over 30% per week. I’m not sure if this is normal since I haven’t used it this intensively before.
-
@VoiGAS said in Software update 2.37.48:
but according to the advertised data your battery lifetime should be muuuuuuuuch better.
And that is based on…?
60h is advertised without solar, so 14 hrs of activities would be roughly the first 25%. Not including the use of maps, S+ apps etc.
Then add 7 days of watch mode (2%-3% a day without HR, sleep). Brings me to 46% as a rough estimate. Not knowing how @rooldaa was using the watch and knowing that battery drainage isn’t linear, I think those numbers quite match the advertised numbers.
-
@surfboomerang You are using the SV values without solar, but @rooldaa is using the solar version. And even if he is living in complete darkness Suunto is promising 65 hours, not 60. Additionaly you calculated 46% vs 56% experienced. All in all this makes a big difference
So I don’t think I am wrong with my statement of a broken promise.
-
@VoiGAS data from a single user make you draw this conclusion? I thinks that’s a little steep…
We don’t know about backlight, notifications etc -
@Egika You are right, there can be special circumstances. But I guess you know all the posts about battery drain before the update and there are still some after the update.
If I would be one of the affected I would be upset. But I am lucky as it seems, my Race S behaves like advertised. -
According to Suunto Vertical specs, you get 30 days with a 100% charge battery, 3.33% per day.
You get 65 hours of GPS activity with a 100% charge battery, 1.54% per hour of activity.
For 7 days as smartwatch (23.3% battery consumption) and 14 hours of GPS activity (21.5% battery consumption), you should drain approximately 45%.
56% should correspond to battery consumption for 7 days as smartwatch and 21 hours of GPS activity (50% more than 14 hours)
So I don’t think @VoiGAS is so wrong by saying it doesn’t match the advertised battery life.I don’t want to polemic and I think we should not focus on the advertised battery life (which is usually obtained under best favorable conditions), but the fact is we have lost battery life since 2.35.34 firmware update.
I agree with @Egika, we cannot draw conclusions for everybody as there are so many use cases, but for the ones concerned by the battery drain issue, it is disappointing.
We should stay positive as Suunto proved us through latest firmware update they are working on the battery “issue”.May we suggest dev team to check again all changes done with firmware 2.35.34 and find what causes much battery drain than before (maybe the battery improvements done is OK for specific usage but worse in other cases).
I would be glad to remove the battery improvement of the changelog and get back to a real 60 hours battery life instead of a 65 hours battery life difficult to reach.Once again, I really enjoy my activities with my Suunto Vertical. I know I will never have the perfect watch, but Suunto watches are the ones which match my need the best (event with some little bugs
).As a reminder :
Staged update starting on July 3rd 2024
This update brings new features, improvements and bug fixes.New really cool features
:
Climb guidance feature during navigation for routes with elevation data
Possibility to select watch face complications
Three new watch faces
Cumulative data fields as watch face complications
Second configurable short cut
Screen lock in watch mode
Map zooming now possible up to 20km
Data field on navigation screen
Automatic and customizable map re-center
Sport mode specific display settings
Browse back one screen in sport mode using long press middle button
New pause and exercise end user interface with possibility to browse screens
Vietnamese language supportImprovements and bug fixes:
Improvements in the battery life with GPS: Vertical 65h - Vertical Solar 90h - Race 50h
Improved Emoji support with more characters
Improved step counter to avoid misdetection from general hand movements
Faster UI browsing
New GNSS and OHR software -
I have noticed that the whole sleep is not synchronized. The watch shows the real time and the App only a part of the dream. That is, if you get up or stay up late but go back to sleep, it no longer goes up to the App. Does anyone else happen to you?
-
-
@iterumtenta thanks
-
@Tieutieu said in Software update 2.37.48:
Battery may need a full cycle discharge and charge for calibration.
No issue on my SRs, consumption seem ok after update.What is “full cycle discharge”?
This is okey, can connect watch and charge it or cycle start when i full discharge watch and this information disappear?
-
@karmazynowycukiereczek
that means it’s discharged -
@sartoric said in Software update 2.37.48:
@karmazynowycukiereczek
that means it’s dischargedSo where does it get the energy for the display?
Ok i will try to charge it, and we will see battery performance.
-
@karmazynowycukiereczek
safely discharged
so you won’t need to trash the battery
-
@karmazynowycukiereczek said in Software update 2.37.48:
@Tieutieu said in Software update 2.37.48:
Battery may need a full cycle discharge and charge for calibration.
No issue on my SRs, consumption seem ok after update.What is “full cycle discharge”?
This is okey, can connect watch and charge it or cycle start when i full discharge watch and this information disappear?After this screen i did few times turn on/off watch by holding upper button. After full charge than, it seems battery was fixed.
-
I have had the issue of touch screen freezing again with this version of firmware in my SVTS. I have had it twice this month.
With the previous firmware I do not recall having it.First time was at beginning of the month, 15 minutes before the start of a race, I was setting everything for the race and only buttons were working. I did a soft-reset and everything went to normal.
Today it happened again, I did my morning run and after stopping the activity the touchscreen wasn’t working, I tried several times. Then I wore the watch without using the touch screen for about 30/35 minutes and the touch screen was working again, without doing a soft-reset.
@Dimitrios-Kanellopoulos @isazi @freeheeler I have sent logs at around 7:10 when the touch screen wasn’t working and I sent them again at around 7:55 when the screen was working again.
-
@Tami999 i did’t press button, i did’t know about that…
After this battery notification (screen photo) i just charge watch… but nothing change maybe even worst… -
@karmazynowycukiereczek I dont know if we should do that (completly discharge), but by that watch must still have some power to show this icon. On this screen with battery and cable i maybe ten times hold upper to turn it off, and 10 times to turn on. After that and charged watch to 100% my Vertical seems go back to normal like before this “bad for battery” updated. I dont say its works for everyone!
-
After this last update, the RS of my wife doesn’t sync the meteo anymore. The first time I saw the problem it was enough to turn the RS off and on again to have the meteo synced, now I’ve tried that workaround again but it doesn’t work: the syncing hangs while showing “updating meteo” and the BT icon on the watch turns off.
This update is a patch for few well defined issues, it shouldn’t broke other (working) things … -
@Stefano-M64 said in Software update 2.37.48:
the syncing hangs while showing “updating meteo” and the BT icon on the watch turns off.
Solved! the problem was caused by the new Google policy that explicitly asks for the Location Accuracy permission. … the meteo wasn’t updated because of lack of GPS fix.
