Thread: Xpuscalar 3.03
View Single Post
  #11 (permalink)  
Old 07-27-2007, 03:42 PM
PolloLoco's Avatar
PolloLoco
Regular 'Geeker
Offline
 
Join Date: Mar 2007
Posts: 290
Reputation: 135
PolloLoco is keeping up the good workPolloLoco is keeping up the good work
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
It doesn't matter what the speed your processor is set at is. That does not dictate battery loss due to Over/Under Clocking.

The problem is that the two scaling programs fight each other, playing tug of war in getting the processor to run at two different speeds. We know that XCPUScalar can win the war and hold your processor down to 200mhz. The problem is that in struggling to do so - the phone ends up burning A LOT MORE battery power than it would without the XCPUScalar running. Our 6700's are unfortunately unique in that respect.

Immier, the creater of XCPUScalar has himself posted on the 6700 programs and explained that due to the tug of war, you're better off NOT using the scaling feature of XCPUScalar to underclock. He's explained that the advantage of using the program is a burst of speed when you need it - and hibernation when you dont. So . . . following HIS instructions, I have my PPC at 624 mhz all the time. But when the screen dims, XCPUScalar shuts down - so I'm not burning ANY more battery than normal.

If you're using the scaling feature with the 6700's you're doing yourself a disservice battery wise. You're probably burning more battery power underclocking with a new scaling, than I am OVERclocking with no scaling.
Reply With Quote