Xiaomi 14/15 Ultra Severe Battery Drain on HyperOS 3 Android 16

Some Xiaomi 14 Ultra and 15 Ultra devices are reporting heavy battery drain right after updating their Xiaomi EU ROM to HyperOS 3 Android 16 build. The battery idle drain is reported to be around -1.15W or 2.6% – 3% per hour on both these devices. The forum member bear0610 did a detailed investigation and found out that the system is trapped in several infinite error loops at the Hardware Abstraction Layer (HAL) and System Linker level, preventing the SoC from entering Deep Sleep. Here are his key findings on this matter.

Xiaomi 14/15 Ultra Severe Battery Drain on HyperOS 3 Android 16

Xiaomi 14 ultra 15 Ultra Severe Battery Drain on HyperOS 3 Android 16 - 1
  1. Universal Sensor HAL Loop (14U & 15U): Constant repetition of libsensor-parseRGB: CWB NotifyCWBBufferDone error 0. This driver-level communication failure keeps the CPU awake via continuous interrupts.
  2. Display HAL Failure: Frequent HwcComposer: getLuts failed Status(-129, EX_TRANSACTION_FAILED). The display composer fails to access color LUTs, causing high overhead for system_server.
  3. Critical Linker Errors (Specific to 15U): Logcats show F linker: CANNOT LINK EXECUTABLE and cannot locate symbol “__android_log_error_write”. This indicates fundamental binary incompatibility within the system libraries on the 15U A16 build.
  4. UI Animation Deadlocks (Specific to 15U): Over 1,700 occurrences of TransitionChain and MultiSpringDynamicAnimation errors (ERROR Not Found Bundle Radius) were detected within minutes. This creates a massive CPU load during screen-on time.
  5. Security/TEE Bottleneck: Frequent Keymaster status: -28 errors (resource exhaustion) across all A16 units, suggesting a conflict between current Keystore2 patches and the Android 16 TEE requirements.

Do note that all these issues were noticed on a non-rooted Xiaomi EU ROM. Moreover, according to the user, executing stop logd hides the messages but does not reduce power consumption , confirming that the battery drain is caused by hardware interrupts and driver-level retries. The data suggests that the current Vendor Blobs provided by Xiaomi for Android 16 are not yet compatible with the system framework.

The Xiaomi 14 Ultra and 15 Ultra suffer from identical HAL loops, while the latter build is further compromised by Linker symbol mismatches. The user performed these tests on Android 15 as well; however, these issues were not there, further cementing his theory about the regression in the Android 16 adaptation.

Although this is a detailed study done by forum member bear0610, and he has done a commendable job, however, this issue hasn’t been echoed by many users till now. We will wait and see if more users come with this issue and then act accordingly. Do check out this space after a few days, as all the developments will be posted here.

Google preferred - 2

(Cancel Reply)

Δ