From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: Nils Faerber
<nils.faerber-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>
Cc: Johan Vromans <jvromans-2pNSKKP3PSKEVqv0pETR8A@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Slightly OT: Battery usage
Date: Tue, 7 Jun 2005 00:31:43 +0200 [thread overview]
Message-ID: <20050606223143.GC65@hell.org.pl> (raw)
In-Reply-To: <42A4282C.7070808-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>
Thus wrote Nils Faerber:
> - - not be charged to full all the time. All Li-* batteries like only to
> be recharged after they have discharged for at least 10% or more (i.e.
> max. 90% remaining). Before that they should not be recharged to full
> again. Many notebook charging circuits do not honor this and kill their
> batteries within approx. one year (my Asus L3C did this, my Fujitsu
True, my original L3C battery is now at 25% of design capacity and it's
a fairly common practice to restart charging every time the power cord is
plugged in. It's good you name the brands that got it right though.
> Siemens Lifebook B-Series does not, IBM T42p does not, etc.)
>
> - - never be discharged completely, i.e. up to the point where the machine
> switches itself off.
Except that given current laptop power consumption, the battery is nowhere
near empty when the voltage drops below the acceptable level and the
circuit is switched off. That said, any attempts at shorting will damage
the battery.
Best regards,
--
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
next prev parent reply other threads:[~2005-06-06 22:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 9:16 Slightly OT: Battery usage Johan Vromans
[not found] ` <m2br6jx2t1.fsf-KjnUIgV0B0bak1Ioo/c9IoRWq/SkRNHw@public.gmane.org>
2005-06-06 9:31 ` Norman Urs Baier
[not found] ` <200506061131.21236.spiessli-hi6Y0CQ0nG0@public.gmane.org>
2005-06-06 17:54 ` Johan Vromans
2005-06-06 10:40 ` Nils Faerber
[not found] ` <42A4282C.7070808-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>
2005-06-06 16:06 ` Stefan Dösinger
[not found] ` <200506061606.01346.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2005-06-06 14:54 ` Florian Hühn
[not found] ` <20050606165454.17e1e9c9.acpi-14TN6mYQPXr1AXQ8ov2VOh2eb7JE58TQ@public.gmane.org>
2005-06-06 17:29 ` Stefan Dösinger
2005-06-06 22:31 ` Karol Kozimor [this message]
[not found] ` <20050606223143.GC65-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2005-06-07 18:04 ` Vasileios Gkanis
[not found] ` <200506071304.30718.gkanis-4fMUIQ/vbHD2fBVCVOL8/A@public.gmane.org>
2005-06-07 22:20 ` Stefan Dösinger
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=20050606223143.GC65@hell.org.pl \
--to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=jvromans-2pNSKKP3PSKEVqv0pETR8A@public.gmane.org \
--cc=nils.faerber-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox