SetCPU on Incredible?

---

Ok, i have a fully rooted incredible with SetCPU installed. I have profiles enabled and setup but when i change the main profile the current clockspeed is always higher. Also, the min/max at the top right never change from 998mhz max and 250 min. Do i need a special kernel or something to use setcpu? i have it under the nexus one/snapdragon profile btw. and its 1.5.4

Originally Posted by mikerulez121

Ok, i have a fully rooted incredible with SetCPU installed. I have profiles enabled and setup but when i change the main profile the current clockspeed is always higher. Also, the min/max at the top right never change from 998mhz max and 250 min. Do i need a special kernel or something to use setcpu? i have it under the nexus one/snapdragon profile btw. and its 1.5.4

Looks like only simple switches like "performance, userspace, etc" and for some reason advanced settings will make a difference. I believe persistent/kernel-level switches not provided for in the UI cannot work at present because we can't write to the build.prop, user.conf, or init.rc.

P.S., the DI's processor is upgraded from N1's. Same product line, newer model.

So im out of luck until a new kernel is out? Ok. But if i get a new kernel, will i be able to keep the default os or does that require a new rom?

Give 1.6 a try. Maybe it works for you.

Originally Posted by larsdennert

Give 1.6 a try. Maybe it works for you.

Nope, even in 1.6 direct throttling still does/can not work, but seems like selecting userdata, performance, or ondemand has an effect on where the processor speed averages

You will need a overclocked kernal for SetCPU to work.

You DO NOT need an overclock kernel for it to work. The problem is the /system partition is not writable from within Android which is how SetCPU works. Once we get the nand unlock, it'll work.

from my understanding is you will need an unlocked kernel and RW NAND

Originally Posted by Berzerker7

You DO NOT need an overclock kernel for it to work. The problem is the /system partition is not writable from within Android which is how SetCPU works. Once we get the nand unlock, it'll work.

Now THAT makes sense. I'm not sure I want a Nand unlock; but I'd like an easier way to push stuff in recovery so I can make intentional tweaks and protect the OS the rest of the time.