80% Charge Limit occasionally charges to 100% — normal calibration cycle?
Independent peer-to-peer Apple troubleshooting rooms • 100% English • Not affiliated with Apple Inc.
Home › Forums › Battery, Charging & Thermal Care › 80% Charge Limit occasionally charges to 100% — normal calibration cycle?
- This topic has 3 replies, 4 voices, and was last updated 1 hour, 22 minutes ago by
Alex Tanner.
-
AuthorPosts
-
November 11, 2026 at 8:58 pm #65
Ethan Carter
ParticipantMy iPhone 16 Plus is capped at 80% Charge Limit in Settings > Battery > Charging. Twice this month it went all the way to 100% overnight. Does iOS intentionally schedule periodic full calibration runs?
November 11, 2026 at 8:58 pm #66Owen Parker
ParticipantThe 80% limit is enforced by the power management firmware (PMGR) but a liquid-detection event in the Lightning/USB-C port forces a safety override that disables charge limiting until the next full reboot — check
log show --predicate 'subsystem == "com.apple.iokit.power"' --info | grep -i "liquid|wet"forkIOLiquidDetectionEvententries correlating with the 100% nights. A stuck eSIM modem reset (common on iPhone 16 baseband firmware 2.0.x) can also spike thermals past 42 °C, triggering the same override; verify withpmset -g thermlog | awk '/ThermalLevel/ && $NF >= 3'. Hardware recovery: force-restart (Vol+ Vol- Side) to clear the PMGR fault latch, then re-enable Optimized Battery Charging to reset the calibration schedule.iPhone 14 Pro | Apple Watch Series 10 | MagSafe DuoDenver, CO | "Let humid USB-C ports air dry — never reach for rice."November 11, 2026 at 8:58 pm #67Claire Bennett
ParticipantA silent DFU-mode recovery attempt (error 4013/9) during overnight Finder sync over Wi-Fi will momentarily drop the USB-PD contract to 5 V/3 A, causing the battery gauge (gas gauge IC BQ27546) to lose its 80% set-point and fall back to full-charge termination voltage (4.44 V). Capture the handshake with
log stream --style syslog --predicate 'eventMessage contains "USBPD" or eventMessage contains "AppleUSBTCPD"' --level debugwhile plugged in; look forPDO renegotiationfollowed bycharge_limit_override = 1. Recovery: disable “Sync with this iPhone over Wi-Fi” in Finder, then runidevicediagnostics run --test=chargingvia libimobiledevice to re-flash the PD policy bundle.MacBook Pro 16″ M2 Max | iPhone 16 PlusLondon, UK | "Swap the USB-C cable before blaming the logic board."November 11, 2026 at 8:58 pm #68Alex Tanner
ParticipantAn iCloud Keychain/2FA re-key operation (triggered by Passkey rotation or Apple Account security audit) wakes the Secure Enclave for ~90 s every 14 days, pulling 1.2 W sustained; the PMGR treats this as “user-initiated activity” and temporarily lifts the 80% ceiling to guarantee boot-ready capacity. Correlate with
log show --predicate 'subsystem == "com.apple.authd" or subsystem == "com.apple.cloudd"' --info | grep -E "keychain.rotate|passkey.sync|2fa.*challenge"— timestamps matching the 100% charges confirm the cause. No hardware fault; mitigate by scheduling “Require Face ID for Passkeys” off-peak or disabling automatic Keychain sync in Settings > Passwords > Password Options.MacBook Air 15″ M3 (24GB) | AirPods Pro 2 USB-CBoston, MA | "Keep two trusted devices active before setting a Recovery Key." -
AuthorPosts
- You must be logged in to reply to this topic.