OverClocking 101

[jroc]

Yea u had good points in that other thread, and Skull One coming and backing it up was beautiful. lol

Its all about the profiles with SetCPU vs. the BB Script.

[Skull One]

I read the OP for the rolled ROM he is producing. Technically he is correct if you go by the purist definition of "Need".

If you two would like, feel free to post a link to my original post on the old thread in his new thread. But I really don't want to get into a pissing contest about his statements versus my testing. In the end I just don't see anything good coming out of it. And I really don't want to start another type of forum war like the one between Koush and Blackdroid. In the end no one won. But a lot of good people left here because of it. And that isn't good for the community.

I think Cereal Killer and the rest of the mods would agree. It's his forum section, his rom, his rope around his neck. Me trying to yank it will only polarize the community.

[Tanknspank]

I think if you delete the Pete script in /system/xbin (maybe its bin, but either way), it takes away those features. Then you could start using SetCPU again with no interference.

I think that's what he meant by that anyway.

[czerdrill]

I read the OP for the rolled ROM he is producing. Technically he is correct if you go by the purist definition of "Need".

If you two would like, feel free to post a link to my original post on the old thread in his new thread. But I really don't want to get into a pissing contest about his statements versus my testing. In the end I just don't see anything good coming out of it. And I really don't want to start another type of forum war like the one between Koush and Blackdroid. In the end no one won. But a lot of good people left here because of it. And that isn't good for the community.

I think Cereal Killer and the rest of the mods would agree. It's his forum section, his rom, his rope around his neck. Me trying to yank it will only polarize the community.

Oh yeah definitely as I had mentioned in that huge out of control thread if all you want to do is overclock then yes you don't "need" setCPU. But setCPU is much more than just a "overclock set it and forget it" app. To boldly say that a CPU profile app is not needed just because your ROM overclocks with a script is foolish.

But you're right. I already argued my arse off in that thread, and have no desire to do it again lol. What's his is his, I just know that I for one will not be uninstalling setCPU anytime soon no matter what ROM I use. But then again Pete will "send me his droid" if mine melts...lip service at its best!

[Skull One]

I think if you delete the Pete script in /system/xbin (maybe its bin, but either way), it takes away those features. Then you could start using SetCPU again with no interference.

I think that's what he meant by that anyway.

Technically you don't need to remove the script. Since it runs earlier than SetCPU does and the fact that Pete, I believe, removed the line that killed SetCPU, you will simply do the same thing twice. Which doesn't hurt anything in the long run since both take only a few milliseconds to execute.

[czerdrill]

I think if you delete the Pete script in /system/xbin (maybe its bin, but either way), it takes away those features. Then you could start using SetCPU again with no interference.

I think that's what he meant by that anyway.

Well,no there really is no reason to delete the Pete script as there is no interference. The lines in the pete script about overclocking may be overkill though since setCPU can do the same thing at boot. I just edit out those lines, and run setCPU to "set at boot"...I've never been happier with my temps or batterly life then I am when I used setCPU. I did try to let BB do the work for me, but seeing 135-140 in my temp monitor quickly convinced me otherwise lol

[czerdrill]

I think if you delete the Pete script in /system/xbin (maybe its bin, but either way), it takes away those features. Then you could start using SetCPU again with no interference.

I think that's what he meant by that anyway.

Technically you don't need to remove the script. Since it runs earlier than SetCPU does and the fact that Pete, I believe, removed the line that killed SetCPU, you will simply do the same thing twice. Which doesn't hurt anything in the long run since both take only a few milliseconds to execute.

Beat me too it

[Tanknspank]

I think if you delete the Pete script in /system/xbin (maybe its bin, but either way), it takes away those features. Then you could start using SetCPU again with no interference.

I think that's what he meant by that anyway.

Technically you don't need to remove the script. Since it runs earlier than SetCPU does and the fact that Pete, I believe, removed the line that killed SetCPU, you will simply do the same thing twice. Which doesn't hurt anything in the long run since both take only a few milliseconds to execute.

Beat me too it

Lol, thanks for correcting me guys. I misunderstood what he meant by that then. :P

[alm0614]

why do you recommend the powersave bias to be at 0?

[RW-1]

P3 ...

I couldn't run the 250 kernel on my droid, when I updated to that (the 1.0 ver) it booted up and gave me a charge phone, then shut down, went to the 125 1.0.

Very interesting read Skull, thank you.

I'm on my first day OC'ing my droid, and it helped greatly.