Battery Drain on Fenix 6X Saphire with firmware 12.20

ANT+ alone cannot fry the battery that fast. Indoors (no GPS) 1h workout with H10 consumes 1-2% of the battery

Since the problem disappears after restart I would suspect GPS remained in active state. Maybe after you stopped/saved activity it somehow remained open in the background and watch is constantly trying to get GPS signal.

The rate it drained for me the other night when I was affected, it was even higher than recording a GPS activity. I'd expect GPS activity to take maybe ~10% an hour, but I dropped from ~96 to 50 in less than 3 hours.

But yea, it's certainly something getting stuck on/running.  It's annoying that it is, for me, a rare bug which means it's hard to understand what triggers it.

Same here. Since upgrading to 12.20 the battery life-time is - even without a lot of GPS related activities - down to 2-3 days. Compared with 7 days before. So far I try not to reset the watch completely as setting it up again takes a lot of time. So still hoping for some fix in the firmware.

It seems I got point what is wrong with fast battery drain since fw update 12.20.

I am CIQ developer, have developed some watchfaces and widget.

Yesterday I recognised fourth time fast batt drain on my f6X Pro Solar, for less than hour drop from 82% to 78%. Previous day was absolutely ok for battery consumptions. When I recognise it watchface was standard one for Solar, digital with solar charging indicator and solar charging graph.

I decided to switch to PONG Watchface https://apps.garmin.com/en-US/apps/35f9d9ba-3242-4e7f-a607-efa2da2f0f94 developed by myself, as I have some theory to check. Sorry, below is some tech specific explanation, I tried to keep it as simple as possible, but you can jump to next paragraph. And...yes, I realised even for 'low power mode' (please do not be confused with Power Saver, it is absolutely different it is what watchface should go after wrist turn timeout, ie after 'high power mode' for wrist turn in some seconds, for my f6X Pro Solar it is 10 sec, watch should invoke watchface to update only once per minute, except some special technics 'partial update' primarily used to draw second hand for analog watchfaces, but this technics is not used for PONG) watchface updated each second what is not normal, and my watchface designed to show animation only for 'high power mode' (wrist turn). Also I tried my other watchface Game of Life, and I continue can see animation for 'low power mode'. Then I switched to other watchface (developed by someone else) and again a realised this watchface continue to update HR each second, what can't be normal behaviour outside 'high power mode'. Then I decided to switch OFF / ON my watch and this negative effect gone. Please remember it happened for me fourth time, and switch OFF / On your watch is just to stop current crazy batt drain and it can happened again unpredictably.

Based on listed, I mostly convinced, since fw update 12.20, sometimes for some unknown reasons watch continue updating watchface each second what causes abnormal battery drain. It can happen for any watchfaces, even to standards. When it started changing watchface doesn't eliminate this negative behaviour. Only OFF/ON watch can temporarily cancel this negative effect.

As I have limited Garmin support in Ukraine, guys, please contact Garmin in your countries to explain to them this case and ask to fix asap with next fw update.

solved

Sorry, not sure I got your point re CIQ version... please rephrase.

Actually, my post is not about CIQ apps (I used some of them to check my theory), it is about firmware 12.20 contains a bug which request each second update for watchfaces, even for watchface which are not require each second update. For any watchfaces. Even for standard out of the box watchfaces.

Bodya said:

firmware 12.20 contains a bug which request each second update for watchfaces, even for watchface which are not require each second update. For any watchfaces. Even for standard out of the box watchfaces

Since I have the fenix / tactix (Aug 2019), I have been using every build in stock WF with always on seconds. No drain for me.

solved

It can happen unpredictably, like few days everything is ok, then in one day batt is completely empty.

I am still looking for correlation what can causes this abnormal behaviour. But reason for drain is every second updates for WF (even for WF without each second update design).