Just installed SetCPU

[AsianHTCHero]

Just installed this app and wondering whats the difference between the one I already have on my phone. I have the GB rom installed. I can go to settings, cyanogenmod settings, performance, set the min/max cpu. Pretty much the same?
Also, what's the max/min a htc hero should be set at? I left the setting on interactive.

 

[srkmagnus]

Just installed this app and wondering whats the difference between the one I already have on my phone. I have the GB rom installed. I can go to settings, cyanogenmod settings, performance, set the min/max cpu. Pretty much the same?
Also, what's the max/min a htc hero should be set at? I left the setting on interactive.

You don't need SetCPU since you have access to those settings through the phone. I'd un-install, unless you feel it's better than the built in settings.

Minimum clock speed should be set no lower than what is default. I have mine kicked up to 528 and the maximum to 691. 691 max has been widely stable for our phones, with anything more than that giving people some problems; though some people have no issues running a higher clock speed set to 768 or below.

Interactive is ok, but you should play with the settings to see what's fit for you. Mine is set to Ondemand at the moment and everything seems fine.

 

[LBPHeretic]

The CPU controller in the AOSP Android 2.3 ROM is very rudimentary. It gets the job done, but I prefer the extra control afforded by SetCPU.

You have an easier and much more comprehensive way to fine tune how your system responds to certain events with regards to CPU speed through various profiles. There are plenty of threads on this forum outlining a good baseline for your profile settings, so fire up the search box and have at it.

 

[genuser]

LBP, did you figure out a way to disable the built in governor? I tried ocwidget, and it seemed to fight with built in. I have heard setcpu works better. I wanted to wait and see if the governors come out in asops vanilla processing before I buy it.

I would prefer the govs come out, as they don't appear to work that well .

 

[SupraEA]

The CPU controller in the AOSP Android 2.3 ROM is very rudimentary. It gets the job done, but I prefer the extra control afforded by SetCPU.

You have an easier and much more comprehensive way to fine tune how your system responds to certain events with regards to CPU speed through various profiles. There are plenty of threads on this forum outlining a good baseline for your profile settings, so fire up the search box and have at it.

On the topic of using the search button... when i search for a topic, the results are a bunch of threads. Is there any way to know what page of a thread my results is on? I could search for an app, and as a result "favorite apps" thread comes out, that thread has a bunch of pages, is there any way to know what post # or what page my results are on?

 

[LBPHeretic]

LBP, did you figure out a way to disable the built in governor? I tried ocwidget, and it seemed to fight with built in. I have heard setcpu works better. I wanted to wait and see if the governors come out in asops vanilla processing before I buy it.

I would prefer the govs come out, as they don't appear to work that well .

Are you saying you are not able to overclock past a certain speed? You probably just need to flash a kernel that will overclock to a higher speed then.

Deca's kernels are a good place to start. There is one for 691 MHz and one for 768 MHz. That being said, I have not tried out the Overclock Widget. I guess I could given that it is free, but most people swear by SetCPU.

 

[LBPHeretic]

On the topic of using the search button... when i search for a topic, the results are a bunch of threads. Is there any way to know what page of a thread my results is on? I could search for an app, and as a result "favorite apps" thread comes out, that thread has a bunch of pages, is there any way to know what post # or what page my results are on?

The search results only look at keywords in the threads and thread titles. It will not direct you to a specific post, but it should indicate which posts contain the keywords you selected in your search criteria.

You are pretty much stuck weeding through all the posts that are returned in the list of threads from the search results. It is better than nothing though.

 

[genuser]

Are you saying you are not able to overclock past a certain speed? You probably just need to flash a kernel that will overclock to a higher speed then.

Deca's kernels are a good place to start. There is one for 691 MHz and one for 768 MHz. That being said, I have not tried out the Overclock Widget. I guess I could given that it is free, but most people swear by SetCPU.

I'm on asops gb with stock kernel. Good up to 768. When I run ocwidget, it tells me everytime it makes a speed change. It's making speed changes all the time compared to his froyo rom.

 

[LBPHeretic]

I'm on asops gb with stock kernel. Good up to 768. When I run ocwidget, it tells me everytime it makes a speed change. It's making speed changes all the time compared to his froyo rom.

If it is set to On Demand it might just be scaling your CPU to meet that demand. I still have not tried it with the Overclock Widget yet.

You could try one of Deca's kernels and see if that alleviates the issue: [Kernel][GPL] DecaFuct [2.6.29.6][12/22/2010] - xda-developers .