Quote:
Originally Posted by geek1011
There shouldn't be anything in NM which could cause it...
|
UPDATE: All seems still to be well now, battery went overnight from 92% to 91% with NM active which is not bad at all.
I did inspect the syslog for any "strange" behavior but found none.
BACKTRACING: what might have happened?
At the moment I wanted to install NM, I got a nasty surprise: my Libra 2 started to install 4.31, likely caused by a sneaky download thereof during my adventures with Bluetooth (BT/WIFI pairing). I let it go-on, an auto reboot (1) followed accordingly, I checked if it now really was on 4.31 and unfortunately it was.
So I quickly connected to the PC, side-loaded 4.30, safely disconnected, got the according auto reboot (2) and checked if 4.30 was now active: it was.
Reconnected to the PC, side-loaded NM 0.5.4, safely disconnected, got the according auto reboot (3) and checked for the expected NM menu. It was there and seemed to function. I did some testing and reading, noticed the battery was on 47% and called it a day.
The next morning the battery indicated 17% left and did quickly reached 10% (triggering charge warning). So I charged to full 100% and then the quick discharging occurred as mentioned in my other posts.
I reasoned that it might have to do with NM, so I uninstalled it with the reboot (4). From then on the discharging stopped.
RETROSPECT:
I think that the changed FW 4.31 & 4.30 & NM installments left some free running process of which we never will know what. The uninstalling of NM caused a reboot, which might have killed that run-away process and place the Libra 2 in a stable situation again. This caused my idea that NM might be the culprit. However the re-install of NM did not induced any new troubles as far as I can see now, so it seems to me that it is unlikely that NM really was causing the problems.
For the moment I leave the NM syslog dump option in place and keep on monitoring for possible future battery draining issues.
Thanks for the pointers geek1011
