[ROOT] Using SetCPU + Perflock Disabler to Save Battery, Underclock

[mscalero]

This is an awesome write up. I would be very interested in a cross comparison like this for the Droid 1, for a user who is on 2.2, and wants to root and use SetCPU on the stock 2.2 rooted image for the Droid 1 to get the best of battery life.

 

[syphex]

wow using his exact settings I was able to go 30 hours on a single charge with two exchange accounts set to push and several short phone calls and some 3d gaming. It's the first time I found something like this that didn't hinder the opperation on the phone and actually worked

 

[milominderbinde]

This works so well that I added a link to it in the Getting Started with Android - Tips and Tricks, under the Battery Life Tips and Tricks section.

Thanks!

 

[Kevin OQuinn]

Yes it works wonderfully.

 

[jonwienke]

Nope, especially if you're using the stock kernel + Perflock Disabler. It used to be that when you flashed a different overclockable kernel, it would screw up the camera.

But now, even custom kernels are based on HTC's released kernel, so nothing breaks.

Disabling perflock has disabled all camera function on my EVO, and now I can't use it even after uninstalling SetCPU with Titanium Backup. Any attempt to access camera for still or video either force closes or locks up the phone. I'm running the following:

Froyo 2.2

Baseband 2.15.00.07.28

Kernel 2.6.32.15-g746f4f0
htc-kernel@and18-2#58

Build 3.26.651.6

Rooted with Unrevoked 3.

Everything works except the camera. I was originally running 3.26.651.5, and I installed a bar code reader along with SetCPU and the phone got disabled. Nothing got the phone working again until I installed 3.26.651.6, which wiped all user data. But when I reinstalled SetCPU, (I initially thought the barcode reader app was the culprit) the camera died again, and hasn't worked since.

SetCPU 2.0.4 does not disable perflock; even after disabling it "successfully" from the menu and setting a max CPU speed of 499 MHz, the CPU still runs at 998 MHz whenever it wants to. It appears to be altering the wrong thing in the stock EVO software I'm running and killing the camera drivers instead of perflock.

How exactly does perflock disabler work? What file is it modifying, and how can I undo the damage? I have a nandroid backup from before 3.26.651.6 started having problems, but would rather not nuke text messages and other user data unnecessarily.

 

[chuckt1]

First I would like to say this is awesome. Second, i wasnt sure if i was doing this right. I tried hitting long bench alot of times but the closest to 1000ms i could get was 1700 ms, am i doing something wrong? evo 4g

 

[jhapsz23]

Re: [ROOT] Using SetCPU + Perflock Disabler to Save Battery, Unde

Hey can i ask why is that my scaling governor doesn't have ondemand option only bcm21553 and performance plsss reps