Please read this before you ask about SetCPU!

[KZIWarrior]

I'm just repeating what the developer has indicated...that you are incorrect. It's not going faster. And I'm guessing the developer knows more about their program than our untrained eyes do. Most likely it just feels faster or smoother for whatever reason. At the very best it's not going noticeably SLOWER.

The "conservative" governor ramps up the CPU more slowly than the "ondemand" governor, leading to slower responsiveness but better battery performance.

Nobody said you have to use it or (heavens forbid TRY IT for yourself) but benchmark tests don't lie... unless you want to argue that too...

I was just putting it out there so people (like you) know not to take everything at face value. If you've ever done any programing you would know that things change and his guide was written during earlier versions and with older kernels... things change and (this might be a shocker) but devs don't always update their guides OR know everything that's going on in their apps (i.e. theory and reality OFTEN differ in programs/tools like this).

If you don't want others contributing to your thread(s) (apparently especially so if/when then offer a counter view) so that you appear to be the 'all knowing' source that's fine I'll simply avoid them from now on.

[Matth3w]

I don't really care what you do, but the developer said that option is slower. I was just pointing that out. No need to get hostile.

[Abe21599]

haha i see what you did with your free weekend

nice choice - this clears up a question i had with it..

[KZIWarrior]

FYI
Going off our conversation/bout this morning I decided to switch my governor to your beloved 'on demand' setting and... sure enough lost ALL profiles and throttling (i.e. none of the profiles worked and hitting 'refresh' on the main screen always showed the CPU stuck on max) ...
I switched back to 'conservative' and they are all working again. SetCPU is throttling the speeds (i.e. hitting 'refresh' on the SetCPU page shows it cycling between all frequencies) and all the profiles are followed correctly.

So, as I mentioned earlier, in programming/coding there is theory (design) and reality. Sadly they rarely coincide.

[Matth3w]

It's not my "beloved" ondemand. >.<

Are you referring to the problem people are having with it not going to the correct profile when charging, etc?

[Matth3w]

I changed to conservative to see what it would be like. I noticed that there was about a .25 second lag when opening up my Apps Organizer folders. And I know that it isn't everything, but my benchmark went from 192 to 248. I'm going to stick with ondemand as a personal preference...but how do you suggest I word the first post so as to include both points of view the best?

[sarreq]

ok, here's a question, I've just rooted and installed sholes 2.0.5, used autodetect, and the minimum setting I'm able to choose is 250mhz. is that something to do with the kernel sholes is using?

[Matth3w]

Yes. You can't get lower than 250. 125 caused too many issues so they removed that option.

[sarreq]

OK, good enough for me

what's the issue with selecting Droid in the device list?

also:

5. If you want to set up profiles, click the Profiles button, and then check the "Use Profiles" box. Here is a screen shot of how I have each of mine set up. Notice each profile box must be checked to enable it. Each of the profiles trumps the standard setting. So when my phone is charging, it DOESN'T use the standard setting that you see in step 4, it uses the profile for charging instead. I have the following profiles:

Standard: 550/1000 (I want the phone to have the most juice I can without overtaxing it, so I don't want it to go back down to 250 at any point)
Charging: 250/550 (This will allow the phone to stay cooler while charging as well as charge faster)
Sleep: 250/550 (When the phone is locked, I want it to have enough power to not lag when coming out of lock but still not use too much juice so I have it set to the stock setting...this is what helps you save battery)
When Power is Less Than: <21%...so any time my phone starts running low on battery it goes back to the stock 250/550
Battery Failsafe: >37C 250/550 ... you can see why I chose this setting for this, here: Tell me your thoughts on this SetCPU idea...

I don't see the "Charging" profile anywhere

[Matth3w]

Charging profile is the first profile in the profile list on 1.4.6. As for the device selection...no idea why it is the way it is.