Rockbox mail archiveSubject: Re: WPS battery levels wrong?
Re: WPS battery levels wrong?
From: gl <gl_at_ntlworld.com>
OK, I've thought about this some more, and the current scheme seems wrong.
As a user I expect each battery segment to signify 25%, so when the first
I think we can fix this and improve on it. First we can lift the battery
With that in mind, assuming the designer wants 4 battery segments as before,
0 = 0-[danger level]%, no segments visible, device will shut off shortly
(assuming 4 enums are used)
5 = 100% (optional, can be used to show a 'completely full' bitmap)
The danger level should be derived from the estimated time remaining, eg.
This scheme would be backwards compatible, and should also correct the
Are there any problems with me implementing this?
-- gl ----- Original Message ----- From: "gl" <firstname.lastname@example.org> To: "Rockbox development" <email@example.com> Sent: Sunday, March 05, 2006 9:39 AM Subject: WPS battery levels wrong? > > I'm confused about the number of WPS battery levels. The CustomWPS online > docs suggest there are 5 ("0-4"), and 4-segment battery bitmaps are > common. > > However, the code in gwps-common.c does this: > > int l = battery_level(); > *intval = l / 20 + 1; > > Which produces 1-6, presumably: > 1 = 0-19% > 2 = 20-39% > 3 = 40-59% > 4 = 60-79% > 5 = 80-99% > 6 = 100% (fully charged) > > You can confirm this with: > BATTERY: ?%bl<1,2,3,4,5,6> > > Shouldn't the code use / 25? > -- > glReceived on Tue Mar 7 03:56:25 2006
Page was last modified "Jan 10 2012" The Rockbox Crew