Prerequisites:

Explanation:

Instructions:

Code: # MultiTasking Tweaks ro.config.dha_cached_max=15 ro.config.dha_cached_min=4 ro.config.dha_empty_max=36 ro.config.dha_empty_min=9 ro.config.dha_empty_init=36 ro.config.dha_lmk_scale=0.545 ro.config.dha_update_max_count=5 ro.config.dha_step=2 ro.config.dha_th_rate=1.4 ro.config.dha_defend_th_level=0 ro.config.64bit_lmk_enable=true ro.config.sdha_apps_bg_max=70 ro.config.sdha_apps_bg_min=8 ro.config.dha_ils_enable=true ro.config.dha_ils_dyna_lmk=true ro.config.dha_ils_rate=1.5

Video Tutorial

Since we've been talking about this pretty extensively in a different thread I figured I would make a new thread for discussing, troubleshooting and attempting to improve the ram management issue on the S6.Hopefully some good will come of thisSo far this Is what we've got:Should work on all variants including the edge and possible on other Samsung devices.Thanks to @ mikeyinid for finding these and @ s.rapp for answering questions, and making the instructions easier to understandAnd anyone else who I may have missed who helped contribute.-A rooted device-A root file explorer/manager app-A backup of your original build.prop to be safe(From @ mikeyinid Here is a quick rundown on how this came about, and what we actually know.Since I purchased the S6 on release day, I've been messing with certain things, as you can see from the ROM I posted, Looper(shameless plug). Debloating Samsung apps really helped with battery life and I was pretty happy with the results. But like so many other people, I didn't understand why my S6 killed apps so aggressively. Initially I thought it might be the memory leak we all know so much about in 5.0. So, I did a little research and found the patch for that. While it did help keep the device stable over time, apps were still being killed with no prejudice. All this time I noticed really useless services running in the background, often stuff I'd never even opened. I studied LMK and started messing with those settings. After a month of trying everything I could find documented, I was ready to give up. Yesterday I was looking through the services.jar smali for the 37,875th time and realized the DHA referenced in there has to have something to do with memory management. I kept overlooking it because I hadn't seen mention of it anywhere else. I am no smali guru, as some of you know. But it was pretty obvious DHA was influencing memory management to some extent. Samsung, although leaving us in the dark on this, was kind enough to give us props to set the values for DHA. I pulled a few that seemed relevant, added them to my build.prop, and what do you know. For the first time in almost two months of tinkering, I saw an improvement in the way my device was managing memory.The thing everyone needs to understand; I have no clue what DHA is. It overrides every aspect of Googles LMK and seems to do so in a way that makes more sense. I'm sure someone with more knowledge than myself will be able to tune this to the point the S6 will be the multi-tasking champ. There are several other props in the smali that are probably useful. I will try to get them all with their default values posted today. This has been pretty exciting for me, I spent way to much time trying to figure out the issue to not make some sort of progress. I hope you guys enjoy the tweaks, and I hope it helps sway those of you on the fence about keeping this device to stay. It's only gonna get betterFirst find your build.prop. This is located in /system. to get to /system you need to go to the root directory using a file explorer and then go to the system folder. The build.prop will be in there. You can also use and app such as build.prop tweaker but its a bit harder (imo)In your build.prop scroll to the very bottom and paste this in:Now you need to find and remove any duplicate build.prop lines which may cause an issue. So look through the build.prop and remove any lines that look like these(Not the ones you just added at the bottom!):ro.config.dha_cached_max=ro.config.dha_empty_max=ro.config.dha_th_rate=ro.config.dha_lmk_scale=Finally reboot your device and report back here!(courtesy of @ Thin_Bezel A note from @ mrapp "The major addendum here seems to be that when using this build.prop apps like Chrome and and those calling webpages via Webview (Tinfoil for Facebook) still suck. The kernels being tested at the moment don't appear to have this issue, so if you're capable of flashing kernels I personally recommend checking out the Vindicator thread if you're on T-Mobile/W8 or UniKernel (universal) if you're on any other device. UniKernel tests may or may not be edge friendly, so always make a backup. Lots of people have gotten in to trouble today. Don't be one of them!"Please note we are constantly experimenting with different values so these are subject to be updated rather frequently