Battery estimate innacurate since FW 28.20

rmcbike
17 days ago

My unit has always shown a reasonably accurate estimate on how many hour of battery life left on the unit, showing aprox. 22-23 hours when charged to 100%. After updating firmware to 28.20 the hours estimate is more than double what it should be (ie. more than 54-56 hours left at 100%). As an example, the other day i did a 2 hour ride, estimate was 15h when i started and finished at 5h... On yesterdays ride by the time i had done 30-35 minutes the estimate had reduced by 2 hours.

I have not changed any setting on the device nor turned on the battery saver feature. Only change has been the updated firmware. I've tried resetting the device without luck.... I'm thinking this has to be a bug, but since i haven't seen anyone with similar issues or Garmin release a fix with the last update i'm not so sure anymore... 

Just to clarify, actual battery consumption has remained constant across different firmwares.

Any ideas on how to get this fixed?

  • 0 15 days ago

    Hello,

    I have the exact same problem. It also appeared when I updated to version 28.20, and it hasn't disappeared with subsequent updates. I contacted sat.spain, but they told me they hadn't reported any other issues of this type:

    Hola, Desde que actualicé a la v.28.20 cuando miro la estimación de batería (al 100%) aparece 60h en vez de las 20h habituales. He actualizado a la v28.33 (la última) pero no sé ha solucionado. También he buscado en foros por si le hubiese pasado a más gente pero no parece ser un problema general, ¿se me ha descalibrado? ¿Podéis ayudarme? Muchas gracias. Un saludo.


    From what I can see, at least two of us have the same problem.

    Can you help us?

    Thank you.
    BR.
     
  • 0 14 days ago in reply to since1982javi

    Thanks for posting that... looks like a bug then, even if very rare apparently.

    I'll reach out to Garmin support on monday and see what they say now...

    In the meantime it'd be nice if someone from Garmin reading this post could escalate this internally and see if they can fix this

  • 0 4 days ago in reply to rmcbike

    I’ve been in contact with garmin support and they’ve agreed on submitting this to the engineering team for review. Let’s hope they can get this fixed.