"Stumbled" across this article
In my opinion one of the most informative!
http://www.acsyndicate.net/which-cpu-governor-should-you-go-with/
good read. thanks.
Shameless.
Sent from my SPH-D700 using xda premium
squshy 7 said:
Shameless.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Lol. Troublemaker!
Sent from my SPH-D700 using xda premium
squshy 7 said:
Shameless.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
What does that mean? lol
qbking77 said:
What does that mean? lol
Click to expand...
Click to collapse
i think because it was a team page it links to. that was my impression.
Sent from my SPH-D700 using xda premium
I was gonna post about this actually very informative. Now I'm using voltage control. What should I set for the I/o scheduler? I tried interactive governor and my phone almost locked up lol. Was using conservative. Just started using ondemand.
Sent from my SPH-D700 using XDA Premium App
Bump
Sent from my SPH-D700 using XDA Premium App
For your reading enjoyment.
There are actually a few things Samsung have done that contrast these docs, the biggest of which is that Samsung's conservative governor is more like a transitional governor, in that it simply uses the "transition_states" array to do it's scaling (rather than the calculation conservative uses to determine the next frequency).
nubecoder said:
For your reading enjoyment.
There are actually a few things Samsung have done that contrast these docs, the biggest of which is that Samsung's conservative governor is more like a transitional governor, in that it simply uses the "transition_states" array to do it's scaling (rather than the calculation conservative uses to determine the next frequency).
Click to expand...
Click to collapse
So Nubecoder, is using "on demand" on our phones bad or not? I haven't had any problems running 1400/100 on demand with no,undervolting for months without issue but I still wanted to know. Thanks.
Sent from my SPH-D700 using xda premium
JohnCorleone said:
So Nubecoder, is using "on demand" on our phones bad or not? I haven't had any problems running 1400/100 on demand with no,undervolting for months without issue but I still wanted to know. Thanks.
Click to expand...
Click to collapse
[The short answer]
If it's working for you, then it's not "bad". ;]
[The much longer than I had expected it to be, other info / opinions on Epic governor related issues, answer]
It's just that the Samsung phones don't have anywhere near the amount of steps as other devices do, and their handling of which step to jump to when asked for freq X is not that great (and becomes more of a problem when frequencies are disabled with tools like setCPU and Voltage Control).
The other big thing is that (in Samsung's code) there isn't any compliance to the cpufreq "scaling_min" setting, it simply uses a clip to make sure it's not below the lowest available freq (ie 100MHz) and doesn't care if it's below the scaling_min. Some phones handle the 100MHz better than others (and the original 100MHz is possibly "broken" when you look at it's divisors).
Note that some do kernels have some changes in place to force the compliance of the scaling_min setting. (I know Genocide does anyway.) (And mine does but it has yet to be released to the wild.)
There's some other things in play as well, like the DVFS lock that can be applied to force the frequency to be a "fixed" freq (as in won't change) or a "high_lock" which is basically "no lower than X".
For example, there is a DVFS lock used any time you touch the touch screen that will not allow the CPU to scale below 800MHz (lock token 6 IIRC). (The lock is lifted when you let go). And Samsung's conservative (IMO transitional) governor uses a fixed lock of 800MHz during sleep (suspend).
I've spent a lot of time trying to figure all of this out and to determine why Samsung's devices (specifically the Epic) simply don't play well with most governors.
I have worked out most of the bugs in my kernel (I wrote a function to handle getting the nearest requested frequency with disabled freqs in mind). But it's still not perfect.
I've considered going full force and adding tons of freqs to see how that works out, but that's a crap-ton of work, and my current goal is to release my kernel before official GB drops.
Hopefully will be over the next few days (but I've been saying that to myself for weeks now it seems).
=]
Related
I am using CM7 ROM and Glitch kernel together on the Verizon Fascinate and was just wondering what everyone is using for the I/O Scheduler and the CPU Governor with Voltage control.
I have mine OC'd to 1.5GHz and using bfq and performance.
that setup you are using will suck down battery in no time. Im running v13 from paid glitch app, smartass v2 with deadline and underclocked to 800mhz and get 5 hours of ACTUAL PHONE USE/SCREEN ON TIME and about a full day before needing a re-charge on an 1800ma samaung battery and the phone still flys. zero lag! You really dont need to run any more than 1 ghz, but 1.2ghz will give you crazy speed and still allow for some good batterylife. 1.5 is overkill.
davwman said:
that setup you are using will suck down battery in no time. Im running v13 from paid glitch app, smartass v2 with deadline and underclocked to 800mhz and get 5 hours of ACTUAL PHONE USE/SCREEN ON TIME and about a full day before needing a re-charge on an 1800ma samaung battery and the phone still flys. zero lag! You really dont need to run any more than 1 ghz, but 1.2ghz will give you crazy speed and still allow for some good batterylife. 1.5 is overkill.
Click to expand...
Click to collapse
smartass is best in my opinion. It seems to run lower clocks more often when high clock is not needed.. I don't have smartass v2 for some reason
Sent from a beautiful miui fascinate
I use cfq and smartassv2. Here is a thread with explanations of all of the schedulers and governers, how they work and what ones are the best.
http://forum.xda-developers.com/showthread.php?t=1309698
Using noop/smartass the last day or so...seems to be running smooth.
Smartass never seems to go below 400mhz on my phone. I've been using OnDemand.
I haven't really noticed any performance difference with any of the IO schedulers. Probably because it's flash and not a disk based drive in the phones.
jimv2000 said:
Smartass never seems to go below 400mhz on my phone. I've been using OnDemand.
I haven't really noticed any performance difference with any of the IO schedulers. Probably because it's flash and not a disk based drive in the phones.
Click to expand...
Click to collapse
actually, I just noticed that as well. interesting find. Ill give ondemand with deadline a shot.
sageDieu said:
I use cfq and smartassv2. Here is a thread with explanations of all of the schedulers and governers, how they work and what ones are the best.
http://forum.xda-developers.com/showthread.php?t=1309698
Click to expand...
Click to collapse
Thanks! This is an awesome post!
davwman said:
that setup you are using will suck down battery in no time. Im running v13 from paid glitch app, smartass v2 with deadline and underclocked to 800mhz and get 5 hours of ACTUAL PHONE USE/SCREEN ON TIME and about a full day before needing a re-charge on an 1800ma samaung battery and the phone still flys. zero lag! You really dont need to run any more than 1 ghz, but 1.2ghz will give you crazy speed and still allow for some good batterylife. 1.5 is overkill.
Click to expand...
Click to collapse
I do have it a little overkill, but I enjoy the speed when using some apps like games. My battery does last a whole day however with the 1800ma battery life, but then again all I use my phone for during the day is texting or VNC. I'm gonna try the smartass V2 and Deadline. Thanks!
I do quite a bit of gaming on my device (9mm, Dungeon Defenders, etc...). Overclock is set at 1.4 no UV, with absolutely no lock ups. BFQ and smartass yield the highest fps for me on V13RC.
Sent from my SCH-I500 using XDA App
I thought we weren't supposed to use performance because it doesn't respect thermal safeguards. Am I correct?
Sent from my HP Touchpad using xda premium
bobloblaw1 said:
I thought we weren't supposed to use performance because it doesn't respect thermal safeguards. Am I correct?
Sent from my HP Touchpad using xda premium
Click to expand...
Click to collapse
I did not know that
Sent from a beautiful miui fascinate
Performance would be a bad idea over long periods of time. Essentially since it runs the phone at the highest possible frequency for 100% of the time, it stresses the CPU much more than any other option. This could cause overheating if used for too long, not to mention the toll on your battery. We all assume that it would decrease the life of your processor because it logically could, but that isn't a big deal sienc you'll likely be upgrading long before the processor would begin to fail regardless of what you do with it now.
lordnikko said:
I do quite a bit of gaming on my device (9mm, Dungeon Defenders, etc...). Overclock is set at 1.4 no UV, with absolutely no lock ups. BFQ and smartass yield the highest fps for me on V13RC.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Interesting, when I set BFQ and Smartass on mine I get force closes on the simple apps, for instance the internet browser or file viewer. But when I play games on it I dont get any force closes on the games.
Maybe try clearing data on voltage control & reflashing kernel. I have been running my current configuration on MIUI, CM7, and now Pool Party for the last 90 days or so with no issues.
Sent from my SCH-I500 using XDA App
Ok will do thanks!
Sent from my SCH-I500 using XDA App
Is performance save
Sent from my SCH-I500 using XDA App
Enyo. said:
Is performance save
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
?
Sent from my SCH-I500 using xda premium
Enyo. said:
Is performance save
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Assuming you mean "safe" then yes over short periods of time it's fine. If you tried to run at a high clock on performance all the time you would probably get heat and battery life problems.
I'm running miui and glitch v12 and I find it very strange that my phone runs really good (almost as good as any combination that I tested) on conservative governor.
Sent from my SCH-I500 using xda premium
mkropf said:
I'm running miui and glitch v12 and I find it very strange that my phone runs really good (almost as good as any combination that I tested) on conservative governor.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Thats not strange at all really. I've had it last multiple days with data and everything off, conservative, and underclocled to 800mhz when I needed to be away from a charger for a while.
and it performed really well.
Sent from my MIUI SCH-i500
Now that we have a new way to overclock in v14 there are near unlimited variables to overclocking with this kernel. I've found a good balance of performance with 1300ghz step and live OC value of 121%. Let us know what has worked for you. You may include voltages as well.
I'm using reborn90's settings
200-1000; 110% live oc arm volt; 800/950/1100/1175 int volt; 1000/1000/1000/1025
Seems rather steady, I also recommend turning save on boot in settings of nstools before applying these settings just in case xD
Sent from my SCH-I500 using xda premium
I am on 100-1300 with 116% Live OC, haven't played with voltage yet but everything runs great.
I can't seem to get any live OC percentage stable and anything around 118% + automatically freezes and reboots.any suggestions?
Sent from my SCH-I500 using xda premium
mleonm5 said:
I can't seem to get any live OC percentage stable and anything around 118% + automatically freezes and reboots.any suggestions?
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Do you UV first then live oc? Or is it just stock voltages?
Sent from my SCH-I500 using xda premium
For the most part I just use stock voltages when playing around with live OC because I haven't found any voltages in threads that i'm sure are stable.
Sent from my SCH-I500 using xda premium
mleonm5 said:
For the most part I just use stock voltages when playing around with live OC because I haven't found any voltages in threads that i'm sure are stable.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
it depends on how far you phone can go, some can oc more then others but some less then others, I usually never go passed 1.2ghz ,I'd rather save battery.
Sent from my SCH-I500 using xda premium
Just my opinion, but since Android 4.0 relies so heavily on the hardware rendering capabilities of the phone you'd be better off to UNDERCLOCK the CPU to 800mHz, and apply the Live OC to say 125% and have an effective CPU speed of 1000mHz while increasing the GPU clock by the same amount. I've tried it and it works very well but I didn't stick with it long enough to see how it affected battery life. You will need to modify your voltages though. I was at 1250mV on the 800mHz step.
If anyone is interested in just using stock settings, i found this thread interesting:
http://forum.xda-developers.com/showthread.php?t=1424064
100-800 mhz, 125% live oc.
So how much of a change have you noticed from Stock kernel to Glitch. I tried OCing once.. and it froze.. and phone died.. and ended up having to wipe / re-flash. Probably user error though
Just wanted to say I accidentally OC'd to 1.4ghz with 110% LOC and man did this thing fly and didn't even crash.
Sent from my ICS Mesmerize
I noticed I'm able to achieve higher stable oc (over 1500) using low leakage voltage and live oc of 116 or less. Without low leakage i can barely acheive 1400 oc at anything over 110 live oc. Never noticed this much difference in internal voltage stability in previous kernel version. I wonder what's changed?
Hey guys, touch booster is really annoying on this phone. It pushes the phone to 1.06GHz everytime I touch it, and is starting to bug me.
Is there anyway to keep it scaling up properly?
I'm no expert at this stuff, but isn't this fast jump in CPU clock what pretty much makes Project Butter possible?
If I understand right (and I probably don't), I think this might have to do with with governor in-use. If your rooted; try using a different governor and then touching the screen.
Great, so now people are complaining about Project Butter's features... ok
How exactly does something like this bug you?
People are getting way too picky with this phone now. Relax, its a phone guys
Sent from my E4GT by using THE FORCE
Next thread will be " This phone is too fast, how do I slow it down to keep up?"
Sent from my Nexus 4 using xda premium
The CPU goes up when you touch it so it can be responsive and quick to your inputs. How is this so annoying?
If you root it you can lower the max or change the governor buy chances are you will lose much of your responsiveness.
I understand that it is good for us to discuss issues and problems but some of the things I am seeing here are just really nit picking and complaining about things that are not bad at all. We are a spoiled society of humans, some more than others i guess.
sent via xda premium with nexus 7
Monk4Life said:
Next thread will be " This phone is too fast, how do I slow it down to keep up?"
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
you joke but there's a surprising amount of people that underclock their cpu thinking it will save battery...
qwahchees said:
Hey guys, touch booster is really annoying on this phone. It pushes the phone to 1.06GHz everytime I touch it, and is starting to bug me.
Is there anyway to keep it scaling up properly?
Click to expand...
Click to collapse
Get some CPU control app and change the minimum frequency from 1GHz to 384MHz.
/thread
neotekz said:
you joke but there's a surprising amount of people that underclock their cpu thinking it will save battery...
Click to expand...
Click to collapse
Under clocking will save battery in most cases but ot will also make your phone sluggish and slow depending on how much.
sent via xda premium with nexus 7
---------- Post added at 12:07 AM ---------- Previous post was at 12:05 AM ----------
richteralan said:
Get some CPU control app and change the minimum frequency from 1GHz to 384MHz.
/thread
Click to expand...
Click to collapse
That will make your phone run so slow and crappy... Why have a decent cpu if the plan is to chop it? This defeats the entire purpose of having a 1.5ghz clock speed..
sent via xda premium with nexus 7
Richieboy67 said:
That will make your phone run so slow and crappy... Why have a decent cpu if the plan is to chop it? This defeats the entire purpose of having a 1.5ghz clock speed..
sent via xda premium with nexus 7
Click to expand...
Click to collapse
You have no idea what you are talking about.
Check the meaning of "MINIMUM CPU FREQUENCY".
P.S. O and btw I'm changed it to 384MHz on my Nexus 4. AND........wait for it........my nexus 4 is not slow and crappy........woo mind blown!
What I find interesting is on the nexus 4 the governor is on demand , and the scaling range is 0mhz- 1026mhz ( you can check using CPU spy +)
However on the nexus 10 , the governor is interactive and the scaling range is 0mhz -200mhz
I wonder why that is
Sent from my Nexus 10 using Tapatalk 2
italia0101 said:
What I find interesting is on the nexus 4 the governor is on demand , and the scaling range is 0mhz- 1026mhz ( you can check using CPU spy +)
However on the nexus 10 , the governor is interactive and the scaling range is 0mhz -200mhz
I wonder why that is
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
that app is broken.
Try No-frills CPU control, or even AnTuTu CPU Master.
Is it interactive on the nexus 4 then? I just checked on my n10 smd it still says interactive
Sent from my Nexus 10 using Tapatalk 2
italia0101 said:
Is it interactive on the nexus 4 then? I just checked on my n10 smd it still says interactive
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
I'm using no-frills and the default is ondemand, scaling from 1GHz to 1.5GHz.
What I changed is only the minimum frequency from 1GHz to 384MHz. Nothing more.
The scaling...
Sent from my Nexus 4 using XDA Premium HD app
richteralan said:
I'm using no-frills and the default is ondemand, scaling from 1GHz to 1.5GHz.
What I changed is only the minimum frequency from 1GHz to 384MHz. Nothing more.
Click to expand...
Click to collapse
Yea that's cool I get that . I just wonder why the governor is different on the nexus 10
Sent from my Nexus 4 using Tapatalk 2
italia0101 said:
Yea that's cool I get that . I just wonder why the governor is different on the nexus 10
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Ask Google.
I have no idea. And I don't have a Nexus 10.
italia0101 said:
Yea that's cool I get that . I just wonder why the governor is different on the nexus 10
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Nexus 10 is a dual core tablet, not a phone. Check your PC some time or laptop. They scale totally differently than a phone does.
sent via xda premium with nexus 7
Can someone please explain to me why none of the kernel's have OC ability?// I think it's due to quad core overheating but I'm not sure and would really love an actual explanation.. Thanks
Sent from my Nexus 4 using xda premium
they all started with OC ability right at the beginning, then .. a good few number of people had HARDWARE bricked devices, that had a fault with the battery no longer being connected or something
they all had overclocking in common, since then , its been removed on most or all kernels
I'm sure that as time progresses it will be made available again. What's the need to clock anyway its fast enough as it is
Sent from my Nexus 4 using xda premium
zephiK said:
I'm sure that as time progresses it will be made available again. What's the need to clock anyway its fast enough as it is
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
This is true, its a 1.5ghz quad core lol why do we need more ?
Also what was happening in some kernels was that mpdecision (which is qualcomms code that says when the cores should be on and offline, i.e hotplug) was using the hardware maxs of each kernel, so if the kernel was capable of going to 1.8ghz, even if you set the max to 1.4ghz ( using software) , mpdecison would override the software and use the hardware max.. therefore.. .it would ramp all cores up to 1.8.. which caused a major cluster ****..
italia0101 said:
This is true, its a 1.5ghz quad core lol why do we need more ?
Also what was happening in some kernels was that mpdecision (which is qualcomms code that says when the cores should be on and offline, i.e hotplug) was using the hardware maxs of each kernel, so if the kernel was capable of going to 1.8ghz, even if you set the max to 1.4ghz ( using software) , mpdecison would override the software and use the hardware max.. therefore.. .it would ramp all cores up to 1.8.. which caused a major cluster ****..
Click to expand...
Click to collapse
Will I certainly don't need it. Would it be nice to have? Yeah but it isn't on the top of my priority list.
What he's saying about mpdecision is true. If you read the change log for Franco kernel he removed mpdecision and is working towards a open platform for kernels. So we should hopefully be seeing more goodies.
Sent from my Nexus 4 using xda premium
Okay,so i made this thread so that development thread become less spammed with your questions.
Please,share your opinions here and ask questions,someone will answer you,and share your screenshots of battery life.
I personally use PegasusQ+VR,it gives great performance and good battery life.
My second choice would be Abyssplug+SIO,especcialy for the hotplug feature.
(In case you dont know what Hotplug is,its the feature that turns off the second core when your phone is not in use.)
I cant decide wich is better,tommorow ill test Hotplug+sio,and ill post screenshots of both tommorow.
Please,ask any questions here,dont spam Benz's threads.
Thank you
DeHuMaNiZeD said:
Okay,so i made this thread so that development thread become less spammed with your questions.
Please,share your opinions here and ask questions,someone will answer you,and share your screenshots of battery life.
I personally use PegasusQ+VR,it gives great performance and good battery life.
My second choice would be Abyssplug+SIO,especcialy for the hotplug feature.
(In case you dont know what Hotplug is,its the feature that turns off the second core when your phone is not in use.)
I cant decide wich is better,tommorow ill test Hotplug+sio,and ill post screenshots of both tommorow.
Please,ask any questions here,dont spam Benz's threads.
Thank you
Click to expand...
Click to collapse
OnDemand + CFQ (Like in stock ROM) the only way that don´t dry my battery.
With that combination my phone is slow like hell..have you tried those that i wrote.
Sent from my GT-I8190 using XDA Premium 4 mobile app
DeHuMaNiZeD said:
With that combination my phone is slow like hell..have you tried those that i wrote.
Sent from my GT-I8190 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, but my batteryd doesn't like them very much
Sent from my GT-I8190 using Tapatalk
thats odd
Sent from my GT-I8190 using XDA Premium 4 mobile app
Hi, can you tell me the best combination of governors to use. I'm using latest cm
10.1 maclaw build with hotplug and noop, but i think CPU its not sleeping cause i loose about 5% battery in 2hours withought using my fone at all. Thanks
Sent from my GT-I8190 using xda app-developers app ?
Hotplug governor is indeed a joke, at least in Maclaw's CM (not surprised). There is no way to set it up for low battery drain /and/ reasonably smooth functionality. Right now I am using Ondemand + CFQ while playing with the powersave bias and up threshold parameters. The only thing I wish I had from Maclaw/Benz's kernel is the vr/sio schedulers.
You have VR and sio schelduer in Benz's kernel,and Abyssplug governor with real hotpulg feature,when you dont use the phone cpu shuts down one core and the remaining core runs on 200Mhz and 1% usage.
Sent from my GT-I8190 using XDA Premium 4 mobile app
I would gladly use that kernel if it didn't have the dirty flickering fix. And if it didn't require CM10.1 reboot edition.
Also, when I was on CM i ran a logcat with hotplug activated. The second core would often reactivate even if the phone wasn't doing anything, with the screen turned off, then soon turn off and after a few seconds repeat the process. Maybe this phone really needs the core.
What flicketing fix? I got no flickering on the latest Maclaws cm and benzs kernel..and it shuts down the core,you can see with system monitor when your screen is on..dunno for screen off,but i get like 1% drained for a hour with screen off
Sent from my GT-I8190 using XDA Premium 4 mobile app
The 63 fps refresh rate, which "fixes" the UI flickering.
And yes, I saw the second core turning off myself. However, I am not sure if it keeps being off enough time.
Well in maclaws rom i dont have flickering,but in olivers i had. I dont know,i got decent battery life. Not good as stock,but its ok
Sent from my GT-I8190 using XDA Premium 4 mobile app
Which is more battery friendly? Abyssplug or Pegasusq?
Sent from my GT-I8190 using XDA Premium 4 mobile app
Nemo1984 said:
Which is more battery friendly? Abyssplug or Pegasusq?
Sent from my GT-I8190 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Read this. It will help you to decide which is the best for your needs:good::good:
P.S: BTW, @DeHuMaNiZeD, if you want, add this link to your OP, so people can read it & learn.
Nemo1984 said:
Which is more battery friendly? Abyssplug or Pegasusq?
Sent from my GT-I8190 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Pegasusq said to have hotplugging but doesnt seem to work with screen on
Based on what I read, my best guess would be Abyssplug. I'll run some tests and will post my results.
Sent from my GT-I8190 using XDA Premium 4 mobile app
AssToast said:
Pegasusq said to have hotplugging but doesnt seem to work with screen on
Click to expand...
Click to collapse
Yes, it only turn off one core when the screen off. I'm testing pegasusq + sio
For the next days, I'll be on abyssplug + sio.
Sent from my GT-I8190 using XDA Premium 4 mobile app
metalboy94 said:
The 63 fps refresh rate, which "fixes" the UI flickering.
And yes, I saw the second core turning off myself. However, I am not sure if it keeps being off enough time.
Click to expand...
Click to collapse
And what exactly is so wrong with 63 fps refresh rate? Will your screen fry because of it? No it won't because it can't. Will your phone explode while being used? No it won't because it can't. What's the issue here then? Tell me.
Benzonat0r said:
And what exactly is so wrong with 63 fps refresh rate? Will your screen fry because of it? No it won't because it can't. Will your phone explode while being used? No it won't because it can't. What's the issue here then? Tell me.
Click to expand...
Click to collapse
Have you considered the battery drain implications? The battery is weak enough as it is, a higher than normal refresh rate only wastes more GPU power thus more battery.