SetCPU Vs Petes V1.1 CPU script

[cereal killer]

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. :

Now I'm very confused : )

A 600 stock kernel you get high temps but run a 1.2GHZ all day and keep cool temps?

How is this possible?

[ZeroBarrier]

Listen, I understand the need to embellish because you want to use an app that you seem to love so much, but the reality is simple.

There is no doubt in my mind that Pete was right to post that his rom removes the need for setCPU, for a couple of good factual reasons.

1) The rom auto-overclocks it;self to the highest slot at boot (no longer needed for overclocking)

2)Choose the highest clocked kernel for your speed+temperature needs (the same functionality that the profiles provide).

3)More space, less waste (no need to install an app that takes up resources).

[jimnutt]

The only advantage SetCPU has over the built in script is profiles. The built in settings will always allow the CPU to run up to max speed, no matter what. Sometimes you don't want that. For example, when my battery gets low, I'd prefer the droid slow down some and save my remaining battery. So I have a profile that kicks in a 30% battery life and kicks the max clock speed down to 600Mhz. And when the phone is sleeping, I have the max clock speed set to 400Mhz, again, to conserve battery if a background task is running with the screen off. Neither is profile is necessary for the safe and smooth operation of the phone, they're just my preference.

[czerdrill]

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. :

Now I'm very confused : )

A 600 stock kernel you get high temps but run a 1.2GHZ all day and keep cool temps?

How is this possible?

A 600 kernel withuot setCPU gives me high temps, just as a 1.2 kernel without setCPU does. With setCPU the 600 gives me low temps. However, obviously the 1.2 gives me more speed, and the same temps. So I go with the 1.2.

[ZeroBarrier]

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

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. :

Now I'm very confused : )

A 600 stock kernel you get high temps but run a 1.2GHZ all day and keep cool temps?

How is this possible?

Even ck noticed you contradicted yourself there, how is it that you haven't noticed?

[czerdrill]

Listen, I understand the need to embellish because you want to use an app that you seem to love so much, but the reality is simple.

There is no doubt in my mind that Pete was right to post that his rom removes the need for setCPU, for a couple of good factual reasons.

1) The rom auto-overclocks it;self to the highest slot at boot (no longer needed for overclocking)

2)Choose the highest clocked kernel for your speed+temperature needs (the same functionality that the profiles provide).

3)More space, less waste (no need to install an app that takes up resources).

awesome. i feel you have far more time on your hands then i do, so like i said i'll defer to you.

[ZeroBarrier]

A 600 kernel withuot setCPU gives me high temps, just as a 1.2 kernel without setCPU does. With setCPU the 600 gives me low temps. However, obviously the 1.2 gives me more speed, and the same temps. So I go with the 1.2.

Unless your profile makes it run under 600Mhz for most of the day, I don't see how that's even possible.

[czerdrill]

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

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. :

Now I'm very confused : )

A 600 stock kernel you get high temps but run a 1.2GHZ all day and keep cool temps?

How is this possible?

Even ck noticed you contradicted yourself there, how is it that you haven't noticed?

where is the contradiction. i get high temps without setCPU, and lower with. I never contradicted that, I never said anything otherwise. Does this mean, setCPU is an HSF (like you so foolishly stated?) No. What it means is, because of my profiles, when/if my CPU goes above a certain temp it clocks down and my temp goes down. I don't notice any lag, any temp differences any issues.

You seem to be arguing for the sake of arguing. I simply don't have the time or the interest to oblige you, man.

[czerdrill]

A 600 kernel withuot setCPU gives me high temps, just as a 1.2 kernel without setCPU does. With setCPU the 600 gives me low temps. However, obviously the 1.2 gives me more speed, and the same temps. So I go with the 1.2.

Unless your profile makes it run under 600Mhz for most of the day, I don't see how that's even possible.

lol...k. what do i say here? not much i can, because you won't believe it...so again...what is the point of this debate?

[ZeroBarrier]

where is the contradiction. i get high temps without setCPU, and lower with. I never contradicted that, I never said anything otherwise. Does this mean, setCPU is an HSF (like you so foolishly stated?) No. What it means is, because of my profiles, when/if my CPU goes above a certain temp it clocks down and my temp goes down. I don't notice any lag, any temp differences any issues.

You seem to be arguing for the sake of arguing. I simply don't have the time or the interest to oblige you, man.

You are contradicting yourself by saying that a 600Mhz kernel without setCPU runs hotter than a 1.2Ghz kernel with setCPU (with it being set to 1.2Ghz for most of the day).

I never stated that it was a HSF, I asked you if it magically worked like a HSF for you, big difference.

I'm not arguing anything, we are discussing the topic at hand, which is what a discussion forum is for.