Rockbox mail archiveSubject: Re: [PATCH] Battery voltage stats for the recorder
Re: [PATCH] Battery voltage stats for the recorder
From: Mike Soultanian <msoultan_at_csulb.edu>
Date: Wed, 24 Jul 2002 07:16:15 -0700
I don't know if you guys have noticed this or not, but one of the many
annoying things about the stock Archos Recorder is how it handles
charging. If the charger is plugged into the recorder for too long, it
actually kills the batteries after it's charged them. It seems like
what is happening is that the charger charges up the batteries like
normal, but because the cable is plugged in, it keeps the unit on (w/
the light on). Then, when it finishes charging, it doesn't turn the
unit off, but instead leaves it on, but stops charging. This eventually
drains the batteries and leaves the unit flickering.
dunno if this is hardware/firmware/software, but it's pretty annoying as
is... Just thought I'd letcha know of that behaviour if it affects any
battery charging coding you guys might be doing...
Heikki Hannikainen wrote:
> Here's a patch that adds a power_thread (drivers/powermgmt.[ch]) which
> keeps a history, 1 sample per minute, of the battery voltage. It also adds
> a debug menu item for viewing an automatically scaled graph of the voltage
> on the bitmap display.
> I don't know if it makes sense to commit this to the CVS yet, I'm just
> posting the patch in case people would like to comment on it or play with
> it. It probably doesn't hurt to commit.
> This code can be used as a starting point for:
> - better battery_level() which exports a filtered battery status
> for the battery icon, currently it flickers too much (linus suggested)
> - calculating a rate of voltage change
> - charging logic on the recorder (the players have hardware charging so
> this is not needed / cannot be done)
> - calculating a sliding average of the voltage point where the battery
> reaches 'full' level (usable for estimating the charging time
> - calculating a sliding average of the voltage where the hard disk
> starts to have lots of errors, so that we know when to write protect
> it (this varies per unit) and estimate the amount of battery time left.
> The sliding averages could be saved to the config block.
> Known issues:
> - the thread should be enabled for players too, only the viewer won't work
> on the player.
> - Hessu
> Name: 20020724-power-history.diff
> 20020724-power-history.diff Type: Plain Text (TEXT/PLAIN)
> Encoding: BASE64
-- [...]Received on 2002-07-24