SetCPU Vs Petes V1.1 CPU script

[ZeroBarrier]

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.

I understand that jimnutt, but why even waste the space or the resources for better battery life when the rom itself already accomplishes this?

Since installing BBv1.0 and BBv1.1 I've been able to get heavy usage out of my phone for the most part of the day and still have 30% or more battery left by the time I get back home.

[czerdrill]

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.

How is this a contradiction? I simply don't get it. Maybe I'm missing something, but kernels without setCPU run hotter for me then kernels with setCPU. Not because setCPU is a HSF, but because setCPU throttles down when I want it to. It's not rocket science.

[cereal killer]

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.

I'm not trying be argumentative so please don't take it that way I'm only trying to understand you.

In your post you said with or without set cpu you were having heat issues at 600mhz.

Sent from my Droid

[czerdrill]

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.

I understand that jimnutt, but why even waste the space or the resources for better battery life when the rom itself already accomplishes this?

Since installing BBv1.0 and BBv1.1 I've been able to get heavy usage out of my phone for the most part of the day and still have 30% or more battery left by the time I get back home.

again you're assuming that because you get better battery life without it that everyone does, and then you're assuming that anyone who says otherwise is not telling the truth. very odd like i said before. i get better battery life with it. that's proven (by myself...on my phone....). It's pretty amazing that you can boldly tell people that they will get better battery life without out...just because you do. Your feelings of self worth are pretty high there, buddy....

[czerdrill]

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.

I'm not trying be argumentative so please don't take it that way I'm only trying to understand you.

In your post you said with or without set cpu you were having heat issues at 600mhz.

Sent from my Droid

hmmm...i don't remember saying that but if i did then it was definitely a typo. the reason for my switching to 1.2 as opposed to 600 would be purely speed. without setCPU both kernels have high temps, with they are both low temps.

I apologize if that's the reason I was being misunderstood or thought to contradict myself, because then yeah definitely i contradicted myself haah.

[ZeroBarrier]

How is this a contradiction? I simply don't get it. Maybe I'm missing something, but kernels without setCPU run hotter for me then kernels with setCPU. Not because setCPU is a HSF, but because setCPU throttles down when I want it to. It's not rocket science.

Ok, so then it's not set to 1.2Ghz for most of the day then, or rather you might think it is but in reality it's throttling down more often than not.

This still points to the assertion that you should just run a lower clocked kernel.

[czerdrill]

How is this a contradiction? I simply don't get it. Maybe I'm missing something, but kernels without setCPU run hotter for me then kernels with setCPU. Not because setCPU is a HSF, but because setCPU throttles down when I want it to. It's not rocket science.

Ok, so then it's not set to 1.2Ghz for most of the day then, or rather you might think it is but in reality it's throttling down more often than not.

This still points to the assertion that you should just run a lower clocked kernel.

what do you think pete's script setting to ondemand is doing? Do you think that the 1.2 kernel using pete's script is set to 1.2 no matter what? i hope not, because then you REALLY don't understand what's going on...

obviously if all my profiles are set to 1.2 all day, 24/7 i'm going to get higher temps. that would be just like me running pete's script without setcpu and using my phone all day 24/7...again, and i hate to ask this again...what are we arguing?

[ZeroBarrier]

what do you think pete's script setting to ondemand is doing? Do you think that the 1.2 kernel using pete's script is set to 1.2 no matter what? i hope not, because then you REALLY don't understand what's going on...

obviously if all my profiles are set to 1.2 all day, 24/7 i'm going to get higher temps. that would be just like me running pete's script without setcpu and using my phone all day 24/7...again, and i hate to ask this again...what are we arguing?

Again, I know exactly what the pete script is doing, it sets the CPU to use the highest available slot.

Let me try to explain this in a more simple kid like approach.

You have BBv1.1 + 1.2Ghz kernel + setCPU but your CPU only really runs an average of 1Ghz because it throttles down more often than not.

You could have BBv1.1 + 1Ghz kernel and it would be the same, except more room and resources because you don't have setCPU installed, nor is it running in the background non-stop.

Did that make sense now?

[czerdrill]

what do you think pete's script setting to ondemand is doing? Do you think that the 1.2 kernel using pete's script is set to 1.2 no matter what? i hope not, because then you REALLY don't understand what's going on...

obviously if all my profiles are set to 1.2 all day, 24/7 i'm going to get higher temps. that would be just like me running pete's script without setcpu and using my phone all day 24/7...again, and i hate to ask this again...what are we arguing?

Again, I know exactly what the pete script is doing, it sets the CPU to use the highest available slot.

Let me try to explain this in a more simple kid like approach.

You have BBv1.1 + 1.2Ghz kernel + setCPU but your CPU only really runs an average of 1Ghz because it throttles down more often than not.

You could have BBv1.1 + 1Ghz kernel and it would be the same, except more room and resources because you don't have setCPU installed, nor is it running in the background non-stop.

Did that make sense now?

and now let me explain it in babyspeak:

do you agree that a lower kernel (or a lower speed) uses less battery...i am praying that you say yes, because if you say no, then i will be stunned haha

do you agree that's pete's script can't distinguish between 105 degrees and 150 degrees? again, I am praying that you say yes.

do you agree that pete's script cannot distinguish between 100% battery and 5% battery? still praying.

if you answered yes to all of the above, then please explain how using setCPU profiles wouldn't give you more battery life and cooler temps.

if you answered no to any of the above questions, then believe it or not, i can fly. without a broom stick. (I'm assuming you'll believe anything...)

You're the guy who said we should ask pete for his "source" right? yeah...i thought as much...you don't even realize that his "source" is right there for us to look at...and you're trying to talk to me with a "simple kid like approach"? laughable...i think you should spend time hunting for pete's source since it's so elusive...

[GDO7]

This is all honestly quite comical. Quite frankly, unless both of you have the exact same phone, programs, and apps running all at the same time then everything you are arguing is a completely moot point.

The profile aspect of setCPU is definitely something I personally take advantage of so I can have a program that regulates my speeds in certain situations and in turn conserves battery. It also prolongs battery failure due to the fact that I can have the phone throttle down at a certain temp. The battery itself is only rated for 60* celcius or 140* F so it would be safe to assume anythign over what the battery is rated for could possibly throw the battery itself into a thermal runaway and thus possibly destroy the battery. The CPU itself is rated for 170*F, but what about teh other components? Not so much.

I personally am running setCPU with BB1.1 on a 1.2ghz kernel because I WANT to be able to have a program monitor my temps for me amongst other things as opposed to having to resort to the touch test. I don't want to wait until my phone feels like it might be fairly hot and then have to research the actual temp and then act accordingly when I can have a program that will do the very thing for me.

Do I need the 1.2ghz kernel? Maybe or maybe not, but I do like to have the option of it being there if the situation ever arises. My only other option would be to run 800mhz and if I need more then I would have to load another kernel.

Of course this is just all my personal WANTS.