Database Users

Overclock widget = placebo

The system already dynamically clocks the CPU
Don't believe? Install OSMonitor and look at the "Misc" tab
Notice the "ondemand" governor scaling the processor from 245000 - 998400 hZ
Leads me to believe CPU governing is already in the kernel

You might be right.
The only difference I can think of is with the widget people are using (I have not tried it) the under clocking happens the instant the screen turns off. Where as we have no idea when/how the standard under clocking happens, if it does at all.
I am waiting it out. If the under clocking widget is true, it will eventually become common knowledge on these forums. For now I have not seen anything that has convinced me and I fear if i tried it I would suffer from the placebo effect. The last thing I want is another app running in the background for no reason.

strung said:
The system already dynamically clocks the CPU
Don't believe? Install OSMonitor and look at the "Misc" tab
Notice the "ondemand" governor scaling the processor from 245000 - 998400 hZ
Leads me to believe CPU governing is already in the kernel
Click to expand...
Click to collapse
I've noticed this as well. System Panel measures my CPU speed at around 245 Mhz when I'm just swiping through the home screen, but cranks up to 1 Ghz when the CPU usage approaches 100%.

Mecha2142 said:
I've noticed this as well. System Panel measures my CPU speed at around 245 Mhz when I'm just swiping through the home screen, but cranks up to 1 Ghz when the CPU usage approaches 100%.
Click to expand...
Click to collapse
Really? I wonder if that could explain some of the choppiness while scrolling around and general phone use.

I can confirm this with SetCPU's real time monitor. drops to 245 when not in use, and 1ghz when scrolling around

I think oc widget is better. I can choose a 5sec interval in which it checks to see if there are processes that need more CPU power.
I wonder what the intervals are in the stock unrooted OS
Oc widget def works for me, and I'm not just letting my phone sit as a paperweight, I'm using moderate to heavy everyday and the results for me are better.

Also, does the unrooted OS allow other frequencies besides 245 and 1ghz?
Oc widget runs mine in the 300s 500s 700s and 800s when needed
1ghz is not needed all he time when the screen is on. And I don't notice extra lag anywhere

And with 5sec intervals, the screen does not have be off to see 245. Just let it idle for 5 secs

I don't even think the OCwidget works. I mean it tries to set new values, and it thinks they succeed, but I think the new values are ignored by the kernel. For example, I tried to set min and max to 250 mHz and it still shot up to 1 GHz.
My apologies for being a debbie downer.

Here you go... can someone produce something similar with the stock OS unrooted
it does help.. even tho you see my battery between 81 and 79 lol... for me, the top 25% of battery life (from 100-75) goes by fast no matter what, but then it really holds good life afterwards.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

strung said:
I don't even think the OCwidget works. I mean it tries to set new values, and it thinks they succeed, but I think the new values are ignored by the kernel. For example, I tried to set min and max to 250 mHz and it still shot up to 1 GHz.
My apologies for being a debbie downer.
Click to expand...
Click to collapse
The problem is we are all in the "i think" stage, so its pure speculation. Maybe the oc widget developer could help us out here.
I Do think the op should put a ? In the thread title to get more discussion on this, cuz there are some brilliant minds here at xda
Edit: I emailed the dev w this thread asking for his insite, hopefully he jumps in

Faith is a powerful force
if overclock widget really controlled the clock
1) Linpack scores would reflect that
2) mHz readings would reflect that
But... they don't

strung said:
The system already dynamically clocks the CPU
Don't believe? Install OSMonitor and look at the "Misc" tab
Notice the "ondemand" governor scaling the processor from 245000 - 998400 hZ
Leads me to believe CPU governing is already in the kernel
Click to expand...
Click to collapse
Sounds like you have a problem if your Evo is only running from 245 kHz to 998 kHz.

Minjin said:
Sounds like you have a problem if your Evo is only running from 245 kHz to 998 kHz.
Click to expand...
Click to collapse
How do you figure a problem? 998mhz is max.. u just poking fun at "hz"? lol

So with OSMonitor, do you see any current values besides 245 and 998?
here's mine with OC Widget and some of my defined frequencies... If it truly fluctuates to differents clocks like mine on the stock OS with NO root (please show screenies), i will resign as the OC Widget evo underclock believer until an overclock kernel is released and camera works .

I'm on stock OS with root
It indeed goes to all the freq's
sorry too lazy to screenshot
EDIT: oh and I uninstalled OC widget!

strung said:
I'm on stock OS with root
It indeed goes to all the freq's
sorry too lazy to screenshot
Click to expand...
Click to collapse
and no oc widget? thought i was headed somewhere lol

itsallsubliminal said:
How do you figure a problem? 998mhz is max.. u just poking fun at "hz"? lol
Click to expand...
Click to collapse
That would be 998 millihertz which would be even slower.
I may seem like I'm being pedantic and I wouldn't even mention it if this forum was for arguing about American Idol winners but this forum is by definition populated by geeks and otherwise smart individuals.
Regardless of what the app displays, the phone is operating at 245MHz to 998MHz. The capitalization of the H is official but I'm not that anal. Capitalizing the M means mega (1000000). Lower case means milli (1/1000).

Minjin said:
That would be 998 millihertz which would be even slower.
I may seem like I'm being pedantic and I wouldn't even mention it if this forum was for arguing about American Idol winners but this forum is by definition populated by geeks and otherwise smart individuals.
Regardless of what the app displays, the phone is operating at 245MHz to 998MHz. The capitalization of the H is official but I'm not that anal. Capitalizing the M means mega (1000000). Lower case means milli (1/1000).
Click to expand...
Click to collapse
ROFL!

email from OC Widget dev
here is what the dev (Billy Cui) wrote back to me about OC Widget and the Evo...
"Yes, most system support dynamically clocking, but you will still
benefit on using OCW, especially for save battery. And some system do
not running cpu full speed, and with OCW, you can force it run faster."
Makes sense, like i said about the update interval being adjusted with OCWidget.
comments?

G2 benchmark... numbers sucked!

Just flashed enoms g2 rom and I cleared up what I can, tried making it efficient.I ran some benchmark tests on quadrant standard and was kinda disappointed in the numbers. My bests score was low 1100 after that it was 850,900, 835... very basic stuff any suggestions???
Sent from my T-Mobile G2 using XDA App

If you ran the benchmark on battery power, try plugging the phone in. Sometimes the CPU will underclock itself to save power. If that doesn't work, download SetCPU (google it) and make sure that the max speed is set above 800 MHz.

On the stock G2 ROM I was getting 1600-1800... maybe it's the ROM your using

omarsalmin said:
On the stock G2 ROM I was getting 1600-1800... maybe it's the ROM your using
Click to expand...
Click to collapse
Yeah this is the typical range for a stock G2.
Those scores in the OP are so low, its almost like hes underclocking or something. Or possibly a running application using a ton of resources?

i got 2064. but i was running virtuous.

im running enom's rom and i had it underclocked at 768 and i was still able to get 1609

Stargazer418 said:
If you ran the benchmark on battery power, try plugging the phone in. Sometimes the CPU will underclock itself to save power. If that doesn't work, download SetCPU (google it) and make sure that the max speed is set above 800 MHz.
Click to expand...
Click to collapse
Umm... No... The CPU doesn't underclock to save power...

gravis86 said:
Umm... No... The CPU doesn't underclock to save power...
Click to expand...
Click to collapse
Perhaps the kernel has an undervolting profile built in and it's triggered by a < battery percentage?
Sent from my HTC Vision using XDA App

What should I have my phone clocked at with enoms rom?? I dnt have much running at all I dnt understand why its so slow, I was gunna flash the latest kernal and try that... clock settings please anyone
Edit: jus tweaked my clock on spareparts. I switched cpu governor from ondemand to performance and the clock setting. I put underclock at the lowest and overclock at the max highest... benchmark test put up a 2200... I feel as if this will drain battery like crazy only time will tell... what do u think, should I drop the overclock? Is it safe at that high number???
Sent from my T-Mobile G2 using XDA App

If I run with Flippy's kernel, CM 6.1.1 Stable and OC my phone to 1.8 GHz, I can get a Quadrant score of 3037 (screenshot below). With it OC'd to 1.4 GHz (my normal OC setting) I can get around 2500.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If I'm averging 2500 I'm fine wit that my current settings are Enoms Rom
Using enoms cpu controls
Cpu governor: performance
Max frequency: 1,516,800
Min frequency 245,760
I dropped 3 percent in battery writing this message.... my main concern is battery and overworking the cpu.... I'm thinking about downloading set cpu and clocking the performance settings then set it for power save after a certain drop point........ does this sound logical?
Sent from my T-Mobile G2 using XDA App

When you set your cpu to performance it means your cpu will stay at max all the time and it never goes down which is why you are getting bad battery life.
There is no need for that.
Yes you can do that with setcpu
Sent from my HTC Vision using XDA App

Maybe you tested your Samsung Galaxy s by mistake?..lol..just joking.

I score around 2500 on quadrant:
OC'd to 1.4 (normally run 1.2)
SetCpu On Demand
CyanogenMod 6.1

fablife said:
Maybe you tested your Samsung Galaxy s by mistake?..lol..just joking.
Click to expand...
Click to collapse
Hey! Not funny! My vibrant gets 2035 in the quadrant! But I'm going to get myself a g2 because I miss the hardware keyboard

Got me 2813 with Virtous 0.9 <---- (sense rom btw) and eVil's latest Glacier based kernel @ 1.5ghz... life is good
Sent from my HTC Vision using XDA App

[Q] Low Quadrant Scores

I know that this tool isn't a good indicator of performance... but when I see other people with the EVO getting 1200+ and I am at 800-900, I am starting to wonder if there is a setting wrong. My phone occasionally feels sluggish. Any idea's what the cause could be? using an AOSP rom with Tiamat Kernel
- Just realized I wasn't in Q&A forums Sorry! - please delete if needed

Stuke00 said:
I know that this tool isn't a good indicator of performance... but when I see other people with the EVO getting 1200+ and I am at 800-900, I am starting to wonder if there is a setting wrong. My phone occasionally feels sluggish. Any idea's what the cause could be? using an AOSP rom with Tiamat Kernel
Click to expand...
Click to collapse
Good question!
Ive always wondered why some score so low on good combos.
I'm on CM nightly rc3 build 18 with savgzen 1.0.0 cfs-havs and scoring very well
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

new quad you will get low scores
imho quad and all the other benchmark test mean nothing

CheesyNutz said:
new quad you will get low scores
imho quad and all the other benchmark test mean nothing
Click to expand...
Click to collapse
I agree when comparing to other phones... but 2 phones of the same model should get similar scores right?

Stuke00 said:
I agree when comparing to other phones... but 2 phones of the same model should get similar scores right?
Click to expand...
Click to collapse
Have you ran it off of a fresh reboot?
I find my best scores were when I rebooted let it sit for 3-5 min after reboot, and then fire it up.

Mark_in_Tulsa said:
Have you ran it off of a fresh reboot?
I find my best scores were when I rebooted let it sit for 3-5 min after reboot, and then fire it up.
Click to expand...
Click to collapse
Trying it again after the phones been on a few minutes.
I used to use SETCPU and I thought maybe that screwed things up

If you want to increase scores why don't you put your Max frequency at 1190 and min at 1190 with setcpu. High scores are a thing of the past.
~ d3rk

dirkyd3rk said:
If you want to increase scores why don't you put your Max frequency at 1190 and min at 1190 with setcpu. High scores are a thing of the past.
~ d3rk
Click to expand...
Click to collapse
That is with my CPU at 1190. I am not trying to get a high score, but a score my phone should be able to get, you know? I see someone with an EVO get 1500 and then I am thinking something is wrong with my phone... I have the same phone..

Stuke00 said:
That is with my CPU at 1190. I am not trying to get a high score, but a score my phone should be able to get, you know? I see someone with an EVO get 1500 and then I am thinking something is wrong with my phone... I have the same phone..
Click to expand...
Click to collapse
Putting stock in scores is foolish though. 936 does seem a Tad bit low for sure. My set up is cm7 #36, tiamat kernel 3.3.5, JIT on, setcpu 1113 Max, 422 min smartass governor. I just ran a linpack and got 37mflops and 1200 in benchmark. This is the same set up I usually run on any rom or kernel. I try not to clock so high because it just drains battery. My evo actually can perform flawlessly clocked at even 998mhz. The only thing I notice different is that scores change and I don't really take a performance hit. Underclocking is the new overclocking lol. My last suggestion would be to play around with different kernels to achieve what you desire. Try savage zen!
Edit: just ran these 2 test just for you right now. Same results and I'm using same kernel you are.
~ d3rk

Run, it once, and then run it again right after w/out quitting. The if you run it multiple times (at least on my phone), all subsequent scores are on par with the second one which is usually 1-300 more than the first. Won't mean anything any different, but at least you might get some higher scores.
Also, you might need to try some different kernel combinations as well as different clock speeds. Mine usually does fine at 998 sometimes even at 921, but if I go too high it will start to slow things down. If you're not getting good results at 1190, try backing it off one setting at a time and see if you can get improved scores.
As far as comparing to other phones, even of the same make/model, you can't really do that. As long as they're in the same ball park, within a couple hundred, you're probably OK. Every phone reacts differently.
It also depends on the version of quadrant. You def can't compare diff phones running diff versions. I usually don't use it to compare to other phones, just diff setups on my phone. I know if I'm getting 1200 avg and then I all of the sudden flash a ROM and kernel and can't break 800 that something is probably wrong.
The most important thing is how the phone feels though. The fact that you say it feels sluggish leads me to believe you might need to try a diff kernel or see if something is eating up your CPU. Also, when you're over clocking, the min clock speed can effect your scores just as much as the max speed.

Ya give savage a go.
Kernel CPU setting:
Ondemand governor
Min 245
Max 998
My Device scores high runs smooth battery drain not a problem.

I just tested mine and got 1326. With these settings.. CM7 Nightly 36 with 2.6.37.6-Tiamat -v3.3.5 kernal.
Governor - Conservative
Min - 384
Max 1036

[Tips & Tricks][Poll] SetCPU Advanced Configs [NS & NS4G]- Share Yours!

Ok so it is very hard to find dedicated threads to this and I think the more of us trying this and reporting back to one thread, the more successful we will be in achieving great battery life or performance (i do it for battery life)
Here's what i have found to work well today, just some simple adjustments but my battery didn't drop a single percent for about 1.5 hours of very light use(still great tho).
MAIN TAB
Setting the Scaling to: Conservative
Max: 1000MHz
Min: 100MHz
PROFILES TAB (i only have one profile set):
Screen off - Max: 400 (don't go lower, your phone wont wakeup)- Min: 100- conservative - Priority 50
ADVANCED TAB(minimal changes, but i feel they have helped a bit):
Sampling Rate: 20000
Up Thresh: 80
Down Thresh: 25
Ignore Nice: 0
Freq Step: 20
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These may not be the best settings as we will play guess n check, but thats the reason of this thread, lets figure these things out.

You need root permission's for this, correct?

driftnut56 said:
You need root permission's for this, correct?
Click to expand...
Click to collapse
yessir you do

You should look into the smartass governor if you want to look for screen off frequencies. SetCPU only wastes CPU cycles for you to do this when a kernel can do it. Of course, I believe the end result is that you're still saving more battery, so at least it's a step forward

I'm overclocking 1.2 ghz. Switching between interactive and conservative.
Conservative has better battery life, but interactive is a bit snappier.
I'm new to the setcpu thing; gathered bits and pieces here and there to try and find the perfect settings.
Great thread though, hopefully people will post so we can take full advantage of this beast!
BTW, Tried to post screenshots, but I need more forum activity.

Had no success with conservative myself it allows the clock to step down to 100 eventhough I have the minimum at 200. The smart ass works like a charm no more lock screen lag
Sent from my Nexus S 4G using Tapatalk

teddybrukshut said:
I'm overclocking 1.2 ghz. Switching between interactive and conservative.
Conservative has better battery life, but interactive is a bit snappier.
I'm new to the setcpu thing; gathered bits and pieces here and there to try and find the perfect settings.
Great thread though, hopefully people will post so we can take full advantage of this beast!
BTW, Tried to post screenshots, but I need more forum activity.
Click to expand...
Click to collapse
Hi. I am new to over clocking with SetCPU. How did you get it to go over the 1000 max? I don't understand all of the other settings enough to feel brave enough to change them other than the first tab.
Thanks

ArizonaLoco said:
Hi. I am new to over clocking with SetCPU. How did you get it to go over the 1000 max? I don't understand all of the other settings enough to feel brave enough to change them other than the first tab.
Thanks
Click to expand...
Click to collapse
You have to flash a custom kernel (i recommend netarchy's kernel), then when you open setcpu, you can "autodetected recommended settings". You will then see the ability to overclock.

itsallsubliminal said:
Ok so it is very hard to find dedicated threads to this and I think the more of us trying this and reporting back to one thread, the more successful we will be in achieving great battery life or performance (i do it for battery life)
Here's what i have found to work well today, just some simple adjustments but my battery didn't drop a single percent for about 1.5 hours of very light use(still great tho).
MAIN TAB
Setting the Scaling to: Conservative
Max: 1000MHz
Min: 100MHz
PROFILES TAB (i only have one profile set):
Screen off - Max: 400 (don't go lower, your phone wont wakeup)- Min: 100- conservative - Priority 50
ADVANCED TAB(minimal changes, but i feel they have helped a bit):
Sampling Rate: 20000
Up Thresh: 80
Down Thresh: 25
Ignore Nice: 0
Freq Step: 20
These may not be the best settings as we will play guess n check, but thats the reason of this thread, lets figure these things out.
Click to expand...
Click to collapse
i used following profiles and UV settings...
still looking into it though...
http://caleb1783.tistory.com/196

I'm not using setcpu. It causes launcher pro to freak out for me. Installed CPU master and all is perfect. Running matr1x 7.5 @1.3 jiggawatts with the smartass v2 governer. Also I'm on gpa17 at the moment.
sent from my Touchwiz'd Nexus S 4g

[Q] OC/UV Beater2v1.7 makes my phone unstable with default values, help!

Ok I need to narrow down if I'm doing something wrong, or if my phone is actually faulty.
I have the latest Virtuous Affinity Rom, and installed OC/UV Beater, and I cannot seem to find a stable setting, and after using the VDD/OC reset .zip's that are supposed to reset everything to normal, I still have the issues.
I'm new to the whole OC the phone thing, can someone tell me if my voltages are far off what they should be for my phone.
ALSO could anyone supply me with their virgin (or stable working) files from their MT4G found in the sys/devices/system/cpu/cpu0/cpufreq/ folder so I can double check mine?
It seems below the 537600mhz is where I'm unstable. I stress tested 3 freq at a time and went down the list, that's where I would get the issues.
My OC settings in OC/UV Beater are:
Wake Gov: ondemand
Wake Min: 122000
Wake Max: 1459200
Sleep Gov: conservative
Sleep Min: 122000
Sleep Max: 460800
VDD:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I can think of 2 things.
1) Your wake min is WAY too low. That alone could be the issue.
2) Try bumping the voltage on higher frequencies up a notch.
Asking us if your voltages are ok is asking us a question we can't answer. Always start with default voltages. If that gives you stability VERY slowly adjust your voltage down a notch at a time, allowing time and testing between each setting. Never set on boot until you're SURE it's stable.
Sent from my HTC Glacier using xda app-developers app

estallings15 said:
I can think of 2 things.
1) Your wake min is WAY too low. That alone could be the issue.
2) Try bumping the voltage on higher frequencies up a notch.
Asking us if your voltages are ok is asking us a question we can't answer. Always start with default voltages. If that gives you stability VERY slowly adjust your voltage down a notch at a time, allowing time and testing between each setting. Never set on boot until you're SURE it's stable.
Sent from my HTC Glacier using xda app-developers app
Click to expand...
Click to collapse
Thanks for that. I understand what you are saying as I have been overclocking my PC for years, however, what I don't understand is why does OC/UV Beater2 seem to not be stable at all stock clocks and voltages when I stress test.
I have now gotten 1.5Ghz through 537600mhz stable, however, I cannot get 460mhz through 122mhz stable at stock volts, but it is stable with the voltage boost I have added. I'm curious to see if maybe my default voltage settings have gotten corrupted or misconfigured, that's why I am looking for someone to fill me in on the stock VDD and Freq for my cpu.
Also looking for advice as to what I have set there is normal voltage for the frequencies there?

Just looked at mine on cm 7.2. Your voltages look a little low across rhe board. Clear the data on oc/uv beater and reflash your kernel.
Sent from my HTC Glacier using xda app-developers app

Awesome, when you get a chance could you give me some screen shots of your voltages or tell me how much more yours are boosted?

Well, I'm on a different ROM now, but maybe this will help you. The voltages on this kernel are pretty low.
Sent from my HTC Glacier using xda app-developers app