Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Anyone else getting increaswd battery drain and glitches on 13.22 again?

fyrefyter14
over 2 years ago
  1. Ive recently updated to 13.22 and the battery drain issue is back. Using 50% in two days with only two short (under 60 mins) activities. Also started getting screen glitches again. Anyone else having a new plethora of bugs? It’s getting old in the 955.
  • 0 over 2 years ago in reply to pnmckenna

    I’ve had intermittent battery and other software glitches since July 2022 when this watch was released. This new round seems to have been decreased in 13.23 but then days like yesterday morning when suddenly the watch drains over 40% overnight leaving me charging on the drive to work then again overnight. No, no pulse ox on except at night and NO that shouldn’t drain 40%. No response from Garmin except blaming the pulse ox that isn’t on. I don’t think they have figured out what’s going on with this watch. GARMIN, we have spent lots of money on your flagship watch sport watch. Make it right.  We shouldn’t be on forums begging for support and self diagnosing.  

  • 0 over 2 years ago

    After 10 hours 7 %, then I restarted my watch and it is back to normal.

  • 0 over 2 years ago

    I too experience fast discharge rates. I don't know what triggers it, but sometimes it is okay, sometimes it is abnormal. E.g., a few days ago it went from 100% to 99% in one night, which is okay I guess. However, last night it went from 84% to 65%, which is more like abnormal. It was in the exact same state (night mode on, airplane mode on, PulseOx off) in both cases. And in the last few hours it continued this rate. Now it is at 58%. Oh, and it just decided to turn off by itself right now while I am writing these lines! :O What is going on with my watch? FW version 13.23. I start loosing my trust in this device. What if it decides to turn off during a race or in the woods?! It never happened to my FR945. 

  • 0 over 2 years ago in reply to Geri

    Watch faces can be the cause. I would try to uninstall all the downloads from CIQ and use the originals.

  • 0 over 2 years ago in reply to Martin Serafín

    Thank you for the suggestion. However, I do not use any thirdparty watch face, only the built-in ones. And, as I mentioned, the watch was in Sleep Mode, which automatically changes the watch face to a low power built-in one for the night, so it should not be an issue at all. 

  • 0 over 2 years ago in reply to fyrefyter14

    In the same boat... batter behavior was fine. Downloaded 13.23... watch lost 50% overnight. Charged to 100% at work, went for a 40 min run with music, now at 85% inside of 4 hours. I've got a 50 miler coming up and now I can't trust this thing to last through a day. 

  • 0 over 2 years ago in reply to igmaino

    Did you do "holding in the light button until the watch powers down , them wait 20s and then restart" routine after the FW update, that is suggested by many. This may help. My watch hasn't had the behaviour you mention since 13.23

  • 0 over 2 years ago in reply to S.M.R.

    I haven't.. but I'll definitely try

  • 0 over 2 years ago in reply to S.M.R.

    general understanding seems to be that restarting the watch will temporarily stop the battery drain regardless of updates. the drain will then return in a day or 2, probably after some event - some suggest sleep mode, maybe an activity using gps who knows but unless you want to restart your watch every day or 2 its not a solution

    garmin themselves have stated that they see no need to restart after an update

  • 0 over 2 years ago in reply to DaKo

    So I had a week of monitoring and gathering information. With several modes used (smartwatch mode only, activity mode + all gps + multiband, indoor activity without gps + music, and activity +all gps + multiband + music) all with heartrate monitoring on. Battery life decreased from 87% to 22%, so 65%. I calculated the theoretical (Garmin stated) values, and it should have been 63%.

    I say: well done :-)