new powermanager and battery

[Hervé Fache]

Hallo Sebastian,

FWIW I have two batteries in my 'old' laptop, so if I can help, I'll
be happy to. Note that I do not necessarily have much time to do
things, but I can try. I have some code knowledge, so if you intriduce
me to your code, I can at least help debug and point to the problems
if any.

Ideally, the user (me) wants to know about 15 minutes from end of
battery that it's dying, so she can hibernate now and still have a bit
left later to restart and double check the meeting room number... 5
minutes from the end, she probably wants a big warning saying she
should hibernate NOW!

About 1 minute from the game over, the computer could decide to
hibernate not risk losing data, but maybe we could not force anything
on the user in case she needs as much time as possible, in which case
remounting the filesystems 'sync' might be a better option (I am
thinking of a researcher collecting data for example: the more the
better).

Hoping that helps more than confuses the matter,
Hervé.

On 8/30/06, Sebastian Kügler <sebas at kde.org> wrote:
> As you might have noticed, development of the new powermanagement tool is
> going quite well.
>
> There are two issues, however, I'm currently running into:
>
> * I do not own a second battery for the Ultrabay of my notebook, so I cannot
>   implement support for this unfortunately. If someone wants to help out, I
>   can assist with the code. If someone wants to send me a battery for the
>   Ultrabay, that welcome of course, too. :-)
>
> * HAL supports two levels of 'batterypower is low', one's called
>   battery.charge_level.warning, the other one is battery.charge_level.low.
>   From my measurements, the "warning" level is reached when 10 minutes of
>   battery life is left, "low" is reached when the lights will go out in less
>   than about half a minute. My configuration would hibernate at low level, but
>   it might not come that far due to measurement skew, or die while
>   hibernating. Therefore I'm pondering to not use the HAL provided values
>   here, but have the user set those values up. There, we're running into
>   another problem, of course. Using a treshold value of N minutes can be
>   inaccurate due to power consumption changing over time. Using HAL's
>   battery.charge_level.rate interpolates that a bit. Using a treshold of N mWh
>   is nice for geeks, but has little value to those that are not arithmetic
>   geniuses and know how much their hardware drains now and in the next
>   minutes.
>
> Thoughts?
> --
> sebas
>
>  http://www.kde.org | http://vizZzion.org |  GPG Key ID: 9119 0EF9
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> Of course, the best way to get accurate information on Usenet is to post
> something wrong and wait for corrections. - Matthew Austern
>
>
>
> --
> kubuntu-devel mailing list
> kubuntu-devel at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
>
>
>
>


-- 
In a world without walls and fences, who needs Windows and Gates?