I messed up mine and forgot how they were.
EDIT: as far as profiles and advanced setting
Sent from my Inspire 4G using XDA Premium App
If you want to make it easy you could use the smartass governor and just set your max overclock. If you wanted to make separate profiles you could use conservative for screen off and set it to like 245 mHz and use the ondemand governor for your max overclock speed during screen on conditions and set it to whatever speed you want to run at, such as 1228 mHz. You would need to set up multiple profiles and activate them.
Here is a link to a guide I just found.
http://androidforums.com/evo-4g-all-things-root/210253-setcpu-guide.html
Wolf_2 said:
If you want to make it easy you could use the smartass governor and just set your max overclock. If you wanted to make separate profiles you could use conservative for screen off and set it to like 245 mHz and use the ondemand governor for your max overclock speed and set it to whatever speed you want to run at, such as 1228 mHz. You would need to set up multiple profiles and activate them.
Here is a link to a guide I just found.
http://androidforums.com/evo-4g-all-things-root/210253-setcpu-guide.html
Click to expand...
Click to collapse
Thanks for the reply. And the kernel I'm on (gingerbeast) doesn't have smartass
Sent from my HTC Sensation Z710e using XDA Premium App
Related
Can anyone elaborate on the scaling settings in set CPU?
Some are obvious......powersave etc
Conservative
Userspace
Ondemand
Powersave
Interactive
Performance
I think its clear performance scales the CPU to highest speed. Powersave to lowest. But all the others seem to be the same. Is conservative a step up from powersave?
I can't find a thread that does a good job at breaking this down by the numbers.
Thanks to who ever points me in the right direction!!!!
Sent from my PC36100 using XDA App
Rtfm, jason.
Always wanted to say that
It's been a while since I checked but iirc the main difference between them is how quickly and aggressively the speed goes up and down. I read it on the help or about link in the app itself.
I did a simple Google search last night and found my ans.
Conservative vs ondemand is the answer for me.
Conservative scales up incramentaly as neded
On demand scales to max from min when needed
For best life with minimal performance hit, it seems conservative is the best scaling setting in set CPU.
Sent from my PC36100 using XDA App
edit: yes I know right after I hit the submit thread button I realized I spelled kernel wrong
I just flashed faux's 0.1.2 1.56 GHz NoHz kernel, and everything worked fine. My question is to do with utilizing the kernel for what it can do. I checked my cpu speeds via adb, and the max speed is indeed just stock. Now, I would love to utilize the 1.56 GHz capability of this kernel, but in the first post of his thread faux says not to use any OC apps and I also remember from reading through another thread (I think the Dual-Core support discussion thread) that he doesn't recommend the OC Daemon either. How are people OC'ing if you can't use OC apps or OC Daemon? I vaguely remember seeing a post/thread once that had to do with manually entering clock speeds, but I can't remember where it was. So my question for this part is how can I get the cpu up to speeds I want to like other people are doing (basically, is there a manual way or some other way I don't know about or is everyone just using OC apps/OC Daemon against faux's wishes)?
This part is to do with governors. I can find a wealth of information on what particular governors are designed to do. "This governor is designed to conserve battery when the screen is off" "this governor is designed for maximum performance" yada yada. What i can't find is how you choose which governor your phone uses. I used adb to check available governors and it gives me "ondemand performance". I assume this means that my phone/kernel is currently using that governor. Cool. But how do I switch to a different governor if I want to? It looks like SetCPU allows you to change governors, but is that the only way?
Thank you in advance for your help.
Shouldnt need oc app with his kernels mine is at 1.56 ever since i flashed it.
On demand is the only one that properly works with dual core processor. Even with an oc app you can only select on demand or performance and you wouldnt want to use that governor since it forces the cpu to work at max frequency at all times. To use oc daemon you need the virtous oc scaling files to select frequencies
Sent from my HTC Sensation 4G using XDA Premium App
hev88 said:
Shouldnt need oc app with his kernels mine is at 1.56 ever since i flashed it.
On demand is the only one that properly works with dual core processor. Even with an oc app you can only select on demand or performance and you wouldnt want to use that governor since it forces the cpu to work at max frequency at all times. To use oc daemon you need the virtous oc scaling files to select frequencies
Sent from my HTC Sensation 4G using XDA Premium App
Click to expand...
Click to collapse
Thanks. I'm curious then why faux includes smartass in his thread if on demand is the only one that works properly. I'm also not sure why mine is at stock clock speed, but it definitely is. So is oc daemon the way I should try to bump it up to 1.56?
I believe the smartass governor is supposed to have buipt in profiles like the ones you can make in a app like setCPU. so a cpu tuner would be pointless with the smartass.
And yes i prefer oc daemon to other apps like it. The newest one is like 2.1.3 i think. You are also gonna need the folder "vituous oc" with 6 files governors for screen on and off and min and max frequency. One file for each. Im on ARHD 3.0.4 with 0.1.0 kernal so it already came with the folder in system/etc/virtuous_oc
Sent from my HTC Sensation 4G using XDA Premium App
Sent from my HTC Sensation 4G using XDA Premium App
OK i have read up a little about live oc, but really i still dont understand it.
In NS tools there are 3 settings.... a % an "oc target low", "oc target high"
As i understand it the percentage is just how much each step of the cpu scaling gets bumped... so if your at 110% @ 1000mhz step it would actually be 1100mhz. And @ 110% the buss speed would be at 220mhz vs the stock 200. (is that correct)
But as far as the other two settings... oc target low, oc target high... what are those?
Really im just looking for a little more incite on how live oc works.
Thanks guys!
You can tell it to live oc within certain frequencies. So if you only want to to be on live oc from 200-800mhz, you can set it to do that
Sent from my Nexus S 4G using xda premium
rocket999 said:
You can tell it to live oc within certain frequencies. So if you only want to to be on live oc from 200-800mhz, you can set it to do that
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
AHHH ok so the min and max are the range in which the live oc takes place. below and above those min and max values it goes back to normal?
how much rise voltages from 1300cpz/100liveoc to 1320cpu/110liveoc?
Bus OC don't work at all. I've tried 3d benchmarks with and without this and there are not difference
Sent from my Nexus S using Tapatalk 2
raulillo88 said:
Bus OC don't work at all. I've tried 3d benchmarks with and without this and there are not difference
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
you must not be doing it right or applying works for me
EDIT: you do realize it will only over clock the freq of the low target and high target.
For example you run your benchmark and your cpu settings are going to be affected on the I/0 scheduler and cpu governor.
if i run Sio ~ On-Demand @ 100/1000 and my Live OC is 1200/1400 your not going to be using the OC settings because its only designed to, to OC the freq you chose it to.
So to make it work for benchmarking purposes i would run Sio ~ Performance @ 1400/1000 or even 1400/1400 so it would only use those OC'ed freqs. and have the Live OC either 1400/1000 say @ 105% or 1400/1400 @ 105% so it run Straight OC'ed freqs only.
Hey hey guys I'm on a nexus 5 with CM 11.2 kitkat 4.2.2 of course, on nightly 12-16-13
So I've recently gotten into Kernels and its my understanding that CM doesn't work with Franco and has one baked in anyway, so I've been trying to keep my max CPU frequency at 2.26 and the min at 300 with the interactive governor and noop I/o but occasionally the darn thing keeps on resetting, so I tried using no frills, but the same result of the min and max being reset occasionally to what they wanna be, what am I doing wrong?
Sent from my Nexus 5 using xda app-developers app
Hi,
It's normal, it's how MpDecision from Qualcomm works, when you touch the screen the min CPU freq jumps to 1,2 Ghz for xx ms, for smoothess purpose...
Try Trickster Mod (Play Store) there is an option to lock the CPU freqs, it will locked the min CPU freq to 300 Mhz (or whatever freq you want). But don't turn off MpDecision in Trickster Mod unless you want the four cores always online because there will not be another hotplug routine instead.
Other thing is to use a custom kernel with MpDecision disabled and different hotplug solution...
Sent from my LG-D802 using xda premium
I think that sir did the trick! Thanks for the help!
my phone has all its frequency’s at 600mv. But this only works in performance mode for some reason.
What I do is set it to performance, lower the frequency’s to 600mv and set it back to smartass v2. That seems to work. But trying to set it to those low frequency on smartass cause the phone to reboot. Why is that?
Is ur kernel custom or stock and what app are u using to control frequencies
Nick_73 said:
Is ur kernel custom or stock and what app are u using to control frequencies
Click to expand...
Click to collapse
Its a custom kernel and I am changing it by the terminal.
Using this app you may be more successful. But the kernel creator may make certain frequencies available to certain governors
The lower frequencies require more voltage to be stable. When on performance, your CPU is stuck at the max frequency, smartass and other governors scale frequencies and so when you are not using your phone, the frequency drops and so those lower frequency were not stable at what you have set your device to. Raise your frequencies back to stock and take it one frequency at a time.
Sent from my Nexus 4 using XDA Free mobile app