[imoseyon (OP)]

View Source

Mod Type: Kernel	Difficulty: Very Easy	Mod Status: Stable	Mod Base:	Carrier:
Requires Root: Yes	Apply In: CWM Recovery	Optional:	Optional:	Android Version:

This is a minimalistic Galaxy Nexus kernel. My philosophy is to keep the kernel as lean and stable as possible, at the same time to keep the kernel as modern and close to latest mainstream linux as possible. You will see that my kernels will lack a lot of the bells and whistles from other kernels.

Download

• For 4.0.3/4.0.4 ICS: stable
  
• Experimentals & notrim builds:
  
  • link to latest 180mhz
    
  • link to latest 230mhz
    
  • all files
    
  • commit/change log (always up to date)
• 4.0.4 76d stock kernel, 4.0.4 76i stock kernel (note these are not leanKernel - this is from google)
  
• 4.0.4 vanilla ROM for toro/vzw (built by birdman, includes stock kernel, repackaged by me with some fixes - dict, build.prop, su, busybox)

If you lost su/root on Axiom read here: http://rootzwiki.com...100#entry597694, and a flashable zip from Droidtheory.
Feature requests? Post it here: http://www.imoseyon....l-features.html

Three Builds

• 1) stable
  
• 2) experimental 180mhz: 180mhz to 1.65ghz
  
• 3) experimental 230mhz: 230mhz to 1.65ghz
  
• Note experimental builds will have the following features in addition to the extra freq slots: notrim + vibe control + SIO scheduler default + tcp_veno default + hotplugx optimization for high freqs.

FEATURES

• Patched to latest in Linux 3.0.x branch: 3.0.31.
  
• All unnecessary kernel components removed to make kernel lean and fast!
  
• OC to 1.35Ghz (stable, 1.65ghz for exp). Boot speed is maxed at 1.2ghz within kernel (in addition to ramdisk) for stability.
  
• User voltage control (Michael Huang, fixed and enhanced by me).
  
• InteractiveX V2 (screen-off hotplug of cpu1) added. Select it using setcpu if you want to use it.
  
• Ramdisk tweaks (sysctl, vm, filesystem speed, etc.)
  
• SWAP & zram (next generation compcache) support. Run "zram enable" in terminal.
  
• init.d support in ramdisk.
  
• HotplugX governor (Hotplug optimized and modified for screen-off suspend).
  
• cpufreq backport from Linux 3.4rc
  
• rcu code backport from Linux 3.3
  
• wakelock tweaks for wlan and lte modem
  
• other linux 3.2/3.3 backports: dm, futex, voltage regulator, memory compaction, etc.
  
• Undervolted by default (1.35ghz/1325, 1.2ghz/1300, 920mhz/1250, 700mhz/1150, 350mhz/950)
  
• lkflash - script to flash latest versions of leanKernel from Terminal (type "su" without quotes, hit enter, then type "lkflash" without quotes and then hit enter)
  
• checkv - voltage checking script (for custom undervolting) - detailed at bottom of this post.
  
• checkt - script that displays 1) your current temp, 2) # of times you were throttled due to temp "recently", 3) CPU trim type, and 4) CPU silicon type. (sample output)
  
• Fast USB charge (by chad0982) and "ffc" toggle script by me. (Open terminal, and type "ffc" without quotes then enter)
  
• ColorControl from both CM9 and Ezekeel (compatible with all ROMs). Helpful posts: 1and 2.
  
• TempControl - sysfs interface to control the CPU temp threshold. Read these two posts: 1 and 2.
  
• Variable GPU OC - sysfs interface to select GPU max speed between 307MHz (stock), 384MHz and 512Mhz. The changes take effect immediately. Check FAQ for more info and how to use it.
  
• Custom SR Tuning - override kernel default minimum voltage for SR calibration. More info here and here.
  
• SoundControl
  
• Gamma Control

CHANGELOG
(* next to version indicates versions that were general regarded as rock stable)

• v1.0.0 - Initial release
  
• v1.0.1 - Fixed power off charging (only upgrade if you care about that).
  
• v1.1.0 - rcu code updated to linux 3.2-rc7, boot speed max forced to 1.2ghz within kernel (stability), hotplug governor should be more stable now, zram enabled including custom enable script (run "zram enable" in terminal), small bug fixed in voltage control code.
  
• v1.2.0 - interactiveX V2 with hotplug support, user undervolting works now, and all speeds undervolted by default (clear setcpu settings before flashing), ALSA SoC driver updated to 3.2-rc7
  
• v1.2.1 - reverted a dep voltage change I made in 1.2.0. Only update if you're experiencing stability issues in 1.2.0 (if your coming directly from a version prior to 1.2.0 make sure you clear custom voltage settings)
  
• v1.3.0 - re-wrote a lot of my user undervolting code (fixed some bugs and probably introduced others - haha), updated dm and futex code to linux 3.2, gpu undervolt at top speed, some code cleanup. (clear setcpu settings before flashing). Oh one more thing: undervolting 1.35ghz and higher is not reliable yet and is not recommended.
  
• v1.4.0 - updated to Linux 3.0.15 (small release), voltage regulator driver from Linux 3.2, omap clock data updated from latest official omap source.
  
• *v1.5.0 - updated to Linux 3.0.16 (big update), more accurate/reliable user voltage control for frequencies less than 1.35ghz.
  
• v1.6.0 - read this post.
  
• v1.6.1 - *battery drain - being fixed*, updated to Linux 3.0.17, fixed potential memleak in slub allocator, small omap4 update from android-omap source.
  
• v1.6.4 (pulled - stay tuned) - moved some of the features off of 1.6.1 (but kept them in experimental) in order to fix/pinpoint potential source of battery drain possibly introduced in 1.6.1. You do not need to upgrade from 1.6.1 if it's working fine for you. Cpufreq updated to Linux 3.3.
  
• v1.6.6 (bd0730ad3f57e050942356b647821256) - Fixed pm_suspend bug introduced by the Linux 3.0.17 patch *this fixes battery drain issue in 1.6.1 and 1.6.4*. Where's 1.6.5?
  
• v1.7.0 (a7f3d241d68fd48c9f216e8399226e9d) - a bunch of fixes and updates from android-omap source including the hotplug fix, deadline scheduler updated to linux 3.2.
  
• v1.7.1 (c2d0d4c59c198bb3f2281f164442ac0f) - removed some omap patches from 1.7.0 that may have been causing issues.
  
• v1.7.3 (049a8ce4be0f0a392d6c0b694de1ad73) - went back to 3.0.16 base as I suspect there were more things in 3.0.17 causing subtle issues in releases newer than 1.5.0. Added a fix to reduce screen unlock lag in interactiveX. Brought back some of the OMAP patches from upstream android-omap source.
  
• *v1.7.4 (3619144bee4cd86883692b48971ee5f8) - applied the rest of OMAP patches from android-omap source. Partially updated to 3.0.17. Wireless ADB support (if ROM has built-in support for it).
  
• *v1.8.0 (7ddb6ac13d01ceaeed25b83ab13afb8c) - Updated to Linux 3.0.18 (big update - lots of fixes/changes). An omap driver fix. A fix for stalling RCU processing. Ramdisk changes for CM9 (or CM9 based ROMs) compatibility. This version should theoretically be smoother than the previous versions.
  
• v1.9.0 (f703a8912d4dd19f82cc4bf17f37f1cd) - detailed log here.
  
• *v1.10.0 (e9f2c4f2b458ddddeebfba842bb51756) - updated to Linux 3.0.20, completely modernized memory management compaction/migration code to Linux 3.3-rc3 (which also includes backporting much of the mm code)
  
• v2.0.0 (a6a518d0a243c071ef6c02445acf2645) - detailed log here.
  
• v2.0.1 (d9457f5fd0d9a74bc1c7fe37e1856907) - custom UV related issues (haptic feedback, volume, etc.) fixed. Custom UV code improved.
  
• v2.1.0 (3362b0879e8a11681dc3e78eef38e4aa) - detailed log here.
  
• v2.2.0(41296a907dd27cbc25593dbbda0e7fe0) - detailed log here.
  
• v2.3.0 (c024897dd55ec4789fb998adb957a855) - detailed log here.
  
• v2.4.0 (6e528aa35a51fc526939be2d51b4c295) - detailed log here.
  
• v2.4.1 (be8d706f851b2700e035b8bd49abe27c) - detailed log here.
  
• *v2.5.0 (793c7be3b35ab35beef3fa1797405378) - ColorControl, TempControl, ext4 optimizations
  
• v2.6.0 (dc015f7c87ac5282ed1693063bd8a24a) - detailed log here.
  
• v2.7.0 (a0a1b5c5de6ae103ce1cbf852fb8990d) - detailed log here.
  
• v2.7.1 (a87b733e31aa9b7a0c447a76f2b5c708) - ColorControl modified to support CM9/AOKP interface as well. (no need to upgrade from 2.7.0 if you don't use colorcontrol)
  
• v2.7.2 (e4d355c0e54ac5c3cbf5b9123e12eb9f) - ramdisk modified for better cm9/aokp compatibility, and better init.d support. Also includes "board" script for detailed board/soc info.
  
• *v2.8.0 (5b3b31519133cebe67348b76ae349bc8) - detailed change log here.
  
• v3.0.0 (0647d8590403eb4921f7f148216841ae) - Merged AOSP 4.0.4 kernel/ramdisk source.
  
• v3.1.0 (7064aec889d9ce92d380090d7ed0b3aa) - changelog
  
• v3.2.0 (8c41c4de4b0a62cdeee89686405401a5) - changelog
  
• v3.2.1 (30190db201f6dcabe318e26c0312c1d2) - reverted omap SR patch that prevented undervolting, interactive (and iX) tuned for extra power saving when screen is off.
  
• v3.2.2 (1d6df86cb5fe6c1644f16d847abdbe85) - reverted a few patches from 3.2.1 to address a few cases of instability, a small colorcontrol fix, small timed_gpio fix.
  
• *v3.3.0 (137955e83ca267b10d2b74dbdf360f99) - changelog
  
• v3.4.0 (9b5f99954de4bbbca01e4701fa04037c) - changelog
  
• v3.5.0 (06ceb50e1155293f86bf4c1e4469fc89) - changelog
  
• *v3.6.0 (3fa30f43a8c0e2439d32b10a0f10f376) - changelog

DIRECTIONS
Uh.... flash the zip in clockworkmod.

FAQ

SOURCE
lk-stable

Thanks to forum member maddler for providing file hosting: http://www.host4droid.com/

Third party mods (not tested by me so use at your own risk)

• Jakes lean tweaks.

Donate to your favorite charity, or donate to me.

Edited by imoseyon, 14 May 2012 - 07:45 AM.

[droidth3ory]

Hey IMO... Good to see you around again man.



Sent from my Galaxy Nexus using Tapatalk

[imoseyon (OP)]

FAQ

How do i change voltage? - Use the latest version of setcpu, leantweaks, cputuner, or your ROM's built-in tools.

Do i need to wipe dalvik/cache? - in general there's no need, but it doesn't hurt so if you have time go ahead. I don't wipe.

​Can we OC higher or add more frequency slots? - You can find the extra slots in my experimental versions.

​Will this work on GSM gnexus as well? - It should. I don't have a GSM phone to test so let me know if it stops working.

What is interactiveX V2? Read this post and this post.

Are you getting Screen-Off/Sleep-Of Death (SOD), general instability, or unusual battery drain?

• Before you post here (especially if you're running the experimental version), try the following steps in order:
  
• 0) dude, disable screen-off profiles if you're running interactiveX.
  
• 1) If you're running the experimental version, do you have 180mhz/230mhz and/or 1.42ghz slots enabled? If so disable them both!
  
• 2) If the above doesn't help, do you have custom undervolting enabled? If so disable it! (keep in mind that the kernel is already undervolted by default).
  
• 3) If the above doesn't help, are you using interactiveX or hotplug governors? If so change to interactive.
  
• 4) If the above doesn't help then you should not be running the experimental version. Install the stable version and try both interactiveX and interactive without custom undervolting.
  
• If you're still getting SOD with stable/interactive, report it here.

What about call-recording? - First the app needs to support Galaxy Nexus. Find out if it does and then find out from the author of the app what kernel changes are required and let me know.

Should i set up screen-off profile? - ICS kernels have built-in screen-off profile for all governors at 700mhz. So you don't need it unless you want to set it lower than 700mhz. In general there isn't a whole lot to gain by setting it lower.

Hotplug vs interactiveX? - Read this post. HotplugX vs interactiveX

What is zram and why do i need it?

• zram basically takes a portion of your RAM (10% using my script) and turns it into a compressed swap device. So in layman's terms you're extending the size of your memory (potentially from ~700mb to close to 1000mb depending on the compression ratio).
  
• To answer the 2nd question, no you don't really need it but if used properly (using my zram script) it could help you in two different ways: 1) Android OS is based on Linux OS and the OS will try to use a growing portion of your RAM for file and inode caches and if you keep your phone up without rebooting after a while you may notice things getting a little sluggish. That's because the OS is not doing a good job in dropping the caches and freeing up memory for the apps. 2) more RAM and tweaked minfree (also handled by my script) could potentially allow your apps to stay in memory longer (this may or may not be desirable based on your preference of course).
  
• In conclusion, I'd say if you're curious it doesn't hurt to try. :) To revert, just type "zram disable".

What's the low-down on the GPU OC?

• My kernel's GPU is now set to stock 307Mhz by default. You can adjust that by using Variable GPU OC (see a separate FAQ entry below).
  
• When you go from say 307 to 512Mhz, you will not experience near double performance increase. Due to the factors outside the GPU module (ie. memory bandwidth limitation), you can't truly OC the GPU. In fact, most people can't tell the difference between 307, 384 and 512. Nenamark2 will roughly give you the following scores: 307/25fps, 384/28fps, and 512/31fps.
  
• Some of you have seen the note from Colin, the Google kernel engineer, not to OC the GPU because using the OV_UV voltage slot will drain the battery. My kernel uses the same voltage for both OV and OV_UV slots. So there's no danger of battery drain there.

Why are the IO benchmark test scores lower than another kernel?

• Some of the kernels out there have fsync disabled to increase benchmark scores. I believe that is unsafe and could cause data corruption. I do have hooks in my kernel to disable it but I don't use it.
  
• In real world there will not be any user perceivable difference whether you have fsync enabled or disabled.

Is there a way to tune hotplug via sysfs?

• yes. Advanced users only!

My phone doesn't seem to be deep-sleeping, what gives?

• (assuming you checked in the right place like cpuspy) In terms of deep-sleep, there's not a whole lot going on in the kernel. It works or it doesn't - and I can assure you that I test every release (well almost every release) for deep-sleep before I release.
  
• 19 out of 20 times it's either 1) some sort of background process that's preventing your phone from going into deepsleep, or 2) something's misconfigured in your ROM, or both. Also connecting to USB will prevent phone from going into deepsleep.

I'm having unusual battery drain - help!

• First of all, our gnex has very poor battery life while in active use. It's downright horrible while screen is on - screen is definitely the main culprit and there's not a whole lot I can do about that.
  
• Custom undervolting can help or can hurt. This is mainly due to SmartReflex (class1.5) which auto-calibrates the ideal voltages for you. In fact, with SR you don't really need to use the custom undervolting feature for frequencies other than the 2 lowest. It does a great job calibrating higher frequencies. I personally don't touch it.
  
• The "notrim" versions are an exception because I had to disable SR1.5 for the trim override to work. There's no auto-calibration going on there. Feel free to mess with custom undervolting on the notrim versions.
  
• Now, if you've already accepted the horrible battery life while screen is on, but have questions about battery drain while idle - read the next question.

I'm having unusual battery drain while screen is off, or phone is sleeping - help!

• First, let's find out if you're phone is going into deep-sleep. Install CPUSpy, unplug phone, turn off screen, and leave the phone alone for 5-10min. Turn the screen back on, launch CPUSpy, and see if you see an active entry for Deep Sleep. If so congratulations - read on.
  
• If you've determined that your phone is not entering deepsleep by using the above method, read my entry above that says "My phone doesn't seem to be deep-sleeping". I've heard that removing SDM.apk helps as well as rebooting the phone. Also try turning your bluetooth on and off, and launching camera app and closing it.
  
• If you've determined that your phone is entering deepsleep fine but still feel like battery drains, read the next question.

I'm having unusual battery drain while phone is in deep-sleep - help!

• First make sure you are absolutely positive that deep sleep is working (read the previous question).
  
• While on my kernel *and* connected to Wifi, you shouldn't drain more than 1% battery per hour *average* while in deep sleep (based on 5-8 hour continuous deep sleep). With wifi turned-off, my guess is probably no more than 1-3% per hour, depending on signal strength.
  
• tip 1: If above is not happening for you, first charge the phone all the way and reboot. Let things settle a bit - give it a day or so. If you're using Battery Monitor Widget (which is not accurate for gnex), things should eventually settle between -2mA and -60mA per sample.
  
• tip 2: Install BetterBatteryStats and look at which wakelocks dominate. Google search for names of the wakelocks to see how you can fix them.
  
• tip 3: http://checkthis.com/d87t
  
• If nothing seems to help, you can try the "notrim" version, but stick to speeds between 350 and 1350 (don't use OC slots). The notrim version has SR1.5 disabled which could help for those of you with drain issues on my other kernels.

What is tempcontrol and how do I use it?

• First, read these two posts: 1 and 2.
  
• Although tempcontrol was designed to be used with the experimental notrim builds because the cpu gets hotter in notrim frequencies, you can actually use tempcontrol to throttle lower frequencies. I haven't tried myself, but theoretically you can set your top speed at say 1.2Ghz and use tempcontrol to throttle at say 60C (instead of the stock value of 63C) resulting in slightly cooler phone. Theoretically. :)

What is SmartReflex?

• SmartReflex performs continuous dynamic voltage scaling around the nominal operating point voltage according to silicon characteristics and operating conditions.
  
• My stable and experimental builds will have SR Class 1.5 enabled by default.
  
• You can disable SR via sysfs: http://rootzwiki.com...210#entry631996

How do I use Variable GPU OC?

• You can use Lean Tweaks by Jake, or use the built-in "oc" script. Both leantweaks and my oc script will create an init.d script so the setting sticks at boot. My "checkt" script will also show the current GPU max speed. Note that 512MHz will probably not work for everyone.
  
• 307Mhz (stock) is set default by the kernel.
  
• Open Terminal, and type for stock speed of 307Mhz: oc gpu 0
  
• for 384MHz: oc gpu 1
  
• for 512Mhz: oc gpu 2

What are the available sysfs options?

• Check this post (thx byrong)

Edited by imoseyon, 29 April 2012 - 08:49 AM.

[Zomb!e]

Loved your work on the TBolt. Thanks for the work and getting this out to us. Can't wait to flash it.

[Benny879]

Development for this phone is off the hook. Loved your kernels on the T-Bolt and happy to see you here imoseyon. Loading this up right now.

[Jgrimberg1979]

imoseyon, on 23 December 2011 - 07:12 PM, said:

This is a minimalistic LTE Galaxy Nexus kernel.

Download
For 4.0.3 ICS: here

FEATURES

• Patched to latest in Linux 3.0.x branch: 3.0.14, which was released 12/21/11 (lots of new/updated kernel code).
  
• All unnecessary kernel components removed to make kernel lean and fast!
  
• OC to 1.35Ghz (Michael Huang).
  
• GPU overclock (Michael Huang).
  
• Voltage control via setcpu (Michael Huang).
  
• Ramdisk tweaks (sysctl, vm, etc.)
  
• SWAP support.
  
• init.d support.
  
• Hotplug governor tweaked for stability.
  
• cpufreq backport from Linux 3.2

CHANGELOG

• v1.0.0 - Initial release

DIRECTIONS
Uh.... flash the zip in clockworkmod.

Donate to your favorite charity, or donate to me.

imoseyon,

I am stoked that you are joining us. I always used your kernels for the tbolt and I will definitely be using them for the gnex !

Sent from my Galaxy Nexus using Tapatalk

[evilmunkeh]

Zomb!e, on 23 December 2011 - 07:14 PM, said:

Loved your work on the TBolt. Thanks for the work and getting this out to us. Can't wait to flash it.

+1 I loved your AOSP and Sense Kernels. Glad you're working on the GNex!

[joemagistro]

sweet.. i forgot what rom it was that i had with your kernel, but i loved your work on the TB!!! i want that kernel again, but cant find it nowhere... it was clocked at 1.4 ghz

[SOTK]

Is this kernel any different than the one you released on twitter last night and the one which was packaged with GummyNex? I had a freeze using 1.35 as well as 1.2. I had to pull the battery on each instance. I was in people app on the first one and on tapatalk on the second. I was undervolting. Also, I was using hotplug governor. FYI

Sent from my Galaxy Nexus using Tapatalk

[amoeller]

Oh god yes. I love these lean kernels.