Battery drain fast

Battery drain is still not fixed in 16.70. One hour run consumed 12% of battery. GPS only, WiFi off, Oxymeter off.

Are you using any external sensors? I'm having battery drain not during activity if a cadence sensor is paired but not reachable. The watch is permanently scanning for the sensor and the search never times out to "not connected"; in this scenario the drain is up to 50%/day. If it unpair the sensor it goes to 10-15%/day... 

Despite sensor paired the drain is crazy. I only have an external HR sensor which I use for running. During my last run the battery went down 20%. It remains high when I walk without the sensor.

Hmm.. but maybe there's something going on. I just had a look, and it looks like my watch is searching for this sensor. While I sit on the sofa watching the news.

No external sensors here. When I downgraded to 15.20 it factory reset my watch so all my settings were wiped. I previously had my C2/PM5 rower as a sensor, but it was set up to only connect when the activity was started (IIRC). No pulse ox, no wifi, bt off at night.  I have GPS+GLONASS enabled, but it was like this prior to the 16.60 update without issue. I went to 16.60, then 16.70beta then back to 15.20 and the battery life on GPS has been horrendous ever since.

6928399 said:

I just had a look, and it looks like my watch is searching for this sensor

Viorel said:

The watch is permanently scanning for the sensor and the search never times out to "not connected"; in this scenario the drain is up to 50%/day

How can you be certain?  Unlike Bluetooth searching, sensors will only try to connect when an activity is started or when you enter sensors and accessories in the settings menu.  Have either of you found a way of determining this outside of the two ways I mentioned? 

i still see quick battery drain but only in watch mode. i now go through 10 to 15% battery a day with no activity, on 6x pro. Ib also noticed that all my ant sensors are "searching" even though iam not in any activity. i don't rremember if that is normal. can someone check? i have a lot of sensors so maybe that's the culprit 

avikoren1 said:

i don't rremember if that is normal. can someone check? i have a lot of sensors so maybe that's the culprit 

I'm not having the excessive battery drain and for years with many different watches anytime I go into the sensor settings any previous paired sensors will attempt to connect, so I believe this is normal. I have two chest straps, a Stryd, Tempe, headphones, cadence and a separate speed sensor paired and they all do this and have always done so.  I was just wondering if there was another way to see if sensors were trying to connect. 

TL;DR - paired sensors can be searched and can stay connected even if not in activity and while not on the Sensors page :)

What is described below is empirical and some assumptions are involved, so take it with a small grain of salt :)
The connection states you can see in the status for a paired sensor are:
- "Not Connected"
- "Searching"
- "Connected"
There is also a "On/Off" toggle that permits/denies the connection to the sensor.

When viewing paired sensors the status goes from "Searching" to "Connected" if the sensor is on and in range OR if a sensor is out of range or turned off the status SHOULD (but doesn't) go from "Searching" to "Not Connected", after a certain timeout expires (probably) - I observed this behavior with BT headphones when they are unreachable the watch eventually stops "Searching" and says "Not Connected", but not with my ANT+/BLE cadence sensor which is always "Searching" and never times out.

In beta firmwares there is a system statistics widget where you can see GPS/ANT+/BLE uptimes.
I already know that when you go to the activities page (but not start an activity) these uptimes start to increment and continue incrementing for about 20 second after exiting the activities page; this shows that the radios can be active without having an activity started.

My biggest assumption is that for some units the ANT+/BLE radios are always on and you can only turn them off completely if you switch to airplaine mode because you can see on the Sensors page the status change to "Airplain mode on".