Software version 10.10 hitting battery

Former Member
Former Member

My watch updated to 10.10 overnight and used approx 30% of the battery whilst doing so - is this normal? 

something for those waiting for the update to be aware of! 

  • This comment raises every time an FW update is released. Just turn off your device - wait 1 minute and turn it on again = no huge battery loss.

    To compare.. My device got a FW update approx 48 hours ago. Turned off after update, half an hour to be fully charged. Yesterday a  1,5 hour of running (with GPS)  and right now with a battery remaining of 77%

  • Former Member
    0 Former Member over 5 years ago

    I did the update with my watch connected to the charger over night. The crazy thing is that when i disconnected it from the charger it showed 50%!!!

    Not expecting any improvement but the normal Garmin mess with every line of code they change.

  • I agree, there was not a single update for my Fenix 3 or my Fenix 5+ without complaints about battery drain. All battery drains I experienced were caused by apps. 10.10 runs fine on my watch, no drains, no issues with GPS accuracy....

  • Its interesting, I certainly share your view and have seen battery life all over the place after firmware updates.  After 10.10 I'm now forecast to get less than 6 days (excluding activities), down from 19 days before.  No number of hard and soft resets has improved things (yet).  I feels like a random % of users suffer this problem at each update, which to me implies that it could be fixed by Garmin.  Any thoughts on how I can get my battery life back would be much appreciated. 

  • I have been very lucky and never suffered an issue with battery, even after updates. I last charged 7 days ago and have logged 3.5 hours GPS running and 2.5 hours treadmill running and still have 31% left (it updated to 10.10 overnight during these 7 days too).

    I do not have any apps or watch faces installed other than spotify so it's possible it is app related.

  • My F5+ is doing the same. Its generally been good with its power (not as good as Garmin quote) but between 7 and 8 days average depending on usage. Now its chewing through battery, last came off charge Thursday evening and now at 12%!!! (88% in about 4.5 days).  i only run the pre-installed watch faces and apps, no wifi, no music, BT to phone and external Garmin HR chest band for all training. Always do a soft reset after a charge/update. So something isn't right. I had two F5's that both issues with battery and contact corrosion. Come on Garmin sort it out....

  • Well I fixed my issue by doing a factory reset.  A pain to have to set it all up from scratch again, but at least my battery life is back to normal.

  • Former Member
    0 Former Member over 5 years ago

    I just don’t update anymore. My current FW is 10 and I don’t see any value in updating as the changelog only refers to the WiFi function which works fine for me .... 

  • Still having issues with battery drain, tried all the usual tricks even a full factory reset and restart like it was a brand new device. Currently 34% battery used in 48 hrs with about 2 and a quarter hours of treadmill and cardio using a Garmin chest HR band. I always turn of the external HE sensor in the settings as I know treadmill carry on "searching" for it via ANT+ this chewing up battery. Really don't know what else to do. I'll be luck to get 5 days at this rate.

    Had this problem with my first F5 so returned it to Amazon for a replacement F5. Then that unit developed the charging contact corrosion issue within 3 months there was no contact left....so that one went back to Amazon for a full refund as it was discontinued by amazon. So I up graded to a F5+ which has been general fine up to now (see my post above).

    I can't believe there aren't more users commenting on there F5+'s, there must be lots of units suffering this issue.

    Come on Garmin give some feedback or find a solution. This one could getting returned to Amazon soon to if thieves any worse.

  • I can't believe there aren't more users commenting on there F5+'s, there must be lots of units suffering this issue.

    Why must there be lots of units suffering this issue?