Some people were asking about how battery is affected by nueClockControl. You have to remember that these phones are composed of many power consuming components such as:
ARM11 core (where CE runs)
ARM9 core (where the radio code runs)
aDSP
Radio Transceiver
GPS
Backlight
etc.
nueClockControl controls the ARM11 core only, including the voltage registers. Some people have done talk time tests and noticed little significant difference in talk time at 19.20MHz (although the phone remained cool, which is a plus).
The reason for this is that when you are talking on the phone, the Radio Transceiver and the ARM9 core are the main consumers of power. So what does this mean? It means that nueClockControl will help when you are using Windows Mobile, or if your phone is just idling there…
Think of it this way (numbers are purely hypothetical):
During a call, or while you are using data, power consumption might look like this:
60% Radio Transceiver
30% ARM9
10% ARM11
Lets say that a drop from 528 MHz to 19.20 MHz uses only 25% of the power that 528MHz uses. This means that the ARM11 core only uses 7.5% less total power (10% – 2.5%), resulting in a 7.5% power savings.
Now, lets look at a power situation when the radio is idle, which might look like the exact opposite:
60% ARM11
30% ARM9
10% Radio Transceiver
Now lets do the calculation again with 25% power consumption in the ARM11. now we have (60 % – 15%), resulting in a total power savings of 45%.
But of course, these are only hypothetical numbers, and maybe 19.20MHz still uses 90% of the power 528MHz uses. I kind of doubt that though. In the future, it might be possible to control the clock rates of other things such as the ARM9.