Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #57795
| From | David Higton <dave@davehigton.me.uk> |
|---|---|
| Newsgroups | comp.mobile.android |
| Subject | Re: charging policy |
| Date | 2018-11-22 21:29 +0000 |
| Organization | Home |
| Message-ID | <74ce215b57.DaveMeUK@my.inbox.com> (permalink) |
| References | (4 earlier) <221120180150118477%nospam@nospam.invalid> <WwElr2JSbt9bFwPQ@255soft.uk> <pt6okf$7uh$1@dont-email.me> <pt70nn.dsc.1@ID-201911.user.individual.net> <fOCdnazguqfEiWrGnZ2dnUU78eHNnZ2d@brightview.co.uk> |
In message <fOCdnazguqfEiWrGnZ2dnUU78eHNnZ2d@brightview.co.uk>
"NY" <me@privacy.net> wrote:
> I think the main reason for leaving *any* rechargeable device connected to
> the mains whenever you don't need it to be portable, is to make sure the
> battery is always as full as possible so that at a moment's notice it can
> be used off-mains for as long as possible. It's just a shame that with
> current battery technology this still seems to shorten the battery
> lifetime (ie it stores progressively less and less charge over a period of
> usage).
Going back 30-odd years, I looked at an Uher portable real-to-reel tape
recorder for an acqauintance. The battery (a NiCad) would no longer
store a charge. I removed the battery's seal strip and looked into
the cells through the rubber vents. The cells had dried out, and
crystals of electrolyte were visible. I took a hypodermic syringe
and filled the cells with water. When I tested the battery, its
capacity was about 105% of nominal.
So the water in the electrolyte had been dissociated into hydrogen and
oxygen as a result of the charging regime he had applied.
Whether that has any relevance to today's battery technologies, I
don't know. (I'm sure water is not involved, but whether any other
constituent can be similarly destroyed...)
All batteries gradually lose their capacity over time and use.
Dave
Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
charging policy "Linea Recta" <bleep.bleep@bleep.invalid> - 2018-11-21 18:24 +0100
Re: charging policy Andy Burns <usenet@andyburns.uk> - 2018-11-21 17:36 +0000
Re: charging policy Libor Striz <poutnik4REMOVEnntp@CAPITALSgmail.com.INVALID> - 2018-11-21 19:02 +0100
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-21 15:10 -0500
Re:charging policy Libor Striz <poutnik4REMOVEnntp@CAPITALSgmail.com.INVALID> - 2018-11-21 18:53 +0100
Re: Re:charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-21 18:42 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-21 15:10 -0500
Re: charging policy Libor Striz <poutnik4REMOVEnntp@CAPITALSgmail.com.INVALID> - 2018-11-22 07:13 +0100
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-22 01:50 -0500
Re: charging policy Libor Striz <poutnik4REMOVEnntp@CAPITALSgmail.com.INVALID> - 2018-11-22 09:15 +0100
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-22 16:09 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-22 11:57 -0500
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-22 16:18 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-22 11:57 -0500
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-22 17:26 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-22 12:54 -0500
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-22 21:26 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-23 01:14 -0500
Re: charging policy Andy Burns <usenet@andyburns.uk> - 2018-11-23 09:28 +0000
"tl; dr" (was: Re: charging policy) "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-23 15:28 +0000
Re: charging policy 123456789 <12345@12345.com> - 2018-11-22 18:39 -0700
Re: charging policy 123456789 <12345@12345.com> - 2018-11-22 10:22 -0700
Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-22 18:45 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-22 13:47 -0500
Re: charging policy "NY" <me@privacy.net> - 2018-11-22 20:40 +0000
Re: charging policy David Higton <dave@davehigton.me.uk> - 2018-11-22 21:29 +0000
Re: charging policy 123456789 <12345@12345.com> - 2018-11-22 18:39 -0700
Re: charging policy 123456789 <12345@12345.com> - 2018-11-22 18:39 -0700
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-22 21:30 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-23 01:14 -0500
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-23 15:26 +0000
Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-23 16:13 +0000
Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-23 19:52 +0000
Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-23 21:29 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-23 16:40 -0500
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-23 21:48 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-23 17:06 -0500
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-23 22:09 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-23 17:23 -0500
Re: charging policy The Real Bev <bashley101@gmail.com> - 2018-11-23 21:00 -0800
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-24 09:05 -0500
Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-24 15:46 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-24 10:51 -0500
Re: charging policy 123456789 <12345@12345.com> - 2018-11-24 10:01 -0700
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-24 12:55 -0500
Re: charging policy 123456789 <12345@12345.com> - 2018-11-24 13:07 -0700
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-24 16:33 -0400
Re: charging policy 123456789 <12345@12345.com> - 2018-11-24 18:52 -0700
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-25 00:42 -0500
Re: charging policy 123456789 <12345@12345.com> - 2018-11-25 11:33 -0700
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-25 19:06 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-25 14:46 -0500
Re: charging policy 123456789 <12345@12345.com> - 2018-11-25 19:37 -0700
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-25 22:07 -0500
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-26 04:46 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-26 00:32 -0500
Re: charging policy 123456789 <12345@12345.com> - 2018-11-25 22:37 -0700
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-25 14:46 -0500
Re: charging policy 123456789 <12345@12345.com> - 2018-11-25 19:37 -0700
Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-26 15:45 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-26 10:49 -0500
Re: charging policy 123456789 <12345@12345.com> - 2018-11-26 16:04 -0700
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-26 19:11 -0500
Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-24 20:14 +0000
Re: charging policy 123456789 <12345@12345.com> - 2018-11-24 18:52 -0700
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-25 00:42 -0500
Re: charging policy Anssi Saari <as@sci.fi> - 2018-11-26 10:36 +0200
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-26 16:37 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-21 15:10 -0500
Re: charging policy 123456789 <12345@12345.com> - 2018-11-21 15:01 -0700
csiph-web