Database Info

[KERNEL][HYBRID]G3MOD v2.5

G3MOD TEAM
Founder
dharamg3
Kernel Developers
hillbeast , moikop , cool.darshak
Application Developers
dympy , andreapier
ROM/Theme Developers
Stylooo , RafayelG , aarrun​
Kernel Features:
Non-OC Version: 83MHz - 667MHz
OC Version: 83MHz - 1200MHz
RootADB
Busybox 1.19
File System Support: rfs/ext2/ext3/ext4
Init.d Scripts
1% Battery Mod
OverClocking
UnderVolt
data2sd
BFQ I/O Scheduler
Voodoo v10
CWM Touch Recovery
Configurable CompCache
BootLogo
TinyRCU
MultiBoot
Kernel Hz: (Non-OC: 250, OC: 500)
tun.ko
100MHz CPU clock stepping
DMA Enabled in G3D
Dynamic OC
Hybrid kernel (supports every firmware for Galaxy 3)
Hybrid Data2SD
Multi Data
NTFS read-only support (but no auto mounting SD card yet)
BLN Support. (Thanks to marcellusbe)
JFS and HFS+ support
CWM Features:
1) Reboot
2) Extended Power Menu
1.1) Power Off
1.2) Reboot
1.3) Reboot Recovery
1.4) Download
3) Update.zip's
3.1) Update.zip from sdcard Root
3.2) Select .zip from sdcard
3.3) Toggle Signature Verification
3.4) Toggle Script Asserts
4) Multiboot
4.1) Switch ROM's
4.2) Backup ROM
4.3) Switch Kernel's
5) Data / Factory Reset
6) Wipe
6.1) Data / Factory Reset
6.2) Cache
6.3) Wipe dalvik cache
6.4) Wipe Battery Stats
7) Backup and Restore
7.1) Backup
7.2) Restore
7.3) Advanced Backup 7.3.1) Boot 7.3.2) System 7.3.3) Data 7.3.4) Cache 7.3.5) sd-ext
7.4) Advanced Restore 7.4.1) Boot 7.4.2) System 7.4.3) Data 7.4.4) Cache 7.4.5) sd-ext
8) Mounts And Storage
9) Advanced

Kernel Downloads:
http://code.google.com/p/g3modteam/downloads/list
Kernel Changelog:
v2.5 (15/05/2012
Supports CM7a8.1
Supports ICS (if colours are screwy, update OpenFIMG)
CWM5 with touch
General source code fixes
v2.4.1 (23/02/2012)]
CM7 A7 support!
Fixed filesystem covertion system.
Lagfree governor properly implemented.
Added BLN support.
Fixed wifi for CM7 (Thanks to Arakmar).
v2.3 (15/12/2011)
Hybrid initramfs: Added support for ICS-based roms.
Multiboot: Fixed dalvik-cache restoring.
Multiboot: Added support for backing up android_secure.
AOSP Proximity sensor support added.
Initramfs: Optimized init.rc files and added usb.rc file.
MAX8998 Driver: Removed led blinking support since it isn't being used anymore.
v2.2.2 (21/11/2011)
Went back to old BLN system, this seems to work fine.
New NON-OC Kernel Hz: 250.
Should have a better battery backup
v2.2.1 (16/11/2011)
JFS Utilities permission fixed.
BLN System fixed.
v2.2 (15/11/2011)
Support for new BLN system.
Optimized SIO Scheduler for flash devices.
Added JFS Utilities (forgotten in the previous release).
Dropped OC+ version support.
v2.1 (09/11/2011)
Lagfree Governor.
83Mhz steps for Non-OC and OC+ version
Lowmemorykiller.c tweak.
Reverted ondemand performance tweak.
Updated BFQ I/O Scheduler to v2.1r1.
Data2SD tweak: Improved IO Performance for non-Data2SD users and fixed *incompatibility* with Kyrillos's App2SD script.
Added Hybrid Data2SD internal System cache.
Compcache is now configurable.
Fixed battery drain problem.
BLN Support. (Thanks to marcellusbe)
Removed InteractiveX governor due to problems.
JFS and HFS+ support.
v2.0 (02/10/2011)
Hybrid kernel (supports every firmware for Galaxy 3 (except Eclair))
CM6.2 and CM7 Support (obviously but it must be said twice)
Adjusted battery driver (more accurate)
83MHz minimum on OC kernel
Hybrid Data2SD
Multi Data
Compcache toggleable
InteractiveX CPU frequency mode
SIO scheduler
MD5 hash disabled on nandroid
More stable at idle
Reduced power drain at idle
jhash3 removed as it increased power drain.
v1.9 (09/09/2011)
tun.ko included and enabled
100MHz CPU clock steppings: you can now set your speed to anything between 100 and 1400MHz in 100MHz step (100, 200, 300...)
CPU minimum frequency now 100MHz on Performance, Ultimate and Extreme
jhash3 for improved HSDPA/3G/EDGE speeds.
Multiboot improved for data backup and recovery
Added Reboot and Wipe Data/Dalvik Cache to main menu of CWM.
DMA enabled in G3D - Thanks marcellusbe
Added InDroid and CM7 to Multiboot
v1.8 [30/08/2011]
Reworked Battery Driver
Reworked CWM Recovery
Now 11 ROM's support in Multiboot
v1.7 [15/08/2011]
Multi Boot
Power off Option in CWM
Dynamic OC (ability to change the maximum freq)
Modify the max_blk_count value to prevent overflow.(sdcard related)
mmc: core: Fix dereferencing after NULL check (sdcard related)
Lower vfs_cache_pressure 100->25.
ARM: fix some sparse errors in generic ARM code
lib: Improve the performance of memcpy and memmove of the general version
lib: Introduce some memory copy macros and functions
ashmem: fix deadlock when system is low on memory
v1.6 [11/08/2011]
Batter Driver Back to Original - Only Change is added Compensation for Data On
Stable OC
UV Works for All Frequencies - Can be checked via dmesg
Removed SavagedZen and SmartAss for now.Giving Problems. Will come back in future versions.
SDCard Partitioning Problem Solved - Ext3 partitioning for mmcblk0p2 - Can be converted to Ext4 Using g3mod app.
Kernel Flashing via CWM Recovery Working
Kernel Hz: Lite:256 Performance:300 Ultimate:500 Extreme: 1000
Noop I/O Scheduler by default
Fixed Typo in Bootlogo
v1.5 [05/08/2011]
CompCache
BootLogo
TinyRCU
Battery Driver Reworked - Please test and give feedback
v1.4 - 31/7/2011
CWM Recovery In Kernel
Fixed CPU Freq Driver. SetCPU now shows properly.
UV working properly now.Can Be Checked in dmesg.
A 1300MHz freq Step in Extreme Version for those who want 1300MHz overclocking.
Changed Kernel Hz to 300 for Better Battery Backup.
v1.3.4 - 27/7/2011
Overclocking Stable (Less freezes) - To Test
BFQ I/O Scheduler - http://algo.ing.unimo.it/people/paolo/disk_sched/
Extreme Version Screen Off Bug Solved
No OC bus for any versions - (For those who want OC Bus, please use v1.3.0 for the moment. I will try to make OC bus in some better manner)
v1.3.3 - 25/7/2011
5 Touch Mod
Removed RAM Optimization Script
Overclocking Stable (Less freezes) - To Test
Solved Bug which showed wrong freq in SetCPU and PimpMyCPU
Solved Time In State for SetCPU
Extreme Version has OC Bus 200MHz

Frequently Asked Questions​
For NOOBS​
Q) How to flash the kernel
A) Just apply update.zip from Recovery or flash tar file using ODIN.
Q) Will i lose my data if i flash kernel?
A) No, you wont lose any data nor do you have to wipe data or cache.
Q) Does my battery need to be 100% to flash?
A) Not at all
Q)Flashed CM 6.2 Kernel on Froyo Rom and WIFI doesnt work?
A) There are two versions of Kernel. One is for Froyo Rom and other is for CyanogenMod Rom 6.2 (CM 6.2). if you are on Froyo rom and flash CM 6.2 then your wifi wont work and vice versa.
Q) 1400 Mhz (Extreme version) doesnt work for me
A) Not all Galaxy 3 suppport overclocking as high as 1400 Mhz. If it doesnt work then keep frequency lower or flash Ultimate, Performance or Lite version
Q) What does this data2sd in g3mod do?
A) data2sd is method by which all your /data partition goes to your sdcard thus giving you more space for downloading apps. Its suggested to use data2sd only if your sdcard class is higher than Class 6
Q) Internel Memory shows 0kb
A) Check if you have fs.data2sd at this location /sdcard/Android/data/g3mod/ If yes then delete it or else your sd card doesnt have sd-ext partition
Q) How can i go to recovery mode
A) Press MENU+VOLUME UP+VOLUME DOWN+POWER button and bingo!!!
Q) Should i use multi boot even if i am having 2 gb card class 2 ?
A) Sd card with any class can use multiboot
Q) Data Wipe Necessary When Switching Between CM and Froyo ?
A) Yes data wipe is necessary for switching roms between CM and Froyo. But we have given option to Backup data also in recovery.
Q) My APP is not working after Flashing KERNEL
A) Its not a kernel problem
Q) What is tun.ko?
A) It is basically used to setup Open VPN connections
Q) What is jhash3?
A) jhash3 improves the HSDPA/3G/EDGE speed
For Advanced users​
Q1) Battery is draining fast?
A) After flashing the kernel please calibrate your battery or else let 3-4 full battery cycles pass.
Q2) Which profiles should i use?
A) Lets take example that you are using Ultimate kernel. Keep the governor ondemand (Like every good boyfriend fulfills all demands of his girlfriend ondemand governor does the same for your CPU ).
Make profiles:-
1) Time Profile - 12 am to 6.00 am Freq 100 Mhz to 400 Mhz Priority 100
2) Screen Off - Freq 100 Mhz to 600 Mhz Priority 95
Q3) What are advanced settings in the SetCPU mean?
A) Sampling rate is rate at which the frequency of your CPU changes. Up Threshold is limit at which CPU will change freq on load (Scales Up). Down Threshold (conservative only) is limit at which CPU will change freq on load (Scales Down). Powersave bias is used for saving the power of CPU, it will slow down the CPU and affect the performance also 200 in powersave bias mean 20%...250 means 25% and so on.
Q4) I want performance and also good battery what profiles should be i use?
A) Refer to Q2 for Profiles Set up and now go in Advanced tab and Keep Sampling Rate 10000 or 15000. Upper Threshold to 90 and Powersave bias to 200 (20%). Since we are using powersave bias, this will affect the performance as it slows down the CPU so to increase the performance we are lowering the Sampling rate thus we get perfect balance of Performance and good battery backup.
NOTE: ABOVE SETTINGS ARE JUST EXAMPLE..PLEASE PLAY AROUND AND CHOOSE SETTINGS WHICH SUITS YOU THE BEST

WATCH THIS NOOBS​

Donations:
If you want to donate to the team as a whole, please divide the amount and donate separately to each member. Sorry for the trouble caused.
Thank You for considering to donate.
dharamg3 -
hillbeast -
moikop -
cool.darshak -

Steps for Multi boot:
1) Flash Kernel v1.7+
2) Go to CWM Recovery -> Multiboot -> Backup ROM.
3) Backup your Current ROM to ROM1 (It will backup the system.img at /sdcard/Android/data/g3mod/roms/romname_ROM )
4) Add the system.img of your 2nd ROM to /sdcard/Android/data/g3mod/roms/romname_ROM and similarly for different ROM's.
5) Use the CWM Recovery -> Multiboot -> Switch ROM option to switch between different ROM's.
6) If switching between Froyo ROM and CM6.2 RoM, you will need to wipe data and also change kernel's via update.zip method.
7) Use the data backup and restore option to prevent loss of data when switching between Froyo and CM6.2 ROM's.
Note: Ask the developer of the ROM's to provide you with the system.img for their ROM
How to use Hybrid Data2SD
1) Connect your phone via ADB
2) Go into adb shell
3) Type 'echo hybrid > /sdcard/Android/data/g3mod/fs.data2sd'
4) Create a text document in Notepad with a list of all the directories you wish to move. Example:
Code:
app
log
dalvik-cache
---LEAVE A BLANK LINE AT THE END---
5) Save the file and call it 'data2sd.dirs'
6) Do 'adb push data2sd.dirs /sdcard/Android/data/g3mod/'
7) Reboot your phone
8) Once your phone has booted, run 'adb shell cat /data2sd.log' to ensure it is running correctly.
How to enable Multi Data
1) Connect your phone via ADB
2) Go into adb shell
3) Type 'echo 0 > /sdcard/Android/data/g3mod/multiosdata'
4) Multi Data will automatically backup your data upon booting into a different OS.
Make sure to not wipe your SD-EXT partition. Doing so will erase the backups from other firmware. Only wipe it if you wish to erase data for everything.
You can also use Multi Data to quickly restore data if your phone has become corrupted. It will restore it back to the last multi-boot switching
1) Connect your phone via ADB
2) Go into adb shell
3) Type 'echo 0 > /sdext/lastos'
4) Reboot the phone
Directories for Multi boot:
//ROM Dir
__system("mkdir /sdcard/Android/data/g3mod/roms/CyanogenMod6_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/CyanogenMod7_ROM"); //Add CM7 Support
__system("mkdir /sdcard/Android/data/g3mod/roms/G3MOD_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/Kyrillos_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/Grigora_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/AOSP_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/DutchMods_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/Kyorarom_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/Indroid_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/rom1_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/rom2_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/rom3_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/rom4_ROM");
//Data + sd-ext Backup Dir
__system("mkdir /sdcard/Android/data/g3mod/data/Froyo_DATA");
__system("mkdir /sdcard/Android/data/g3mod/data/CM6_DATA");
__system("mkdir /sdcard/Android/data/g3mod/data/CM7_DATA");
//Kernel dir
__system("mkdir /sdcard/Android/data/g3mod/kernel/Froyo");
__system("mkdir /sdcard/Android/data/g3mod/kernel/CM6");
__system("mkdir /sdcard/Android/data/g3mod/kernel/CM7");
How to configure compcache:
If you want to use default configuration (as up to now.. 62 MB aprox.), you don't have to do anything different as what you have been doing. But if you want to use a more/less memory, here are the steps:
Inside that /sdcard/Android/data/g3mod/compcache file, write ONLY the number of MegaBytes you want to use for compcache.
Reboot.
If compcache file is empty or contains a "0" inside, it will use default configuration.
How to: BLN
This is only "needed" if you have a i5801 | i5800L or any other Galaxy 3 model with back button lights and want BLN in it.
How to install:
First, download the lights.GT-I5800.so file from google code. Then execute this commands:
adb remount (or if this doesn't work: mount -o remount,rw /dev/stl6 /system)
adb rm /system/lib/hw/lights*
adb push [Location of this file] /system/lib/hw
After that, reboot and now you have BLN working
Steps for Changing the Max Freq(Dynamic OC):
There is an entry in /sys/devices/system/cpu/cpu0/cpufreq/plls_table where you can put your own value for APLL.
Before doing this, set "PERFORMANCE" governor on and min and max frequencies to the maximum.
Code:
// Do this in adb
echo "0 a[SIZE="5"][B][U]258[/U][/B][/SIZE]0[SIZE="5"][B][U]3[/U][/B][/SIZE]01 a14d0303 c07e13fc cf850240" > /sys/devices/system/cpu/cpu0/cpufreq/plls_table
You need to replace the 258(Hex Value) with your desired value.
Here 258 means
(2*16*16) + (5*16) + 8 = 600
and 3 means it is 600*2 = 1200
Therefore, a2580301 means 1200MHz.
This is a temporary method. For a permanent Method, add this line to a init.d script. Name the script to something like S10_Dyanmic_OC.
Help Others: If you calculate a Hex Value for a particular frequencies add it here:
https://docs.google.com/spreadsheet/viewform?formkey=dG5hdnpsWFdTNExiY2t3dy16VzBvaWc6MQ
You can view all the frequency Hex value's calculated by others over here:
https://docs.google.com/spreadsheet...G5hdnpsWFdTNExiY2t3dy16VzBvaWc&hl=en_US#gid=0

Kernel Related Media:
5 Touch Support:
BootLogo and Progess Bar
Multi Boot

g3mod_v1.3.4_LITE.tar (5.9 MB)
http://www.multiupload.com/3BIF9S2IES
g3mod_v1.3.4_LITE.zip (6.1 MB)
http://www.multiupload.com/9IJTKFIJDX
g3mod_v1.3.3_LITE.tar (5.9 MB)
http://www.multiupload.com/DDMMU0U9YB
g3mod_v1.3.3_LITE.zip (6 MB)
http://www.multiupload.com/DW1QZPDQOY
g3mod_v1.3.4_PERFORMANCE.tar (5.9 MB)
http://www.multiupload.com/H53ZTO5ULW
g3mod_v1.3.4_PERFORMANCE.zip (6.1 MB)
http://www.multiupload.com/WWFL3EXH0Y
g3mod_v1.3.3_PERFORMANCE.tar (5.9 MB)
http://www.multiupload.com/Y9CDMFVH61
g3mod_v1.3.3_PERFORMANCE.zip (6 MB)
http://www.multiupload.com/0MQQRR1KV8
g3mod_v1.3.4_ULITMATE.zip (6.1 MB)
http://www.multiupload.com/I4JCH7E5JE
g3mod_v1.3.4_ULTIMATE.tar (5.9 MB)
http://www.multiupload.com/TEQXRZMKPQ
g3mod_v1.3.3_ULITMATE.zip (6 MB)
http://www.multiupload.com/97DV0V4OQC
g3mod_v1.3.3_ULTIMATE.tar (5.9 MB)
http://www.multiupload.com/KV9SSVWWZ7
g3mod_v1.3.4_EXTREME.tar (5.9 MB)
http://www.multiupload.com/EGZKK89JTZ
g3mod_v1.3.2_LITE Odin
g3mod_v1.3.2_LITE CWM
g3mod_v1.3.1_LITE Odin
g3mod_v1.3.1_LITE CWM
g3mod_v1.3.0_LITE Odin
g3mod_v1.3.0_LITE CWM
g3mod_v1.3.2_PERFORMANCE Odin
g3mod_v1.3.2_PERFORMANCE CWM
g3mod_v1.3.1_PERFORMANCE Odin
g3mod_v1.3.1_PERFORMANCE CWM
g3mod_v1.3.0_PERFORMANCE Odin
g3mod_v1.3.0_PERFORMANCE CWM
g3mod_v1.3.2_ULTIMATE Odin
g3mod_v1.3.2_ULTIMATE.zip CWM
g3mod_v1.3.1_ULTIMATE Odin
g3mod_v1.3.1_ULTIMATE CWM
g3mod_v1.3.0_ULTIMATE Odin
g3mod_v1.3.0_ULTIMATE.zip CWM
g3mod_v1.3.2_EXTREME Odin
g3mod_v1.3.2_EXTREME CWM
g3mod_v1.3.1_EXTREME Odin
g3mod_v1.3.1_EXTREME CWM
g3mod_v1.3.0_EXTREME Odin
g3mod_v1.3.0_EXTREME CWM

Source For Developers:
https://github.com/dharamg3
Note:
We am learning how to develop kernels.
We willl add different features as and when we can implement them.
The main goal of this kernel will be to keep the phone stable and fast.
There will be nothing as alpha or beta releases.
We will give out the kernels directly, but if anything goes wrong and you have to reflash the ROM or kernel, please dont start shouting.
You may give us different ideas on what features to implement. We will try our best to implement all the features you want
Many of the features implemented in this kernel, are taken from marcellusbe's Fugumod Kernel, and we shall be ever thankful to marcellusbe for the fugumod kernel
Warning:
We are not responsible for any damage caused to your phone (softbrick or hardbrick)

Credits:
marcellusbe for all his help, awesome fugumod kernel
supercurio for voodoo v10
Paolo for BFQ I/O Scheduler
All developers for making this an awesome phone
Everyone who is helping is solving different issues with this kernel
Please let us know if we miss anyone ...oh we did already miss someone..thanks G3MOD TEAM too

What to the old thread?
Nm read that
Btw 6th post got some errors...

@Dharam, i have a question. In your v1.8 Kernel, We can change the partitions to any type we want, can't we? Because in Mumbozver's recovery, we could only use ext2/ext4/ext2.

kyrillos13 said:
@Dharam, i have a question. In your v1.8 Kernel, We can change the partitions to any type we want, can't we? Because in Mumbozver's recovery, we could only use ext2/ext4/ext2.
Click to expand...
Click to collapse
The kernel itself supports everything, but CWM only supports EXT2. I will look into either porting CWM4 or getting 2.5 to support more systems.

hillbeast said:
The kernel itself supports everything, but CWM only supports EXT2. I will look into either porting CWM4 or getting 2.5 to support more systems.
Click to expand...
Click to collapse
getting 2.5 to support other partitions will be a better idea...coz for CWM 4 you need complete CM7 source, and also most of the update.zip's on the g3 forums use amend...and CWM 4 supports only edify....

All the best to the future process
Sent from my GT-I5800 using XDA App

Right, I want to work on USB OTG but lack the cable, and the only way I can do it with what I have is if I destroy my only USB cable for my phone. So if someone wants me to do USB OTG, then buy me a cable and I'll do it
All the stuff is there to do it, I just need to get the phone to switch into host mode.

I think v1.9 is going to come sooner than expected...excellent work by the whole team...

Will this root my phone if I install this in Stock ROM?

[email protected] said:
Will this root my phone if I install this in Stock ROM?
Click to expand...
Click to collapse
it will give you ADB Root, but not the superoneclick root...

dharamg3 said:
it will give you ADB Root, but not the superoneclick root...
Click to expand...
Click to collapse
Ok thanks.....
I am a newbie at this...
But, which root did I get when I installed Kyrillos' ROM?

[KERNEL][06 August 2013] B2B |&| Patched [ICS Sense][MIUIv4]

This is a kernel, build from the recently released saga-ics-crc-3.0.16-62a67df source.
Compatible with all ICS (Android 4) + Sense (3.6, 4A or 4) based ROMs
OFFICIAL MIUIv4 and Stock rooted ICS users can enjoy init.d scripts support with this kernel​Enjoy!​BACK2BASICS EDITION​
FEATURES​
Interactive Aroma Installer
Completely Stock code, with only 2 additions by me:
Configurable sweep2wake.
Ported bcmdhd wireless driver from the HTC One V latest source code for better reception and no wakelocks. Still breaks WiFi tethering in ROMs based on Sense 3.6. Tethering works fine in Sense 4
Completely Stock ramdisk. The only changes are:
Unsecured boot.img (adb remount and USB debugging)
Busybox run-parts (init.d scripts) support
Some extra lines, required for the proper operation of the new WiFi driver
No OC, UV, optimizations or any other changes.
Compiled with the recommended by HTC toolchain 4.4.3
ISSUES​
For all with BLUETOOTH issues: use 4EXT Recovery
due to incompatibility with sweep2wake the native Sense screenshot function has to be disabled (on some ROMs Power+Volume Down is working- 10x to rzr09 for pointing it out). You will need to change the value of ro.htc.framework.screencapture = , located in /system/build.prop from true to falsemanually, using any root file explorer. To make it functional again (if you decide to disable s2w) just change back from false to true
NEW USERS: before flashing install/update BusyBox in /system/xbin (with some of the apps available in the Google Play - the one by Stericsson+Smart Install worked fine for me) and check for the existence of the busybox binary and run-parts symlink in the /system/xbin folder on your device. If there is no such files install/reinstall BusyBox until you have it.
OPTIONAL: If you do not have an /system/etc/init.d folder AND you want to use additional modules you should create it manually BEFORE flashing the kernel:adb remount
adb shell
mkdir /system/etc/init.d
chmod 775 /system/etc/init.d​
DOWNLOAD AND INSTALLATION​Download: b2b_3-0-16.zip
md5sum: d5bd32bd12a0e1120b03f800eaf1beda
S-OFF users: flash in recovery, no wipe required. Follow the instructions
HTCDEV users: flash in recovery, no wipe required; follow the instructions, reboot straight to bootloader and flash the corresponding to your ROM boot.img (extract it from the zip) with th following commands:adb reboot bootloader
fastboot erase boot
fastboot flash boot XXX_boot.img​IMPORTANT (HTCdev users): if you are using 4EXT Recovery Control for flashing make sure to select the "Stay in recovery after flashing" option!​
Boot images are:
Sense4_boot.img - for all Sense4 based ROMs (Fallout, ProjectX, Cooldroid, Sabsa Prime, Desire XS, ViperSaga, others)
Custom_Sense36_boot.img - for ICE_DS, Stock ICS by masteross, or other custom Sense 3.6 ROM without lib partition
Stock_Sense36_boot.img - for Ice Cream Saga or clean RUU/PG88IMG (that keeps S-OFF and Recovery) install (rooted)
MIUIv4_boot.img - for any version of official MIUIv4
NOTES:
There is no boot.img for Virtuous Infinity since it cannot operate smooth with the Stock CPU settings
If sweep2wake takes screenshot upon screen off in this version you have to modify your build.prop manually (see above)
PATCHED KERNEL 3.0.89​
Due to controversial feedback on Tweaked kernel starting from version 5.0 I have decided to take a different approach.
Patched kernel unifies the concept of both Tweaked3 and B2B kernels.
So what does this mean?
The HTC source is taken as a base and is synced completely with the upstream (the official Android kernel 3.0) where applicable. Since it is patched only up to 3.0.72 the rest of the patches are taken directly from the Linux kernel upstream.
All is done from scratch and revising every single commit (it took me 4 days to complete this only). The result is absolutely clean merge (not as in Tweaked where I took the patches from other developers without actually knowing have they screw up something in the progress). During the patching I have discovered some misses or copy-paste from 3.4 upstream (which I consider for another generation devices and probably the changes from there are not completely suitable for our device). I have cleaned and synced with the 3.0 upstream all not-updated files that I discovered during the patching. ​
FEATURES​The features of the kernel are the basic ones from Tweaked, but staying as close as possible to the Stock configuration (B2B concept):
Interactive Aroma Installer
Compiled with GCC 4.4.3 toolchain
Patched to Linux Kernel version 3.0.89
Synced with Android kernel 3.0 upstream
Overclockable to 1.5 GHz
Added VDD sysfs interface for userspace UV control
Stock Frequencies and Voltages
Default governor: INTERACTIVE @ 254 - 1024 MHz
Interactive governor updated from android 3.4 upstream
Default scheduler: DEADLINE
Configurable Sweep2Wake
Fixed WiFi tethering on Sense 4 based ROMs
Updated WiFi drvier from HTC One V source
Built-in CIFS support
Built-in TUN support
Built-in NTFS + NLS_UTF8 support
Optional WiFi calling
Two way call recording - both WAV and AMR
Enabled USB OTG HOST (big thanks to astro757 and engelmarkus)
Enabled SWAP support
ISSUES​
If your WiFi does not work upon install check this solution /10x to toxic-hero/
Sometimes the sweep2wake does not work instantly after deep sleep period. Just swipe once more to unlock the device or press the search button.
due to incompatibility with sweep2wake the native Sense screenshot function has to be disabled (on some ROMs Power+Volume Down is working- 10x to rzr09 for pointing it out). You will need to change the value of ro.htc.framework.screencapture = , located in /system/build.prop from true to false manually, using any root file explorer. To make it functional again (if you decide to disable s2w) just change back from false to true
For all with BLUETOOTH issues: use 4EXT Recovery
USEFUL INFORMATION, PLEASE READ​Overclocking applications, reported to work:
If you are in doubt which governor and IO scheduler to use - there is a lot of useful info here (thanks to Tectas and the authors)
SetCPU
Voltage Control {settings not stick after reboot on Virtuous Infinity}
No-frills CPU Control {settings not stick after reboot on Virtuous Infinity}
Daemon Controller app + andrev_oc script
note1: there is virtuous_oc on Virtuous Infinity already, so you can use only the Daemon Controller app
note2: oc daemons are not supporting scheduler changing
undervolting can be done with a command from Terminal Emulator or adb shell:echo -X > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels​where X is the desired value (-25, -50, -75, -100, -125 or whatever you like). Unfortunately has to be repeated after every reboot since putting it in an init.d script is risky
Originally posted by engelmarkusHi,
I played around with the experimental branch of your kernel once more and today it works perfectly.
Keyboards, mice and USB storage devices work without any messing with the terminal. For almost-auto-mounting I used this app here: https://play.google.com/store/apps/d....shajul.usbotg
So I think you can very well enable this in your next kernel version so others can try this out, too.​
DOWNLOAD AND INSTALLATION​Download: 3089.zip
md5sum: 921dda7817b33ee1b7730afca4c57e1c
S-OFF users: flash in recovery, no wipe required. Follow the instructions
HTCDEV users: flash in recovery, no wipe required; follow the instructions, reboot straight to bootloader and flash the corresponding to your ROM boot.img (extract it from the zip) with the following commands:adb reboot bootloader
fastboot erase boot
fastboot flash boot XXX_boot.img​IMPORTANT (HTCdev users): if you are using 4EXT Recovery Control for flashing make sure to select the "Stay in recovery after flashing" option!​
Boot images are:
Virtuous_boot.img - for any version of Virtuous Infinity
Sense4_boot.img - for other Sense4 based ROMs (Fallout, ProjectX, Cooldroid, Sabsa, Desire XS, ViperSaga, others)
Custom_Sense36_exp_boot.img - EXPERIMENTAL (New wireless driver, without issues in standby. Native WiFi tethering will be broken) - for ICE_DS, Blackout ICS, Stock ICS by masteross, or other custom Sense 3.6 ROM
Custom_Sense36_boot.img - STABLE (Old HTC wireless driver, may cause battery drain in stand-by. Working native WiFi tethering) - for ICE_DS, Blackout ICS, Stock ICS by masteross, or other custom Sense 3.6 ROM
Stock_Sense36_exp_boot.img - EXPERIMENTAL (New wireless driver, without issues in standby. Native WiFi tethering will be broken) - for Ice Cream Saga or clean RUU/PG88IMG (that keeps S-OFF and Recovery) install (rooted)
Stock_Sense36_boot.img - STABLE (Old HTC wireless driver, may cause battery drain in stand-by. Working native WiFi tethering) - for Ice Cream Saga or clean RUU/PG88IMG (that keeps S-OFF and Recovery) install (rooted)
MIUIv4_exp_boot.img - EXPERIMENTAL (New wireless driver, without issues in standby. Native WiFi tethering will be broken) - for any version of official MIUIv4
MIUIv4_boot.img - STABLE (Old HTC wireless driver, may cause battery drain in stand-by. Working native WiFi tethering) - for any version of official MIUIv4
Sense4_lib_boot.img - for recent versions of Desire XS or other Sense 4 ROM that is reodexed/with separate lib partition
If sweep2wake takes screenshot upon screen off in this version you have to modify your build.prop manually (see above)​
TWEAKED3 VERSION XI DISCONTINUED - reference only​
FEATURES​
Interactive Aroma Installer
Patched to Linux Kernel version 3.0.56
Added ck1 patchset by Ziggy (thx to Coolexe) - aims towards better performance
Compiled with the latest stable Linaro GCC 4.7.3-2012.11 toolchain
Overclockable to 1.5 GHz
Added VDD sysfs interface (10x to lowveld) for userspace UV control
Stock Frequencies and Voltages
Tuned ONDEMAND and INTERACTIVE governors
Tuned DEADLINE and SIO schedulers
ONDEMAND @ 254 - 1024 MHz and DEADLINE set as default
Enabled TINY_PREEMPT_RCU
Some tweaks and optimizations for better performance
Configurable Sweep2Wake
Fixed WiFi tethering on Sense 4 based ROMs (10x to m0narx)
Updated WiFi driver from the latest HTC One V source
Enabled CIFS and TUN support
Enabled NTFS + NLS_UTF8 support
Enabled PPP_ASYNC and PPP_SYNC_TTY
Two way call recording - works in AMR and WAV (10x to Andromadus) format with CallRecorder app by skvalex
CHANGELOG​
16 Dec 2012: Tweaked3 XI:
Compiled with the latest stable Linaro GCC 4.7.3-2012.11 toolchain
Patched to Linux Kernel version 3.0.56
Upstream update of interactive governor change speed routine
Enabled TINY_PREEMPT_RCU - should give small-memory-footprint on uniprocessor systems (where all processing tasks share a single CPU)
23 Nov 2012: Tweaked3 10.0 (X):
Patched to Linux Kernel version 3.0.52
Removed all third party governors
Removed BFQ, VR and CFQ schedulers
Tweaked SIO for better performance on Android
All modules built-in, except the one for WiFi Calling (kineto-gan.ko - optional)
No more init.d scripts, except for sweep2wake
During installation a /system/etc/init.d folder will be created, with the right permissions on ROMs that do not have such
09 Nov 2012: Tweaked3 9.0:
Compiled with the latest Linaro Toolchain 4.7.3-2012.10
Patched to Linux Kernel version 3.0.51 (10x to oliverclaude)
Ondemand and Interactive governors synced to upstream (10x to Andromadus)
Scheduler improvements (10x to faux123)
16 Oct 2012: Tweaked3 8.6:
Patched to Linux Kernel version 3.0.46
Updated BFQ code to v5 (10x to Andromadus repo)
2WCR now makes recording in WAV format (10x to Andromadus repo)
BCMDHD wireless driver is updated to the latest HTC One V source - there are some changes related to the Country Codes, so please anyone that has such issues to try it without WiFi FIx app and report
Initialization of the wireless modules moved to ramdisk, no need of init.d script to run them anymore, so new users can skip that part and go straight to flashing!
10 Oct 2012: Tweaked3 8.5:
Patched to Linux Kernel 3.0.45
Added ck1 patchset by Ziggy (thx to Coolexe) - aims towards better performance
Removed ZRAM - it seems that the compression was the reason for the battery drain
Removed the script for changing the screencapture line in build prop from Aroma, hopefully this will solve the installation issues. You will have to change it manually if needed
01 Oct 2012: Tweaked3 8.0:
Aroma installer - one file for all. No need to do any preparations anymore (like changes of the updater-script, etc) The installer will gather the important information about your ROM and hboot and the flashing process will be done accordingly.
HTCDEV users: there are instructions in the first post which boot.img to flash. Important: if you are using 4EXT Recovery Control for flashing make sure to select the "Stay in recovery after flashing" option!
All governors are tuned up according to the CPU frequencies (should have done it long time ago, sorry for the delay). OndemandX (proved unstable) and Userspace (doubt that anyone even uses it) governors removed
CIFS, TUN, KINETO_GAN, NTFS+NLS_UTF8 and ZRAM moved to modules for optional install (the installer will give you a menu for selection, where the purpose of each module is explained)
Updated LZO compression/decompression method for ZRAM (it sould be at least twice faster now)
TREE_RCU and SLAB memory allocator set as default (as it was in the Stock kernel).
21 Sep 2012: Tweaked3 7.1:
Patched to Linux kernel version 3.0.43
Compiled with the latest stable Linaro GCC 4.7-2012.08 toolchain
Added VDD sysfs interface (10x to lowveld) for userspace UV control (comes with Stock Voltages by default)
Added BrazilianWax, InteractiveX and OndemandX governors
All modules except bcmdhd.ko are built-in in the kernel
Finally found the reason of the battery drain when the Screen is ON and hopefully fixed it. Now the battery life should be rock solid
Flashable zips should be fixed for good. They now will wipe dalvik-cache and cache during flash, no need to do it manually. Version 5.0 zips are backwards compatible (this means you can flash version 5 over version 7.1 without additional actions (deleting or moving files)
05 Sep 2012: Tweaked3 6.0:
Added bcmdhd WiFi driver and fix WiFi Tethering on Sense 4 ROMs (10x to m0narx)
Flashable zips are back!
Comes is two flavors - undervolted -100 and Stock voltages
02 Sep 2012: Tweaked 5.0:
Built with Linaro toolchain
Patched to Linux Kernel version 3.0.42
Reverted to Stock Voltages due to some users complaints
SLUB is the default memory allocator
Added tun.ko module (use 51-modules init.d script to load it)
Added cifs.ko module (use 51-modules init.d script to load it)
Enabled full capacity charge in non-OEM chargers (e.g. some car chargers)
Enabled NTFS + NLS_UTF8 support
Enabled PPP_ASYNC and PPP_SYNC_TTY
Enabled ZRAM - adds another 100 MB to your RAM as a SWAP partition (use 52-zram init.d script to load it)
Enabled USB-OTG (needs confirmation, since I do not have the necessary equipment) - not working
27 Aug 2012: Tweaked3 4.7:
Expanded frequency table - to give the CPU more steps until the highest frequency
Slight undervolting to save some battery life
Fixed backlight staying on when pressing only home button when s2w with backlights enabled (10x to scan6 for the heads up)
Default clock frequency is 1024 MHz for everyone that requested it
Enabled init.d support in the MIUIv4 version (now you can use the 50-sweep2wake script too)
Separate installation files and instructions for S-ON (hboot 2.00.0002) and S-OFF (hboot 0.98.2000, 2.00.2002, 7.xx) users
25 Aug 2012: Tweaked3 4.0:
Patched to Linux Kernel version 3.0.41
Added sweep2wake configuration: default Enabled with no backlight
Added lionheart, lulzactive, intellidemand, scary, lagfree, lazy and savagedzen governors
Added BFQ and VR schedulers
Added Snapdragon optimizations
23 Aug 2012: Tweaked3 3.0:
Added Lionheart and Smartass2 governors
Added Simple IO Scheduler
Enabled ARCH_POWER
Disable GENTLE_FAIR_SLEEPERS
22 Aug 2012: Tweaked3 2.0:
Patched to Linux Kernel version 3.0.30
Added support for MIUIv4 and Virtuous Infinity
Source code published @github
21 Aug 2012: Initial release
Based on the released by HTC saga-ics-crc-3.0.16-62a67df source
Added Sweep2wake functionalit
Overclocked to 1,5 GHz
ISSUES​
due to incompatibility with sweep2wake the native Sense screenshot function has to be disabled (on some ROMs Power+Volume Down is working- 10x to rzr09 for pointing it out). You will need to change the value of ro.htc.framework.screencapture = , located in /system/build.prop from true to falsemanually, using any root file explorer. To make it functional again (if you decide to disable s2w) just change back from false to true
For all with BLUETOOTH issues: use 4EXT Recovery
USEFUL INFORMATION, PLEASE READ​Overclocking applications, reported to work:
If you are in doubt which governor and IO scheduler to use - there is a lot of useful info here (thanks to Tectas and the authors)
SetCPU
Voltage Control {settings not stick after reboot on Virtuous Infinity}
No-frills CPU Control {settings not stick after reboot on Virtuous Infinity}
Daemon Controller app + andrev_oc script
note1: there is virtuous_oc on Virtuous Infinity already, so you can use only the Daemon Controller app
note2: oc daemons are not supporting scheduler changing
undervolting can be done with a command from Terminal Emulator or adb shell:echo -X > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels​where X is the desired value (-25, -50, -75, -100, -125 or whatever you like). Unfortunately has to be repeated after every reboot since putting it in an init.d script is risky
DOWNLOAD AND INSTALLATION​Download: Tweaked3_XI.zip
md5sum: e9bf1393d48c6f7e7e8697e34ac63e7a
S-OFF users: flash in recovery, no wipe required. Follow the instructions
HTCDEV users: flash in recovery, no wipe required; follow the instructions, reboot straight to bootloader and flash the corresponding to your ROM boot.img (extract it from the zip) with the following commands:adb reboot bootloader
fastboot erase boot
fastboot flash boot XXX_boot.img​IMPORTANT (HTCdev users): if you are using 4EXT Recovery Control for flashing make sure to select the "Stay in recovery after flashing" option!​
Boot images are:
Virtuous_boot.img - for any version of Virtuous Infinity
Sense4_boot.img - for other Sense4 based ROMs (Fallout, ProjectX, Cooldroid, Sabsa, Desire XS, ViperSaga, others)
Custom_Sense36_exp_boot.img - EXPERIMENTAL (New wireless driver, without issues in standby. Native WiFi tethering will be broken) - for ICE_DS, Blackout ICS, Stock ICS by masteross, or other custom Sense 3.6 ROM
Custom_Sense36_boot.img - STABLE (Old HTC wireless driver, may cause battery drain in stand-by. Working native WiFi tethering) - for ICE_DS, Blackout ICS, Stock ICS by masteross, or other custom Sense 3.6 ROM
Stock_Sense36_exp_boot.img - EXPERIMENTAL (New wireless driver, without issues in standby. Native WiFi tethering will be broken) - for Ice Cream Saga or clean RUU/PG88IMG (that keeps S-OFF and Recovery) install (rooted)
Stock_Sense36_boot.img - STABLE (Old HTC wireless driver, may cause battery drain in stand-by. Working native WiFi tethering) - for Ice Cream Saga or clean RUU/PG88IMG (that keeps S-OFF and Recovery) install (rooted)
MIUIv4_exp_boot.img - EXPERIMENTAL (New wireless driver, without issues in standby. Native WiFi tethering will be broken) - for any version of official MIUIv4
MIUIv4_boot.img - STABLE (Old HTC wireless driver, may cause battery drain in stand-by. Working native WiFi tethering) - for any version of official MIUIv4
If sweep2wake takes screenshot upon screen off in this version you have to modify your build.prop manually (see above)​
Stock Sense GingerBread sweep2wake kernel​​
MIRROR @ DEV-HOST /all versions/:​
​
SOURCE CODE
​
Tweaked3 - experimenal branch
B2B - stable branch
Patched - linux branch​​
CREDITS​HTC for the source code
BIG thanks to m0narx for the WiFi Tethering fix!
showp1984 and his source for atmel touchscreen devices
mdeejay for some of the linux version patches
AdiPat for his repo
Coolexe for his repo
cjoliver for the sweep2wake switch and the recent upstream patches
crking for the sweep2wake init.d script
lowveld for his all great projects for HTC Desire S and the VDD sysfs
Ziggy for the ck1 patchset
Team Andromadus for their repo
astro757 and engelmarkus for the USB OTG HOST
All the great kernel developers @Xda For their great work​Thanks for testing and corrections:rzr09
dr.higgins
dont know
signfinder/dalexx
dmatik
TatoValverde
toxic-hero​Thanks for donating. Much appreciated:dont know
TatoValverde
petjoh​
XDA:DevDB Information
B2B |&| Patched, Kernel for the HTC Desire S
Contributors
amidabuddha
Source Code: https://github.com/amidabuddha/saga-ics-crc-3.0.16
Kernel Special Features:
Version Information
Status: No Longer Updated
Current Stable Version: BACK2BASICS EDITION
Stable Release Date: 2012-08-21
Current Beta Version: PATCHED KERNEL 3.0.8
Beta Release Date: 2013-08-06
Created 2015-02-24
Last Updated 2015-02-24

amidabuddha said:
Features:
- Sweep2wake functionality
- Overclocked to 1,5 GHz
Download: View attachment 1273069
md5sum: 98fe244bbfb430283f194e61031e0d7f
Issues:
- due to incompatibility with s2w the native Sense screenshot function is disabled
- do not use with the official MIUI v4, since it is not mounting /system/lib on init
Installation: flash in the Recovery
Click to expand...
Click to collapse
man you are the best!!

Installed on Nik Project, any issues with buttons backlight? It seems like they are always on

Nope,it works well to me
Nik project v4.1:
1.oc ---ok
2.s2w---ok
Sent from my HTC Desire S using xda app-developers app

Nik 4.1, have 3600 in anututu =)
Will try to reinstall with really full wipe, because my buttons are always on

mizerok said:
Installed on Nik Project, any issues with buttons backlight? It seems like they are always on
Click to expand...
Click to collapse
On Fallout the backlight works as it should.
In a room without direct sunlight - off
On screen off - off
Outdoor or in a dark place - on
Try in different conditions, maybe there is too much light where you are

I wish it was usable for non Sense ROMs

Nik 4.1, Atuntu - 3527
No prob with S2W. Auto brightenss is off.
Thx Stefan.

I get 3883 on antu with fallout rom
sent from my desire s from one of lowvelds roms

docertabum said:
I wish it was usable for non Sense ROMs
Click to expand...
Click to collapse
Working on it more or less ^^
Great done amidabuddha
Gesendet von meinem GT-I9300 mit Tapatalk 2

I am not a big fan of benchmarking. But tried just out of curiosity.
Antutu: 4035 on Fallout
Sent from my HTC Desire S

It's perfect! I haven't seen so cool and fast rom as fallout with this kernel yet!

Is it not harmful for Desire S to overclock to 1.5 GHz ?

Shouldnt make any harm going to 1.5.
Now the kernel source, is https://github.com/showp1984/bricked-shooteru-ics-sense what you releasing? if no you need to release the exact kernel source you using, laws
I dont want any saga dev to have issues
Edit:
More then that, some devices comes with stock 1.5 with same processor but remember, the more you put, the less battery

Hi, is there a way to revert it to stock? Thanks.
Sent from my HTC Desire S using xda app-developers app

superkid said:
Shouldnt make any harm going to 1.5.
Now the kernel source, is https://github.com/showp1984/bricked-shooteru-ics-sense what you releasing? if no you need to release the exact kernel source you using, laws
I dont want any saga dev to have issues
Edit:
More then that, some devices comes with stock 1.5 with same processor but remember, the more you put, the less battery
Click to expand...
Click to collapse
Good point
Yes the changes for sweep2wake are the same, made by showp1984, unmodified by me
And yes, this is the stock OC, I have just enabled it for the time being.
I am pretty sure that soon there will be much more tweaked and polished kernels made by the experienced devs, but since most of them are taking summer holidays I compiled this one for playing with Sense 4 until they come back to development

Dreamtheater2003 said:
Hi, is there a way to revert it to stock? Thanks.
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Yes you can always flash the original boot.img of the ROM that you are using via fastboot. Then copy the bcm4329.ko and kineto_gan.ko of your original ROM to /system/lib/modules with any root file explorer. To restore the stock screenshot feature change the value ro.htc.framework.screencapture from false to true in your build.prop

Dreamtheater2003 said:
Hi, is there a way to revert it to stock? Thanks.
Click to expand...
Click to collapse
flash the rom once again...

masterross said:
Nik 4.1, Atuntu - 3527
No prob with S2W. Auto brightenss is off.
Thx Stefan.
Click to expand...
Click to collapse
Nik Project X v4.1 with AnTuTu - 3907
sdcard: class6

wifi not working after flashed this oc file.....why?

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

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

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

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

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

\o/ Thank you and good luck!

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel][LU650137] Icaros Kernel 1.2 Update 04

Hello Everyone!
My name is Icaros7 ([email protected] / [email protected])
Kor Ver. Post on cafe.naver.com/optimusq2life/12143
It's a Custom Kernel for LG-LU6500 137 F/W
This is very low. But is expected to continue to be update!
Feature
+ Update 04
- zRAM, zCache Supprot
- Add sakuractive, pegasusq, ondemandx Governer
+Update 03
- Add Some Governer
- Show Charging Animation Bug Fixed
- Delete Temp Files on RAMDISK
- Add cfq I/O Governer
- Add 750Mhz
- Edit Touch LED UV (Thanks to 백원만)
- CWM Update zip Script Edit
+ Update 02 / 01
- Add Lazy, Minmax, SmartassV2, Powersave
- Delete Some governer
- GPU OC Fixed (Thanks to 백원만)
- init.d Apply Bug Fix
- Add Voltage Settings
- Add deadline / sio I/O Governer
- Add about 100MB RAM ensure available (Thanks to 백원만)
- LG OpenSource's Battery Temple Bug Fix (Thanks to 백원만)
- LG OpenSource's Plug USB Bug Fix (Thanks to 백원만)
How to Install
1. Go to CWM Recovery (Use App or Power + Vol. UP)
2. Select Install zip form sdcard
3. Select Install zip form (internal) sdcard (if you download in internal sdcard, select internal sdcard)
4. Select icaroskernel_build20_lu6500_update04.zip
5. Select Yes
Download
Mediafire : mediafire.com/?fp6jrc0ut941n41

[KERNEL][STOCK 4.4.2][D295] KitKatExtended Kernel for L Fino

I compiled this kernel using linaro 4.8 toolchain from official LGE-D295 kernel sources and adding these some features:
Added CPU underclock to 249 & 192 Mhz (default CPU freqs is 0.3-1.2 GHz, so you need to set up underclock in Kernel Auditor)
Added support for FAST CHARGE function (disabled by default - for enable use Fast Charge)
Default governor changed to ondemand
Default I/O sheduler changed to CFQ
Added new CPU governors: interactive, conservative, pegasusQ
Added some new I/O shedulers: BFQ, SIO, SIOPLUS, FIOPS, FIFO, VR, ZEN.
Information:
Developer: Nikita Pro Android
Tester: kubarek777 (4pda)
Kernel version: 3.4.10
Device model: D295
ROM: STOCK 4.4.2
Installation:
1. Download and put to storage: >>>LINK<<< (v1.0)
2. Go to recovery and wipe cache.
3. Flash downloaded .zip and reboot.
4. Reboot again!
5. This is all.
To set up CPU frequency and another kernel parametres use: Kernel Auditor
Source code: https://github.com/NikitaProAndroid/android_kernel_lge_msm8610_l70pds/tree/master

Nikita Pro Android said:
[/HIDE]
Installation:
1. Download and put to storage: []>>>LINK<<< (v1.0)[]
2. Go to recovery and wipe cache.
3. Flash downloaded .zip and reboot.
4. Reboot again!
5. This is all.
Click to expand...
Click to collapse
The link not available, new link please..