OverClocking 101

[Skull One]

I hope the pictures help with the explanation. It never occurred to me, when I first started this, to do pictures until I was reviewing the thread tonight and saw the benchmark screen capture. It was one of those "OMG" moments.

 

[Phxphenom]

The pics are great as I have my SetCPU opened while reading the post and it really helps me relate to your writeup. I am currently running a Chevy 1.2 Ghz Kernel that I had to clock down to 1.1Ghz. I am going to model what you have in the pics and see the difference. I may download a bunch of P3Droid and Chevy kernels and start experimenting to see what gives me the greatest results without my Droid Fcing.....

Thanks for your contribution to the community!

I hope the pictures help with the explanation. It never occurred to me, when I first started this, to do pictures until I was reviewing the thread tonight and saw the benchmark screen capture. It was one of those "OMG" moments.

 

[Phxphenom]

It would be very cool if the top display bar (say next to the tiny battery icon) showed the actual CPU speed the Droid was running...

 

[Skull One]

I would like to thank JBPruitt for pointing out something, in another thread, I missed in my hurry to get my thread updated.

My original BAD sequence that I took a screen capture of and listed.

If you look at my simple profile it works like this:
If the Droid is in Screen Off/Standby, it is clocked to 125/400.
If the Battery Temp is > than 44.9C, it is clocked to 125/500.
If the Battery is charging (regardless of USB or Wall), it is clocked to 125/800.
If the Battery is < 41%, it is clocked to 125/600.
If the Battery is < 21%, it is clocked to 125/400.


The now CORRECT sequence.
If you look at my simple profile it works like this:
If the Droid is in Screen Off/Standby, it is clocked to 125/400.
If the Battery Temp is > than 44.9C, it is clocked to 125/500.
If the Battery is charging (regardless of USB or Wall), it is clocked to 125/800.
If the Battery is < 21%, it is clocked to 125/400.
If the Battery is < 41%, it is clocked to 125/600.

The last two items HAVE TO BE reversed. The reason of course is SetCPU doesn't understand intentions, it does exactly what it is told. So my original list would always hit the first Battery < profile and say "I meet that condition, so stop and execute". Well that isn't what I wanted it to do, I need it to check each level of the battery in reverse order and then set the proper profile.

When I first started playing with SetCPU 2.0 I only had one Battery <. When I wrote the article, I took the first set of pictures about an hour apart, well the difference in time was because I noticed I didn't have TWO examples of Battery <. So I added one, took a picture, wrote in the extra example and thought "Finally done" because I was tried and wanted to call it a night. Mistake! I promise I will try not rush a major update again

Again, thanks goes to JBPruitt!

 

[EbE404]

Excellent comments and thoughts, as always, Skull.

Thanks!

 

[hookbill]

Totally Confused

I apologize in advance for the amount of stupidity you may be reading from this point forward.

The new version of SetCPU and my own decision to go with a 125-11000 kernel has got me really confused.

First I have read that the Droid won't even perform at 125, so I've set all my minimums to 400 mghz. This is for everything.

I've got my fail safe temperature set at 50c. 400 max 125 minimum
Charging full 1ghz and 400min
Charging AC/full 1ghz 400 min
Charging USB 1gnz 400 min
Charging AC/Full 1ghz 400min
Screen off priority 500 max 400 min
Battery <20% 400 max 125 min
CPU Temp >50.0 C 400 mx 125 min
Temp 50.0 C 1000max 125 min

I'm not running anything at 11ghz

It honestly seems to be running fine at these settings. Skull One, suggestions?

 

[Skull One]

I apologize in advance for the amount of stupidity you may be reading from this point forward.

The new version of SetCPU and my own decision to go with a 125-11000 kernel has got me really confused.

First I have read that the Droid won't even perform at 125, so I've set all my minimums to 400 mghz. This is for everything.

I've got my fail safe temperature set at 50c. 400 max 125 minimum
Charging full 1ghz and 400min
Charging AC/full 1ghz 400 min
Charging USB 1gnz 400 min
Charging AC/Full 1ghz 400min
Screen off priority 500 max 400 min
Battery <20% 400 max 125 min
CPU Temp >50.0 C 400 mx 125 min
Temp 50.0 C 1000max 125 min

I'm not running anything at 11ghz

It honestly seems to be running fine at these settings. Skull One, suggestions?

Ok, I specifically stated PRIOR to Froyo 2.2 that Droid does not work at 125Mhz with custom ROMs. So you are not crazy or confused. But I did, in a few places buried in this thread, say the Froyo 2.2 FIXED that issue. So you are going to be able to use it now. And believe me, it is truly fixed.

And yes, you can run with everything set at 400Mhz. The only issue is battery life might be a little lower. In fact, I think I will test that condition ASAP.

Also it is 1.1 Ghz not 11 Ghz. I wish the Droid was that fast thought.

And why we are here, lets arrange these in a nice order

Screen off - 500 max 400 min (Set at Priority: 100)
fail safe temperature set at 50c. 400 max 125 minimum (Set at Priority: 90)
CPU Temp >50.0 C 400 mx 125 min (Set at Priority: 80)
Charging full 1ghz and 400min (Set at Priority: 70)
Battery <20% 400 max 125 min (Set at Priority: 60)

Ok the ones below here, they can be deleted because they duplicate rules from above.

*Charging USB 1gnz 400 min
*Charging AC/Full 1ghz 400min
*Temp 50.0 C 1000max 125 min

Hope that helps clear things up.

 

[EbE404]

CPU Temp >50.0 C 400 mx 125 min (Set at Priority: 80)

One comment I would make about this setting is to be rather cautious with this particular profile. I know that in many of the Froyo builds out there, the OMAP3 temp sensor was either inaccurate or not working at all (people were reporting readings of 0 C, which would be great, but I don't think they're running around with liquid cooled phones)

In my case, I just checked and I'm reading 51 C, which I do not think is accurate, as the phone has been idling with the screen off for the past couple of hours.

The ROM I'm using is Kangerade V4.0.7, which is based on the most current Froyo code, but I haven't heard if this OMAP3 sensor issue was resolved in this latest code batch.

One other thing I'm noticing in SetCPU is that I am not getting any "Time in State" measurements-everything is 0. Is anybody else experiencing that?

 

[Phxphenom]

Now I am a bit confused. I am running the Chevy 1.2GHz kernel that has a minimum clock speed of 250Mhz....It is the Ultra Low voltage kernel....Should I be using one that now goes down to 125 Ghz to conserve Battery? Choices, Choices, choices......

 

[furbearingmammal]

The ULV kernel at 250 uses about the same amount of juice as a regular LV kernel at 125. I'm not sure which edges out which, but the ULV will use less at higher speeds, so it's probably a good trade to keep the ULV kernel.

Someone correct me if I'm wrong!

Personally I'd like to see the 125 back on Chevy's kernels, but he's the Dev and until I learn Linux compiling (HAH!) he's in charge. My 1550ish Quadrant scores tell me he's got the right ideas with his 1100mhz ULV kernel, and I'm pulling in better battery life than I was stock!

 

[Phxphenom]

My 1550ish Quadrant scores tell me he's got the right ideas with his 1100mhz ULV kernel, and I'm pulling in better battery life than I was stock!

That is interesting. I have my Chevy kernel maxed out at 1.1Ghz since otherwise I end up with FCs.....My Quadrant score is 1399 which is quite a bit less than your 1550ish yet we both have the same Max CPU setup.....

Guess I should probably just load up the same 1.1Ghz kernel you are using and compare scores.....

 

[furbearingmammal]

My 1550ish Quadrant scores tell me he's got the right ideas with his 1100mhz ULV kernel, and I'm pulling in better battery life than I was stock!

That is interesting. I have my Chevy kernel maxed out at 1.1Ghz since otherwise I end up with FCs.....My Quadrant score is 1399 which is quite a bit less than your 1550ish yet we both have the same Max CPU setup.....

Guess I should probably just load up the same 1.1Ghz kernel you are using and compare scores.....

My last run was 1556, today, on battery, when it was over 80 degrees out. I was astounded, but I've been getting higher scores on FRF84B than I did on FRF57.

My phone LOVES this kernel. I can run at 1200 ULV but the heat buildup was insane and eventually caused a lockup/battery pull. ULV 1250 caused a bootloop, which just stresses the point people make about finding a kernel your phone likes. I changed the up threshold to 85 and left the sampling rate and everything else alone.

I also had airplane mode on. I don't know if that made much of a difference but I suspect it might. I was in an area where the best signal I was getting was -103dB.

 

[Phxphenom]

That does it! I will give Chevy 1.1GHz a go....By the way, it is 9:20Pm here in Phoenix and it is 93F outside...

 

[furbearingmammal]

That does it! I will give Chevy 1.1GHz a go....By the way, it is 9:20Pm here in Phoenix and it is 93F outside...

I'll take my 87 in the shade at 6:30PM, thanks.

Make sure you're running the kernel from his 4.3 Simply Stunning build. The ones from 4.2 lack Conservative and Powersave power management profiles. Oh, and they're the ones I used. If you can't find them, let me know. I'll send you a copy of mine if I have to.

 

[Phxphenom]

Thanks, I switched to Chevy 1.1 ULV ensuring I used the latest version (4.3) and my Quadrant scored increased to 1,485! Linpack is about 17.3.....

Now to keep an eye out for FCs...I also upgraded my System Panel ($1.99) as it has some additional features I thought were worth the 2 bucks.

Thanks,
Marc