OverClocking 101

[Skull One]

For those that care, see my sig. That is what I'm running and I've noticed an improvement over battery life. I am not using setcpu either. As far as temps goes, I have no idea. Other then it doesn't "feel" hot. But for those that want to know what stock kernel does with 2.2. I'd have no remorse telling you that it runs faster and extends the battery at the same time.
But I think that could also be because I am launching my apps quicker, jit is doing it's thing, and I have picked up on download speeds from 3G somehow (guess baseband update did that) that I don't have my screen on as much. Even w/ more use out of my phone (by simplying playing w/ froyo) I still get longer battery life between charges. And my definition of between charges is once the phone kills itself, do a full battery charge, and remove from charger.
I will not say how many days I can go off a full charge as my definition of use and yours is different.

Yes, base kernel clocks in at 600Mhz when booted without a script or SetCPU. Since 600Mhz under 2.2 is roughly equal to 1000Mhz under 2.1, you will see the same speed but much better battery life.

 

[J. Dub]

Ah, so that explains it. I see said the once blind man.

 

[Phxphenom]

Skull,
I downloaded the just released Bugless Beast v0.2 tonight and then redownloaded Chevy 1.25 LV kernel that I was using in BB v0.1. I still need to scale things back on the max slider of SetCPU to 1.1Ghz but when I open System Panel, the CPU clock only shows either 250Ghz minimum or 1.1GHZ max and no longer shows values in between......same seems to be the case with SetCPU.....

very odd and yes I checked SetCPU to ensure everything is ondemand.


EDIT: Mflops are 17 and Quadrant is 1404 which is as good as it ever was in BB v0.1.....I guess everything is peachy afterall. will keep an eye on battery usage.

 

[DROIDGNRL]

CPU temp anytime soon

Hey skull thanks for the great in-depth posts. I'm wondering if we are going to get kernels with the omap3 cpu temp sensor working any time soon. I'm just kind of leery running without being able to use a fail safe. Any idea if we have to wait for the original source to be released? Also any idea why the devs haven't figured it out yet? I'm sure they are working on it. BTW I got confused reading your post the first time cause I was running P3droid's 125-1200 for froyo and everyone kept mentioning 30000 as the sampling rate for setcpu. but mine was set to 300000 just noticed it when I went to Chevyn01's 1.2 ulv which is set at 32000. Just wondered if anyone else noticed and if that could cause reboots at 1.25 cause I was good at 1.2 but not 1.25. Now BBv0.2 (Pete is the MAN!) Blue Energy(Thanks Roberj13) and (Thanks Chevy) 1.2 ulv 1703 Quadrant and 19.6 Linpack at 1.2.dancedroid

 

[Phxphenom]

Wow DROIDGNRL! So I just had to try the Chevy 1.2ulv Kernel

Since I have been bombing out using the Chevy 1.25Ghz LV kernel and therefore having to have set Max @ 1.1GHZ in SetCPU, I thought I would try the Chevy 1.2ULV that DROIDGNRL just referenced.

So yes I just set my SetCPU to the maximum 1.2slot and she did not bomb out on me.

Linpack MFLOPS = 18.7
Quadrant = 1,439

Not as good as your scores DROIDGNRL but certainly better than I was running.

Thanks and I think I will leave this kernel on for a few days and see how things go.

Again thanks,
Marc

Hey skull thanks for the great in-depth posts. I'm wondering if we are going to get kernels with the omap3 cpu temp sensor working any time soon. I'm just kind of leery running without being able to use a fail safe. Any idea if we have to wait for the original source to be released? Also any idea why the devs haven't figured it out yet? I'm sure they are working on it. BTW I got confused reading your post the first time cause I was running P3droid's 125-1200 for froyo and everyone kept mentioning 30000 as the sampling rate for setcpu. but mine was set to 300000 just noticed it when I went to Chevyn01's 1.2 ulv which is set at 32000. Just wondered if anyone else noticed and if that could cause reboots at 1.25 cause I was good at 1.2 but not 1.25. Now BBv0.2 (Pete is the MAN!) Blue Energy(Thanks Roberj13) and (Thanks Chevy) 1.2 ulv 1703 Quadrant and 19.6 Linpack at 1.2.dancedroid

 

[DROIDGNRL]

no one's gonna believe this!!!!

Lets let my screen shot speak for itself. Must have just got lucky cause my quadrant is usually around 1690-1700!!!!! BBv0.2(oh ya) Blue energy and Chevy's1.2ulv!!!!

 

[Tanknspank]

Lets let my screen shot speak for itself. Must have just got lucky cause my quadrant is usually around 1690-1700!!!!! BBv0.2(oh ya) Blue energy and Chevy's1.2ulv!!!!

I believe you, but that is just insane! Bet you can't reproduce it!

 

[Phxphenom]

That is crazy....What are you doing that perhaps contributes to that score? The Theme? Wow!

 

[DROIDGNRL]

I haven't even come close to that since. (not that I haven't been trying lol) I'm back at a very fast 1700 ish. Anyone have any ideas how it got that high cause I don't.

 

[Skull One]

Skull,
I downloaded the just released Bugless Beast v0.2 tonight and then redownloaded Chevy 1.25 LV kernel that I was using in BB v0.1. I still need to scale things back on the max slider of SetCPU to 1.1Ghz but when I open System Panel, the CPU clock only shows either 250Ghz minimum or 1.1GHZ max and no longer shows values in between......same seems to be the case with SetCPU.....

very odd and yes I checked SetCPU to ensure everything is ondemand.


EDIT: Mflops are 17 and Quadrant is 1404 which is as good as it ever was in BB v0.1.....I guess everything is peachy afterall. will keep an eye on battery usage.

If you have your Advanced settings at 30000, 93 (or lower), 0, 0 then it is possible to see that condition.

 

[Phxphenom]

If you have your Advanced settings at 30000, 93 (or lower), 0, 0 then it is possible to see that condition.

My advanced settings that came with the Chevy 1.2 ULV kernel are 32000,50,0,0

 

[Skull One]

Hey skull thanks for the great in-depth posts. I'm wondering if we are going to get kernels with the omap3 cpu temp sensor working any time soon. I'm just kind of leery running without being able to use a fail safe. Any idea if we have to wait for the original source to be released? Also any idea why the devs haven't figured it out yet? I'm sure they are working on it. BTW I got confused reading your post the first time cause I was running P3droid's 125-1200 for froyo and everyone kept mentioning 30000 as the sampling rate for setcpu. but mine was set to 300000 just noticed it when I went to Chevyn01's 1.2 ulv which is set at 32000. Just wondered if anyone else noticed and if that could cause reboots at 1.25 cause I was good at 1.2 but not 1.25. Now BBv0.2 (Pete is the MAN!) Blue Energy(Thanks Roberj13) and (Thanks Chevy) 1.2 ulv 1703 Quadrant and 19.6 Linpack at 1.2.dancedroid

We need source for battery temp unless Motorola decides to be nice to us. Rumor on source is the end of the month, but I am guessing in July to be safe. It is possible the kernel is compiled from 2.1 source code which allows for modifying the defaults. I could see this being possible because *nix is very flexible about how it works.

 

[Skull One]

If you have your Advanced settings at 30000, 93 (or lower), 0, 0 then it is possible to see that condition.

My advanced settings that came with the Chevy 1.2 ULV kernel are 32000,50,0,0

Oh you will ramp up and down really fast with those numbers for sure.

 

[Skull One]

That is crazy....What are you doing that perhaps contributes to that score? The Theme? Wow!

Actually I would theorize it is the "Perfect Scenario".

IE:
No tasks running in background made a request for CPU time.
There were no deferred memory writes pending.
The CPU was at max freq the entire time.

It might be possible to reproduce with a very stripped down ROM. I have a 2.1 setup that way. If I get bored this weekend, I will setup a 2.2 ROM the same way and run tests.

 

[Taegost]

Since I updated to 2.2, Systempanel doesn't show the clock speed anymore, even with the paid version

My Droid Does Tapatalk...

And that is the clue I was looking for. That means SetCPU isn't working. Because SetCPU fixes that issue believe it or not

So uninstall SetCPU. Reboot. Install SetCPU. Menu. Device selection. Autodetect. Change min max sliders. Check System Panel.

I noticed yesterday that it is working again, which is after an update to both SystemPanel and SetCPU... I just saw your response now or I would have tried it earlier
Even though I go into SystemPanel several times a day, I don't usually pay attention to the clock speed, I'm one of those "set it and forget it" kinda guys
The only thing I really pay attention to is memory usage and temperature in there, once I've tested the kernel initially and it's running fine.
Keep up the good work, I'm really glad you've got this thread going, I've learned a lot. I actually have this thread set to auto-open in Chrome when I'm at work