I noticed a difference with mm memory management seems to handle multitasking much betterBy the content of your post, you never gave any indication of what you actually know and don't. The answer is no.
And BTW MM is out and all 5.1.1 development is discontinued. This thread will remain open until MM is released for some other variant I "might" consider supporting. I guarantee nothing though.
MM kernel has much better RAM management, so watch out for those LL "tweaks" screwing things up. A lot of VM and LMK values have changed and those still continuing to put those in MM ROMs / kernels are not improving anything.
Not for n920t but n920c is out official firmware Cambodian though
I always thought you guys would get it firstCambodia, Korea, and Iraq so far...
---------- Post added at 11:20 PM ---------- Previous post was at 11:19 PM ----------
I'm very much anticipating the t variant release! I said they wouldn't release mm for existing tmo devices until after release day for the s7's....
So I'll wait for it instead of dealing with the call audio issues that have been around on ported mm from other variants- i feel like i read where uita solved some audio issue but i don't think it was the same thing? I haven't been following closely enough smh
It was because of the leaked firmware thats why i thought n920t would get it i mean they had the firmware by now they should have tested and fine tuned everything
[COLOR="Red"]PLEASE SHOW RESPECT TO ACTUALLY [COLOR="PURPLE"][B]READ POSTS #1-3[/B][/COLOR] [URL="http://forum.xda-developers.com/announcement.php?a=81"][B]XDA RULE #1 "SEARCH BEFORE POSTING"[/B][/URL] (GOOGLE, XDA & THREAD), IF YOU DON'T LIKE A UP-FRONT "MATTER OF FACT" APPROACH, [B]THEN DON'T BOTHER POSTING[/B]. [/COLOR]
* Based on official Samsung source: [URL="http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=n920"]Samsung OSRC[/URL] * ramdisk source: [INDENT][COLOR="red"]N920C/CD/I/G[/COLOR] XXU2APA2 [COLOR="red"]N9200[/COLOR] ZCU2AOL2 [COLOR="red"]N9208[/COLOR] XXU2AOL1[/INDENT] * Compiled with Linaro gcc-linaro-4.9-2015.02-3-x86_64_aarch64-linux-gnu * Linux 3.10.96 * [COLOR="red"]AUTO-ROOT binary v2.52[/COLOR] & Install busybox v1.24.1-Dorimanx * [COLOR="Red"]KNOX WARRANTY VOID: 1[/COLOR] * [COLOR="red"]SELinux PERMISSIVE[/COLOR] (for Titanium Backup and other apps to work correctly) * adb insecure * stock dt.img * init.d script support (drop in script & set permissions to 755 or 777 and reboot) * [COLOR="red"]DEEP SLEEP FIX[/COLOR] * [COLOR="red"]IN-CALL REBOOT BUG "FIX"[/COLOR] * Possible Screen Mirroring / AllShare Cast fix * Secure storage = false (should prevent WIFI settings & passwords wiping on reboots) * RAM management tweaks * GearVR [U]reported[/U] working (depends on ROM/firmware version installed) * [B]Synapse app support[/B] for many kernel configurations + more !! * Many descriptions are in the app ! If you require more info, don't be lazy, please [B]SEARCH[/B] like I did ;)
[COLOR="Red"]* Under-volting can cause instability * Over-clocking can cause freeze/reboot, heat & damage to CPU, GPU or other hardware * Any customizations may void warranty * May not be suitable for your device or customizations * UpInTheAir is NOT responsible, the person you see in the mirror is !![/COLOR]
1. DEVICE MODEL ? 2. ROM and firmware version (build number, boot-loader etc) ? 3. EXACT steps taken to reproduce YOUR issue 4. Screen-shots (if applicable) 5. Did you read Posts #1-3 completely? 6. Did you search the thread, XDA or GOOGLE? 7. Did you follow the install instructions EXACTLY? 8. What was your previous kernel? 9. Do you have any other known kernel tweaking apps, scripts or mods? ([B]remove them[/B]). [COLOR="Red"]This includes Xposed etc[/COLOR] 10. Try older kernel (if available) 11. Factory reset ? 12. Try latest stock [B]UNMODIFIED[/B] firmware (without custom ROM - if you have installed) and factory reset 13. Delete your ROM BusyBox (kernel uses it's own in /sbin)
This feature allows to have two different intervals for dirty page
writebacks and to dynamically manage them when the system has been
resumed (it's active) or when has been suspended.
Three new procfs parameters are exposed inside /proc/sys/vm path:
- dynamic_dirty_writeback is the activation status of this feature,
set 1 to enable it, set 0 to disable it and use the standard behaviour
- dirty_writeback_active_centisecs is the interval for the dirty page
writebacks when the system is active (screen on)
- dirty_writeback_suspend_centisecs is the interval for the dirty page
writebacks when the system is suspended (screen off)
This feature is in part inspired on Francisco Franco's patch: