From: Alexey Starikovskiy <aystarik@gmail.com>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: hal@lists.freedesktop.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: kpowersave stuck at battery charging
Date: Wed, 02 Jan 2008 19:18:33 +0300 [thread overview]
Message-ID: <477BB959.1040207@gmail.com> (raw)
In-Reply-To: <200801021610.45582.arvidjaar@mail.ru>
Andrey Borzenkov wrote:
> On Wednesday 02 January 2008, Alexey Starikovskiy wrote:
>
>> Andrey Borzenkov wrote:
>>
>>> This is did not happen before; I am not sure right now what caused this
>>>
> (i.e.
>
>>> battery aging or some software change) nor whether this is
>>>
> kernel/HAL/kpowersave
>
>>> issue.
>>>
>>> kpowersave is stuck at assuming battery is loading and at 94%. Sysfs
>>>
> displays
>
>>> battery state as Full:
>>>
>>>
>>>
>> Frequent battery charging shortens lifetime of the battery, so some (may
>> be all now)
>> notebook manufacturers do not start charging battery until it discharge
>> to some degree (~90%).
>>
>
> I thought Li-Ion batteries do not have memory effect. Actually I remember to
> have read recommendation to avoid deep discharges of Li-Ion battery, it was
> adviced to charge it as often as possible.
>
IBM has advice to not re-charge battery until it discharged to 95%.
It was implemented in their batteries/notebooks.
There is no memory effect in Li-Ion batteries, there is only limited
number of
charge cycles -- about 1000 times, thus "as often as possible" is advice
of the battery seller :)
>
>> It could be your case. Please try to discharge battery to, say, 89% and
>> then check if it charges to the
>> 100%.
>>
>
> That is exactly the question - how do you compute 100%? As far as I can tell the
> only possibility is - when battery stops charging. At this point you have to
> assume battery is fully charged.
>
Last charge would be good reference. Think of the battery as constantly
degrading resource.
> I tried to discharge battery (it was around 78%) and plug AC in again. It went
> on Charging until the same limit after that state changed to Full (well, in case
> of ACPI battery we really only can state - not (dis-)charging, there is no
> special Full state flag); kpowersave still believes battery is not fully
> charged. Main interface shows 84% (no Charging) - tooltip states it is being
> charged.
>
>
So, that is the state of your battery. If you buy new one, it will go
high again.
Regards,
Alex.
prev parent reply other threads:[~2008-01-02 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 9:48 kpowersave stuck at battery charging Andrey Borzenkov
2008-01-02 9:48 ` Andrey Borzenkov
2008-01-02 10:42 ` Alexey Starikovskiy
2008-01-02 13:10 ` Andrey Borzenkov
2008-01-02 13:10 ` Andrey Borzenkov
2008-01-02 16:18 ` Alexey Starikovskiy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=477BB959.1040207@gmail.com \
--to=aystarik@gmail.com \
--cc=arvidjaar@mail.ru \
--cc=hal@lists.freedesktop.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.