From: Simon M. <simon.me_at_gmail.com>
Date: Tue, 17 Apr 2007 23:02:49 +0200

> Meaning that percentage is an accurate value. The problem with times,
> is that they're only accurate for new batteries, while playing MP3,
> without skipping. Once you start moving from the usage pattern used to
> determine that runtime, it becomes meaningless, or at least much less
> meaningful.

How about changing the battery menu entry to a value where the user
can set their own maximum runtime based on experience? If we provide
meaningful target specific default values, then most users won't
notice the change and people who want to have everything exactly to
the hour (and minute) can do their own mesurements. Let's call it
"expected battery runtime" or something like that.

At the moment, the runtime estimate is very conservative (on my
iriver), which is fine, because I know that I have at least that
amount of runtime left, even with headphones, eq and vbr mp3s. I don't
think many people will complain if their battery lasts longer than
estimated. And with my proposal above, they can change it easily (and
more meaningful than with mAh values).
Received on 2007-04-17