Just posting to raise more awareness from Garmin. 14.20 is draining battery a lot. Idling and high drain durin activity too.
Fix please, there’s been way too many bugs on 955 from your part.
Just posting to raise more awareness from Garmin. 14.20 is draining battery a lot. Idling and high drain durin activity too.
Fix please, there’s been way too many bugs on 955 from your part.
UPDATE: After I conducted a full reset of my 955, I've left it a while and this seems to have solved the issue (although it is VERY annoying to have to do this and reapply all your settings). The 955 is no longer continuously syncing with the GC app and battery usage has dropped down to around 0.5% per hour with OHR and BT on. Syncs now appear to happen every 60s or so, at least that is what I am observing, but they are brief. The GC app is still the second most used app on my handset (OP9Pro) but TBH usage is around 3.5% across a spread of other apps I use. I used to get around 0.3 - 0.4% per hour so power usage still a little high. Looks like perhaps some conflicts on the device post-update. If it's not a pain for you, you may wish to reset the device and give it a day to settle. I use the Power Manager widget from Connect IQ to monitor my battery and I highly recommend it.
Neither of these solutions help in my case...well I won't reset it for the third time, 2 (1 new setup manually from zero) watches same thing. I wait for release of stable v15 firmware to see. My drain is, I guess, not related to CG and phone. The watch keeps draining after the activity when it was connected to one of the sensors (H7 HRM, Cadence sensor or Varia RTL515). Each one of those caused drain, even when turned off in the Sensors....till 10 seconds restart of the watches.
Similar with my case.
Like below drain chart.
I just ran during the two red dash line then stayed in smartwatch mode, however FR955s kept draining for very long time.
And I still do not know why it back to normal after long time drain.
I spoke too soon. My watch is now showing over 1% drain per hour, 27% per day, with a long term average of 3.69 days per charge. Completely unacceptable. Thinking about this, when I did my reset I did not add any sensors to the device immediately. Then last night I did an indoor bike session and added my powermeter from my bike. I wonder then if the reason why I was receiving OK battery life is due to not having any sensors, but with a sensor the watch is constantly looking for it even when not in an exercise mode. I might remove the sensor now and see whether this causes the issue.
issue present on my side too...what do you suggest to do in order to solve the problem? thanks again
I purchased the 955 in July and had problems since, I swapped it with a new one after trying all the tricks and hacks suggested by the Garmin Support and by the forum and had the same issues.Ultimately I came to the conclusion (also backed by hundreds of users having the same issue) that the battery's life is rubbish and it's not what was it's advertised and that the watch just need to charged very ooften.So if I didn't come up with a more helpful solution.
Another one from me...14.20 is now causing significant battery drain. I recharged the 955 this morning and since then, with only the OHR and BT on (no activities and only one 40 minute walk) the battery life is as follows:
Since last charge: 1.4%/hr drain, 33% per day drain, 3.03 days per charge.
The watch and GC are syncing almost every 5 seconds again. The next thing I am going to try is to disable automatic sync (by disabling BT) and see what happens.
Do Garmin support read the forums? If not I'll have to submit a ticket through UK support.
SpO2 on Demand, turn off Phone Sync/BT and restart the watch and see how the battery behaves just as a dumb watch. If it is the same, send it back for a replacement/refund. If it looses 4-6% per day...that is OK so I would suggest a test on the new firmware when available. If afterwards happens the same - send it back as I will if the problem not resolved.
Almost a year with that problem, but it did not happen on some later version of 11 (when it was solved draining by earlier GPS activity) or early v12 of firmware if I recall correctly.