Related
Rom: Leedroid V2.1, Axiom S V1.0, TrickDroid V5.0(EU)
Kernel: stock HTC, Lowkernel v1.0.1, Vistuous v06
Apps & scripts: SetCPU, CPU Editor, Quick system info pro
http://forum.xda-developers.com/showthread.php?p=28214411#post28213828
There are also some other people who reported the same issue in this thread.
I'v tried all these kernels on three ROMs and they reported the same problem. The cpu1(2nd core) always keeps as ondemand mode. I've to use CPU Editor and enable Dual Core Mode to force it to other mode but after a reboot, it will reset to ondemand again. Sticky Enabled has no use here.
Another thing is after a reboot, the cpu1 frequency will also get a reset to the kernel's max. frequency supported. I've to set it again too.
Use Quick system info pro, it will shows out the current cpu0/1 governor and cpu scaling range very clearly.
SetCpu looks messed up on One S. The max frequency actually works as cpu1's max frequency while min frequency actually works as cpu0's max frequency.
It has no club to run the cpu1 ondemand at max all day long, it's just a waste of battery. On such a powerful S4 cpu, it's also non-sense to use ondemand governor as default. Interactive, Conservative, SmartassV2 are all better choices.
As a result, by using CPU Editor to lower the cpu1's speed and switch to other governor, my battery on daily use improved.
Android CPU governors explained
1: OnDemand
2: OndemandX
3: Performance
4: Powersave
5: Conservative
6: Userspace
7: Min Max
8: Interactive
9: InteractiveX
10: Smartass
11: SmartassV2
12: Scary
13: Lagfree
14: Smoothass
15: Brazilianwax
16: SavagedZen
17: Lazy
18: Lionheart
19: LionheartX
20: Intellidemand
21: Hotplug
22: BadAss
23: Wheatley
24:Lulzactive
25: Pegasusq/Pegasusd
26: hotplugx
27: AbissPlug
28: MSM DCVS
29: IntelliActive
30: Adaptive
31: Nightmare
32: ZZmove
INFO I/O Scheduler Go Here: SCHEDULER
1: OnDemand Governor:
This governor has a hair trigger for boosting clockspeed to the maximum speed set by the user. If the CPU load placed by the user abates, the OnDemand governor will slowly step back down through the kernel's frequency steppings until it settles at the lowest possible frequency, or the user executes another task to demand a ramp.
OnDemand has excellent interface fluidity because of its high-frequency bias, but it can also have a relatively negative effect on battery life versus other governors. OnDemand is commonly chosen by smartphone manufacturers because it is well-tested, reliable, and virtually guarantees the smoothest possible performance for the phone. This is so because users are vastly more likely to ***** about performance than they are the few hours of extra battery life another governor could have granted them.
This final fact is important to know before you read about the Interactive governor: OnDemand scales its clockspeed in a work queue context. In other words, once the task that triggered the clockspeed ramp is finished, OnDemand will attempt to move the clockspeed back to minimum. If the user executes another task that triggers OnDemand's ramp, the clockspeed will bounce from minimum to maximum. This can happen especially frequently if the user is multi-tasking. This, too, has negative implications for battery life.
2: OndemandX:
Basically an ondemand with suspend/wake profiles. This governor is supposed to be a battery friendly ondemand. When screen is off, max frequency is capped at 500 mhz. Even though ondemand is the default governor in many kernel and is considered safe/stable, the support for ondemand/ondemandX depends on CPU capability to do fast frequency switching which are very low latency frequency transitions. I have read somewhere that the performance of ondemand/ondemandx were significantly varying for different i/o schedulers. This is not true for most of the other governors. I personally feel ondemand/ondemandx goes best with SIO I/O scheduler.
3: Performance Governor:
This locks the phone's CPU at maximum frequency. While this may sound like an ugly idea, there is growing evidence to suggest that running a phone at its maximum frequency at all times will allow a faster race-to-idle. Race-to-idle is the process by which a phone completes a given task, such as syncing email, and returns the CPU to the extremely efficient low-power state. This still requires extensive testing, and a kernel that properly implements a given CPU's C-states (low power states).
4: Powersave Governor:
The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.
5:Conservative Governor:
This biases the phone to prefer the lowest possible clockspeed as often as possible. In other words, a larger and more persistent load must be placed on the CPU before the conservative governor will be prompted to raise the CPU clockspeed. Depending on how the developer has implemented this governor, and the minimum clockspeed chosen by the user, the conservative governor can introduce choppy performance. On the other hand, it can be good for battery life.
The Conservative Governor is also frequently described as a "slow OnDemand," if that helps to give you a more complete picture of its functionality.
6: Userspace Governor:
This governor, exceptionally rare for the world of mobile devices, allows any program executed by the user to set the CPU's operating frequency. This governor is more common amongst servers or desktop PCs where an application (like a power profile app) needs privileges to set the CPU clockspeed.
7: Min Max
well this governor makes use of only min & maximum frequency based on workload... no intermediate frequencies are used.
8: Interactive Governor:
Much like the OnDemand governor, the Interactive governor dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user. This is where the similarities end. Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.
Unlike OnDemand, which you'll recall scales clockspeed in the context of a work queue, Interactive scales the clockspeed over the course of a timer set arbitrarily by the kernel developer. In other words, if an application demands a ramp to maximum clockspeed (by placing 100% load on the CPU), a user can execute another task before the governor starts reducing CPU frequency. This can eliminate the frequency bouncing discussed in the OnDemand section. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. This is another pro-battery life benefit of Interactive.
However, because Interactive is permitted to spend more time at maximum frequency than OnDemand (for device performance reasons), the battery-saving benefits discussed above are effectively negated. Long story short, Interactive offers better performance than OnDemand (some say the best performance of any governor) and negligibly different battery life.
Interactive also makes the assumption that a user turning the screen on will shortly be followed by the user interacting with some application on their device. Because of this, screen on triggers a ramp to maximum clockspeed, followed by the timer behavior described above.
9: InteractiveX Governor:
Created by kernel developer "Imoseyon," the InteractiveX governor is based heavily on the Interactive governor, enhanced with tuned timer parameters to better balance battery vs. performance. The InteractiveX governor's defining feature, however, is that it locks the CPU frequency to the user's lowest defined speed when the screen is off.
10: Smartass
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!"
11: SmartassV2:
Version 2 of the original smartass governor from Erasmux. Another favorite for many a people. The governor aim for an "ideal frequency", and ramp up more aggressively towards this freq and less aggressive after. It uses different ideal frequencies for screen on and screen off, namely awake_ideal_freq and sleep_ideal_freq. This governor scales down CPU very fast (to hit sleep_ideal_freq soon) while screen is off and scales up rapidly to awake_ideal_freq (500 mhz for GS2 by default) when screen is on. There's no upper limit for frequency while screen is off (unlike Smartass). So the entire frequency range is available for the governor to use during screen-on and screen-off state. The motto of this governor is a balance between performance and battery.
12: Scary
A new governor wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.
13: Lagfree:
Lagfree is similar to ondemand. Main difference is it's optimization to become more battery friendly. Frequency is gracefully decreased and increased, unlike ondemand which jumps to 100% too often. Lagfree does not skip any frequency step while scaling up or down. Remember that if there's a requirement for sudden burst of power, lagfree can not satisfy that since it has to raise cpu through each higher frequency step from current. Some users report that video playback using lagfree stutters a little.
14: Smoothass:
The same as the Smartass “governor” But MUCH more aggressive & across the board this one has a better battery life that is about a third better than stock KERNEL
15: Brazilianwax:
Similar to smartassV2. More aggressive ramping, so more performance, less battery
16: SavagedZen:
Another smartassV2 based governor. Achieves good balance between performance & battery as compared to brazilianwax.
17: Lazy:
This governor from Ezekeel is basically an ondemand with an additional parameter min_time_state to specify the minimum time CPU stays on a frequency before scaling up/down. The Idea here is to eliminate any instabilities caused by fast frequency switching by ondemand. Lazy governor polls more often than ondemand, but changes frequency only after completing min_time_state on a step overriding sampling interval. Lazy also has a screenoff_maxfreq parameter which when enabled will cause the governor to always select the maximum frequency while the screen is off.
18: Lionheart:
Lionheart is a conservative-based governor which is based on samsung's update3 source.
The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.
19: LionheartX
LionheartX is based on Lionheart but has a few changes on the tunables and features a suspend profile based on Smartass governor.
20: Intellidemand:
Intellidemand aka Intelligent Ondemand from Faux is yet another governor that's based on ondemand. Unlike what some users believe, this governor is not the replacement for OC Daemon (Having different governors for sleep and awake). The original intellidemand behaves differently according to GPU usage. When GPU is really busy (gaming, maps, benchmarking, etc) intellidemand behaves like ondemand. When GPU is 'idling' (or moderately busy), intellidemand limits max frequency to a step depending on frequencies available in your device/kernel for saving battery. This is called browsing mode. We can see some 'traces' of interactive governor here. Frequency scale-up decision is made based on idling time of CPU. Lower idling time (<20%) causes CPU to scale-up from current frequency. Frequency scale-down happens at steps=5% of max frequency. (This parameter is tunable only in conservative, among the popular governors)
To sum up, this is an intelligent ondemand that enters browsing mode to limit max frequency when GPU is idling, and (exits browsing mode) behaves like ondemand when GPU is busy; to deliver performance for gaming and such. Intellidemand does not jump to highest frequency when screen is off.
21: Hotplug Governor:
The Hotplug governor performs very similarly to the OnDemand governor, with the added benefit of being more precise about how it steps down through the kernel's frequency table as the governor measures the user's CPU load. However, the Hotplug governor's defining feature is its ability to turn unused CPU cores off during periods of low CPU utilization. This is known as "hotplugging."
22: BadAss Goveronor:
Badass removes all of this "fast peaking" to the max frequency. On a typical system the cpu won't go above 918Mhz and therefore stay cool and will use less power. To trigger a frequency increase, the system must run a bit @ 918Mhz with high load, then the frequency is bumped to 1188Mhz. If that is still not enough the governor gives you full throttle. (this transition should not take longer than 1-2 seconds, depending on the load your system is experiencing)
Badass will also take the gpu load into consideration. If the gpu is moderately busy it will bypass the above check and clock the cpu with 1188Mhz. If the gpu is crushed under load, badass will lift the restrictions to the cpu.
23: Wheatley:
Building on the classic 'ondemand' governor is implemented Wheatley governor. The governor has two additional parameters:
target_residency - The minimum average residency in µs which is considered acceptable for a proper efficient usage of the C4 state. Default is 10000 = 10ms.
allowed_misses - The number sampling intervals in a row the average residency is allowed to be lower than target_residency before the governor reduces the frequency. This ensures that the governor is not too aggressive in scaling down the frequency and reduces it just because some background process was temporarily causing a larger number of wakeups. The default is 5.
Wheatley works as planned and does not hinder the proper C4 usage for task where the C4 can be used properly .
For internet browsing the time spend in C4 has increased by 10% points and the average residency has increased by about 1ms. I guess these differences are mostly due to the different browsing behaviour (I spend the last time more multi-tabbing). But at least we can say that Wheatley does not interfere with the proper use of the C4 state during 'light' tasks. For music playback with screen off the time spend in C4 is practically unchanged, however the average residency is reduced from around 30ms to around 18ms, but this is still more than acceptable.
So the results show that Wheatley works as intended and ensures that the C4 state is used whenever the task allows a proper efficient usage of the C4 state. For more demanding tasks which cause a large number of wakeups and prevent the efficient usage of the C4 state, the governor resorts to the next best power saving mechanism and scales down the frequency. So with the new highly-flexible Wheatley governor one can have the best of both worlds.
Obviously, this governor is only available on multi-core devices.
24:Lulzactive:
Lulzactive:
This new find from Tegrak is based on Interactive & Smartass governors and is one of the favorites.
Old Version: When workload is greater than or equal to 60%, the governor scales up CPU to next higher step. When workload is less than 60%, governor scales down CPU to next lower step. When screen is off, frequency is locked to global scaling minimum frequency.
New Version: Three more user configurable parameters: inc_cpu_load, pump_up_step, pump_down_step. Unlike older version, this one gives more control for the user. We can set the threshold at which governor decides to scale up/down. We can also set number of frequency steps to be skipped while polling up and down.
When workload greater than or equal to inc_cpu_load, governor scales CPU pump_up_step steps up. When workload is less than inc_cpu_load, governor scales CPU down pump_down_step steps down.
Example:
Consider
inc_cpu_load=70
pump_up_step=2
pump_down_step=1
If current frequency=200, Every up_sampling_time Us if cpu load >= 70%, cpu is scaled up 2 steps - to 800.
If current frequency =1200, Every down_sampling_time Us if cpu load < 70%, cpu is scaled down 1 step - to 1000.
25: Pegasusq/Pegasusd
The Pegasus-q / d is a multi-core based on the Ondemand governor and governor with integrated hot-plugging.
Ongoing processes in the queue, we know that multiple processes can run simultaneously on. These processes are active in an array, which is a field called "Run Queue" queue that is ongoing, with their priority values arranged (priority will be used by the task scheduler, which then decides which process to run next).
To ensure that each process has its fair share of resources, each running for a certain period and will eventually stop and then again placed in the queue until it is your turn again. If a program is terminated, so that others can run the program with the highest priority in the current queue is executed.
26: Hotplugx
It 'a Hotplug modified and optimized for the suspension in off-screen
27: AbissPlug
It 'a Governor derived hotplug, it works the same way, but with the changes in savings for a better battery.
28: MSM DCVS
a very efficient and wide range of Dynamic Clock and
Voltage Scaling (DCVS) which addresses usage models from
active standby to mid and high level processing requirements.
A Krait CPU can smoothly scale from low power, low
leakage mode to blazingly fast performance.
Believe it's a governor that is mfg'd by qualcomm to utilize new on chip features.
MSM is the prefix for the SOC (MSM8960) and DCVS is Dynamic Clock and Voltage Scaling. Makes sense, MSM-DCVS
29: IntelliActive
Based off Google's Interactive governor with the following enhancements:
1. self-boost capability from input drivers (no need for PowerHAL assist)
2. two phase scheduling (idle/busy phases to prevent from jumping directly to max freq
3. Checks for offline cpus and short circuits some unnecessary checks to improve code execution paths
30: Adaptive
This driver adds a dynamic cpufreq policy governor
designed for latency-sensitive workloads and also for demanding
performance.
This governor attempts to reduce the latency of clock
increases so that the system is more responsive to
interactive workloads in loweset steady-state but to
to reduce power consumption in middle operation level level up
will be done in step by step to prohibit system from going to
max operation level.
31:Nightmare
A PegasusQ modified, less aggressive and more stable. A good compromise between performance and battery.
In addition to the SoD is a prevention because it usually does not hotplug.
32: ZZmove
ZZmove Governor optimized for low power consumption with the screen off, with particular attention to the limitation of consumption applications in the background with the screen off, such as listening to music. It has three settings: battery saver, balanced and performance. In addition to a performance boost, there is also the governor zzmove optimized.
Credits goes to:
http://icrontic.com/discussion/95140...m-tuner-tegrak
http://forum.xda-developers.com/show....php?t=1369817
20 and 21 seem to be the best choice cause it saves batery but doesnt compromise performance when its needed. What do you think? And even a better question whitch one do you use?
Sent from my Xperia S
king-dano said:
20 and 21 seem to be the best choice cause it saves batery but doesnt compromise performance when its needed. What do you think? And even a better question whitch one do you use?
Sent from my Xperia S
Click to expand...
Click to collapse
I often use intellidemand, excellent battery life and good performance
Nice guide.
For my Galaxy Note, I am using abyssplug governor. It is derived from Hot plug.
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
stempox said:
I often use intellidemand, excellent battery life and good performance
Click to expand...
Click to collapse
Thanks !
Very nice guide!
Good guilde. I am using SmartassV2 on my galaxy r.
What about Lulzactive and pegasusq ?
thanks .. I hope that many of you may be a useful guide
if you want, as governor scivete used and why,
so we will have evidence of actual use
coming soon new governors
thread updated
Really good work!!
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
thanks, I'm glad it's useful for you
Thanks, for the next week, renewal of the thread
Very useful thanks
Thanks to you guys
Smartassv2 is the best that I have used.
itisbasi said:
Smartassv2 is the best that I have used.
Click to expand...
Click to collapse
Also here, with nexus s use mainly smartassv2
24:Lulzactive added
This is not my work, i adjusted a bit (take several Governor out) for Sensation, so all credits go to droidphile.
i will myself accept THANKS
Explanation of Different Governors
1. GOVERNORS
These are the 9 governors we're talking about.
1) Ondemand
2) Ondemandx
3) Conservative
4) Interactive
5) SmartassV2
6) Intellidemand:
7) Lagfree
8) Userspacce
9) Performance
1) Ondemand:
Default governor in almost all stock kernels. One main goal of the ondemand governor is to switch to max frequency as soon as there is a CPU activity detected to ensure the responsiveness of the system. (You can change this behavior using smooth scaling parameters, refer Siyah tweaks at the end of 3rd post.) Effectively, it uses the CPU busy time as the answer to "how critical is performance right now" question. So Ondemand jumps to maximum frequency when CPU is busy and decreases the frequency gradually when CPU is less loaded/apporaching idle. Even though many of us consider this a reliable governor, it falls short on battery saving and performance on default settings. One potential reason for ondemand governor being not very power efficient is that the governor decide the next target frequency by instant requirement during sampling interval. The instant requirement can response quickly to workload change, but it does not usually reflect workload real CPU usage requirement in a small longer time and it possibly causes frequently change between highest and lowest frequency.
2) Ondemandx:
Basically an ondemand with suspend/wake profiles. This governor is supposed to be a battery friendly ondemand. When screen is off, max frequency is capped at 500 mhz. Even though ondemand is the default governor in many kernel and is considered safe/stable, the support for ondemand/ondemandX depends on CPU capability to do fast frequency switching which are very low latency frequency transitions. I have read somewhere that the performance of ondemand/ondemandx were significantly varying for different i/o schedulers. This is not true for most of the other governors. I personally feel ondemand/ondemandx goes best with SIO I/O scheduler.
3) Conservative:
A slower Ondemand which scales up slowly to save battery. The conservative governor is based on the ondemand governor. It functions like the Ondemand governor by dynamically adjusting frequencies based on processor utilization. However, the conservative governor increases and decreases CPU speed more gradually. Simply put, this governor increases the frequency step by step on CPU load and jumps to lowest frequency on CPU idle. Conservative governor aims to dynamically adjust the CPU frequency to current utilization, without jumping to max frequency. The sampling_down_factor value acts as a negative multiplier of sampling_rate to reduce the frequency that the scheduler samples the CPU utilization. For example, if sampling_rate equal to 20,000 and sampling_down_factor is 2, the governor samples the CPU utilization every 40,000 microseconds.
4) Interactive:
Can be considered a faster ondemand. So more snappier, less battery. Interactive is designed for latency-sensitive, interactive workloads. Instead of sampling at every interval like ondemand, it determines how to scale up when CPU comes out of idle. The governor has the following advantages: 1) More consistent ramping, because existing governors do their CPU load sampling in a workqueue context, but interactive governor does this in a timer context, which gives more consistent CPU load sampling. 2) Higher priority for CPU frequency increase, thus giving the remaining tasks the CPU performance benefit, unlike existing governors which schedule ramp-up work to occur after your performance starved tasks have completed. Interactive It's an intelligent Ondemand because of stability optimizations. Why??
Sampling the CPU load every X ms (like Ondemand) can lead to under-powering the CPU for X ms, leading to dropped frames, stuttering UI, etc. Instead of sampling the CPU at a specified rate, the interactive governor will check whether to scale the CPU frequency up soon after coming out of idle. When the CPU comes out of idle, a timer is configured to fire within 1-2 ticks. If the CPU is very busy between exiting idle and when the timer fires, then we assume the CPU is underpowered and ramp to max frequency.
5) SmartassV2:
Version 2 of the original smartass governor from Erasmux. Another favorite for many a people. The governor aim for an "ideal frequency", and ramp up more aggressively towards this freq and less aggressive after. It uses different ideal frequencies for screen on and screen off, namely awake_ideal_freq and sleep_ideal_freq. This governor scales down CPU very fast (to hit sleep_ideal_freq soon) while screen is off and scales up rapidly to awake_ideal_freq (500 mhz for GS2 by default) when screen is on. There's no upper limit for frequency while screen is off (unlike Smartass). So the entire frequency range is available for the governor to use during screen-on and screen-off state. The motto of this governor is a balance between performance and battery.
6) Intellidemand:
Intellidemand aka Intelligent Ondemand from Faux is yet another governor that's based on ondemand. Unlike what some users believe, this governor is not the replacement for OC Daemon (Having different governors for sleep and awake). The original intellidemand behaves differently according to GPU usage. When GPU is really busy (gaming, maps, benchmarking, etc) intellidemand behaves like ondemand. When GPU is 'idling' (or moderately busy), intellidemand limits max frequency to a step depending on frequencies available in your device/kernel for saving battery. This is called browsing mode. We can see some 'traces' of interactive governor here. Frequency scale-up decision is made based on idling time of CPU. Lower idling time (<20%) causes CPU to scale-up from current frequency. Frequency scale-down happens at steps=5% of max frequency. (This parameter is tunable only in conservative, among the popular governors )
To sum up, this is an intelligent ondemand that enters browsing mode to limit max frequency when GPU is idling, and (exits browsing mode) behaves like ondemand when GPU is busy; to deliver performance for gaming and such. Intellidemand does not jump to highest frequency when screen is off.
7) Lagfree:
Lagfree is similar to ondemand. Main difference is it's optimization to become more battery friendly. Frequency is gracefully decreased and increased, unlike ondemand which jumps to 100% too often. Lagfree does not skip any frequency step while scaling up or down. Remember that if there's a requirement for sudden burst of power, lagfree can not satisfy that since it has to raise cpu through each higher frequency step from current. Some users report that video playback using lagfree stutters a little.
8) Userspace:
Instead of automatically determining frequencies, lets user set frequencies.
9) Performance:
Sets min frequency as max frequency. Use this while benchmarking!
So, Governors can be categorized into 3/4 on a high level:
1.a) Ondemand Based:
Works on "ramp-up on high load" principle. CPU busy-time is taken into consideration for scaling decisions. Members: Ondemand, OndemandX, Intellidemand, Lagfree.
1.b) Conservative Based:
Members: Conservative,
2) Interactive Based:
Works on "make scaling decision when CPU comes out of idle-loop" principle. Members: Interactive, InteractiveX, Smartass, SmartassV2,
3) Weird Category:
Members: Userspace, Performance.
__________________________________________________ __________________________________________________ ____________
II) QUESTION TIME
Q. "Ok. Enough of explanations. Tell me which governor is for performance and which one is for battery life."
A. Tough question! smartassV2 for a balance between performance and battery. For light weight tasks. To get maximum performance, use a tweaked ondemand or conservative, but never complain about battery. NOTE: If you don't know how exactly to do it, stay away from it or you will end up complaining about battery drain!
Q. "Hey, almost forgot. How do i change governors?"
A. Best way is to use apps such as system tuner,android tuner,kernel tuner etc.
Q. "How do i know which governor is best for me?"
A. It depends on what you need and your daily usage pattern. Performance or battery. Better choose a governor that's balanced for battery/performance. Or tweak a governor to give performance an upper-hand as compared to battery. We can always re-charge the phone: In car when off to work, or overnight. But we can not recharge performance!
Q. "I can feel slight lags here and there with a governor. For ex: while scrolling through app drawer/vertically scrolling browser, etc. I really love this governor and don't tell me to use another governor. Can i diminish this lag?"
A. Hmm well, you can. Basically what we have to do is make the governor "poll" less often to scale-down cpu. Increase down-sampling-time of your governor (whichever parameter that corresponds to), so that the cpu will stay longer on a frequency before scaling down. This should eliminate the lag.
Q. "Even though i don't have too much uv/oc, once in a while; may be once in two weeks, i experience a freeze/lock/reboot. I'm using governor X. How do i solve this?"
A. Well, a random reboot/freeze once in a while signifies that we're android/ enthusiast. If everything go smooth as silk, what's the fun? We could use stock rom/kernel/governor and be happy. A rare reboot or freeze is nothing to worry about. Just restart the phone.
Q. "OK. I want to tweak these governors according to my usage pattern, because i'm not happy with the default behavior of these governors".
A. You can tweak the governors using an init.d script to echo suitable values into:
/sys/devices/system/cpu/cpufreq/name-of-active-governor/name-of-the-paramater-to-tweak
screen-on will not drain too much battery like you think!
HIT THE THANKS IF THIS INFORMATION WAS HELPFULL
{
"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"
}
Ultimate battery guide
Battery, one of the most important thing on todays phones. Even if we have awesome battery life we always want more and it is never enough.
This is the small guide to tips, trick and tweaks to improve battery life.
This topic is to share tips and tricks and basically just small talk about battery and sharing screenshots.
Use Gsam or Android battery history to show your battery life.
Our goal is to make most of the screen on time with average use of 24 hours. So lets start.
Post 1: Tips
Post 2: ROMS, kernels, undervolting, underclocking
Tips to improve battery life
Location services
One of the first thing that your device will ask when you are setting up your phone. Most of the users let them ON and just forgot about them. Location services are battery hungry and the will drain your battery like you drinking juice.
Thing is that you do not need them always, just sometimes. Turn it OFF then. I have them turned off always and when I need it I just simple turn it ON.
Wi-Fi
Wi-Fi scanning is thing that will drain your battery always. When you are out and you are not expecting to use wi-fi any time soon turn it off. You do not need to run scanning all the time.
You could also edit build.prop to reduce.
Edit wifi.supplicant_scan_interval. Default value is 180. You can set it higher to reduce the scanning intervals.
Signal strength / Network mode
Signal strength is always trouble for battery. Weak signal will drain more battery. Also, constant changing between 4G/3G and 2G will drain battery faster.
Tweak to this is to set your phone to only use 2G, 3G or 4G.
Example: when I am not using my phone, or it is connected to wifi my network is on 2G. I dont need 3G or 4G then and changing network state is disabled then because it will stay always on 2G. I found it has positive effect on battery.
When I need, I just simple toggle 3G or 4G.
Screen brightness
Screen is the thing that drains most of our battery. There is not much philosophy here. Higher brightness will drain more battery.
My personal setup is that I do not use auto brightness. I always change brightness manually. Right now during winter my brightness does not go more then 25% outside, and inside it is lower. At night it is under 10%.
I found that not using auto brightness has also slight positive effect on battery.
Syncing / Airplane mode / Vibration / Animations / Task Killers
Lets start in order.
Syncing: more syncing your device does it drains more battery. On your phone probably you do not to sync all accounts and apps you have every few minutes or hours. Set those apps you do not need on manual sync.
Airplane mode: I am using airplane mode during night because I do not want to be disturbed during sleep. With airplane mode battery consumption during night is 0%. Yes, zero percent.
Vibration: more your device vibrates, more battery it drains. You can reduce vibrations on keyboard settings and similar. I found that is not much effect on battery but it has slight.
Animations: animations drains your battery also and who really needs them. Personally, I am annoyed with them and I always switch them to 0 or .5. You can do that in Settings-Developers options
Task Killers: task killers, clean maters and similar software is a big NO. You dont need it. It does more damage then good.
Bloatware
Yes, bloatware. There is huge amount of bloatware on our phones and we really do not need it. So, what to do? Freeze that bloatware.
You can find list of apps HERE.
ROMS and kernels
Custom ROMs and kernels will give you in most cases better battery life then stock firmware. Plus there is huge amount of options to play with. You can read more in posts bellow.
Summary:
If you change some of those thing you will see the effect.
You can always use apps like Greenify or Tasker and play with their options.
How to follow your battery life
GSam Battery Monitor
This one of the most useful apps to track your battery. On Lollipop (even on Kitkat) it will not give you much useful info without root.
If you are using it without root everytime you reboot the phone statistic would be reset also. If you have root it will give you access to wakelocks and some other stuff, plus stats would not get reseted.
Play store link
Wakelock detector
Wakelocks, one of the painful things on phone. If you see your battery is draining faster in idle then you got problem with wakelocks. This is useful app because it shows wakelocks on very simple setup and you can discover which app is causing which wakelock.
Play Store link
Disable service
If you are using Wakelock detector you need this app also. With this app you can freeze every single process that app can launch. It will provide detail look on all processes from apps. With this app I have reduced wakelocks to 1%.
Play Store link
ROMS
Discussion about ROMs never looked nice. It always gets to what you personally like. Some ROMs will be easier on battery, some will be rough. You will never know before you try them.
Kernels
Kernels are similar to ROMS but you can play with them. Currently there is not much kernels available but you can play even with stock one.
I recommend to use Trickster MOD Kernel Settings app to play with kernel settings.
Undervoting
Undervolting is the thing when you control how much power each CPU frequency can have. Trickster MOD app gives really nice view on them. You can undervolt every frequency by itself or all in one.
My personal recommendation is to undervolt them at once. I always use -50 value. Found it stable.
Of course, you can always play with different values but remember: when you play with this do not click on option "Set on Boot" or you will end in bootloop if you click it. Click that option when you find out that values are safe for using and stable.
Underclocking
Underclocking is changing your CPU frequency. Rough truth is that we dont need our CPU to run on 2,7 GHz in normal use. Only gamers will need that probably but since this is not thread were we are aiming gamers we dont need that high frequency.
Me personally, I use always 1,7 GHz or 1,9 GHz. To my daily usage (most common like everyone else but without games) this is more then enough. Everything is still smooth and runs fast.
Governors
A CPU governor in Android controls how the CPU raises and lowers its frequency in response to the demands the user is placing on their device. Governors are especially important in smartphones and tablets because they have a large impact on the apparent fluidity of the interface and the battery life of the device over a charge.
You can find explanation hidden here.
Many users have wrote about governors and they are practically the same on most of the phones so I will copy list from droidphile.
On his topic you have more details about governors.
Link to original topic: http://forum.xda-developers.com/galaxy-s2/general/ref-kernel-governors-modules-o-t1369817
I) MANUAL:
These are the 19 governors we're talking about.
1) Ondemand
2) Ondemandx
3) Conservative
4) Interactive
5) Interactivex
6) Lulzactive
7) Lulzactiveq
8) Smartass
9) SmartassV2
10) Intellidemand
11) Lazy
12) Lagfree
13) Lionheart
14) LionheartX
15) Brazilianwax
16) SavagedZen
17) Userspacce
18) Powersave
19) Performance
1) Ondemand:
Default governor in almost all stock kernels. One main goal of the ondemand governor is to switch to max frequency as soon as there is a CPU activity detected to ensure the responsiveness of the system. (You can change this behavior using smooth scaling parameters, refer Siyah tweaks at the end of 3rd post.) Effectively, it uses the CPU busy time as the answer to "how critical is performance right now" question. So Ondemand jumps to maximum frequency when CPU is busy and decreases the frequency gradually when CPU is less loaded/apporaching idle. Even though many of us consider this a reliable governor, it falls short on battery saving and performance on default settings. One potential reason for ondemand governor being not very power efficient is that the governor decide the next target frequency by instant requirement during sampling interval. The instant requirement can response quickly to workload change, but it does not usually reflect workload real CPU usage requirement in a small longer time and it possibly causes frequently change between highest and lowest frequency.
2) Ondemandx:
Basically an ondemand with suspend/wake profiles. This governor is supposed to be a battery friendly ondemand. When screen is off, max frequency is capped at 500 mhz. Even though ondemand is the default governor in many kernel and is considered safe/stable, the support for ondemand/ondemandX depends on CPU capability to do fast frequency switching which are very low latency frequency transitions. I have read somewhere that the performance of ondemand/ondemandx were significantly varying for different i/o schedulers. This is not true for most of the other governors. I personally feel ondemand/ondemandx goes best with SIO I/O scheduler.
3) Conservative:
A slower Ondemand which scales up slowly to save battery. The conservative governor is based on the ondemand governor. It functions like the Ondemand governor by dynamically adjusting frequencies based on processor utilization. However, the conservative governor increases and decreases CPU speed more gradually. Simply put, this governor increases the frequency step by step on CPU load and jumps to lowest frequency on CPU idle. Conservative governor aims to dynamically adjust the CPU frequency to current utilization, without jumping to max frequency. The sampling_down_factor value acts as a negative multiplier of sampling_rate to reduce the frequency that the scheduler samples the CPU utilization. For example, if sampling_rate equal to 20,000 and sampling_down_factor is 2, the governor samples the CPU utilization every 40,000 microseconds.
4) Interactive:
Can be considered a faster ondemand. So more snappier, less battery. Interactive is designed for latency-sensitive, interactive workloads. Instead of sampling at every interval like ondemand, it determines how to scale up when CPU comes out of idle. The governor has the following advantages: 1) More consistent ramping, because existing governors do their CPU load sampling in a workqueue context, but interactive governor does this in a timer context, which gives more consistent CPU load sampling. 2) Higher priority for CPU frequency increase, thus giving the remaining tasks the CPU performance benefit, unlike existing governors which schedule ramp-up work to occur after your performance starved tasks have completed. Interactive It's an intelligent Ondemand because of stability optimizations. Why??
Sampling the CPU load every X ms (like Ondemand) can lead to under-powering the CPU for X ms, leading to dropped frames, stuttering UI, etc. Instead of sampling the CPU at a specified rate, the interactive governor will check whether to scale the CPU frequency up soon after coming out of idle. When the CPU comes out of idle, a timer is configured to fire within 1-2 ticks. If the CPU is very busy between exiting idle and when the timer fires, then we assume the CPU is underpowered and ramp to max frequency.
5) Interactivex:
This is an Interactive governor with a wake profile. More battery friendly than interactive.
6) Lulzactive:
This new find from Tegrak is based on Interactive & Smartass governors and is one of the favorites.
Old Version: When workload is greater than or equal to 60%, the governor scales up CPU to next higher step. When workload is less than 60%, governor scales down CPU to next lower step. When screen is off, frequency is locked to global scaling minimum frequency.
New Version: Three more user configurable parameters: inc_cpu_load, pump_up_step, pump_down_step. Unlike older version, this one gives more control for the user. We can set the threshold at which governor decides to scale up/down. We can also set number of frequency steps to be skipped while polling up and down.
When workload greater than or equal to inc_cpu_load, governor scales CPU pump_up_step steps up. When workload is less than inc_cpu_load, governor scales CPU down pump_down_step steps down.
Example:
Consider
inc_cpu_load=70
pump_up_step=2
pump_down_step=1
If current frequency=200, Every up_sampling_time Us if cpu load >= 70%, cpu is scaled up 2 steps - to 800.
If current frequency =1200, Every down_sampling_time Us if cpu load < 70%, cpu is scaled down 1 step - to 1000.
7) Lulzactiveq:
Lulzactiveq is a modified lulzactive governor authored by XDA member robertobsc and is adapted in Siyah kernel for GS2 and GS3. Lulzactiveq aims to optimize the second version of luzactive from Tegrak by a) providing an extra parameter (dec_cpu_load) to make scaling down more sensible, and b) incorporating hotplug logic to the governor. Luzactiveq is the first ever interactive based governor with hotplugging logic inbuilt (atleast the first of its kind for the exynos platform). When CPU comes out of idle loop and it's time to make a scaling decision, if load >= inc_cpu_load CPU is scaled up (like original luzactiveq) and if load <dec_cpu_load, CPU is scaled down. This possibly eliminates the strict single cut-off frequency for luzactiveq to make CPU scaling decisions. Also, stand hotplug logic runs as a separate thread with the governor so that external hotplugging logic is not required to control hotplug in and out (turn On and Off) CPU cores in multi core devices like GS2 or GS3. Only a multi core aware governor makes real sense on muti-core devices. Lulzactiveq and pegasusq aims to do that.
8) Smartass:
Result of Erasmux rewriting the complete code of interactive governor. Main goal is to optimize battery life without comprising performance. Still, not as battery friendly as smartassV2 since screen-on minimum frequency is greater than frequencies used during screen-off. Smartass would jump up to highest frequency too often as well.
9) SmartassV2:
Version 2 of the original smartass governor from Erasmux. Another favorite for many a people. The governor aim for an "ideal frequency", and ramp up more aggressively towards this freq and less aggressive after. It uses different ideal frequencies for screen on and screen off, namely awake_ideal_freq and sleep_ideal_freq. This governor scales down CPU very fast (to hit sleep_ideal_freq soon) while screen is off and scales up rapidly to awake_ideal_freq (500 mhz for GS2 by default) when screen is on. There's no upper limit for frequency while screen is off (unlike Smartass). So the entire frequency range is available for the governor to use during screen-on and screen-off state. The motto of this governor is a balance between performance and battery.
10) Intellidemand:
Intellidemand aka Intelligent Ondemand from Faux is yet another governor that's based on ondemand. Unlike what some users believe, this governor is not the replacement for OC Daemon (Having different governors for sleep and awake). The original intellidemand behaves differently according to GPU usage. When GPU is really busy (gaming, maps, benchmarking, etc) intellidemand behaves like ondemand. When GPU is 'idling' (or moderately busy), intellidemand limits max frequency to a step depending on frequencies available in your device/kernel for saving battery. This is called browsing mode. We can see some 'traces' of interactive governor here. Frequency scale-up decision is made based on idling time of CPU. Lower idling time (<20%) causes CPU to scale-up from current frequency. Frequency scale-down happens at steps=5% of max frequency. (This parameter is tunable only in conservative, among the popular governors )
To sum up, this is an intelligent ondemand that enters browsing mode to limit max frequency when GPU is idling, and (exits browsing mode) behaves like ondemand when GPU is busy; to deliver performance for gaming and such. Intellidemand does not jump to highest frequency when screen is off.
11) Lazy:
This governor from Ezekeel is basically an ondemand with an additional parameter min_time_state to specify the minimum time CPU stays on a frequency before scaling up/down. The Idea here is to eliminate any instabilities caused by fast frequency switching by ondemand. Lazy governor polls more often than ondemand, but changes frequency only after completing min_time_state on a step overriding sampling interval. Lazy also has a screenoff_maxfreq parameter which when enabled will cause the governor to always select the maximum frequency while the screen is off.
12) Lagfree:
Lagfree is similar to ondemand. Main difference is it's optimization to become more battery friendly. Frequency is gracefully decreased and increased, unlike ondemand which jumps to 100% too often. Lagfree does not skip any frequency step while scaling up or down. Remember that if there's a requirement for sudden burst of power, lagfree can not satisfy that since it has to raise cpu through each higher frequency step from current. Some users report that video playback using lagfree stutters a little.
13) Lionheart:
Lionheart is a conservative-based governor which is based on samsung's update3 source. Tweaks comes from 1) Knzo 2) Morfic. The original idea comes from Netarchy. See here. The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.
To 'experience' Lionheart using conservative, try these tweaks:
sampling_rate:10000 or 20000 or 50000, whichever you feel is safer. (transition latency of the CPU is something below 10ms/10,000uS hence using 10,000 might not be safe).
up_threshold:60
down_threshold:30
freq_step:5
Lionheart goes well with deadline i/o scheduler. When it comes to smoothness (not considering battery drain), a tuned conservative delivers more as compared to a tuned ondemand.
14) LionheartX
LionheartX is based on Lionheart but has a few changes on the tunables and features a suspend profile based on Smartass governor.
15) Brazilianwax:
Similar to smartassV2. More aggressive ramping, so more performance, less battery.
16) SavagedZen:
Another smartassV2 based governor. Achieves good balance between performance & battery as compared to brazilianwax.
17) Userspace:
Instead of automatically determining frequencies, lets user set frequencies.
18) Powersave:
Locks max frequency to min frequency. Can not be used as a screen-on or even screen-off (if scaling min frequency is too low).
19) Performance:
Sets min frequency as max frequency. Use this while benchmarking!
Schedulers
Everything has been said about them so I will use droidphile explanations.
Link to original topic: http://forum.xda-developers.com/galaxy-s2/general/ref-kernel-governors-modules-o-t1369817
Q. "What purposes does an i/o scheduler serve?"
A.
Minimize hard disk seek latency.
Prioritize I/O requests from processes.
Allocate disk bandwidth for running processes.
Guarantee that certain requests will be served before a deadline.
So in the simplest of simplest form: Kernel controls the disk access using I/O Scheduler.
Q. "What goals every I/O scheduler tries to balance?"
A.
Fairness (let every process have its share of the access to disk)
Performance (try to serve requests close to current disk head position first, because seeking there is fastest)
Real-time (guarantee that a request is serviced in a given time)
Q. "Description, advantages, disadvantages of each I/O Scheduler?"
A.
1) Noop
Inserts all the incoming I/O requests to a First In First Out queue and implements request merging. Best used with storage devices that does not depend on mechanical movement to access data (yes, like our flash drives). Advantage here is that flash drives does not require reordering of multiple I/O requests unlike in normal hard drives.
Advantages:
Serves I/O requests with least number of cpu cycles. (Battery friendly?)
Best for flash drives since there is no seeking penalty.
Good throughput on db systems.
Disadvantages:
Reduction in number of cpu cycles used is proportional to drop in performance.
2) Deadline
Goal is to minimize I/O latency or starvation of a request. The same is achieved by round robin policy to be fair among multiple I/O requests. Five queues are aggressively used to reorder incoming requests.
Advantages:
Nearly a real time scheduler.
Excels in reducing latency of any given single I/O.
Best scheduler for database access and queries.
Bandwidth requirement of a process - what percentage of CPU it needs, is easily calculated.
Like noop, a good scheduler for solid state/flash drives.
Disadvantages:
When system is overloaded, set of processes that may miss deadline is largely unpredictable.
3) CFQ
Completely Fair Queuing scheduler maintains a scalable per-process I/O queue and attempts to distribute the available I/O bandwidth equally among all I/O requests. Each per-process queue contains synchronous requests from processes. Time slice allocated for each queue depends on the priority of the 'parent' process. V2 of CFQ has some fixes which solves process' i/o starvation and some small backward seeks in the hope of improving responsiveness.
Advantages:
Considered to deliver a balanced i/o performance.
Easiest to tune.
Excels on multiprocessor systems.
Best database system performance after deadline.
Disadvantages:
Some users report media scanning takes longest to complete using CFQ. This could be because of the property that since the bandwidth is equally distributed to all i/o operations during boot-up, media scanning is not given any special priority.
Jitter (worst-case-delay) exhibited can sometimes be high, because of the number of tasks competing for the disk.
4) BFQ
Instead of time slices allocation by CFQ, BFQ assigns budgets. Disk is granted to an active process until it's budget (number of sectors) expires. BFQ assigns high budgets to non-read tasks. Budget assigned to a process varies over time as a function of it's behavior.
Advantages:
Believed to be very good for usb data transfer rate.
Believed to be the best scheduler for HD video recording and video streaming. (because of less jitter as compared to CFQ and others)
Considered an accurate i/o scheduler.
Achieves about 30% more throughput than CFQ on most workloads.
Disadvantages:
Not the best scheduler for benchmarking.
Higher budget assigned to a process can affect interactivity and increased latency.
5) SIO
Simple I/O scheduler aims to keep minimum overhead to achieve low latency to serve I/O requests. No priority quesues concepts, but only basic merging. Sio is a mix between noop & deadline. No reordering or sorting of requests.
Advantages:
Simple, so reliable.
Minimized starvation of requests.
Disadvantages:
Slow random-read speeds on flash drives, compared to other schedulers.
Sequential-read speeds on flash drives also not so good.
6) V(R)
Unlike other schedulers, synchronous and asynchronous requests are not treated separately, instead a deadline is imposed for fairness. The next request to be served is based on it's distance from last request.
Advantages:
May be best for benchmarking because at the peak of it's 'form' VR performs best.
I/O Schedulers
Disadvantages:
Performance fluctuation results in below-average performance at times.
Least reliable/most unstable.
7) Anticipatory
Based on two facts
i) Disk seeks are really slow.
ii) Write operations can happen whenever, but there is always some process waiting for read operation.
So anticipatory prioritize read operations over write. It anticipates synchronous read operations.
Advantages:
Read requests from processes are never starved.
As good as noop for read-performance on flash drives.
Disadvantages:
'Guess works' might not be always reliable.
Reduced write-performance on high performance disks.
reserved
A Mugen 6200 wouldn't hurt either
2SHAYNEZ
---------- Post added at 04:17 PM ---------- Previous post was at 04:14 PM ----------
Also...... Wheatley gov? Not in list.
2SHAYNEZ
shayneflashindaily said:
A Mugen 6200 wouldn't hurt either
2SHAYNEZ
---------- Post added at 04:17 PM ---------- Previous post was at 04:14 PM ----------
Also...... Wheatley gov? Not in list.
2SHAYNEZ
Click to expand...
Click to collapse
Mugen is to big for daily use to me
Will add Wheatley to the list.
Lop but it was a free battery
2SHAYNEZ
Jury duty today meant a lot of screen on time.
shimbob said:
View attachment 3055082
Jury duty today meant a lot of screen on time.
Click to expand...
Click to collapse
so how many hours of screen on time did u get in one charge?
7hours sot
stock phone, stock CM11 12/12. No real tweaks asides stripping out .apks before flashing CM11 and Greenify.
shimbob said:
7hours sot
Click to expand...
Click to collapse
ROM and tweaks ? Extended battery ? More info.
2SHAYNEZ
Well that's kind of cool. 8hrs (of mostly screen off) and 0% battery drain
Nice. I managed to get that during the night also but with airplane mode ON.
I think I have a rogue app eating battery, I only get 2H Screen on time, and it will drain battery without thouching it, I've flashed multiple Roms, I'm going to completely wipe my phone and do a clean install, I remember the first day I got the phone I went all day and still had battery, and that was heavy usage as I was playing with it
SmokeyTech1 said:
I think I have a rogue app eating battery, I only get 2H Screen on time, and it will drain battery without thouching it, I've flashed multiple Roms, I'm going to completely wipe my phone and do a clean install, I remember the first day I got the phone I went all day and still had battery, and that was heavy usage as I was playing with it
Click to expand...
Click to collapse
Maybe you should start all over with flashtooling back to stock. If you can't figure it out.
2SHAYNEZ
shayneflashindaily said:
Maybe you should start all over with flashtooling back to stock. If you can't figure it out.
2SHAYNEZ
Click to expand...
Click to collapse
I installed greenify and snapdragon battery guru, it appears almost all my apps run at startup and stay running, so i hibernated all of them
SmokeyTech1 said:
I installed greenify and snapdragon battery guru, it appears almost all my apps run at startup and stay running, so i hibernated all of them
Click to expand...
Click to collapse
I would avoid snapdragon battery guru, that thing is notoriously bad when it comes to wakelocks. In the end, it probably uses more battery than it saves.
In any case, you need a wakelock detector to pinpoint the source of wakelocks.
4ndroid99 said:
I would avoid snapdragon battery guru, that thing is notoriously bad when it comes to wakelocks. In the end, it probably uses more battery than it saves.
In any case, you need a wakelock detector to pinpoint the source of wakelocks.
Click to expand...
Click to collapse
So after completely wiping my phone and starting over, im sitting here with 13% battery and 2H screen on time, i should add i use a VPN 24/7, and on battery stats the Android OS and Android System use 20% by them selves, so either its something really deep in the phone or my battery is shot
Tuning Battery Life on Samsung Note 3 N900
I don't have a device anymore, but I still wish to share my experience and how I achieved 6 hours SoT with my typical daily usage on this phone.
This guide is for CM12.1 / AICP 10.0 (I recommend latter, it's the same CM 12.1 but with more options).
You can try this settings on aurora/stock ROMs with respective custom kernel (Suemax).
First of all, you need a kernel with Synapse support. This section is for CM12.1/AICP only! Don't try to flash these kernels if you are on Aurora/Stock - you'll have bootloop!
-- Download Stock and DJMax81's V2 kernel from this post and Suemax kernel from this post.
-- Make a backup
-- Flash CM12.1-DJmax81-Kernel-Lite-V2.zip
-- Boot your phone once and open Camera app to ensure it works.
-- Reboot to recovery and flash CM12.1-SueMax-Kernel-V3-By-DJMAX81.zip dirty. No need to wipe cashes.
-- If you encounter issues, restore backup or flash CM12.1-Stock.zip to return to the stock CM12.1 kernel.
Now you can fine-tune your Exynos!
First, disable touchboost. It's some sort of cheating Samsung use to make it's touchwiz not so laggy. On stock Android you simply don't need it, even if you set max CPU to lowly 250 Mhz, Stock Android UX is still decently smooth.
How to do this: open Synapse, go to the QoS tab. There are many, many sliders to control boost in different situations. Slide every one of them to the left. Now you gave full control of your phone freq to the governor.
This setting alone gave me up to 1 hour of SoT when texting or browsing. Because these are not demanding tasks and there's no need for CPU freq to ramp up.
Second, set min GPU speed to 100 MHz. This will save some juice when idle. Go to GPU Control in settings and set the corresponding Min freq slider to 100 MHz, then apply (you need to push the Set GPU settings button and a tick at the right top). You can also adjust Max GPU freq to suit your gaming needs. The more max GPU speed, the better gaming perfomance will be and the worse battery life in games (600 MHz stock value).
Third, let's go to Kernel Adiutor and here are some profiles for you that I found best!
Max Performance profile: Use zzmoove governor, max CPU speed to 1900 MHz, and at advanced governor settings set disable_hotplugging to 1.
Exynos hotplugging has rather negative effect on battery life as I found from my tests, you should never use it. If you are reading this and on Stock/Aurora ROM: disable hotplugging. It makes your battery life worse! Here is the test on Snapdragon 801, on Exynos hotpluging would yield even worse results because CPU with less core active will spend more time on unefficient A15 cores.
Zzmoove is the smoothest and fastest governor I found that still uses all available frequencies wisely.
That's the profile one should use for heavy games (and also set max GPU speed to 720 MHz in Synapse if you need it).
Performance profile: Use Interactive governor and max CPU speed 1900 MHz.
Interactive governor proactively ramps CPU to high (but not highest freq) to ensure great smoothness and still yield not-that-bad battery life (I had usually 4 hours SoT with 2G). For better fine-tuning you can go to advanced governor settings and set hispeed_freq to something in the middle, 800 MHz for example (but not lower than 800). hispeed_freq setting is the intermediate cpu speed which governor uses when there's initial load on cpu.
Balanced profile: Change governor to Ondemand, max CPU speed is still 1900 MHz.
You shouldn't worry, with touchboost disabled it would rarely ramp up to max speed, most often sitting on energy-efficient A7 cores and sometimes ramping to 1200 of A15, going even higher only when needed - still gives you whole power of your device without restrictions. DJMax81 did great job tuning this governor to our needs. You still can set max CPU lower (to 1400 Mhz) if you wish to conserve battery more on this profile.
Power saving profile: Go to Synapse and enable a slight touchboost: on QoS tab set CPU freq touchboost level 1 to 800 MHz (only the first slider). Then in Kernel Adiutor change CPU governor to Interactive. Set Max CPU speed to 1400. Go to advanced governor settings and set hispeed_freq to 400 MHz.
These settings are doing two things:
1. When not in use (e.g. you are not touching your phone), your device will use ONLY energy-efficient A7 cluster. So max 1300 MHz (it shows 650 MHz in Kernel Adiutor because A7 cluster is showing it's real freq divided by 2) with four cores - a performance level of middle-ground MTK device. Most often the phone will use 800 MHz freq of A7 (that's 400 MHz setting of hispeed_freq - a division by 2, remember)
2. When you are using device (actively tapping), touchboost will switch your device to A15 cores (starting from 800 MHz - at this freq they consume roughly same amount of energy as 1300 MHz'd A7) and if needed, interactive governor will ramp the freq even some more - up to 1400 MHz. When there will be no load, freq will drop to the minimum and system will switch to A7 cluster until next time you use it.
Extreme Power Saving profile: Disable touchboost, CPU governor is Interactive. At advanced governor settings set hispeed_freq to 400 MHz.
This makes your phone use ONLY energy-efficient A7 cluster no matter what circumstances. No matter what max CPU freq is set, interactive governor can't switch from A7 cluster to A15 (maybe that's a bug, but we'll use it). You can set max CPU speed to 650 MHz for sure, didn't make a difference for me.
Yes, it may lag. Yes, games are not playable. But we don't paint your screen black and white at least. Movies are fine, texting is fine, browsing too, 1300 MHz of A7 are still quite good - it's like low-end phone but with 3 GB RAM and AMOLED. Combine it with lollipop powersaving mode and GPU powersave bias (set in Synapse, always clocks GPU at 100 MHz). And your phone will go on and on and on...
Don't forget to click thanks button. Tell me your experience. My device is broken so there could be some mistakes. My apologizes. Have a nice day!
First. Thank u sir
Sent from my SM-A9000 using Tapatalk
Dude thank !!!!!!!
Where's Link's My Bro
Send From My N900. Resurrection Mix 5.5.9
hostess79197 said:
Where's Link's My Bro
Send From My N900. Resurrection Mix 5.5.9
Click to expand...
Click to collapse
Kernel Adiutor doesn't make profiles to share. You have to manually set parameters and then save profile for your device. That's only the guide of parameters to use for your needs.
Thanks for sharing.
I'm using TOS (a Chinese rom) now, and I got excellent battery life. The phone is still smooth.
If you're strict with battery life, TOS is really worth trying.
View attachment 3777633
View attachment 3777634
View attachment 3777635
Noyllopa said:
Thanks for sharing.
I'm using TOS (a Chinese rom) now, and I got excellent battery life. The phone is still smooth.
If you're strict with battery life, TOS is really worth trying.
View attachment 3777633
View attachment 3777634
View attachment 3777635
Click to expand...
Click to collapse
wow that battery life looks awesome, where u got the rom?
can u share it?
im still using kitkat rom myself since battery is better than any lollipop rom
ervanthe said:
wow that battery life looks awesome, where u got the rom?
can u share it?
im still using kitkat rom myself since battery is better than any lollipop rom
Click to expand...
Click to collapse
Here’s the download page. http://tos.cn/download/details-4.html
View attachment 3778089
SPEN working. But there‘s no GAPPS, you need to flash it yourself.
looking cool!
Noyllopa said:
Here’s the download page. http://tos.cn/download/details-4.html
View attachment 3778089
SPEN working. But there‘s no GAPPS, you need to flash it yourself.
Click to expand...
Click to collapse
is that rom based on cm or touch wiz? probably cm coz of u mentioned gapps. But spen is working is doubting me that is touchwiz. Also how big is that rom? and is it prerooted?
that battery pics that u showed r awesome!
is it stable to use in everyday?
any lags? and free ram available?
tnx ! cheers!
Anirup =) said:
is that rom based on cm or touch wiz? probably cm coz of u mentioned gapps. But spen is working is doubting me that is touchwiz. Also how big is that rom? and is it prerooted?
that battery pics that u showed r awesome!
is it stable to use in everyday?
any lags? and free ram available?
tnx ! cheers!
Click to expand...
Click to collapse
Based on Touch Wiz. In China google is blocked so there's no gapps.
The rom is already prerooted, you just need to open it in Manage(an app)-Permissons-Root access.
It's 905MB.
Now i'm using it everyday, it's quite stable and smooth. And games (e.g. Hearthstone) are playable.
I don't know how to install Xposed, it errors every time I want to flash it.
As for free ram, I don't know how to check it in this rom.
i want to know that if this kernel works on flyme rom
Sent from my SM-N900 using Tapatalk
Makshow said:
Tuning Battery Life on Samsung Note 3 N900
I don't have a device anymore, but I still wish to share my experience and how I achieved 6 hours SoT with my typical daily usage on this phone.
This guide is for CM12.1 / AICP 10.0 (I recommend latter, it's the same CM 12.1 but with more options).
You can try this settings on aurora/stock ROMs with respective custom kernel (Suemax).
First of all, you need a kernel with Synapse support. This section is for CM12.1/AICP only! Don't try to flash these kernels if you are on Aurora/Stock - you'll have bootloop!
-- Download Stock and DJMax81's V2 kernel from this post and Suemax kernel from this post.
-- Make a backup
-- Flash CM12.1-DJmax81-Kernel-Lite-V2.zip
-- Boot your phone once and open Camera app to ensure it works.
-- Reboot to recovery and flash CM12.1-SueMax-Kernel-V3-By-DJMAX81.zip dirty. No need to wipe cashes.
-- If you encounter issues, restore backup or flash CM12.1-Stock.zip to return to the stock CM12.1 kernel.
Now you can fine-tune your Exynos!
First, disable touchboost. It's some sort of cheating Samsung use to make it's touchwiz not so laggy. On stock Android you simply don't need it, even if you set max CPU to lowly 250 Mhz, Stock Android UX is still decently smooth.
How to do this: open Synapse, go to the QoS tab. There are many, many sliders to control boost in different situations. Slide every one of them to the left. Now you gave full control of your phone freq to the governor.
This setting alone gave me up to 1 hour of SoT when texting or browsing. Because these are not demanding tasks and there's no need for CPU freq to ramp up.
Second, set min GPU speed to 100 MHz. This will save some juice when idle. Go to GPU Control in settings and set the corresponding Min freq slider to 100 MHz, then apply (you need to push the Set GPU settings button and a tick at the right top). You can also adjust Max GPU freq to suit your gaming needs. The more max GPU speed, the better gaming perfomance will be and the worse battery life in games (600 MHz stock value).
Third, let's go to Kernel Adiutor and here are some profiles for you that I found best!
Max Performance profile: Use zzmoove governor, max CPU speed to 1900 MHz, and at advanced governor settings set disable_hotplugging to 1.
Exynos hotplugging has rather negative effect on battery life as I found from my tests, you should never use it. If you are reading this and on Stock/Aurora ROM: disable hotplugging. It makes your battery life worse! Here is the test on Snapdragon 801, on Exynos hotpluging would yield even worse results because CPU with less core active will spend more time on unefficient A15 cores.
Zzmoove is the smoothest and fastest governor I found that still uses all available frequencies wisely.
That's the profile one should use for heavy games (and also set max GPU speed to 720 MHz in Synapse if you need it).
Performance profile: Use Interactive governor and max CPU speed 1900 MHz.
Interactive governor proactively ramps CPU to high (but not highest freq) to ensure great smoothness and still yield not-that-bad battery life (I had usually 4 hours SoT with 2G). For better fine-tuning you can go to advanced governor settings and set hispeed_freq to something in the middle, 800 MHz for example (but not lower than 800). hispeed_freq setting is the intermediate cpu speed which governor uses when there's initial load on cpu.
Balanced profile: Change governor to Ondemand, max CPU speed is still 1900 MHz.
You shouldn't worry, with touchboost disabled it would rarely ramp up to max speed, most often sitting on energy-efficient A7 cores and sometimes ramping to 1200 of A15, going even higher only when needed - still gives you whole power of your device without restrictions. DJMax81 did great job tuning this governor to our needs. You still can set max CPU lower (to 1400 Mhz) if you wish to conserve battery more on this profile.
Power saving profile: Go to Synapse and enable a slight touchboost: on QoS tab set CPU freq touchboost level 1 to 800 MHz (only the first slider). Then in Kernel Adiutor change CPU governor to Interactive. Set Max CPU speed to 1400. Go to advanced governor settings and set hispeed_freq to 400 MHz.
These settings are doing two things:
1. When not in use (e.g. you are not touching your phone), your device will use ONLY energy-efficient A7 cluster. So max 1300 MHz (it shows 650 MHz in Kernel Adiutor because A7 cluster is showing it's real freq divided by 2) with four cores - a performance level of middle-ground MTK device. Most often the phone will use 800 MHz freq of A7 (that's 400 MHz setting of hispeed_freq - a division by 2, remember)
2. When you are using device (actively tapping), touchboost will switch your device to A15 cores (starting from 800 MHz - at this freq they consume roughly same amount of energy as 1300 MHz'd A7) and if needed, interactive governor will ramp the freq even some more - up to 1400 MHz. When there will be no load, freq will drop to the minimum and system will switch to A7 cluster until next time you use it.
Extreme Power Saving profile: Disable touchboost, CPU governor is Interactive. At advanced governor settings set hispeed_freq to 400 MHz.
This makes your phone use ONLY energy-efficient A7 cluster no matter what circumstances. No matter what max CPU freq is set, interactive governor can't switch from A7 cluster to A15 (maybe that's a bug, but we'll use it). You can set max CPU speed to 650 MHz for sure, didn't make a difference for me.
Yes, it may lag. Yes, games are not playable. But we don't paint your screen black and white at least. Movies are fine, texting is fine, browsing too, 1300 MHz of A7 are still quite good - it's like low-end phone but with 3 GB RAM and AMOLED. Combine it with lollipop powersaving mode and GPU powersave bias (set in Synapse, always clocks GPU at 100 MHz). And your phone will go on and on and on...
Don't forget to click thanks button. Tell me your experience. My device is broken so there could be some mistakes. My apologizes. Have a nice day!
Click to expand...
Click to collapse
Hello sir.... I am using sumax v3 karnel with the settings you have mentioned in the thread. Everything is fine... Battery life is great... No problem of heating... Speed is ok but i have facing a problem.... MY PHONE FREEZES RANDOMLY ANY SOLUTION PLEASE HELP. IT FREEZES WHEN SCREEN IS OFF AND I HAVE TO RESTART MY PHONE. I AM USING CYANOGENMOD 12.1. PROBLEM OCCURS ONLY WHEN I USE SUMMAX KARNEL AND PRESCRIBED SETTINGS.
set cpu gov ondemand because its hard to wake up cores on extreme low freq when on sleep mode
Sent from my SM-N900 using Tapatalk 2
Makshow said:
Tuning Battery Life on Samsung Note 3 N900
I don't have a device anymore, but I still wish to share my experience and how I achieved 6 hours SoT with my typical daily usage on this phone.
This guide is for CM12.1 / AICP 10.0 (I recommend latter, it's the same CM 12.1 but with more options).
You can try this settings on aurora/stock ROMs with respective custom kernel (Suemax).
First of all, you need a kernel with Synapse support. This section is for CM12.1/AICP only! Don't try to flash these kernels if you are on Aurora/Stock - you'll have bootloop!
-- Download Stock and DJMax81's V2 kernel from this post and Suemax kernel from this post.
-- Make a backup
-- Flash CM12.1-DJmax81-Kernel-Lite-V2.zip
-- Boot your phone once and open Camera app to ensure it works.
-- Reboot to recovery and flash CM12.1-SueMax-Kernel-V3-By-DJMAX81.zip dirty. No need to wipe cashes.
-- If you encounter issues, restore backup or flash CM12.1-Stock.zip to return to the stock CM12.1 kernel.
Now you can fine-tune your Exynos!
First, disable touchboost. It's some sort of cheating Samsung use to make it's touchwiz not so laggy. On stock Android you simply don't need it, even if you set max CPU to lowly 250 Mhz, Stock Android UX is still decently smooth.
How to do this: open Synapse, go to the QoS tab. There are many, many sliders to control boost in different situations. Slide every one of them to the left. Now you gave full control of your phone freq to the governor.
This setting alone gave me up to 1 hour of SoT when texting or browsing. Because these are not demanding tasks and there's no need for CPU freq to ramp up.
Second, set min GPU speed to 100 MHz. This will save some juice when idle. Go to GPU Control in settings and set the corresponding Min freq slider to 100 MHz, then apply (you need to push the Set GPU settings button and a tick at the right top). You can also adjust Max GPU freq to suit your gaming needs. The more max GPU speed, the better gaming perfomance will be and the worse battery life in games (600 MHz stock value).
Third, let's go to Kernel Adiutor and here are some profiles for you that I found best!
Max Performance profile: Use zzmoove governor, max CPU speed to 1900 MHz, and at advanced governor settings set disable_hotplugging to 1.
Exynos hotplugging has rather negative effect on battery life as I found from my tests, you should never use it. If you are reading this and on Stock/Aurora ROM: disable hotplugging. It makes your battery life worse! Here is the test on Snapdragon 801, on Exynos hotpluging would yield even worse results because CPU with less core active will spend more time on unefficient A15 cores.
Zzmoove is the smoothest and fastest governor I found that still uses all available frequencies wisely.
That's the profile one should use for heavy games (and also set max GPU speed to 720 MHz in Synapse if you need it).
Performance profile: Use Interactive governor and max CPU speed 1900 MHz.
Interactive governor proactively ramps CPU to high (but not highest freq) to ensure great smoothness and still yield not-that-bad battery life (I had usually 4 hours SoT with 2G). For better fine-tuning you can go to advanced governor settings and set hispeed_freq to something in the middle, 800 MHz for example (but not lower than 800). hispeed_freq setting is the intermediate cpu speed which governor uses when there's initial load on cpu.
Balanced profile: Change governor to Ondemand, max CPU speed is still 1900 MHz.
You shouldn't worry, with touchboost disabled it would rarely ramp up to max speed, most often sitting on energy-efficient A7 cores and sometimes ramping to 1200 of A15, going even higher only when needed - still gives you whole power of your device without restrictions. DJMax81 did great job tuning this governor to our needs. You still can set max CPU lower (to 1400 Mhz) if you wish to conserve battery more on this profile.
Power saving profile: Go to Synapse and enable a slight touchboost: on QoS tab set CPU freq touchboost level 1 to 800 MHz (only the first slider). Then in Kernel Adiutor change CPU governor to Interactive. Set Max CPU speed to 1400. Go to advanced governor settings and set hispeed_freq to 400 MHz.
These settings are doing two things:
1. When not in use (e.g. you are not touching your phone), your device will use ONLY energy-efficient A7 cluster. So max 1300 MHz (it shows 650 MHz in Kernel Adiutor because A7 cluster is showing it's real freq divided by 2) with four cores - a performance level of middle-ground MTK device. Most often the phone will use 800 MHz freq of A7 (that's 400 MHz setting of hispeed_freq - a division by 2, remember)
2. When you are using device (actively tapping), touchboost will switch your device to A15 cores (starting from 800 MHz - at this freq they consume roughly same amount of energy as 1300 MHz'd A7) and if needed, interactive governor will ramp the freq even some more - up to 1400 MHz. When there will be no load, freq will drop to the minimum and system will switch to A7 cluster until next time you use it.
Extreme Power Saving profile: Disable touchboost, CPU governor is Interactive. At advanced governor settings set hispeed_freq to 400 MHz.
This makes your phone use ONLY energy-efficient A7 cluster no matter what circumstances. No matter what max CPU freq is set, interactive governor can't switch from A7 cluster to A15 (maybe that's a bug, but we'll use it). You can set max CPU speed to 650 MHz for sure, didn't make a difference for me.
Yes, it may lag. Yes, games are not playable. But we don't paint your screen black and white at least. Movies are fine, texting is fine, browsing too, 1300 MHz of A7 are still quite good - it's like low-end phone but with 3 GB RAM and AMOLED. Combine it with lollipop powersaving mode and GPU powersave bias (set in Synapse, always clocks GPU at 100 MHz). And your phone will go on and on and on...
Don't forget to click thanks button. Tell me your experience. My device is broken so there could be some mistakes. My apologizes. Have a nice day!
Click to expand...
Click to collapse
Hello Where can I go to see the "Kernel Adiutor" whether I need to install it from PlayStore?
SAINI99 said:
set cpu gov ondemand because its hard to wake up cores on extreme low freq when on sleep mode
Sent from my SM-N900 using Tapatalk 2
Click to expand...
Click to collapse
Sir i have been already using ondemand governor but problem priciest i reflashed the rom and usesed with stock karnel for 2 days phone didn't freeze with stok karnel but as i flashed the karnel and set the given values it started freezing again... I want to use the karnel because everything is better than the stock one heating issue is major one with the rom but can be solved by the karnel but how to get rid of freezing problem.
Balraj77712 said:
Hello sir.... I am using sumax v3 karnel with the settings you have mentioned in the thread. Everything is fine... Battery life is great... No problem of heating... Speed is ok but i have facing a problem.... MY PHONE FREEZES RANDOMLY ANY SOLUTION PLEASE HELP. IT FREEZES WHEN SCREEN IS OFF AND I HAVE TO RESTART MY PHONE. I AM USING CYANOGENMOD 12.1. PROBLEM OCCURS ONLY WHEN I USE SUMMAX KARNEL AND PRESCRIBED SETTINGS.
Click to expand...
Click to collapse
Try to increase voltage slightly, +25 mV should be fine. Kernel Adiutor - CPU Voltage - Global at right top. It will not make any effect to battery life. If I remember correctly, Suemax kernel is a bit undervolted by default and if on most phones it's fine, on some it can make issues.
premryp007 said:
Hello Where can I go to see the "Kernel Adiutor" whether I need to install it from PlayStore?
Click to expand...
Click to collapse
You can install it from Play Store, if you don't have one. On my ROM it was just built-in. Synapse should be built-in in kernel, you can update it from Play Store as usual.
Makshow said:
Try to increase voltage slightly, +25 mV should be fine. Kernel Adiutor - CPU Voltage - Global at right top. It will not make any effect to battery life. If I remember correctly, Suemax kernel is a bit undervolted by default and if on most phones it's fine, on some it can make issues.
Sir i have set cpu voltage +25 the problem have been solved by doing so but some time cpu voltage automatically increased and phone start lagging and freezing... Any solution sir.. Thanks in advance.
Click to expand...
Click to collapse
Balraj77712 said:
Sir i have set cpu voltage +25 the problem have been solved by doing so but some time cpu voltage automatically increased and phone start lagging and freezing... Any solution sir.. Thanks in advance.
Click to expand...
Click to collapse
Hmm, can you tell some more about this? I don't even have a clue, how the voltage can be increased automatically and phone start to lagging from more voltage? Usually, it's the contrary: more voltage = more stability for overclock etc.
Makshow said:
Hmm, can you tell some more about this? I don't even have a clue, how the voltage can be increased automatically and phone start to lagging from more voltage? Usually, it's the contrary: more voltage = more stability for overclock etc.
Click to expand...
Click to collapse
Sir i set the cpu voltage by +25. Phone didn't freeze but after a day it freezed again when i checked the cpu voltage after restarting the phone it was the default values i set it by +25 again. After 7-8 hours some apps like Es file Explorer, Whats app, uc browser stopped working (saying like whats app is not responding) i was unable to move some content from phone to sd card. Other functions like settings, dialer etc. Was working. Phone didn't connect to pc. Neither restarted nor power off (restarting and shutting down.) after restarting the cpu voltage was more then the default values. See screenshots sir
Balraj77712 said:
Sir i set the cpu voltage by +25. Phone didn't freeze but after a day it freezed again when i checked the cpu voltage after restarting the phone it was the default values i set it by +25 again. After 7-8 hours some apps like Es file Explorer, Whats app, uc browser stopped working (saying like whats app is not responding) i was unable to move some content from phone to sd card. Other functions like settings, dialer etc. Was working. Phone didn't connect to pc. Neither restarted nor power off (restarting and shutting down.) after restarting the cpu voltage was more then the default values. See screenshots sir
Click to expand...
Click to collapse
Really strange. What ROM do you use? And build date.