How to overclock without setcpu

[mjesenovec]

I think i have been having some minor issues with setcpu on jrummy v.7. after spending some time reading around, people say to not use setcpu, just use the dev's built in kernal, etc. i've been thinking about trying bugless beast 1.0, and i've read not to use setcpu with it. if i uninstall setcpu and dont use it, how do i manage my overclock, or even tell if the phone is overclocked at all?

 

[thebizz]

without set cpu thiers no way to know if your phone is overclocked just use the overclock widget to see the speeds your running. but the stock kernel may get you up to those speeds without set cpu

 

[borgey401]

I think i have been having some minor issues with setcpu on jrummy v.7. after spending some time reading around, people say to not use setcpu, just use the dev's built in kernal, etc. i've been thinking about trying bugless beast 1.0, and i've read not to use setcpu with it. if i uninstall setcpu and dont use it, how do i manage my overclock, or even tell if the phone is overclocked at all?

i have been wondering the same thing myself. i hope we get some answers to this quick because im running 1.0 right now

 

[thebizz]

Try the overclock widget from the market let me know is that will allow overclocking of the Droid

 

[Jeatin]

Uh... Don't use setcpu? Why not and how would you manage your overclock (I'm sure the widget does the same damn thing)?

This does not make sense at all.

 

[matrix2004]

The latest Bugless Beast ROM has overclocking already setup. There is no need for installing set cpu.

 

[thebizz]

Um have you ever noticed once you installed setcpu when you first open it won't show you running at the overclocked speed but stock speeds

 

[mjesenovec]

i guess that was my question. are some roms set up to run 800mhz, 900, 1ghz as soon as you install it? or is setcpu necessary to activate any clock speed over 550? that's why i was confused because i've been using setcpu for months, but then i read somwhere online that the newest cyanogen version works best and has fewer issues if you dont use setcpu to manage overclock. i just didn't know if there was another way to manage it without setcpu. i recently had random reboot issues with jrummy v.7. i uninstalled my most recently installed app (No Lock) and disabled setcpu profiles and haven't had a problem since.

 

[thebizz]

You need setcpu to get those overclock speeds I just flashed another kernel and my phone was running at 550 until I went into setcpu and changed it

 

[Flyguide83]

BB V1 you DONT need setCPU UNLESS you want to turn down clock speeds. He has programed -the phone to do exactly what setcpu does and has his custom profiles pre set in his script that auto runs at install. You can still use setcpu, but it will auto kill after you set the speed you want. Basically it has been found that setcpu is not NEEDED and really is just a security blanket at this point with his rom at least. It only bulks on the drag with the processor.
I'm sure this will become common practice once the other devs finger out how he was able to do it.

 

[coolbho3000]

It only bulks on the drag with the processor.

I'm not going to let all this talk go on without saying something.

While it is true that SetCPU runs as a background service when profiles are enabled, it is very passive in its current state (as long as you keep the refresh interval on the CPU temperature profile down, but that was only introduced in the last two versions) and should not affect performance at all.

The application runs no code in the background when profiles are not enabled and the widget is not on the screen. When you use it, it sets the CPU speed and leaves it alone. You may see it in your task manager, but it will be killed by Dalvik as soon as the Android system needs the memory. That's right, just having SetCPU installed cannot possibly cause any problems, as many people seem to assert. If profiles are disabled, it is certainly your ROM or setup, if profiles are enabled, it is almost certainly your ROM or setup. SetCPU is a very small part of the equation. Correlation does not imply causation.

I am planning to move parts of the code to the NDK to get additional performance benefits, but for now, the profiles service will not "bulk on the drag with the processor," whatever the hell that means.

As for the other concerns about 1.5.2x, the active widget was a huge mistake (I really regret pushing it out, though I can't pull it back now), and perhaps the Droid temperature sensor support was a mistake too. People just don't get that checking/updating something at a relatively fast interval will have detrimental costs to battery life. And the people who are asserting that their Droid is running hotter (oh noes!) don't get that a different sensor will have different readings. There is a reason why I didn't push the active widget for so long. Someone else (who defaults the update interval to something like 30 or 60 seconds, effectively rendering it useless - cpufreq polls in the range of the thousands of microseconds) gave people the idea that an active widget was such a good idea, though. The funny thing is that all of these detrimental effects can be reversed by removing a widget and changing a drop down list.

There's a common sense factor too, and many users just don't seem to get it. Yes, I am continuing to work on updates. Yes, SetCPU will get better. It's a complex beast that I admit is difficult for end users to grasp at first.

coolbho3k