OverClocking 101

[Skull One]

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?

If the kernel has a voltage in one or more of the seven slots that is too low for your phone, you will get overheating from the OMAP3430's ECC module kicking in to fix data read/write errors.

I always recommend now to test with a Standard or Medium voltage kernel first to see what your phone is initially capable of. Then try lower voltage kernels. And you might have to try several different makers of kernels to find the "best fit" voltage levels for your phone. Since each developer has a different "Idea / Theory" on what is best.

 

[jerroedr]

i recommend chevyno1's kernels, however when messing around with a cvcps with compcache i was regularly over 1700 on my quadrant score.

 

[rmart88]

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.

So if 50 is good for one aspect, and 93 for another... it would be fine to set it at, say, 75?

BTW, AHHHMAZING thread Skull. This thread is the only reason I Rooted and OC'd. Lovin it! Thanks sooo much!!

 

[projekt128]

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.

What should the priorities for each of these settings be set at? Roughly speaking

 

[jerroedr]

100
90
80
70
ect.

but it can be whatever as long as its in descending order

 

[Skull One]

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.

So if 50 is good for one aspect, and 93 for another... it would be fine to set it at, say, 75?

BTW, AHHHMAZING thread Skull. This thread is the only reason I Rooted and OC'd. Lovin it! Thanks sooo much!!

I used to run 50000, 65, 0, 0 and 65000, 75, 0, 0 while under 2.1. And it did make a difference back then. So yes, I could recommend a 35000, 75, 0, 0 with no problem.

 

[yakitori]

Skull

Ive been playing with the advance settings.

I have noticed that my quadrant standard scores are actually higher with the higher up threshold. I get faster response out of my OS when my threshold value is 90 compared to 50...not sure why, but I guess its a good thing if you say it actually gives the battery a break at higher upthreshold. If so...Ill just leave it at 85-90 unless my apps start opening sluggishly.

my quadrant scores went from:

~1100
32000, 50, 0, 0

to

~1380
32000, 90, 0, 0


linpacks are around 11.2-11.5 or so...even though I know they are only standard tests...I would think that testing against my phone at different settings is ok way to scale performance of different settings.

And I have found that the chip I got off the wafer is topped out a little over 1000mhz because when I overclocked to 1100mhz...run any kind of benchmark or quadrant...my phone freezes during the test and I have to pull battery, but I was running 1000mhz w/o any probs. I dont see any more of a performance increase between 1000mhz and 800mhz...so I run it at 800.

That is good news for me because previously I was running ss4.7 with a mv 1.0ghz kernel at 1000mhz OC...temps were constantly around 116-125 with sustained use (I did have failsafe profiles in place). This was pushing the limit of my chips max.

I get the same benchmark scores and linpacks (and my phone is really snappy) after I flashed to UD8.0, chevy lv 1.1ghz kernel, OC to 800mhz with my other profiles still in place. My advance settings are 32000, 90, 0, 0 and my quadrants are 1380s and my linpacks are 11.3 +/- 0.2 And my temps are way lower. Heavy usage only pushes me to about 111..118 if plugged in to wall charger AND playing with phone.

 

[aggiechase37]

I still don't think conservative profile gets enough love around here!

 

[Skull One]

I still don't think conservative profile gets enough love around here!

And I would agree wholeheartedly. The issue I have with it is; How do I test it to show its benefits? Plus it has been changed a lot from 2.1. I am actually trying to download all the source to 2.2 so I can pull each Governor apart to show what it actually does. But I am not having a whole lot of luck because I am using a RedHat ES distro and all the write ups are for Ubuntu at present.

 

[aggiechase37]

I still don't think conservative profile gets enough love around here!

And I would agree wholeheartedly. The issue I have with it is; How do I test it to show its benefits? Plus it has been changed a lot from 2.1. I am actually trying to download all the source to 2.2 so I can pull each Governor apart to show what it actually does. But I am not having a whole lot of luck because I am using a RedHat ES distro and all the write ups are for Ubuntu at present.

That's cool. I've been using conservative for a while now. I notice a lot of gain in battery and not much of a hit in performance. Also interesting is that it sets your advanced settings for you at 300,000, 80, 20, 0, 5. I try to change that first one to lower, but it will reset itself to 156,250 every time. So if you guys are looking for a good battery booster, conservative is certainly something to try out. It's working great for me. btw I am on Chevy LV 1ghz. But I have it clocked at 800mhz normally on setCPU.

 

[jeffe65]

I have a question, but first here are my settings:

P3 kernel, 1250MHz, Std. Voltage
All set OnDemand
Main: 125 min, 1250 max
Battery Temp > 47.5°: 125 min, 600 max, Priority 100
Screen Off: 400 min, 600 max, Priority 90
Charging/Full: 125 min, 600 max, Priority 80
Battery < 21%: 125 min, 400 max, Priority 70
Battery < 41%: 125 min, 800 max, Priority 50

Screen Off is set the way it is because the phone doesn't wake up easily with any kernel, if min is at 250 or lower, and I was missing calls or it just wouldn't let me answer them (not enough response to the slider when I tried to answer), and it wasn't saving applied ringtones for contacts.

Battery temps and life are great, performance is incredible, and no instability issues. I had tried Chevy's 1.1GHz LV kernel, and it gave me force closes and erratic CPU temp readings (Rapid changes from 38° to 47°), so that's why I switched.

My question is, does anyone know of an app that can give CPU temp readings on the P3 kernels? TempMonitor will only give battery, as will SetCPU, and SetCPU won't show "Time in State" with it either. I tried emailing the P3 dev, but no response yet. Battery temp is fine, but the CPU can get hot without realizing it when clocking this high, so that's why my concern.

 

[Aixelsyd]

@Jeffe65 you need to update to one of P3's new kernels that has CPU temp monitor built into it. For a wile there was no way to do it until they figured it out on the Froyo build kernels. Sounds to me like you still have one of his older ones that did not have CPU temp in them when he was first making the kernels for Froyo.

as for an app to get you the CPU temp grab Temp Monitor from the Market. It will report battery and CPU temps as long as the kernel is desinging for it which all his new ones are

 

[Skull One]

I have a question, but first here are my settings:

P3 kernel, 1250MHz, Std. Voltage
All set OnDemand
Main: 125 min, 1250 max
Battery Temp > 47.5°: 125 min, 600 max, Priority 100
Screen Off: 400 min, 600 max, Priority 90
Charging/Full: 125 min, 600 max, Priority 80
Battery < 21%: 125 min, 400 max, Priority 70
Battery < 41%: 125 min, 800 max, Priority 50

Screen Off is set the way it is because the phone doesn't wake up easily with any kernel, if min is at 250 or lower, and I was missing calls or it just wouldn't let me answer them (not enough response to the slider when I tried to answer), and it wasn't saving applied ringtones for contacts.

Battery temps and life are great, performance is incredible, and no instability issues. I had tried Chevy's 1.1GHz LV kernel, and it gave me force closes and erratic CPU temp readings (Rapid changes from 38° to 47°), so that's why I switched.

My question is, does anyone know of an app that can give CPU temp readings on the P3 kernels? TempMonitor will only give battery, as will SetCPU, and SetCPU won't show "Time in State" with it either. I tried emailing the P3 dev, but no response yet. Battery temp is fine, but the CPU can get hot without realizing it when clocking this high, so that's why my concern.

P3Droid has to compile the options in. So he is the only one that can fix the issue. I know cvpcs does have everything compiled in at present.

 

[Aixelsyd]

FYI my mistake as I just talked to P3 he has not updated them o his kernel page yet. I thought he already had done them. He did mention he will try to get them updated this weekend at some point tho.

 

[jeffe65]

FYI my mistake as I just talked to P3 he has not updated them o his kernel page yet. I thought he already had done them. He did mention he will try to get them updated this weekend at some point tho.

Thanks! I'll check the Web site again in a couple of days.