Comment 85 for bug 135548
Revision history for this message
| Anoop P B (anoop-pb) wrote Re: [Gutsy] Action on critical battery isn't triggered - regression | #85 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
This works for me now on Gutsy with all updates. I have use_profile_time and use_time_for_policy both enabled (default).
I also raised the time thresholds (low, critical, action) to 1560, 960 and 660.
For me, the solution was to go through a couple of charge/discharge cycles without letting it drain through. This helped it to build up a profile of my battery. I think this point should be mentioned somewhere in g-p-m so that the user knows that it doesn't work well until a profile is built up. Alternatively, the system should use a higher threshold value by default (err on the safe side) until a profile is built up.