setCPU and other overclocking apps on new 3.3.6 kenel

---

Since detule has pushed in patches that require an app to overclock now instead of inserting the appropriate lines in the startup.txt file, I am looking to get a better understanding of what exactly the line in the startup.txt file did and how to achieve similar settings in an app like setCPU.

I have setCPU, and set it up to run the default program at 710MHz both the Max and the Min. I am not really interested in battery saving features of the program or anything else. I just want it to run at 710MHz all the time. I thought it pretty much did this when using the startup.txt command set to 710400.

My question is, am I correct that if I set it up setCPU that way is that mirroring what the command did or am I going to get worse battery life then I did before because the app does something different?

I know the phone still sleeps with the app set that way. What happens in sleep with both the startup.txt command or this app? Does Android knock the processor down when going into sleep by either method or both?

Shifting only the MAX to a desired frequency achieves the same as using, what used to be, the command line method and specifying oc_freq_khz.

Shifting the MIN to match MAX will result in poorer battery life, though your phone will run constantly at the desired frequency.

When going into suspend, the driver first down-shifts the clocking frequency and then powers down ARM11 completely regardless of the OC settings.

Originally Posted by detule

Shifting only the MAX to a desired frequency achieves the same as using, what used to be, the command line method and specifying oc_freq_khz.

Shifting the MIN to match MAX will result in poorer battery life, though your phone will run constantly at the desired frequency.

When going into suspend, the driver first down-shifts the clocking frequency and then powers down ARM11 completely regardless of the OC settings.

So before with the oc_freq_khz it would just go shift down to 528MHz or did it go lower? I have the minimum set down to 245MHz now, hopefully I won't see too much lag with that.

Originally Posted by slickdaddy96

So before with the oc_freq_khz it would just go shift down to 528MHz or did it go lower?

It would down-shift to 245, unless under load.

Originally Posted by slickdaddy96

So before with the oc_freq_khz it would just go shift down to 528MHz or did it go lower? I have the minimum set down to 245MHz now, hopefully I won't see too much lag with that.

You probably won't. The chip just goes to 245 if it is just idling. Under load, it'll snap back up to your desired frequency. It is kinda like the i7 2600K when in Turbo Core mode. It'll drop to 1.6 gh/z when doing nothing, then snap up to whatever it is set for when under load.

My settings are 787max and 122 min (This is ACL's OMGB NAND, but it'll probably be similar) and I don't notice lag in comparison to just leaving it at 787.

i need something to speed this thing up a little.... my electrify broke

Originally Posted by moparfreak426

my electrify broke

um, what?

Originally Posted by wizardknight

um, what?

My rebadged motorola photon(electrify broke) and kind of had to switch back this touch pro 2 (rhod500)

Sent from my MSM using XDA

Originally Posted by moparfreak426

My rebadged motorola photon(electrify broke) and kind of had to switch back this touch pro 2 (rhod500)

Sent from my MSM using XDA

If you are using kernel 3.3.6 just grab your favorite overclocking tool from the market. If not, go to the thread for the rom you are using and ask for help.

Originally Posted by wizardknight

If you are using kernel 3.3.6 just grab your favorite overclocking tool from the market. If not, go to the thread for the rom you are using and ask for help.

2.67.96 I think..... need to look for kernal 3.3.6

Sent from my MSM using XDA