What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

OverClocking 101

Status
Not open for further replies.
You are the man sir! this thread helped so much. I read it when it was just a baby before all 39 pages and it convinced me it was safe to overclock. I can run the 1.25ulv kernels (im a lucky duck) but they heated up just a little too quick for me, and the 1.2 ulv is by far the most stable i have found. Thanks!

While im here, let me ask, are the recommended advanced settings still

30,000
50
0
0

and i might as well toss my profiles in here

screen off 250-400
cpu temp over 55 250-550
temp over 55 250-550
charging/full 250-1200
battery under 20 250-400
battery under 30 250-550
battery under 40 250-800

hows all this look?

I have been running 30000, 50, 0, 0 for the last month. I really have no complaints about it. With my normal usage, I still get 18 to 24 hours between charges. Froyo 2.2 really fixed a LOT of issues with governors as far as I am concerned. I doubt the code changed in that area much but the over OS did change a lot and I suspect the governors now work as originally intended.

And your Profile looks good.
 
Id suggest setting your battery < values up by 1 degree. The phone status goes by 10's, so the below 40 percent clock wont start until your battery shows 30 percent. and by the time you get to your 20 percent setting...it wont clock down even more until your phone says...plug into charger.

Set them for 41,31, and 21 percent.
 
Id suggest setting your battery < values up by 1 degree. The phone status goes by 10's, so the below 40 percent clock wont start until your battery shows 30 percent. and by the time you get to your 20 percent setting...it wont clock down even more until your phone says...plug into charger.

Set them for 41,31, and 21 percent.

Good catch! I totally missed that. On the Droid 1 that is essential.
 
Id suggest setting your battery < values up by 1 degree. The phone status goes by 10's, so the below 40 percent clock wont start until your battery shows 30 percent. and by the time you get to your 20 percent setting...it wont clock down even more until your phone says...plug into charger.

Set them for 41,31, and 21 percent.

Good catch! I totally missed that. On the Droid 1 that is essential.

well, I have been trying to read up on this...there is a LOT of info. You have done a lot of work...and it has helped thousands of people Im sure. Pretty cool when you think of it that way! I know it has helped me..and I am thankful for it.

Im curious about the advanced settings for myself.

I am using chevy ss4.7 and chevy mv 1.o ghz kernel (my phone doesnt seem to like LV kernels for some reason). I set profiles very similar to the above post, but Im curious as to the autodetect speeds in the device selections on set cpu.

Right now my advanced settings are 30000,50,0,0...and Im wondering if that is an optimal setting. I believe when I did autodetect...it recommended 32000,93,0,0.

Have you found an advance setting that has proven to be more effective than another?
 
Id suggest setting your battery < values up by 1 degree. The phone status goes by 10's, so the below 40 percent clock wont start until your battery shows 30 percent. and by the time you get to your 20 percent setting...it wont clock down even more until your phone says...plug into charger.

Set them for 41,31, and 21 percent.


I havnt tested it but to me it seems like the phone only TELLS us in ten percent intervals. I am sure with all the wonderful things the droid can do that it knows its own charge more than what it tells us.
 
Id suggest setting your battery < values up by 1 degree. The phone status goes by 10's, so the below 40 percent clock wont start until your battery shows 30 percent. and by the time you get to your 20 percent setting...it wont clock down even more until your phone says...plug into charger.

Set them for 41,31, and 21 percent.


I havnt tested it but to me it seems like the phone only TELLS us in ten percent intervals. I am sure with all the wonderful things the droid can do that it knows its own charge more than what it tells us.

well, I can tell you (and you can observe for yourself too) that if you leave your clock setting down to lets say 550 for batt<40 percent....when your battery gets to 40 percent...its still running your main setting...ex: 1000mhz. Its not until the cpu shows 30 percent when your 40 percent profile kicks in. So whatever the case...the cpu is not reporting battery in increments less than 10 percent. And that is how nearly all battery monitor apps report as well.

trust me...Ive done it

the increments above should be raised 1 degree.
 
Last edited:
Id suggest setting your battery < values up by 1 degree. The phone status goes by 10's, so the below 40 percent clock wont start until your battery shows 30 percent. and by the time you get to your 20 percent setting...it wont clock down even more until your phone says...plug into charger.

Set them for 41,31, and 21 percent.

Good catch! I totally missed that. On the Droid 1 that is essential.

well, I have been trying to read up on this...there is a LOT of info. You have done a lot of work...and it has helped thousands of people Im sure. Pretty cool when you think of it that way! I know it has helped me..and I am thankful for it.

Im curious about the advanced settings for myself.

I am using chevy ss4.7 and chevy mv 1.o ghz kernel (my phone doesnt seem to like LV kernels for some reason). I set profiles very similar to the above post, but Im curious as to the autodetect speeds in the device selections on set cpu.

Right now my advanced settings are 30000,50,0,0...and Im wondering if that is an optimal setting. I believe when I did autodetect...it recommended 32000,93,0,0.

Have you found an advance setting that has proven to be more effective than another?

The overall affect or "difference" between those two settings is two fold:
a) Battery usage
b) Initial application execution speed.

The sampling rate difference simply can't be measured but the Threshold can be.

At 50% UpThreshold the Android OS is going to ramp up the slots in the kernel very quickly. Which will use more battery. But the counter to this is Applications will be very snappy because they will be running at a higher frequency the majority of the time.

Now at 93% UpThreshold the battery is actually catching a break if the OS doesn't load up. Which in most instances, when in sleep/standby and light use is the case. So that battery savings can add up. But the down side is some apps "might" be a tad sluggish on launch and/or resume as the OS does load up with work.

Personally, if I can get a day of use (18 to 24 hours) between charges, then I call it a good day. At present I can hit that mark using 30000, 50, 0, 0. But you might want to try both and see if you can actually tell a difference. Because 2.2 is so much faster than 2.1 with no modifications, you might not even notice a difference going with 32000, 93, 0, 0.
 
Id suggest setting your battery < values up by 1 degree. The phone status goes by 10's, so the below 40 percent clock wont start until your battery shows 30 percent. and by the time you get to your 20 percent setting...it wont clock down even more until your phone says...plug into charger.

Set them for 41,31, and 21 percent.


I havnt tested it but to me it seems like the phone only TELLS us in ten percent intervals. I am sure with all the wonderful things the droid can do that it knows its own charge more than what it tells us.

I said the same exact thing when I was delving deep into the Droid 1s inner workings. "It can't be that hard for it to do 1% detection". Boy did I end up being wrong. And here is the "why":

The Droid 1 can detect the mV (micro Volt) of the battery in real time. The issue is the accuracy of reading it in real time. The first 20% (from 100% down to 80%) and then the last 20% both show sever "Rubber Banding" in the data readings. This equates to the reading showing one voltage level one second and a higher voltage reading the next second because the work load on the phone has been reduced. Which means you could read 3.758 mV while the screen is on and using GPS but as soon as you stop GPS and browse a web page it could suddenly read 3.792 mV. Simply put the battery load was reduced so it can snap back to a static level. The other way to detect a batteries charge is asking it directly "What is your percentage" and unfortunately the battery we use only responds with 10% measurements until it reaches 15% charge. Why they made it that way? No clue. But it is what we have to live with.
 
Id suggest setting your battery < values up by 1 degree. The phone status goes by 10's, so the below 40 percent clock wont start until your battery shows 30 percent. and by the time you get to your 20 percent setting...it wont clock down even more until your phone says...plug into charger.

Set them for 41,31, and 21 percent.


I havnt tested it but to me it seems like the phone only TELLS us in ten percent intervals. I am sure with all the wonderful things the droid can do that it knows its own charge more than what it tells us.

I said the same exact thing when I was delving deep into the Droid 1s inner workings. "It can't be that hard for it to do 1% detection". Boy did I end up being wrong. And here is the "why":

The Droid 1 can detect the mV (micro Volt) of the battery in real time. The issue is the accuracy of reading it in real time. The first 20% (from 100% down to 80%) and then the last 20% both show sever "Rubber Banding" in the data readings. This equates to the reading showing one voltage level one second and a higher voltage reading the next second because the work load on the phone has been reduced. Which means you could read 3.758 mV while the screen is on and using GPS but as soon as you stop GPS and browse a web page it could suddenly read 3.792 mV. Simply put the battery load was reduced so it can snap back to a static level. The other way to detect a batteries charge is asking it directly "What is your percentage" and unfortunately the battery we use only responds with 10% measurements until it reaches 15% charge. Why they made it that way? No clue. But it is what we have to live with.

thanks for explaining that
 
I have a newbie question. I tried P3 LV kernel and Chevy ULV kernel. For both kernels, my phone overheats (CPU over 50C and battery over 45C) once I OC to 900MHz. So, is 800MHz the limit of my phone? If I use MV or SV kernel, will they help the overheating issue? Thanks.

BTW, the overheating always happens when I'm using Dolphin HD to surf the web. Why is that?
 
yes skull thanks for the explaination about battery reporting. I didnt know that. I am going to try with both settings and see what I come up with in terms of battery life/temps etc.
 
I have a newbie question. I tried P3 LV kernel and Chevy ULV kernel. For both kernels, my phone overheats (CPU over 50C and battery over 45C) once I OC to 900MHz. So, is 800MHz the limit of my phone? If I use MV or SV kernel, will they help the overheating issue? Thanks.

BTW, the overheating always happens when I'm using Dolphin HD to surf the web. Why is that?

OK. The heat is being generated by the 3G antenna. If you are surfing heavily and all over the place pulling down full sites then the phone will get warm. 50c is not by any stretch overheating at all. I have my Droid set to clock down when the CPU hits 52c. I regularly operate at 47c - 50c when using the phone heavily and have been since day one. Nothing new and nothing to really worry too much about. The one thing you will notice though is that your battery life will be woefully shorter than normal the longer the phone is "warm".
 
OK. The heat is being generated by the 3G antenna. If you are surfing heavily and all over the place pulling down full sites then the phone will get warm. 50c is not by any stretch overheating at all. I have my Droid set to clock down when the CPU hits 52c. I regularly operate at 47c - 50c when using the phone heavily and have been since day one. Nothing new and nothing to really worry too much about. The one thing you will notice though is that your battery life will be woefully shorter than normal the longer the phone is "warm".

Thanks for the explanation. I feel better now. But what about the kernel with different voltage? Will they help the temperature profile, or just for battery life?
 
OK. The heat is being generated by the 3G antenna. If you are surfing heavily and all over the place pulling down full sites then the phone will get warm. 50c is not by any stretch overheating at all. I have my Droid set to clock down when the CPU hits 52c. I regularly operate at 47c - 50c when using the phone heavily and have been since day one. Nothing new and nothing to really worry too much about. The one thing you will notice though is that your battery life will be woefully shorter than normal the longer the phone is "warm".

Thanks for the explanation. I feel better now. But what about the kernel with different voltage? Will they help the temperature profile, or just for battery life?

Both. Lower voltage generally translates to lower heat and better battery life.
 
Status
Not open for further replies.
Back
Top