Database Users

Cynanogen mod Clock cpu?

ok i was under the impression that cynanogen mod autmatically over clocks the cpu to 528mhz. But someone told me it doesn't. Does it? and if i use setcpu will affect the stability?

Your not really Oc'ing because the CPU was made to run at a max of 528 and 384 is the stock(Offical OTAs) to save battery life. It will only go that high when needed, you dont drive at a 100MPH just to do it, you do that when no one else is around. It will reach that high under heavy load not if your dialing on just swiping on home.

ace is right from what ive been told and read. the cpu is underclocked so its not hitting its full potential.
also no cyanogen does not do this automatically. this is best done by the user anyway as they can get a prefered setup then on their phone as this does consume battery life.

Ok i downloaded setcpu but i dont see a big difference i selected 528 as max and the max stock as minumum and put set on boot and i rebooted. I dont know why im typing in upper case, im on my g1

to be honest i never really noticed too much of a difference myself.

I've been using SetCPU now for about 48 hours and am very impressed with it. See my sig for current system setup. As far as SetCPU settings: on-demand throttling, 528 MHz max, 245 Mhz min, no profile settings, scaling up setting 75%, and both "set on boot" options checked. The SetCPU settings definitely make the phone snappier compared to the normal CyanogenMod settings.

is there a difference between on demand governor or performance? whitch one is faster?

nahanee20 said:
is there a difference between on demand governor or performance? whitch one is faster?
Click to expand...
Click to collapse
http://www.pokedev.com/setcpu
On demand will scale CPU speed between the minimum and maximum settings, and performance runs it at maximum constantly.

Current CM rom fluctuates from 256Mhz/min to 528Mhz/max on demand. I suggest you leave it alone since it's an exceptional setup. Unless you prefer a constant max and have your battery die in 6 hours give or take.

BoomBoomPOW said:
Current CM rom fluctuates from 256Mhz/min to 528Mhz/max on demand. I suggest you leave it alone since it's an exceptional setup. Unless you prefer a constant max and have your battery die in 6 hours give or take.
Click to expand...
Click to collapse
It's not that exceptional, nor does modifying that setup drain your battery much faster. My G1 is much faster after using SetCPU to change the settings. My battery drain in standby is unchanged (because I'm using the same minimum setting as CM), and it is significantly faster under heavy usage. There's really no downside to it, so to assume that the default CM setup is optimal is a little short sighted in my opinion. Don't be offended...just my 2 cents.

TeeJay3800 said:
It's not that exceptional, nor does modifying that setup drain your battery much faster. My G1 is much faster after using SetCPU to change the settings. My battery drain in standby is unchanged (because I'm using the same minimum setting as CM), and it is significantly faster under heavy usage. There's really no downside to it, so to assume that the default CM setup is optimal is a little short sighted in my opinion. Don't be offended...just my 2 cents.
Click to expand...
Click to collapse
What you just stated is the exact performance the coded frequency default on CM does. On demand is the key word. When you go standby/sleep, frequencies goes minimum. When under heavy usage, frequencies goes maximum. So how is that short sighted? When everything you stated that SetCpu does better, is the exact thing that the default CM setup does. Plus having SetCpu process run constantly in background is a main factor that eats up RAM. While the default CM setup does not. The only benefit I see with SetCpu are the profiles.

The main thing that SetCPU does that CM does not is adjust the threshold at which the CPU begins to scale up. I have mine set to 50% which is far lower than CM's setting, and I believe that is the main reason my phone is so much faster.
Also, SetCPU does not stay running in the background. A script runs at boot to apply your settings, but the app doesn't actually run unless you start it yourself.

CM's default up threshold is at 40, so I have no clue where you got the idea that is far higher. Also, it does not affect speed. It's the percent cpu usage before going up a speed step. So actually the higher the threshold, the longer it stays on current/lower speed.
SetCpu does stay running in the background. Open your app drawer, open Dev Tools, Running Processes, and you will see SetCpu (com.mhuang.overclocking) running.

Well pal, all I can tell you is my phone is a LOT faster after using SetCPU to adjust settings. I don't mean only marginally, I mean significantly. In fact I can't overstate how much more snappy the phone is. If you can explain why that might be, I'd love to hear it.

Well pal, all I can tell you is my phone is a LOT faster after using SetCPU to adjust settings. I don't mean only marginally, I mean significantly. In fact I can't overstate how much more snappy the phone is. If you can explain why that might be, I'd love to hear it.
EDIT: That process is not running.

It boils down to user experience. If it feels cold, then it must be cold. Am I right? But these are all perceptions manufactured by our brain. That is why we have crazy people. I'm not calling you crazy, but crazy people see things that are not there. Perception is the word of the day.

I guess we'll have to agree to disagree. I could measure the before and after difference with a stopwatch, meaning it genuinely is faster. In my opinion, it is entirely possible that SetCPU allows for faster performance than CM does by default. Unfortunately, that is impossible for me to prove via an internet forum. Anyway, it was fun debating with you.

BoomBoomPOW said:
What you just stated is the exact performance the coded frequency default on CM does. On demand is the key word. When you go standby/sleep, frequencies goes minimum. When under heavy usage, frequencies goes maximum. So how is that short sighted? When everything you stated that SetCpu does better, is the exact thing that the default CM setup does. Plus having SetCpu process run constantly in background is a main factor that eats up RAM. While the default CM setup does not. The only benefit I see with SetCpu are the profiles.
Click to expand...
Click to collapse
I've been rooted and running SetCPU for a while but just recently switched to CM. I had CM running with SetCPU until today when I decided to remove SetCPU to see how CM does on it's own. My phone seems exactly the same from what I can tell... if not a tad faster. BUT I really liked the ability to have SetCPU clock the CPU waaaay down when the battery gets below a certain %. I had it set to run at 245max/128min when the battery dropped below 30%... yes it was sluggish but it would stretch that 30% for many hours if I needed it to.
Does CM do anything like this or have a provision somewhere for setting cpu speed based on battery level? I don't like having stuff installed if I don't need to, but missing this feature may have me reinstalling SetCPU.

Processor Throttling

Does anyone know if the desire hd has any sort of processor throttling enabled on it? Am running Linpack benchmarks on my phone and am getting some very weird results.
My linpack benchmark changes between ~35Mflops and ~62Mflops seemingly at random, this is a fresh install of cyanogen 7.0 with LorDMod V4.0 kernel. Also have the google apps installed (are any of these known to cause high cpu-usage?) I have checked the background CPU usage using SystemPanel and there appears to be no other processes using the CPU.
Phone is running at 1.996ghz at 1300mv, have run mutiple stress tests over several hours and its rock solid in terms of stability, the max temperature i've seen is 37 degrees which also seems perfectly fine (I've heard from other threads that the processor temperature is normally around 5 degrees higher than the battery, so this doesn't seem to be an issue)
Have also tried increasing the voltage at 1.996ghz all the way up to 1475mv (incase of strange stability issues) however, as expected this has no impact on the linpack readings.
Basically i'm at a complete loss to explain this myself and therefore am wondering if any of you guys can come up with any other ideas?
Thanks.

What CPU govenor are you running the benchmarks with? You should use Performance, as it will lock your CPU at the maximum allowed frequency

I hope your not running your processor at that speed all day
Sent from my Desire HD using XDA App

Wait wait wait...You are running 2GHz @1300mV?What the F*CK?Mine needs 1450mV to run @1.8GHz,maximum is a really unstable 1.9GHz with 1500mV,and this only for some seconds!
Anyway...You could try killing some apps.It's normal that tests aren't consistent however.

Does cpu frequency affects battery life?

The question is simple, the higer the freq. the more battery consumption? i am asking because i cannot see any difference from 1.4GHZ to 1.0GHZ, the battery consumption is the same under oxygen and francos kernels. i would be grateful if the experts would give us some advise or their opionion. I know it is subjective but i would like a second opinion.
Thanks alot guys

If you look with any cpu spy app, you cab see on what clock the processor is used. I mainly have it the lowest and sometimes higher. When you change the max, it should still automatically choose what clock is used, so battery should last as much as before, if not used in high clock.
Sent from my Huawei u8800 using XDA App

Invicta said:
The question is simple, the higer the freq. the more battery consumption? i am asking because i cannot see any difference from 1.4GHZ to 1.0GHZ, the battery consumption is the same under oxygen and francos kernels. i would be grateful if the experts would give us some advise or their opionion. I know it is subjective but i would like a second opinion.
Thanks alot guys
Click to expand...
Click to collapse
Probably not much difference, when you overclock, think the cpu voltage remains the same as it is on 800mhz... And the highest cpu freq is rarely even at use...

Invicta said:
The question is simple, the higer the freq. the more battery consumption? i am asking because i cannot see any difference from 1.4GHZ to 1.0GHZ, the battery consumption is the same under oxygen and francos kernels. i would be grateful if the experts would give us some advise or their opionion. I know it is subjective but i would like a second opinion.
Thanks alot guys
Click to expand...
Click to collapse
Well, thanks to most devoted users of U8800, we have somewhat better speed+battery life than stock also. To answer your question, yes depending on your activity the frequency have some impact, but overall shouldn't be huge in change, for example from .800 to 1.0GHz will not affect so much in daily use. However from .800 to 1.5GHz would make a somewhat huge gap difference. This doesn't mean it will drain faster if you do same activity as with .800 to 1.0GHz, for example check the watch, answer sms or few "entertainment" breaks. Only when using the phone over a longer period of time that's when you will notice the change of battery life with different frequency. Hope it clears up most hums and huhs for you. I am pretty sure some expert within this field will give a better explanation than me.
Bye~

higher freqs uses more energy, but lower uses less energy but do things slower (so energy consumption is longer). ALSO imo - if you set cpu to 1Ghz the lowest value so it always is 1ghz - it will not consume the same amount of energy if it's in idle mode - it's like your laptop - if cpu is working only in 4-7% of it's power - then the power consumption is lower no matter what freq - how do we know that? - because of heat - the more heat you get - the more energy was used. and when cpu is idle - it will not be hot.
So the answer is - if it saves then in VERY minimal amounts. But even so - i use min freq - 360mhz. it's good for me i do not get any lag so i use it.

I use the "Root System Tool Free", option CPU and I see the graphics of all clocks.
For ex. now at 245 mhz ->46%, at 368 ->10%, at 768 mhz ->18% .... and at 1612 mhz -> 1,8%, at 1804 mhz ->4,9%. Not very mutch use at 1804.
Oxygen-test-140911 + Franco.Kernel1709#1. Clock at 1804 Mhz by Menu-settings-cpu ... and smartassV2 (no profils).
The battery, I charge it all 24 hours. But I like my work... and testing things. When then will dead...I see...

ValenteL said:
I use the "Root System Tool Free", option CPU and I see the graphics of all clocks.
For ex. now at 245 mhz ->46%, at 368 ->10%, at 768 mhz ->18% .... and at 1612 mhz -> 1,8%, at 1804 mhz ->4,9%. Not very mutch use at 1804.
Oxygen-test-140911 + Franco.Kernel1709#1. Clock at 1804 Mhz by Menu-settings-cpu ... and smartassV2 (no profils).
The battery, I charge it all 24 hours. But I like my work... and testing things. When then will dead...I see...
Click to expand...
Click to collapse
cpu spy is more pretty, anyway all those apps just reads text file of cpu stat and that's it

Tommixoft said:
cpu spy is more pretty, anyway all those apps just reads text file of cpu stat and that's it
Click to expand...
Click to collapse
Thanks
But I like more the Root System Tool, because has also a Linux Console. I use it when I want make some cmd's Linux in #. I don't like the Terminal Emulator.

Well, there is a "catch" somewhere in there. The frequency does indeed affects the power consumption of the CPU and greatly at that too! But the thing is, your CPU is not the worst enemy of your battery life. Even though CPU consumes more power in higher frequencies, it still can not compete with what your screen LEDs or your GSM module or your GPS chip consumes leisurely. So, if you're looking at the overall picture -meaning if you're wondering if it will affect how long you'll be able to use your battery in your phone- the answer is, "yes but not so much". Especially if you're switching the CPU frequency based on the demand (like using smartass or on-demand governors)
Here are the thing that sucks your batteries life juice like a vampire :
Your Screen (especially background LEDs)
GSM module (talking, using GPRS/Edge/3G network communication)
GPS chip
Wireless module (this also includes Bluetooth, even though it does not consume as much as Wireless network access but everything is relative -think about playing music through A2DP headphones compared to having your wireless network active but not using it much-)
(oh yes, I love to use lots of parenthesis -and even this hyphenation thingy- )
Correct me if I'm wrong about anything by the way ..
Regards ..

I did some experiments with a msm8250 a while back and there's a graph here:
http://forum.xda-developers.com/showpost.php?p=14324649&postcount=3786
msm7x30 should be fairly similar though the graph is probably shallower since it's a smaller process size.
The CPU uses no power when it's not in use, even with the display on, the CPU is powered down completely when idle (power collapse).

How high can I overclock

I can set it as high as 1646. IV looked around and it seems that people use 1504. Is it unsafe to go any higher?
Thanks
Sent from my A501 using XDA App

1400 is safest I run Alexandra iii

if you go up to 1.6 GHZ, you might get SHUTDOWNS...
if you don't run any games, or apps, sure it will work. But not smart to overload it.
If on Custm ROM, Read DEV Notes, usually they'll say (or mention about Kernel changing)
as a rule I keep it on 1.5 Ghz (when 1.6 was max) (have tested on about 8-10 diff roms) (never have had any shutdowns yet)
*** also maybe use a meter app to check TEMPS (like battery TEMP)
Cool Tool - shows battery temp, RAM, Proc Freq, + more in little box on screen all the time (adjust settings)
https://market.android.com/details?id=ds.cpuoverlay
"setCPU for Root users" - underclock to lowest when off, set lower cpu freq if battery gets warmed to ur custom Degrees)
http://www.setcpu.com/
***Some custom ROM's have thier own Freq CONTROLER app (that could clash with prog or have 2 progs do the same thing)

Like humans NO TWO CPU's are equal
All of the above it true with one exception..NOT every cpu is created equal Not all ram chips and so on also live up to this..
Start over clocking your cpu slowly. as you push clocks higher of course lower voltage. This keeps heat down .
Two processors even made on the same casting can be totally different . Where one will take more heat with less errors and corruption and the die next to it will almost crash running its designed clock speeds . Being that extreme is very rare with a few exceptions. most are close as to a common ability. within a few 100 mhz.
So the answer is there is NO TRUE Answer. its trial and error but on the side of caution and testing clock speeds and heat is not a 30 second yes it runs. Do it over a week or so. I know with my dragon cup in cell phone its at its end of life from being over clocked for a few years. some last longer some die quicker.. Its kinda like drinking on your brain the more you drink the more cells you kill.. The hotter your cpu gets the more transistors fail the slower it becomes the more errors you have .
Relax .. go slow.do not expect to get what everyone else is claiming. and you will be fine..
Sorry again for long winded post..

dr mcknight said:
I can set it as high as 1646. IV looked around and it seems that people use 1504. Is it unsafe to go any higher?
Thanks
Sent from my A501 using XDA App
Click to expand...
Click to collapse
Any is unsafe. Higher speed equals heat and heat kills semiconductors. Might work for a while but why risk it

My daughters has been running at 1.6GHz for 2.5 months without any crashing or blowing up.

I say at 1.6, you're starting to enter the "red zone", sort of asking for problems. Why go up that high? I mean, 1.5 shows enough performance improvement over the 1GHz...

CPU never goes above 1.440 ghz

So I usually use CPUSpy to monitor my CPU usage. This comes in handy once the device is rooted and I can see how custom kernels and settings affect battery life and cpu cycles. My LG G4 is the tmobile variant and obviously not currently rooted. I notice through CPUSpy that my cpu speed literally never exceeds 1440mhz.
I don't have any problems with that per say, everything on the device still runs buttery smooth without anything more than the occasional hiccup or lag. I'm curious if anyone else has monitored their CPU speeds and noticed the same thing? I just find it a little interesting.

CPU spy can't even see the A57 cores so there's no way it can see what speed it's running at.

4 cores are limited to 1.44 the rest are 1.8

I have not used CPUSpy. But CPU-Z will show you the speed of each of the 6 cores. As mentioned, the last 2 are the only ones I've seen reach 1.8GHz, the first 4 seem to top out at 1.4 GHz.

Ok.. Using cpu-z..

That's how mine looks "at rest". When it's sitting quietly, saving the battery. Crank up some apps, and you should see those clock speeds rise.
But, trying to improve my battery life, and keep the temps down, I've been hoping to see those numbers stay low, not actually show how high they can go

I agree.. As ive stated, the device runs great i just found it odd. It even calls it a 1.44ghz cpu in the cpu profile and mostly no matter how hard i push the device i cant break that speed

Right as CPU-Z opens, the clock speeds spiked briefly. I was able to get a screenshot quickly.
Do yours also jump up for a second or two right as the app opens?

This has been discussed already. As the previous post shows, they do get to 1.8Ghz when required.