EC Firmware Bug on New Lenovo Laptop: How a Simple Telemetry Freeze Became a Full Firmware Disaster
When you buy a new laptop, the last thing you expect is a firmware disaster — especially one that breaks battery diagnostics on day three. But that’s exactly what happened to me, and it all leads back to one culprit: RYEC26WW, the EC firmware that introduced a new and deeply frustrating telemetry bug.
What makes this worse is that the laptop is physically healthy. The battery is new, the sensors are working, and the hardware is fine. Yet the Embedded Controller is stuck reporting incorrect battery information, and that creates a nightmare for anyone who relies on accurate telemetry.
A Bug Introduced by RYEC26WW
After updating through multiple BIOS versions (RYCN25WW → RYCN26WW → RYCN27WW), one thing never changed:
The EC remained stuck at RYEC26WW.
This version introduced a regression that breaks one specific — but critical — battery parameter:
Full Charge Capacity (FCC) remains frozen.
While other telemetry values update correctly, the FCC number never changes, never recalculates, and never reflects the real battery state.
What Still Works (And What Doesn’t)
One of the most confusing parts of this bug is that it does not freeze all telemetry.
Here’s what still updates normally:
-
Temperature
-
Voltage
-
Battery percentage
-
Cycle count
-
Runtime
-
Power state
-
AC/DC switching
But the Full Charge Capacity, arguably the most important value for determining long-term battery life, is permanently stuck.
This means:
-
Battery health cannot be measured
-
Wear level becomes meaningless
-
Calibration tools fail
-
Lenovo Vantage receives incorrect capacity data
-
Battery-report.html shows static maximum capacity
It’s a subtle bug — but a devastating one.
My Latest Telemetry (Nov 20, 2025)
Here is today’s real data captured from my system:
-
Status: Tidak ada aktivitas
-
Sisa persentase: 83%
-
Sisa kapasitas: 69.92 Wh
-
Kapasitas penuh: 84.24 Wh (frozen value)
-
Tegangan: 16.88 V
-
Suhu: 30°C
-
Akumulasi siklus: 4
-
Produsen: BYD
-
Tanggal pembuatan: 02/07/2025
-
Tanggal penggunaan pertama: 17/11/2025
-
Kandungan baterai: Li-Polimer
-
Kapasitas desain: 80 Wh
-
Tegangan desain: 15.52 V
-
Versi firmware EC: 0008-0056-0100-0008 (RYEC26WW logic)
Everything in this list looks normal — except the one data point that never changes.
What the Battery Report Shows
My uploaded battery-report.html confirms several things:
-
Full Charge Capacity is stuck at 84.24 Wh
-
The EC is reporting the same value across multiple days
-
Cycle count is increasing, proving the battery is used normally
-
Voltage and current readings are functional
-
BIOS updates did not affect EC firmware
This isn’t degradation.
This is EC firmware refusing to recalculate FCC.
Why This Is a Nightmare
This situation is more than just annoying — it’s infuriating:
-
The laptop is brand new.
-
The battery is perfectly healthy.
-
The bug started only after updating to RYEC26WW.
-
BIOS updates do not update the EC.
-
Only a Lenovo technician can perform a full EC reset.
-
FCC freezing destroys the ability to measure real battery health.
-
Diagnostics become misleading and unreliable.
It’s the kind of failure that makes a user feel helpless, because nothing you do in software will fix it.
And that’s exactly why this feels like a nightmare.
What Lenovo Must Fix
This issue will not be solved by Windows updates, Vantage updates, or even BIOS updates.
Lenovo needs to:
-
Release an EC firmware patch after RYEC26WW, or
-
Provide a standalone EC reflasher, or
-
Perform EC resets for affected units
Until then, users like me are stuck with a frozen FCC, broken diagnostics, and a misleading battery report on a brand-new machine.
Final Thoughts
This entire situation could have been avoided if EC firmware updates were properly validated before release. RYEC26WW introduced a regression that affects only one value, but it’s the most critical one for battery health.
My laptop runs fine.
My battery is healthy.
But the firmware makes it impossible to trust anything the system reports.
And yes — this truly is a nightmare.
This article is AI-generated. Check for any mistakes and UMC would refine it with human-made corrections.
Comments
Post a Comment