Root setcpu settings for incredible

[Two_cents]

I noticed that hydra kernels dont reccomend setcpu but with the kingxkernel alot of people are useing it.. just curious on what profiles and settings you are useing... I was happy with the stock hydra UV cause it was stable everytime I went to overclock it would run fine for 2 or 3 days then throw me into a bootloop randomly... but if I can OC a little and be stable i'd love to

 

[yojoe600]

just make a sleep profile that is 245-384 then you make the rest what ever you want

 

[narf]

just make a sleep profile that is 245-384 then you make the rest what ever you want

Did you mean "screen off" profile?

 

[crazydog]

Are you guys even able to underclock with the hydra kernels? I'm using the 0.5 undervolted ones, and if I try to use SetCPU, I get no visual feedback that it's doing anything. It'll ignore whatever I've set it to. I have had it re detect my speeds, but that doesn't help.

 

[narf]

Are you guys even able to underclock with the hydra kernels? I'm using the 0.5 undervolted ones, and if I try to use SetCPU, I get no visual feedback that it's doing anything. It'll ignore whatever I've set it to. I have had it re detect my speeds, but that doesn't help.

Under setCPU you may have to hit Menu > disable perflock. Thought it was auto disabled under Hydra but maybe I am wrong.

 

[crackers8199]

here's how i set mine up, using king's #2 kernel...

main profile: 1152 max, 245 min, conservative

other profiles...

battery < 10% - 245 max, 245 min, powersave (priority 100)
screen off - 499 max, 245 min, conservative (priority 99)
battery < 17% - 499 max, 245 min, conservative (priority 95)
battery < 25% - 729 max, 245 min, conservative (priority 89)
battery < 35% - 998 max, 245 min, conservative (priority 79)
battery < 50% - 1113 max, 245 min, conservative (priority 69)


i am impressed with how stable it has been so far, but i've only been overclocking for a few hours. i'll report back later after i've been using it for a while...i'm still at 91% battery after almost 2 hours off the charger, and that includes a ton of different quadrant benchmarks with different settings, just to see how everything worked...

this is my first attempt at overclocking, so if anyone has recommended changes to my setup or additional profiles i should add, i'm all ears...

edit: changed the profiles slightly to move screen off up in the order (to make sure it's actually clocking down even if the battery is below one of the thresholds).

 

[crazydog]

Under setCPU you may have to hit Menu > disable perflock. Thought it was auto disabled under Hydra but maybe I am wrong.

I'm aware, but it tells me that it catches some miscellaneous exception. I've also been told that it's already supposed to be disabled with hydra.

I've just delt with not underclocking for now since the undervolting does help the battery, but I'd like to be able to do both=/

http://imgur.com/HGXLI.jpg
http://imgur.com/bqWsy.jpg
http://imgur.com/riCJQ.jpg

 

[Therev29]

I think ejhart said he wasn't going to disable perflock anymore in the under clock kernel and to use setcpu for it.

 

[Two_cents]

hydra highly suggests not to use setcpu... it states to let the builtin governor do its job... I'm using the kingxkernel... I'm happy with a light overclock to just 1075 .. I'm happy ay 998 but if I can do it why not right? 1.19 is definitely not stable for me... 1.15 is barely stable... the screen off profile helps the most... battery all day long and im still at 50%...

 

[MisterMixelpix]

1113 Max, 245 Min, conservative, SR2.5.2 vanilla with the King2 kernel, and I just hit my first 1400 score on Quadrant.

Woot.

 

[Ptriz21]

I have SR 2.5.2 Vanilla with Hydra OC/UV 1.113. Had no problems with this set up. Then got SetCPU
Ugh. what a mess. Without setCPU i was running about 1450 with quadrant. With setCPU set to max i got 1485. wooo000oo.
I had a profile to set the clock speed to 460mhz when it got less than 50% and things started to get nutty. I would get a random reboot or 2, then over and over. After unlock for the first time after booting i would just get FC window over and over again until it rebooted.

I have since nand recovered to before I had setCPU. Going to hopefully get my money back now.

 

[birthofahero]

I have SR 2.5.2 Vanilla with Hydra OC/UV 1.113. Had no problems with this set up. Then got SetCPU
Ugh. what a mess. Without setCPU i was running about 1450 with quadrant. With setCPU set to max i got 1485. wooo000oo.
I had a profile to set the clock speed to 460mhz when it got less than 50% and things started to get nutty. I would get a random reboot or 2, then over and over. After unlock for the first time after booting i would just get FC window over and over again until it rebooted.

I have since nand recovered to before I had setCPU. Going to hopefully get my money back now.

I have the same setup as you and have been using setcpu with no problems. Just posted my numbers here http://androidforums.com/incredible-all-things-root/156801-ultimate-performance-battery-life.html

 

[crackers8199]

I have SR 2.5.2 Vanilla with Hydra OC/UV 1.113. Had no problems with this set up. Then got SetCPU
Ugh. what a mess. Without setCPU i was running about 1450 with quadrant. With setCPU set to max i got 1485. wooo000oo.
I had a profile to set the clock speed to 460mhz when it got less than 50% and things started to get nutty. I would get a random reboot or 2, then over and over. After unlock for the first time after booting i would just get FC window over and over again until it rebooted.

I have since nand recovered to before I had setCPU. Going to hopefully get my money back now.

...or you could give one of the king's kernels a shot, probably get better battery life and better quadrant scores. of course ymmv, but i'd at least give them a shot...

 

[Eris Lover]

Are you guys even able to underclock with the hydra kernels? I'm using the 0.5 undervolted ones, and if I try to use SetCPU, I get no visual feedback that it's doing anything. It'll ignore whatever I've set it to. I have had it re detect my speeds, but that doesn't help.

The clockspeed on the 0.5 ss/uv kernel is non adjustable.