Battery Degradation and EC Misreporting on Acer Nitro ANV15-41 (BIOS V1.18)

FCC

Model Name : Acer Nitro ANV15-41 (BIOS V1.18)

Dear Acer Support,

I am experiencing abnormal battery degradation and misreporting on my Acer Nitro ANV15-41 laptop after updating to BIOS V1.18. My battery shows a wear level of 10.1% after only 2 full charge cycles, and the cycle count remains undefined. I have performed full calibration (0% drain to 100% charge), reinstalled the battery driver, and rebooted the system. Despite these steps, the wear level remains unchanged.

The battery report also logs a “Battery changed” event on 2025-10-13, although no physical replacement occurred. This was triggered by a driver reset, confirming EC-level misreporting. Additionally, battery life estimates and FCC readings are erratic, and the battery capacity history shows a steady decline from 55.1 mWh to 52.8 mWh within days of normal use.

I have reviewed multiple reports from other users with the same model and BIOS version experiencing similar issues. One such case is documented here:
Acer Community Thread – ANV15-41 Battery Dropping Rapidly

These symptoms suggest a firmware or EC-level fault rather than normal battery wear. I request a battery replacement under warranty or guidance on an EC/BIOS fix if available.

Ayana1

Hi @FCC ,

Thanks for the detailed report — this definitely sounds like an EC (Embedded Controller) misreporting issue rather than genuine battery degradation, especially since the “Battery changed” event appeared without hardware replacement.

A few things you can try before pursuing warranty service:

1. Perform an EC reset – Disconnect AC, hold the power button for 30 seconds, then reconnect and boot.
2. Rollback BIOS (if available) to V1.17 to confirm whether the issue started with V1.18.
3. Check with Acer Care Center → Diagnostics → Battery Health — see if readings differ from Windows’ powercfg /batteryreport.
4. If the misreporting persists, open a support ticket referencing this thread and request escalation for EC recalibration or BIOS patch confirmation.

Several users have seen similar issues post-V1.18, so Acer may need to issue a firmware correction.

— Brown_