Ktoonsez presents:
{
"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"
}
KT-NOTE4 kernel features
•Must have a Note 4 model N910T or N910P or N910W8
•Must have a Touchwiz Rooted ROM
•Must have CWM/TWRP based recovery installed
•Samsung open source
•Optimized kernel configuration
•unsecure root adb
•Voltage interface
•KTweaker app for kernel control
•KTweaker Widgets
•Schedulers (CFQ, BFQ, VR, SIO, NOOP, DEADLINE, ROW, FIFO, FIOPS)
•GOVERNORS (ktoonservativeq, intellidemand, msm-dcvs, wheatley, userspace, smartassh3, slp, powersave, pegasuq, nightmare, interactive, dancedance, conservative, badass, asswax, adaptive, abyssplug, performance, ondemand
•exFAT for Touchwiz
Click to expand...
Click to collapse
Touchwiz Kitkat 4.4 VERSION:
11.11.2014: http://goo.gl/IG2O5Q
Click to expand...
Click to collapse
Always do the following AFTER installing the kernel:
1. Clear cache
2. Clear dalvik
Post #2 will be reserved for change logs
Post #3 will be reserved for MY Settings, Extras and FAQ's
Sources can be found here:
https://github.com/ktoonsez/KTNOTE4
Change Log 12.08.2014
1. Added some Profiles to the KTweaker Shop, thanks to @zman2107 for helping out
2. Some tweaks to ktoonservativeq
3. Added Trinity Colors, thanks to @twistedumbrella for porting in the code
4. Added Bluetooth Min Mhz control
5. Added Music/Media Min Mhz control
6. Added bfq scheduler
Change Log 11.13.2014
1. Rebase kernel source on N910F
2. NOW Working on F and G models!!!!!!!!!!!!!!!
3. Make ramdisk universal so its working on all Qualcomm variants
4. Add Fast Charge from my S4/S5 code
5. Increase bandwidth fro OC steps from @twistedumbrella
6. Removed a butt load of dmesg spam
Change Log 11.11.2014
1. Initial release
2. Based on Samsung source from N910T model
3. Added multi compatibility for multiple models
4. Removed root restrictions from kernel
5. Made selinux permissive
6. Added voltage control
7. Added OC to 3072 Mhz
8. Added KThermal
9. Added KT Hotplug
10. Lots more stuff to come!!!!!!!!!!!!!!!!!!!!!!!!
11. Linaro -O3 compiled plus Make file opto's
12. Added bfq scheduler
13. There is lots of stuff in KTweaker not enabled yet so only use the stuff that is listed in this change log!!!
ktoonservativeq explained:
***** NOTES *****
Any item with the word cycle in it refers to how many sampling_rate's have occurred.
Examples:
A "boost_hold_cycles" of 22 and a sampling_rate of 45000 equates to 1 seconds of holding your Mhz at the boost level.
A block_cycles_offline_screen_on of 11 and a sampling_rate of 45000 equates to a half of a second block before it takes cores offline.
***** NOTES *****
block_cycles_offline_screen_off =1
How many sampling_rate cycles need to occur before a core is allowed to go OFFLINE while the screen is OFF.
block_cycles_offline_screen_on = 11
How many sampling_rate cycles need to occur before a core is allowed to go OFFLINE while the screen is ON.
block_cycles_online_screen_off = 11
How many sampling_rate cycles need to occur before a core is allowed to go ONLINE while the screen is OFF.
block_cycles_online_screen_on = 3
How many sampling_rate cycles need to occur before a core is allowed to go ONLINE while the screen is ON.
block_cycles_raise_screen_off = 11
How many sampling_rate cycles need to occur before the current Mhz is allowed to be raised while the screen is OFF.
block_cycles_raise_screen_on = 3
How many sampling_rate cycles need to occur before the current Mhz is allowed to be raised while the screen is ON.
boost_2nd_core_on_button_screen_off = 1
When this item is a 1, it will turn on the 2nd core when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
boost_2nd_core_on_button_screen_on = 1
When this item is a 1, it will turn on the 2nd core when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
boost_3rd_core_on_button_screen_off = 0
When this item is a 1, it will turn on the 3nd core when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
boost_3rd_core_on_button_screen_on = 0
When this item is a 1, it will turn on the 3nd core when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
boost_4th_core_on_button_screen_off = 0
When this item is a 1, it will turn on the 4nd core when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
boost_4th_core_on_button_screen_on = 0
When this item is a 1, it will turn on the 4nd core when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
boost_hold_cycles = 22
How many sampling_rate cycles need to occur before going out of CPU/GPU boost mode
disable_hotplug = 0
When this item is a 1, it disables hotplugging so all cores stay on full time. 0 lets all cores turn on and off when needed.
disable_hotplug_bt = 0
When this item is a 1, it disables hotplugging so all cores stay on full time while paired to a bluetooth device and doing bluetooth activities like playing music, transfering files.... 0 doesn't do anything extra to the cores when doing bluetooth functions.
disable_hotplug_chrg = 0
When this item is a 1, it disables hotplugging so all cores stay on full time while charging the device. 0 doesn't do anything extra to the cores while charging.
disable_hotplug_media = 0
When this item is a 1, it disables hotplugging so all cores stay on full time while playing music or movies. 0 doesn't do anything extra to the cores while music or movies are playing.
down_threshold_screen_off = 52
A percentage of CPU utilization that needs to occur before the current Mhz begins to lower while screen is OFF.
down_threshold_screen_off_hotplug_1 = 35
A percentage of CPU utilization that needs to occur before the 2nd core is taken offline while screen is OFF.
down_threshold_screen_off_hotplug_2 = 45
A percentage of CPU utilization that needs to occur before the 3rd core is taken offline while screen is OFF.
down_threshold_screen_off_hotplug_3 = 55
A percentage of CPU utilization that needs to occur before the 4th core is taken offline while screen is OFF.
down_threshold_screen_on = 52
A percentage of CPU utilization that needs to occur before the current Mhz begins to lower while screen is ON.
down_threshold_screen_on_hotplug_1 = 35
A percentage of CPU utilization that needs to occur before the 2nd core is taken offline while screen is ON.
down_threshold_screen_on_hotplug_2 = 45
A percentage of CPU utilization that needs to occur before the 3rd core is taken offline while screen is ON.
down_threshold_screen_on_hotplug_3 = 55
A percentage of CPU utilization that needs to occur before the 4th core is taken offline while screen is ON.
freq_step_lower_screen_off = 8
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when lowering the current Mhz while the screen is OFF.
freq_step_lower_screen_on = 2
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when lowering the current Mhz while the screen is ON.
freq_step_raise_screen_off = 1
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when raising the current Mhz while the screen is OFF.
freq_step_raise_screen_on = 5
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when raising the current Mhz while the screen is ON.
ignore_nice_load = 0
If this value is "1," the system will ignore "Nice" processes when deciding to scale up or down. Nice processes are used by the IO scheduler to designate a low-priority process. Ignore nice load basically tells a governor to disregard processes with higher nice values.
lockout_2nd_core_hotplug_screen_off = 0
This is a 3 way option. While the screen is OFF, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_2nd_core_hotplug_screen_on = 0
This is a 3 way option. While the screen is ON, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_3rd_core_hotplug_screen_off = 0
This is a 3 way option. While the screen is OFF, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_3rd_core_hotplug_screen_on = 0
This is a 3 way option. While the screen is ON, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_4th_core_hotplug_screen_off = 0
This is a 3 way option. While the screen is OFF, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_4th_core_hotplug_screen_on = 0
This is a 3 way option. While the screen is ON, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
no_extra_cores_screen_off = 1
When set to a 1, this option keeps all extra CPU cores offline while the screen is OFF. 0 lets it hotplug them on and off as needed
sampling_down_factor = 1
NOT USED!
sampling_rate = 45000
The amount of milliseconds that the governor will analyze the CPU usage and adjust for changes in load while the screen is ON.
sampling_rate_min = 10000
READ-ONLY value that specifies the lower value that "sampling_rate" and "sampling_rate_screen_off" will accept.
sampling_rate_screen_off = 45000
The amount of milliseconds that the governor will analyze the CPU usage and adjust for changes in load while the screen is OFF.
super_conservative_screen_off = 0
With the screen OFF: When set to a 1, this option will explicitly obey your block cycles settings to be a super battery saver (Setting a 1 will slow down the UI a little bit). When set to a 0 it uses fuzzy logic on the "block cycle" items.
super_conservative_screen_on = 0
With the screen ON: When set to a 1, this option will explicitly obey your block cycles settings to be a super battery saver (Setting a 1 will slow down the UI a little bit). When set to a 0 it uses fuzzy logic on the "block cycle" items to create a smooooooth UI experience.
sync_extra_cores_screen_off = 0
With the screen OFF: When set to a 1, all online cores will be sync'd to the same speed as core 0. When set to a 0, all cores will operate at speeds independant of each other.
sync_extra_cores_screen_on = 0
With the screen ON: When set to a 1, all online cores will be sync'd to the same speed as core 0. When set to a 0, all cores will operate at speeds independant of each other.
touch_boost_2nd_core = 1
When set to a 1, this option turns on the 2nd core when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_3rd_core = 0
When set to a 1, this option turns on the 3rd core when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_4th_core = 0
When set to a 1, this option turns on the 4th core when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_cpu = 1804800
The Mhz that you want the online CPU's to jump to when the screen is touched.
touch_boost_cpu_all_cores = 0
When set to a 1, this option sets the current Mhz on all online cores to the selected touch_boost_cpu value.
touch_boost_gpu = 462400
This value specifies what Mhz the GPU should jump to when the screen is touched.
up_threshold_screen_off = 57
A percentage of CPU utilization that needs to occur before the current Mhz begins to raise while screen is OFF.
up_threshold_screen_off_hotplug_1 = 58
A percentage of CPU utilization that needs to occur before the 2nd core is put online while screen is OFF.
up_threshold_screen_off_hotplug_2 = 68
A percentage of CPU utilization that needs to occur before the 3rd core is put online while screen is OFF.
up_threshold_screen_off_hotplug_3 = 78
A percentage of CPU utilization that needs to occur before the 4th core is put online while screen is OFF.
up_threshold_screen_on = 57
A percentage of CPU utilization that needs to occur before the current Mhz begins to raise while screen is ON.
up_threshold_screen_on_hotplug_1 = 58
A percentage of CPU utilization that needs to occur before the 2nd core is put online while screen is ON.
up_threshold_screen_on_hotplug_2 = 68
A percentage of CPU utilization that needs to occur before the 3rd core is put online while screen is ON.
up_threshold_screen_on_hotplug_3 = 78
A percentage of CPU utilization that needs to occur before the 4th core is put online while screen is ON.
Other Governors and schedulers explained:
http://forum.xda-developers.com/showthread.php?t=1687578
http://forum.xda-developers.com/showthread.php?t=1369817
http://tinzdroid.blogspot.com/2012/07/android-kernel-governors-modules-io.html
http://forum.xda-developers.com/showpost.php?p=21638852&postcount=56
First
Everybody be sure to give @em0ney14 a big "THANKS" for the countless hours of testing the kernel while I spent countless hours doing the programming
@LuigiBull23
Man am I glad to see you here I was missing you over on the s4 forum! Love being able to rock your kernels from the s2 all the way here
Excellent! Flashing now, thanks for all your hard work throughout the years. I always rock KT whenever possible! :highfive:
Can you post stock kernel just in case .
BAD ASS NOTE 4
BACARDILIMON said:
Can you post stock kernel just in case .
BAD ASS NOTE 4
Click to expand...
Click to collapse
I cant but maybe someone else can, but if you are using somones ROM from the forum, all u have to do is flash the ROM again
re: official stock N910T Note 4 kernel
BACARDILIMON said:
Can you post stock kernel just in case .
BAD ASS NOTE 4
Click to expand...
Click to collapse
Here is a download link for the Tmobile N910T Note 4 stock kernel.
https://app.box.com/s/nj34un45zxdo01ygd1dk
Flash this kernel using Flashify.
Here is the Play Store link for Flashify in case you need it:
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Good luck!
Misterjunky said:
Here is a download link for the Tmobile N910T Note 4 stock kernel.
https://app.box.com/s/nj34un45zxdo01ygd1dk
Flash this kernel using Flashify.
Here is the Play Store link for Flashify in case you need it:
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Good luck!
Click to expand...
Click to collapse
Thanks fir that info mister junky, I also have a flashable for a near stock kernel kt and I was working on as a base if anyone has issues with this release let us know.
Cant seem to get cpu to go past 2649. I have it set with ktweak to 3000 but it stops at 2649
Sent from my SM-N910T using XDA Free mobile app
WOOT WOOT (I never understood why it is WOOT WOOT - versus WHOOO WHOOO - ? I never heard anyone ever go WOOT WOOT and prounce the T when they are really happy - more like WOO HOO - or something along those lines - well regardless The point is the same - and the sentiment is obvious - I am really glad to see you here - and just as glad to see you are brining us a new kernel -
Looking forward to flashing this and getting some ktnoonze kernel goodness on my NOTE 4 - thanks!
PS - who came up with the WOOT - versus the WOO ? Inquiring minds want to know.
Thanks Koontz. Downloading now. Be like the old a Asus tf101 days up in here.
chrisgto4 said:
Cant seem to get cpu to go past 2649. I have it set with ktweak to 3000 but it stops at 2649
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
What app r u using to see what spees its hitting? My KTMonitor app? Are you running a benchmark app to push the CPU?
ktoonsez said:
What app r u using to see what spees its hitting? My KTMonitor app? Are you running a benchmark app to push the CPU?
Click to expand...
Click to collapse
Im using ktmonitor. I tried the most cpu intensive apk i have. Video to gif.....it runs the cpu at avg 75-100% cpu usage. Then changed the governor to performance and set min/max to 3000. Still stayed at 2649. Other than that very impressed with kernel. Nice work
Sent from my SM-N910T using XDA Free mobile app
Man this is awesome.
Sent from my SM-N910T using Tapatalk
chrisgto4 said:
Cant seem to get cpu to go past 2649. I have it set with ktweak to 3000 but it stops at 2649
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Click main settings - CPU Settings - then select - enable OC settings - then set your CPU to what you want to set it to - I did these steps and had no issues.
Some things are not working yet - but I know it is very early in this kernel's life - more good things are sure to be coming soon.
chrisgto4 said:
Im using ktmonitor. I tried the most cpu intensive apk i have. Video to gif.....it runs the cpu at avg 75-100% cpu usage. Then changed the governor to performance and set min/max to 3000. Still stayed at 2649. Other than that very impressed with kernel. Nice work
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Here is a screen shot from em0ney, I know it works;
https://plus.google.com/u/0/photos/...6080647202194515042&oid=116366863869938231344
Related
Here is a great resource where you can learn a lot about the setCPU app and what all the features actually do.
It is very informative and in particular, this is what appealed to me:
"The Advanced menu allows you to tweak the finer aspects of certain CPU governors. It is only activated when you choose the ondemand or conservative governors.
Sampling Rate - An interval (in microseconds) at which the governor will poll for updates. When this happens, the governor will decide whether to scale the CPU up or down.
Up Threshold - Defines a percentage from 1% to 100%. When the CPU load reaches this point, the governor will scale the CPU up.
Down Threshold (conservative only) - Defines a percentage from 1% to 100%. When the CPU load reaches this point, the governor will scale the CPU down.
Ignore Nice Load - If this value is "1," the system will ignore "Nice" processes when deciding to scale up or down.
Powersave Bias (ondemand only) - Setting this value higher will "bias" the governor toward lower frequencies. This is a percentage, where 1000 is 100%, 100 is 10%, and 0 is 0%. The ondemand governor will scale the CPU to a frequency lower than its "target" speed according to this value.
Freq Step (conservative only) - Defines how much (as a percentage of the maximum CPU speed) the conservative governor will increase the CPU speed by each time the CPU load reaches the Up Threshold.
Choose the "Set on Boot" checkbox to apply advanced settings when the phone boots. This option is completely independent of the similar option in the Main tab."
Thought i would post this to keep people informed.
Also, you can save battery with higher up thresholds ;D
I remember seeing this info at http://setcpu.com link mentioned in the about tab.
Higher up thresholds are not always good. It is better to have processor stay in 1200 state at 50% for 2 seconds compared to staying at 800 for 5 seconds at 100%.
diablo009 said:
I remember seeing this info at http://setcpu.com link mentioned in the about tab.
Higher up thresholds are not always good. It is better to have processor stay in 1200 state at 50% for 2 seconds compared to staying at 800 for 5 seconds at 100%.
Click to expand...
Click to collapse
WHOA theres a setCPU.com? wow
Mohammad_Adib said:
WHOA theres a setCPU.com? wow
Click to expand...
Click to collapse
Yes sir. It explains each and every option in the app, plus has a changelog too.
Edit: I saw the site u mentioned. It is a copy-paste from the setcpu.com site.
diablo009 said:
Yes sir. It explains each and every option in the app, plus has a changelog too.
Edit: I saw the site u mentioned. It is a copy-paste from the setcpu.com site.
Click to expand...
Click to collapse
wow....lolz
hi guys..,
pls share ur setcpu settings here...so that we can get some idea...we can choose the better ones...
To start with..,
i 've kyrillos rom 9.2 oc.., g3mod v2.2.2
My Settings:
- Main tab: Min 83Mhz, Max 1200MHz, Scaling: Conservative
- Profile (1): In call: 83min, 400max, Scaling: Ondemand, Priority:100
- Profile (2): Time profile: 1AM - 7AM (here put the time you sleep), min/max 83MHz, Scaling: Powersave, Priority: 99
- no voltage profile...
but it lags a bit at times....
pls share ur setcpu settings....here...
G3Mod 2.2.2.
Main profile : - Min 83, Max 800, Profile Lagfree.
Profiles, priorities in descending order.
1) Battery<15 : 400 Max 83 Min, Powersave.
2) Screen off : 400 Max 83 Min, On Demand.
3) Charging : 600 Max 83 Min, On Demand.
4) In call : 400 Max 83 Min, On Demand.
Kyrillos 9.3 and G3Mod 2.2.2 OC
main profile: 400-1000 - ondemand
time profile (00:00-06:59): 83-200 - conservative (priority: 100)
screen off profile: 400-500 - ondemand (priority: 99)
no undervolting and other settings, just sampling rate set to: 10000
guys...,only a few reply...
i don't know...why nobody show any interest to share ur setcpu settings...
LooksLikeSmart said:
guys...,only a few reply...
i don't know...why nobody show any interest to share ur setcpu settings...
Click to expand...
Click to collapse
simple answer... DONT USE MORE THAN 800mhz... even 801 will burn your phone's motherboard thats all i can say..
lovelyprincess said:
simple answer... DONT USE MORE THAN 800mhz... even 801 will burn your phone's motherboard thats all i can say..
Click to expand...
Click to collapse
I dont think so... It will just shorten the life of the cpu.
Sent from my GT-I9003 using xda premium
hi bscraze.,
i've posted my setcpu settings above...is it safe...?? whether i've to change max to 800Mhz...what about scaling...conservative or lag free..
pls post urs if u have...
My profiles for i5801:
Main tab - 200~700mhz on demand/lag free both works for me
Charging - 300~1200mhz on demand
Screen off - 83~500mhz on demand
Time 1am to 5.30am 83~83mhz powersave
You can try my profile, may work, may not but i advise you to change to 800mhz for your main tab.
Sent from my GT-I9003 using xda premium
lovelyprincess said:
simple answer... DONT USE MORE THAN 800mhz... even 801 will burn your phone's motherboard thats all i can say..
Click to expand...
Click to collapse
. No it won t.
hi..,dhirend_6d
i've set cpu settings used for 3 months...Main tab: Min 83Mhz, Max 1200MHz, Scaling: Conservative
no harm done...everything working fine...
but..is it safe...to continue always...? or
whether i've change it to 800MHz as suggested by bscraze...
LooksLikeSmart said:
hi..,dhirend_6d
i've set cpu settings used for 3 months...Main tab: Min 83Mhz, Max 1200MHz, Scaling: Conservative
no harm done...everything working fine...
but..is it safe...to continue always...? or
whether i've change it to 800MHz as suggested by bscraze...
Click to expand...
Click to collapse
You should keep it 800 max for normal usage because keeping high frequencies shortens processor life. Use higher frequencies(1000+) only when needed like when playing games and etc. At 800, in normal usage, all works smooth. Note I use lagfree as main profile. I suggest you also try lagfree once.
Kyrillos 9.3 and G3Mod 2.2.2 OC
main profile: min 83 - max 700 - ondemand
In call: min 83 - max 400 ondemand(priority: 100)
screen off profile: min 83 - max 400 - ondemand (priority: 98)
Ok now you scared me. Can higher freqs really damage motherboard or shorten cpu life?
These are my settings:
main 400min 800max ondemand
prof1: time 01:00 - 07:30 83min 83 max pwersave priority 99
prof2: screen off 83min 400max ondemand priority 98
prof3:In call 83min 400max ondemand priority 100
No undervolting.
Any suggestions or something?
cecenac said:
Ok now you scared me. Can higher freqs really damage motherboard or shorten cpu life?
These are my settings:
main 400min 800max ondemand
prof1: time 01:00 - 07:30 83min 83 max pwersave priority 99
prof2: screen off 83min 400max ondemand priority 98
prof3:In call 83min 400max ondemand priority 100
No undervolting.
Any suggestions or something?
Click to expand...
Click to collapse
They are perfect. You don t have to worry about anything with those settings. If you use 1000+ frequencies for longer periods continuously then it may reduce your CPU life. Use only when required.
cecenac said:
Ok now you scared me. Can higher freqs really damage motherboard or shorten cpu life?
These are my settings:
main 400min 800max ondemand
prof1: time 01:00 - 07:30 83min 83 max pwersave priority 99
prof2: screen off 83min 400max ondemand priority 98
prof3:In call 83min 400max ondemand priority 100
No undervolting.
Any suggestions or something?
Click to expand...
Click to collapse
Cpu chips are made to last at least 5 yrs so dont worry about it and like what dhirend said, only if you keep it at high frequencies for long times will it dmg the cpu more.
Sent from my GT-I9003 using xda premium
Hi, I have Kyrillos 9.4 & g3mod 2.2.2 OC.
My settings:
Main: 83-700Mhz ondemand
InCall 83-600Mhz ondemand
Screen Off 83-400Mhz ondemand
and I my i5800 freezes 3 times per day.
I don't have game, only necessary aps.
Please help me.
lefar333 said:
Hi, I have Kyrillos 9.4 & g3mod 2.2.2 OC.
My settings:
Main: 83-700Mhz ondemand
InCall 83-600Mhz ondemand
Screen Off 83-400Mhz ondemand
and I my i5800 freezes 3 times per day.
I don't have game, only necessary aps.
Please help me.
Click to expand...
Click to collapse
try cm7 marcellusbe or kyrillos, then you will never have a freeze again!
I'm on Kyrillos v9.4, kernel G3Mod v2.3
83Mhz, Max 800-1200MHz, Scaling: Ondemand
In call: 83min, 400max, Scaling: Ondemand, Priority:100
Time profile: 1AM - 7AM (here put the time you sleep), min/max 83MHz, Scaling: Powersave, Priority: 99
Screen off: 83min, 400max, Scaling: Ondemand, Priority:98
my battery lasts three days with normal/heavy usage
Hi,
I'm on kyorarom 0.5.1 with kernel G3MOD-Kyorarom-0.5.0
main: 83 - 800 lagfree
1. in call: 300 - 800 lagfree (if less I have to wait a lot to see the screen waking up) priority 100
2. screen off: 83 - 600 lagfree priority 100
3. charging: 83 - 900 lagfree priority 99
no freese, no FC, only one thing: when I wake up the phone from screen off I sometimes see the last screen before the lockscreen appears and I tried to change the off screen values and it was all the same...
baterry lasts at least 3 days with some wifi use, low BT use, some apps and games, but a lot of phone calls and sms
Everybody over here just check out this(forum.xda-developers.com/showthread.php?t=1369817) thread to understand the things better. (about governers, modules, etc) . Must see thread!!!
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.
Lately I've tried to use underclock and undervolt to improve the bad battery life of the Mi4c. I tried different values on the XOSP 7.1 (https://forum.xda-developers.com/mi-4c/development/unofficial-xosp-7-1-libra-aqua-t3551296) in the past days, and I discovered a combination of clock of the cpu and governor that seems to work quite nicely.
REQUIREMENTS:
Rooted phone
Kernel that provides the possibility to change this values
Busybox and Kernel Adiutor or analogue app
Recommended the use of XOSP 7.1 Rom (Not necessary)
Greenify
STEPS:
After having enabled the root access to busybox and Kernel Adiutor(the apps will ask you this to you when you first open them, just check "enable"), enter in Kernel Adiutor in the CPU section and dial in the following values.
BIG CORES: Max Frequency = 864 Mhz / Min = 302 Mhz
SMALL CORES: Max Frequency = 672 Mhz / Min = 302 Mhz
For both cores use "smartmax" Governor (this setting is right below the Frequency dials).
GPU: Max Frequency = 450 Mhz / Min = 180 Mhz.
Governor: simple_ondemand.
As last step, go in development settings and watch for active apps that you don't need and with Greenify disable them. This should help the battery even more. Remember to freeze only apps that don't send notification, otherwise you will not receive them until you open the apps.
REVIEW:
Yesterday I had a pretty heavy day, I used the phone quite a lot both with Wi-Fi and 3G and I ended up with 4:30 h Screen On Time and I even had 20% left. I really hope that this may help some of you because I know how stressful this is and I decided to share my experience with you.
Why you need to pay a 1k8Mhz phone to use 864Mhz, i can get to 5h without any configure cpu clock with lastest miui rom.
Increase/Improve Battery life of any phone Kernel manager best settings best power settings and can double the battery life of Samsung note 3 and other phones too
Disclaimer: I am not responsible for any damage or soft/hard brick that may happen to your device...please make sure you follow the instructions below !
Instructions
Download Smartpack-kernel manager from the Playstore or You can Use any of the kernel manager of your choice (i.e Smartpack-kernel manager, Franco kernel, Elementalx kernel manger) open the app grant root permission and follow the Steps below!
Steps
1) CPU Governor Settings: Set CPU governor to conservative and Multicore Power Saving set to Aggressive make sure you set Apply on boot
2) This is optional the Low Memory Killer : Foreground Applications set to 16MB, Visible Applications set to 32MB, Secondary Server set to 64MB, Hidden Applications set to 128MB, Content Providers set to 144MB ,Empty Applications set to 180MB make sure you set Apply on boot.
3) Reboot and Enjoy!:good:
Extras
1) Underclock CPU: Lowering the CPU clocks will greatly increase your screen on time SOT at the expense of performance. Most of your device operations aren't really CPU intensive so lowering it at least 25%, 50% and 75% is enough to greatly reduce power consumption.
For instance
Underclock CPU of Samsung Note 3 for 25% power reduction set to 1728MHz Maximum CPU frequency set on boot
Underclock CPU of Samsung Note 3 for 50% power reduction set to 1190MHz Maximum CPU frequency set on boot
Underclock CPU of Samsung Note 3 for 75% power reduction set to 652MHz Maximum CPU frequency set on boot
2) Underclock GPU of Samsung Note 3 use the powersave governor for power reduction set on boot
FAQ
Q: Will these work without Root?
A: NO. you can use magisk or superSu to root your device
Q: Does this work for xyz kernel?
A: Works on xyz kernel just follow the Instructions and Steps
Q: What are the advantages of this?
A: Better battery life.
Thanks
Thanks but i dont have Multicore Power Saving my device is Samsung Galaxy Note 3 HLTE
and rom is HAVOC OS 3.1 ANDROID 10 and kernel Lolz v14
nerannon said:
Thanks but i dont have Multicore Power Saving my device is Samsung Galaxy Note 3 HLTE
and rom is HAVOC OS 3.1 ANDROID 10 and kernel Lolz v14
Click to expand...
Click to collapse
Which kernel manager are you using? For Elementalx kernel manager it shows as mc_power_saving
Underclock CPU: Lowering the CPU clocks will greatly increase your screen on time SOT at the expense of performance. Most of your device operations aren't really CPU intensive so lowering it at least 25%, 50% and 75% is enough to greatly reduce power consumption.
Check Extras to see an example
Yai!
Послато са SM-N9005 помоћу Тапатока
Need extra SOT+ on most devices
Join group https://t.me/tweakmypixel
I dont have conservative on governors. what should I do
PennyZ said:
I dont have conservative on governors. what should I do
Click to expand...
Click to collapse
use interactive
enweazudaniel said:
Which kernel manager are you using? For Elementalx kernel manager it shows as mc_power_saving
Click to expand...
Click to collapse
Well im using smartpack kernel manager from Google play store
Nvm i found it ?
Followed these instructions; I've lost 2% while typing this, with a new battery, under LineageOS 16.0
I guess it's a ROM bug, unless proven otherwise.
Does anybody know if is there any way to get this without root-app, by mean of a one-time TWRP flashable zip?
Thank you.
lucbertz said:
Does anybody know if is there any way to get this without root-app, by mean of a one-time TWRP flashable zip?
Thank you.
Click to expand...
Click to collapse
No, not really
enweazudaniel said:
Increase/Improve Battery life of any phone Kernel manager best settings best power settings and can double the battery life of Samsung note 3 and other phones too
Disclaimer: I am not responsible for any damage or soft/hard brick that may happen to your device...please make sure you follow the instructions below !
Instructions
Download Smartpack-kernel manager from the Playstore or You can Use any of the kernel manager of your choice (i.e Smartpack-kernel manager, Franco kernel, Elementalx kernel manger) open the app grant root permission and follow the Steps below!
Steps
1) CPU Governor Settings: Set CPU governor to conservative and Multicore Power Saving set to Aggressive make sure you set Apply on boot
2) This is optional the Low Memory Killer : Foreground Applications set to 16MB, Visible Applications set to 32MB, Secondary Server set to 64MB, Hidden Applications set to 128MB, Content Providers set to 144MB ,Empty Applications set to 180MB make sure you set Apply on boot.
3) Reboot and Enjoy!:good:
Extras
1) Underclock CPU: Lowering the CPU clocks will greatly increase your screen on time SOT at the expense of performance. Most of your device operations aren't really CPU intensive so lowering it at least 25%, 50% and 75% is enough to greatly reduce power consumption.
For instance
Underclock CPU of Samsung Note 3 for 25% power reduction set to 1728MHz Maximum CPU frequency set on boot
Underclock CPU of Samsung Note 3 for 50% power reduction set to 1190MHz Maximum CPU frequency set on boot
Underclock CPU of Samsung Note 3 for 75% power reduction set to 652MHz Maximum CPU frequency set on boot
2) Underclock GPU of Samsung Note 3 use the powersave governor for power reduction set on boot
FAQ
Q: Will these work without Root?
A: NO. you can use magisk or superSu to root your device
Q: Does this work for xyz kernel?
A: Works on xyz kernel just follow the Instructions and Steps
Q: What are the advantages of this?
A: Better battery life.
Click to expand...
Click to collapse
I have a 4G Ram device, can you tell me the settings? I'm using Franco Kernel Manager.