© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
update-
Still having problems with this, although a lot has been changed recently in the affected components.
First tried some of the packages in Lucid to see if that would help, but no joy.
Then upgraded to Lucid Alpha completely and checking in for updates at least twice a day.
The problem still comes and goes. I think I've noticed some sort of pattern:
- if I plug in the charger when the battery is still over 10%, it tends to start charging -not always-.
- if the battery is under 10% (I prefer to go as low as 3-5%), plugging in the charger -usually- takes me straight to the 'battery full' status
- if I then unplug and re-plug the charger, I get the 'critically low' message and the pc shuts down, no matter what.
When rebooting after an unexpected shutdown ('battery critically low') I have seen in history/statistics that the 'rate' shows spikes up to 500W or so. Of course that would calculate to a remaining battery capacity of only seconds. The normal rate for this laptop is about 20-50W, no more.
Could it be that there is an error in handling the charge or rate inputs, multiplying the rate by 10 ?
- if the battery is reported as 'fully charged' but in fact is quite empty, after a while it shows a normal increase in cell charge, but only to about 60-80% after which it stabilizes. This graph is drawn in green (charged).
When the battery status is changed to 'charging' again (don't really know what triggers that) the cell charge goes up further to 96% or more and then jumps to 100% / fully charged.
Also, when the battery is reported to be in 'fully charged' state while it is not, I see a new error when booting. This is my BIOS telling me the charger could not be identified (oh?) and therefore the battery may not be charged properly.
Does this have to do with the interaction between the embedded system in the battery, the bios/hw on the motherboard and the way this is managed by devicekit-power and/or gnome power manager?
I do not know much about the more intimate conversation between these pieces of my pc.
Let me know if I can do something else to help you find the cause of this.
cheers
Tom