Database Info

[KERNEL][CM10.1-UNOFFICIAL] Moretz v3.0.9 (Updated: 7.13.13)

Moretz - Kernel​
Version: 3.0.9
Linux-Version: 3.0.72
Base: CM10.1 (4/24 builds and later)​
This ROM fully supports IncrediControl by chad0989 for managing USB Fast Charge, Governors and Voltages.
{
"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"
}
Get IncrediControl from the play store here:
https://play.google.com/store/apps/details?id=com.incredicontrol&hl=en
TAKE 20 MINUTES TO READ THE THREAD BEFORE FLASHING THIS.
Do us, and yourself a favor and read before asking a question. Repeat questions will be ignored because they cause clutter.
Features:
- Ultra KSM 0.1.2.2
- Voltage Control (OV/UV)
- Tweaked min/max allowable voltages
- Tweaked CPU bus speed (added 400MHz)
- Clock Speeds: 192MHz - 1.78GHz
- 3D GPU Clocks Up to 320MHz
- 3D GPU Max Freq Control (Kernel Sysfs: /sys/kernel/gpu_control) - Included init.d script to manage
- 2D GPU Clocks Up to 266Mhz
- 2D & 3D Bandwidth Increase
- KGSL (GPU) Tweaks
- Added Scheduler: BFQ v6, SIO, V(R)
- Added Governors: Ondemand 2 Phase (modded), SmartassV2 (modded), Badass 3 Phase, Lionheart (tweaked)
- USB Fast Charge
- MSM MPDecision (Enables hotpluging across all governors) - modded for dual core CPU
- Smart Zipalign at Boot
- SQLite Optimize Databases at Boot
- Sync CPU governors (thanks elbermu)
- Sync CPU frequency policies (thanks elbermu)
- sweep2wake
- BLN support
- Other small tweaks / fixes / enhancements
Supported ROMs:
CyanogenMod 10.1
Supported Devices:
AT&T Samsung Galaxy Skyrocket
Thanks:
Team Chopsticks
Project Mayhem
Team ROOK
Cyanogen
InstagatorX
roger_n
The Muppets
ktoonsez
elbermu
toyes
mindmajick
franciscofranco
Your Mom
mtdew
Cl3Kener
This build wouldn't be possible if it wasn't for the hard work of Team Chopstics and Cyanogen who got JB4.2 (CM10.1) up and running for the Skyrocket.
Discussion vs. Bug Reports​
Bug Reports:
Please post bug reports to this thread with logcats, kernel messages, etc. Specify which version your are running, the ROM you are using, your setings (voltage, governor, scheduler, etc) and exactly how you can reproduce the bug to this thread. Simple, unquantified or otherwise subjective statements without evidence or detailed description will be ignored.
Discussion:
There a discussion thread in the Q&A section (thanks mtdew) where you can post general questions, feedback and feature requests. That thread is here: http://forum.xda-developers.com/showthread.php?p=40321746
Click to expand...
Click to collapse
Donations - Please Read​
I have had people asking me about donations lately, so I figured I'd give you my take on it publicly. I do this for fun and for self education. While I greatly appreciate anyone who would consider donating to me, I would ask that you please donate to the real developers and service providers of our community at any of the links below:
Goo.im Donations: http://goo.im/home (Click the Donate button on their homepage)
CyanogenMod Donations: http://www.cyanogenmod.org/ (Click the Donate button on their homepage)
Thanks!
CvD
Click to expand...
Click to collapse

Code:
[center]
[B]Installation Instructions:[/B]
Download
Nandroid
Flash
Reboot
Enjoy!
[/center]
Download Moretz Releases Below ...
DevHost: http://d-h.st/users/carvsdriver/?fld_id=16909#files
*I recommend using TWRP for flashing my work.​
Click to expand...
Click to collapse
GPU Frequency Control:
You can manage the max frequency of the 3D GPU via sysfs.
The interface is located: /syst/kernel/gpu_control
There are two settings, currently only the gpu_3d_freq_phase works. I have not enabled 2D max frequency yet.
There are seven valid values for gpu_3d_freq_phase:
0 - 320Mhz
1 - 300Mhz
2 - 266Mhz
3 - 228Mhz
4 - 200Mhz
5 - 177Mhz
6 - 27Mhz
Setting a value outside of 0-6 will result in either a 0 or 6 being set. These values will reset to the default (0) at boot via the included init.d script 02gpu_control. You can change the max setting on the fly by editing the gpu_3d_freq_phase file directly, or just update the init.d script and reboot.
If in doubt, just leave it alone and your GPU will remain over clocked at 320MHz.
Click to expand...
Click to collapse
SWEEP2WAKE:
Sweep2Wake provides the ability for you to wake up your phone by sweeping your finger across the haptic buttons from left to right. You can disable this functionality via sysfs here: /sys/android_touch/sweep2wake (1 = on, 0 = off)
Click to expand...
Click to collapse
USB Fast Charge:
USB Fast Charge is a hotly debated topic. In short, it violates the USB 1.0 & 2.0 spec by drawing more than .500A from the two power wires in the USB interface. USB 3.0 supports up to .900A so it works just fine there.
This is a use at your own risk feature of the kernel. If you have a poorly made USB host controller, it could theoretically destroy it. Some USB host controllers are smart enough to either prevent the additional power draw, or simply prevent you from charging when you have it enabled.
If in doubt, don't use it.
Click to expand...
Click to collapse
MSM MPDecision:
MPDecision, put simply is a better, more powerful way to hotplug your CPU cores across all governors. Primarily, this will determine when to shut off CPU1 and when to bring it online based on work queue load and time in queue. This is fully configurable via sysfs as follows:
startdelay = time until mpdecision starts doing it's magic (20000)
delay = time between checks (70)
pause = if something else plugs in the cpu, fall asleep for 5000ms (5 secs)
scroff_single_core = if the screen is off, don't plug in cpu1 (1)
enabled = enable(1) or disable(0) mpdecision. This does not affect scroff_single_core!
idle_freq = a value against that will be checked if a core +/- is requested. (384000)
nwns_threshold_up (down) = runqueue threshold to up or down CPU1
twts_threshold_up (down) = how much time passes before taking the related up/down action
max_cpus = maximum number of cpu's - just leave this one alone. mpdecision was designed for 4 core chips, i modded it for two
Click to expand...
Click to collapse
Stock CPU Voltages (Reference):
Frequency ---- Voltage
192MHz ---- 800000
384MHz ---- 825000
432MHz ---- 850000
486MHz ---- 850000
540MHz ---- 875000
940MHz ---- 875000
648MHz ---- 900000
702MHz ---- 900000
756MHz ---- 925000
810MHz ---- 975000
864MHZ ---- 975000
918MHZ ---- 1000000
972MHz ---- 1025000
1.02GHz --- 1025000
1.08GHz ----1050000
1.13GHz --- 1075000
1.18GHz --- 1100000
1.24GHz --- 1125000
1.29GHz --- 1150000
1.35GHz --- 1150000
1.40GHz --- 1175000
1.45GHz --- 1200000
1.51GHz --- 1225000
1.56GHz --- 1225000
1.62GHz --- 1225000
1.67GHz --- 1250000
1.72GHz --- 1275000
1.78GHz --- 1300000​
Click to expand...
Click to collapse

Moretz v3.0.9 - 7.13.13 - Changelog:
cpufreq: ondemand: remove two-phase logic
msm: msm_fb: remove mmio access through mmap
msm8660-common: cifs: use offsetof macro
msm8660-common: clean up uninitialized variables
msm8660-common: i2c: fix Kconfig error for INPUT_YAS529_POSITION
drivers: misc: remove dos formatting from a2220.c
cpufreq: Avoid using smp_processor_id() in preemptible context
cpufreq: ondemand: Fix kernel warning in cpufreq_governor_dbs
msm: cpufreq: make the gov stop part fully atomic
cpufreq: Fix optimal_freq logic on ramp down
cpufreq: ondemand: Fix store_powersave_bias() race with hotplug
cpufreq: ondemand: Fix locking issue in store_powersave_bias
ondemand: Add support to consider other cpu load when scaling frequencies
Revert "cpufreq: notify avg load for short sampling_rate"
msm8660: add additional locking protection to touckey driver
msm8660: fix incorrect gpio_config in touchkey driver
cpufreq: enforce governor to stay in sync across CPU cores
msm8660-common: fix Kconfig error for USA model name choice
msm: audio: qdsp6v2: Add size safety check to ACDB driver
Moretz 3.0.8
gpu: add 228MHz & 266MHz 2D gpu frequencies
Moretz v3.0.7.1 - (6/11/13) - Changelog:
kgsl: gpu: revamped 3D scaling logic
touchkey: add BLN support
ld9040: various driver updates to fix locking and regulator on/off
Use lowmemorykiller.c from pre 04-24 kernel
Moretz v3.0.7 - (5/31/13) - Changelog:
board config: build with arm-eabi-4.4.3 toolchain
msm_fb: Fix the hang issues due to improper usage of vsync
ld9040: fix lcd brightness
kgsl: change how active power level is set
msm8660: disable CONFIG_GPIO_SX150X
Moretz v3.0.6 - 5/20/13 - Changelog:
defconfig: Disable INLINEs and enable debugging for mutex and spinlocks
Moretz v3.0.5 - 5/19/13 - Changelog:
mdp: Do not start LUT for overlay0
video: msm: Check for null in LCDC IRQ handler
lib/sha1.c: quiet sparse noise about symbol not declared
arm: remove "optimized" SHA1 routines
lib/sha1: use the git implementation of SHA-1
hardlockup: detect hard lockups without NMIs using secondary cpus
staging: android: lowmemorykiller: Change default debug_level to 1
staging: android: lowmemorykiller: Don't count reserved free memory
staging: android: lowmemorykiller: Add config option to support oom_adj values
tty: hold lock across tty buffer finding and buffer filling
msm: smp: Remove WFE/SEV from secondary core bootup
msm: cpufreq: Fix store_powersave_bias to account for sync' CPUs.
USB: f_mtp: Fix corner cases in MTP driver while syncing
arm: show present cpu instead of online cpu in /proc/cpuinfo
msm: cpufreq: Add API to allow limiting of min and max cpu frequencies
msm: thermal: Simplify kernel thermal safeguard mechanism
thermal: Don't limit CPU frequency after msm_thermal is disabled
msm: pm: save registers to noncached area before pc
msm: idle-v7 : Restore context for NR_CPUS >= 2 when PC fails
msm: idle-v7: Remove redundant cache clean
msm: idle-v7: Power collapse Krait with caches enabled
msm: idle-v7.S: Warmboot support for NR_CPUS >= 2
lib: genalloc: Change chunk allocation to vmalloc
Moretz 3.0.4 (unreleased)
video: msm: Remove buggy locking around FB operations
ARM: Fix deadlock scenario with smp_send_stop()
staging: zcache: support multiple clients, prep for KVM and RAMster
msm: pm-8x60: Don't restore ACPU frequency for hotplug cases.
msm: gpio-v2: Fix lockdep warning
msm: gpio-v2: Add support for irq_domains
irq: irqdomain: Change irq_domain_add to detect errors
irq: irqdomain: Add support for dynamic irq_desc allocations
ARM: gic: Remove unnecessary irq spinlocks from gic_resume path
ARM: gic: Disable all interrupts before Power collapse
ARM: gic: protect some of 8625 GIC functionality with irq spinlocks
ARM: gic: Move GIC based code out from mpm-8625
ARM: gic: Add spinlocks for SGIR/AIR/EOI for 8625
ARM: gic: Add support to access GIC in secure mode
arm: gic: Configure the GIC to run in secure mode
arm: gic: Check for error code on irq_domain_add
arm: gic: Register irqdomain after adding it
Perf: Dont reset PMU's if perf is not active
msm: gic: Remove manual GIC programming for PPI trigger type
msm: clock-8960/8660: Support 32/64MHz prng clock frequency plan
msm: gpio-v2: Clear the interrupt status before unmasking
msm: gpio-v2: Re-arrange the write to RAW_STATUS_EN
msm: gpio-v2: Fix spurious interrupts when gpio-irq is unmasked
msm: pm: clean msm_pm_pc_pgd in the cache after writing
msm: 8960: Set last sleep mode variable for WFI
Moretz v3.0.3 - 5.12.13 - Changelog:
msm: restart: Always send Samsung magic reset reason
video: msm: Remove dead code causing compilation failure on MIPI devices
video: msm: Call complete_all if vsync times out for LCDC
bdi: use deferable timer for sync_supers task
sched: Fix select_fallback_rq() vs cpu_active/cpu_online
panic: Fix a possible deadlock in panic()
sched/nohz: Fix logic in trigger_load_balance
sched/nohz: Fix logic in run_rebalance_domains
sched/nohz: Fix logic in nohz_kick_needed
sched/nohz: Correctly initialize 'next_balance' in 'nohz' idle balancer
msm_fb: Optimize the resolution change on hdmi interface
msm_fb: hdmi: Do not turn on HDMI if not ready
msm_fb: hdmi: update data on resolution change
qt602240_ts: add additional mutex protection
qt602240_ts: fix incorrect #if !defined(CONFIG_*_MODEL) usage
qt602240_ts: clear unused slots in the framework after calibration
msm: display: update non-double-buffered register
msm_fb: Check for panel power on after Unblank.
msm_fb: display: Assign proper destination rectangles to mdp blit
video: msm: Call unblank for DTV too
msm_fb: Use an exclusive semaphore for Vsync IOCTL
Moretz v3.0.2 - 5.9.13 - Changelog:
Set as-instr to use printf instead of echo
net/wireless: Backport stack from 3.4
video: msm: Remove dead code
bluetooth: Fix race conditions in BT LPM
lcdc_ld9040: add additional mutex protection
cpufreq: fix utilization statistics for sync cpus
cpufreq: notify avg load for short sampling_rate
cpufreq: Fix panic when setting sampling rate
msm: cpufreq: Fix the race between dbs_refresh and hotplug.
msm: Remove idle stats and cpuidle hooks
msm: cpuidle: Don't disable IRQ's before calling down into the cpuidle driver
msm: cpuidle: Update C state time stats in the cpu idle device.
msm: cpufreq: fix a race between hotplug and cpufreq
msm: rq_stats: remove io_is_busy from load computation
msm:rq_stats: Register for Cpufreq policy notification
cpufreq: Resolve CPUFREQ_NOTIFY issue
msm: rq_stats: Fix missing initalization of cur_freq
msm_fb: display: do not use ION_IOMMU_UNMAP_DELAYED
msm_fb: display: init pipe default configure as solidfill
msm_fb: display: free previous iommu buffer only at overlay_unset
msm_fb: display: add one more pipe_commit delay before free ion buffer
Revert: msm_fb: display: free base layer pipe at adb stop
msm_fb: display: Do a pre-fill to writeback buffers.
msm_fb: display: remove extra dmap irq disable
msm_fb: display: Wait for DMAE for external interface (DTV)
msm_fb: display: calculate mdp clock including borderfill pipe
Asynchronous I/O latency to a solid-state disk greatly increased
lib/string: use glibc version
sweep2wake: re-introduce sweep2wake support for the capacitive buttons

Thanks for all your hard work!

theshow4life said:
Thanks for all your hard work!
Click to expand...
Click to collapse
You bet, working on a fix for the OC frequencies - I think I just missed a few lines of code somewhere. I'm shooting to get that out sometime tomorrow, taking a break for the evening to chill out.
For now, please report in any other bugs. If possible, include logcats and kmsg files. Thanks!

Re: [KERNEL][JB 4.2-CM10.1] Moretz Kernel - OC - UV (Updated: 2.9.13) [TEAM ROOK]
Gonna give it a try right now .
Sent from my SAMSUNG-SGH-I727 using xda premium

Re: [KERNEL][JB 4.2-CM10.1] Moretz Kernel - OC - UV (Updated: 2.9.13) [TEAM ROOK]
Your previous kernel was top of the line. I expect this to be as well. Can't wait to see what you do with 10.1
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Re: [KERNEL][JB 4.2-CM10.1] Moretz Kernel - OC - UV (Updated: 2.9.13) [TEAM ROOK]
CvsD the kernel king!
Sent from my SAMSUNG-SGH-I727 using xda premium

Re: [KERNEL][JB 4.2-CM10.1] Moretz Kernel - OC - UV (Updated: 2.9.13) [TEAM ROOK]
Ok it says wont overclock but what if I underclock? I usually have it set to 1026.
Thanks
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

greekunit690 said:
Ok it says wont overclock but what if I underclock? I usually have it set to 1026.
Thanks
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Should be fine. That's what I have setup now.
Also, doesn't seem to be deep sleeping either. Might be related to the OC frequency issue.

car vs driver said:
Should be fine. That's what I have setup now.
Also, doesn't seem to be deep sleeping either. Might be related to the OC frequency issue.
Click to expand...
Click to collapse
System tuner says the clocks at 1.78 but stability test pegs at 1.56. Running smooth though. No issues with deep sleep here. How much did you drop stock voltages? The look pretty low already. Or it could just be my really bad memory. lol

Re: [KERNEL][JB 4.2-CM10.1] Moretz Kernel - OC - UV (Updated: 2.9.13) [TEAM ROOK]
Exactly what I have been waiting for. Thank you. I'll let you know how it performs tomorrow.
Sent from my SGH-T989 using Tapatalk 2

Thanks for this! Much smoother then stock. So far, no jitters during game play. Will test a bit and get back.
Oh ya, what happened to init.d folder?
Does this cmd delete the whole folder?
Code:
ui_print(" Clearing init.d..");
delete_recursive("/system/etc/init.d");

Re: [KERNEL][JB 4.2-CM10.1] Moretz Kernel - OC - UV (Updated: 2.9.13) [TEAM ROOK]
Working awesome for an alpha, no issues and smooth game play on order and chaos, was using pegasusq out of habit, switched to the tweaked ondemand and checking the battery drain today
Is the row scheduler not compatible with the skyrocket? Haven't ever seen it on the device anywhere and it seems to have great performance on my other devices, just food for thought I guess

Re: [KERNEL][JB 4.2-CM10.1] Moretz Kernel - OC - UV (Updated: 2.9.13) [TEAM ROOK]
stoopendis said:
CvsD the kernel king!
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Well, I certainly appreciate your enthusiasm sir. But I'm just a hack, I wouldn't consider myself to be a really good dev yet. I just happen to get some things right once in a while.
hechoen said:
System tuner says the clocks at 1.78 but stability test pegs at 1.56. Running smooth though. No issues with deep sleep here. How much did you drop stock voltages? The look pretty low already. Or it could just be my really bad memory. lol
Click to expand...
Click to collapse
Voltages are stock across the board, use IncrediControl if you want to UV.
wantowan2 said:
Thanks for this! Much smoother then stock. So far, no jitters during game play. Will test a bit and get back.
Oh ya, what happened to init.d folder?
Does this cmd delete the whole folder?
Code:
ui_print(" Clearing init.d..");
delete_recursive("/system/etc/init.d");
Click to expand...
Click to collapse
It will remove the contents of that folder, yes. I do that for this version because I don't want false alarms or conflicts with crap placebo init.d scripts. I'll put a couple back in later if I determine they are actually helpful / compatible with 4.2
XsceneXhippieX said:
Is the row scheduler not compatible with the skyrocket? Haven't ever seen it on the device anywhere and it seems to have great performance on my other devices, just food for thought I guess
Click to expand...
Click to collapse
Beast me, I'm not looking at adding stuff right now. Trying to work out OC frequencies and the lack of deep sleep first. Seems like everything else is working pretty well though.
I should get some time this evening to work on the frequency issue. I slapped in a bunch of changes along with that, so I'm going to back it out in the code and go back through it.
On the list ...
1. Fix OC
2. Fix deep sleep
3. Add GPU OC
4. Add some schedulers
5. Add in fast charge
6. Add in some other neato things
Based on that list, I wouldn't expect this to come out of Alpha for a good week. Just depends on how much time I can dedicate to it. In the meantime, keep reporting in any bugs that haven't been reported already.
Oh, and thanks for the positive feedback otherwise. I wouldn't daily drive this quite yet until the deep sleep is at least fixed, but I appreciate participation in the open testing so far
Edit:
Row is compatible, reading through the kernel commits - Cyanogen added it yesterday to the main repo. I'm working through the latest commits and applying them to my base. Unfortunately, git wouldn't let me fork the repo to do it the easy way ... so i have to get the updates through cherry picking.

Re: [KERNEL][JB 4.2-CM10.1] Moretz Kernel - OC - UV (Updated: 2.9.13) [TEAM ROOK]
Is there a deep sleep issue? Mine sleeps like a baby.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Mines sleeping as well. AOKP 4.2 smartassV2, noop, UV'd by 100 across the board. Bluetooth and GPS both work. It's running pretty damn well for an Alpha. Nice work man.

Re: [KERNEL][JB 4.2-CM10.1] Moretz Kernel - OC - UV (Updated: 2.9.13) [TEAM ROOK]
We can flash this with a rotation fix Herc side right?

Re: [KERNEL][JB 4.2-CM10.1] Moretz Kernel - OC - UV (Updated: 2.9.13) [TEAM ROOK]
krazeecracker said:
We can flash this with a rotation fix Herc side right?
Click to expand...
Click to collapse
You could try but I doubt you'll be able to get your phone to get passed boot ani. I think the rotation fix needs to upgraded for 4.2
Sent from my SAMSUNG-SGH-I727 using xda premium

krazeecracker said:
We can flash this with a rotation fix Herc side right?
Click to expand...
Click to collapse
AndroidGee209 said:
You could try but I doubt you'll be able to get your phone to get passed boot ani. I think the rotation fix needs to upgraded for 4.2
Click to expand...
Click to collapse
The old rotation fix doesn't work. I used it as a baseline then copied the same files from the i727CM10.1 over to the t989AOKP4.2. Then put the CM10.1 kernel in the zip. That hosed wifi but fixed rotation. Then I just switched out the wifi libs. Now everything works great.

[KERNEL][3.4.70][JB][PMEM] K^Kernel 3.4.70 v2.6 for JB 4.2.2 & 4.3 [25/11/2013][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.4.x for JB 4.2.2 and JB 4.3 rom (CM 10.1, CM 10.2 and derivatives) that use PMEM memory allocations.
Of course, your feedback, as always, are welcome and certainly valuable.
The main features are the following:
- Kernel 3.4.x
- Sources synched with cm-10.1 and cm-10.2 repo branches of Arco68 and DevCon Team
- 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
- Disabled Gentle Fair Sleepers for better UI performance
- Filesystem dynamic read-ahead (based on disk size)
- CIFS support on boot
- Memory compaction
- Dynamic compression of clean pagecache pages
- 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
- Updated sensor drivers
- 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
- Fiops
- Noop
- ROW
- SIO (default)
- V(R)
Kernel Downloads for JB 4.2.2:
K^Kernel JB-4.2.2 Mediafire Folder
[QRCODE]http://www.mediafire.com/folder/wcqdvd7pnyl3y/JB-4.2.2[/QRCODE]
- v2.6 -
for ADC CM 10.1 Release 9
and the other roms based on this latest CM 10.1
- v2.5 -
for ADC CM 10.1 Release 8
and the other roms based on this latest CM 10.1
- v2.3 -
for ADC CM 10.1 Release 7
and the other roms based on this CM 10.1​
Kernel Downloads for JB 4.3:
K^Kernel JB-4.3 Mediafire Folder
[QRCODE]http://www.mediafire.com/folder/0qp1ma43v8l3p/JB-4.3[/QRCODE]
- v2.6 -
for ADC CM 10.2 Release 1
and the other roms based on this latest CM 10.2
- v2.5 -
for ADC CM 10.2 Alpha 3
and the other roms based on this latest CM 10.2
- v2.3 -
for ADC CM 10.2 Alpha 2
and the other roms based on this CM 10.2​
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) Reboot the system
Kernel sources (on GitHub):
Development branch of K^Kernel 3.4 for JB 4.2.2
Development branch of K^Kernel 3.4 for JB 4.3
​
Useful info:
- Special features and sysfs settings
- Frequently asked questions
​
Rom and kernel 3.4.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
Tables:
​
Changelog:
Code:
[B]24/11/2013 - K^Kernel 3.4 v2.6 for JB 4.2.2 and JB 4.3[/B]
- Kernel 3.4.70
- Sources synched with cm-10.1 and cm-10.2 repo branches of Arco68 and DevCon Team
- Built with my latest custom Linaro 4.8.3-2013.11 toolchain optimized for Cortex-A8
- Clone ion.h to msm_ion.h (credits to Arco68)
- msm: kgsl: Avoid turning on GPU clock if already off (credits to Ananta Kishore K)
- Makefile: Use -fno-inline-functions to build with Linaro GCC 4.8 toolchains (credits to Christopher83)
- Revert "ALSA: fix oops in snd_pcm_info() caused by ASoC DPCM" (credits to Christopher83)
- 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)
- msm: vidc: Check validity of userspace address (credits to Deepak Verma)
- ALSA: pcm: check for integer overflow during multiplication (credits to Phani Kumar Uppalapati)
- base: genlock: Zero a structure before sending it to user space (credits to Jordan Crouse)
- 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)
- qt602240_ts: updated touchscreen driver in according of Multi-touch protocol (credits to CastagnaIT)
Additional commits for CM 10.2 only:
- SELinux: include definition of new capabilities (credits to Eric Paris)
- msm: vidc: Reset stop_called state when START is called (credits to Deepak Verma)
- msm: vidc: set EOS on output buffer pending transaction (credits to Deepak Verma)
[B]27/10/2013 - K^Kernel 3.4 v2.5 for JB 4.2.2 and JB 4.3[/B]
- Kernel 3.4.67
- Sources synched with cm-10.1 and cm-10.2 repo branches of Arco68 and DevCon Team
- Built with my latest custom Linaro 4.7.4-2013.10 toolchain optimized for Cortex-A8
- gp2a_proximity: readded wakelock is necessary to avoid problems with answer calls and some cleanups (credits and thanks to CastagnaIT)
[B]15/10/2013 - K^Kernel 3.4 v2.4 for JB 4.2.2 and JB 4.3[/B]
- Kernel 3.4.66
- Sources synched with cm-10.1 and cm-10.2 repo branches of Arco68 and DevCon Team
- Built with my latest custom Linaro 4.7.4-2013.09 toolchain optimized for Cortex-A8
- msm: display: Prevent fb suspend in charging mode for ancora only
- decompressor: Add LZ4 decompressor module (credits to Kyungsik Lee)
- lib: Add support for LZ4-compressed kernel (credits to Kyungsik Lee)
- arm: Add support for LZ4-compressed kernel (credits to Kyungsik Lee)
- lib: Add lz4 compressor module (credits to Chanho Min)
- crypto: Add lz4 Cryptographic API (credits to Chanho Min)
- lib/lz4/lz4_compress: fix macro usage error (credits to Faux123)
- LZ4: compression/decompression signedness mismatch (v2) (credits to Sergey Senozhatsky)
- binder: use freezable blocking calls (credits to Colin Cross)
- epoll: use freezable blocking call (credits to Colin Cross)
- select: use freezable blocking call (credits to Colin Cross)
- af_unix: use freezable blocking calls in read (credits to Colin Cross)
- usb: gadget: mass_storage: added sysfs entry for cdrom to LUNs (credits to FrozenCow)
- Resolved problems of magnetic, proximity and orientation sensor (credits to CastagnaIT)
[url="http://forum.xda-developers.com/showpost.php?p=42865239&postcount=2"](PLEASE REFER TO ADC CM 10.1 POST#2 for CALIBRATION PROCEDURE)[/url]
- Updated default and custom configs for new sensor drivers and LZ4 support
[B]09/10/2013 - K^Kernel 3.4 v2.3 for JB 4.2.2 and JB 4.3[/B]
- Kernel 3.4.65
- Sources synched with cm-10.1 and cm-10.2 repo branches of Arco68 and DevCon Team
- Built with my latest custom Linaro 4.7.4-2013.09 toolchain optimized for Cortex-A8
- New bootsplash logo
- Revert "block: Add URGENT request notification support to CFQ scheduler" (credits to Tatyana Brokhman)
- 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)
- fs/sync: Make sync() satisfy many requests with one invocation (credits to Paul E. McKenney)
- ARM: add SCHED_HRTICK config option (credits to Russell King)
- HACK: ARM: disable sleeping while atomic warning in do_signal (credits to Colin Cross)
- alarmtimer: Use hrtimer per-alarm instead of per-base (credits to John Stultz)
- freezer: define try_to_freeze_nowarn if CONFIG_FREEZER=n (credits to Ben Jones)
- lockdep: remove task argument from debug_check_no_locks_held (credits to Colin Cross)
- freezer: shorten freezer sleep time using exponential backoff (credits to Arve Hjønnevåg)
- freezer: skip waking up tasks with PF_FREEZER_SKIP set (credits to Colin Cross)
- futex: use freezable blocking call (credits to Colin Cross)
- nanosleep: use freezable blocking call (credits to Colin Cross)
- sigtimedwait: use freezable blocking call (credits to Colin Cross)
- freezer: add unsafe versions of freezable helpers for NFS (credits to Colin Cross)
- freezer: add unsafe versions of freezable helpers for CIFS (credits to Colin Cross)
- lockdep: check that no locks held at freeze time (credits to Mandeep Singh Baines)
- freezer: convert freezable helpers to freezer_do_not_count() (credits to Colin Cross)
- freezer: convert freezable helpers to static inline where possible (credits to Colin Cross)
- freezer: add new freezable helpers using freezer_do_not_count() (credits to Colin Cross)
- msm: display: Prevent fb suspend in charging mode for all (credits to Arco68)
Additional commits for CM 10.2 only:
- msm: display: plane alpha support (credits to Ken Zhang)
- Add PR_{GET,SET}_NO_NEW_PRIVS to prevent execve from granting privs (credits to Andy Lutomirski)
- Fix execve behavior apparmor for PR_{GET,SET}_NO_NEW_PRIVS (credits to John Johansen)
- netfilter: xt_qtaguid: remove AID_* dependency for access control (credits to JP Abgrall)
- netfilter: qtaguid: rate limit some of the printks (credits to JP Abgrall)
- ancora: Update defconfig for selinux (credits to Arco68)
- ariesve: Update default and custom configs for selinux
- Makefile: Use -fno-inline-functions for Linaro toolchain
Thanks again to Arco68 for his work!
[B]15/09/2013 - K^Kernel 3.4 v2.2 for JB 4.2.2 and JB 4.3[/B]
- Kernel 3.4.62
- Sources synched with cm-10.1 and cm-10.2 repo branches of Arco68 and DevCon Team
- Built with my latest custom Linaro 4.7.4-2013.09 toolchain optimized for Cortex-A8
- msm_fb: Correct R and G offsets for correct mapping (credits to Jeevan Shriram, thanks to Arco68)
- Fix disconnect not sent from host when pairing is cancelled (credits to Subramanian Srinivasan, thanks to Arco68)
- USB: gadget: Cleanup boot-up message with default usb composition (credits to Mayank Rana, thanks to Arco68)
- Bluetooth : hidp: Get the valid hci_conn while unlink (credits to Sumit Bajpai, thanks to Arco68)
- Bluetooth: Disable Sniff on HID ACL(s) if SCO is active (credits to Hemant Gupta, thanks to Arco68)
- msm: kgsl: Do not try to resume the device from INIT state (credits to Lucille Sylvester, thanks to Arco68)
- cpufreq: interactive: fix show_target_loads and show_above_hispeed_delay (credits to Minsung Kim, thanks to Arco68)
- 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
[B]07/09/2013 - K^Kernel 3.4 v2.1 for JB 4.2.2 and JB 4.3[/B]
- Kernel 3.4.60
- Sources synched with cm-10.1 and cm-10.2 repo branches of Arco68 and DevCon Team
- Built with my latest custom Linaro 4.7.4-2013.08 toolchain optimized for Cortex-A8
- ariesve_sensors: updated all sensors to match with the new opensource libsensors (credits to CastagnaIT)
- board_ariesve: cleanup mdp_pdata and added missing mem_hid (credits to CastagnaIT)
- msm: scm: Add scm_call_noalloc and helper macros (credits to Laura Abbott)
- msm: implement ARCH_RANDOM (credits to Laura Abbott), not yet completed
- init: Move stack canary initialization after setup_arch (credits to Laura Abbott)
- input: Propagate hardware event timestamp to evdev (credits to Sasha Levitskiy)
- memcg: add memory.pressure_level events (credits to Anton Vorontsov)
- mm: add a field to store names for private anonymous memory (credits to Colin Cross)
- 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)
- Enabled COMPACTION to allow memory compaction
- Enabled QCACHE to allow dynamic compression of clean pagecache pages
[B]21/08/2013 - K^Kernel 3.4 v2.0 for JB 4.2.2[/B]
- Kernel 3.4.58
- Sources synched with cm-10.1 repos of Arco68 and DevCon Team
- 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)
- Better support for VPN over IPsec
- CIFS support on boot
[B]05/08/2013 - K^Kernel 3.4 v1.9 for JB 4.2.2[/B]
- Kernel 3.4.56
- Sources synched with cm-10.1 repos of Arco68 and DevCon Team
- 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)
- block: row: Remove warning massage from add_request (credits to Tatyana Brokhman)
[B]25/07/2013 - K^Kernel 3.4 v1.8 for JB 4.2.2[/B]
- Kernel 3.4.54
- Sources synched with cm-10.1 repos of Arco68 and DevCon Team
- 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)
- block: urgent: Fix dispatching of URGENT mechanism (credits to Tatyana Brokhman)
- block: Remove "requeuing urgent req" error messages (credits to Tatyana Brokhman)
- block: row: change hrtimer_cancel to hrtimer_try_to_cancel (credits to Tatyana Brokhman)
- block: Add URGENT request notification support to CFQ scheduler (credits to Tatyana Brokhman)
- 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 3.4 v1.7 for JB 4.2.2[/B]
- Kernel 3.4.53
- Sources synched with cm-10.1 repos of Arco68 and DevCon Team
- Built with my latest custom Linaro 4.7.4-2013.07 toolchain optimized for Cortex-A8
- Fix a race between hotplug and cpufreq (credits to Narayanan Gopalakrishnan, thanks to Arco68)
- 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]06/07/2013 - K^Kernel 3.4 v1.6 for JB 4.2.2[/B]
- Kernel 3.4.52
- Sources synched with cm-10.1 repos of Arco68 and DevCon Team
- Built with my latest custom Linaro 4.7.4-2013.06 toolchain optimized for Cortex-A8
- Update camera code to use clk_prepare api (credits and thanks to Arco68)
- Fixes to graphic drivers (credits to Lynus Vaz and Lucille Sylvester)
- Implement suspend/resume for cpufreq driver (credits to Anji Jonnala)
- Check for pending_resume in SDCC system suspend (credits to Subhash Jadavani)
- Other minor fixes (from CAF sources)
- 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]29/06/2013 - K^Kernel 3.4 v1.5 for JB 4.2.2[/B]
- Kernel 3.4.51
- Sources synched with cm-10.1 repos of Arco68 and DevCon Team
- 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 display and graphic drivers (credits to Suman Tatiraju and Mayank Chopra, thanks to Arco68)
- Fixes to I/O block and ROW I/O scheduler (credits to Lee Susman and Tatyana Brokhman, 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]22/06/2013 - K^Kernel 3.4 v1.4 for JB 4.2.2[/B]
- Kernel 3.4.50
- Sources synched with cm-10.1 repos of Arco68 and DevCon Team
- Built with my latest custom Linaro 4.7.4-2013.06 toolchain optimized for Cortex-A8
- Temporary workaround for flicker brightness after screen on (credits and thanks to Krislibaeer)
- Corrected an unmanaged gamma for autobrightness
- Restored CM sysfs interface path for timeout of touchkeys backlight to be compatible with external apps (for example NsTools)
- Customizable activation status of touchkeys backlight on touchscreen press
- Fix for discharging battery issue while charging to 100% (credits and thanks to Skywalker01)
- Fix to dynamic fsync to don't disable fdatasync (credits and thanks to Faux123)
- Enabled CleanCache
[B]17/06/2013 - K^Kernel 3.4 v1.3 for JB 4.2.2[/B]
- Kernel 3.4.49
- Sources synched with cm-10.1 repos of Arco68 and DevCon Team
- Built with my latest custom Linaro 4.7.4-2013.06 toolchain optimized for Cortex-A8
- Battery drain fix for WIFI "Disabled SUPPORT_PM2_ONLY and DISABLE_FW_ROAM_SUSPEND" (credits and thanks to Arco68)
- Fixed data CRC errors for WIFI (credits and thanks to CastagnaIT)
- Updates and fixes to Interactive CPU governor (credits to Todd Poynor and Minsung Kim, thanks to Arco68)
- Squashed update of BFQ-V6 to BFQ-v6r1 (thanks to Arco68)
- Support for customizable timeout of touchkeys backlight after a key press
[B]13/06/2013 - K^Kernel 3.4 v1.2 for JB 4.2.2[/B]
- Re-added "Squashed update of kernel from 3.4.47 to 3.4.48"
- Re-added "ashmem: avoid deadlock between read and mmap calls"
- Fixed the problems with 3.4.48 kernel by reverting "mm/pagewalk.c: walk_page_range should avoid VM_PFNMAP areas"
[B]09/06/2013 - K^Kernel 3.4 v1.1 for JB 4.2.2[/B]
- Revert "Squashed update of kernel from 3.4.47 to 3.4.48"
- Revert "ashmem: avoid deadlock between read and mmap calls"
[B]08/06/2013 - K^Kernel 3.4 v1.0 for JB 4.2.2[/B]
- Kernel 3.4.48
- Sources synched with cm-10.1 repos of Arco68 and DevCon Team
- Built with my latest custom Linaro 4.7.4-2013.05 toolchain optimized for Cortex-A8
- Compilation flags optimized for ARM Cortex-A8 cpu and Neon vfp
- Overclocking and undervolting support
- Increased cpu frequency on boot
- High memory configurations (360MB, 370MB and 390MB of free RAM)
- Increased audio volume on board side
- Lowered WIFI voltage
- Lowered display panel voltage
- Lowered Atmel QT602240 touchscreen voltage
- Lowered Vibetonz voltage
- Added Fiops, SIO, V(R) I/O schedulers (credits and thanks to Shaoua Li, Miguel Boton and Aaron Carroll)
- Added InteractiveX, OnDemandX, Lionheart, SmartAssV2, Lulzactive, Adaptive, Hyper,
BrazilianWax and Intellidemand CPU governors (credits and thanks to Imoseyon, ErasmuX, Tegrak, Faux123)
- Fast Random generator support (frandom)
- CPU Voltage Control (VDD sysfs interface)
- Asynchronous I/O latency to a solid-state disk greatly increased (credits and thanks to Dave Kleikamp)
- Lowered swappiness 60->45
- Optimized SLUB memory allocator
- Filesystem dynamic read-ahead (credits and thanks to Chad Gooldman)
- Battery Life eXtender (BLX) version 1 (credits and thanks to Ezeekel, adapted by me for I9001)
- 100% battery notification after charger unplug
- Optimized ARM RWSEM algorithm and other RWSEM updates and optimizations from 3.10 kernel
- Disabled Gentle Fair Sleepers for better UI performance
- Optimized string and memcopy libs (credits and thanks to Miao Xie)
- Dynamic Fsync (credits and thanks to Faux123)
- Dynamic dirty page writebacks
- Phantom key presses filter module
- VM tweaks for performance and less battery consumption
- Revised LowMemoryKiller parameters for better performance
Credits and Thanks to:
Arco68, CastagnaIT and Ivendor for their awesome work and their kernel sources
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
KTulu84, TwinHeadedEagle, Smeroni68, XeLLaR* and Dellup for their support in testing
Sament83, B1tt1, Dellup, Pierm, Leonbeson, Cippoz89 and Marco Z. for their donations
XDA:DevDB Information
[GT-I9001][PMEM] K^Kernel 3.4 for JB 4.2.2 and JB 4.3, Kernel for the Samsung Galaxy S I9000
Contributors
Christopher83
Source Code: https://github.com/Christopher83/samsung-kernel-msm7x30
Kernel Special Features: Customized kernel 3.4.x for JB 4.2.2 and JB 4.3 rom (CM 10.1, CM 10.2 and derivatives)
Version Information
Status: Stable
Current Stable Version: v2.6
Stable Release Date: 2013-11-25
Created 2013-09-13
Last Updated 2015-06-08

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 v1.3 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 using the related setting inside System -> Advanced -> Backlight Timeout
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 v1.4 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 the related setting inside System -> Advanced -> Backlight on Touchscreen Press
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 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
3) By directly editing the file /sys/class/misc/notification/touchlight_enabled (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 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...
How to disable / re-enable the redirection to frandom module during boot process:
By using Terminal Emulator:
- Run these commands to create the flag file and disable Frandom redirection:
Code:
su
touch /data/frandom_disabled
- Or run these commands to delete the flag file and re-enable Frandom redirection:
Code:
su
rm /data/frandom_disabled
The change will take effect after a reboot.
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.
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
Q: How can I mount a shared Windows folder with CIFS module?
1) By using Terminal Emulator
Code:
mount -o unc=\\\\[COLOR="DarkGreen"][I]ip[/I][/COLOR]\\[COLOR="Blue"][I]share[/I][/COLOR],noserverino,username=[I][COLOR="DarkOrange"]user[/COLOR][/I],password=[I][COLOR="Lime"]password[/COLOR][/I] -t cifs //[COLOR="DarkGreen"]ip[/COLOR]/[COLOR="Blue"]share[/COLOR] [I][COLOR="DarkSlateGray"]/mnt/cifs[/COLOR][/I]
2) Downloading and using CifsManager and configuring the new share as follow:
- Share Path = ip/share
- Mount Point = /mnt/cifs/share
- Username = username
- Password = password
- Options = unc=\\\\ip\\share,noserverino
Where:
ip is the ip address of your pc where the folder is shared
share is the shared folder name
user is the user name that can access the shared folder
password is the user password
/mnt/cifs is the mount point (must be created if you'd like to use the command approach with Terminal Emulator)

First & thanks Christopher83
EDIT : Smooth & awesome as always~

Downloading right now.
Thank you! :good:

Thank you !!!
Sent from my GT-I9001 using xda app-developers app

H2othebest said:
Downloading right now.
Thank you! :good:
Click to expand...
Click to collapse
Yeah ! Best kernel ! Smooth
Sent from my iPad using Tapatalk 2

thanks!!! release 1 + 3.4.48 perfect!!

amazing kernel as usual, chris you're the best

Awesome! I like your kernels and this is very smooth .

Your kernels are my favorite

Thank you for your time and effort. I really like your detail description.
Sent from my GT-I9001 using Tapatalk 4 Beta

I have crash and soft reboot with 3.4.48.. I have problem also with other 3.4.48 kernel.. Not only yours kernel
Inviato dal mio GT-I9001

Giorgio555 said:
I have crash and soft reboot with 3.4.48.. I have problem also with other 3.4.48 kernel.. Not only yours kernel
Inviato dal mio GT-I9001
Click to expand...
Click to collapse
did you wiped dvalik and fix permissions after start and getting back into recovery ?
Also on some devices the exUV versions doesn't work. You could try UV versions.
---------- Post added at 06:05 AM ---------- Previous post was at 06:02 AM ----------
Great Kernel !!!!
Had only 2% battery drain over night, which is in general the same I had before with the 3.0.80 kernel base.
Drain during daily usage will be checked today ...
But very smooth and works perfect with the new CM10.1 RC5 relesae 1.
Thank you !
:highfive:

me too... two soft reboot...
Enviado desde mi GT-I9001 usando Tapatalk 2

With this kernel debugging not working???

Screen brightness goes instantly to 100% (?)
Hi Christopher,
Nice work from you, the rest of devs and testers. I installed your Kernel (360MB, EXUV) and I will try to report my tests if any. I am following some threads in SGS+ development and I am not sure (I am busy this period) If I saw a post about the annoying instant flash light (higher brightness) when the phone is coming back from sleep using he power button. Then, the brightness gets back to its settings again. Not a big deal…
So far is working great. I will try to use the GPS to check if the deep sleep works after turning it off.
Thanks for your dedicated work on SGS+.

I have flashed all your kernels(for ICS,JB 4.1,4.2).Everything was smooth. But with this kernel I got 2 soft reboots while streaming video on MX player and one hard reboot while installing a game.

Me too. Freez and reboot especially using browsers (stock and Firefox).
None in 47 now.
Sent from my GT-I9001 using xda app-developers app

[KERNEL][3.4.107][AOSP/CM][GCC-5.0]Spirit.Kernel r1

Spirit Kernel
This kernel is ONLY for AOSP based ROMs. This will NOT work on the stock Moto roms.
I will update this regularly as I have time and will add new features and fixes as well.
If you have any feature requests or ideas that haven't been seen before, don't hesitate to post it here!!​
PLEASE READ
How to report a bug?
Include the following in your bug report:
The ROM you are currently using + a link to the ROM's thread
A log, preferably dmesgs or kmsgs (use Google to find out how to pull these from your device)
The version of SpiritKernel you use (=rx, e.g.r3)
Bug reports not meeting these requirements will be ignored.
NO BUG REPORTS ON EXPERIMENTAL BUILDS!​
Features
This Hybrid kernel contains features from great kernel devs with like faux,franco and neobuddy,optimized for thea to make it work.Initially there are less features but I will add much more soon
[*]Based on the Latest CyanogenMod sources
[*]Patched 3.4.106 kernel
[*]Governors: ondemand/userspace/powersave/performance/interactive/IntelliMM/inteliidemand/intelliactive/smartmax/pegasusQ
[*]Hotplug: MPDecision/MSM Hotplug/Intelliplug(default)
[*]Intellithermal v2
[*]DT2W/S2W/S2S Wake controls
[*]CPU Underclocking 192Mhz
[*]GPU OC 533Mhz | UC 100Mhz
[*]Add MSM Hotplug Driver
[*]Asynchronous Fsync extracted from HTC
[*]Sweep2Sleep driver
[*]Dynamic management of timer slack
[*]Slimbus OC thanks to neeobuddy89 and poondog
[*]increase Torch power 20mA
[*]Dynamic management of dirty page writebacks
[*]IO: BFQv7r7/FIFO/SIO/FIOPS/ZEN/VR IO Schedulers
[*]Faux Sound Control 3.2
[*]KCAL v2 by @savoca
[*]USB forced fast charge
[*]Stereo call recording support by skvalex
[*]Powersuspend from Faux and yank555-lu *updated to 1.8 after r8*
[*]Kernel Compression: XZ
[*]psx2usb controller
[*]Use Android device as USB keyboard/mouse
[*]optimized ARM RWSEM algorithm.
[*]Ultra Kernel Samepage Merging {UKSM}
[*]FRandom
[*]Dynamic FSync Control
[*]Added Simple GPU Algorithm
[*]WQ_POWER_EFFICIENT for bettery battery life. Hello Battery!!
[*]ANY Kernel
[*]Kexec hardboot patch for Multirom support
[*]TCP: HTCP/HSTCP/HYBLA/VEGAS/SCALABLE/LP/VENO/YEAH/ILLINOIS/WESTWOOD
Optimizations
[*]Compiled Using UBER 5.0.1 SaberMod 4.8 Optimized toolchain for better performance | UBER 4.9 Toolchain after r4
[*]Added optimized ARM RWSEM algorithm.
[*]Disable add_random
[*]Pocketmode and deepsleep for dt2w/s2w
[*]Optimized VFP Module
[*]FIx integer-overflow in veno,vegas
[*]Add sysinterface for GENTLE_FAIR_SLEEPERS
[*]NOATIME and NODIRATIME as default
[*]New 99LMK script by @pizza_Dox
[*]Nvidia Patches to enhance power efficiency.
[*]Sched optimizations
[*]Increase battery level check interval
[*]writeback: increase bdi_min_ratio to 5
[*]block: cfq: merge tweaked tunables.
[*]Wait just 1 second for other CPU to halt
[*]net: combat buffer bloat
[*]PM: Introduce suspend state PM_SUSPEND_FREEZE
[*]Disable -fconserve-stack on ARM v2
[*]Enable power efficient workqueues by default
[*]do not use msm_run_queue_stats
[*]enable/disable cpu-boost via sysfs
[*]softirq: reduce latencies
[*]Built with Ofast flags
[*]Force SELinux permissive
[*]LowMemoryKiller management of non killable processes
[*]Headset High Performance Mode
[*]Allow CPU-supported unaligned accesses
[*]Enable UNALIGNED_ACCESS
[*]enable ARCH_POWER
[*]lower swappiness
[*]vfp: remove double entries
[*]Disable disable crc check for 30% extra performance in IO
[*]Optimized SLUB memory allocator
[*]Optimize Sfck Compression
[*]set sched_mc_power_savings to 2 (moar powarrrrrrr! saving)
[*]readahead to 256
[*]Built with Graphite flags
[*] Enabled Pipe Flag
TO-Do List
IntelliMM-intelliminmax
New Govs and I/Os
Intelliplug 4.0
GPU OC and UC
* Recommended app for tweaking the kernel: FauxControl,Kernel Auditor or TricksterMod
Recommended settings :
Governor: Intelliactive
I/O Scheduler: Fiops or row
TCP Congestion : Westwood
GPU Governor : Simple Ondemand Or Msm-adreno-tz
Hotplug : Intelliplug ( Keep screen off frequency to 787 MHz )
Powersuspend : Hybrid
Simple GPU Algorithm : On​
How DO I flash this?
Reboot to recovery.
Install zip from SD Card.
Choose the SpiritKernel-Rx-thea.zip
Insatll and Reboot.
Changelog:
Click Me
Downloads:
Basketbuild
Source:
Github(branch:spirit)
Wiki containing changelogs,settings and more
Antutu Score: http://forum.xda-developers.com/showpost.php?p=59736983&postcount=136
Credits (In no specific order)
@faux123
@Cl3Kener
 @slukk
 @luca020400
 @savoca
@Anas Karbila
@hurtsky
 @YoshiShaPow
@Flashhhh
@flar2
And more

Works on Official CM12.1! Thank u DC

No update?

just tried this kernel and seems great (much snappier than stock cm)... only issue is cam does not work

Great work OP, but same here, camera FC all the time, even with different cameras =(

Hey, very nice kernel with lots of options and features! However, like the others above, the camera says it is busy and closes (motorola app, but should be the same with other camera apps). The torch (flashlight/flash) also does not work, probably same problem as with the camera. Could it be because of your modification of torch power by 20ma?
Tested on cm12.1
Cheers

Camera doesn't work. Torch is completely removed. Are you actually going to update this?

Locking this one, until I make a fully working zip.
Links will remain and users who want to give a try can go ahead.
YOU"VE BEEN WARNED

[KERNEL][MIDO][8.1.0-11] Ethereal Kernel for Redmi Note 4 - Mar 27

{
"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"
}
Compatibility​
All Oreo, Pie , Android 10 and 11 Custom ROMS. Official MIUI based on Nougat is not supported. However, it may work on MIUI GSIs. This kernel is only for ROMs shipping with 3.18 kernels.
Features​
L̶e̶g̶e̶n̶d̶a̶r̶y̶ Pretty Good™ Battery life
Flash and Forget
Minimal in ZIP Size; Only Around 10 MB
Compiled Using Clang 13 with Cortex-A53 Optimizations
CPU Overclocked Up to 2.2 Ghz
GPU Overclocked Up to 725 Mhz (Not on by Default)
CPU Governors: Interactive, Powersave, Performance
I/O Scheduler: CFQ
TCP Congestion Algorithms: Westwood, Reno
The Absolute Best F2FS Support [Inline with Linux 3.18 + Backports from up to Mainline | Rapid GC | Default to nobarrier FSync Mode | Optimization of F2FS' "extension list" to be specific to Android's usecases]
Super Low Screen-wake Latency
KCAL Control
Vibration Strength Control
Ability to Choose Between Stock and Stronger Modified Vibration Patterns (See installation instructions for more info)
Kill Haptics while Camera is in Use
ElementalX Sound Control
Faster Fingerprint Verification
CPU Input Boost (User Configurable)
TTL Target / IP Mangle Support
Optimized Audio Codec for Better Audio Output Through Earphones and Speakers [ Louder | Cleaner | Less Hissy ]
USB Fast Charge Up To 900mA
Disabled a lot of Debugging Bloat for Less User Overhead
NEON Accelerated ChaCha20 Crypto Algorithm for Faster Random Data Generation
SafetyNet Flag Bypass
ZRAM Backports and Additional Swap Improvements
Supports Franco Kernel Manager Performance Profiles
Supports Spectrum Profiles
Installation Instructions​
If you're updating from previous versions of Ethereal kernel or flashing a custom kernel for the first time
❯ Flash kernel ZIP -> Reboot
If you've flashed a different custom kernel before but would like to migrate to Ethereal
❯ Flash boot.img of your ROM (located in root of ROM ZIP) -> Flash kernel ZIP -> Magisk (optional) -> Reboot
The kernel ships with stock vibration patterns by default. If you'd like to switch to the modified one, simply add the keyword modvib to the file name before flashing (e.g. EtherealXO-30.0~Deity-GCC930-Mido-20200825-modvib.zip). Once this is done the ZIP MUST be flashed from recovery instead of through other means such as FKM's flasher.
Download
Download the Latest Version of the Kernel from Here
Telegram Release Channel
Ｅｔｈｅｒｅａｌ　Ｋｅｒｎｅｌ　セヅ易​
If you like the kernel then consider donating on my PayPal Here
XDA:DevDB Information
Ethereal Kernel, Kernel for the Xiaomi Redmi Note 4
Contributors
SJD Ayy, englezos, Everyone
Source Code: https://github.com/obscenelyvague/ethereal_mido/
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: FinalAF
Stable Release Date: 2018-11-19
Created 2018-11-19
Last Updated 2020-11-17

Changelogs:
07-09-2020
Merged ACK
Reevaluated Selinux State Related Changes
Miscellaneous FiX0rZ
25-08-2020
Selectively Merged ACK
F2FS Fixups from 4.14
Unified Stock & Modified Vibration Pattern Variants in One ZIP
Kill Haptics while Camera is in Use. Bzzt-Bzzt? NO.
Switched to Software Deboucing for Power Key
Updated WiFi Regulatory Database
Back to Reporting True Selinux State to System and Spoofing it Only for GMS
25-07-2020
Merged kernel_common
Latest F2FS Fixups from 4.14
Optimized 4 More Instances of Frequent Memory Allocations in the Kernel
Improved Touchscreen Suspend/Resume Routines
Updated WLAN Stack from a Diverging CAF Tag
02-06-2020
Merged Common Kernel Changes
F2FS Fixups from 4.14
Sped-up Magisk Preservation Process
Updated Wireguard
Reverted LOS' MAC Address Override
May or May Not Have Slightly Improved Battery Life
24-04-2020
Selectively Merged Android Common Kernel Changes
F2FS Fixups from 4.14
Updated GCC to Version 9.3.0
Brought Back Wireguard Support
Increased Swap Space to 2 GB
Ditched Module Blocker. You do you, buddy!
Started Honoring Thermal Engine's Restrictions Again
09-03-2020
Backported Scheduler Changes Agennnnnnn! Yeah, I think I'm okay with where it's at now ツ
Overhauled Flasher Interface
Optimize F2FS Extension List to be Specific to Android Usecases, For Storage Longevity
Default to nobarrier FSync Mode on F2FS
Went Back to CFQ I/O Scheduler Again; But Now with I/O Group Weights Set Up
Made Boosting Kinda Aggressive Doe
Improved LMK to Kill Less; Alongside Other Memory Management Improvements
04-02-2020
Selectively Merged Android Common Kernel Changes
Selectively Backported F2FS Changes from k4.9
Finally Went Back to Enforcing Selinux Again
Re-enabled Accurate Task Stats Accounting
Enabled Support for Alternative Bluetooth MACs and PHYs
EVeN mOAR SchED fIxuPS
Makes Usage of Various (((Optimizer))) Magisk Modules Completely Useless and Redundant
13-01-2020
Merged kernel_common Changes
Backported Select F2FS Patches from Mainline
Replaced Samsung's SdFat Driver with arter97's Newer Modified Version of It
Nuked Custom CPU Governors and Unused I/O Schedulers
Experimental: Blocked Thermal Engine from Capping off CPU Frequency
Made Miscellaneous Performance Improvements from Upstream & CAF
07-12-2019
Merged Common Kernel Changes
Backported F2FS Changes from Mainline (Read More)
Ported over kerneltoast's Stable Rewritten ION & IOMMU Drivers (Credits: Zile995)
Imported Newest WLAN Stack from CAF (Enables Some Features Introduced with the WPA3 Standard)
Moar Sched Fixups
Inlined Mutex with k4.4
08-11-2019
Completely Overhauled Scheduler from the Ground Up
Merged Android Common Kernel Changes
Fixed ADB Over USB
Backported Latest F2FS Patches from 4.9 & Mainline
Optimized and Sped-up Entropy Pool
Experimental: Brought Over Select Additions from Pixel 4 Kernels
15-10-2019
Obligatory kernel_common Merge
Backported LowMemoryKiller from 4.9 Alongside Motorola's Optimizations for it
Fixed 1 More Memleak
Reverted Recent Rapid GC Changes; Not *really* Needed to Keep Core Functionality
Brought Over Select Fixes From Pie and Android 10 CAF Tags
19-09-2019
Merged in Latest Google Common Kernel Changes
Merged in Changes from the Latest Appropriate CAF Tag for the SoC
Tuned Vibration Settings Once Again but Slightly Differently this Time Around
Cleaned-up Ramdisk to be Less Cluttered
Fixed 2 Memleaks
Various Minor Improvements in the NET Subsystem and ProcFS
+ Some Other Stuff Not Really Worth Writing Out
23-08-2019
Compiled Using GCC 9.2.0
Merged in Latest Google Common Kernel Changes
Sped-up More Cache Allocations (15 New Instances)
Merged in Latest F2FS Changes (+Sped-up Cache Allocations | Updated Rapid GC)
Back to Stock Vibration Settings and Patterns
Brought Back Anxiety I/O Sched.
Refactored Input Boosting [Tunables for it May No Longer be Visible on Some Kernel Managers]
+ A Whole Lot More I Wont Go Through on This One
12-07-2019
Compiled using Bare-Metal GCC 9.1.1 (Wasn't the root cause of any problem in the past)
Merged in Changes from Google Common Kernel
Merged in Changes from Appropriate CAF Tags
Don't Let the Kernel Dynamically Allocate Memory for Various Kernel Subsystems; Allocate Fixed Amounts Instead. This Improves Performance to a Certain Extent
Don't Let GCAM and the Settings App Hog Memory in the Background
Re-enabled Devfreq Memory Latency Governors
Experimental: Backported eMMC Patches from Mainline Linux
Experimental: Put SDcards in a 'Hibernated' State When Not in Use to Save Power
Improved Idle Drain (*Relaxed* Workqueues, Wakelocks and Alarmtimers Sent in by Apps)
Ditched BFQ I/O Scheduler
Tuned Boosting
Fixed Orangefox Recovery Not Being Able to Mount cust Partition at the End of the Flashing Procedure
[Insert Obligatory Line about Other Miscellaneous Under-the-Hood Changes Here]
20-06-2019
Fixed Random Screen Freezing for Certain People
19-06-2019
Merged in Latest Google Common Kernel Changes
Merged in Latest F2FS Changes
Updated Prima WLAN Driver
Optimized Android Binder and Shared Memory Allocator
Micro-Optimized Process Information Pseudo-Filesytem
Backported Changes for Various Kernel Libraries
Updated LZ4 Compression Algorithm
Temporarily Removed Anxiety I/O Scheduler
Updated AK3
07-06-2019
Switched back to Clang 'cuz GCC 9.1.1 no stable 〴⋋_⋌〵
Fixed Random Sudden Display Anomalies
Removed Electron CPU Governor
Updated AK3
06-06-2019
Compiled Using Bare-Metal GCC 9.1.1
AK3 Fam Squad
Merged the Latest CAF Tag
Improved GPU Power Efficiency
Back to Using CFQ as the Default I/O Scheduler
Removed zstd from the Supported List of Compression Algorithms
Turned on File Synchronization
Additional Camera Fixups from CAF
Miscellaneous Under-the-Hood Changes
26-05-2019
Fixed Splashloop
Stopped Verbose Logging when Booting
TCP/Net Improvements
Minor Memory Management Improvements
Miscellaneous Under-the-Hood Changes
23-05-2019
Actually Upstreamed to Linux 3.18.140
Back to Using Intelliactive as the Default CPU Governor
Enabled Dynamic FPS on All Display Panels
Updated Anxiety I/O Sched.
Reduced Dirty Writeback Frequency as per Google's Recommendation
Fixed Kernel Panics, Hopefully
17-05-2019
U̶p̶s̶t̶r̶e̶a̶m̶e̶d̶ ̶t̶o̶ ̶L̶i̶n̶u̶x̶ ̶3̶.̶1̶8̶.̶1̶4̶0̶ (Edit: Linux Upstream Changes were accidentally left out on this release)
Merged in Latest F2FS Changes
Tuned Vibration Motor Again [Actually Differentiable this Time Around]
Made Boosting Less Aggressive
Removed Devfreq Boost Driver
Removed Maple I/O Scheduler
Added Back LZ4 for ZRAM and Use it as the Default Compression Algorithm [zstd Still Available as an Option]
Bumped Up Swappiness to 100 and Increase ZRAM DiskSize to a Gig Again
Fixed USB OTG
Disabled Support for Ancient Filesystem which Hopefully Nobody still Uses
28-04-2019
Upstreamed to Linux 3.18.139
"""Fix""" the Wake-up Delay on Pie ROMs; Omit the Previous Hack
Reworked the GPU Freq Table; Max Freq is Now 725 Mhz Instead of 700
Added Compat VDSO for Faster Syscalls on 32-bit Applications
Updated sdFAT Driver to the Latest Version
Changed Display Dimming Method
Nuked IPA_WS Wakelock
Nuked WireGuard
Minor Adjustments to Both Of the Fingerprint Drivers
Experimental: Updated Anxiety; Set it as Default I/O Scheduler
Experimental: Backported Memory Manangement and Multi-Queue Block IO Changes From 4.x Kernels
Experimental: Backported ZRAM From Linux 4.9
Experimental: Use zstd Compression Algorithm for ZRAM
Experimental: Tuned Vibration Motor
05-04-2019
Upstreamed to Linux 3.18.138
Merged CAF Tag "LA.UM.6.6.r1-11000-89xx.0"
Change Up Default CPU Settings
Restore ZRAM Stuff to How they were Before
Prevent Init from Changing I/O Scheduler on Boot (Some ROMs set it to BFQ; We Don't Want that)
Removed Deadline and NOOP I/O Scheds. (Gone for Good this Time)
Boost Frequencies on Camera Auto-Focus
Fixes and Whatnot
28-03-2019
Upstreamed to Linux 3.18.137
Fall back to ALMK, Disabled SLMK (Turns out this isn't as stable as I had initially thought)
Replaced State Notifier with a Simple Display State Tracker
Allocate 1 gig of ZRAM with 2x the Compression Streams; Bumped Up Swappiness to 100
Don't Hotplug Half the Cores When Battery Goes Below 15%
Updated Anxiety I/O Sched.
Couple of Upstreams from Google Common Tree
Removed Unused Devfreq Governors
Removed LiveDisplay Driver
Enabled OOM Kill Allocating Task
Fixed(?) Issues Introduced with Release 10
16-03-2019
Compiled Using DragonTC/Clang 9.0.0 with Polyhedral Optimizations
Upstreamed to Linux 3.18.136
Merged in Latest F2FS Changes
Dropped Non-Treble Support // Updated the Flasher as well
Stop Shipping Modified Thermal Config (Temps Skyrocket Because of It)
Removed Darkness CPU Governor
Removed Boeffla Wakelock Blocker (Does Nothing Significant. If Anything, Having it Only Makes Idle Drain Worse)
Added Devfreq Boost Driver
Tune Default Boost Parameters
Bump Up Swappiness to 20
Completely Disable I/O Stats Accounting
Experimental: Replaced Android LMK with Simple LMK
NEON Accelerated ChaCha20 Crypto Algorithm for Random Data Generation
Switch to 300 Hz Kernel Timer Tick Rate
We /LightAF/ Now, ZIP Size Down to Only 10 MiB
Updated Spectrum and FKM Profiles
A lot More Under-the-hood Changes
20-02-2019
Compiled using ARM's Bare-Metal Toolchain
Upstreamed to Linux 3.18.135
Removed Dyn Fsync; Wasn't Working as Intended
Started relying on Input Boost Again
Boost DDR Bus to MaxFreq on Screen Wake
Kanged Thermal Config; Will be Placed upon Installation
07-02-2019
Removed Undervolts
Minor Fixes
06-02-2019
Upstreamed to Linux 3.18.134
Uv'd by 100 mV Instead Just to be Safe from Any Panics
Brought back Deadline and NOOP I/O Scheds
Disabled SECCOMP
Added in Kernel-sided Stuff Needed to Ensure Ultra and HPH:X Compatibility
Made sure proper Bootparams get Applied on All ROMs
A lot of Under-the-hood Changes I Won't Go Through
26-01-2019
Upstreamed to Linux 3.18.133
Up-to-Date with Latest CAF/Prima Tag
Back to Old CPU Settings with Intelliactive
Undervolt the CPU by 150mV
Merged in Latest F2FS Changes Along with arter97's GC Patches
Introduce Dynamic FSync 2.1
Imported Latest DTS Driver from X00QD
Removed Generic FP Boost Driver; Emulating It's Boost Behavior Straight from Our Own FP Drivers Now
Added USB HID Gadget Support
Removed Unused TCP Algos and I/O Scheds
Enable ULPS, Partial Update and High Speed DSI Mode for All Display Panels
Fixed an Issue Where Spectrum Profiles weren't Getting Applied on Selinux Enforcing ROMs
Few Upstreams from Google Common Tree and Other Miscellaneous Under-the-Hood Changes
04-01-2019
Haxx: Fix Wakeup Delay on Pie ROMs (@lilblinx)
Removed ElementalX and Conservative. Added Electron (Set as Default Now)
Start Relying on Input Boost to Avoid Micro-Stutters
Enabled TTL Target / IP Mangle Support
Omit Auditing from Selinux and Other Places
Omit A LOT more Debugging Stuff End-Users Won't Ever Utilize
Omit Some GPU Thermal Limits
Added Live Printk Toggle Interface
Anxiety Upstreams
Enable Support for TCP FastOpen on All Listeners
Tweak the Slimbus Just a Lil'
Refresh the Spectrum and FKM Profiles According to New Changes
22-12-2018
Upstreamed to Linux 3.18.131
Multiple CAF Upstreams
Multiple Prima Upstreams
Android Binder Updates
Pull Missing USB, MMC Changes
Remove unneeded SMP2P Test Support
13-12-2018
Compiled using UberTC 8
Upstreamed to Linux 3.18.129
Back to Stock I/O Settings
Fixed App Opening Delays for Certain People (((Hopefully)))
Added State Notifier
Minor Changes in Goodix FP Driver Again
Slight Spectrum Profile Tune-Ups
Bring Back KCAL Color Inversion
Some Under-the-hood Improvements that aren't worth mentioning
03-12-2018
We're Now Compiling with Linaro GCC 7.2 with Cortex-A53 & Graphite Optimization Flags
Upstreamed to Linux 3.18.128
Reworked Spectrum and FKM Profiles
Now Using SultanXDA's Simplified CPU Input Boost Instead of Traditional CPU Boost
Replaced Barry_Allen with ElementalX Governor
Tuned-up Westwood TCP Algorithm for Slightly Better Latency (Ping)
Minor Changes in FP Sensor and Touchscreen Drivers
Reduced GPU Idle and Deepnap Timeout; Now in-sync with MDSS
Some MDSS & KGSL Additions for Power Efficiency
23-11-2018
Upstreamed to Linux 3.18.126
Removed Logging Lines from Both Goodix and FPC Fingerprint Drivers. Unlocking and Fingerprint Operations should be a Few Milliseconds Faster Now
Removed Arch Power and Gentle Fair Sleepers SySInterface and Disable Fair Sleepers from Source
Temporarily Disable Frandom
Do Final Bits of Audio Codec Tuning
Overclock Crypto Engine Driver from 100Mhz to 160Mhz
Disable some Miscellaneous Debugging Stuff
Some GPU Tune-Ups and Improvements for Power Efficiency
18-11-2018
Initial Release

Kindly include your kernel source code

long time support to mido?

Highly interested. I think I may have a kernel fetish.

Loved the kernel, the features, observed significant improvement in sound.

Waiting another overclock kernel and its come,,try right now,,thanks dev

i wish it also has a version for miui 10 nougat

Nikhil said:
Loved the kernel, the features, observed significant improvement in sound.
Click to expand...
Click to collapse
Come back pixel mido please. We miss you

This kernel have alot future funcition,but scrolling in apps get little lags,not smooth

Very smoooooooooooth ....!!! :good:

Niceee!!!

Woww

Using with miui 10 8.1 sgsi. Good Performance:Battery backup.
---------- Post added at 12:15 PM ---------- Previous post was at 12:14 PM ----------
mad jebon said:
Niceee!!!
Click to expand...
Click to collapse
Which rom? Balanced or Performance profile?

So far so good. Thank you Dev.

xcongc said:
Using with miui 10 8.1 sgsi. Good Performance:Battery backup.
---------- Post added at 12:15 PM ---------- Previous post was at 12:14 PM ----------
Which rom? Balanced or Performance profile?
Click to expand...
Click to collapse
Rom Aosp extended 8.1,i dont use profile,just tweaks using ex kernal manager

Ohh a new kernel, have to try this haha!

Doesn't 900mA sounds too low for fast charge or is it just mistyped.

Edesh Kumar said:
Doesn't 900mA sounds too low for fast charge or is it just mistyped.
Click to expand...
Click to collapse
Normal USB charging current is 500mA. This is increased to 900mA.
This is not related to Quick Charge.

ferow2k said:
Normal USB charging current is 500mA. This is increased to 900mA.
This is not related to Quick Charge.
Click to expand...
Click to collapse
No, I mean when I am plugging my charger I can't see current above 900mA but in other roms it goes upto 1750mA.

[CLOSED][KERNEL][MIDO]Meepo Kernel - Redmi Note 4/4x

delete this thread pls

What the different of chronicle and deadly?

Irfan Mohamed said:
What the different of chronicle and deadly?
Click to expand...
Click to collapse
deadly is first release , deadly better

Ultimatum Release
Meepo Kernel Is Update 10/07/2019 By @rafiester
Codename : Ultimatum
Changelogs :
[Thanks to kerneltoast for all great commits]
-Increased vmstat interval to 20 seconds
-Slimbus Overclock
-Binder: Reserve caches for small, high-frequency memory allocations
-Msm: kgsl: Don't allocate memory dynamically for temp command buffers
-ALSA: control: Don't dynamically allocate a single struct instance
-Proc: Don't let Google Camera and Settings run in the background
-Kernfs: Avoid dynamic memory allocation for small write buffers
-Selinux: Avoid dynamic memory allocation for small context buffers
-Ext4 crypto: Use a larger on-stack file name buffer
-Kernfs: Avoid dynamic memory allocation for small write buffers
-Msm: kgsl: Avoid dynamically allocating small command buffers
-Selinux: Remove audit dependency
-Cpufreq: interactive: Skip timer when policy->min == policy->max
-ASoC: wcd-mbhc: Improve detection speed and accuracy
-Msm: kgsl: Remove POPP
-Msm: camera: sensor: Fix memory leaks when sensor probe fails
-Delete some file to avoid some error
-Minor fix performance hope got more improvement
Download Link : https://www.androidfilehost.com/?fid=6006931924117913488

Nice Kernel
I'm using it.
Keep it up.

Costa001 said:
Nice Kernel
I'm using it.
Keep it up.
Click to expand...
Click to collapse
thankss

thx ramadhanr124..

Meepo Kernel Is Update 12/07/2019
Codename:ZennyX
Changelogs :
-Merged Latest Caf Tag LA.UM.7.6.r1-05500-89xx.0
-Merged Latest Android-3.18
-Revert "msm: mdss: Reduce display commit latency caused by deep CPU idle"
-cpufreq: interactive: Remove the jump_to_max hack
-dmaengine: Fix memory leak
Download Link : https://www.androidfilehost.com/?fid=6006931924117915055

good.
kthx

Are there any groups on the telegram for discussion?

Meepo Kernel Is Update 19/07/2019
Codename: EnchantrezX
Changelogs :
-Compiled Using GCC 10 + DragonTc 9.0
-Added GPU Oc 700Mhz
-Added UKSM Dan KSM
-Added Audio Overclock
-Added DTS Eagle Support
-Added IO Anxiety, Zen, Fio, Sio, SIoplus, Fifo
-Added Back Spectrum config this one better
-Added Francokernel profil app
-Tune vibration intensity
-Improve vibrator scheduling
-Dont dynamically allocate single-use structs
-Import Ion driver thanks to @Zile995
-Revert "Ion panic"
-Misc and improvement for performance and battery life
Note :
-Deleted Thermal.Config so its not replace ur favourite thermal anymore
Download Link : https://www.androidfilehost.com/?fid=6006931924117919863

Hello, can someone explain the "adreno idler" feature?
Is really effective?
Tnx
By the way, this is a great kernel. Kudos to the dev.

MeepoKernel Is Update 28/07/2019
Codename: Natozylde
Changelogs :
-Compiled using Bare-Metal GCC 9.1.1
-Add Cafactive Governors
-Add GPU OC 750Mhz
-Intoduce Intelliactive tweaking
-Intoduce conservative tweaking
-Drop polly clang support
-Performance improvement
Download Link : https://www.androidfilehost.com/?fid=6006931924117925817

Edit: Thread Reopened on OP request.
@ramadhanr124 Please update the links
Funk Wizard
Forum Moderator

Thanks to u for using my meepe

Thread closed as per OP post
Funk