SetCPU Vs Petes V1.1 CPU script

[czerdrill]

As an extra, "overheating" is relative too. There's people here who say "Let your phone go to 145, we're rated for 170", and then there's others (like myself) that see no need for the phone to go above 120 (because...there is no need). It's a never ending debate.

But there's no need to stop it going over 120 F, right?

Absolutely not. IF you're fine with your phone hitting 145 everytime you open a game, there's nothing I nor anyone can do to stop you. I'm not fine with it, because I know my phone can run with zero lag doing the same things you're doing and only go to 110 (if that.)

[ZeroBarrier]

setCPU is "needed" for me cuz it gives me the most stability.

I just want to clear this statement up; BBv1.0 and BBv1.1 is stable on it's own merit and setCPU does not provide any added stability (I'm saying this so that any new users will not take what you said there as fact).

I think what you meant to say is that gives you a less fluctuating temperature, but a lower clocked kernel will do the exact same thing for you.

[ZeroBarrier]

Absolutely not. IF you're fine with your phone hitting 145 everytime you open a game, there's nothing I nor anyone can do to stop you. I'm not fine with it, because I know my phone can run with zero lag doing the same things you're doing and only go to 110 (if that.)

My phone doesn't reach that temperature, because I don't run it at a higher clock for an extended period of time, yours would do the same if you weren't running a 1.2Ghz kernel.

You seem to think that running a 1.2Ghz kernel and then limiting it to run slower is actually productive??? I see that as counter-productive.

[czerdrill]

setCPU is "needed" for me cuz it gives me the most stability.

I just want to clear this statement up; BBv1.0 and BBv1.1 is stable on it's own merit and setCPU does not provide any added stability (I'm saying this so that any new users will not take what you said there as fact).

I think what you meant to say is that gives you a less fluctuating temperature, but a lower clocked kernel will do the exact same thing for you.

Again...no it does not. I did NOT just blindly install a 1.2 kernel and then complain about temps. I started with the 600 kernel and still got temps in the 130s. Again, you're assuming that what works for you works for everyone. I tried every kernel in the OP with setCPU and without. I'm amazed that you're telling me how my phone performs. It doesn't make sense to me and is frankly quite odd.

[czerdrill]

Absolutely not. IF you're fine with your phone hitting 145 everytime you open a game, there's nothing I nor anyone can do to stop you. I'm not fine with it, because I know my phone can run with zero lag doing the same things you're doing and only go to 110 (if that.)

My phone doesn't reach that temperature, because I don't run it at a higher clock for an extended period of time, yours would do the same if you weren't running a 1.2Ghz kernel.

You seem to think that running a 1.2Ghz kernel and then limiting it to run slower is actually productive??? I see that as counter-productive.

you seem to think i have a 1.2 kernel and then I have my profiles set up for 600. I'm confused what would give you that idea? My kernel is set to 1200 until it hits below 30% at which point it drops to 1000. It stays at 1200 from 100% to 30% (which in my case is the entire day usually unless I have an especially heavy day of usage). If my phone overheats to 118 (which it doesnt) it'll drop to 550. It has never once had to drop to 550 because of heat. So again, not sure why or how you're assuming I'm running at a slower speed.

[ZeroBarrier]

Again...no it does not. I did NOT just blindly install a 1.2 kernel and then complain about temps. I started with the 600 kernel and still got temps in the 130s. Again, you're assuming that what works for you works for everyone. I tried every kernel in the OP with setCPU and without. I'm amazed that you're telling me how my phone performs. It doesn't make sense to me and is frankly quite odd.

What makes no sense is that now you're telling us that setCPU magically acts like a HSF for your phone with a higher kernel than even 600Mhz???

[ZeroBarrier]

you seem to think i have a 1.2 kernel and then I have my profiles set up for 600. I'm confused what would give you that idea? My kernel is set to 1200 until it hits below 30% at which point it drops to 1000. It stays at 1200 from 100% to 30% (which in my case is the entire day usually unless I have an especially heavy day of usage). If my phone overheats to 118 (which it doesnt) it'll drop to 550. It has never once had to drop to 550 because of heat. So again, not sure why or how you're assuming I'm running at a slower speed.

Now you're just contradicting yourself here...

[cereal killer]

Again, this is easier said then done. If my "sweet spot" happens when I use setCPU, does that mean I'm wrong for using it? I'm running my phone the way that gives me best performance, best speed, best temps and best stability. I'm not purposely running a buggy phone to prove Pete wrong haha

I do think the whole concept of Set CPU vs Script should be explored more.

I'm wondering if Pete MAY have stumbled onto something here. Does a script that is "set it and forget it" generate a smoother and cooler running device? Maybe or maybe not. Just because it works great for me proves nothing.

When Skull runs his tests it will probably give us a lot more insight into this whole discussion.

Maybe Set CPU does generate more heat and effect performance negatively by it's constant polling. Maybe it doesn't. Maybe the script will become the best "tool" for over clocking or maybe it won't but I think the topic is worth exploring more.

[czerdrill]

Again...no it does not. I did NOT just blindly install a 1.2 kernel and then complain about temps. I started with the 600 kernel and still got temps in the 130s. Again, you're assuming that what works for you works for everyone. I tried every kernel in the OP with setCPU and without. I'm amazed that you're telling me how my phone performs. It doesn't make sense to me and is frankly quite odd.

What makes no sense is that now you're telling us that setCPU magically acts like a HSF for your phone with a higher kernel than even 600Mhz???

...i'm not sure where to go from here. It's hard to have a constructive debate with someone who assumes incorrect things to the point of absurdity. setCPU is not an HSF for me. It is something that keeps my temps cool if my phone starts to overheat (because like you said yourself, the higher the speed the higher the heat...i believe your exact phrase was "that's not an opinion, it's a fact"). I'll have to just defer to you, dude. You seem hell bent on proving that Pete's script is God's gift to ROMS haha...so I guess I have to agree with you....?

[czerdrill]

you seem to think i have a 1.2 kernel and then I have my profiles set up for 600. I'm confused what would give you that idea? My kernel is set to 1200 until it hits below 30% at which point it drops to 1000. It stays at 1200 from 100% to 30% (which in my case is the entire day usually unless I have an especially heavy day of usage). If my phone overheats to 118 (which it doesnt) it'll drop to 550. It has never once had to drop to 550 because of heat. So again, not sure why or how you're assuming I'm running at a slower speed.

Now you're just contradicting yourself here...

lol wuttt?? please explain how...i have to hear this.