[Sony Xperia 1 V] Haldi4803:
Android 14 Batterylife​

Batterylife on Android 14 seems okay.

As always.. if you don't use your phone you get decent batterylife -.-

But now you don't have standard Battery monitoring, but instead have a "Daily usage" So no more intricate line detailing when what happened, but you can select each segmet separately and check what used battery in this 2hour segment.

View attachment 6034109

At least Bugreports and Batteryhistorian still work :)

View attachment 6034110

Duration: 101h44m55.648s

Aggregated Checkin Stats:
Metric | Value
Screen Off Discharge Rate (%/hr) | 0.60 (Discharged: 59%)
Screen On Discharge Rate (%/hr) | 5.33 (Discharged: 20%)
Screen On Time | 3h45m19.914s
Screen Off Uptime | 6h10m54.984s
Userspace Wakelock Time | 3h35m15.837s
Sync Activity | 4m11.601s (108 times)
JobScheduler Activity | 1h28m22.296s (2866 times)
App Wakeup Alarms | 1043 times
CPU Usage | 3h28m22.514s user time, 4h44m5.247s system time
Kernel Overhead Time | 2h35m39.147s
Kernel Wakelocks | 4h55m10.711s (396112 times)
Wakeup Reasons | 1h25m6.084s (30156 times)
Mobile KBs/hr | 12144.02
WiFi KBs/hr | 30250.04
Total WiFi Scan Activity | 2m27.319s (50 times)
Total WiFi Full Lock Activity | 0
Mobile Active Time | 27h38m59.336s
Signal Scanning Time | 1m34.831s
Full Wakelock Time | 26m12.716s
Interactive Time | 3h40m47.399s
Phone Call Time | 0
Device Idle Mode Enabled Time | 57h17m4.048s
Device Idling Time | 57h29m50.96s
Total GPS Use | 0 (0 times)
Wifi Power Usage | 0.00%/hr, 0.00% total
Wifi Transfer Time | 0
Wifi Idle Time | 0
Bluetooth Power Usage | 0.00%/hr, 0.00% total
Bluetooth Transfer Time | 0
Bluetooth Idle Time | 0
Camera Use | 2m47.185s (22 times)
Flashlight Time | 0 (0 times)
Modem Transfer Time | 0
Modem Idle Time | 0

Taking a closer look at these:

Screen Off Discharge Rate (%/hr)	0.60 (Discharged: 59%)
Screen On Discharge Rate (%/hr)	5.33 (Discharged: 20%)
Screen On Time	3h45m19.914s
Screen Off Uptime	6h10m54.984s

The full Doze Screen off discharge rate is around 0.3-0.4% /hour so an Average 0.6% /hour isnt that bad.

As said before i rarely used my phone during this time, and when i did it was to quickly browse something or messenger apps. As you can see in the 5.33% /hour screen on Discharge. That's way too low. Normally thats around 8-10% for heavy usage.

From the almost 102hours the 3h45min SoT is barely 3.6% and the Screen off Uptime 6h10min is only 6%.

Going by the Wakelocks there is nothing out of the ordinary there:

Userspace Wakelocks:
Ranking | Name | Uid | Duration / Hr | Count / Hr | Total Duration | Total Count
0 | RADIO : RILJ_ACK_WL | 1001 | 50s48ms | 222.62 | 1h34m1.33s | 22651
1 | com.sonymobile.providers.media : *job*/com.sonymobile.providers.media/.job.OptionalAllSyncJob#2000 | 10241 | 24s982ms | 0.04 | 45m3.462s | 4
2 | com.sonymobile.telephony.extension : HookMsgTunnel | 10324 | 10s911ms | 0.13 | 19m47.261s | 13
3 | ANDROID_SYSTEM : deviceidle_maint | 1000 | 8s613ms | 1.48 | 19m36.496s | 151
4 | com.maxmpz.audioplayer : AudioMix | 10414 | 3s858ms | 0.02 | 8m56.784s | 2
5 | RADIO : *telephony-radio* | 1001 | 2s115ms | 684.11 | 8m3.407s | 69607
6 | com.aspiro.tidal : AudioMix | 10440 | 1s740ms | 0.00 | 6m34.895s | 0
7 | com.aspiro.tidal : ExoPlayer:WakeLockManager | 10440 | 1s738ms | 0.00 | 6m34.461s | 0
8 | BLUETOOTH : StartingObexMapTransaction | 1002 | 1s233ms | 0.07 | 5m0.002s | 7
9 | org.thoughtcrime.securesms : *overflow* | 10411 | 1s222ms | 1.99 | 4m11.961s | 202

Kernel Wakesources:
Ranking | Name | Duration / Hr | Count / Hr | Total Duration | Total Count
0 | rmnet_ctl | 34s867ms | 255.89 | 59m7.726s | 26037
1 | IPA_CLIENT_APPS_WAN_LOW_LAT_CONS | 33s413ms | 259.09 | 56m39.797s | 26362
2 | IPA_CLIENT_APPS_LAN_COAL_CONS | 28s5ms | 258.68 | 47m29.511s | 26320
3 | rmnet_ipa%d | 20s650ms | 116.86 | 35m1.115s | 11890
4 | IPA_CLIENT_APPS_WAN_COAL_CONS | 19s239ms | 84.10 | 32m37.562s | 8557
5 | 898000.qcom,qup_uart | 11s908ms | 3.16 | 20m11.631s | 322
6 | hal_bluetooth_lock | 11s831ms | 2.49 | 20m3.856s | 253
7 | alarmtimer.0.auto | 3s669ms | 1.83 | 6m13.388s | 186
8 | qcom_rx_wakelock | 1s865ms | 21.08 | 3m9.833s | 2145
9 | PowerManagerService.Broadcasts | 1s631ms | 2.48 | 2m45.956s | 252

Kernel Wakeup Reasons:
Ranking | Name | Duration / Hr | Count / Hr | Total Duration | Total Count | Show Count vs Time
0 | Abort: Pending Wakeup Sources: [timerfd] | 6s976ms | 114.17 | 11m49.881s | 11617 |
1 | 241 ipa | 10s840ms | 59.36 | 18m22.984s | 6040 |
2 | Abort: Last active Wakeup Source: qrtr_ws | 1s69ms | 32.83 | 1m48.801s | 3340 |
3 | Abort: Pending Wakeup Sources: IPA_CLIENT_APPS_LAN_COAL_CONS | 10s894ms | 25.69 | 18m28.476s | 2614 |
4 | Abort: Pending Wakeup Sources: IPA_CLIENT_APPS_WAN_LOW_LAT_CONS rmnet_ctl | 9s995ms | 24.72 | 16m57.053s | 2515 |
5 | 266 pm8xxx_rtc_alarm | 391ms | 12.04 | 39.813s | 1225 |
6 | Abort: Pending Wakeup Sources: IPA_WS | 2s628ms | 6.94 | 4m27.424s | 706 |
7 | Abort: Pending Wakeup Sources: [timerfd] [timerfd] | 558ms | 5.08 | 56.802s | 517 |
8 | Abort: Last active Wakeup Source: ta_qmi_wakelock | 1s77ms | 2.16 | 1m49.612s | 220 |
9 | Abort: Callback failed on alarmtimer.0.auto in platform_pm_suspend.cfi_jt+0x0/0x8 returned -16 | 1s838ms | 1.82 | 3m7.101s | 185 |

i think i accidently manually triggered a media rescan somehow.... not entirely sure.

As you can see the first 12 hours used WAY more Battery than later.... You can also see that the "Abort: Pending Wakeup Sources: [timerfd]" and "Abort: Last active Wakeup Source: qrtr_ws" are happening way more often in that time frame.

View attachment 6034113View attachment 6034118

I was connecting a Bluetooth Meat Thermometer for Cooking, with BLE Scanning (Bluetooth low Energy) and WiFi Multicast was activ. Also Mobile Signal Strength was REALLY bad. (Fully red on the Graph).

View attachment 6034117

IPA Wakeups are related to Modem, as clearly seen in the middle, the deep gap comes from the Deep Doze with WiFi on.

View attachment 6034121

View attachment 6034119

View attachment 6034120

From a battery viewpoint it doesn't really mater if it's connected to WiFi or Mobile Network.

At both Deep Doze Times i had around 0.3-0.4%/hour battery drain.

On the other side when WiFi is active there are other Wakelocks occuring.

View attachment 6034123