Originally Posted by T4UR14N

you honestly need to stop installing everything you see....honestly

its like you like making the same mistakes over & over again

Originally Posted by F2thaK

does your version autostart??

Originally Posted by trisha02

i am using kp47. installed it like the way mentioned. found the file in usr/local/bin/overclock.

my freq is 250 and 750.
rebooted my phone. locked it and unlocked it (activate the patch)
i had max cpu installed earlier.after applying the patch max cpu always shows 500. healthcheck doesnt show any available freq or anythng.it was jst a simple patch.and applying it was easier than other patches i hav installed successfully.i am sure there is no problem of my installation. just i need the correct profile and the correct min and max frq with which i can have a better battery life. if its not possible for you to help me then plzz tell me how to remove the patch.i will wait for karam's next battery patch update, he told me to wait bt i applied the patch before that.

Originally Posted by Estel

Back on topic, all of this is pointless, because device with limits 500-900 (or any other) doesn't "sit" on 500 when idle - it effectively underclock to 0 mhz, so You save also on power leakage. Talking in simplified way, CPU do it's job, and then go to "sleep" - every second.

So, if You set limits to lower (i.e 250), You got less time on 0 mhz - every second - cause it takes longer to finish "idle" set of task on 250, than on - for example - 500 mhz.

Furthermore, monitoring every dbus signal use resources and battery power.

Effect is, that You loose battery life, instead of gaining it. Of course people will report increased battery life - via placebo effect - but there is no reason why it should give any real-life gain.

Originally Posted by Estel

Back on topic, all of this is pointless, because device with limits 500-900 (or any other) doesn't "sit" on 500 when idle - it effectively underclock to 0 mhz, so You save also on power leakage. Talking in simplified way, CPU do it's job, and then go to "sleep" - every second.

So, if You set limits to lower (i.e 250), You got less time on 0 mhz - every second - cause it takes longer to finish "idle" set of task on 250, than on - for example - 500 mhz.

Furthermore, monitoring every dbus signal use resources and battery power.

Effect is, that You loose battery life, instead of gaining it. Of course people will report increased battery life - via placebo effect - but there is no reason why it should give any real-life gain.

Originally Posted by F2thaK

can you set underclock max lower than 500 MHz?