Driver 2023 — Mediatek

“Then disable it in your device tree.”

At 6:00 AM, she checked the battery graph: . Fixed. Part V: The Gray Zone The fix worked. But it was a “proprietary modification” to MediaTek’s binary-licensed driver—technically a violation of their software agreement.

For the next 14 hours, Lena reverse-engineered the driver’s state machine. She found that mtk_disp_qos_boost() was called by a display IRQ that never fired the corresponding release. The fix was six lines of code: mediatek driver 2023

/* * Fixed: December 2023. * If you are reading this in 2025 and battery drain returns, * look for new PM_QoS votes. They multiply like rabbits. * - Lena Wei, last commit of the year. */ And somewhere in MediaTek’s Hsinchu office, Dr. Chen quietly merged Lena’s fix into the 2024 driver branch, pretending he had written it himself. Because in the world of chipset drivers, credit is fleeting—but a working phone is forever.

It was a zombie driver. Alive, breathing, and eating battery. At 8:13 AM, Lena joined a video call with MediaTek’s driver team in Hsinchu. On the screen: a balding senior architect named Dr. Chen, who had authored the original sleep controller in 2019. “Then disable it in your device tree

She compiled the kernel. Flashed it to a test device. Let it sit overnight.

For two weeks, the team blamed the battery vendor. For another week, they blamed the Android 14 beta. But Lena knew the truth: the kernel was lying to them. But it was a “proprietary modification” to MediaTek’s

Lena wrote a careful email to her CTO: “We can ship this patch as a ‘vendor enhancement.’ MediaTek does not need to know. But if they ever audit us, we lose support.” The CTO, a pragmatic woman named Priya, called her back in 30 seconds.