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

9.40 Battery Life

ic3cold
over 3 years ago

Has something changed with the 9.40 that affects battery life.  I feel mine is draining extremely fast.  It was at 67% yesterday and today is 44%.  I only road for an hour.  I have auto brightness off and backlight set to off.  Not sure what is going on.

  • 0 over 2 years ago in reply to sgnrus

    How can you demonstrate WiFi is always on? I experience fast battery drain as well.

  • 0 over 2 years ago

    same problem here ,it even drains battery when its off. I normally have 60% left after a few hours ride now its on 0% after a few days

  • 0 over 2 years ago in reply to 2514899

    i have ~2.5% per hour battery drain (with 3 sensors and 1sec recording). usually the BT connection is the problem after a fw update, remove the BT pairing from your mobile and from Edge and repair everything. if it doesnt help, do a master reset in the Edge and repair/reset everything.

  • 0 over 2 years ago in reply to Luko79

    What makes you think it is usually the BT connection being the culprit and what makes you think it is BT this time as well? Did repairing BT help with yours?

  • 0 over 2 years ago in reply to Martin Borsje

    i dont use BT connection on my Edge(s). But if somebody has higher battery drain than the normal ~2.5-4% per hour without navigation, then there are those 2 things are the culprit unfortunately, due to the "amazing" programmers at the Garmin HQ. this is how all Garmin devices "work" (probably You are a new user if You dont know these issues , it is "known" facts for old (~10years) users as i am ...). So If You have high battery drain, 1.: remove and repair the BT phone connection in Edge and in the mobile. If it is not helping, then You have to do a master reset in the Edge , and if it is still not helping , then You have a faulty device or the latest firmware version has bug and You can send a complain to the Garmin Support . but as we (and as the Garmin too) see, only 1-2 users have such an issue, so it is not fw related, it is only invidual problem,  something is corrupted there and has to be fixed by the user itself