Beta 20.51 battery Logging only

Try go to settings / widgets / add

and scroll down to battery widget and add it to your list. 

I’m really surprised to see the lack of interest in this “battery debug version” from both garmin (No sticky thread) can some one pleas help me tagging garmin employees

and

from the many peoples posting battery complaints after ver 19.20.

if we in this community doesn’t help garmin to run this “beta” and collect info for them how can they solve this issue of loosing 10% of total battery stamina?

I hope that I have not offended anyone by posting this.

Quite a good point, the "many people" may possibly not even know this is out, missing the usual sticky thread in the forum...

My results and analyse, ?? - means what is this
Because I use only my own CIQ WF I exactly know what it does:
- during low power, practically nothing only one check if should draw AOS - seconds/colons, but I don't use AOS, so during low power only full draw every minute;
-after wrist gesture - about 10 full drawing;
I'm not good "case  for battery saving" because I all the time testing my apps, download new version, everyday activity with/without  GPS. But for long time (with the same style of day) I had 4/5 days on my one charging, Now is rather 2/3 days. My WF's users  clime they don't' charge battery even 7 days.

3-8-2022 17:53:59 UTC
Software: 20.51
Sensor Hub Version: 11.01
Wi-Fi Version: 2.60
GPS Version: 5.30
ANT/BLE/BT: 6.15
Time on since last charge:        2d:21:49:22 (251362 sec)
Time with backlight on:           02:03:41 (7421 sec)
Time with GPS on:                 02:12:56 (7976 sec)
Time with OHR active scan on:     03:21:22 (12082 sec)
1. HR is reading rather good and practically every second
2. SpO2 - problems
- Many times I can see old data 140', 260' - so it means watch tries count SpO2 without sucess
- System widget, many times progress circle doesn't start for minuets even it starts measuring last long time and often without success
SpO2 - can drain battery.

Time with ANT active scan on:     00:03:56 (236 sec)
Time with BLE active scan on:     00:03:56 (236 sec)
What does "scan" mean? Looking for new devices or trying find paired?
I have only one paired device - phone.
I don't have any ANT device so why watch try to scan for it? Without any permission and without any my action.
So it can mean it's looking for new devices without  any my action and permission- security issue.
Only 236s but if it costs a lot of energy it can influence o draining.

Time with WiFi active:            00:00:00 (0 sec)
Time with GCM connected:          1d:00:41:30 (88890 sec)
My WF uses internet connection - every half hour when BT is on.
I'm not sure how exactly BT connection runs. For me should be active and passive (standby) connection and of course no connection. Active should be only when I need exchange data:
- by action initialised by watch (looking for phone, sending exercise, sending/receiving data to the Internet) but  it can happen only after some action (e.g. saving activity) not all the time
- when I look on Connect app (android) it updates data every second to show current HR/breath etc. I hope there is no active communication when phone is locked  or Connect is in background - nobody can see data so communication should be passive
- when Connect wants to send something (notification, data etc) it should wake up connection to active and exchange data
BT connection can drain battery even there is need to exchange data.


Time with headphones connected:   00:00:00 (0 sec)
Time with music playback on:      00:00:00 (0 sec)
Time with pulse ox on:            2d:21:49:22 (251362 sec)
Time recording activity:          03:04:41 (11081 sec)
Time playing videos:              00:00:00 (0 sec)
Time WD on:                       2d:21:49:22 (251362 sec)
??

Smart notifications count:        15
Time on Native Watchface:         00:00:00 (0 sec)
Time on TVM Watchface:            2d:18:00:24 (237624 sec)
?? probably time when watch face is in foreground

Runtime Assert Counter:           0
??

BTM in fast interval:             01:03:39 (3819 sec)
?? high power?

Move alert count:                 0
NOT TRUE, I have had a lot of "Move message"

Gesture up count:                 1683
Time in Do Not Disturb:           22:29:13 (80953 sec)
Time in Livetrack:                00:00:00 (0 sec)
Time powered off:                 29d:16:49:24 (2566164 sec)
Is it the time from last power off? If yes - not true, I've powered watch few day ago.

Device info when plugged in:
Battery percentage:           8.642341%
Current backlight mode:       3
Current backlight brightness: 70%
Current backlight timeout:    8
Current backlight timeout in activity:    8

You can find the widget Device Usage in Widget section

My hourly usage on 20.51, terrible battery drain on 6s, as bad as 18% drop in one hour. Any suggestions or ideas?


----------------------------------------------------------------------
3-15-2022 03:22:30 UTC
Software:      20.51
Sensor Hub:    11.01
GPS:           5.30
ANT/BLE:       3.00

***STATS SINCE LAST CHARGE***
Time on since last charge:    03:00:22 (10822 sec)
Time in low power:            00:49:43 (2983 sec)
Time with backlight on:       00:07:45 (465 sec)
Time with GPS on:             01:48:41 (6521 sec)
Time with OHR active scan on: 00:00:00 (0 sec)
Time with ANT active scan on: 00:00:44 (44 sec)
Time with BLE active scan on: 00:00:44 (44 sec)
Time with GCM connected:      00:42:12 (2532 sec)
Time with Pulse Ox on:        00:00:00 (0 sec)

NOTE: First usage log after powerup!
No VEXT detected.
Battery percentage:           92.785156%
Current CDP power mode:       1
Current backlight mode:       3
Current backlight brightness: 20%
----------------------------------------------------------------------
3-15-2022 04:22:30 UTC
Software:      20.51
Sensor Hub:    11.01
GPS:           5.30
ANT/BLE:       3.00

***STATS SINCE LAST CHARGE***
Time on since last charge:    04:00:22 (14422 sec)
Time in low power:            01:23:44 (5024 sec)
Time with backlight on:       00:11:50 (710 sec)
Time with GPS on:             02:05:17 (7517 sec)
Time with OHR active scan on: 00:16:36 (996 sec)
Time with ANT active scan on: 00:09:32 (572 sec)
Time with BLE active scan on: 00:09:28 (568 sec)
Time with GCM connected:      00:42:12 (2532 sec)
Time with Pulse Ox on:        00:00:00 (0 sec)

No VEXT detected.
Battery percentage:           74.460938%
Current CDP power mode:       0
Current backlight mode:       3
Current backlight brightness: 20%
----------------------------------------------------------------------
3-15-2022 05:22:30 UTC
Software:      20.51
Sensor Hub:    11.01
GPS:           5.30
ANT/BLE:       3.00

***STATS SINCE LAST CHARGE***
Time on since last charge:    05:00:22 (18022 sec)
Time in low power:            01:43:46 (6226 sec)
Time with backlight on:       00:15:49 (949 sec)
Time with GPS on:             02:41:33 (9693 sec)
Time with OHR active scan on: 00:52:52 (3172 sec)
Time with ANT active scan on: 00:10:29 (629 sec)
Time with BLE active scan on: 00:10:47 (647 sec)
Time with GCM connected:      00:42:12 (2532 sec)
Time with Pulse Ox on:        00:00:00 (0 sec)

No VEXT detected.
Battery percentage:           59.488277%
Current CDP power mode:       2
Current backlight mode:       3
Current backlight brightness: 20%
----------------------------------------------------------------------
3-15-2022 06:22:30 UTC
Software:      20.51
Sensor Hub:    11.01
GPS:           5.30
ANT/BLE:       3.00

***STATS SINCE LAST CHARGE***
Time on since last charge:    06:00:22 (21622 sec)
Time in low power:            02:41:58 (9718 sec)
Time with backlight on:       00:16:19 (979 sec)
Time with GPS on:             02:41:33 (9693 sec)
Time with OHR active scan on: 00:52:52 (3172 sec)
Time with ANT active scan on: 00:10:29 (629 sec)
Time with BLE active scan on: 00:10:47 (647 sec)
Time with GCM connected:      00:42:12 (2532 sec)
Time with Pulse Ox on:        00:00:00 (0 sec)

No VEXT detected.
Battery percentage:           47.554688%
Current CDP power mode:       2
Current backlight mode:       3
Current backlight brightness: 20%
----------------------------------------------------------------------
3-15-2022 06:44:11 UTC
Software:      20.51
Sensor Hub:    11.01
GPS:           5.30
ANT/BLE:       3.00

***STATS SINCE LAST CHARGE***
Time on since last charge:    06:22:04 (22924 sec)
Time in low power:            03:03:21 (11001 sec)
Time with backlight on:       00:16:41 (1001 sec)
Time with GPS on:             02:41:33 (9693 sec)
Time with OHR active scan on: 00:52:52 (3172 sec)
Time with ANT active scan on: 00:10:29 (629 sec)
Time with BLE active scan on: 00:10:47 (647 sec)
Time with GCM connected:      00:42:12 (2532 sec)
Time with Pulse Ox on:        00:00:00 (0 sec)

Detected external power source!
Battery percentage:           42.750000%
Current CDP power mode:       2
Current backlight mode:       3
Current backlight brightness: 20%

Any idea how to interpret the following pwrstat.csv?

Really hard to conclude anything from this, it takes general knowledge on ARM processor power management and knowledge of the architecture of the system. See Garmin Fenix 6x Pro disassembly to get an idea of what is inside. FlexIO may refer to NXPs FlexIO module that's present the main Kinetis K28F MCU. UART, SPI, IIC are communications, DMA is memory access. DEEP is deep sleep. CPUWAIT generally means waiting for I/O. 

The timestamps are in seconds and often 1 hour apart, but more or less spaced apart also occurs. I made a graph of it once, adjusted on time, and could see a clear 24-hour pattern of usage (nighttime, activities). But that was for amusement only - no idea what would be 'normal' or 'abnormal'.

I would recommend you to send your data in an email to [email protected]

My last reply was removed.

please email beta team on email address mentioned in notes in download links.