Database Info

[KERNEL][3.0.101][JB][PMEM] K^Kernel 3.0.101 v3.1 for JB 4.2.2 and JB 4.1.2 [EOL]

{
"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"
}
In this thread you may find my customized kernel 3.0.x for JB 4.1.2 and JB 4.2.2 rom (CM10, CM10.1 and derivatives) that use PMEM memory allocations.
I hope it will be useful, and ensures better performance and battery life.
Of course, your feedback, as always, are welcome and certainly valuable.
The main features are the following:
- Kernel 3.0.x
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my custom Linaro 4.8.3-2013.11 toolchain optimized for Cortex-A8
- Built with Cortex-A8 and NEON VFP optimization flags (both kernel and modules)
- Built with -O3 optimization flag (both kernel and modules)
- CPU overclockable up to 1824 MHz
- CPU frequencies undervolted (UV version) or extremely undervolted (EXUV version)
- CPU voltage control VDD sys interface (click for more details)
- 360MB, 370MB or 390MB of free RAM
- Init.d support
- Fast Charge support (default disabled, click for more details)
- Battery Life eXtender support (default disabled, click for more details)
- Ram Console support (click for more details)
- Backlight Notification v9 (BLNv9) (click for more details)
- USB OTG support (if also implemented on rom side)
- Customizable vibration intensity (click for more details)
- Lowered display panel voltage
- Lowered touchscreen voltage
- Lowered wifi voltage
- Lowered swappiness (60 -> 45)
- Increased CPU frequency during boot
- Optimized AES and SHA1 routines for ARM cpu architecture
- Fixed 100% battery notification after charger unplug
- Increased audio volume on board side
- Con Kolivas' CK3 Tweaks
- Optimized SLUB memory allocator
- Optimized ARM RWSEM (read/write semaphore) algorithm
- Optimized asynchronous I/O latency on solid state disks
- Optimized string and memcopy libs
- Disabled Gentle Fair Sleepers for better UI performance
- Filesystem dynamic read-ahead (based on disk size)
- CIFS support on boot
- Fast Random generator (frandom) support (click for more details)
- New display drivers from Samsung Galaxy SII
- Updated light sensor driver and display driver light sensor changes
- Phantom key presses filter (click for more details)
- Dynamic FSync v1.2 (click for more details)
- Dynamic dirty page writebacks (click for more details)
- VM tweaks for performance and less battery consumption
- Revised LowMemoryKiller parameters for better performance (click for more details)
- Customizable timeout for touchkeys backlight after a key press or touchscreen press (click for more details)
- Customizable activation status of touchkeys backlight on touchscreen press (click for more details)
- Timer slack controller (click for more details)
- Dynamic management of the minimal timer slack value during suspend/resume (click for more details)
- LowMemoryKiller management of not killable processes (click for more details)
- exFAT support
- Additional TCP Congestion algorithms
Available CPU governors:
- Adaptive
- BrazilianWax
- Conservative
- Hyper
- Intellidemand
- Interactive
- InteractiveX
- LionHeart
- LulzActive
- OnDemand (default)
- OnDemandX
- Performance
- Powersave
- SmartAssV2
Available I/O schedulers:
- BFQ
- CFQ
- Deadline
- Noop
- ROW (default)
- SIO
- V(R)
Kernel Downloads for JB 4.1.2:
K^Kernel JB-4.1.2 Mediafire Folder
[QRCODE]http://www.mediafire.com/?l9vakf1dadf37[/QRCODE]
- v3.1 -
for CM 10
and the other roms based on latest CM 10​
Kernel Downloads for JB 4.2.2:
K^Kernel JB-4.2.2 Mediafire Folder
[QRCODE]http://www.mediafire.com/?pd9zpuideo7zm[/QRCODE]
- v3.1 -
for ADC CM 10.1 Release 9
and the other roms based on this CM 10.1
- v3.0 -
for ADC CM 10.1 Release 8
and the other roms based on this CM 10.1​
Howto install the kernel:
1) Download the preferred kernel zip file to sdcard or external sdcard
2) Reboot to recovery mode
3) Flash the kernel zip file
4) Wipe cache and dalvik cache
5) Fix permissions
6) Reboot the system
Kernel sources (on GitHub):
Development branch of K^Kernel 3.0 for JB 4.1.2
Development branch of K^Kernel 3.0 for JB 4.2.2​
Useful info:
- Special features and sysfs settings
- Frequently asked questions
​
Rom and kernel 3.0.x known problems:
- For the builds with 390MB of free RAM, the camera works and the video recording works only in 480p mode
- Possibile graphical glitches in camera preview
- Wifi Tethering doesn't work on new CM 10.1 roms that use 3.4 kernels
Tables:
​
Changelog:
Code:
[B]29/11/2013 - K^Kernel v3.1 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.101
- Sources synched with jb-3.0 repo of Arco68 and ADC Team for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 and ADC Team for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.8.3-2013.11 toolchain optimized for Cortex-A8
- fs/sync: Make sync() satisfy many requests with one invocation (credits to Paul E. McKenney)
- usb: gadget: mass_storage: added sysfs entry for cdrom to LUNs (credits to FrozenCow)
- Update default and custom defconfigs for additional TCP Congestion algorithms (credits to Christopher83)
- add exfat support (credits to radu)
- Update default and custom defconfigs for exFat support (credits to Christopher83)
- acpuclock-7x30: Raised some standard UV and stock voltages for high OC cpu frequencies (credits to Christopher83)
- input: Updates to Phantom Key Presses filter (credits to Christopher83)
- softirq: reduce latencies (credits to Eric Dumazet)
- fs: vfat: reduce the worst case latencies (credits to xiaogang)
- jiffies conversions: Use compile time constants when possible (credits to Joe Perches)
- Makefile: Use -fno-inline-functions to build with Linaro GCC 4.8 toolchains (credits to Christopher83)
Additional commit for JB 4.1.2 only
- msm: display: Prevent fb suspend in charging mode for ancora only (credits to Christopher83)
Additional commit for JB 4.2.2 only
- qt602240_ts: updated touchscreen driver in according of Multi-touch protocol (credits to CastagnaIT)
[B]27/10/2013 - K^Kernel v3.0 for JB 4.2.2[/B]
- Kernel 3.0.101
- Sources synched with cm-10.1_3.0 repo of Arco68 and ADC Team for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.10 toolchain optimized for Cortex-A8
- Resolved problems of magnetic, proximity and orientation sensor (credits to CastagnaIT)
- gp2a_proximity: readded wakelock is necessary to avoid problems with answer calls and some cleanups (credits to CastagnaIT)
[B]10/10/2013 - K^Kernel v2.9 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.99
- Sources synched with jb-3.0 repo of Arco68 and ADC Team for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 and ADC Team for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.09 toolchain optimized for Cortex-A8
- New bootsplash logo
- mm: remove compressed copy from zram in-memory (credits to Minchan Kim)
- lib/lzo: Rename lzo1x_decompress.c to lzo1x_decompress_safe.c (credits to Markus F.X.J. Oberhumer)
- lib/lzo: Update LZO compression to current upstream version (credits to Markus F.X.J. Oberhumer)
- lib/lzo: huge LZO decompression speedup on ARM by using unaligned access (credits to Markus F.X.J. Oberhumer)
- ARM: 7668/1: fix memset-related crashes caused by recent GCC (4.7.2) optimizations (credits to Ivan Djelic)
- ARM: 7670/1: fix the memset fix (credits to Nicolas Pitre)
- msm: vidc: return error in case of init failure (credits to Pushkaraj Patil)
- Switched to SIO I/O scheduler
- Fixed change conflicts between custom settings and init.d settings during boot
- Possibility to disable the redirection to frandom number generator
Additional commits for JB 4.1.2 only
- Revert "video: msm: Fix LCD enable sequence for ancora lcd rev.3" (credits to Arco68)
- msm: display: Prevent fb suspend in charging mode for all (credits to Arco68)
[B]11/09/2013 - K^Kernel v2.8 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.95
- Sources synched with jb-3.0 repo of Arco68 and ADC Team for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 and ADC Team for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.08 toolchain optimized for Cortex-A8
- Bluetooth: Fix for the l2cap layer crashes while turning OFF BT (credits to Nitin Shivpure)
- Enable setting security contexts on rootfs inodes (credits to Stephen Smalley)
- ariesve_sensors: updated all sensors to match with the new opensource libsensors for CM 10.1 kernel (credits to CastagnaIT)
- board_ariesve: cleanup mdp_pdata and added missing mem_hid (credits to CastagnaIT)
- net: ipv6: add missing lock in ping_v6_sendmsg (credits to Lorenzo Colitti)
- net: ipv6: fix wrong ping_v6_sendmsg return value (credits to Lorenzo Colitti)
- msm_fb: Correct R and G offsets for correct mapping (credits to Jeevan Shriram, thanks to Arco68)
- USB: gadget: Cleanup boot-up message with default usb composition (credits to Mayank Rana, thanks to Arco68)
- cpufreq: interactive: fix show_target_loads and show_above_hispeed_delay (credits to Minsung Kim, thanks to Arco68)
- CIFS support on boot
[B]05/08/2013 - K^Kernel v2.7 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.89
- Sources synched with jb-3.0 repo of Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.07 toolchain optimized for Cortex-A8
- Revert "ARM: 7765/1: perf: Record the user-mode PC in the call chain.", this should solve the battery charging failures (credits and thanks to Arco68)
[B]25/07/2013 - K^Kernel v2.6 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.87
- Sources synched with jb-3.0 repo of Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.07 toolchain optimized for Cortex-A8
- msm: msm_fb: remove mmio access through mmap (credits to Manoj Rao, thanks to Arco68)
- writeback: Fix occasional slow sync(1) (credits to Jan Kara)
- cfq-iosched: Fix null pointer dereference (credits to Sujit Reddy Thumma)
- staging: android: timed_gpio: Fix unreg order (credits to Olav Haugan)
- msm: cpufreq: Only apply driver limits for scaling_min/max_freq writes (credits to Deepak Katragadda)
[B]15/07/2013 - K^Kernel v2.5 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.86
- Sources synched with jb-3.0 repo of Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.07 toolchain optimized for Cortex-A8
- Fixed lost of the touchscreen configuration after suspend (credits and thanks to CastagnaIT)
- LowMemoryKiller management of not killable processes (implemented by me, thanks to CastagnaIT for the original idea of this feature)
[B]07/07/2013 - K^Kernel v2.4 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.85
- Sources synched with jb-3.0 repo of Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.06 toolchain optimized for Cortex-A8
- Timer slack controller (credits to Kirill A. Shutemov, thanks to Boype and Stuffynet)
- Dynamic management of the minimal timer slack value on suspend/resume
[B]30/06/2013 - K^Kernel v2.3 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.84
- Sources synched with jb-3.0 repo of Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.06 toolchain optimized for Cortex-A8
- Updates and fix to Interactive CPU governor (credits to Lianwei Wang, thanks to Arco68)
- dpram: Some minor changes from ics-3.0 (credits and thanks to Arco68)
- Revert Temporary workaround for flicker brightness after screen on
- Fixed flicker brightness when turning on the screen (credits and thanks to CastagnaIT)
- Fixes to graphic drivers (credits to Suman Tatiraju, thanks to Arco68)
- Fixes to ipv6 (credits to Hannes and Lorenzo Colitti, thanks to Arco68)
- Other minor fixes (from CAF sources)
- CK3 tweaks (credits and thanks to Con Kolivas)
- Increased battery check interval from 5 seconds to 15 seconds
- New static Cyanogen boot logo (credits and thanks to Stefano187)
[B]24/06/2013 - K^Kernel v2.2 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.83
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.06 toolchain optimized for Cortex-A8
- Updates and fixes to Interactive CPU governor (credits to Todd Poynor and Minsung Kim, thanks to Arco68)
- Squashed update of BFQ-V6 to BFQ-v6r2 (thanks to Arco68)
- Corrected an unmanaged gamma for autobrightness
- Customizable timeout of touchkeys backlight after a key press
- Customizable activation status of touchkeys backlight on touchscreen press
- Fix for discharging battery issue while charging to 100% (credits to Skywalker01)
- Fix to dynamic fsync to don't disable fdatasync (credits to Faux123)
- Enabled CleanCache
[B]10/06/2013 - K^Kernel v2.1 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.81
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.05 toolchain optimized for Cortex-A8
- Re-added optimized string and memcopy libs (credits and thanks to Miao Xie)
- Dynamic Fsync (credits and thanks to Faux123)
- Dynamic dirty page writebacks
- VM tweaks for better performance and less battery consumption
- Revised LowMemoryKiller parameters for better performance
[B]27/05/2013 - K^Kernel v2.0 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.80
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.05 toolchain optimized for Cortex-A8
- Remove a not needed mmc_power_off (credits and thanks to Arco68)
- Some display fixes (credits and thanks to Arco68)
- Some changes to the touchscreen power-on routine
- Fixed display regulators init
- Updated LCD regulator (credits and thanks to CastagnaIT)
- Power management support on S6E63M0 display driver
- Fixed double activation of the regulators of the display (credits and thanks to CastagnaIT)
- Lowered Vibetonz voltage
- Adjusted some voltage regulators
- Restored min read ahead (from 32 kbytes to 16 kbytes)
- Other fixes and optimizations to RWSEM (read and write semaphore) taken from 3.10 kernel
[B]13/05/2013 - K^Kernel v1.9 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.78
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.3-2013.04 toolchain optimized for Cortex-A8
- Removed pop-up noise at the end of power off sequence (credits and thanks to CastagnaIT)
- Fixed bluetooth files transfer, the issue was present only on CM 10.1, ported from 3.4 kernel branch (credits and thanks to Arco)
- Changes to fix the suspend problems caused by BLN
[B]28/04/2013 - K^Kernel v1.8 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.75
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.3-2013.04 toolchain optimized for Cortex-A8
- Added Intellidemand CPU governor (credits and thanks to Faux123)
- Imported the new LowMemoryKiller from 3.4 kernel
- Changed the debug level of the LowMemoryKiller from 2 to 1
- Added Voku and Dorimanx tweaks to LowMemoryKiller (credits and thanks to them)
- Removed PMEM reservation for audio (credits and thanks to Arco68)
- Updated light sensor driver and display driver light sensor changes (credits and thanks to CastagnaIT and Ivendor)
[B]19/04/2013 - K^Kernel v1.7 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.74
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.3-2013.04 toolchain optimized for Cortex-A8
- Phantom key presses filter, changed the default home_allowed_irqs parameter from 2 to 4
- Disabled Gentle Fair Sleepers for better UI performance
- Lowered touchscreen voltage
- Added BrazilianWax CPU governor
- Various changes and updates to ARM RWSEM (read/write semaphore) algorithm
- New available memory configuration with 390MB of free RAM (camera works, video recording works only in 480p mode)
[B]15/04/2013 - K^Kernel v1.6 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.73
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.3-2013.04 toolchain optimized for Cortex-A8
- Phantom key presses filter (new module developed by me)
- New display drivers s6e63m0 from Samsung Galaxy SII (credits and thanks to CastagnaIT)
[B]06/04/2013 - K^Kernel v1.5.5 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.72
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Fixed WEP Connections (credits and thanks to Ivendor)
[B]02/04/2013 - K^Kernel v1.5 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.71
- Sources synched with jb-3.0 repos of Ivendor and Arco68 for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 for JB 4.2.2 (CM 10.1) kernel builds
- Revised PMEM allocations to preserve more memory for Surface Flinger
- Removed optimized lib/string and lib/memcopy, cause performance issues
- Added Adaptive and Hyper CPU governors
[B]26/03/2013 - K^Kernel v1.4.6 for JB 4.1.2 and JB 4.2.2[/B]
- Sources synched with jb-3.0 repos of Ivendor and Arco68
- Backlight Notification v9 (BLNv9) (credits and thanks to CastagnaIT)
- Customizable vibration intensity (credits and thanks to CastagnaIT)
[B]24/03/2013 - K^Kernel v1.4.5 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.70
- Sources synched with jb-3.0 repos of Ivendor and Arco68
- Fixed performance issues
- Ram Console support (credits and thanks to Ivendor)
- Different builds with RAM Console support or without (seems to be more responsive)
[B]18/03/2013 - K^Kernel v1.4 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.69
- Sources synched with jb-3.0 repos of Ivendor and Arco68
- Built with my latest custom Linaro 4.7.3-2013.03 toolchain optimized for Cortex-A8
- Optimized SLUB memory allocator (thanks to CastagnaIT)
- Optimized ARM RWSEM algorithm (credits and thanks to Ashwin Chaugule)
- Optimized lib/string and lib/memcopy (credits and thanks to Miao Xie)
- Filesystem dynamic read-ahead (based on disk size) (credits and thanks to Chad Goodman)
- Fast Random generator support (frandom) (credits and thanks to Eli Billauer)
- Optimized asynchronous I/O latency on solid state disks (credits and thanks to Dave Kleikamp)
- Various fixes
[B]11/03/2013 - K^Kernel v1.3.5 for JB 4.1.2[/B]
- New Broadcom Wireless drivers adapted by Samsung (dhd.ko) support for CM 10 (JB 4.1.2) by Ivendor Beta 3 and next builds
[B]10/03/2013 - K^Kernel v1.3.5 for JB 4.2.2[/B]
- New Broadcom Wireless drivers adapted by Samsung (dhd.ko) support for CM 10.1 (JB 4.2.2) by Xistance Alpha 5 and next builds, CM 10.1 by Doomsday94 builds released from 11/03/2013
[B]09/03/2013 - K^Kernel v1.3 for JB 4.1.2 and JB 4.2.2[/B]
- Kernel 3.0.68 sources synched with jb-3.0 repos of Ivendor and Arco68
- Built with my custom Linaro 4.7.3-2013.02 toolchain optimized for Cortex-A8
- Added Cortex-A8 and NEON VFP optimization flags (both kernel and modules)
- Added -O3 optimization flag (both kernel and modules)
- Added more CPU frequencies and overclockability up to 1824 MHz (thanks to Doomsday94)
- Added CPU frequencies undervolted (UV version) and extremely undervolted (EXUV version) options (thanks to CastagnaIT and Smeroni for the initial implementation for our device)
- Added 5 additional CPU governors (InteractiveX, LionHeart, LulzActive, OnDemandX, SmartAssV2)
- Added 2 additional I/O schedulers (SIO and VR)
- Some fixes and tuning to LuzActive CPU governor for better battery life
- Added CPU voltage control VDD sys interface (thanks to Doomlord)
- Added 360MB or 370MB of free RAM options (thanks to Diablo555 and Doomsday94)
- Added optimized AES and SHA1 routines for ARM cpu architecture (credits and thanks to CastagnaIT)
- Added Fast Charge support (credits and thanks to Ivendor)
- Added Battery Life eXtender support (thanks to Ezekeel), adapted by me for I9001 and I8150
- Lowered display panel voltage
- Lowered wifi voltage
- Lowered swappiness
- Increased CPU frequency during boot (for faster boot process)
- Fixed 100% battery notification after charger unplug
- Increased audio volume on board side
- Old Broadcom Wireless drivers (dhd.ko) support for CM 10 (JB 4.1.2) by Ivendor Beta 2 and previous builds
- New Broadcom Wireless drivers (bcmdhd.ko) support for CM 10.1 (JB 4.2.2)
Credits and Thanks to:
Arco68 and Ivendor for their awesome work and their kernel sources
CastagnaIT for his awesome work, his 2.6 kernel sources where I learned many things and for the useful features inspiration
Xistance for his wonderful work to give us the CM 10.1 rom
Ezekeel, Doomlord, Faux123, Stratosk, Tegrak, ErasmuX, Imoseyon, Doomsday94, Hadidjapri, Diablo555 and other devs I'm surely missing
CyanogenMod, Kernel.org, Code Aurora Forum, [Google], Linaro GCC developers
XDA:DevDB Information
[GT-I9001][PMEM] K^Kernel 3.0 for JB 4.1.2 and JB 4.2.2, Kernel for the Samsung Galaxy S I9000
Contributors
Christopher83
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v3.1
Stable Release Date: 2013-11-29
Created 2013-09-13
Last Updated 2014-08-30

Special features and sysfs settings (Part 1):
Here you can find some useful scripts that can be used with the following described features:
Scripts​
Phantom Key Presses filter
This feature is an attempt to workaround a well known hardware bug of some Samsung devices.
Pratically, the high activity of the radio hardware, in particular the antenna, could cause interference on Melfas chip, which is located very close to the antenna.
This interference could induce bad interrupts that are seen by the chip as possible HOME, MENU or BACK key presses.
These phantom key presses are happening expecially in 2G mode.
The solution includes a new device module (phantom_kp_filter), which also allows the filtering parameters customization, and various changes to cypress-touchkey and pmic8xxx-keypad modules.
The phantom key presses filtering is enabled by default for incoming MENU and BACK touch keys, because for these keys is simpler to recognize a bad interrupt or an invalid key press, instead it's disabled for incoming HOME key (read the next howto infos to enable it).
I also developed a new app to better manage the filtering status and the filtering parameters customization, you can find it on this thread:
Phantom Key Presses Filter Manager​
How to enable/disable the feauture and customize the filtering parameters:
The new device module allows to show the number of ignored key presses and to customize the filtering parameters by means of a sysfs interface, at the following system path: /sys/class/misc/phantom_kp_filter
The interface exposes these files:
home_enabled: show/edit the enable status of the phantom HOME key presses filtering (0 = disabled and 1 = enabled, disabled by default)
home_allowed_irqs: show/edit the allowed max number of incoming interrupts to consider a HOME key press as valid (from 1 to 32, default = 4), a lower value allows to have a more aggressive filtering, instead a higher value allows to have a more permissive filtering
home_report_wait: show/edit the wait time in ms before report the collected HOME key presses (from 5 to 25 ms, default = 12 ms), the key presses during this wait time are collected and reported only if the system received a number of interrupts less than or equal to the allowed max number of incoming interrupts (home_allowed_irqs parameter)
home_ignored_kp: show the ignored possible phantom HOME key presses
menuback_enabled: show/edit the enable status of the phantom MENU and BACK key presses filtering (0 = disabled, 1 = enabled, enabled by default)
menuback_interrupt_checks: show/edit the number of interrupt checks to be performed for the incoming MENU and BACK key presses (from 1 to 10, default = 10), a lower value is more permissive, a higher value securely avoids most of the bad interrupts
menuback_first_err_wait: show/edit the time in ms to wait after the first error on MENU or BACK keys if there are many invalid key errors in rapid sequence (from 50 to 1000 ms, default = 500 ms), the default value is optimal and well tested
menuback_last_err_wait: show/edit the time in ms to wait after the last error on MENU or BACK keys if there are many invalid key errors in rapid sequence (from 50 to 1000 ms, default = 100 ms), the default value is optimal and well tested
menuback_ignored_kp: show the ignored possible phantom MENU and BACK key presses
version: show the module version
To change the filtering parameters:
1) By downloading and using my new app PkfManager
2) By using a customized init.d script (the custom value will be always restored after a reboot, if you don't format the system partition)
- Download the script named 05pkf_alt
- If the file has been saved with .txt extension (stock browser), rename it by removing the .txt extension
- Edit the file by setting your preferred filtering parameters (the downloaded script has the default filtering parameter values and enables the phantom HOME key presses filtering)
- Copy the new file inside /etc/init.d
- Give the rwxr-xr-x permissions to the file (read, write, execution for owner, read and execution for group users, read and execution for others)
- Reboot
3) By directly editing the files inside /sys/class/misc/phantom_kp_filter (the values you set will be lost after a reboot/shutdown)
4) By using Terminal Emulator (note that set values will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run these commands
Code:
su
echo [COLOR="Blue"][I]value[/I][/COLOR] > /sys/class/misc/phantom_kp_filter/[COLOR="Green"][I]parameter_name[/I][/COLOR]
where value is the value you want to set and parameter_name is one of the previously described editable parameters
For example, these commands will enable phantom HOME key presses filtering:
Code:
su
echo 1 > /sys/class/misc/phantom_kp_filter/home_enabled
To show the number of ignored key presses (possible phantom key presses):
1) By directly opening the files /sys/class/misc/phantom_kp_filter/home_ignored_kp and /sys/class/misc/phantom_kp_filter/menuback_ignored_kp
2) By using Terminal Emulator
- Open Terminal Emulator
- Run these commands
Code:
su
cat /sys/class/misc/phantom_kp_filter/home_ignored_kp
cat /sys/class/misc/phantom_kp_filter/menuback_ignored_kp
Customizable timeout of touchkeys backlight after press
This feature is available for v2.2 kernel and next releases, it allows to set a customized timeout of touchkeys backlight after a key press or touchscreen press. The default value is 1600 ms.
How to set the timeout of touchkeys backlight:
1) By downloading and using the related setting inside NsTools
2) By using a customized init.d script (the custom value will be always restored after a reboot, if you don't format the system partition)
- Download the script named 20backlight_timeout
- If the file has been saved with .txt extension (stock browser), rename it by removing the .txt extension
- Edit the file by setting your preferred timeout (the downloaded script will set the status to 0 = disabled)
- Copy the new file inside /etc/init.d
- Give the rwxr-xr-x permissions to the file (read, write, execution for owner, read and execution for group users, read and execution for others)
- Reboot
3) By directly editing the file /sys/class/misc/notification/bl_timeout (the value you set will be lost after a reboot/shutdown)
4) By using Terminal Emulator (note that set values will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run these commands to set the timeout of touchkeys backlight to 1000 ms (1 second)
Code:
su
echo 1000 > /sys/class/misc/notification/bl_timeout
Customizable activation status of touchkeys backlight on touchscreen press
This feature is available for v2.2 kernel and next releases, it allows to enable/disable the touchkeys backlight after a touchscreen press.
How to set the status of touchkeys backlight on touchscreen press:
1) By using a customized init.d script (the custom value will be always restored after a reboot, if you don't format the system partition)
- Download the script named 25touchlight_status
- If the file has been saved with .txt extension (stock browser), rename it by removing the .txt extension
- Edit the file by setting your preferred status(the downloaded script will set the status to 0 = disabled)
- Copy the new file inside /etc/init.d
- Give the rwxr-xr-x permissions to the file (read, write, execution for owner, read and execution for group users, read and execution for others)
- Reboot
2) By directly editing the file /sys/class/misc/notification/touchlight_enabled (the value you set will be lost after a reboot/shutdown)
3) By using Terminal Emulator (note that set values will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run these commands to disable the touchkeys backlight on touchscreen press
Code:
su
echo 0 > /sys/class/misc/notification/touchlight_enabled
- Or run these commands to enable the touchkeys backlight on touchscreen press
Code:
su
echo 1 > /sys/class/misc/notification/touchlight_enabled
CPU voltage control VDD sys interface
This feature allows to customize the voltage assumed by each cpu scaling frequency.
It could be useful if you'd like to decrease one or more voltages for battery saving purposes (undervolting), or to increase/adjust them to prevent phone freezes (overvolting).
How to customize the voltages:
1) By downloading and using Trickster MOD
or IncrediControl and changing the voltages table inside the SVS tab
2) By using customized init.d scripts (the custom values will be always restored after a reboot, if you don't format the system partition)
- Download one of the script named 01vdd_levels*
- If the file has been saved with .txt extension (stock browser), rename it by removing the .txt extension
- Edit the file by setting your customized voltages, where each line has this syntax
Code:
echo "[I][B][COLOR="Blue"]cpu_freq_HZ[/COLOR][/B][/I] [I][COLOR="SeaGreen"][B]mV[/B][/COLOR][/I]" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
cpu_freq_HZ is the cpu frequency in Hz you'd like to change
mV is the voltage you want to set
For example, the following line means that when the cpu frequency is 1516800 Hz = 1516 MHz, the voltage used will be 1175 mV
Code:
echo "1516800 1175" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
- Copy the new file inside /etc/init.d
- Give the rwxr-xr-x permissions to the file (read, write, execution for owner, read and execution for group users, read and execution for others)
- Reboot
3) By using Terminal Emulator (note that the values you set will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run these commands
Code:
su
# Run a command for each cpu frequency voltage you'd like to change
echo "[I][B][COLOR="Blue"]cpu_freq_HZ[/COLOR][/B][/I] [I][COLOR="SeaGreen"][B]mV[/B][/COLOR][/I]" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
cpu_freq_HZ is the cpu frequency in Hz you'd like to change
mV is the voltage you want to set
For example, the following line means that when the cpu frequency is 1516800 Hz = 1516 MHz, the voltage used will be 1175 mV
Code:
echo "1516800 1175" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
Alternative Extreme Undervolted (ExUV) settings
If after overclocking your I9001 you noticed some freezes when on ExUV kernel builds, you may use an alternative extremely undervolted setting with the init.d script you can find here: 01vdd_levels_alt_exuv
- Download the script
- If the file has been saved with .txt extension (stock browser), rename it by removing the .txt extension
- Copy the new file inside /etc/init.d
- Give the rwxr-xr-x permissions to the file (read, write, execution for owner, read and execution for group users, read and execution for others)
- Reboot
Customized vibration intensity
This feature has been developed by CastagnaIT and allows to set a customized vibration intensity (121 is the default stock value).
It could be useful if you don't like the stock vibration intensity and you'd like to have a lower / stronger vibration.
The setting will affect the haptic feedback and the notification vibration intensity.
How to set a customized vibration intensity:
1) By using the related setting inside System->Advanced->Vibration (only on CM 10 Beta 4 and next releases)
2) By using a customized init.d script (the custom value will be always restored after a reboot, if you don't format the system partition)
- Download the script named 10vibetonz
- If the file has been saved with .txt extension (stock browser), rename it by removing the .txt extension
- Edit the file by setting your preferred vibration intensity (the downloaded script will set the vibration intensity to 70)
- Copy the new file inside /etc/init.d
- Give the rwxr-xr-x permissions to the file (read, write, execution for owner, read and execution for group users, read and execution for others)
- Reboot
3) By directly editing the file /sys/class/vibetonz/immDuty/pwmvalue_intensity (the value you set will be lost after a reboot/shutdown)
4) By using Terminal Emulator (note that set values will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run these commands (changing the intensity value = 70 with the preferred one)
Code:
su
echo 70 > /sys/class/vibetonz/immDuty/pwmvalue_intensity
Backlight Notification V9 (BLNv9)
This feature allows to notify you of missing calls, messages, emails, etc... by lighting up or blinking the Menu and Back buttons.
With BLNv9 enabled you don't need to unlock the screen to see if you have new notifications.
How to configure the BLNv9:
1) By downloading and using BLN Control Free, BLN Control Pro or NsTools
2) By directly editing the file /sys/class/misc/backlightnotification/enabled and setting 1 to enable the feature, 0 to disable it (note that set value will be lost after a reboot/shutdown)
3) By using Terminal Emulator (note that set value will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run this command to enable the feature
Code:
su
echo 1 > /sys/class/misc/backlightnotification/enabled
- Run, instead, this command to disable the feature
Code:
su
echo 0 > /sys/class/misc/backlightnotification/enabled
Work in progress (init.d, blinking and other settings)...
Force Fast Charge
This feature allows you to force AC charging for any charger that is detected as USB (eg. PC USB ports, USB Car Chargers) and pull the full current the charger can support, in such a way as to speed up the time required for a complete battery recharge.
By enabling this feature, the USB / ADB data transfers will be disabled (security limitation to protect your data).
How to enable/disable the Force Fast Charge:
1) By using the related setting inside System->Advanced->Force Fast Charge (only on CM 10 Beta 3 and next releases)
2) By downloading and using Trickster MOD
or IncrediControl or NsTools
2) By directly editing the file /sys/kernel/fast_charge/force_fast_charge and setting 1 to enable the force charge, 0 to disable it (note that set value will be lost after a reboot/shutdown)
3) By using Terminal Emulator (note that set value will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run this command to enable the force fast charge feature
Code:
su
echo 1 > /sys/kernel/fast_charge/force_fast_charge
- Then, when you want to restore the normal status, run this command to disable the force fast charge feature
Code:
su
echo 0 > /sys/kernel/fast_charge/force_fast_charge
4) By using a customized init.d script, but I don't recommend it because you have to remember to disable the feature every time you want to connect your device to a pc for data transfering after every reboot
Battery life extender (BLX)
This feature has been developed by Ezekeel and allows to set a customized battery charging limit (100% is the default stock value, if you want, you can set a lower value).
As Ezekeel said, it is commonly accepted that both very low and very high charge states accelerate the degradation of the battery capacity (that is why you should store Li-Ion batteries at around 40% charge).
If you set a charging limit equal to 100, this feature will be disabled.
How to activate this feature and set a customized charging limit:
1) By downloading and using Trickster MOD or NsTools by setting the customized battery life extender charging limit
2) By using a customized init.d script (the custom value will be always restored after a reboot, if you don't format the system partition)
- Download the script named 15blx
- If the file has been saved with .txt extension (stock browser), rename it by removing the .txt extension
- Edit the file by setting your preferred charging limit (the downloaded script will set the charging limit to 95%)
- Copy the new file inside /etc/init.d
- Give the rwxr-xr-x permissions to the file (read, write, execution for owner, read and execution for group users, read and execution for others)
- Reboot
3) By directly editing the file /sys/class/misc/batterylifeextender/charging_limit (the value you set will be lost after a reboot/shutdown)
4) By using Terminal Emulator (note that set value will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run these commands (changing the charging limit = 95 with the preferred one)
Code:
su
echo 95 > /sys/class/misc/batterylifeextender/charging_limit
LowMemoryKiller
The LowMemoryKiller driver is used to kill a selected process and free the memory when it is under one of the defined thresholds.
The tuning of the driver could be achieved by means of two parameters exposed by the kernel module via sysfs interface:
- /sys/module/lowmemorykiller/parameters/minfree
This file includes a comma separated array of the threshold numbers for minfree memory size (in page units).
The parameter value set for K^Kernel is "2048,4096,6656,9216,14336,19456".
- /sys/module/lowmemorykiller/parameters/adj
This file includes the comma separated array of oomadj factors, if the corresponding minfree threshold has been reached, one of the process with an oomadj greater than this number will be killed.
The oomadj factor is a property associated to each process, its value is in a range from -17 to +15, the processes with a higher oomadj factor will be the first to be killed when a specific minfree threshold has been reached.
The parameter value set for K^Kernel is "0,20,50,100,250,500".
Frandom - Fast Random Generator
As Eli Billauer (the creator of this module) said, Frandom is a Linux kernel random number generator, which is 10-50 times faster than what you get from Linux built-in /dev/urandom. And it uses very little (/dev/frandom) or none (/dev/erandom) of the kernel's entropy pool, so it is very useful for applications that require a handy source for lots of random data.
How to test if frandom builtin module is correctly working:
- Download the script named frandom_test.sh
- Using your preferred file explorer, copy the file inside the folder /data/local of your device
- Give the rwxr-xr-x permissions to the file (read, write, execution for owner, read and execution for group users, read and execution for others)
- Open Terminal Emulator
- Run this command
Code:
/data/local/frandom_test.sh
You should see a result similar to this one:
If the urandom tests take more than 1 or 2 seconds and are more different than related frandom tests, then the random number generation is not fully optimized for your currently used kernel...
RAM Console
This feature is useful expecially for development and debugging purposes, when occurs kernel panic / unexpected shutdowns or reboots. Pratically, the kernel messages are also stored inside a little RAM portion and restored during reboot after a kernel panic, inside the file /proc/last_kmsg.
Dynamic FSync
This feature has been developed by Faux123 and allows to dynamically manage the synchronous writes performed on file system (FSync).
It uses asynchronous writes when the screen is on, instead of synchronous writes, to have better performance and a slightly lower battery drain, while when the screen is off the synchronous writes are re-enabled to flush all the outstanding writes and prevent possible data loss.
How to enable/disable the Dynamic FSync (default enabled):
1) By downloading and using Trickster MOD
2) By directly editing the file /sys/kernel/dyn_fsync/Dyn_fsync_active and setting 1 to enable the dynamic fsync, 0 to disable it (note that set value will be lost after a reboot/shutdown)
3) By using Terminal Emulator (note that set value will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run this command to disable the dynamic fsync feature
Code:
su
echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active
- Or run this command to re-enable the dynamic fsync feature
Code:
su
echo 1 > /sys/kernel/dyn_fsync/Dyn_fsync_active
Dynamic dirty page writebacks
This feature has been developed by me and allows to dynamically manage the dirty page writebacks with two different intervals, one when the screen is on and another when the screen is off.
It is based on a commit of Francisco Franco, but instead of using hard coded values and of disabling at all the dirty page writebacks while the screen is on (possibility of data loss), I preferred to use a customizable higher dirty page writebacks interval (15 seconds) than the default one (5 seconds) while the screen is on and a customizable default interval (5 seconds) when the screen is off.
By using a higher interval we have better performance and less battery consumption, with a very low risk of data loss.
How to customize the dynamic dirty page writebacks feature (default enabled):
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), the default value is 1500 centisecs (15 seconds)
- dirty_writeback_suspend_centisecs is the interval for the dirty page writebacks when the system is suspended (screen off), the default value is 500 centisecs (5 seconds)
In my kernel builds, during boot, I set other customized values:
- an interval of 30 seconds while the screen is on
- an interval of 10 seconds when the screen is off
1) By directly editing one of the file written above inside /proc/sys/vm and setting the preferred value (note that set value will be lost after a reboot/shutdown)
2) By using Terminal Emulator (note that set value will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run this command to disable the dynamic dirty page writebacks feature
Code:
su
echo 0 > /proc/sys/vm/dynamic_dirty_writeback
- Or run this command to re-enable the dynamic dirty page writebacks feature
Code:
su
echo 1 > /proc/sys/vm/dynamic_dirty_writeback
- Run this command to set customize the two intervals (30 seconds while the screen is on, 10 seconds when the screen is off)
Code:
su
echo "3000" > /proc/sys/vm/dirty_writeback_active_centisecs
echo "1000" > /proc/sys/vm/dirty_writeback_suspend_centisecs

Special features and sysfs settings (Part 2):
Timer slack controller and dynamic management of the minimal timer slack value
The timer slack controller is a feature developed by Kirill Shutemov and it allows to set the minimal timer slack value for every process contained within a control group (cgroup).
A timer slack allows the kernel to manage processes wakeup requests at some future time.
Thanks to this feature, the kernel can set a specific timer slack for the involved processes, minimizing the number of wakeups and allowing a lower system's power consumption.
For further info: Timer slack for slacker developers
I also implemented a new feature in addition to the above one that allows the dynamic management of the minimal timer slack value.
So, it's possible to use different minimal timer slack value when the system is active and when has been suspended.
How to customize the dynamic timer slack controller feature:
Three new cgroup parameters are exposed inside each processes hierarchy contained in /dev/cpuctl path:
- timer_slack.min_slack_ns is the timer slack used when the system is active for the current processes hierarchy
- timer_slack.min_slack_suspend_ns is the timer slack used when the system is suspended for the current processes hierarchy
- timer_slack.effective_slack_suspend_ns is the timer slack currently used
At the moment, the values chosen and used by K^Kernel are the following:
- core processes (/dev/cpuctl), 0 ns when the system is active, 50000 ns when the system is suspended
- foreground apps/processes (/dev/cpuctl/apps), 0 ns when the system is active, 250000 ns when the system is suspended
- background non interactive apps/processes (/dev/cpuctl/apps/bg_non_interactive), 100000000 ns when the system is active, 250000000 ns when the system is suspended
1) By directly editing one of the file written above inside /dev/cpuctl and inside each hierarchy subfolder, by setting the preferred value (note that set value will be lost after a reboot/shutdown)
2) By using Terminal Emulator (note that set value will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run these commands to set the minimal timer slack for generic and core apps/processes
Code:
su
echo 0 > /dev/cpuctl/timer_slack.min_slack_ns
echo 50000 > /dev/cpuctl/timer_slack.min_slack_suspend_ns
- Run these commands to set the minimal timer slack for apps/processes in foreground
Code:
su
echo 0 > /dev/cpuctl/apps/timer_slack.min_slack_ns
echo 100000 > /dev/cpuctl/apps/timer_slack.min_slack_suspend_ns
- Run these commands to set the minimal timer slack for apps/processes in background and non interactive
Code:
su
echo 100000000 > /dev/cpuctl/apps/bg_non_interactive/timer_slack.min_slack_ns
echo 250000000 > /dev/cpuctl/apps/bg_non_interactive/timer_slack.min_slack_suspend_ns
LowMemoryKiller management of not killable processes
This feature allows to define processes and system processes white-lists filled with the preferred process names and to not be killed by lowmemorykiller, unless it is absolutely necessary.
This feature exposes four new lowmemorykiller parameters:
- donotkill_proc, is the flag to enable / disable this feature for the processes chosen by the user
- donotkill_sysproc, is the flag to enable / disable this feature for the system processes chosen by the user
- donotkill_proc_names, is the list of process names (comma separated) chosen by the user to be preserved from killing
- donotkill_sysproc_names, is the list of user system process names (comma separated) chosen by the user to be preserved from killing
When the lowmemorykiller needs to free ram, it will first kill the processes not included inside the two process name lists chosen by the user.
If there are no more standard killable processes, then it will be necessary to kill one of the processes included inside one of the two white-lists, to prevent system hangs, slowdowns, etc.
How to customize the white lists of processes to preserve from killing:
On K^Kernel the feature is enabled by default and the provided processes white lists are the following:
- donotkill_proc_names = "com.cyanogenmod.trebuchet,com.anddoes.launcher,com.teslacoilsw.launcher,org.adwfreak.launcher,gtp.nextlauncher,android.inputmethod.latin,com.touchtype.swiftkey"
this means that Trebuchet Launcher, Apex Launcher, Nova Launcher, ADW Launcher, Next Launcher, stock keyboard and SwiftKey keyboard will be preserved from killing
- donotkill_sysproc_names = "android.process.acore,com.android.phone,com.bel.android.dspmanager"
this means that the system process, the phone process and DSP Manager will be preserved from killing
1) By using a customized init.d script (the custom value will be always restored after a reboot, if you don't format the system partition)
- Download the script named 80dnkp
- If the file has been saved with .txt extension (stock browser), rename it by removing the .txt extension
- Edit the file by setting your preferred status and processes list
- Copy the new file inside /etc/init.d
- Give the rwxr-xr-x permissions to the file (read, write, execution for owner, read and execution for group users, read and execution for others)
- Reboot
2) By directly editing the files inside /sys/module/lowmemorykiller/parameters (note that set values will be lost after a reboot/shutdown)
3) By using Terminal Emulator (note that set values will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run these commands if you want to enable the feature
Code:
# To enable this feature for the processes chosen by the user
echo 1 > /sys/module/lowmemorykiller/parameters/donotkill_proc
# To enable this feature for the system processes chosen by the user
echo 1 > /sys/module/lowmemorykiller/parameters/donotkill_sysproc
- Run these commands if you want to disable the feature
Code:
# To disable this feature for the processes chosen by the user
echo 0 > /sys/module/lowmemorykiller/parameters/donotkill_proc
# To disable this feature for the system processes chosen by the user
echo 0 > /sys/module/lowmemorykiller/parameters/donotkill_sysproc
- Run this command if you want to add, for example, Trebuchet Launcher (CM default launcher) and the default keyboard to the processes white list
Code:
echo "com.cyanogenmod.trebuchet,android.inputmethod.latin" > /sys/module/lowmemorykiller/parameters/donotkill_proc_names
- Run this command if you want to add, for example, the system process, the phone process and DSP Manager to the system processes white list
Code:
echo "android.process.acore,com.android.phone,com.bel.android.dspmanager" > /sys/module/lowmemorykiller/parameters/donotkill_sysproc_names
Work in progress...

FAQ - Frequently asked questions:
Q: What are the differences between EXUV and UV kernel versions?
A: The EXUV kernel versions have extremely undervolted settings for the cpu frequencies, they allows to have a very low battery drain, instead the UV kernel versions have undervolted settings a bit higher than EXUV versions, but always lower than stock kernel settings (take a look at the comparison table on the first post).
The EXUV kernel versions could give some problems (freezes, shutdowns, huge lags) on some devices because the cpu doesn't support too low voltage settings.
For a lower battery consumption, I suggest you to try EXUV versions first and to switch to UV versions only if you encounter one of the above mentioned problems.
Q: What are the differences between 360MB, 370MB and 390MB versions?
A: 360MB, 370MB and 390MB kernel versions have different free ram available for user space, with a higher free ram your device will work better with heavy apps, many concurrently used apps, heavy games, etc.
- 360MB versions have additional 8 MB of free ram than stock kernels (352 MB of free ram), they are suitable for the users that use the device primarly for calls, messages, simple apps and simple games. The camera, video recording (both 480p and 720p modes) and video playback are fully working.
- 370MB versions have additional 18 MB of free ram than stock kernels, they are suitable for the users that use the device also with heavy apps, various concurrently used apps and games. The camera, video recording (both 480p and 720p modes) and video playback are fully working.
- 390MB versions have additional 38 MB of free ram than stock kernels, they are suitable for the users that use the device also with heavy apps, many concurrently used apps and heavy games. The camera and video playback are fully working, the video recording works only in 480p mode.
Q: How can I get the Performance and Developer Options entries inside Settings menu?
A: Go inside Settings -> About Phone -> Scroll down and tap 7 times on Build number (it's an Easter Egg).
Q: How can I get the log after an unexpected shutdown / reboot?
A: After an unexpected shutdown / reboot of the device, if the problem may be kernel related, you should have the /proc/last_kmsg, if so, send me that log and I'll check it to find the possible cause of the problem.
Q: How can I get the logs when I encounter strange system issues while it's running?
A: Check first if the problems could be related to an app you're using and if you changed something in the last days before facing those issues.
If the problem started after installing the kernel, then let me have you logcat and dmesg:
- Open Terminal Emulator and execute these commands:
Code:
su
dmesg > /sdcard/dmesg.txt
locat -v time -d > /sdcard/logcat.txt
- Open you preferred file manager and go inside the internal sd card partition /sdcard
- Send me the dmesg.txt and logcat.txt files, if you want zip them first

\o/ Thank you and good luck!

Wow, this is well formatted thread
Thanks Christopher, will try now
---------- Post added at 08:21 PM ---------- Previous post was at 08:16 PM ----------
What's the difference between 360 and 370mb kernel?

woooowwww !! THANKS !!!! you're great !!:good:

Awesome job man. Make sure to get the new kernel ready as my next build is coming with ALL wifi problems fixed with the new driver. It uses a different kind of dhd.ko instead of the old one or bcmdhd.ko.

R: [KERNEL][3.0.x][JB] K^Kernel 3.0.x for JB 4.1.2 and JB 4.2.2 v1.3 [09/03/2013]
TwinHeadedEagle said:
Wow, this is well formatted thread
Thanks Christopher, will try now
---------- Post added at 08:21 PM ---------- Previous post was at 08:16 PM ----------
What's the difference between 360 and 370mb kernel?
Click to expand...
Click to collapse
Thank you too!
360MB version has more ram allocated by Surface Flinger, should be more stable, suitable for who uses his I9001 primarly for calls, browsing, and not heavy playing.
370MB version should be useful for players.
Sent from my GT-I9001 using xda premium

R: [KERNEL][3.0.x][JB] K^Kernel 3.0.x for JB 4.1.2 and JB 4.2.2 v1.3 [09/03/2013]
Xistance said:
Awesome job man. Make sure to get the new kernel ready as my next build is coming with ALL wifi problems fixed with the new driver. It uses a different kind of dhd.ko instead of the old one or bcmdhd.ko.
Click to expand...
Click to collapse
You are great! I'll be ready.
Sent from my GT-I9001 using xda premium

Amaaaaaaaaaazing kernel. For me, the user experience is better on 10.1. In term of performance I can't imagine it can be better. the only thing missed is DeepSleep From Ezekeel which not implemnted yet. more than 10% of drain in the night on my phone

inhirz said:
Amaaaaaaaaaazing kernel. For me, the user experience is better on 10.1. In term of performance I can't imagine it can be better. the only thing missed is DeepSleep From Ezekeel which not implemnted yet. more than 10% of drain in the night on my phone
Click to expand...
Click to collapse
Deep sleep is the built in suspend feature of embedded Linux systems, it's not developed by Ezekeel...
The BLX feature has been developed by Ezekeel.

Released new v1.3.5 kernel versions for CM 10.1 Alpha 5.
The new Broadcom Wireless drivers adapted by Samsung are correctly working

Christopher83 said:
Released new v1.3.5 kernel versions for CM 10.1 Alpha 5.
The new Broadcom Wireless drivers adapted by Samsung are correctly working
Click to expand...
Click to collapse
What about Doomsday CM10.1? I can use this kernel on his rom?

Harrocan said:
What about Doomsday CM10.1? I can use this kernel on his rom?
Click to expand...
Click to collapse
Yes you can use v1.3

AW: [KERNEL][3.0.x][JB] K^Kernel 3.0.x for JB 4.1.2 v1.3 and JB 4.2.2 v1.3.5 [10/03/2
Does this kernel use the OC table from diablo?
Sent from my GT-I9001 using xda app-developers app

XeLLaR* said:
Does this kernel use the OC table from diablo?
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
It's similar to CatagnaIT one...
Remember that you can customize each frequency voltage using IncrediControl, the kernel has Voltage Control interface on sysfs...

AW: [KERNEL][3.0.x][JB] K^Kernel 3.0.x for JB 4.1.2 v1.3 and JB 4.2.2 v1.3.5 [10/03/2
Wttffff this **** is incredible
Awesome bro :thumbup: CM 10.1 is flying <3 its so damn smooth, thanks :thumbup:
Sent from my GT-I9001 using xda app-developers app

R: [KERNEL][3.0.x][JB] K^Kernel 3.0.x for JB 4.1.2 v1.3 and JB 4.2.2 v1.3.5 [10/03/20
I can't play videos 720p with kernel 360mb and 370mb for cm10.1
I have alpha5 xistance
Inviato dal mio GT-I9001 con Tapatalk 2

Good Good Good christopher awesome kernel for me is very smooth and the WiFi works great!!

[KERNEL][STOCK|CROMI] that11 » stock++ kernel

Introduction
This kernel is designed to be more stable than the stock kernel, with more features and more performance. Choose any three.
I do not include any changes that have no clear positive effect on these goals.
Features
zImage (kernel binary) features:
- Asus 10.6.1.14.10 base
- Support for Samsung's F2FS filesystem (experimental) and exFAT
- ISO 9660 + UDF support (CD/DVD filesystems)
- CIFS (for mounting Windows shares)
- BFQ I/O scheduler (http://algo.ing.unimo.it/people/paolo/disk_sched/) v7r5; ROW I/O scheduler v4 (https://patchwork.kernel.org/patch/1862241/) and "deadline" is also available
- fsync control (echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled)
- Overclocking up to 1800 MHz, based on clemsyn's patch, configurable clock frequencies for balanced and performance mode
- User voltage control for undervolting
- Crash fixes when reading various files in /sys
- mount space hack from http://forum.xda-developers.com/show...php?p=36889027 allows mounting across Android processes again (e.g. using CIFS Manager)
- NFS v3/v4 client (supports files > 2 GB)
- NFS v3/v4 server as module (untested, needs userspace tools which I haven't yet compiled)
- Framebuffer console at boot (Android penguins!)
- Keyboard dock: support for F1-F12 function keys, special key mappings for CyanogenMod and GNU/Linux (Esc, Insert, Delete, Alt, Windows)
- Support for various USB Ethernet adapters and FTDI serial port adapters
- Kexec-able and able to kexec other kernels
- SELinux is not included for compatibility with the stock ROM's proprietary NTFS and exFAT drivers
- Tethering via dock USB port (untested), see http://forum.xda-developers.com/showpost.php?p=52917184&postcount=2740
Ramdisk features:
- adbd with root access enabled in default.prop, ro.secure=0
- optimized mount options (noauto_da_alloc)
- init.d script support
- USB IDs for all Tegra 3 based Transformer models (init.xx.rc)
- does not set lcd_density (dpi unlocked), must/can be set in /system/build.prop instead
- preinit system for easy ramdisk customization without repacking or reflashing the kernel: if exists, runs a custom script "/system/boot/preinit" before Android init, e.g. for adding Data2SD detection, ROM2SD, etc.
- File-system auto-detection for use in preinit scripts
Installation/Download
Flash the zip in recovery and reboot; the bootloader will move the kernel to its final place while showing a blue progress bar.
Compatibility
This kernel is compatible with the 10.6.1.14.x bootloaders and stock-based (Asus Android 4.2.1) ROMs that set lcd_density (dpi) in build.prop - in other words, this is the preferred kernel for CleanROM Inheritance. It also works with other ROMs up to Android 4.4 (requires a preinit script to provide the corresponding ramdisk files). The kernel is derived from the original TF700T sources but is known to work also on the TF300.
MD5 sum:
You don't need an MD5 sum. Enable "Zip file signature verification" in TWRP instead - it checks the SHA1 checksum embedded in the archive, which is both more secure and more convenient.
Download the latest version here -> http://forum.xda-developers.com/showpost.php?p=55513454&postcount=484
Credits
- Linux kernel devs and Asus for the base
- Gentoo devs for their easy "crossdev" toolchain-generation tool
- scrosler for the original CleanROM
- sbdags for CleanROM Inheritance
- Ezekeel for the fsynccontrol patch (http://rootzwiki.com/topic/14685-kernel27-jul-glados-v20-for-jb/page__st__700#entry607555)
- faux123 for the user voltage control patch
- clemsyn for the overclocking patch. I still use his frequency and voltage tables but rewrote the EDP handling.
- Hundsbuah for decoding the EDP limit tables and finding an f2fs patch that applies cleanly to our kernel
- cogano for improving the dock key mapping for native Linux
- wenchien for cherry-picking lots of f2fs updates from later kernels
Development Info
Guide for unpacking and repacking kernel blobs and boot images -> http://forum.xda-developers.com/showpost.php?p=36925180&postcount=4
XDA:DevDB Information
_that-kernel, Kernel for the Asus Transformer TF700
Contributors
_that
Kernel Special Features: Stock kernel with more stability, more features and more performance. Choose any three.
Version Information
Status: Stable
Current Stable Version: that11
Stable Release Date: 2014-09-17
Current Beta Version: that11
Beta Release Date: 2014-09-17
Created 2014-02-17
Last Updated 2014-10-14

Changelog/History
2014-09-17: 3.1.10-that11
New features:
- enable tethering via dock USB port (untested)
- fix for the Towelroot exploit
- lots of f2fs updates from mainline kernel, thanks to wenchien
- new BFQ (budget fair queueing) I/O scheduler
- added FTDI USB serial support
- exFAT filesystem support from Samsung
download -> http://forum.xda-developers.com/showpost.php?p=55513454&postcount=484
2014-05-14: 3.1.10-that10
New features:
- Removed the special overclocking mode (system_mode 3) - instead, clock speeds for balanced and performance modes are now user-configurable.
- More options for dock key mapping for GNU/Linux and autorepeat
- File system auto-detection in init for use in preinit script
download -> http://forum.xda-developers.com/showpost.php?p=52659251&postcount=446
2014-03-29: 3.1.10-10.6.1.14.10-that9-oc
New features:
- Dock function keys and CyanogenMod-compatible mode for dock keys
- Support for various USB Ethernet adapters
download -> http://forum.xda-developers.com/showpost.php?p=51486800&postcount=414
2014-02-17: 3.1.10-10.6.1.14.10-that8-oc
New features:
- F2FS (Flash Friendly) filesystem by Samsung (experimental, may eat your data)
- USB mass storage support (needs a computer that understands ext4 (i.e. Linux))
- Enabled dual filenames on FAT filesystems for compatibility with some devices
download -> http://forum.xda-developers.com/showpost.php?p=50408485&postcount=396
2013-11-22: 3.1.10-10.6.1.14.10-that7-oc
Security config options disabled to restore compatibility with proprietary exFAT/NTFS modules. Details and download -> http://forum.xda-developers.com/showpost.php?p=47743629&postcount=358
The Data2SD auto-detection add-on is here: http://forum.xda-developers.com/showpost.php?p=40522097&postcount=56
Or if you prefer Data2SD with internal /sdcard: http://forum.xda-developers.com/showpost.php?p=41305526&postcount=159
(these add-ons are unchanged since they were released, so if you already have them installed, you don't need to reinstall when updating the kernel)
2013-11-11: 3.1.10-10.6.1.14.10-that6-oc
Now with 100% more penguins! Get it here -> http://forum.xda-developers.com/showpost.php?p=47361802&postcount=325
2013-09-06: 3.1.10-10.6.1.14.8-that5-oc
Overclocking is back! Get the new version here -> http://forum.xda-developers.com/showpost.php?p=45332265&postcount=263
2013-07-03: 3.1.10-10.6.1.14.8-that4
The latest version is here -> http://forum.xda-developers.com/showpost.php?p=43199757&postcount=237
New kernel features since -that2
- rebased on Asus source release 10.6.1.14.8
- mount space hack from http://forum.xda-developers.com/show...php?p=36889027 allows mounting across Android processes again (e.g. using CIFS Manager)
- some more sysfs crash fixes
- "deadline" I/O scheduler added (default is still ROW)
- NFS v3/v4 client (supports files > 2 GB)
- NFS v3/v4 server as module (untested, needs userspace tools which I haven't yet compiled)
New ramdisk features since -that2
- fstab: optimized mount options (added noauto_da_alloc)
- added init.xx.rc files for other Transformer models
2013-06-25: 3.1.10-10.6.1.14.8-that3
preview release, see http://forum.xda-developers.com/showpost.php?p=42915255&postcount=201
2013-04-11: 3.1.10-10.6.1.14.4-that2
The Asus source release was surprisingly fast this time. I ported all my popular non-intrusive stock kernel improvements (http://forum.xda-developers.com/showthread.php?t=2125783) and recompiled the kernel. Special thanks to buhohitr for testing this release!
I couldn't get the framebuffer console to work, so no UltraCleanROM support for now.
(-that2 downloads deleted)

Documentation
This kernel supports a few additional parameters. As usual these can be set from a root shell or an init script - for details how to do that, read a tutorial about using the Unix/Linux command line.
fsync
To turn off fsync (warning: read this and this before):
Code:
echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled
To turn it on, write 1 instead of 0.
Clock speeds and overclocking
Note that the special overclocked system_mode 3 has been removed in -that10. There are now only 3 modes, as in the stock kernel (powersave, balanced, performance). To enable overclocking beyond 1700 MHz (or 1600 MHz for more than one core), you need to override the EDP limit:
Code:
echo 1 > /sys/module/cpu_tegra/parameters/override_edp
To set clock speeds for balanced and performance mode, for example:
Code:
echo 1300 > /sys/module/cpu_tegra/parameters/override_mhz_bal
echo 1800 > /sys/module/cpu_tegra/parameters/override_mhz_perf
User voltage control
works exactly like in upstream implementation - ask me to update this if you want to know more.
Keyboard dock tweaks
CyanogenMod has a slightly different mapping for some of the dock function keys. To enable compatibility with CM and CM-based ROMs:
Code:
echo 1 > /sys/module/asusdec/parameters/cm_mode
Function keys F1 to F12 can be entered using right Alt/AltGr and the keys from "Toggle WiFi" to "Next Track". This might only work in native Linux and maybe CM.
For native Linux users, I added additional parameters:
Code:
echo $flags > /sys/module/asusdec/parameters/key_flags
echo 1 > /sys/module/asusdec/parameters/key_autorepeat
where $flags is a number between 0 and 15, by combining these bit flags:
1 = inverts the meaning of Alt for function keys (F1-F12 without Alt, and special functions with Alt. Also, Mute is Insert and Lock is Delete.)
2 = Back is Esc
4 = Search is left Alt
8 = Home is left Windows (aka "Meta" aka "Super_L")

Thanks so much for the RIL patch that seems like fixed my compiling problems lets see
IM just a noob here trying to compile and learn hehe:victory:
EDIT: Yes it compiled
Now I ask myself why Asus released a bad source code lol?

maxrdlf95 said:
Thanks so much for the RIL patch that seems like fixed my compiling problems lets see
Click to expand...
Click to collapse
The RIL include fix is old news - it was already required in the 10.4.4.x kernel, and it's published in my 10.4.4.25 kernel release thread.
maxrdlf95 said:
IM just a noob here trying to compile and learn hehe
Click to expand...
Click to collapse
Learning by doing is still the best way. If you manage to get your own kernel installed and running (if not, read my blob repacking guide), then you have definitely left the "n00b" status.
maxrdlf95 said:
Now I ask myself why Asus released a bad source code lol?
Click to expand...
Click to collapse
Maybe they are using an older compiler that behaves differently.

Thanks man I already knew how to make the blob file and put the signing in, I used to help clemsyn packing its kernel when he didnt have time and well I did it tonight :good: I compile my kernel thanks now will learn how to make it with linaro
EDIT:
P.D I left the n00b status some time ago lol

To install this kernel, do I need to flash both the flash zip and the patch for sbdags' Asus stock rom . I have a US bootloader and a WW rom

lartomar2002 said:
To install this kernel, do I need to flash both the flash zip and the patch for sbdags' Asus stock rom . I have a US bootloader and a WW rom
Click to expand...
Click to collapse
Which patch for sbdags' stock ROM?

_that said:
Which patch for sbdags' stock ROM?
Click to expand...
Click to collapse
In the OP the line just brlow where the krrnel flash zip is.

lartomar2002 said:
In the OP the line just brlow where the krrnel flash zip is.
Click to expand...
Click to collapse
That patch has nothing to do with sdbags roms,that patch contains all the changes made to the original kernel and it's for development only (you can apply that patch to the original or own 4.2.1 kernel source).

Pretoriano80 said:
That patch has nothing to do with sdbags roms,that patch contains all the changes made to the original kernel and it's for development only (you can apply that patch to the original or own 4.2.1 kernel source).
Click to expand...
Click to collapse
Ok, so I only need to flash the kernel zip for 4.2?

lartomar2002 said:
Ok, so I only need to flash the kernel zip for 4.2?
Click to expand...
Click to collapse
Yes.Keep in mind that after flashing the kernel the DPI will be set to 160.

Pretoriano80 said:
Yes.Keep in mind that after flashing the kernel the DPI will be set to 160.
Click to expand...
Click to collapse
In other words: either not be old or have your reading glasses at hand?

Not here. DPI is still at 240.
Flashed kernel, UV 75mV and all looks ok. :good:
Pretoriano80 said:
Yes.Keep in mind that after flashing the kernel the DPI will be set to 160.
Click to expand...
Click to collapse

Snah001 said:
Not here. DPI is still at 240.
Flashed kernel, UV 75mV and all looks ok. :good:
Click to expand...
Click to collapse
Flashed on top of the original Asus 10.6.1.14.4 firmware?

Pretoriano80 said:
Flashed on top of the original Asus 10.6.1.14.4 firmware?
Click to expand...
Click to collapse
I had already changed the build prop file to set dpi to 213 and when I flashed this new kernel it held the setting.
Obviously if you edit the build prop file then your setting remains however if you haven't then maybe it will change to 160. This I'm not sure about since if the default set by stock ROM is 240 and this is what we edit, why would it change to 160?

Pretoriano80 said:
Flashed on top of the original Asus 10.6.1.14.4 firmware?
Click to expand...
Click to collapse
Yes, just flashed kernel as always
Sent from my Asus Infinity TF700 with Dock

Does anyone have the md5 handy for the kernel zip? Thanks in advanced...
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

calvinb1 said:
Does anyone have the md5 handy for the kernel zip? Thanks in advanced...
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
This
abbea13a9c1f9efa46fd4235a6a2f1b9

eckka said:
Obviously if you edit the build prop file then your setting remains however if you haven't then maybe it will change to 160. This I'm not sure about since if the default set by stock ROM is 240 and this is what we edit, why would it change to 160?
Click to expand...
Click to collapse
For some unknown reason, the default build.prop on the TF700 contains the line "ro.sf.lcd_density=160" - the correct 240 dpi is set by the stock kernel's ramdisk. I removed the latter, so the setting in build.prop takes effect.
calvinb1 said:
Does anyone have the md5 handy for the kernel zip? Thanks in advanced...
Click to expand...
Click to collapse
Ah, I forgot to mention this, which I now added to the OP:
You don't need an MD5 sum. Enable "Zip file signature verification" in TWRP instead - it checks the SHA1 checksum embedded in the archive, which is both more secure and more convenient.

[DISCONTINUED][KERNEL][G906S/K/L][4.4][5.0] Lolliwiz Kernel R10 [Sep 8]

This post can be updated anytime.
For korean support and for those who can translate Korean, visit my blog:
http://kykint.tistory.com/
Download TWRP Recovery v2.8.7.0 for G906SKL
/* Requirements */
* Galaxy S5 broadband LTE-A (SM-G906S, G906K, G906L)
* Samsung stock firmware or Dokdo-projct
- Kitkat: ANK1
- Lollipop: BOG2 for G906K, BOH1 for G906S/L
* Custom recovery (Philz, TWRP, etc)
/* Note before using */
* Backup important data before installing
* Upon installation, every warranty inclusing KNOX becomes void
* I, kykint, am not responsible for any inconvenience or problems that occur while using this kernel
* Only one hotplug driver should be on (mpdecision, intelli_plug, alucard_hotplug, lazyplug)
Lazyplug is currently not supported on kernel customizing applications. Wait until their developers update.
* Dokdo-Project version of lolliwiz is highly experimental. Don't complain about battery drain.
It also does not support uninstaller yet.
/* About new installer */
Since Release 9, the installer will automatically extract your device's ramdisk, merge it with lolliwiz kernel, and then install it.
Upon installation, if a backup folder (/system/lolliwiz-bak) is found, it will automatically restore it first and then continue installation.
It will backup original boot.img and sensors library to the backup folder (/system/lolliwiz-bak) while installing.
There might be some problems regarding this new installer, so please keep the following instructions in mind.
* When installing another variant's ROM, do not install lolliwiz right after flashing ROM.
Install the stock kernel of your variant, and then install lolliwiz.
* Those who have been using R8 or older version of lolliwiz must flash stock kernel first before installing R9 or later.
* Do not install stock kernel when lolliwiz is installed on your device.
Only install stock kernel when uninstaller fails to remove lolliwiz and restore to stock kernel.
/* Kernel features */
Built with custom compiled krait-optimized UBERTC 5.2.1
Various compile optimization flags
Various improvements backported from Linux mainline
CPU Governors: franco interactive & conservative, intelliactive, and a lot more
I/O Schedulers: CFQ, ROW, DEADLINE, SIO, FIOPS
Custom hotplug drivers: intelli_plug, alucard_hotplug, lazyplug
CPU Voltage control
Adreno_idler GPU governor addon
Simple_ondemand is not crashing anymore
Display gamma control
Dynamic FSync Control
SELinux set as permissive by default
FauxSound ported for wcd9330 (LP only)
Support for kernel mode NEON
Optimized Kernel Samepage Merging
Quickwakeup driver by Motorola
Random driver ported from latest Linux mainline
Adaptive LowMemoryKiller
Full support for F2FS
Power-efficient Workqueue
Unaligned access support for lib
Init.d script support
Various minor fixes and improvements
/* Changelogs */
Refer to the 3rd post
/* Kernel customization */
Recommended applications: Kernel Adiutor, TricksterMod
/* Downloads */
Lolliwiz & stock kernels
Previous versions of lolliwiz
LW-G906-Dokdo-R*.zip : for Dokdo-Project users
LW-G906-R*_F2FS.zip : for F2FS users
/* F2FS Conversion Manual */
Refer to the 2nd post.
/* Chatters */
Release 9 and 10 are mostly bug fix releases, so there isn't much difference.
Kitkat support has been put off to R11, and if a bug is found again and R11 happens to be released early, it will be put off to later release again.
Still, I'm considering EOL of kitkat version as it is becoming harder to support the old Linux version.
/* Contacts */
You can contact me through telegram @maplezeon, but I won't listen to complaints.
On weekdays I'm mostly at school, from 7am to 10pm, so there's no much time for chats.
/* Source */
http://pc.cd/U2YrtalK
/* Special thanks to */
세이님, 티라미슈님, hsk님, arter97님, JustArchi, Christopher83, faux123,
franciscofrancoeng.stk, flar2, imoseyon, friedrich420, Google, Samsung
and every single one of you guys, for using my kernel
XDA:DevDB Information
Lolliwiz Kernel for SM-G906, Kernel for the Samsung Galaxy S 5
Contributors
kykint
Source Code: http://pc.cd/U2YrtalK
Kernel Special Features:
Version Information
Status: Stable
Created 2015-04-28
Last Updated 2015-09-11

Changelogs
Release 10 - Sep 7
Reverted GCC 5+ compatibility improvement patches
=> Hopefully fixed some applications disappearing
Unaligned access enabled explicitly for lib
Release 9 - Sep 6
Brand new installer
=> Now support all three variants (S/K/L), boot.img and sensors library are backed up in /system/lolliwiz-bak
Add uninstaller
Fixed proximity sensor not working
=> Caused by Merge of G906K Kernel source, solved by installing sensors library from OG2 firmware
Applied patches regarding media driver
Updated lz4 source and enable unaligned access
NVIDIA's power savings patch
Westwood as default TCP congestion control method
Optimized intelli_plug
New hotplug driver: Lazyplug by arter97
=> Currently not supported on kernel setting applications, wait for updates
Some GCC 5+ compatibility improvements
Release 8 - Sep 1
Added experimental support for Dokdo-Project
(Compatible with all three variables and every version of Dokdo-Project)
KK support dropped at the moment
LP: Common: Merged G906K OG2 kernel source
LP: kt: Merged OG2 ramdisk
LP: skt,lgu: Merged OH2 ramdisk
LP: kt: fixed a typo in ramdisk
Linux 3.10.70
Full F2FS support + source updated to the latest
Power-efficient workqueue
Random driver backported from Linux 4.2+
Another new hotplug driver - Alucard hotplug
Custom built UBERTC with Krait optimizations
New build optimization flags
Fixed min cpu frequency changing on its own
Dynamic fsync disabled by default
built-in support for NTFS
Other miscellaneous fixes and updates
Release 7 - Jun 28
LP: Imported patches from upstream (1,000+ patches)
LP: Linux 3.10.59
KK: Imported patches from upstream (300+ patches)
KK: Linux 3.10.6
Compile optimization flags from arter97's kernel, big thanks to @arter97
Added adreno_idler addon for adreno-msm-tz GPU governor
Removed Simple GPU Algorithm
Switched to UBER Toolchain, GCC 5.1
Added motorola's quickwakeup driver
Added patches to reduce wakelock
Backported random driver from Linux 4.0.6
Optimized KSM
Added adaptive_lmk
Various small fixes & improvements
Release 6 - May 30
Added support for KitKat
Fixed wrong boot.img arguments
Fixed Sweep2Sleep not working on some variants
Removed SEANDROID warning on boot logo
Added advanced TCP congestion methods
Disabled crc check for better performance
Merged BOE1 changes
Ramdisk compressed with LZ4
Other small tweaks & fixes
Release 5 - Apr 20
Removed smartassV2 CPU Governor
Added mythx_plug CPU Governor
Added support for kernel NEON mode
Removed Franco's Sound Control
Ported FauxSound for work with wcd9330
Applied patches for gpu and video driver
Imported latest interactive & conservative governor from franco's shamu kernel
Added support for KSM on/off
Enabled tuning option for Cortex-A15
Some minor fixes from faux123

F2FS Conversion manual
/* F2FS Conversion Manual */
(for LP and Dokdo-Project only, no KK support)
(Not tested on Dokdo-Project)
I will not add any additional explanations about F2FS, since this is a very risky task and recommended only for experts,
and since not knowing about F2FS means that you're not one of them.
Cautions
1. Conversion process of /data partition and filesystem will wipe away every single data in your device,
so every data in internal sdcard should be backed up on your PC.
2. Flashing /cache partition image when the device has already been converted to F2FS will format /cache partition to EXT4,
so manual conversion process of /cache partition to F2FS must be done again.
3. The /cache partition image mentioned above is included in stock firmware package, so be careful when installing stock firmware
4. Inside stock firmware is included a stock kernel which only supports EXT4, so again, be careful when installing stock firmware
5. /data and /cache partition must be set to the same filesystem, both EXT4, or both F2FS
6. I personally recommend that every process be done using my TWRP recovery, which will be posted in a seperate thread later.
7. The F2FS version of kernel zip has a '_F2FS' tag at the end of its filename, while EXT4 has nothing.
Be careful, Dokdo-Project version supports both EXT4 and F2FS, so they're not seperated,
and when converting to F2FS on Dokdo-Project, you can skip kernel switching(reinstalling) process.
How to change filesystem on TWRP
Wipe > Advanced Wipe > (Select a partition) > Repair or Change File System > Change FIle System > (choose between EXT4 and F2FS) > Swipe to Change
* It takes a great amount of time when changing to EXT4, up to several minutes.
How to check current filesystem on TWRP
Wipe > Advanced Wipe > (Select a partition) > Repair or Change File System
and you'll see your current filesystem on the upper part of the screen.
Converting to F2FS
0. For stability, flash uninstaller first if you already have lolliwiz installed.
1. Install F2FS version of Lolliwiz. (_F2FS.zip)
2. Change the filesystem of /data and /cache partition to F2FS.
3. Reboot into recovery mode again.
Back to EXT4
0. For stability, flash uninstaller first if you already have lolliwiz installed.
1. Install EXT4 version of Lolliwiz.
2. Change the filesystem of /data and /cache partition to EXT4.
3. Reboot into recovery mode again.
Installing stock firmware on F2FS
1. Reboot into download mode and install stock firmware with odin as usual.
2. When the installation finishes, it'll automatically reboot into recovery mode and flash CSC package.
Wait until androboy disappears and the device reboots again.
3. Reboot into download mode again.
4. Install my TWRP.
5. Reboot into recovery right after installing.
6. Install F2FS version of lolliwiz.
7. Format /cache partition to F2FS
8. Run factory reset if needed. This is an option.
9. Reboot.
If the device won't boot even if you carefully followed all of the above instructions, repeat the process again.

Thanks

Thanks I was on the Korean forums yesterday trying to translate lol.

I noticed there's a test for b5. Giving it a try.
One issue I seem to have on b4 and 5 test is that no matter what kernel tuning app I use if I turn off mpdecision and intelliplug on, after a reboot mpdecision always comes back on.

Audioboxer said:
I noticed there's a test for b5. Giving it a try.
One issue I seem to have on b4 and 5 test is that no matter what kernel tuning app I use if I turn off mpdecision and intelliplug on, after a reboot mpdecision always comes back on.
Click to expand...
Click to collapse
Kernel settings are set to defaults on each reboot and the default setting on hotplug is mpdecision on, intelli_plug off. That's why every kernel app has the ability to restore previous settings after reboot. Try enableing them, kernel adiutor works fine for me

kykint said:
Kernel settings are set to defaults on each reboot and the default setting on hotplug is mpdecision on, intelli_plug off. That's why every kernel app has the ability to restore previous settings after reboot. Try enableing them, kernel adiutor works fine for me
Click to expand...
Click to collapse
Thanks, but I told it to save settings. It's weird as all the settings were saved, including intelliplug on, but mpdecision was turned on as well. I'll uninstall it and start again!
Do you have a donation link btw?
Edit: Here is what I mean
{
"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"
}
Edit2: Strange, I reflashed the kernel and it is now working!

Audioboxer said:
Thanks, but I told it to save settings. It's weird as all the settings were saved, including intelliplug on, but mpdecision was turned on as well. I'll uninstall it and start again!
Do you have a donation link btw?
Edit: Here is what I mean
Edit2: Strange, I reflashed the kernel and it is now working!
Click to expand...
Click to collapse
Nice to hear it's working well now.
I don't get donations, maybe you could donate to the REAL developers out there, they're always working hard for us XD

Very interesting!
I'm reading the Asian forums since a week and I have found that this kernel is well used.
How can I flash back stock kernel if something happens? And where can I find stock kernels??
If they are unavailable, I'd like to make my own Odin tar.md5 files for flashing stock kernel.
Can I follow the script/batch procedure (found here on Xda) that produces the tar.md5 flashable files?
Tnx!!
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4

Thanks

PIRATA! said:
Very interesting!
I'm reading the Asian forums since a week and I have found that this kernel is well used.
How can I flash back stock kernel if something happens? And where can I find stock kernels??
If they are unavailable, I'd like to make my own Odin tar.md5 files for flashing stock kernel.
Can I follow the script/batch procedure (found here on Xda) that produces the tar.md5 flashable files?
Tnx!!
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
Click to expand...
Click to collapse
No worries, I'll upload stock kernels for recovery/odin as soon as I get back home

kykint said:
No worries, I'll upload stock kernels for recovery/odin as soon as I get back home
Click to expand...
Click to collapse
Can you do it also for KitKat if you have then?
Tnx.
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4

Sharing battery based profile still in testing
Hi everyone ,
i would like to share my battery based profile.
I used Trickstermod kernel app taken from bbs dot sonyue dot com
( The kernel app is under attachment)
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Install the app.
2. Open the app, at top left a list will open, Choose the General
3. Change the following
I/O Control:
Read Ahead Buffer Size 1024
Schedular fiops
CPU Frequency Control
Frequency Lock ON
Min 300000 (choose the lowest scroll to the top first)
Max 1574400
CPU Governor Control
Governor Conservativex
------------------------------------------------------------------------------------------------------------------------------------------
4. Now Choose Specific
Mp-Decision OFF
Intelli-Plug ON
Dynamic FSYNC ON
GPU Governor Powersave
GPU Max Frequency 240
Intelli-Thermal Control ..........> Intelli-Thermal ON
MPU Voltages
( I undervolted from Snapdragon 805 thread in xda)
< 300MHz 700
< 345MHz 710
< 422MHz 720
< 499MHz 730
< 576MHz 740
< 652MHz 750
< 729MHz 760
< 806MHz 770
< 883MHz 780
< 960MHz 820
< 1036MHz 830
< 1113MHz 840
< 1190MHz 850
< 1267MHz 860
< 1344MHz 870
< 1420MHz 880
< 1497MHz 890
< 1574MHz 900
< 1651MHz 910
< 1728MHz 920
< 1804MHz 930
< 1881MHz 940
< 1958MHz 950
< 2035MHz 960
< 2112MHz 975
< 2188MHz 990
< 2265MHz 1005
< 2342MHz 1020
< 2419MHz 1035
< 2457MHz 1040
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
Or You can download the profile in attachment and do the following:
1. Download the profile and extract it.
2. Go to your phone storage and look for a folder name tm_profiles
3. Paste it there.
4. Open the trickstermod app.
5. press at the top left and choose Tool.
6. You will find Global Profile. press restore and choose my profile Battery Test V2 pvs11 .
----------------------------------------------------------------------------------------------------------------------------------------------------------------
I hope you will test it guys and my aim is just battery light user no gaming.
Please feedback its just test if you more knowledge share as i already contacted the OP permission to open a profile thread.
@kykint
Undervolting source
http://forum.xda-developers.com/htc-one-m8/general/guide-snapdragon-801-clocking-voltage-t2807173

kardinal969 said:
Hi everyone ,
i would like to share my battery based profile.
I used Trickstermod kernel app taken from bbs dot sonyue dot com
( The kernel app is under attachment)
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Install the app.
2. Open the app, at top left a list will open, Choose the General
3. Change the following
I/O Control:
Read Ahead Buffer Size 1024
Schedular fiops
CPU Frequency Control
Frequency Lock ON
Min 300000 (choose the lowest scroll to the top first)
Max 1574400
CPU Governor Control
Governor Conservativex
------------------------------------------------------------------------------------------------------------------------------------------
4. Now Choose Specific
Mp-Decision OFF
Intelli-Plug ON
Dynamic FSYNC ON
GPU Governor Powersave
GPU Max Frequency 240
Intelli-Thermal Control ..........> Intelli-Thermal ON
MPU Voltages
( I undervolted from Snapdragon 805 thread in xda)
< 300MHz 700
< 345MHz 710
< 422MHz 720
< 499MHz 730
< 576MHz 740
< 652MHz 750
< 729MHz 760
< 806MHz 770
< 883MHz 780
< 960MHz 820
< 1036MHz 830
< 1113MHz 840
< 1190MHz 850
< 1267MHz 860
< 1344MHz 870
< 1420MHz 880
< 1497MHz 890
< 1574MHz 900
< 1651MHz 910
< 1728MHz 920
< 1804MHz 930
< 1881MHz 940
< 1958MHz 950
< 2035MHz 960
< 2112MHz 975
< 2188MHz 990
< 2265MHz 1005
< 2342MHz 1020
< 2419MHz 1035
< 2457MHz 1040
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
Or You can download the profile in attachment and do the following:
1. Download the profile and extract it.
2. Go to your phone storage and look for a folder name tm_profiles
3. Paste it there.
4. Open the trickstermod app.
5. press at the top left and choose Tool.
6. You will find Global Profile. press restore and choose my profile Battery Test V2 pvs11 .
----------------------------------------------------------------------------------------------------------------------------------------------------------------
I hope you will test it guys and my aim is just battery light user no gaming.
Please feedback its just test if you more knowledge share as i already contacted the OP permission to open a profile thread.
@kykint
Undervolting source
http://forum.xda-developers.com/htc-one-m8/general/guide-snapdragon-801-clocking-voltage-t2807173
Click to expand...
Click to collapse
Good!
I'm following the Asian forum where I've found this kernel and related config app, from which I've read that there's a modified version of the app....And for this please give me some infos.
I'm also searching for some interesting custom rom as I see there are some, like the KingWolf one or the Milan one.
Any help on using this kernel with some roms?
Tnx!
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4

PIRATA! said:
Can you do it also for KitKat if you have then?
Tnx.
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
Click to expand...
Click to collapse
I uploaded lollipop stock kernels for both recovery and odin. I'll upload for kitkat as well when I get the latest kitkat firmware.

Sorry, this might be a dumb question, but I'd rather ask it then brick my only smart-phone:
I'm currently on miscom's ROM (see here: http://forum.xda-developers.com/galaxy-s5/development/galaxy-s5-g906-custom-rom-t2848569)
Also using Philz recovery
How do I get to the Lolliwiz Kernel safely? Can I keep my apps, settings and so on?
Again, sorry. This is my first android phone (but certainly not the last one!) and I'm pretty clueless... But getting the miscom kernel on it was pretty easy with a bit of reading...

mcbrite said:
Sorry, this might be a dumb question, but I'd rather ask it then brick my only smart-phone:
I'm currently on miscom's ROM (see here: http://forum.xda-developers.com/galaxy-s5/development/galaxy-s5-g906-custom-rom-t2848569)
Also using Philz recovery
How do I get to the Lolliwiz Kernel safely? Can I keep my apps, settings and so on?
Again, sorry. This is my first android phone (but certainly not the last one!) and I'm pretty clueless... But getting the miscom kernel on it was pretty easy with a bit of reading...
Click to expand...
Click to collapse
Make a backup of whole apps with TitaniumBackup first, then backup system, data, boot in philz recovery(run custom backup) and flash stock lollipop through odin. miscom's rom is 4.4.2 as I know of, and my kernel supports 5.0.1 only at the moment.
If your phone bootloops after flashing lollipop, factory reset through philz and restore apps from TitaniumBackup, or flash back stock kitkat firmware and then restore system, data, boot in recovery.
Note that flashing stock firmware will blow away your recovery and you should manually install it again with odin. Also, factory reset through philz will preserve your internal sdcard but stock recovery WILL NOT.

kykint said:
Make a backup of whole apps with TitaniumBackup first, then backup system, data, boot in philz recovery(run custom backup) and flash stock lollipop through odin. miscom's rom is 4.4.2 as I know of, and my kernel supports 5.0.1 only at the moment.
If your phone bootloops after flashing lollipop, factory reset through philz and restore apps from TitaniumBackup, or flash back stock kitkat firmware and then restore system, data, boot in recovery.
Note that flashing stock firmware will blow away your recovery and you should manually install it again with odin. Also, factory reset through philz will preserve your internal sdcard but stock recovery WILL NOT.
Click to expand...
Click to collapse
Wait a minute!!! I though that factory reset in Philz recovery for G906 was not working and doing that would brick the phone!!!!!
I've read this in the info thread on the S5 G906 here on XDA!!!
Look under here in the Known issues:
prodigiez said:
.........
CWM
Unofficial PhilZ recovery is also available as below
Credit to hsk for unofficial CWM
updated : adb fix for cwm
Source: http://www.matcl.com/?m=bbs&bid=appDB&where=subject|tag&keyword=hsk&uid=231166
PhilZ Touch official thread http://forum.xda-developers.com/showthread.php?t=2201860
Download unofficial philz cwm here
This document is unofficial (Unofficial) ported version.
There may be bugs, so please use at your own risk.
Before flashing this, you must understand the contents of this post after you decide whether to apply please.
G906S/K/L = Tested working.
Flashing guide
Flash philz cwm with Odin as AP/PDA
Uncheck Auto Reboot and Start flashing.
Once completed , disconnect the USB cable and enter recovery manually by pressing the combination key.
Recovery time and date synchronization
PhilZ Settings - GUI Preferences - Time Setup - Change date and time - Qualcomm Time Daemon and (x) check - Yes Load Time Daemon
PhilZ Settings - GUI Preferences - Time Setup - Time Zone ( your preferred timezone )
Date / time will be synchronized with the system.
Reboot device.
Known issues:
KNOX Warranty 0x1
.
Wipe Data / Factory Reset from Clean to Install a New ROM feature is not working and might brick your device. Do not use this feature. If you brick your device , you may download the stock firmware from sammobile and flash it with ODIN.
CWM does not work with adb. CWM now works with ADB
CWM does not work with aromafm.
Credit to : XDA , PhilZ , hsk , bluecloud ,dougiebee and whoever involve. Tks
.......
Click to expand...
Click to collapse
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4

Great.... Bricked it.... Gonna need you guys' help again....
Did it like instructed... After flashing stuck lollipop, stuck on the second boot logo ("olleh o" for me).
Since recovery went back to stock, tried a factory reset and cache delete from the stock recovery... no help....
UPDATE: HOLD THE HELP!!! Unbricked it! On Stock Lollipop now... Working on it... Will get back to you....

[KERNEL] [ROOT] [SM-N920T/W8] Exynos 7420 | SkyHigh Kernel

[KERNEL] [ROOT] [SM-N920T/W8] Exynos 7420 | SkyHigh Kernel [ v6.8.0-EOL ] | Synapse | Aroma | F2FS | UBERTC 6.2.1 20161012
The BEST & FULLY FEATURED EXYNOS 7420 KERNEL IS REBORN . . . . .
Many select patches for better security, performance and efficiency (not all listed). THERE IS "NO NEED" to tweak anything -- Just FLASH it !! But, if you desire, can further tweak many settings and available features with Synapse to suit your own habits and device capability. That is for you to find out
SUPPORTED DEVICES:
SM-N920T
SM-N920W8​
RAMDISK BASE:
N920T : N920TUVS4DPH2 ​
FEATURES:
Modified from the LATEST device specific official Samsung source(s): Samsung OSRC
AUTO-ROOT SYSTEM-LESS SR3-SuperSU-v2.78 (on flash)
KNOX WARRANTY VOID: 1
SELinux PERMISSIVE (default) or ENFORCING
DEEP SLEEP FIX
UX ROM (BOOT support only)
AROMA Installer (set your own defaults)
Auto-Install busybox v1.24.1-Dorimanx & Sqlite3 to /system/xbin (on flash)
Compiled with UBERTC 6.2.1 20161012 + Graphite optimizations
Linux 3.10.104
init.d script support (drop in script & set permissions to 755 or 777 and reboot)
adb insecure
stock dt.img
Secure storage = false (should prevent WIFI settings & passwords wiping on reboots)
Reduced logging
F2FS experimental support (Much faster I/O - write speeds).
exFAT FS support
NTFS R/W support with app
CIFS support (not tested)
ISO 9660 CDROM & UDF FS support
Frandom
mount all partitions NOATIME (better performance & efficiency)
mount EXT4 /data & /cache partitions LAZYTIME (better performance & efficiency)
A53 LITTLE cores increased boot frequency (faster boot)
LZO ramdisk de/compression algorithm (faster boot)
CLEANCACHE & ZCACHE
Microsoft X-BOX gamepad controller module (updated)
Slub tweaked
Invisible CPUSETs (better efficiency)
A tonne of select patches for features, better performance & efficiency
Synapse app support for many kernel configurations + much much more !!
SYNAPSE FEATURES:
Too many too list . . . Have a look through Synapse yourself. If you don't know, then read and research or leave it DEFAULT !!
About
A57 CPU frequency scaling
A57 voltage control
A53 CPU frequency scaling
A53 voltage control
CPU governor
A57 governor tunables
A53 governor tunables
Multicore
CPU stats
Boost
GPU frequency scaling
GPU voltage control
Thermal
BUS
IO
Memory
Advanced
Power Suspend
Doze
Wakelocks
Audio
Battery
LED
Screen
Network
Security
FS (file system)
CortexBrain
Crontab
USB mode
Modules
Backup & Restore profiles + EFS (auto on boot to /sdcard/SkyHigh/EFS)
Logs
Reboot
Info
CREDITS:
My family !!
Chainfire - root & SuperSU app
AndreiLux - years of support for Exynos development and his various kernel features + Synapse app and UCI code
halaszk88 - patches and some Synapse code I adapted to many of my kernels
dorimanx - BusyBox and various ramdisk tweaks/ideas
apb_axel - I adapted and used many of the Synapse controls to suit my kernels
arter97 - various source fixes/patches
ktoonsez - ktoonservative hotplug governor
YashdSaraf - BusyBox-Cleaner script
Android File Host
Linus Torvalds & Linux Foundation
Google & Samsung OSRC
and many others!
All those in my select private group that have provided constructive feedback, help, and support.
IF I'VE FORGOTTEN ANYONE, PLEASE DON'T BE SHY AND SPEAK UP, THANKS
XDA:DevDB Information
SkyHigh Kernel for N920T/W8 devices, Kernel for the T-Mobile Samsung Galaxy Note5
Contributors
UpInTheAir
Source Code: https://www.androidfilehost.com/?w=files&flid=88214
Kernel Special Features: Aroma - Synapse ++ almost everything !!
Version Information
Status: Stable
Current Stable Version: 6.8.0-EOL
Stable Release Date: 2016-11-19
Created 2016-07-30
Last Updated 2016-11-19

License - requirements - installation - download - source
DON'T POST LAME QUESTIONS THAT YOU CAN FIND THE ANSWER TO BY A LITTLE SEARCHING.
I AM NOT GOOGLE & NEVER PRETEND TO KNOW EVERYTHING, SO A LITTLE HELP FROM YOURSELF WILL GO A LONG WAY. . .
THANKS & ENJOY !!
** LICENSE & DISCLAIMER **
/*
© Copyright (c) 2015-2016 UpInTheAir <[email protected]>
All rights reserved. The alterations from OEM, associated script files and coding packed within this ramdisk & installation package (the "Software"), may not be reproduced, displayed, modified or distributed without the express prior written permission of the copyright holder. For permission, contact [email protected].
The above copyright notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF , FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
*/
In plain language
DO NOT STEAL MY SH*T !!
UpInTheAir is NOT responsible, the person you see in the mirror is !!
REQUIREMENTS:
Supported variant only !!
Touch Wiz Android M 6.0.1 ROM or UX leaked firmware (beta support)
Appropriate custom recovery (i.e..TWRP for your variant)
INSTALLATION & UPDATE:
If you have Synapse installed = = you must clear Synapse app data before flash !!
Device Settings: Enable Developer Options > OEM UNLOCK is ENABLED
Boot into custom recovery (volume UP + home + power)
DO NOTHING but flash SkyHigh kernel.zip (ALWAYS flash again AFTER any custom ROM installation, system or data wipe)
After flash == DO NOTHING but REBOOT IMMEDIATELY from TWRP or you will have to re-flash !!
CONVERT EXT4 TO F2FS FS:
If not already, install the latest TWRP for your device variant (ie. 3.0.2-2). This must support F2FS.
Boot into TWRP.
Insert USB-OTG
** ALL DATA WILL BE WIPED FROM INTERNAL STORAGE (restored later)
Backup (copy) all important files (incl. your NANDROID) off device (ie. from internal storage > USB STORAGE). This can take a while. Advanced > File Manager > .....
Home > Backup > Select Storage > USB Storage > OK > "Swipe to Backup" (Only need DATA, but recommend to backup all partitions).
Install > Select Storage > USB Storage > OK.
Select f2fs.zip > "Swipe to confirm flash" (This will WIPE ALL DATA !! & convert DATA & CACHE to F2FS. System is not supported by kernel).
Check the box to remember setting and “Swipe to allow Modifications”.
If you do not have Step #8, then Data was not converted to F2FS.
Mounts > unchecked both Cache & Data. Repeat Step #7 & 8.
Restore > Select Storage > USB Storage > OK > Select TWRP Backup folder > DATA ONLY !! > "Swipe to Restore" (ignore warning about EXT4).
Home > Install > Select Skyhigh_kernel.zip > "Swipe to confirm Flash".
Home > Mount > USB STORAGE > uncheck/unmount (then remove USB-OTG).
Home > Reboot > SYSTEM.
Wait ~2-5 mins for boot.
Once booted, let stabilize for ~5 mins.
You can check Data & Cache F2FS FS status in either /proc/mounts or Synapse app (FS section).
Use a root type explorer (su permission) & navigate to /sdcard, and delete the "0" folder.
Move (copy) your backed up files from Step #4 to internal storage (/sdcard). This can take a while. Maybe one folder at a time is better?
ISSUES ?
If using TWRP MTP mode, deleting some folders/files may crash TWRP and cause corruption. Instead, use a root type file explorer to delete from device.
If you need to wipe data, then use the ext4 or f2fs.zip, otherwise this is not possible with this TWRP !!
Not tested any method with customized ROMs. The ROM installer script may re-format partitions back to EXT4 or not mount correctly causing TWRP crash or corruption. I can only suggest to Flash ROM with EXT4 FS > make a NANDROID on USB-OTG and then follow the F2FS steps above.
CONVERT F2FS TO EXT4 FS:
The Same steps as above, but use the ext4.zip !!
OPTIONAL SYNAPSE INSTALLATION:
After boot:
Wait at least 120 secs to stabilize
Install Synapse app from Google Play and rate it ☆☆☆☆☆ !!
Open Synapse
Tap "Understood"
So changes stick every time you start Synapse == Make any change & 'apply'.
Recommend: Disable KNOX with Synapse
DOWNLOADS:
** I will NEVER support KOREAN (S/K/L) variant. Get over it and flash ARTER kernel instead !! **
Mod Edit: Link removed.
BUGS:
Aroma Installer: 10% of installation will encounter Aroma installer "freeze". It's only the display that freeze, the script still execute in the background. Just wait a minute, then press slightly to the top right 'home' key / top left of the 'back' key . . .
UX BETA firmware - blue light filter
UX BETA firmware - torch light (some ROMs)
HD voice ? - Speakerphone: other party cannot hear voice
SOURCE - ALL SkyHigh VARIANT:
Available upon request.
v6.6.1 AFH
v6.8.0 uploaded soon. . . . .
.

FAQ & HELP
TROUBLESHOOTING GUIDE:
I might not have your device variant and or able to reproduce your "issue".
Please provide as much information as possible.
Without resetting your device to a stable unmodified baseline, any potential troubleshooting or logs could be meaningless.
So please follow the guidelines set out below. Users can't "read minds".
Without providing important information, we are unable to help YOU.
Search thread, XDA and Google before posting
Provide as much information as possible.
- Device model
- Firmware version
- ROM name / version
- Kernel version
- Modem version
- Bootloader version
- Synapse settings (try default)
- Installed tweaks and apps etc (Xposed ?)
- The exact steps you've taken to try resolve the issue yourself.​
Exact steps to reproduce the issue. Provide screenshots if able.
Does it work with older / other versions etc
Reset your device to a stable baseline (ie. stock) with only custom TWRP recovery and kernel (FULL WIPE: system, cache, dalvik-ART)
Possible logs
FAQ & HELP:
CAN I BUILD A KERNEL FOR YOUR __XX DEVICE ?
Sorry. I don't have the spare time for any more variant support.
Additionally, I do not build for any device that I can not compile using SAME source, personally test method or debug. Some device variants can compile with same source.
CAN I INCLUDE SkyHigh KERNEL IN MY ROM
NO == My ramdisk modifications are COPYRIGHT (refer LICENSE in Post #2), and distribution without MY (UpInTheAir) prior written consent is not only in a breach of that license, but also XDA Rule #12)
Although I do appreciate your contribution, if you could please do not include my kernel in any ROM package etc. This policy goes for anyone.
Having my kernel distributed outside my development thread just removes a lot of credit and more importantly, constructive user feedback that could be helpful to my development or user issue.
ALWAYS on DISPLAY (AoD)
I have spent some time to attempt port S7 display drivers to our kernel, but haven't had success as yet with too many errors.
TBH, it's a lot of work for something I'm not really interested in or would use. . . so I don't wish to spend any more of my own time on it, sorry. If someone else does it, GREAT
DO I "NEED" SYNAPSE
THERE IS NO "NEED" !!
It is "recommended", which is OPTIONAL, and not "needed".
It is for ADVANCED or adventurous users who wish more control of their device or use various features I've added.
Using any other optional tweaking or control app may conflict & many features and options won't be available.
WHY WAIT 120 SECS
The kernel and Synapse scripts need time to boot up properly and allow SU permission.
There are scripts / code that have a deliberate delay and must run after Synapse. These are not user optional.
Synapse has a stability check on boot. You may get "synapse boot cancelled".
Thermal throttling will be trying to limit many things, let the device settle
OTHER PARTY CAN NOT HEAR VOICE ON SPEAKER PHONE
It could be a conflict in the system/etc/mixer_*.xml. I don't know for sure, but if I exclude the sound mod, then this "fixes" the problem.
As I cannot reproduce the issue (and the majority), then the audio mod stays.
Unfortunately, making it optional would require to build kernels without and create much more work for many device I don't actually use.
Either live with it, or use another kernel. Sorry.
"NO UCI SUPPORT"
It's a ROM busybox compatibility issue !!
Re-flash kernel as per Installation Instructions. (kernel install zip flashes proven busybox binary to /system/xbin)
BACKUP / RESTORE ISSUES
It's a ROM busybox or sqlite3 compatibility issue !!
Re-flash kernel as per Installation Instructions. (kernel install zip flashes proven busybox binary to /system/xbin)
BACKUP & RESTORE
DO NOT restore profiles from different kernel version
Refer to THIS post for "how-to" screen-shots
Refer to THIS post for a "how-to" video
LOADABLE MODULES AREN'T WORKING
Check your /system/lib/modules directory. Are any ____.ko present?
Did you flash a ROM or wipe the system partition at any point? Doing this will remove them !
Re-flash the kernel will install the modules.
If modules aren't installed after flash, then re-flash and manually mount system in recovery first.
You can check running modules in terminal with:
​lsmod
KTOONSERVATIVE GOVERNOR
Some info from the author HERE
DT2W & COLOUR CONTROL
No, I cannot make it work properly with single source for all supported variants
CPU POWER CONSUMPTION
The Samsung Exynos 7420 Deep Dive - Inside A Modern 14nm SoC (by ANANDTECH - Andrei)
F2FS SUPPORT
It's not needed. You wouldn't see any difference or measure much, if anything. Not worth the potential trade-off. This is not eMMC anymore
Storage Benchmarks
STUCK ON SAMSUNG BOOT LOGO AFTER FLASH
Ensure you flashed the correct kernel for your device model
Ensure your download is not corrupted. Check MD5 hash or re-download
Your current base firmware (ROM, boot-loader version etc.) may be incompatible - UPDATE to latest with Odin and try again.
CM SUPPORT
Read THIS
BATTERY TIPS (require updating !! )
Try some (or combination) of the CPU MULTICORE features in Synapse:
HMP profile = Default (values are battery orientated)
Power Aware Scheduling (slight performance cost) = Enabled
HMP LITTLE Packing (slight performance cost) = Enabled
PEWQ (power-efficient workqueue) (slight performance cost) = Enabled
Set A57 & A53 Interactive governor profile = Battery
Set Input-Booster for key/touchkey profile = Battery
Multi-tasking: enable UKSM & "low" or "quiet" profile (slight performance/battery cost)
PERFORMANCE TIPS (requires updating !! )
Set A57 & A53 Interactive governor profile = Performance
Set A57 & A53 Interactive governor = Turbo Mode (battery cost)
Set HMP threshold profiles = Stock or Performance
Once in a while:
Optimize Databases
FSTrim​
RANDOM REBOOT
Don't UV or UC CPU or GPU
Use SkyHigh defaults
Use a stock UNMODIFIED ROM for your device variant
No tweaks, Xposed or other CPU control apps installed
Follow the TROUBLESHOOTING GUIDE
ASV_GROUP (ALL DEVICES ARE NOT CREATED EQUAL)
THIS is an example from my Exynos5420 source. Similar idea for Exynos4
DOWNLOAD LINK NOT WORKING
I want to keep this project all in one place - ☆☆ NO MIRRORS ☆☆
Please try again in a few minutes
POOR CPU/GPU BENCHMARK or GRAPHICS PERFORMANCE
Disable any CPU MULTICORE options in Synapse
Disable any Battery profiles in Synapse. Set to default or Performance.
Allow the device to cool. Repetitive testing will heat the device hardware and invoke thermal throttling and lead to decreased benchmark.
HIGH CPU/GPU OC == excessive heat == thermal throttling == reduced clock frequency == DECREASE PERFORMANCE
DYNAMIC MANAGEMENT OF DIRTY PAGE WRITEBACKS
by Christopher83
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
TCP/IP NETWORK SECURITY
Thanks to zeppelinrox & V6SuperCharger
Hardening the TCP/IP stack to SYN attack
Bump up tw_buckets in case we get DoS'd
Ignore pings
Don't cache connection metrics from previous connection
Don't pass traffic between networks or act as a router
Enable spoofing protection (turn on reverse packet filtering)
Don't accept source routing
Don't accept redirects
Further reading:
http://www.cyberciti.biz/faq/linux-kernel-etcsysctl-conf-security-hardening
http://www.symantec.com/connect/articles/hardening-tcpip-stack-syn-attacks
CHROMECAST - STREAMING PROBLEMS
Lock screen MUST be enabled (simple screen lock swipe) I don't know why but it breaks the chromecast app's ability to resume smoothly if switched off
Synapse > Network > DTIM (both screen ON & OFF) = 1
Synapse > Network > WIFI Power Mode (screen OFF) = FAST

@UpInTheAir needed to create these threads to compile them for Synapse. He contacted me to close these as soon as he made them until he is ready with the finished product. Have patience.
Also I would like to apologize to UITA as the last ban may have been due to a system glitch where the signature was restored upon return, so was unjust. I have seen these glitches before and better communication might have prevented the error. We will do better going forward!

SkyHigh KERNEL REBORN - v5.6 released !!
SkyHigh KERNEL REBORN - v5.6 released !!
Hi fellow members.
Please find my latest release for SkyHigh kernel. There are many many changes, both visually (more / improved features) and a upgraded engine (better performance & efficiency) since I last publicly released. Far too many to talk about. . . .
And no - it DOES NOT fix call audio issue with leaked UX ROM. I believe it to be a ROM issue n!
Please note that although I have taken as much care in building and testing by my friends and I, the kernel may still not perform as hoped for you. Could be due to various factors including (but limited to):
hardware quality
firmware installed (incompatibility)
user habit (how you use the device)
apps & mods installed, customization's (conflicts)
user kernel settings (read them carefully - if in doubt == defaults)
As noted in Post #3, I may not have your device variant and not be always able to help either. In the end, sometimes SkyHigh is just not meant for you . . . .
If you have issues = = READ & FOLLOW ALL Posts #1-3
READ & FOLLOW THE INSTALLATION INSTALLATIONS EXACTLY (or else device will not boot)
Also please note (as per OP) the support for UX based ROMS is still in beta. I have personally tested very briefly, and also some of my friends (not all variant)
Enjoy
UITA
.

Welcome back with a MF'IN Vengeance and a new colorful avatar and best yet a beast of a kernel. Testing a few setups, glad to see ya here. Dr gave you a nice supply of xanax to deal with the idiots? :x
Sent from my SM-N920T using XDA-Developers mobile app

n0ve said:
Welcome back with a MF'IN Vengeance and a new colorful avatar and best yet a beast of a kernel. Testing a few setups, glad to see ya here. Dr gave you a nice supply of xanax to deal with the idiots? :x
Sent from my SM-N920T using XDA-Developers mobile app
Click to expand...
Click to collapse

BUG Report Update: UX firmware Bluelight Filter
The blue-light issue is in kernel source.
Compiled & flash SkyHigh + stock ramdisk + stock dt.img == no blue-light
Compiled & flash SkyHigh + stock ramdisk (with permission edits) + stock dt.img == no blue-light
Compiled & flash SkyHigh + UX ramdisk + stock dt.img == no blue-light
Compiled & flash SkyHigh + UX ramdisk + UX dt.img == no blue-light
Which all points to the source I’m using . . . and nothing I can do about it. That's leaked firmware and no proper source, what else to expect. . . .

So many menues on aroma installer i got lost any tips of what option do I have to choose please? Im on tmobile note 5 running darthstalker 9.0V marshmallow 6.0.1 PG1 baseband

torhect said:
So many menues on aroma installer i got lost any tips of what option do I have to choose please? Im on tmobile note 5 running darthstalker 9.0V marshmallow 6.0.1 PG1 baseband
Click to expand...
Click to collapse
Now. If you'd actually read any of Posts #1-3 you would know then to stay with DEFAULTS. You don't "have" to change anything.

Welcome back bud looks good

UpInTheAir said:
THREAD UNDER CONSTRUCTION !!
[KERNEL] [ROOT] [SM-N920T/W8] Exynos 7420 | SkyHigh Kernel [ v5.6 ] | Synapse | Aroma
The BEST & FULLY FEATURED EXYNOS 7420 KERNEL IS REBORN . . . . .
Many select patches for better security, performance and efficiency (not all listed). THERE IS "NO NEED" to tweak anything -- Just FLASH it !! But, if you desire, can further tweak many settings and available features with Synapse to suit your own habits and device capability. That is for you to find out
SUPPORTED DEVICES:
SM-N920T
SM-N920W8​
RAMDISK BASE:
N920T : N920TUVU3DPG1 ​
FEATURES:
Modified from a combo of the LATEST official Samsung source(s): Samsung OSRC
AUTO-ROOT SYSTEM-LESS SuperSU v2.76 (on flash)
KNOX WARRANTY VOID: 1
SELinux PERMISSIVE (default) or ENFORCING
DEEP SLEEP FIX
UX ROM support (beta)
Aroma Installer (set your own defaults)
Auto-Install busybox v1.24.1-Dorimanx & Sqlite3 to /system/xbin (on flash)
Compiled with Ubuntu/Linaro GCC 5.4.0 20160609 + Graphite optimizations
Linux 3.10.102
init.d script support (drop in script & set permissions to 755 or 777 and reboot)
adb insecure
stock dt.img
Secure storage = false (should prevent WIFI settings & passwords wiping on reboots)
Reduced logging
exFAT FS support
NTFS R/W support with app
CIFS support (not tested)
ISO 9660 CDROM & UDF FS support
Frandom
mount all partitions NOATIME (better performance & efficiency)
mount /data & /cache partitions LAZYTIME (better performance & efficiency)
A53 LITTLE cores increased boot frequency (faster boot)
LZO ramdisk de/compression algorithm (faster boot)
CLEANCACHE & ZCACHE
Microsoft X-BOX gamepad controller module (updated)
Slub tweaked
Invisible CPUSETs (better efficiency)
A tonne of select patches for features, better performance & efficiency
Synapse app support for many kernel configurations + much much more !!
SYNAPSE FEATURES:
Too many too list . . . Have a look through Synapse yourself. If you don't know, then read and research or leave it DEFAULT !!
About
A57 CPU frequency scaling
A57 voltage control
A53 CPU frequency scaling
A53 voltage control
CPU governor
A57 governor tunables
A53 governor tunables
Multicore
CPU stats
Boost
GPU frequency scaling
GPU voltage control
Thermal
BUS
IO
Memory
Advanced
Power Suspend
Doze
Wakelocks
Audio
Battery
LED
Screen
Network
Security
FS (file system)
CortexBrain
Crontab
USB mode
Modules
Backup & Restore profiles + EFS (auto on boot to /sdcard/SkyHigh/EFS)
Logs
Reboot
Info
CREDITS:
My family !!
Chainfire - root & SuperSU app
AndreiLux - years of support for Exynos development and his various kernel features + Synapse app and UCI code
halaszk88 - patches and some Synapse code I adapted to many of my kernels
dorimanx - BusyBox and various ramdisk tweaks/ideas
apb_axel - I adapted and used many of the Synapse controls to suit my kernels
arter97 - various source fixes/patches
ktoonsez - ktoonservative hotplug governor
YashdSaraf - BusyBox-Cleaner script
Android File Host
Samsung OSRC
and many others!
All those in my select private group that have provided constructive feedback, help, and support.
IF I'VE FORGOTTEN ANYONE, PLEASE DON'T BE SHY AND SPEAK UP, THANKS
XDA:DevDB Information
SkyHigh Kernel for N920T/W8 devices, Kernel for the T-Mobile Samsung Galaxy Note5
Contributors
UpInTheAir
Source Code: https://www.androidfilehost.com/?fid=24651442761499085
Kernel Special Features: Aroma - Synapse ++ almost everything !!
Version Information
Status: Stable
Current Stable Version: 5.6
Stable Release Date: 2016-08-02
Created 2016-07-30
Last Updated 2016-08-02
Click to expand...
Click to collapse
Glad to see you back friend only kernel I use thank you for your work

@AmbientLights
Can you please state the full firmware version of the N920W8 boot.img you sent me ?
The latest is N920W8VLS3BPF1
EDIT: You sent me N920W8VLU2BPE3 . . . this is not the latest

Been running your latest kernel for 920t running great awesome battery life thanks
Sent from my SM-N920T using XDA-Developers mobile app

UpInTheAir said:
@AmbientLights
Can you please state the full firmware version of the N920W8 boot.img you sent me ?
The latest is N920W8VLS3BPF1
EDIT: You sent me N920W8VLU2BPE3 . . . this is not the latest
Click to expand...
Click to collapse
It turns out to be the google DNS causing the problem. I forgot L Speed was applying the google dns as well. Sorry for being wasting your time. Thanks for the support ! the kernel is smooth and the battery last longer. I can send you the latest boot.img if you still want it.

AmbientLights said:
It turns out to be the google DNS causing the problem. I forgot L Speed was applying the google dns as well. Sorry for being wasting your time. Thanks for the support ! the kernel is smooth and the battery last longer. I can send you the latest boot.img if you still want it.
Click to expand...
Click to collapse
When in Aroma, please DELETE all that interfering BS init.d 'tweaks' that are not optimised for our device. Those that come with SkyHigh are !!
Don't worry about boot.img thanks.

Cone1237 said:
Been running your latest kernel for 920t running great awesome battery life thanks
Sent from my SM-N920T using XDA-Developers mobile app
Click to expand...
Click to collapse
Only 4 hours of screen time

torhect said:
Only 4 hours of screen time
Click to expand...
Click to collapse
I see your posts in various development threads. . .
From your history, seems you're never happy with anything.. .
THREE options:
1. Read and follow what's requested of YOU top of Post #3.
2. Use a different kernel
3. Use stock

Anyone using a Grace UX rom with this kernel and if so can you link me one that's working? Been wanting to try it out.

momulah said:
Anyone using a Grace UX rom with this kernel and if so can you link me one that's working? Been wanting to try it out.
Click to expand...
Click to collapse
I don't believe the T/W8 call audio issue has been solved yet for all UX beta ROMs
UN-recognised Developer of my SkyHigh Kernel v5.6.x powered SM-N920C

[Kernel] AnyKernel for Alcatel One Touch Pop C1

About AnyKernel:
AnyKernel is a template for an update.zip that can apply any kernel to any ROM, regardless of ramdisk. -Koush
The concept of AnyKernel has been around for awhile, (originally by Koushik Dutta/ClockworkMod,) which allowed a device-specific kernel zImage to be flashed over device-specific ROM and use the ramdisk that came with the ROM to reduce the chance of any issues arising from the custom kernel pairing.
Jelly Bean:
Jellybean kernel can used to all Jellybean based ROM like AOSP, MIUI, Lewa, Etc
3.4.5 Jelly Bean kernel by @kirito9:
Features:
1) Added Governers
2) Added Double tap to wake
3) Added Sweep to wake
4) Many more
Link:
https://mega.nz/#!S4cAzY7Q!Mxr6zwbTUnbpH3QZA8jhOlgWh6WIQketaiJ08Ci7G3M
3.4.5 OverClocked Jelly Bean kernel by @chijure:
Features:
1) Based on the STOCK Source OT_4015D_20140610.tar.xz from Alcatel
2) Toolchain: Built with GCC 5.2 toolchain from Linaro
3) Linux: 3.4.5
4) CPU OC: Up to 1.4GHz
5) Thunder Sonic Sound Control Engine
6) Thunder Charge Fast Charge Driver
7) Thunder Quake Engine 1.0 - Vibration Intensity Controller for MTK vibrators
8) Swap
9) KSM: Kernel Same-page Merging enabled
10) Dynamic management of dirty page writeback
11) Dynamic Fsync: Faux123's Dynamic File Sync v1.5
12) Sweep2wake
13) Doubletap2wake
14) Lowered swappiness (60 -> 70)
15) Optimized AES and SHA1 routines for ARM cpu architecture
16) Optimized SLUB memory allocator
17) Enabled arch power
18) Disabled CRC check in MMC for 30% extra performance with IO
19) Block:
•Added SIO IOScheduler
•Added BFQ IOScheduler
•Added fiops scheduler
20) Disabled Gentle fair sleepers
21) NOATIME and NODIRATIME
22) Dynamic management of dirty page writebacks
23) Mali:
•GPU cache Optimizations
•Increase L2 cache max read size
•Disable state tracking
•Reduce GPU utilization timeout
•Increase kernel memory buffer size
24) Additional Governors:- SmartassV2
25) Additional I/O Schedulers:
•NOOP
•BFQ
•FIOPS (by default)
•SIO (SImple Ondemand)
Link:
https://mega.nz/#!C99z3JQR!7ECpzlgKzjWSY11ayCAbqLw-tIzRlHlv9PyZOxStu6I
KitKat:
KitKat kernel can used to any KitKat ROM such as AOSP, MIUI, CM 11. This kernel also used in Lollipop ROM such as CM 12.1 and CM 12.1 Based ROM. Also used in Marshmallow ROM such as CM 13.0 and CM 13.0 based ROM and AOSP 6.0.1 ROM. This not used in MTK based 5.1 Lollipop ROM
3.4.113 OverClocked KitKat kernel by @getakgt1:
Features:
1) Upstreamed to 3.4.113
2) OverClocked to 1.4GHZ
Link:
https://mega.nz/#!3pl2FJqR!zD4UnHbt16CVqsot3uqULTaANCWW4FK4ubmyKO5NwNM
Instructions:
1) Download any kernel zip
2) Place it in SDCard
3) Reboot to recovery
4) Flash Zip
5) Reboot to system
6) Done
Credits:
1) @kirito9
2) @chijure
3) @getakgt1
4) Team Dev Pop
5) GETAKGT1
6) Team Panther
7) @osm0sis
8) @Koush