Hi RehabMan.
If you can give a clue on my test please.
Tested on debug kext.
What is happening is this.
On boot the batteries check does not start. I need to "force" it to wake/start working.
Even with power unplugged at boot the status % remain always at 100 (or whatever it is) and only playing with Energy Saver specially the Dim display checkbox start working. And it using, being unplugged, the powered conf in ES a not the battery one.
The sooner it starts everything seems to work OK: the % start decreasing or increasing on charge, the display dims or undims, it applies correct config being or on on batteries or plugged etc.
What I see in the log.
The first thing I notice is:
ACPIBatteryManager: clearBatteryState: do_update = false
this at boot. I do not know if this does not start the battery checking.
There is a way to force this to true if it has any meaning? Checked config.plist in the kext with no luck.
Also I can find this:
ACPIBatteryManager: entering addBatteryManager(<private>)
{"restrictedMode":false,"pushServiceConnected":false,"batteryData":{"wasConnected":false,"charged":false,"level":-1,"connected":false,"chargerType":"kChargerTypeUnknown"},"thermalLevel":-1,"batterySaverModeEnabled":false,"reachability":"kReachabilityLarge","airplaneMode":false}
where kChargerTypeUnknown can be something wrong?
The ACPI_BIF it is alway 13 plugging or unplugging the power:
ACPIBatteryManager: setBatteryBIF: acpibat_bif size = 13
Doe not change in any case. Also in the log state changing (plugged or not)clearly generates log but with no big changes in the fields logged.
So what I suppose that for some reason battery status does not start at boot and I need to force starting it.
After that it is working OK.