OverClocking 101

[dolfanpete]

ok. when i open up set cpu, i get to the main tab....on the very top it says 1250 MHz

but the two sliders that are max:
and min:

the max: maxes out at 600 MHz.....

shouldn't it max out at 1250?

and yes i did install a new kernel, slayer2.6.32.9 slayher-laptop #30..........

 

[jeffe65]

One thing that comes to mind that I forgot: In SetCpu go to menu then device selection and choose auto-detect.

 

[dolfanpete]

Bingo!!!! Thank you sir!!

Sent from my Droid using DroidForums App

 

[jeffe65]

You're welcome! That setting has passed me by more than once when I needed it...

 

[jerroedr]

so what are the recommended advanced settings these days? its been a while since i dropped in tho this thread...

 

[nuwizard]

Last i read;

Conservative
186250,85,45,0,10

Ondemand
30000,50,0,0

Sent from my Droid

 

[Aram58]

Bad if I have upload threshold at 93?

Sent from my stunning rooted droid using tapatalk.

 

[moset]

I recently had to replace my D1 because of the screen doing phantom touches. I had to get a second CLN because the notification bar would not slide open. This one seems to be working well with the stock kernel. I'm running Steel Droid 2.2 . I have tried to run other kernels with this and other ROMs and no matter what combination I try my CPU temp quickly runs above 50° when I use navigator or stream videos etc. Anything that pushes the CPU causes it to heat up. I've even run standard voltage 800mhz. The stock kernel does not give me XPU temp in SETCPU. I see CPU temp with System Panel but using a different sensor than other non-stock kernels. So I have 2 questions. Is my CPU running hot with the stock kernel also and I just can't see it? How can I tell? I'm not running any task killer. System Panel monitor is disabled. I have uninstalled setCPU. My performance is good with this set up. It just bugs me that I can only run stock kernel.

Sent from my Droid using DroidForums App

 

[jerroedr]

Last i read;

Conservative
186250,85,45,0,10

Ondemand
30000,50,0,0

Sent from my Droid

thanks

Bad if I have upload threshold at 93?

Sent from my stunning rooted droid using tapatalk.

i dont know if it does anything...

 

[wingdo]

Bad if I have upload threshold at 93?

Sent from my stunning rooted droid using tapatalk.

i dont know if it does anything...

Up threshold is the % of CPU utilization which must take place for the kernel to clock up the the next speed slot. 93 is waaaaaay too high, try something around 50.

 

[hrdnhvy]

Actually 93 is not to high? What it comes down to is if u want slightly better battery life or a snappier phone, the lower the % = snappier phone, higher % possibly slightly better battery life, for me I tend to lead toward battery life, so I usually keep my up threshold around 90% & honestly I can not tell much a diff in snappyness vs running at 50% so I usually just keep it at arpund 90 & hope Im getter longer battery life vs if I were running at 50.

Bad if I have upload threshold at 93?

Sent from my stunning rooted droid using tapatalk.

i dont know if it does anything...

Up threshold is the % of CPU utilization which must take place for the kernel to clock up the the next speed slot. 93 is waaaaaay too high, try something around 50.

 

[Skull One]

Actually 93 is not to high? What it comes down to is if u want slightly better battery life or a snappier phone, the lower the % = snappier phone, higher % possibly slightly better battery life, for me I tend to lead toward battery life, so I usually keep my up threshold around 90% & honestly I can not tell much a diff in snappyness vs running at 50% so I usually just keep it at arpund 90 & hope Im getter longer battery life vs if I were running at 50.

i dont know if it does anything...

Up threshold is the % of CPU utilization which must take place for the kernel to clock up the the next speed slot. 93 is waaaaaay too high, try something around 50.

Your summary is spot on and well said.

 

[wingdo]

Actually 93 is not to high? What it comes down to is if u want slightly better battery life or a snappier phone, the lower the % = snappier phone, higher % possibly slightly better battery life, for me I tend to lead toward battery life, so I usually keep my up threshold around 90% & honestly I can not tell much a diff in snappyness vs running at 50% so I usually just keep it at arpund 90 & hope Im getter longer battery life vs if I were running at 50.

Up threshold is the % of CPU utilization which must take place for the kernel to clock up the the next speed slot. 93 is waaaaaay too high, try something around 50.

Your summary is spot on and well said.

It's true his summary is indeed spot on. I just assumed that someone overclocking wanted a snappier phone. It's always a fight between performance of the system or the battery. In testing I can certainly see a difference between 93% and 50% with regards to initial lag.

 

[jhom]

I recently changed P3 kernels from 125-800 to 125-1000 low voltage. I've noticed that "Time in State" notification in SetCPU no longer shows time in state for each of the slots. It is there something I'm missing to get the data?

 

[hrdnhvy]

Ok...this actually i have brought up a few times in the past but no one else seemed to care or notice.

Chances are if u dl or use the market apps "system panel" or "android system info" u will notice the same findings = clock speeds nor clock speed history will be shown.

My observations have told me (im not sure if im right or not, just what I have noticed) its a kernel related thing or possibly a phone kernel related thing, why, because i have noticed it fluctuates from kernel to kernel to phone, not kernel to app issue.

Now all of these kernels are good so im not knocking on any but: 90% of p3 & slayhers do not show the above mention info & if they do it does not maintain it, the info may show for a brief time but once ur ph sleeps or just after time it will no longer show. Jdlfg's kernel are hit or miss, some of them show the info 100% of the time while other of his kernels do not. So far Chevys 11.5 release kernels are the only kernels (on my phone) that show all of the above info all of the time.

Just my .02

I recently changed P3 kernels from 125-800 to 125-1000 low voltage. I've noticed that "Time in State" notification in SetCPU no longer shows time in state for each of the slots. It is there something I'm missing to get the data?