Software update 2.18.18 Sept 28 2021

[isazi]

@andré-faria said in Software update 2.18.18 Sept 28 2021:

Kindly advice to look for “battery drain” and garmin, I believe there is not a single model that doesn’t have it with some updates.

I gave up on first a F5S and then a F5 because of that. My F5S could not record more than 8 hours of GPS activity without emptying the battery (during my tour du Mont Blanc I had to stop and recharge it mid way to arrive at the end of the day with battery left), and the F5 would get from 100 to 0 in a couple of days without recording activities (gladly Amazon allowed me to return it).

[Pavlas]

Hmmm, in the morning (8 am), my watch reported a battery level of 10%. Now it’s at 9%. Power saving OFF, HR OFF, notification ON. Looks like the battery drains significantly slower at low levels.

[Dimitrios Kanellopoulos]

@pavlas yup and there you know all this is about battery calibration

we do have monitoring that alarms us when many devices have battery issues after a SW update.

[halajos]

My S9B’s battery vent from 45% to 37% in one day, sitting on the shelf. It’s on 2.18.20 and had a few partial charging cycles since the update.

[cosme.costa]

@dimitrios-kanellopoulos @Pavlas With the new firmware 2.18.20 and the S9B I think is quite clear that there is an increase in battery consumption in idle mode.

The battery meter in the S9B has never been lineal (I doubt any electronic device is completely lineal) but the behaviour over time should be the same for the same device and eventually the battery duration should be quite similar for the same model and same conditions, so we can do comparation here.

As I said in a previous post I have never needed a battery calibration after an upgrade to get more or less the same consumption compared to previous firmwares, some times I did need a soft reset. So with the new firmware the first that I did was a soft reset when I saw the increase in battery drain, after this didn’t fix it I did the calibration and the “drain” is still there.

In my case, with my configuration and more or less the same GPS load I used to charge the watch every 7 days with a 15/20% of battery remaining and now I charge it every 7 days with a 0/5% of battery remaining.

@Dimitrios-Kanellopoulos You have said that the idle consumption is related to the watchface. I haven’t tried to use another watchface because as @Pavlas said in a previous post it didn’t make any difference, now using the originally exclusive S9P and previously the original S9 outdoors watchface. In my opinion, the original outdoors watchface should be as battery demanding as the S9P as the dynamic fields are moon ring, watch time and battery level vs training dots, watch time and battery level.

[Dimitrios Kanellopoulos]

@cosmecosta yes I know of the idle issue you reported. But here I get all other assumptions that I would prefer not to mix.

The reason is that if for example the watch (s9B) lasts still 5d as specs (that we see from monitoring) having it idle on the table while it is ack and problematic, will be fixed asap in the next update.

[northeast_trekker]

Another crash mid activity while having Suunto+ weather screen on as well as navigating a route from start with waypoints. Seems like its the addition of the media controls screen because before the latest firmware update I would often use S+ and navigate and sometimes be using a route with waypoints while I did it. Was changing from the S+ screen through media controls to map when the crash happened. Wiped out AGPS logs and this time I didn’t start a new activity for the rest of the run because I wanted to send diagnostic logs. when I go to send logs the app says ‘could not send logs’, ‘please try again later’. Pretty frustrating…

[isazi]

@northeast_trekker okay, so navigation + S+ + media control. I will check this on Saturday.

[Brad_Olwin]

@isazi said in Software update 2.18.18 Sept 28 2021:

@northeast_trekker okay, so navigation + S+ + media control. I will check this on Saturday.

I will also test with S9baro. I have tested this with my S9Peak and have no crashes using media, S+ and Navigation.

[northeast_trekker]

as a follow up, I was able to send logs to support. there was no id that popped up however when they had successfully sent. I am on iOS app. I also submitted an app contact to support to let them know telling them all the detail that went along with the crash.

[plopes73]

@dimitrios-kanellopoulos you’re correct. I did a battery calibration, and the battery drains get back to old levels ( at least the 1% drain in sleep tracking for 7h sleep)

Next time will calibrate battery before posting
Cheers

[freeheeler]

@pedromslopess
…guys, why’s this post worth a down vote?!
I noticed today that my watch drained 25% in 36h with only 2 min gps tracking… no sleeptracking, 24/7 HR activated and neither frequent syncing…
this would be like 6 days battery life… normally I’ve got 5-7 days with around 5h gps tracking…
I said I will not track it down and wait patiently, but today I was very surprised about this scale of drain.
…just in case it would be my battery approaching it’s end of life: please Suunto, get S9P XL ready

[isazi]

@freeheeler I would hope that downvote is just a wrong click.

[dulko79]

@isazi True, when reading on mobile you can easily miss the appropriate arrow.

[freeheeler]

@dulko79
only if you’re fat fingered
why is there down voting anyway?
if someone disagrees he/she can just ignore the post… and if it’s a spammer, they get thrown out of our nice little team anyhow

[dulko79]

@freeheeler hahaha I am fat fingered, I press both arrows and quote button at the same time.

[MiniForklift]

@freeheeler I’m with you. Get rid of the thumbs down button!

[BinoWorld UK]

@miniforklift it’s happening on my S9 non-Baro!

It’s almost in loop sync

[isazi]

Hiking for more than 3 hours today with an S9 baro, navigation enabled, S+ weather, media controls enabled. No crash. Need to try with waypoints also, as in the past that was one issue.

[inkognito]

@isazi I am using navigation with waypoints together with S+ usually at least twice a week, different routes. I noticed one crash half a year ago and another one ~ one month ago… I was not using media controls. Therefore, I would say that the probability of the crash was less than ~ 1:20. Good luck trying to replicate that

Anyway - one thing might help. During the first crash (one year ago) the navigation went nuts - although I named my waypoints different names, the watch was showing just the waypoint type instead of the name (like in the older firmwares, but I was already using the firmware that was showing the proper names). Once the watch rebooted, the waypoint names were shown properly. So, if there is something strange with the waypoint names, chances of crash might be higher