Let not even think system overhead and just compare lets say 750 mhz to 1000mhz
If it takes us 10 seconds to decode information to install a file with 1ghz not even figuring in overhead it would take us 13.3 seconds to decode that file at 750mhz that means that our screen would be on an extra 3.3 seconds and that we would be running the cpu for an extended time but at a lower current draw.
So unless the current draw increases EXPONENTIALLY as the frequency goes up then underclocking can only increase battery draw since it will use the same energy itself over the longer period of time and it will cause us to wait longer for things with the backlight on.
So unless there is proof that I am unaware of that the CPU does not draw power in a linear way and does draw it exponentially as the frequency rises then underclocking doesn't help while the screen is on.
Now if for example @750mhz the cpu draws 10 pretend units of power vs 20 pretend units of power @1ghz and that the difference in draw is significant enough to provide a saving even after the screen stays on longer then ok but has anyone proved that?
If so let me know so I can underclock my phone.
Using: Thunderbolt (rooted+OC'd) Incredible (rooted+OC'd) Galaxy Tab (rooted).
Retired: Droid X (rooted+OC'd) gave to GF, Droid 1 (rooted+OC'd 1.25GHz) gave it to my lil brother, G1 (rooted) was stolen from me.
Lets say that my phone, granted i dont have a tbolt, is set to use 76 pretend units at full speed (which it is, in vsel), and clocking it down to the next lowest stage puts it at 52 pretend units (which it does in vsel).
The saving versus time, granted is miniscule, but is there.
Edit/ for 20% more time with cpu being used, there is a 22.x% drop in vsel. This is stock settings. I know that the phone will run reliably at 1000 mhz at 45 vsel.
Last edited by kptphalkon; 03-31-2011 at 12:59 AM.