OverClocking 101

[Skull One]

First off I would like to say that what you have done here is invaluable for the community we have here with the Droid. I can say that I, as well as just about anyone else who has opened this thread up cant thank you enough for all the time and hard work that you have put into all of this; everything is set up so it is understandable to almost everyone, from the basic user who just rooted their phone, to the die-hard advanced users.

As for me, I am in a toss up as to what to do with my advanced settings. I have briefly looked through here and saw some things that might help base what I do off of, but I would like to hear it from the man himself.

Pretty much what I am going for is:
FAST, and also will last a full day (at least 18 hours and not be at 0% lol [Phone cant handle anything above a 1Ghz kernel, at least last time I checked it couldn't]). As I am right now I can expect about 16-24 hours of battery life with my current setup.

250-1.0Ghz
Screen off - 250 max 250 min (100) ondemand
Temp > 51.5c 550 max 250 min (95) conservative
Charging USB/Full 1000 max 250 min (81) ondemand
Charging AS/full 800 max 250 min (80) ondemand
Battery < 20% 400 max 250 min (75) conservative
Battery < 31% 550 max 250 min (70) conservative
Battery < 41% 700 max 250 min (65) conservative
And as far as the advanced settings go, well, they have not been changed.
Once again thank you for all the hard work. I'll be checking back here daily to see whats up.

First off, thank you for the kind words.

As I mentioned in my response to Hookbill, which is what took me so long to respond to your question, I am finding that certain settings don't always restore properly after a reboot. It almost seems like Froyo 2.2, that is built from source, sets the values twice. Once during boot and again after all the startup programs finish. I have been looking at this now since Sunday and really don't have a good explanation for it.

The good news is, the setting it seems to default to in advanced (32000, 50, 0, 0) actually does a really good job and I go 24 hours with no issue between charges.

I am interested in hearing if you run custom ringtones and if they play correctly when coming out of a long standby/sleep with your settings at 250/250. I run a 125/400 and I think my Droid only misses a ringtone once every 15th call or so right now. Of course, I also use Voice Caller ID which takes up CPU time as well as the phone switches fully awake.

 

[Hahn24]

i think this is a great guide to all of this. alot of good information. i just am a little confused on being brand new to this and just have rooted my phone. I just downloaded setcpu and want my phone to be quicker then it is stock but also to have decent battery life. im just on rooted 2.1. could anyone give me just like a good setting to sit at where my phone will be quick and with good battery life? thanks a ton. im going to keep reading up on this in the mean time.

 

[Skull One]

i think this is a great guide to all of this. alot of good information. i just am a little confused on being brand new to this and just have rooted my phone. I just downloaded setcpu and want my phone to be quicker then it is stock but also to have decent battery life. im just on rooted 2.1. could anyone give me just like a good setting to sit at where my phone will be quick and with good battery life? thanks a ton. im going to keep reading up on this in the mean time.

You should be able to use the baseline setting I have in post #2.

But you might want to change the advanced to 65000, 70, 0, 70 and see how that works out.

 

[Corinacakes]

OK so what version are you talking about now skull? I'm still on 1.5.1a becuz I never got clearance from you to update!

 

[Skull One]

OK so what version are you talking about now skull? I'm still on 1.5.1a becuz I never got clearance from you to update!

2.0.1 is very stable
See post #2 for the tutorial.

 

[Corinacakes]

:woot: ty, ty!

 

[NewDroidOrder]

First off I would like to say that what you have done here is invaluable for the community we have here with the Droid. I can say that I, as well as just about anyone else who has opened this thread up cant thank you enough for all the time and hard work that you have put into all of this; everything is set up so it is understandable to almost everyone, from the basic user who just rooted their phone, to the die-hard advanced users.

As for me, I am in a toss up as to what to do with my advanced settings. I have briefly looked through here and saw some things that might help base what I do off of, but I would like to hear it from the man himself.

Pretty much what I am going for is:
FAST, and also will last a full day (at least 18 hours and not be at 0% lol [Phone cant handle anything above a 1Ghz kernel, at least last time I checked it couldn't]). As I am right now I can expect about 16-24 hours of battery life with my current setup.

250-1.0Ghz
Screen off - 250 max 250 min (100) ondemand
Temp > 51.5c 550 max 250 min (95) conservative
Charging USB/Full 1000 max 250 min (81) ondemand
Charging AS/full 800 max 250 min (80) ondemand
Battery < 20% 400 max 250 min (75) conservative
Battery < 31% 550 max 250 min (70) conservative
Battery < 41% 700 max 250 min (65) conservative
And as far as the advanced settings go, well, they have not been changed.
Once again thank you for all the hard work. I'll be checking back here daily to see whats up.

First off, thank you for the kind words.

As I mentioned in my response to Hookbill, which is what took me so long to respond to your question, I am finding that certain settings don't always restore properly after a reboot. It almost seems like Froyo 2.2, that is built from source, sets the values twice. Once during boot and again after all the startup programs finish. I have been looking at this now since Sunday and really don't have a good explanation for it.

The good news is, the setting it seems to default to in advanced (32000, 50, 0, 0) actually does a really good job and I go 24 hours with no issue between charges.

I am interested in hearing if you run custom ringtones and if they play correctly when coming out of a long standby/sleep with your settings at 250/250. I run a 125/400 and I think my Droid only misses a ringtone once every 15th call or so right now. Of course, I also use Voice Caller ID which takes up CPU time as well as the phone switches fully awake.

Thank you for your response, I'll be throwing that in there now. Anyway, as far as my custom ringtones go, its pretty hit n miss when it comes to playing correctly. My standard custom ringtone that I have set is one that I created, and then I have another one for my girlfriend when she calls. The only time there is any kind of complication is with her ringtone. Rather than playing her ringtone it played the one that I have set for everyone. I'm now on a new kernel and im goin to try out my screen off to be set at 125/400 and see how that goes.

 

[dpaine88]

Hey Skull,

First off I would love to thank you for all this useful info, and without it I would have no idea what I was doing. You are doing a wonderful thing for the Droid community.:heart:

With that said, I have only been rooted for like 4 days now so I am screwing around with various kernels still.

Currently running Chevyno1's ULV 1.1Ghz (switching anywhere from 800 max to 1.1 max).
Running Bugless Beast v0.4.
Currently have the settings you listed in post #2.
For Advanced I have the standard 32000, 50, 0 , 0.

Any changed I should make?



However I have two questions:

1) Regarding voltage(which I read an FAQ on), for whatever reason, the only 125mhz Kernel I can use is 800mhz for P3. If I try any higher of P3y It only shows the min as 250mhz.

I can however use Chevyno1's ULV pretty stable.

There may not be an answer for this or it may be dependent on devices but would the battery life and performance be any different if you had (for example) an 800mhz Chevy ULV kernal with 800 max and 250 min vs a P3 800mz LV but the LV has 125mhz?

2) What are your thoughts on using A) Juice Defender and B) Auto Memory Manager set on Aggressive.

I see a good amount of people saying that they found better battery life with these installed.


Thanks Skull for any information you can give me.

 

[Skull One]

Hey Skull,

First off I would love to thank you for all this useful info, and without it I would have no idea what I was doing. You are doing a wonderful thing for the Droid community.:heart:

With that said, I have only been rooted for like 4 days now so I am screwing around with various kernels still.

Currently running Chevyno1's ULV 1.1Ghz (switching anywhere from 800 max to 1.1 max).
Running Bugless Beast v0.4.
Currently have the settings you listed in post #2.
For Advanced I have the standard 32000, 50, 0 , 0.

Any changed I should make?



However I have two questions:

1) Regarding voltage(which I read an FAQ on), for whatever reason, the only 125mhz Kernel I can use is 800mhz for P3. If I try any higher of P3y It only shows the min as 250mhz.

I can however use Chevyno1's ULV pretty stable.

There may not be an answer for this or it may be dependent on devices but would the battery life and performance be any different if you had (for example) an 800mhz Chevy ULV kernal with 800 max and 250 min vs a P3 800mz LV but the LV has 125mhz?

2) What are your thoughts on using A) Juice Defender and B) Auto Memory Manager set on Aggressive.

I see a good amount of people saying that they found better battery life with these installed.


Thanks Skull for any information you can give me.

Everything I have in post #2 is what I have been running since that day. Found no reason to change it so far.

Your first question is the "$64K Question". I wish I could answer it. But for now "Every Droid is unique" is the best answer I have.

Second question is almost controversial. There are people that swear by task killers and programs like Juice Defender. Others will say they are useless. I think the answer is somewhere in the middle. I don't use either. But I have done some things to mitigate the need for them. I use "Autostarts" to turn off programs on boot and I use System Panel to monitor for programs that hog CPU time when idle. If a program runs too much, I find another app to replace it that doesn't.

 

[dpaine88]

Thanks Skull for all the information, loving autostarts so far!

You may or may not be able to field this question for me since its sliiightly off topic but anyways.

So turns out all of chevyno1's ULV run fast, but cant last an hour without hanging or rebooting.

Right now I am using p3 800mhz/125mhz. I downloaded 1.25 and 1.1 of p3 125mhz versions but they will not allow my setCPU slider to go down past 250mhz, only the 800mhz kernel allows this even though they are the correct downloads and not the 250mhz versions.

Any thoughts on why this might be?

 

[Skull One]

Thanks Skull for all the information, loving autostarts so far!

You may or may not be able to field this question for me since its sliiightly off topic but anyways.

So turns out all of chevyno1's ULV run fast, but cant last an hour without hanging or rebooting.

Right now I am using p3 800mhz/125mhz. I downloaded 1.25 and 1.1 of p3 125mhz versions but they will not allow my setCPU slider to go down past 250mhz, only the 800mhz kernel allows this even though they are the correct downloads and not the 250mhz versions.

Any thoughts on why this might be?

None actually. And very odd to say the least.

What ROM are you using?

 

[dpaine88]

None actually. And very odd to say the least.

What ROM are you using?

Im rollin with BB v0.4 right now.

p3 is definitly running better than Chevys ULV of the same speed so far.

Right now I have 1.25/250 but would love to get 1.25ghz/125mhz so I could come as close to a ULV as possible(using 125mhz min).

Tried it several times, using 1.0, 1.1 and 1.25 and only the 800 allows the 125mhz min.

 

[Aixelsyd]

Some thing is not right because I've used all the different P3 kernels that use the 125Mhz slot and have no trouble with them. I currently have his 900Mhz kernel install and have the setting for use at 125Mhz. Personally tho this idea of ULV kernels is questionable IMO as there is not that much of a difference from what I'm told. That said and speaking for myself I seem to get much much better battery life out of a low or standard voltage kernels depending on whos they are.

And as far as using a 125Mhz or 250Mhz slot kernel make no difference from what I've found so far. When the device is in sleep mode the different between 125 and 250 is so minimal it really seems to have no affect on my end at least unless you have a boatload of things running in the backround.

One suggestion tho as I have run into this when messing wit ha buddies phone. For some reason after a flash and reinstalling all his stuff including CPU I couldn't get anything to set correctly after a reboot. Knowing I had the correct kernel I went ahead and just uninstalled setCPU. Did a quick reboot of the device and then reinstalled via the Market and it seemed to clear up the glitch. If you haven't done so alreayd I'd maybe try that out and move forward frmo there.

 

[dpaine88]

Some thing is not right because I've used all the different P3 kernels that use the 125Mhz slot and have no trouble with them. I currently have his 900Mhz kernel install and have the setting for use at 125Mhz. Personally tho this idea of ULV kernels is questionable IMO as there is not that much of a difference from what I'm told. That said and speaking for myself I seem to get much much better battery life out of a low or standard voltage kernels depending on whos they are.

And as far as using a 125Mhz or 250Mhz slot kernel make no difference from what I've found so far. When the device is in sleep mode the different between 125 and 250 is so minimal it really seems to have no affect on my end at least unless you have a boatload of things running in the backround.

One suggestion tho as I have run into this when messing wit ha buddies phone. For some reason after a flash and reinstalling all his stuff including CPU I couldn't get anything to set correctly after a reboot. Knowing I had the correct kernel I went ahead and just uninstalled setCPU. Did a quick reboot of the device and then reinstalled via the Market and it seemed to clear up the glitch. If you haven't done so alreayd I'd maybe try that out and move forward frmo there.

Thanks for all the info man.

This just gets weirder... So I uninstalled SetCPU, rebooted and redownloaded.

Open it and find all weird mhz ranges up to 528 max and 250 min. It does let me adjust the slider all the way down to 19.2 Mhz.

However for my current mhz it shows it peaking at 600 mhz in SetCPU. System monitor just shows 0 mhz the entire time.

Considering backing up my data and wiping as now I cant even get it to how it was haha

EDIT: Reinstalled Kernel and deleted SetCPU and on reboot System Monitor still cannot pick up any mhz but does pick up on CPU % and network.

EDIT 2: Did more installing/rebooting and got SetCPU reading properly, but still only down to 250mhz.

 

[Aixelsyd]

If it is allowing you to go down to 19.2 like you mentioned sounds to me like you have the wrong device selected now. I'd press menu and reselect what device. And in doing so make sure you select Autodetect. Anything else will cause nothing but issues as I've done it on accident myself before. If I were to guess it sounds like you have selected Custom frequencies

Edit: Shortly I'll upload a copy of P3's 1.0Ghz kernel with the 125Mhz slot. It is on my sons phone currently and I know for a fact it is allowing you to select 125Mhz. If it doesn't on your end there there is something else going on.

Here ya go http://www.***********/file/UDZaephS/LV-125-1000-v32kernel.html