Develop Bugs

How to configure the standard kernel scheduler (CFS) to behave more like BFS

First an introduction (sorry, if this got a little long, just wanted to make clear for everybody what we are talking about).
What is a scheduler?
The scheduler is a built-in part of the Linux kernel. It is that part of the kernel which decides how the available cpu power is divided among all running processes. As the cpu can only work for one process at any given time, the scheduler is responsible to assign cpu time-slices fairly to running processes.
Because of this the scheduler (among other things) plays an essential role on how responsive a system "feels" for the user. That's because responsiveness depends among other things on the time how long it takes from user input until the cpu handles the input (i.e. until "your" task/process gets cpu-cycles).
Current state of the art:
The standard Linux kernel uses the so called "Completely Fair Scheduler" (CFS) since some time (October 2007) now and seems to be useful for most use-cases (server, desktop, smartphone..).
As you may have already heard, since August 2009 there is a new player on the field, namely the "Brain **** Scheduler" (BFS). BFS promises some better latency behaviour on smaller platforms with fewer cpu-cores and mobile devices. Altough it wasn't accepted into the official Linux kernel tree, it was used by cyanogen and also adopted by Google into the mainline Android kernel (and as we are having kernel sources now, I'm sure you will see some more BFS-enabled kernels for the Hero, too).
But back to topic:
So, what I am going to talk about applies to those of you who DON'T have a kernel with the BSF scheduler (i.e. which have the standard CFS scheduler) which should be the majority of ROMs at the moment.
Tuning the CFS scheduler:
Even it's said that BFS may be better for small devices it's also possible to configure CFS for our needs:
While searching around I learned that the behaviour of the CFS scheduler can be influenced at runtime by a few parameters. All these settings can be applied at runtime and will be gone after a reboot. So it is safe to play around a little bit.
One interesting parameter I found was "NO_NEW_FAIR_SLEEPERS". As stated by some people on the Linux kernel mailinglist :
NO_NEW_FAIR_SLEEPERS is something that will turn the scheduler into a more classic fair scheduler (like BFS is too)
Click to expand...
Click to collapse
If this is true, maybe it will let the CFS behave better optimized for small devices.
But let's try it out! Let's see if it gives us some improvements.
How to to this:
Code:
# Step 1: Mount debugfs (which is a virtual filesystem like /proc/ or /sys/)
mount -t debugfs none /sys/kernel/debug
# Step 2 (optional): Display the current scheduler flags
cat /sys/kernel/debug/sched_features
# Step 3: Set the flag NO_NEW_FAIR_SLEEPERS
echo "NO_NEW_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features
# Step 4: Unmount debugfs again
umount /sys/kernel/debug
As said before: These changes are NOT PERMANENT. They will be gone after a reboot. But therefore it's safe to play around here.
Testing:
Tuning the scheduler will not give you plain speed improvements, so testing with Linpack is useless here. Instead it changes the way how the system reacts if there is a lot of multi-tasking.
So when you have changed the settings try testing around a little bit when the system is under load (like playing music while doing CPU intensive stuff or things like that) and report if it behaves better/worse than with default settings.
How to undo the setting:
Simple reboot your phone.
Or redo the steps above and replace the command in Step 3 with this one (note that the prefix "NO_" is ommited here):
Code:
echo "NEW_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features
Feel free to test and share your findings!

I guess I can copy paste the lines and use GScript to run them.
Any way to make this permanent? Put something in init.d maybe?

Geochelone said:
I guess I can copy paste the lines and use GScript to run them.
Click to expand...
Click to collapse
Of course. You will find 2 scripts for gscript in the attached zip-file:
enable_CFS_tweak.sh
disable_CFS_tweak.sh
So you can simply switch for easy testing.
For those who don't know GScript: It's an app from the market to easily execute scripts on your phone. Pretty handy if you are testing things before you add them to an init-script.
Instructions:
Install "GScript Lite" from the market
Unzip the 2 scripts and place it on the sd-card into the folder gscript
Launch GScript Lite, press "Menu" -> "Add script" -> "Load file" and select the scripts you just placed into "gscript" folder.
Make sure the "Need SU?" checkbox is checked and press "Save"
Tap on the script to launch it.
Geochelone said:
Any way to make this permanent? Put something in init.d maybe?
Click to expand...
Click to collapse
Correct. You would need to place the commands into an init script, which are located in "/system/etc/init.d" on most ROMs.

Hard to test..
I underclocked my Hero to 245Mhz, started the music player, launched NeoCore benchmark and via adb launched 10 instances of "md5sum /dev/urandom".
Music still not choppy. No matter whether the tweak is enabled or disabled.
The scheduler seems too good to exploit it..
[edit]
just got a NeoCore benchmark if 02.8 FPS Yeahh, that's stresstesting..
[/edit]

is there a way to make this by default in the source?
maybe add the option to the .config file?

MaXo64 said:
is there a way to make this by default in the source?
maybe add the option to the .config file?
Click to expand...
Click to collapse
Yes, you can edit kernel/sched_features.h
and replace
Code:
SCHED_FEAT(NEW_FAIR_SLEEPERS, 1)
with
Code:
SCHED_FEAT(NEW_FAIR_SLEEPERS, 0)

thanks mate, compiling right away..

what is the test result?

Just so you guys know we are basically doing this now on the Eris... via some cool scripts:
http://forum.xda-developers.com/showthread.php?t=784089&page=7

Thanks for the tip will definitively check it out

Wow! Thanks for the tip. After reading it sparked my curiosity in the Linux kernel so I went hunting on the web for more detailed info on this particular parameter (NEW_FAIR_SLEEPERS) but I found no useful info as to what exactly it is or what it does. unfortunately, the name doesnt give too much away either (to the layman).
Anyway eventually I came across a site that a couple of other SLEEPER parameters are mentioned. and it claimed that tweaking these as well as changing the sched_latency and sched_granulairty parameters will enhance android phone performance. Again I searched for explanations of these parameters but to no avail (im obviously not very good at searching!). In the end I thought id just apply the tweaks and see what happened. and voila! the phone is the smoothest I have ever felt it!
As I said I dont know which tweak is responsible for the smoothness or if its just a combination of all three but my phone is really nice to use now. I can scroll long lists and actually see scrolling instead of a stutter from start to finish! I am running elelinux 1.8 and flykernel10a at 528MHz and its smoother than i've had it when running at > 600MHz.
I have no idea what implications the changes have on the overall performance of the phone but its smooth and not overclocked! cant be bad??
so heres the changes I applied: (from ./adb shell or terminal emulator on phone)
$ su
# mount -o remount,rw /system
# echo 'kernel.sched_latency_ns = 600000' >> /etc/sysctl.conf
# echo 'kernel.sched_min_granularity_ns = 400000' >> /etc/sysctl.conf
# echo 'kernel.sched_features = 24188' >> /etc/sysctl.conf
# mount -o remount,ro /system
# sysctl -p
kernel.sched_latency_ns = 600000
kernel.sched_min_granularity_ns = 400000
kernel.sched_features = 24188
# exit
$ exit
the 24188 parameter disables a couple of sleepers and the other two change some timings in the kernel. The changes are supposedly ONLY suitable for non-BFS kernels. but they are supposed to make the CFS kernel behave more like the BFS kernel in general.
Anyway try it and see if you want and report back if it makes your phone any better or worse. Or if there are any Linux gurus maybe you can shed more light on what these parameters actually do.

I know this thread is a little old, but I wanted to report that those settings worked great on my MyTouch Slide! I'm also overclocked/underclocked to 825/245 and using the autokiller memory optimizer, with the settings you suggest my phone is amazingly fast!
I did a little research on these settings as well, and will report back as I do some more testing to see what works best with the specs in this specific phone. At that time I will post a link to a new thread on this in the section for my specific phone.
Thanks for the great tips!

PesasusQ governor here

Hi everyone,
i'm not quite sure about governor information , it's for this cause i'm asking here
My main answer is:
Is really pegasusQ governor the better multi-core governor?
start from begin.
pegasusQ is a ondemand governor which also controls hotplugging of cores.
i know, every core has run queue with different thread, but for now our 2core work in synchronous core speed, when core0 ( first core ) is underload tells cpudriver to raise cpufreq ( both core ) , also core1 ( second core ) get high clock that it need.
if i'm not wrong,
pegasusQ work in a-synchronous mode, each core has different clock, if core0 is underload, governor will increase only core0 clock and not core1
can be better this for battery and lag-kill right?
Gokhanmoral modified pegasusq (originally authored by Samsung for quad core devices) in Siyah kernel to be dual core friendly, with good results ( he make default governor in his kernel ) ,
why we dont have a kernel ( or famous kernel like franco, fugu,air, trinity or same ) doesn't include this?
with this value ( mixed driodphile relaxed settings and franco ondemand settings ) can we get a better battery and better speed?
Code:
echo "98" > /sys/devices/system/cpu/cpufreq/pegasusq/up_threshold
echo "80" > /sys/devices/system/cpu/cpufreq/pegasusq/up_threshold_at_min_freq
echo "30000" > /sys/devices/system/cpu/cpufreq/pegasusq/sampling_rate
echo "1" > /sys/devices/system/cpu/cpufreq/pegasusq/sampling_down_factor
echo "5" > /sys/devices/system/cpu/cpufreq/pegasusq/down_differential
echo "4" > /sys/devices/system/cpu/cpufreq/pegasusq/freq_step
echo "384000" > /sys/devices/system/cpu/cpufreq/pegasusq/freq_for_responsiveness
echo "15" > /sys/devices/system/cpu/cpufreq/pegasusq/cpu_up_rate
echo "15" > /sys/devices/system/cpu/cpufreq/pegasusq/cpu_down_rate
echo "729000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_1_1
echo "384000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_2_0
echo "350" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_1_1
echo "200" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_2_0
echo "0" > /sys/devices/system/cpu/cpufreq/pegasusq/ignore_nice_load
echo "1" > /sys/devices/system/cpu/cpufreq/pegasusq/io_is_busy
echo "0" > /sys/devices/system/cpu/cpufreq/pegasusq/max_cpu_lock
echo "0" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_lock
thanks for answer and i hope to myself understand of this governor, thanks

Hope some one can explain >_< Curious to know :good:

[Team Kernelizers][How To][SPR][TK MOD 1.0.4]KT747 Kernel Tweaks-Updated 5-14-13

About​Welcome to Team Kernalizers's SPRINT Thread. This thread will attempt to teach you and show you how to maximize the performance and battery life of your GS3 running the KT747 kernel by Ktoonsez.
In this thread, you will learn everything you need to know about Governors, I/O Schedulers, Underclocking (UC), Overclocking (OC), Undervolting (UV) and the KTweaker application. We will also provide you with pre-configured tweaks to use.
This is a friendly support community. You can post your benchmarks, battery stats, feedback and settings. We will also help troubleshoot any problems that you may encounter while using this kernel and our tweak packages.
Rules​Please consider these rules before using this thread:
1. Follow XDA Forum rules (http://forum.xda-developers.com/announcement.php?f=1712)
2. There will be NO FLAMING, NO SPAMMING, NO HARRASMENT of any kind. These will not be tolerated. You have been warned!
3. Search the thread first before asking questions. Most likely, your question may have been answered already.
4. If you are stuck and need help, DO NOT post comments like "this is not working". It will be ignored. You must provide necessary information like ROM Type (AOSP/TW), Kernel Version, OC, UV ...etc. You get the picture. The more you provide the better we can help
5. Please allow time for the team to find an answer if we can’t figure it out we know enough people to help us out finding a answer thank you
6. Be Patient We have our own personal lives outside of here. Allow the team some time to find answers. We will do our best to help.
7. If you post screenshots, you are allowed a maximum of 3 screenshots.
8. Keep posts/threads on-topic
By post in this thread, you are agreeing to the above rules.
Members​
Galaxys3Man30
mw86
GTOJIM
Ramondal
clothednblack1
RErick
chinkybean
daniel4653
steelers_exe
crazymook
castle_bravo
luis86dr
MorphiousGX
TexasEpic4G for awesome banners he makes for us!!!!!
​
Supported Devices​AT&T Samsung Galaxy SIII : http://forum.xda-developers.com/showthread.php?t=2144004
Sprint Samsung Galaxy SIII: http://forum.xda-developers.com/showthread.php?t=2032956
T-Mobile Samsung Galaxy SIII: http://forum.xda-developers.com/showthread.php?t=2207286
Verizon Samsung Galaxy SIII: http://forum.xda-developers.com/showthread.php?t=2201555
USCELLULAR Samsung Galaxy SIII:
http://teamuscellular.com/Forum/index.php?/topic/3472-[SUPPORT]-(Kernel)-ktoonsez-kt747
Thanks​
ktoonsez - For giving us this amazing kernel and the plethora of options available with it. His thread his here Make sure to thank him!
AT&T: http://forum.xda-developers.com/showthread.php?t=1756776
Sprint: http://forum.xda-developers.com/showthread.php?t=1800576
T-Mobile: http://forum.xda-developers.com/showthread.php?t=1871946
Verizon: http://forum.xda-developers.com/showthread.php?t=1853816
All of the Team Kernelizers members for their tweaks and dedication and help
All of the testers, and followers
All of the ROM developers out there for making our phones fun to use
And of course our Friendly Forum Moderator:
kennyglass123
Disclaimer​Team Kernalizers members, Ktoonsez, and ROM developers are not responsible for bricked devices or any other device issues you experience as a result of using information in this thread.
Every phone is different, especially since it was found that we have slow, nominal, and fast variations.
Tweaks provided are extremely experimental and should be avoided by beginners and people who have important responsibilities tied to the usage of their phone.
You Have Been Warned: Use of any information, tweaks and applications in this thread at your own risk. You assume full responsibility for your own actions.
Downloads
Team Kernelizers Tweaks​All of our TK bin files will be available here:
From Phone: https://m.box.com/s/5hazifi3odci94uyykws/1/698338185
From PC: https://www.box.com/shared/5hazifi3odci94uyykws
Reporting Tools​Huge thanks to MorphiousGX for our live report form. Please report battery usages at these links.
We will use this information to help make better adjustments to our tweaks. It will collect the necessary information to make sure people compare apples to apples*
You can also view results after you submit, and filter on any of the questions asked (i.e. Tweaker's name, governor, release date..etc).
The form can be found here*https://docs.google.com/forms/d/1-uz...3jPpg/viewform
The results can be viewed here*https://docs.google.com/spreadsheet/...Xc&usp=sharing
If you have any feedback (good or bad) please feel free to let MorphiousGX know he maintains it and you all should thank him.
Team Kernelizers Proudly Presents​TK Mod 1.0.4-REV 4​
Download​ http://db.tt/a1fiJtuF ​
Features​
Bin File Rename
Individual renaming of the following bin Files for battery savings:
gsiff_daemon
mpdecision
qosmgr
smd
smdexe
Renames bin files with .bak
Bin File Restore
Individual restoring of the following bin files:
gsiff_daemon
mpdecision
qosmgr
smd
smdexe
Restores bin files to their original state.
Mods
KT747 Bootanimation Fix:
Use only if bootanimation is broken. Usually occurs on TW Roms.
Team Kernelizers TouchWiz Build Prop Tweaks
Team Kernelizers AOSP Build Prop Tweaks
Restore of Original TouchWiz Build Prop
Restore of Original AOSP Build Prop
​
Changelog​Located in TKMod zip​
Contest Splash Screens​
You now have access to all Team Kernelizers Contest Splash Screens in one zip!
1st Place Splash Screen:
{
"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"
}
2nd Place Splash Screen:
3rd Place Splash Screen:
4th Place Splash Screen:
5th Place Splash Screen:
6th Place Splash Screen:
7th Place Splash Screen:
8th Place Splash Screen:
9th Place Splash Screen:
10th Place Splash Screen:
11th Place Splash Screen:
Stock Splash Screen: Reverts to Original Splash Screen.
Thanks from luis86dr​
Edgehood for answering all my questions about Aroma! Thanks buddy!
steelers_exe for his awesome splash screen for Aroma Installer.
RErick for his build prop updater script & for providing Splash Screen zips.
mw86 for his build prop tweaks.
GMan for testing and helping me. Also for providing mirrors!
decimalman for making the build prop script work!
Ktoonsez for such a awesome Kernel and inspiring us to do what we do.
Everyone who helped with testing!
Team Kernelizers for being so damn awesome!
Known Bugs​Splash Screens will only work on TouchWiz
Working on finding out the cause of these issues. Please report bugs in either of the Team Kernelizers threads.
This is still in Beta, more is yet to come!!!!!!
Kernel Information​General Installation Instructions (for both TW and AOSP):​1. Download correct version of kernel for your device and rom. This is important as you may brick your phone is you use the wrong version.
2. Flash kernel using your preferred recovery
3. Do the following AFTER installing the kernel and BEFORE you reboot your phone:
a. Clear cache
b. Clear dalvik
c. Fix Permissions
4. Reboot your device.
TW Specific Kernel Instructions:
(can be used with AOSP too)​There are some files on your TouchWiz phone that need to be renamed in order to maximize the battery life of your phone. There has been some debate on whether or not this is necessary, but for now we would recommend renaming these files to ensure that there is no chance of excessive battery drain.
Part 1:
These steps are only necessary on TouchWiz ROMs, however you can also do this on AOSP as well:
1. You must have ROOT. You will need to have a root enabled file explorer on your phone (ES File Explorer works very well and you can get it from the play store (https://play.google.com/store/apps/details?id=com.estrongs.android.pop&hl=en). When you get it, open it up and go the the settings and scroll all the way down until you see the Root Settings. Go in there and enable ALL of the root settings.
2. After that is done, navigate to your root folders using the Folder Up icon at the top. Once you are in your root folders, navigate to /system/bin and locate the following files. You will need to rename them with a ".bak" at the end of the filename
gsiff_daemon --> gsiff_daemon.bak
mpdecision --> mpdecison.bak
qosmgr --> qosmgr.bak
smd --> smd.bak
smdexe --> smdexe.bak
Renaming these files will not harm your phone. Many users rename these files every time they flash a rom, and no damge is done.
Also, some ROMs come with these files renamed or deleted entirely, so if you don’t find a file, don’t be alarmed.
You have to do this every time you flash the ROM and/or Kernel.
If you feel uncomfortable doing this yourself, you can use the TK-MOD (see Downloads section) and it will handle this for you.
Part 2:
Stopping mpdecision from being called:
1. Open terminal emulator and type the following code:
su
2. When terminal emulator asks for root permission hit 'Grant' or 'Allow'.
3. At the # prompt type:
stop mpdecision
Using Rom Toolbox (https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox) we will make a script that will stop mpdecision from being called at each boot so you don't need to use terminal emulator each time
1. Open Rom Toolbox and scroll down to the Scripter option
2. In the scripter, click the “+” button in the top right corner, then select 'Create'
3. Type a name for our new script, lets call it “stop mpdecision”
4. In the commands enter the following text:
#!/system/bin/sh
stop mpdecision
5. Hit the disk icon to save it
6. Select the script that you just created and a dialog box should pop up, select set at boot
Were done here
AOSP Specific Kernel Instructions:​When coming from a 3.0 Kernel to a 3.4 Kernel there is a new method with kernel updates. Skipping these steps will cause phone instability, due to some bad data left behind. This is a flaw in the Android OS, not the application. You must follow the instructions below (Thanks ktoonzs for the new method of the ktweaker app)
1. Go to Settings on the phone
2. Go to app manager then all apps
3. Scroll down to ktweaker app n open it
4. Once open hit FORCE STOP and then hit CLEAR DATA
5. Reboot and flash your new update of ktoonzs kernel
6. Repeat steps 1-4 in the above “General Installation” section
You should be good to go after that
Resources & Useful Links​
[*]Rescan Media Root (click link on phone and be sure to select launch link with play store)
https://play.google.com/store/apps/d...diascannerroot
[*]Kill Media Server (thanks for the link Jcdominguez)
http://www17.zippyshare.com/v/77111471/file.html
[*]Lux Auto Brightness (set brightness lower than stock minimum brightness on any rom)
https://play.google.com/store/apps/d...d=com.vito.lux
[*]Rom Toolbox Lite by Jrummy
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox
[*]Build Prop Editor free by Rom Toolbox maker Jrummy
https://play.google.com/store/apps/d...ld.prop.editor
[*]Swipe Pad (thanks Naddict) make a easy to launch multitask launcher from anywhere a shortcut to Developer Options (great for aosp Hwoverlay)
https://play.google.com/store/apps/d...ipepad.android
[*]Known Wakelocks thread (Thanks T. J. Bender)
http://forum.xda-developers.com/show...php?p=31974989
[*]DS Battery Saver Pro (manage radios like juice defender with less overhead) (thanks for the link AdamDelozier)
http://forum.xda-developers.com/show...php?p=35046431
[*]Battery Review Thread including extended batteries (Thanks Rlatjs17)
http://forum.xda-developers.com/show...php?p=30478980
[*]Fast Reboot (closes/restarts apps and services similar to rebooting without a reboot)
https://play.google.com/store/apps/d...streboot&hl=en
[*]Better Batter Stats (track all forms of wake locks) (Thanks Sven Knispel)
https://play.google.com/store/apps/d...erbatterystats
[*]Carat (track and discover battery drain prone apps)
https://play.google.com/store/apps/d....carat.android
[*]Seeder 2.0.0b1 (Thanks Lambgx02)
http://forum.xda-developers.com/showthread.php?p=592
[*]Cpu Spy (check used mhz and deep sleep usage) (Thanks Brandon Valosek)
https://play.google.com/store/apps/d...valosek.cpuspy
[*]Universal Initd Support APK (Thanks RyuInferno) (enable check for initd support)
http://forum.xda-developers.com/show....php?t=1933849
[*]Lag Fix(fs-trim) (use trim to trim blocks labeled deleted from storage where blocks are still full) (thanks AuxLV)
http://forum.xda-developers.com/show...&postcount=122
[*]CrossBreeder Combo MOD (combines three discussed entropy lag/lockup tweaks)
http://forum.xda-developers.com/show...php?p=37062006
[*]Flashable Recoveries (please thank Naddict for this amazing resource)
http://forum.xda-developers.com/show...php?p=35741601
[*]If you flashed the KT747 kernel separate from your ROMs installer, you can enable the boot animations by following the directions in this thread:
http://forum.xda-developers.com/show...22&postcount=4
[*]This is a link to the Better Battery Stats thread. This app is only free to XDA members, but I strongly encourage you to donate. And please hit the thanks button while you are there.
http://forum.xda-developers.com/show....php?t=1179809
[*]Schedulers and Governors explained:
http://forum.xda-developers.com/show...php?p=19846276
http://forum.xda-developers.com/show...php?p=26884853
PERSONAL EXPERIENCES OF FOLLOWERS​ @Maybelle
I've been following along and will be so bold as to put in my two cents worth. I am a general/vascular surgeon. I got into Android because I was pissed off about a tablet I had that Toshiba wouldn't update. That lead me to y'all in time. I cannot say enough about how much respect I have for the Android and XDA development community. You truely "stick it to the man" while making the platform better.
I have been following the events related to Exit_Only and can say that while I have a hard time understanding the details of what is evolving I do understand that he, as well as all of you on the TK team, have helped me and my ability to communicate with my patients and my colleagues using a phone that does a lot more than its manufacturers or carrier would have it do.
We have "kanging" in medicine too. As a matter of fact it is written into the Hippocratic Oath IMO. What we do not tolerate in medicine is claiming credit for another doctor's work, although we are free to use it to benefit our patients as long as we do not claim glory for ourselves.
Kudos to EO for defending his hard work and kudos to all the rest of y'all for rising to his defense. I would be proud to support a TK website if that is the direction you wish to go in. I only wish I was more knowledgeable and could contribute in a more technical way. With your help I will get there.
I'm sorry if I am off topic but I had to speak.

*Users with Ktweaker settings reseting: Freezing system tuner and or rom toolbox is a possible fix for either min/max mhz, scheduler or governor resetting in Ktweaker. Another way could be making a backup of your settings, clear data on ktweaker, reboot and restore settings twice as not all apply right first time and reboot again with restore settings immediately at boot.
*Ktweaker Issues if on Kt747 Kernel: could have issues on roms like Freegs3 and it is noted that if you prefer to use Ktweaker to set your settings vs script than make sure no conflicting script is running for example check /system/etc/initd/ for 70tweaks and remove or place somewhere for safe keeping to prevent conflicts with Ktweaker for example min max changing or voltage tables, governor or scheduler. This script in the example is Freezas script to set phone based on screen on and off and current battery level for example of some of its functions, there is nothing wrong with using scripts nor is there a problem with this script in particular. Just be aware there will be conflicts if used in conjunction with Ktweaker and or setcpu and the like.
Ktoonservative governor presets from our thread
BALANCED PERFORMANCE BATTERY LIFE (no order)
Ktoonservative 50 30 67 68 Freecharlesmanson tunables
Ktoonservative 50 30 85 80 docnas tunables
Ktoonservative 33 11 99 35
Ktoonservative 42 11 99 99
Ktoonservative 75 11 95 75 tunables
HIGH BATTERY SAVINGS (no order)
-#*note#* (you can get away with one of these high threshold tunings and not feel laggy by using touch booster set to 384mhz on booster one and for touch two 486mhz which should help response time on any interactive action where in you touch the screen and immediately resume the normal minimum mhz as during touch boost the cpu still ramps based on load over the touch boost values if and as needed. It provides less frequency steps to target frequency during interactive use)*! 384/486 being conservative and 702mhz touch boost 1 756mhz touch boost 2 for more response and still will not be over target frequency during interactive use.
Ktoonservative 75 90 95 99 single core
Ktoonservative 85 94 95 99 single core 12 31 2012
Ktoonservative 60 35 97 75 Castle Bravo
Ktoonservative 60 35 90 70 Daniel4653
Ktoonservative 65 45 99 99 tunables
Ktoonservative 65 55 99 99 tunables old revision
Ktoonservative 65 45 97 95 Castle Bravo
SCHEDULERS
Jcdominguez chart
[Light usage] SIO> ZEN> NOOP> Deadline > BFQ > CFQ [medium/heavy usage]
************
Battery Saving:
-Noop: best battery savings for all mobile but not the best data rates. Considered a simple i/o
-SIO: similar to noop but uses a little more battery with benefit of some deadlines.
-Zen: Combo of noop, sio and deadline.
Balanced:
-BFQ: a good balance of battery and performance.
*tuning for solid state storage
# Freecharlesmanson tunables original
# MW86 tunables (use if above tuning resets ever time)
Performance with battery secondary:
-Row: fastest latencies on reads over all governors but may have the highest battery drain. Read Over Write.
#performance tuning Castle Bravo
-Schedulers/Governors Explained (thanks droidphile) (thanks for link Clothednblack)
http://forum.xda-developers.com/showthread.php?p=19846276
(thanks Grift) (thanks for link Clothednblack)
http://forum.xda-developers.com/showthread.php?p=26884853
Extra low Voltage Table:
! #@$ do not try this table if you have not tried the one in post one above. This is much lower and likely not okay for every phone but has been a non issue on mine and for a few others.
2106mhz: 1290 mV
1998mhz: 1260 mV
1890mhz: 1225 mV
1809mhz: 1200 mV
1728mhz: 1175 mV
1674mhz: 1160 mV
1512mhz: 1150 mV
1458mhz: 1145 mV
1404mhz: 1140 mV
1350mhz: 1135 mV
1296mhz: 1125 mV
1242mhz: 1110 mV
1188mhz: 1100 mV
1134mhz: 1085 mV
1080mhz: 1075 mV
1026mhz: 1035 mV
972mhz: 1025 mV
918mhz: 1010 mV
864mhz: 1000 mV
810mhz: 985 mV
756mhz: 975 mV
702mhz: 935 mV
648mhz: 925 mV
594mhz: 910 mV
540mhz: 900 mV
486mhz: 885 mV
384mhz: 880 mV
192mhz: 875 mV
144mhz: 870 mV
96mhz: 865 mV
Low Rider Volt Table
-note may not be stable using the same volts but a higher maximum mhz
-if the above table or the one in post one are not stable do not attempt to load these
-Thanks goes to Clothednblack1
1242 MHz - 995mV
1188 MHz - 975mV
1134 MHz - 950mV
1080 MHz - 945mV
1026 MHz - 930mV
972 MHz - 915mV
918 MHz - 910mV
864 MHz - 855mV
810 MHz - 850mV
756 MHz - 835mV
702 MHz - 820mV
648 MHz - 805mV
594 MHz - 835mV
540 MHz - 825mV
486 MHz - 805mV
384 MHz - 785mV
192 MHz - 775mV
144 MHz - 765mV
96 MHz - 700mV this may be too low for some
General Tips for faster UI
-enable Hwoverlay and force gpu rendering (leave out Hwoverlay on touchwiz to prevent a noted video playback issue)
-Disable animations and transitions on launcher (or set to as fast as possible)
-Use Launcher options to force launcher into memory like in Nova Launcher (Thanks Pberge)
Create localprop and force app in memory thanks nonato
- Go to terminal type su hit enter
-Type all of the following and hit enter to add an app to local.prop and force it in memory. Nova Launcher would be as follows. If local.prop doesn't exist the command will create it.
echo sys.keep_app_1=com.teslacoilsw.launcher-1 >> /data/local.prop
-(Thanks nonato for posting this trick in Seeder thread.)
Fix Gtalk fully disable if it was removed and causing a wakelock (needs credit need to find poster of this)
Cyanogenmod Based tweaks
-enable memory management options
-disable dithering (dithering on smooths color transitions off can show a banding effect) (if not on a CM based rom the use dithering 0 build prop has same effect)
-16bit transparency (close to half the bandwidth needed for 24/32bit color)
Rename these files on Touchwiz as pictured in System/Bin to prevent unnecessary battery drain (thanks for pic Jcdominguez)
Thread on Touchwiz safe to remove apps GS3 (Thanks Vegas Rooted)
http://forum.xda-developers.com/showthread.php?p=32212501
User suggestions for removable apps (Touchwiz)
Stop MPDECISION on a 4.2.1 Rom
- Navigate like in this pic to system/etc
- Open initpostboot.sh
- Go to line 223 (i use droidedit free at play store to edit the file it makes it easy to find line numbers)
- Place cursor in front of mpdecision and insert a #. Save the file and exit and reboot. Thats all thats necessary to prevent stopping mpdecision from starting or showing errors over and over in logcat on Android AOSP 4.2.1.
-*Credit goes to Decimalman thank you
Info on ROW Scheduler
http://lwn.net/Articles/509829/
-*Thanks CastleBravo
BUILD PROP
-tested on Freegs3(4.1.1), Goodness(4.1.1)rom, Paranoid Android(4.1.2), Chemistry(4.1.1), Unofficial AOKP(4.2.1), PACman(4.1.2), Cm10.1 nightly(4.2.1), Kiljoy(4.1.1)
- Build prop i use and has been tested on 4.1.1/4.1.2/4.2.1
- Gtojim and I are running these without issues. Tested on freegs3, cm10.1, Paranoid android and PAKman (#*has not been tested with Morphology need feedback*#)
-credit for the build props goes to Rom Toolbox and an XDA member Custodian. Thank you Custodian.
http://db.tt/q7S1s8yp
- Directions same as other build props we have listed. Until we have an easy install script this is for advanced users only who already have experience editing build.prop. I will always suggest using rom toolbox to do so vs manually editing your build prop file. Do not add all of them in without checking if the value exists already. You don't want double lines that one says the line and true and the other false, its hard to say but one may override the other. THIS IS NOT A BUILD PROP IT IS A SIMPLE TEXT FILE WITH ALL THE ONES I USE. THE BUILD PROP ENTRY IS TO THE LEFT OF THE EQUAL SIGN AND THE VALUE USED IS TO THE RIGHT OF THE EQUAL SIGN. YOU MUST SEARCH AND REPLACE OR ADD THEM MANUALLY.
-whats included in the build prop list:
debug.composition.type=gpu
debug.egl.hw=1
debug.mdpcomp.maxlayer=2
debug.sf.hw=1
debug.performance.tuning=1
debug.sf.nobootanimation=1 (set to 0 to reenambe Bootanimation or do not use this build prop)
debug.qctwa.preservebuf=1
debug.qctwa.statusbar=1
debug.qc.hardware=true
ro.HOME_APP_ADJ=1
video.accelerate.hw=1
windowsmgr.max_events_per_sec=256
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-fma2dp=false
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-rtsp=true
media.stagefright.enable-record=false
mot.proximity.delay=20
movfilter=40
move_hyst=0
lpa.decode=false
lpa.use-stagefright=false
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.enc.hprof.vid.fps=25
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
ro.camcorder.videoModes=true
ro.telephony.call_ring.delay=400
ro.ril.disable.power.collapse=0
ro.config.nocheckin=1
ro.config.hwfeature_wakeupkey=0
ro.lge.proximity.delay=20
ro.min_pointer_dur=8
ro.max.fling_velocity=15000
ro.min.fling_velocity=4000
ro.mot.eri.losalert.delay=900
ro.HOME_APP_MEM=8192
ro.FOREGROUND_APP_MEM=6144
ro.VISIBLE_APP_MEM=8192
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
ro.cwm.enable_key_repeat=true
dalvik.vm.checkjni=false
dev.pm.dyn_samplingrate=1
drm.service.enable=false
persist.hwc.mdpcomp.enable=false
persist.gps.qmienabled=true
persist.sys.use_dithering=0
persist.sys.scrollingcache=3
per_sec=300
com.qc.hdmi_out=true
com.qc.hardware=true
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.heapidealfree=8388608
dalvik.vm.heapconcurrentstart=2097152
ring.delay=0
TCHTHR=28
ENFORCE_PROCESS_LIMIT=false
wifi.supplicant_scan_interval=300
AOSP only
dalvik.vm.heaptargetutilization=0.25
Touchwiz Only
dalvik.vm.heaputilization=0.25
Systctrl settings via Init.d (requires kernel with init.d support or enable initd with RyuInfernos apk link at bottom) (tested on same roms as Build Prop)
- * Thanks Zeppelinrox for talking some settings over with me.
- Help entropy pool
- read_wakeup_threshold to 1366
- write_wakeup_threshold to 128
http://db.tt/NilQsqG6
- Init.d for systctrl with the above set already and other optimized values
- Here guys this one is without anything special for entropy the values related to it are set to default on this one
- read_wakeup_threshold 64
- write_wakeup_threshold 128
- randomize_va_space 2
http://db.tt/rHcNuTfR
- Instructions:
Download. Using a file explorer, i like es file explorer go up from internal storage with a root explorer till you are at / you should see system, sys and much more. Go to /system/etc/initd/ and paste this file in there. Select it and go to properties of the file and select permissions. Change them to rwxrwxrwx. In other words enable read, write and execute for the three options user, system and other or whichever they are called. Now exit and reboot. Now at boot systctrl are applied. These are the presets system tuner sets plus a few tweaks by Freecharlesmanson (if you see him please be sure to give him thanks) and a fix for entropy where noted above.
- What is changed in the two systctrl (initd commands are as follows in the above files except the settings mentioned) (you can pick and choose and make your own initd script):
#!/system/bin/sh
echo "524288" > /proc/sys/fs/file-max
echo "32000" > /proc/sys/fs/inotify/max_queued_events
echo "256" > /proc/sys/fs/inotify/max_user_instances
echo "10240" > /proc/sys/fs/inotify/max_user_watches
echo "10" > /proc/sys/fs/lease-break-time
echo "64" > /proc/sys/kernel/random/read_wakeup_threshold
echo "128" > /proc/sys/kernel/random/write_wakeup_threshold
echo "65536" > /proc/sys/kernel/msgmax
echo "2048" > /proc/sys/kernel/msgmni
echo "10" > /proc/sys/kernel/panic
echo "'500 512000 64 2048'" > /proc/sys/kernel/sem
echo "268435456" > /proc/sys/kernel/shmmax
echo "524288" > /proc/sys/kernel/threads-max
echo "2" > /proc/sys/kernel/randomize_va_space
echo "10485760" > /proc/sys/net/core/optmem_max
echo "8388608" > /proc/sys/net/core/rmem_default
echo "65536" > /proc/sys/net/core/wmem_default
echo "524288" > /proc/sys/net/core/rmem_max
echo "524288" > /proc/sys/net/core/wmem_max
echo "'10485760 10485760 10485760'" > /proc/sys/net/ipv4/tcp_mem
echo "1" > /proc/sys/net/ipv4/tcp_no_metrics_save
echo "1" > /proc/sys/net/ipv4/tcp_rfc1337
echo "0" > /proc/sys/net/ipv4/tcp_ecn
echo "'6144 87380 524288'" > /proc/sys/net/ipv4/tcp_rmem
echo "1" > /proc/sys/net/ipv4/tcp_tw_recycle
echo "'6144 87380 524288'" > /proc/sys/net/ipv4/tcp_wmem
echo "35" > /proc/sys/vm/dirty_ratio
echo "40" > /proc/sys/vm/dirty_background_ratio
echo "5" > /proc/sys/vm/swappiness
echo "900" > /proc/sys/vm/dirty_expire_centisecs
echo "300" > /proc/sys/vm/dirty_writeback_centisecs
echo "100" > /proc/sys/vm/vfs_cache_pressure
echo "95" > /proc/sys/vm/overcommit_ratio
echo "3" > /proc/sys/vm/page-cluster
echo "4096" > /proc/sys/vm/min_free_kbytes
echo "3" > /proc/sys/vm/drop_caches
Recommended Juice Defender Setup - (Thanks Clothednblack)
Resources/Apps
#############
- Rescan Media Root (click link on phone and be sure to select launch link with play store)
https://play.google.com/store/apps/details?id=com.addz.mediascannerroot
- Kill Media Server (thanks for the link Jcdominguez)
http://www17.zippyshare.com/v/77111471/file.html
-Lux Auto Brightness (set brightness lower than stock minimum brightness on any rom)
https://play.google.com/store/apps/details?id=com.vito.lux
-Build Prop Editor free by Rom Toolbox maker Jrummy
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
-Swipe Pad (thanks Naddict) make a easy to launch multitask launcher from anywhere a shortcut to Developer Options (great for aosp Hwoverlay))
https://play.google.com/store/apps/details?id=mobi.conduction.swipepad.android
-Known Wakelocks thread (Thanks T. J. Bender)
http://forum.xda-developers.com/showthread.php?p=31974989
-DS Battery Saver Pro (manage radios like juice defender with less overhead) (thanks for the link AdamDelozier)
http://forum.xda-developers.com/showthread.php?p=35046431
-Battery Review Thread including extended batteries (Thanks Rlatjs17)
http://forum.xda-developers.com/showthread.php?p=30478980
-Fast Reboot (closes/restarts apps and services similar to rebooting without a reboot)
https://play.google.com/store/apps/details?id=com.greatbytes.fastreboot&hl=en
-Better Batter Stats (track all forms of wake locks) (Thanks Sven Knispel)
https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats
-Carat (track and discover battery drain prone apps)
https://play.google.com/store/apps/details?id=edu.berkeley.cs.amplab.carat.android
-Seeder 2.0.0b1 (Thanks Lambgx02)
http://forum.xda-developers.com/showthread.php?p=592
-Cpu Spy (check used mhz and deep sleep usage) (Thanks Brandon Valosek)
https://play.google.com/store/apps/details?id=com.bvalosek.cpuspy
-Universal Initd Support APK (Thanks RyuInferno) (enable check for initd support)
http://forum.xda-developers.com/showthread.php?t=1933849
-Lag Fix(fs-trim) (use trim to trim blocks labeled deleted from storage where blocks are still full) (thanks AuxLV)
http://forum.xda-developers.com/showpost.php?p=37029420&postcount=122
-CrossBreeder Combo MOD (combines three discussed entropy lag/lockup tweaks)
http://forum.xda-developers.com/showthread.php?p=37062006
-Flashable Recoveries (please thank Naddict for this amazing resource)
http://forum.xda-developers.com/showthread.php?p=35741601

galaxys3man30 said:
Reserved
jelly bombed SGS3 jelly bomber 4 life
Click to expand...
Click to collapse
Thank you good sir! Testing now..
firstish!

Great job galaxys3man30, well written, easy to understand.

WIFI TETHER APP
I'M understanding that people are having problems getting it to work i will explain what you have to do there a few steps that you have to do to get it to work
STEP 1: Always make sure you use the wifi tether that is baked into your settings the one in your toggles want work
STEP 2: Open it up and for the those of ya'll that's using it for the first time it will take about 45 seconds before you can use it because its has to get all the permissions from SU so once that is done tap on the wifi sign and start broadcasting the tether
STEP 3: Now you need to hit your menu button on your phone and you will see access control tap on it and enable this will let whatever you wanting to connect to the wifi tether see that it is there
STEP 4: Now go to your laptop,gaming system and etc etc and click on android wifi tether that is your phone
STEP 5: Now go to back to your phone and open up the access control and you should see mac address and ssid there with box's to be check them these are the device trying to connect to your tether now that you have check the box's hit apply at the bottom of the screen and that gives your device access to the internet
Hope this helps everyone that is having a problem with it

I'M always open for suggestions please let me know what ya'll want to have a how to on and i will get one up on it

Thank you to everyone involved to figure out and provide this for us.
Thanks for the great write up. Very easy to follow.
3 questions.
1: What is TPR?
2: What exactly are the process you had us stop used for? Just curious.
3: Do I want to run a particular I/O scheduler? I am using your suggested current Ktoonz governor tweaks.
Thank you again,
Whiteice

Thanks for this! Went ahead and stopped the mpdecision with the mw86 tweaks, Koonservative gov and bfq scheduler. Time to full charge and give it a run

WhiteiceDMSTech said:
Thank you to everyone involved to figure out and provide this for us.
Thanks for the great write up. Very easy to follow.
3 questions.
1: What is TPR?
2: What exactly are the process you had us stop used for? Just curious.
3: Do I want to run a particular I/O scheduler? I am using your suggested current Ktoonz governor tweaks.
Thank you again,
Whiteice
Click to expand...
Click to collapse
TPR is another rom called The Peoples Rom
The 2 files that are renamed r stop because they cause bad battery drain with ktoonsnative gov and the mpdecision is stop because it keeps core 2 going even with the tweaks I have posted so you stop it to keep core 2 running on the tweaks saves battery more less
We have found that bfq is about the best one to use but you can use whatever one you want to you use bud
jelly bombed SGS3 jelly bomber 4 life

Great work Galaxyman. Thanks for the great words! If I see anything i can further suggest ill be sure to chime in.
Paranoid Galaxy S3 on Tapatalk 2

mw86 said:
Great work Galaxyman. Thanks for the great words! If I see anything i can further suggest ill be sure to chime in.
Paranoid Galaxy S3 on Tapatalk 2
Click to expand...
Click to collapse
Thank you sir thank you for all ur hard work
jelly bombed SGS3 jelly bomber 4 life

Thanks galaxy man! Giving this a go...1 question...can I apply the freecharlesmanson I/o scheduler tweaks with mw86 gov settings? Should I just pick one set of tweaks or can I mix it up? Hope I make sense.
Sent from my SPH-L710 using xda app-developers app

Chinkybean said:
Thanks galaxy man! Giving this a go...1 question...can I apply the freecharlesmanson I/o scheduler tweaks with mw86 gov settings? Should I just pick one set of tweaks or can I mix it up? Hope I make sense.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
No you have too bud they can work together n yw n enjoy
jelly bombed SGS3 jelly bomber 4 life

I'm sorry still confused.... So it's okay to use free Charles Manson I/o scheduler tweaks with MW 86 gov settings?
Sent from my SPH-L710 using xda app-developers app

Chinkybean said:
I'm sorry still confused.... So it's okay to use free Charles Manson I/o scheduler tweaks with MW 86 gov settings?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Yea its ok buddy lol
jelly bombed SGS3 jelly bomber 4 life

galaxys3man30 said:
Yea its ok buddy lol
jelly bombed SGS3 jelly bomber 4 life
Click to expand...
Click to collapse
Galaxy, Check Pm.. sent ya some stuff..

To clarify i use the same io scheduler and tunings lol so ha ha guys
Glad this thread is hitting it off so well.
Paranoid Galaxy S3 on Tapatalk 2

thanks a lot galaxy is there anyway to see if mp decision is disabled after doing these tweaks

Awesome. Thanks for making this thread. Keeps me from having to scan thru like 5 others, haha.
---------- Post added at 02:26 PM ---------- Previous post was at 02:25 PM ----------
ryandubbz said:
thanks a lot galaxy is there anyway to see if mp decision is disabled after doing these tweaks
Click to expand...
Click to collapse
Settings > Developer Options > Check "Show CPU usage" > at the top right, see if the process is running. If not, youre good

Great work
Thanks galaxys3man30 for starting this thread, and thanks mw86 for giving me the link. I can attest to the fact that the setting work and stick. Ive been following the several threads prior to this one. Ive use the tunings while tinkering with them, til I based my own off them.

[DISCONTINUED][KERNEL][ICS][JB] dewadgKernel v1.5, now supports JB 2.6!

SORRY FOR THIS BEFORE, I'VE TOTALLY STOPPED TO DEVELOP THIS KERNEL BECAUSE OF MY PHONE GOT HARDBRICKED. THANK YOU FOR SUPPORT ME UNTIL NOW
My kernel comes in ICS version and JB version.These are my very first kernels built by me, I am still learning to develop an Android Kernel, so if it's dissapointing for you, I will try my best to improve it.
For SlimBean users! Move the files in lib/modules to system/lib/modules to fix wifi bug!
Features
Lulzactive governor
SmartAssV2 governor
OndemandX governor
InteractiveX governor
Zen I/O scheduler (Only ICS)
SIO I/O scheduler (Only ICS)
VR I/O scheduler (Only ICS)
zRam capable
CIFS network file system
NFS network file system
Changelog
==JB 2.6==
v1.0 | Initial release
Added Lulzactive governor
Added SmartAssV2 governor
Added OndemandX governor
Added InteractiveX governor
zRam capable
CIFS network file system support
NFS network file system support
I/O schedulers coming soon!
==ICS==
v1.0 | Initial release
Added Lulzactive governor
Added SmartAssV2 governor
zRam swap support
v1.1
Added OndemandX governor
Added InteractiveX governor
Added BFS support (Brain Fu*k Scheduler)
Lulzactive as the default governor now
v1.2
Wifi and wifi tethering bug fix
BFS removed (this causes wifi issue)
v1.3
Added Zen I/O scheduler
Added SIO I/O scheduler
Added VR I/O scheduler
CIFS support
NFS support
v1.4
Wifi bug fixed (again)
CIFS and NFS removed for now, sorry for this
v1.5
Added CIFS network file system again
Added NFS network file system again
Download
==JB 2.6==
v1.0 >> http://www.mediafire.com/?5zu9904mfubkyzj
==ICS==
v1.0 >> http://www.mediafire.com/?4sf7g9rl33puib0
v1.1 >> http://www.mediafire.com/?2hmysyn72udli67
v1.2 >> http://www.mediafire.com/?fd005grg1oq5bzk
v1.3 >> http://www.mediafire.com/?12ttrdii2rz1il4
v1.4 >> http://www.mediafire.com/?kg9x9s26om4lcc9
v1.5 >> http://www.mediafire.com/?im8mz3059u0kv9k
Wipe cache, dalvik cache before flashing. Do fix permissions after flashing.
Thanks to!
Arco68 for his source
Hadidjapri and Filosofi as my teachers
My WhatsApp Developing group
Google to help me find a lot of informations
Everyone who has already testing this kernel

1st
-sent from my awesome phone-

#2nd

3rd
Sent from my GT-I8150 using xda premium

Thank you friends

I got 4th sadly...
Sent using my Smoothie ICS ROM

TiTAN-O-One said:
I got 4th sadly...
Sent using my Smoothie ICS ROM
Click to expand...
Click to collapse
Actually 5th or 6th if we count the OP

aaaaaaaaaaaaaw...
goooood job brow

is it based on arco cm9 rc2 kernel..
Sent from my GT-I8150 using Tapatalk 2

kacanghantu said:
is it based on arco cm9 rc2 kernel..
Sent from my GT-I8150 using Tapatalk 2
Click to expand...
Click to collapse
Yes, it used the latest source from arco's git

mikrotik said:
aaaaaaaaaaaaaw...
goooood job brow
Click to expand...
Click to collapse
Thanks bro

Gaming perfomance improved drastically with the added governor... Thanks! ^^
Sent using my Smoothie ICS ROM

TiTAN-O-One said:
Gaming perfomance improved drastically with the added governor... Thanks! ^^
Sent using my Smoothie ICS ROM
Click to expand...
Click to collapse
Thank you for reviewing and feedback

No prob
Sent using my Smoothie ICS ROM

This is a tuning setting for lulzactive by Droidphile
Code:
[B]i) For battery:-[/B]
echo "90" > /sys/devices/system/cpu/cpufreq/lulzactive/inc_cpu_load
echo "1" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_up_step
echo "2" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_down_step
echo "50000" > /sys/devices/system/cpu/cpufreq/lulzactive/up_sample_time
echo "40000" > /sys/devices/system/cpu/cpufreq/lulzactive/down_sample_time
echo "5" > /sys/devices/system/cpu/cpufreq/lulzactive/screen_off_min_step
This tweak cause lulzactive gradually scale up CPU and rapidly scale down on low load.[/INDENT]
ii) For performance:-
Code:
echo "60" > /sys/devices/system/cpu/cpufreq/lulzactive/inc_cpu_load
echo "4" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_up_step
echo "1" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_down_step
echo "10000" > /sys/devices/system/cpu/cpufreq/lulzactive/up_sample_time
echo "70000" > /sys/devices/system/cpu/cpufreq/lulzactive/down_sample_time
echo "5" > /sys/devices/system/cpu/cpufreq/lulzactive/screen_off_min_step
This tweak cause lulzactive scale up CPU rapidly, polling often and scale down gradually.​
iii) For balanced-performance:-
Code:
echo "90" > /sys/devices/system/cpu/cpufreq/lulzactive/inc_cpu_load
echo "4" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_up_step
echo "1" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_down_step
echo "10000" > /sys/devices/system/cpu/cpufreq/lulzactive/up_sample_time
echo "40000" > /sys/devices/system/cpu/cpufreq/lulzactive/down_sample_time
echo "5" > /sys/devices/system/cpu/cpufreq/lulzactive/screen_off_min_step
This tweak cause lulzactive to poll more often and scale up 4 steps above current frequency, but only at 90% load. CPU is scaled down normally.[/code] :thumbup:
Sent from my GT-I8150 using xda premium​

eryzerz said:
This is a tuning setting for lulzactive by Droidphile
Code:
[B]i) For battery:-[/B]
echo "90" > /sys/devices/system/cpu/cpufreq/lulzactive/inc_cpu_load
echo "1" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_up_step
echo "2" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_down_step
echo "50000" > /sys/devices/system/cpu/cpufreq/lulzactive/up_sample_time
echo "40000" > /sys/devices/system/cpu/cpufreq/lulzactive/down_sample_time
echo "5" > /sys/devices/system/cpu/cpufreq/lulzactive/screen_off_min_step
This tweak cause lulzactive gradually scale up CPU and rapidly scale down on low load.[/INDENT]
ii) For performance:-
Code:
echo "60" > /sys/devices/system/cpu/cpufreq/lulzactive/inc_cpu_load
echo "4" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_up_step
echo "1" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_down_step
echo "10000" > /sys/devices/system/cpu/cpufreq/lulzactive/up_sample_time
echo "70000" > /sys/devices/system/cpu/cpufreq/lulzactive/down_sample_time
echo "5" > /sys/devices/system/cpu/cpufreq/lulzactive/screen_off_min_step
This tweak cause lulzactive scale up CPU rapidly, polling often and scale down gradually.​
iii) For balanced-performance:-
Code:
echo "90" > /sys/devices/system/cpu/cpufreq/lulzactive/inc_cpu_load
echo "4" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_up_step
echo "1" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_down_step
echo "10000" > /sys/devices/system/cpu/cpufreq/lulzactive/up_sample_time
echo "40000" > /sys/devices/system/cpu/cpufreq/lulzactive/down_sample_time
echo "5" > /sys/devices/system/cpu/cpufreq/lulzactive/screen_off_min_step
This tweak cause lulzactive to poll more often and scale up 4 steps above current frequency, but only at 90% load. CPU is scaled down normally.[/code] :thumbup:
Sent from my GT-I8150 using xda premium​
Click to expand...
Click to collapse
for balance-performance
how about if the cpu load is only at 70-80% ?
for performance option. i think pump up 2 stage is already enough and for me that's already been too agressive to go 4 stage pump up
also have a look at sample time. it also gives influence on battery saving or not.
for screen_off_min_step i prefer to set it at high around 7-9 steps to prevent laggy transition from screen off to working state. in my cpu freq, 9 step is equal to 1401MHz​

How do you apply these codes?
Sent using my Smoothie ICS ROM

hadidjapri said:
for balance-performance
how about if the cpu load is only at 70-80% ?
Click to expand...
Click to collapse
I have change the cpu load to 70% hihi. 90% is too much. So, i think 70%-80% is the best choice for balance
Sent from my GT-I8150 using xda premium

Kernel updated ~

[/COLOR]
TiTAN-O-One said:
How do you apply these codes?
Sent using my Smoothie ICS ROM
Click to expand...
Click to collapse
dewadg said:
. You can use this application for tuning the lulzactive governor, this.
Click to expand...
Click to collapse
Sent from my GT-I8150 using xda premium

LG H440N 4G LTE battery & performance tweaks

LG H440N 4G LTE kernel performance tweaks
FINAL VERSION
any other tweaks I find useful will be posted in the "init.d" section
{
"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"
}
​Changelog:
27. December 2015 - added FINAL values. Everyone should use these. "They are nice!" - says Borat.
28. December 2015 - added a changelog. Heh!
29. December 2015 - added a super secret, secret testing zone. I dare you to find it. Note that it's well hidden!
30. December 2015 - new tcp tweaks in init.d section, screenshot how it should look like, Recently tweaks.
31. December 2015 - added a link to a web site with an excellent article on battery care. Added Kernel Adiutor tips by jonathansmith.
1. January 2016 - Added 7+ hours SOT settings in the testing zone. Happy New Year!
3. January 2016 - Since I achieved what I aimed for, I am taking a break from this thread. It will stay open, so feel free to keep on discussing.
18. January 2016 - Testing settings became default settings, with a few changes.
29. January 2016 - Low Memory Killer & swappiness value updated.
BATTERY CARE - a must read for everyone!
Disclaimer:
I am not to be held responsible if anything goes wrong. Simple as that. You do these mods of your own free will.
Warning:
Please, do not report issues or complain about lousy battery times/performance, if you've used any of those pre-made scripts that promise godly battery or performance - they often cause more trouble than they're worth, and are mostly snake oil. And often, you cannot easily undo those changes. If you run a lot of background apps ( for example, five different messengers that cause wakelocks or increased battery usage ), then this guide is not for you. Do not report issues if you've modded your phone with any audio scripts ( like v4a ), xposed, or anything like that! Do not report if you did any permanent system mods, period! These kernel are for CLEAN & STOCK phones, that are rooted ONLY. To summarize, I will not bother replying if you did anything to your phone besides the tweaks I recommend.
Nothing done here is permanent. Everything can be returned to stock in a matter of minutes, if you prefer so, just by uninstalling Kernel Adiutor, unfreezing the bloatware and power cycling the phone.
And hugs to all that pushed the "Thanks!" button. Hell, hugs for everyone!!!
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
BEFORE WE START...
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●​
Must be done before modifying CPU values:
Open your hidden system menu by dialing 277634#*#, go down to Power, find items "High temperature property" and "Thermal mitigation daemon", and set them like this:
High Temp Prop OFF
Disabled
Thermal Mitigation
Disabled
After that, turn phone off, wait 15-20 seconds and turn back on.. The screen will not dim in hot conditions anymore. Benchmarks are higher, games run smoother. And we can tweak our CPUs.
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
KERNEL ADIUTOR SETTINGS
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●​
Apply on boot time is to be decided by the user. Although Kernel Adiutor waits for boot complete, I noticed ( on few occasions ) that it takes more time to apply the settings properly. Why? Who knows. Depends on the number of apps you have running on boot, version of the firmware or how lazy it is on boot... Safest setting is 40 seconds, but 20 should cause no issues and is preferred. 10 can be a problem.
CPU:
CPU Maximum Frequency: 1209
CPU Minimum Frequency: 800
CPU Governor: interactive
*note: Minimum frequency is set to default 800, since Snapdragon 410 draws the same voltage on 200, 400, 533 and 800. That's the reason I set the frequency back to 800 idle. No need to go lower for absolutely no gain in battery life or performance.
CPU Governor Tunables subsection:
above_hispeed_delay: 20000 1094400:40000
go_hispeed_load: 80
hispeed_freq: 998400
min_sample_time: 40000
timer_slack: -1
DEFAULT ( 7+h SOT ) - target_loads: 1 800000:75 998400:80 1094400:85
PERFORMANCE ( smoother, few hours less SOT ) - target_loads: 1 800000:75 998400:80 1094400:80 1152000:85
timer_rate: 20000
max_freq_hysteresis: 40000
*note: Reason for system lags is found in the cheaper and slower memory LG has used for H440N ( my guess is, to cut cost ). You can test that yourself by running various I/O benchmark tools and noting speeds of random and sequential reads/writes. I did not manage to make that better in any way by tweaking the I/O schedulers, be it deadline, cfq or row - even testing some examples from Franco's Dev Team. Seems that it's best to leave it on cfq and cut overhead with the flashtweaks init.d script found later mentioned in this post.
Frequency changes happen VERY fast. So fast that CPU widgets or passive frequency readers have a lousy time keeping up. Only values you can trust are found in Kernel Adiutor's Frequency Table.
Those values found above are the best possible values for H440N's CPU for performance & battery saving, and I stand by them. If anyone else cares to try and do some tweaking to improve on those, by all means, please do so. If in the future I decide to add new CPU values, they will be strictly performance based, hence no battery saving.
Reason for the CPU frequency sticking to 1209600 is caused by the LG Home launcher. It contains a system call where, if you open up your apps drawer, it immediately ramps up the frequency to the max for almost 8 seconds or until you close the app drawer! That sucks, and is a lazy way for LG to provide smooth app drawer opening/swiping/closing! Bad LG, bad!!!
Two ways to solve that:
1. Spend less time listing through your apps drawer, since the frequency drops as soon as you stop swiping through it, or...
2. Freeze LG Home and use another launcher ( like Nova or Apex ), if you don't mind losing Double Tap to Wake, or work around that problem with launchers that support double tap gesture and link that gesture with a screen off app like this. Do not freeze any LG Home system apps, besides Easy Home. No need. System will automatically kill the unneeded launcher. Just follow my frozen bloatware list. Nothing more, nothing less.
Low Memory Killer values ( top to bottom ):
48
60
72
84
96
120
Virtual Memory:
vfs cache pressure: 100
swappiness: 80
Build prop Editor
dalvik.vm.heapsize: 174m
dalvik.vm.heapminfree: 512k
dalvik.vm.heapstartsize: 8m
dalvik.vm.heapgrowthlimit: 128m
dalvik.vm.heaptargetutilization: 0.75
dalvik.vm.heapmaxfree: 8m
*note: Dalvik tweaks are based upon Intel's recommended Dalvik tweaks for Lollipop phones with 1 GB RAM and xhdpi displays.
Init.d
1. Turn on "Emulate Init.d" and click that big "+" to create a new script.
2. Name the new script: flashtweaks
Contents of the "flashtweaks" script are:
Code:
#!/system/bin/sh
echo 0 > /sys/block/mmcblk0/queue/nomerges;
echo 2 > /sys/block/mmcblk0/queue/rq_affinity;
echo 512 > /sys/block/mmcblk0/queue/nr_requests;
echo 0 > /sys/block/mmcblk0/queue/iostats;
echo 0 > /sys/block/mmcblk0/queue/add_random;
echo 0 > /sys/block/mmcblk1/queue/nomerges;
echo 2 > /sys/block/mmcblk1/queue/rq_affinity;
echo 512 > /sys/block/mmcblk1/queue/nr_requests;
echo 0 > /sys/block/mmcblk1/queue/iostats;
echo 0 > /sys/block/mmcblk1/queue/add_random;
2. Name the new script: tcptweaks
Contents of the "tcptweaks" script are:
Code:
#!/system/bin/sh
#more reasonable tcp tweaks
echo 1 > /proc/sys/net/ipv4/tcp_low_latency;
echo 0 > /proc/sys/net/ipv4/tcp_timestamps;
echo 900 > /proc/sys/net/ipv4/tcp_keepalive_time;
echo 5 > /proc/sys/net/ipv4/tcp_keepalive_probes;
echo 156 > /proc/sys/net/ipv4/tcp_keepalive_intvl;
Example of properly added scripts. I just named them differently:
Ignore the "99SuperSUDaemon" script unless you know what it is. It's not needed for our tweaks, and if you don't have it, it's perfectly fine.
Here are some screenshots on clearing / checking Kernel Adiutor's Frequency Table, by our fellow XDA member jonathansmith:
How to clear timers?
Check correct frequency usage.
Now, since you've finished with Kernel Adiutor, power cycle the phone. You're almost done. All that's left are:
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
OTHER SETTINGS
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●​
In Developer options, set animation scale values to OFF.
In Settings / Display / Brightness enable Night Brightness. Who needs anything over 0% brightness from midnight to six in the morning?
Visit Play Store and install these apps:
Recently by Chainfire
Trimmer (fstrim)
Recently! settings ( preferred ):
Age limit: No limit
Entry limit: 12
Apply on boot: Yes
Freeload: Checked ( yeah, we're cheapskates )
EVERYTHING ELSE DISABLED / UNCHECKED.
Recently! settings ( much faster version ):
Age limit: Running apps only
Entry limit: Running apps only
Apply on boot: Yes
Freeload: Checked ( yeah, we're cheapskates )
EVERYTHING ELSE DISABLED / UNCHECKED.
Do a "Clear all" in recent apps list after a reboot. It will make things faster. Believe me.
As for Trimmer (fstrim), run that every week or so, on "/data", "/cache" and "/system". No need to run it daily.
Apps frozen with Titanium Backup ( freeze bloatware, do not delete it - you'll thank me later ):
Chrome
Drive
E-mail
EasyHome
Gmail ( I am using Aqua Mail. )
Google Play Books
Google Play Games
Google Play Movies
Google Play Music
Google Play Newsstand
Google Search
Google+
Hangouts
HTML viewer ( do not disable if using stock browser or Chrome )
Internet ( I am using this version of Opera. It's the best one.
LG Keyboard ( disable only if already using another keyboard. I am using Smart Keyboard. )
LG Keyboard Black Theme ( disable only if already using another keyboard. I am using Smart Keyboard. )
LG MLT ( disable LG MLT in the hidden service menu before freezing it! Menu code is 277634#*# )
Live Wallpaper
Music ( both widget and app - I am using PlayerPro. )
Trusted Face
Weather
Weather Theme
WeatherPlatform
Do not touch anything else! Don't say I did not warn you.
If you prefer blocking ads on web sites, like I do... then download AdAway from XDA forum, and enjoy ad-free surfing.
That's it. Have fun, and enjoy your buttery smooth phone. One of this year's best-buy smartphones. Too bad it doesn't get the attention it deserves. Really, an unsung hero if there ever was one.
Although there are a lot of other CPU tweaking values throughout the thread, these values are the standard ones you should use. Other ones are experiments, or just plain testing values.
H440N is compatible with DriveDroid - in case you want to boot an operating system or a Linux distro off of it.
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
SUPER SECRET, SECRET TESTING ZONE
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
by WellHidden™​
THESE SETTINGS BECAME THE DEFAULT SETINGS. SEE ABOVE.
With the latest test settings I achieved 7+ hours SOT. And yes, it can be done! You got the proof below.
Everything else besides these TESTING values below stays the same as in FINAL values ( dalvik, init.d, etc. ).
CPU:
CPU Maximum Frequency: 1209
CPU Minimum Frequency: 400
CPU Governor: interactive
CPU Governor Tunables subsection:
above_hispeed_delay: 20000 1094400:40000 1152000:20000
go_hispeed_load: 82
hispeed_freq: 998400
min_sample_time: 40000
timer_slack: -1
target_loads: 72 998400:82 1094400:85 1152000:86 1209600:90
timer_rate: 20000
max_freq_hysteresis: 40000
Virtual Memory:
Swappiness: 60 ( I recommend 100, but go back to 60 if you feel the memory gain is not worth a slight performance drop. )
Vellamo 3.2 scores:

My phone was originally set at frequency max 1200 and min 1200. After all the changes you suggest, do you set the min cpu frequency at 200 or leave it on 1200?

polfrank said:
My phone was originally set at frequency max 1200 and min 1200. After all the changes you suggest, do you set the min cpu frequency at 200 or leave it on 1200?
Click to expand...
Click to collapse
Min 200 Max 1200
Interactive / Noop
Other values as suggested.
But, damn. Those original settings must've drained the battery like hell... Are people at LG crazy?
EDIT: Sometimes, SetCPU will show the lowest frequency as 1200, but don't worry. Set it to 200, and verify it's at 200 in Times in state on the last SetCPU tab. It seems to be a bug in the app. That's why I used Kernel Adiutor.

ondemand + noop + lmk set to agressive and the phone flies like never before! looks like constant 60 fps. Thanks op!

Always glad to help out. Like I mentioned before, this phone has good hardware and is capable of stellar performance. Only problem is LG did not pay much attention on the tweaking side of things.
It's easy for them to tweak flagships
EDIT: Just found out about another gem! The app is called Recently by chainfire.
Installed, tried and it's marvelous even on default settings. I encourage everyone to try it. It's what Recent cards were supposed to be, in my opinion.

So I installed Busybox and Kernel Adiutor, set CPU min frequency to 200 Mhz, cpu governor to interactive and and I/O scheduler to noop. I've set both to apply on boot. Is that everything I need to do?

Fobos531 said:
So I installed Busybox and Kernel Adiutor, set CPU min frequency to 200 Mhz, cpu governor to interactive and and I/O scheduler to noop. I've set both to apply on boot. Is that everything I need to do?
Click to expand...
Click to collapse
It is, if you don't mind the default Interactive values. Otherwise, go a bit lower to "CPU Governor Tunables". Click that and set values as mentioned in first post. Those give a much better battery life.
After that, my recommendation is to visit the Low Memory Killer section and set that to Aggressive and apply on boot.
I can say that, after a bit of tweaking, this phone rocks! Glad to have bought it. Still hoping for a unlocked bootloader and maybe a CM port

Can you please take a screenshot of your CPU Governor Tunables section? I'm not completely sure that I did it right.

No problem, my good man. Here they are:
http://imgur.com/yDbXHE3
http://imgur.com/3uDi04u

holy ..! this really does make a difference. is it ok if i set cpu to "performance" and dont mess anything else with it? i dont care about battery life that much. cuz it seems that with agressive setting for ram, and changing to "noop" made wonders for me performance wise

Performance governor forces 1200, so that's not desirable.
For the best performance with lowest idle, set it to Ondemand / Noop. You will lose a bit more battery with those, but the phone will fly.
Otherwise, set as I've set it. Tweaked interactive.

userspace,powerspace hotplug and performance is what i have in karnel auditor.. which one should i choose then? tyvm!
p.s. thanks again for these tips man

That's strange. Are you using the LG Spirit H440N or some other variation?
See here ( list of governors ):
http://imgur.com/hxZOoDz

ah right. that could be a reason.. i use 3g version, with mediatek cpu

* moved to first post *

Tomo123 said:
Performance governor forces 1200, so that's not desirable.
For the best performance with lowest idle, set it to Ondemand / Noop. You will lose a bit more battery with those, but the phone will fly.
Otherwise, set as I've set it. Tweaked interactive.
Click to expand...
Click to collapse
amazing speed and multitasking (with Recently), thank you for this

Can you help me with target loads? Is this ok?
Sent from my LG-H440n using Tapatalk

String seems to be written ok, but my guess is it will clash with go_hispeed_load value.
If go_hispeed_load has a value of 85, then your initial value in target loads can't be "1". It must be higher than 85.
We're using our hispeed frequency ( 400000 ) as idle. It often drops to 200, so I see no reason of adding 200 to target loads.
Did you check out my post above?
Also, take a look at my KA frequency table:
http://imgur.com/BikoQk2

It seems that ive messed up something. Now my phone wont go deepsleep. This is the result over night.
Sent from my LG-H440n using Tapatalk

Can you make a screenshot of your target loads. Im having a hard time making it work. Performance is on point but i get a lot of battery drain.
Sent from my LG-H440n using Tapatalk