SetCPU Vs Petes V1.1 CPU script
It's a one-shot, only-at-boot-time, setup. As other folks have said, it ONLY sets the CPU for OnDemand overclocking. It does _not_ try to duplicate the custom profiling that you can do with SetCPU.
BB0.3 OC'd @ 1000mhz
ChevyNo1 7 slot 1000mhz kernel
Bodyglove Case and Invisishield
I just want to chime in my opinion.
I think we should start making the distinction been needs and wants. Before BBv1.0, users needed an app like setCPU to overclock, because without it you couldn't overclock. Now with BBv1.0 and BBv1.1 if what you want is a blazing fast room with an added cool CPU temp, all you need to do is run BBv1.1 with the stock 600Mhz kernel, or just bump it up a little to 800Mhz with the bekit kernel and call it a day.
Seriously people, it's simple. This is Pete's rom, if you don't follow his recommendations your phone is bound to have problems/FC's/errors and so on. If what you want is to have total control over your phone by way of setCPU/task managers/etc.; why not just go with any other one of the numerous roms out there that let you do so?
Your other option is of course to ask Pete is you could get his roms source and change it to your liking or make a rom from scratch however you see fit (I know this is not an option for 99.9% of us; but dayaum people. Why complain and cry over something given to you freely with no strings attached?).
I'm running BBv1.1, and before that BBv1.0 and neither one has yet to give me a problem/FC/error/reboot/freeze (you name it). It runs perfectly fine/cool/fast, and runs even better than stock ESE81. I can honestly say it's because I've followed Pete's recommendations and I don't go out of my way to switch any number of apps that can cause conflicts such as different phone.apk, contacts.apk, setCPU, Task Managers or anything else that can mess with Pete's rom.
I want to repeat that this is only my opinion and should be taken as such. This is not personal or some troll post of any kind (sorry czerdrill, but your posts were exactly the things I wanted to talk about an proved the most useful in contrast).
Last edited by ZeroBarrier; 05-30-2010 at 08:45 PM.
Perhaps you don't understand what the pete file does, but I'm telling you that it does NOT do anything other than set a max speed (as far as "replacing" setcPU goes). If pete has some other "hidden" file somewhere in his "source", I would like him to state so. Until then, this ROM does not eliminate the need for setcPU.
That's not a complaint. It's the truth. The ROM is the best ROM I've ever used. It's not a replacement for setCPU...at least not for me.
Last edited by czerdrill; 05-30-2010 at 09:14 PM.
update: Still have not downloaded or touched Set CPU. Running 1GHZ kernel.
Stellar Battery: Easy full day. Pull off the charger before bed at night and use the device the following day without charging until night time. Average 30-40% end of day.
Low temps: Highest seen 110 while browsing internet for approximately 60 minutes.
Zero reboots or FC's.
So far so good. Not sure if it's the ROM that is giving me the great battery life or not using Set Cpu.
Skull One is going to be doing some testing on BB and I'm VERY interested to see what his results are.
Maybe Pete's simple script has some value that can be carried over to other ROMS where users need Set CPU.
I don't know but I find this very interesting. I've ran a clean deodexed ESE 81 Stock ROM OC'd to 800MHZ and never saw this kind of battery life.
You "need" setCPU to set profiles because you "want" to set profiles. Again, the differences between needs and wants.
Fair enough, the profiles aspect is a valid "want".
I understand what the Pete file does fine, and yet see no need to fiddle with it on my phone. One other thing we seem to forget is that this is in it's root a phone and everything else is secondary.
As for higher speeds equating to higher heat, that's exactly how these electronic components work. The longer you run your CPU at a higher frequency, the higher the heat will get (this is a fact and not an opinion).
So basically you want to run 1.2Ghz till the CPU gets to "X" temperature and then have it "yo-yo" up and down the speeds to limit it from surpassing "X" temperature? I still come to the conclusion you should save yourself the headache and choose a kernel with a max speed that doesn't surpass your temperature requirements, because it's obvious that setCPU profiles is doing just that for you, setting a max clock to fulfill your temperature requirement. All you seem to be doing is using a higher clock till the temperature requirement is surpassed and then switching to a lower clock to keep your temperature requirement in check.