What do you mean by "battery stats"? Anyway, when calibrating to *lower* capacity that your LMD/ILMD (like, in your case, single polarcell, from 2000+ mAh), unplugging at green led should be OK. If you would be, OTOH, calibrating from lower to higher capacity, you should monitor via bnf or bq27200.sh and count minutes*mA (like written in calibration post), to avoid getting hit by limit of calibration capacity change.
---

From "different barrel" - I've found some problems with BME + bq27x00_battery combination, when device is plugged in and charging ended already. Nothing serious - it just doesn't work then, due to Pali's bad design decisions about bq27x00_battery sysnodes (When charging ended, bq27x00_battery stops exporting some sysnodes, causing read_erro,r when trying to access them).

Sadly, same happens when battery is uncalibrated and bqx00_battery loaded - for same reasons. Pali seems confident into keeping it that way to maintain compatibility with upstream bq27x00_battery, which I see as plain wrong (sysfs nodes should *always*.report what hardware gives, not censor data, due to someone's idea that it may be good thing).

Workaround for that is to unload bq27x00_battery, when device is not calibrated. Due to it's being PITA, I plan to rewrite BNF again, to only use i2cget, even when bq27x00_battery is loaded - fortunately, I2C_FORCE_SLAVE allows for safe accessing i2c values of bq27x00 chip, even if bq27x00_battery.ko access them already (due to bq27x00_battery module reads being atomic).

This should fix both problems mentioned above.

/Estel