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
I'm using and experimenting around with ARHD now.
Using Sultan's latest kernel.
I am a guy that likes battery a lot. Under what settings will the battery be the most efficient?
I'm using.
MPDecision(or smth) - On
Badass
Balanced
Max -810
SecP - 594(or the closest one to it)
ThirdP - 704(or the closest one to it)
SIO.
Vsync - ON
Fsync - Off(dont know what this really do anyway)
Max aggressive OOM
No Swaps.
-50mv
disabled logcat
If its okay I'd love suggestions to max out battery life.
Or the best efficiency to balance battery life and performance prioritizing on battery life. (at least no lags on UI)
KiD3991 said:
I'm using and experimenting around with ARHD now.
Using Sultan's latest kernel.
I am a guy that likes battery a lot. Under what settings will the battery be the most efficient?
I'm using.
MPDecision(or smth) - On
Badass
Balanced
Max -810
SecP - 594(or the closest one to it)
ThirdP - 704(or the closest one to it)
SIO.
Vsync - ON
Fsync - Off(dont know what this really do anyway)
Max aggressive OOM
No Swaps.
-50mv
disabled logcat
If its okay I'd love suggestions to max out battery life.
Or the best efficiency to balance battery life and performance prioritizing on battery life. (at least no lags on UI)
Click to expand...
Click to collapse
Don't make your OOM settings that aggressive if you want battery life. When you have the OOM set to the most aggressive setting, the phone will use more CPU power and thus battery power in order to clean the RAM. Another problem with OOM settings that aggressive is that applications you use frequently and multitask with will be terminated and when you open them the phone has to open them from scratch all over again, wasting much more power than if the program was still cached in the RAM.
I see. Thanks for the tip. I always thought when OOM is set to maximum, there won't be background apps running so it'll save battery.
If its not too much to ask, what about governor and scheduler combination? Max freq I feel smooth is 910. So I can coup with low freq. With no GPU underclock NFS most wanted still runs smooth so its fine too. I disable Vsync because it felt like its using CPU power to keep the sync on.
KiD3991 said:
I see. Thanks for the tip. I always thought when OOM is set to maximum, there won't be background apps running so it'll save battery.
If its not too much to ask, what about governor and scheduler combination? Max freq I feel smooth is 910. So I can coup with low freq. With no GPU underclock NFS most wanted still runs smooth so its fine too. I disable Vsync because it felt like its using CPU power to keep the sync on.
Click to expand...
Click to collapse
Disabling vsync causes a lot of visual tearing and I'm not sure if doing that saves power
Best I/O scheduler is SIO. As for governor, best for battery is badass. In the next release of my kernel I'll add badass GPU scaling so you can save even more power
Other ways to save power: use PM_MAX instead of PM_FAST and set the 2D GPU frequency to 145MHz.
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.