So im running moto Z Play stock kernel and governor Interactive.
There are 7 levels of frequency 600-1000-1400-1600-1800-1900-2000
My goal is to maximize performance with within acceptable heating.
Should inset the minimum to 1000 or 1400 ?
Will there be any differences ?
Related
Hi all!
I'm playing with setCPU and probably I found my high stable freq. to 787Mhz.
I can run quandrant till 825MHz (1300+) but it seems not very stable and sometimes freeze during normal operation.
I set 787Mhz and interactive mode on setCPU and I leave 245 as min freq.
I setup 2 profile in order to downgrade to the original 600MHz and 245 with powersave when the battery is < 20% or the temperature of the cpu is > 50.
My question are:
- Is the interactive mode the best option for our Optimus One or there's a best choice? What is the differenze of the different operating mode?
- What is the "temperature limit" of the cpu? I set 50 but my cpu start from 35 up to 39.5 during stress at the moment. Should I set 40?
- How the min freq influence the performance and the battery life? Is it good to increse the min freq (320?) too?
Many thanks and sorry for the many questions.
is set cpu stable on lg optimus one?
Hi guys,
Please clarify on the following points:
1. Are there any major differences among the CPU governers??? I use Smartass because I see a major group of people using it.
2. What are the optimal values for Min and Max CPU speed? And are there any factors based on which we have to decide the values or we can keep anything we wish?
Thanks in advance
Frequencies and their effect on battery here
^Pretty much what you're looking for. Just analyze the chart and test it for yourself too. Also read, read
For governors:
smartass governor - is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 - why?! - it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more.
ondemand
Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed. - SetCPU website
conservative
Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery. - SetCPU website
performance
Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking. - SetCPU website
powersave
Available in some kernels. It will keep the CPU running at the "min" set value at all times. - SetCPU website
userspace
A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor. - SetCPU website
interactive
Advantages:
+ significantly more responsive to ramp cpu up when required (UI interaction)
+ more consistent ramping, existing governors do their cpu load sampling in a workqueue context, the 'interactive' governor does this in a timer context, which gives more consistent cpu load sampling.
+ higher priority for cpu frequency increase, rt_workqueue is used for scaling up, giving the remaining tasks the cpu performance benefit, unlike existing governors which schedule rampup work to occur after your performance starved tasks have completed.
Click to expand...
Click to collapse
I hope that makes it clearer
Kira.Lawliet said:
Frequencies and their effect on battery here
^Pretty much what you're looking for. Just analyze the chart and test it for yourself too. Also read, read
I hope that makes it clearer
Click to expand...
Click to collapse
Wonderful post! Thank you.. even though the post was too technical for a n00b like me, I could grasp info out of it. Sure it helped me.
Hey guys!
I was wondering if anyone can give me some info on the differences between the governors with doomkernel and the schedulers.
Thanks!
Cheers,
This was posted by DooMLoRD, i just copied the post not all governors are there:
2. Governors In the Linux Kernel ================================
2.1 Performance ------------------------------
The CPUfreq governor "performance" sets the CPU statically to the highest frequency within the borders of scaling_min_freq and scaling_max_freq.
2.2 Powersave ----------------------------
The CPUfreq governor "powersave" sets the CPU statically to the lowest frequency within the borders of scaling_min_freq and scaling_max_freq.
2.3 Userspace ----------------------------
The CPUfreq governor "userspace" allows the user, or any userspace program running with UID "root", to set the CPU to a specific frequency by making a sysfs file "scaling_setspeed" available in the CPU-device directory.
2.4 Ondemand ---------------------------
The CPUfreq governor "ondemand" sets the CPU depending on the current usage. To do this the CPU must have the capability to switch the frequency very quickly. There are a number of sysfs file accessible parameters:
sampling_rate: measured in uS (10^-6 seconds), this is how often you want the kernel to look at the CPU usage and to make decisions on what to do about the frequency. Typically this is set to values of around '10000' or more.
show_sampling_rate_(min|max): the minimum and maximum sampling rates available that you may set 'sampling_rate' to.
up_threshold: defines what the average CPU usage between the samplings of 'sampling_rate' needs to be for the kernel to make a decision on whether it should increase the frequency. For example when it is set to its default value of '80' it means that between the checking intervals the CPU needs to be on average more than 80% in use to then decide that the CPU frequency needs to be increased.
ignore_nice_load: this parameter takes a value of '0' or '1'. When set to '0' (its default), all processes are counted towards the 'cpu utilisation' value. When set to '1', the processes that are run with a 'nice' value will not count (and thus be ignored) in the overall usage calculation. This is useful if you are running a CPU intensive calculation on your laptop that you do not care how long it takes to complete as you can 'nice' it and prevent it from taking part in the deciding process of whether to increase your CPU frequency.
2.5 Conservative -------------------------------
The CPUfreq governor "conservative", much like the "ondemand" governor, sets the CPU depending on the current usage. It differs in behaviour in that it gracefully increases and decreases the CPU speed rather than jumping to max speed the moment there is any load on the CPU. This behaviour more suitable in a battery powered environment. The governor is tweaked in the same manner as the "ondemand" governor through sysfs with the addition of:
freq_step: this describes what percentage steps the cpu freq should be increased and decreased smoothly by. By default the cpu frequency will increase in 5% chunks of your maximum cpu frequency. You can change this value to anywhere between 0 and 100 where '0' will effectively lock your CPU at a speed regardless of its load whilst '100' will, in theory, make it behave identically to the "ondemand" governor.
down_threshold: same as the 'up_threshold' found for the "ondemand" governor but for the opposite direction. For example when set to its default value of '20' it means that if the CPU usage needs to be below 20% between samples to have the frequency decreased.
2.6 Interactive ------------------------------
The CPUfreq governor "interactive" is designed for low latency, interactive workloads. This governor sets the CPU speed depending on usage, similar to "ondemand" and "conservative" governors. However there is no polling, or 'sample_rate' required to scale the CPU up.
Sampling CPU load every X ms can lead to under powering the CPU for X ms, leading to dropped framerate, stuttering UI etc..
Scaling the CPU up is done when coming out of idle, and like "ondemand" scaling up will always go to MAX, then step down based off of cpu load.
There is only one tuneable value for this governor:
min_sample_time: The ammount of time the CPU must spend (in uS) at the current frequency before scaling DOWN. This is done to more accurately determine the cpu workload and the best speed for that workload. The default is 50ms.
2.7 MinMax ------------------------------
The CPUfreq governor "maxmin" tries to minimize the frequency jumps by limiting the selected frequencies to only two frequencies: either the min or the max frequency of the current policy. The frequency is raised or lowered according to the current load and the 'up_threshold' and 'down_threshold'.
Its parameters and implementation are similar to that of conservative.
It does not have the freq_step parameter as it jumps right from min to max and vice-versa.
The sampling_down_factor, unlike conservative, will count the minimal number of samplings since the last time we saw the 'up_threshold' load on the CPU. Hence it is set to higher default and acts as a limiter not to do too many frequency jumps without hurting the performance.
Thanks sorry, didnt see it for some reason. Ignore my questions.
Cheers,
oppiee said:
Thanks sorry, didnt see it for some reason. Ignore my questions.
Cheers,
Click to expand...
Click to collapse
One thing to note pal. All chipsets have different tolerances so whereas interactive works best for me, it may not be good for u. Just test em and use CPU spy/ ur own judgement to c which suits ur phone best.
Sent from my X10i using XDA App
Yup I am currently fiddling around with the different settings. The main thing I want to accomplish is not to have lag when im scrolling and opening up basic apps such as dialer and browser. I dont really play games. I hate the fact that the phone lags up sometimes. So far Its ok, but getting some WLOD on super high freq.
Any suggestions?
oppiee said:
Yup I am currently fiddling around with the different settings. The main thing I want to accomplish is not to have lag when im scrolling and opening up basic apps such as dialer and browser. I dont really play games. I hate the fact that the phone lags up sometimes. So far Its ok, but getting some WLOD on super high freq.
Any suggestions?
Click to expand...
Click to collapse
Can u post a screenshot of CPU tuner or whatever u use of freqs u use? Also are u using doomkernel fs version as I think some handsets can't even boot up oc kernel.
Sent from my X10i using XDA App
Any good programs to take screen shots? I am using the highest OC kernel by DL, and using doomkernel wolfbreak V7b6.
Not mean to sound patronising pal but just type screen shot into android market theres plenty
Edit: ur phone prob can't handle the overclock. Read the kernel thread it says this pal.
Sent from my X10i using XDA App
Oh i think there might has been some misunderstanding. My phone is running fine, just doing some testing. at 1.229 Mhz I tend to get WLODs, using minmax with SIO.
At 1.114 and 245, using min max with SIO. everything is fine so far. I just thought you wanted to know for your own purposes.
Cheers
Sorry buddy I misunderstood
Sent from my X10i using XDA App
thers some missing from the top
lagfree
scary
brazilianwax
savaged zen
what do theese do
also whats the best settings from all of them from your opinion
I have:
Brazilianwax
Smoothass
Lagfree
Smartassv2
SavagedZen
Scary
Smartass
Minmax
Interactivex
Interactive
Conservative
Userspace
Powersave
OnDemand
Performance.
Not used them all but lagfree is (as suggested free from lag & smooth. Brazilianwax didnt work for me very laggy. Scary was quite good also, along with interactive. Not really tested the others enough to pass comment to be honest
I had seen different scaling for processor which is the best to knight elf scaling for a normal day today usage
sent from my xperia neo v
roninnbaby said:
I had seen different scaling for processor which is the best to knight elf scaling for a normal day today usage
sent from my xperia neo v
Click to expand...
Click to collapse
Scale from 245 to 806 Mhz and governor smartassv2 for overall performance and battery saving...if more performance needed then go for onedemand governor and the same scaling..else you can always leave it at default i.e 1017 Mhz I believe and just have a scaling profile for screen off..
Scaling range
phil427 said:
Scale from 245 to 806 Mhz and governor smartassv2 for overall performance and battery saving...if more performance needed then go for onedemand governor and the same scaling..else you can always leave it at default i.e 1017 Mhz I believe and just have a scaling profile for screen off..
Click to expand...
Click to collapse
Yup...works smoothly within this range....:laugh:
phil427 said:
Scale from 245 to 806 Mhz and governor smartassv2 for overall performance and battery saving...if more performance needed then go for onedemand governor and the same scaling..else you can always leave it at default i.e 1017 Mhz I believe and just have a scaling profile for screen off..
Click to expand...
Click to collapse
But since I am using knight elf kernal I can over cloxk up to 1.6 but now o had only overclocked to 1.2 and ondemand scaling is. Tht good or should I do anything to make my phone smooth
sent from my xperia neo v
Currently it looks like the swappiness in kernel settings is set to 100%...typically this is around 60...on hi ram devices it might be set to something low like 10 to be resistant to swapping...still 100% seems really high....I've also noticed when several apps have been installed to the device after a while of sitting it becomes unusable due to non-responsiveness. Reboot it and it will be allright for a while...so I think the apps are eating up the memory and the swap is dragging everything to a crawl. Anyone have some suggested "Kernel Adiuter" settings?
famewolf said:
Currently it looks like the swappiness in kernel settings is set to 100%...typically this is around 60...on hi ram devices it might be set to something low like 10 to be resistant to swapping...still 100% seems really high....I've also noticed when several apps have been installed to the device after a while of sitting it becomes unusable due to non-responsiveness. Reboot it and it will be allright for a while...so I think the apps are eating up the memory and the swap is dragging everything to a crawl. Anyone have some suggested "Kernel Adiuter" settings?
Click to expand...
Click to collapse
I had tons of performance isssues, which were easily solved by flashing Squid Kernel on my device. I followed the isntructions given by squid my device performance much better and also has great battery life.
squid2 said:
My new Lionfish governor combines traits of the conservative, ondemand, and interactive governors. It is designed to maximize battery life without noticeably impacting performance. It responds quickly to heavy loads (similar to ondemand and interactive) while staying within the region of optimal CPU performance per watt. With moderate loads, it periodically votes to raise, maintain, or decrease the frequency. When there are enough votes to change the frequency, it is ramped up and down gradually. The voting mechanism reduces frequency jitter compared to ondemand and conservative. My testing had found that this governor uses moderate frequencies (where efficiency is optimal) more effectively than interactive, ondemand, and conservative. This improved frequency distribution results in a moderate reduction in CPU power consumption while maintaining responsiveness comparable to the interactive governor.
IntelliPlug is enabled by default in this kernel. The default governor is still interactive. For optimal performance and battery life, I recommend using the fiops IO scheduler, Lionfish governor, and lowering the CPU idle frequency to 400 MHz (from the default of 800 MHz). The combination of IntelliPlug, Lionfish, undervolting, and reducing idle to 400 MHz should result in a CPU power consumption reduction of around 20% compared to the stock kernel. This will typically correspond to 8-15% increase in battery life compared to the stock configuration.
Click to expand...
Click to collapse
famewolf said:
Currently it looks like the swappiness in kernel settings is set to 100%...typically this is around 60...on hi ram devices it might be set to something low like 10 to be resistant to swapping...still 100% seems really high....I've also noticed when several apps have been installed to the device after a while of sitting it becomes unusable due to non-responsiveness. Reboot it and it will be allright for a while...so I think the apps are eating up the memory and the swap is dragging everything to a crawl. Anyone have some suggested "Kernel Adiuter" settings?
Click to expand...
Click to collapse
Wikipedia says: "Swappiness can be set to values between 0 and 100 inclusive. A low value causes the kernel to avoid swapping, a higher value causes the kernel to try to use swap space. The default value is 60, and for most desktop systems, setting it to 100 may affect the overall performance, whereas setting it lower (even 0) may decrease response latency." This value set to 100 is definitely the source of non-responsiveness. I would recommend 40 if you are using apps that are heavy on RAM (advanced games) and 60 if not but you may find better values yourself.