why 88% battery shows only 2 hours on IPOD VIDEO

[lifeisogood]

I have IPOD video 5.5 30gb
rockbox installed
batter shows 87% 2h 24m

why so low?
i've just bought this ipod last week
the ipod original firmware gives about 10-12 hours

[Llorean]

Yes, but you're using Rockbox. Feel free to solve the battery problem, other people have worked on it but as I'm sure you've seen by searching and reading the many threads on this issue, it's not a simple solution.

[linuxstb]

Also, the runtime estimate (2h 24m in your example) is not calibrated yet for the ipods - i.e. it's wrong.  

People seem to be reporting about 7 hours playback on a full charge with Rockbox on the 30GB ipod video.

[Buschel]

As both members before told you, the battery calculations are not correct. This is because rockbox's battery capacity for iPOD Videos was corrected, but not the assumed power consumption.
If you are able to build rockbox for yourself you may use patch #7216 (http://www.rockbox.org/tracker/task/7216) which will assume 8h runtime for a 100% charged iPOD 5.5G 30GB.

[Raineer]

or....

Settings
General Settings
System
Battery
Battery Capacity


Change it to around 900mAh and go from there. I make 9 hour drives from Denver to KC more often than I care to admit, and I've arrived at that figure as being as close to reality as I can get with my iPod 5G (about 7:45 at 0db ported into my sound system.) I might recompile with an intermediate value for kicks..but at most it's off like 15 minutes.

There was a patch within the last couple weeks that changed the range one could set the battery too, after that patch I was able to dial it in quickly.

[robin0800]

Not sure where your 900mAh figure comes from?
 If you look at this table
http://ipodbatteryfaq.com/ipodbatteryandpower.html
I can't see 900mAh at all I think your better just setting the capacity from this table.

[Buschel]

He just hacks the capacity to have a realistic runtime estimation. The actual trunk is kind of "broken" or better "not finished" regarding the iPODs batteries.

[robin0800]

I know But what has that to do with 900mAh as this figure is clearly? not correct.

[Rincewind]

you can also use this patch to get a nice runtime estimate:

http://www.rockbox.org/tracker/task/7092

You can adjust the maximum runtime in a settings menu entry. The advantage is, that you don't have to change the battery capacity value, which might be used in other power related functions.

This patch is more flexible than #7216

[Buschel]

The actual battery configuration for iPOD Videos uses (at leat for 30GB-units) correct capacity of 400mAh. The current consumption for all iPODs is assumed to be default = 145mA. So, maximum runtime is 400/145 = 2:45h. To get a proper runtime estimation you can either correct the current consumption (my way in patch #7216) or use an incorrect but much higher battery capacity (e.g. 900mAh -> 900/145 = 6:12h runtime estimated).

The trunk was never adapted to iPOD Video's and/or nano's and with the "correction" of the battery capacity for iPOD Video's nothing works as it was...
Please check out the patch as it uses correct capacities for nano and both Video's (via usage of MEM), defines much better current consumptions and introduces new battery types (as the former used LIPOL wasn't suiting at all).

[robin0800]

I am using this patch and having set the capacity to 600mAh as per the table the display shows 13 hours, after a full charge. This seems to be accurate enough as this sort of playng time is about what i usually get.

Perhaps this should be nearer 10 hours if half the run time of the orignal firmware at 20 hours is correct.
 
Having re read your last comment I see what your saying but would observe That since the capacity range has been changed in svn the maximum now is 1000mAh not enough for mine to be doubled.

Also using Apples figures 600mAh/20 hours is 30mA So at least In my case perhaps 60mA is nearer the value needed

[robin0800]

you can also use this patch to get a nice runtime estimate:

http://www.rockbox.org/tracker/task/7092

You can adjust the maximum runtime in a settings menu entry. The advantage is, that you don't have to change the battery capacity value, which might be used in other power related functions.

This patch is more flexible than #7216

yes this is good you could battery bench and then plug the figure in to this.
What would be realy good is to link this to a wiki page that collects runtime figures from players in real operation shuffling full colour wps etc.
also to know the age of the player that the figures come from.

[Buschel]

I am using this patch and having set the capacity to 600mAh as per the table the display shows 13 hours, after a full charge. This seems to be accurate enough as this sort of playng time is about what i usually get.

Perhaps this should be nearer 10 hours if half the run time of the orignal firmware at 20 hours is correct.
 
Having re read your last comment I see what your saying but would observe That since the capacity range has been changed in svn the maximum now is 1000mAh not enough for mine to be doubled.

Also using Apples figures 600mAh/20 hours is 30mA So at least In my case perhaps 60mA is nearer the value needed

It is not correct to assume rockbox running with half the playtime (=double current consumption) of the Apple firmware. Depending on the playback material  you are able to get 50-70% of the original playtime.
Why you want to double the 600mAh? Doing so you will further increase the calculated runtime. If you want to lower the estimated runtime from 12h to 10-11h you would simply have to select 500mAh (10h) or 550mAh (11h).

[Raineer]

I know But what has that to do with 900mAh as this figure is clearly? not correct.

How is it not correct when it makes the runtime value to be within 15 minutes of my actual battery life everytime?

When the patch was posted to make it 400mAh default I saw it jump to 2:30 max life (also "clearly not correct" from your scenario).

When all you care about is the battery estimator being right, why wouldn't you adjust this?

[Buschel]

The runtime will also be correct with your solution, from this point of view you've chosen the pragmatic way.

But there is some kind of bitter taste to know that there is something wrong internally (e.g. battery type, discharge and power off behaviour etc.) 8-)