Hey all, I’ve recently looked into logs on my Fairphone 5 (/e/OS version 2.9t, official), to see if I can save some more battery. I’ve found, that every 3 seconds in my log there are 3 failures from Wifi related services:
[2025-05-05 17:48:04.417 wifi:1005:1005 E/WifiHAL]
get_wifi_interface_info: QCA_WLAN_VENDOR_ATTR_LL_STATS_IFACE_INFO_TS_DUTY_CYCLE not found
[2025-05-05 17:48:04.417 wifi:1005:1005 E/WifiHAL]
nl80211: requestResponse->nl_recvmsgs failed: -5
[2025-05-05 17:48:04.419 1000:19396:19588 E/WifiVendorHal]
getWifiLinkLayerStats_1_6_Internal(l.1199) failed {.code = ERROR_INVALID_ARGS, .description = }
Also every 1-5 seconds (there is no such regularity) I get failures:
[2025-05-05 17:48:02.521 root:0:0 E/[ C3] [soft_i][0x31d90d3987c][17]
48:06.043086] wlan: [0:E:QDF] htc_rx_completion_handler: Received initial wake up
[2025-05-05 17:48:02.524 root:0:0 F/[ C3] [soft_i][0x31d90d48dd0][17]
48:06.046357] wlan: [0:F:WMA] WLAN triggered wakeup: BPF_ALLOW (39), vdev: 0 (STA)
Is this some misconfiguration on my side? Internet is working normally, speed is OK. I see almost no other errors of failures. These two kinds of errors generate like 90% of my log, which I think is not normal. Any idea how to approach fixing those?
I’m seeing a similar thing on my OnePlus phone with /e/os and on my Motorola phone with stock Android. Using logcat *:e I get one or two of the same errors that click off every few seconds. Everything works so I figure it’s just the nature of beast. I don’t worry about it too much since everything is working, but I would be happier not to see spurious errors.
As far as the impact on battery consumption, I don’t believe that’s an issue. The CPU still runs at a very low clock speed in deep sleep and I don’t think it’s waking up, but it would better not to see any activity.
Still I think that requesting lock to write to log every 3 seconds is some work, and even if just annoying.
Might qcacld-3.0: Add time slice duty cycle in wifi_interface_info · LineageOS/android_kernel_fairphone_qcm6490@982e25d · GitHub be related this? If I look at it correctly, even that this is 3 years old commit, it is in LineagOS 21 and up, and 2.9t is based in LineageOS 20, am I correct? Is there possibility to make a feature request to /e/os team to backport this change to older release as well? Is there some procedure? (I’m new on this forum).
EDIT: nope, never minds, seems fairphone 5 kernel has this commit already qcacld-3.0: Add time slice duty cycle in wifi_interface_info (982e25d1) · Commits · e / devices / android_kernel_fairphone_FP5 · GitLab – man, this thing is annoying
1 Like