[Kernel][JB & ICS] Leankernel: Minimalistic Kernel (ICS 3.10.0, JB 4.2.0 , 7/23/12)

Search This thread
By:
Advanced…
B

beatles420

Member
Oct 16, 2010
24
3
I was using it on nitro's eclipse rom build 4. After a day or two System UI kept randomly force closing and I started getting random reboots.

Build 4 is 4.1.2 though, so that may be why.

Sent from my Galaxy Nexus using Tapatalk
 
a1exus

a1exus

Senior Member
Jun 4, 2008
1,056
65
NYC
alexus.org
I keep getting following message:

Code: 
E/Tuna PowerHAL(  345): Error opening /sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq: No such file or directory

do I need to do something?
also while boot I got following


Code: 
D/libsuperuser( 2297): [libsuperuser][SU%] START
D/libsuperuser( 2297): [libsuperuser][SU+] echo 2004318071 2004318071 2004318071 > /sys/class/misc/colorcontrol/multiplier
D/libsuperuser( 2297): echo 0 0 0 > /sys/class/misc/colorcontrol/v1_offset
D/libsuperuser( 2297): echo interactivex > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
D/libsuperuser( 2297): sysctl -w net.ipv4.tcp_congestion_control=westwood
D/libsuperuser( 2297): echo 1 > /sys/module/sync/parameters/fsync_enabled
D/libsuperuser( 2297): echo 1 > /sys/module/omap_temp_sensor/parameters/throttle_enabled
D/libsuperuser( 2297): echo 0 > /sys/devices/tegradc.0/smartdimmer/enable
D/libsuperuser( 2297): echo null > /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay
D/libsuperuser( 2297): echo null > /sys/devices/system/cpu/cpufreq/interactive/boost
D/libsuperuser( 2297): echo null > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
D/libsuperuser( 2297): echo null > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
D/libsuperuser( 2297): echo null > /sys/devices/system/cpu/cpufreq/interactive/input_boost
D/libsuperuser( 2297): echo null > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
D/libsuperuser( 2297): echo null > /sys/devices/system/cpu/cpufreq/interactive/timer_rate
D/libsuperuser( 2297): echo null > /sys/devices/system/cpu/cpufreq/interactive/input_boost_freq
D/libsuperuser( 2297): [libsuperuser][SU-] net.ipv4.tcp_congestion_control = westwood
D/libsuperuser( 2297): [libsuperuser][SU*] sh: <stdin>[5]: can't create /sys/module/sync/parameters/fsync_enabled: No such file or directory
D/libsuperuser( 2297): [libsuperuser][SU*] sh: <stdin>[6]: can't create /sys/module/omap_temp_sensor/parameters/throttle_enabled: No such file or directory
D/libsuperuser( 2297): [libsuperuser][SU*] sh: <stdin>[7]: can't create /sys/devices/tegradc.0/smartdimmer/enable: No such file or directory
D/libsuperuser( 2297): [libsuperuser][SU*] sh: <stdin>[8]: can't create /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay: No such file or directory
D/libsuperuser( 2297): [libsuperuser][SU*] sh: <stdin>[9]: can't create /sys/devices/system/cpu/cpufreq/interactive/boost: No such file or directory
D/libsuperuser( 2297): [libsuperuser][SU*] sh: <stdin>[10]: can't create /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load: No such file or directory
D/libsuperuser( 2297): [libsuperuser][SU*] sh: <stdin>[11]: can't create /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq: No such file or directory
D/libsuperuser( 2297): [libsuperuser][SU*] sh: <stdin>[12]: can't create /sys/devices/system/cpu/cpufreq/interactive/input_boost: No such file or directory
D/libsuperuser( 2297): [libsuperuser][SU*] sh: <stdin>[13]: can't create /sys/devices/system/cpu/cpufreq/interactive/min_sample_time: No such file or directory
D/libsuperuser( 2297): [libsuperuser][SU*] sh: <stdin>[14]: can't create /sys/devices/system/cpu/cpufreq/interactive/timer_rate: No such file or directory
D/libsuperuser( 2297): [libsuperuser][SU*] sh: <stdin>[15]: can't create /sys/devices/system/cpu/cpufreq/interactive/input_boost_freq: No such file or directory
D/libsuperuser( 2297): [libsuperuser][SU%] END
 
M

magnethart

Senior Member
Jul 16, 2010
76
17
Tampa, FL
SahilC said:
Anyone tested the 4.2 kernel? (just trying to revive this thread :p)

Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse

Was reading over on Rootzwiki that this has not been updated to run on a 4.2 ROM yet. Flashing it will cause some pretty serious boot issues. If you are looking for one that seems to have gotten high recommendations, try the Tiny2.0 kernel. I've been running it myself with MMuzzy 4.2 and it's good and stable.
 
rynosaur

rynosaur

Senior Member
Nov 29, 2008
765
28
Dekalb
Faux123's beta 23b10 "tuna" works perfectly with MMuzzy's 4.2 ports. Better still, it offers overclocking and multiple governor choices. As far as I've seen, it also improves compatibility with android apps that aren't optimized for 4.2. Win-Win :)


http://faux.androidro.ms/tuna/beta/


Sent from my Galaxy Nexus using Tapatalk 2
 
jonstrong

jonstrong

Senior Member
Jan 20, 2012
1,790
719
www.jonathanrstrong.com
Travisdroidx2 said:
On rootz I found lean kernel does support 4.2 it is his 5.00rc3 kernel. Been using it on eclipse 3.0 which is 4.2 and it is running great :)
Click to expand...
Click to collapse

Can you please post a link to the page on rootz that has this? I haven't seen any versions of lean for JB past 4.5.0 exp4. Not familiar with "5.00rc3", and can't find any references to a leanKernel with this numbering aside from your posts about it... Very curious about this. Thanks...
 
You must log in or register to reply here.

Similar threads

franciscofranco
[KERNEL] [GPL] [GN] franco.Kernel r398
Replies
45K
Views
8M
C
Ctzokas
ak
[KERNEL] [TUNA] [3.0.80+] [4.2.x] [SKL v256 - KUBO r50^] [30/05] AK
Replies
32K
Views
3M
S
Sik-1
boype
[KERNEL] Fancy Kernel r60 [Android JB+KK] [F2FS/EXT4] [Linux 3.0.101+] [OCT-24-2014]
Replies
10K
Views
2M
rahimali
rahimali
morfic
[KERNEL] Trinity 4.3 / 4.2.2 [KWISATZ HADERACH]
Replies
29K
Views
3M
Clark Joseph Kent
Clark Joseph Kent
Romanbb
  • Locked
[ROM] Android Open Kang Project - maguro - JB
Replies
15K
Views
3M
Mikey
Mikey

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 25
    B
    BusyPooping
    [Kernel][JB & ICS] Leankernel: Minimalistic Kernel (ICS 3.10.0, JB 4.2.0 , 7/23/12)

    Mod Type:: Kernel

    Difficulty:: Very Easy

    Mod Status:: Stable

    Apply In:: CWM Recovery

    Requires Root:: Yes

    Source::
    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 some of the bells and whistles from other kernels.

    DOWNLOADFEATURES
    • Patched to latest in Linux 3.0.x branch: 3.0.38.
    • All unnecessary kernel components removed to make kernel lean and fast!
    • OC to 1.65ghz. Boot speed is maxed at 1.2ghz within kernel (in addition to ramdisk) for stability.
    • User voltage control
    • 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.
    • lk.conf for basic kernel configuration.
    • HotplugX governor (Hotplug optimized and modified for screen-off suspend).
    • wakelock tweaks for wlan and lte modem
    • 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, etc. (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. V2
    • SoundControl
    • Gamma Control

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

    FAQ

    SOURCE
    ICS
    JB

    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)Donate to your favorite charity, or donate to me.
    View
    6
    B
    BusyPooping
    threepio said:
    Im curious to know which governor will provide the best battery savings? Ive always been confused about governors. Currently have mine on hotplug.
    Click to expand...
    Click to collapse

    Updated thread with links to latest stable build.

    Also, here is some info on governors. Its not all completely up to date, but this is a good read.

    LiNK


    1. GOVERNORS

    I) MANUAL:

    These are the 18 governors we're talking about.

    1) Ondemand
    2) Ondemandx
    3) Conservative
    4) Interactive
    5) Interactivex
    6) Lulzactive
    7) Smartass
    8) SmartassV2
    9) Intellidemand
    10) Lazy
    11) Lagfree
    12) Lionheart
    13) LionheartX
    14) Brazilianwax
    15) SavagedZen
    16) Userspacce
    17) Powersave
    18) Performance


    1) Ondemand:
    Default governor in almost all stock kernels. One main goal of the ondemand governor is to switch to max frequency as soon as there is a CPU activity detected to ensure the responsiveness of the system. (You can change this behavior using smooth scaling parameters, refer Siyah tweaks at the end of 3rd post.) Effectively, it uses the CPU busy time as the answer to "how critical is performance right now" question. So Ondemand jumps to maximum frequency when CPU is busy and decreases the frequency gradually when CPU is less loaded/apporaching idle. Even though many of us consider this a reliable governor, it falls short on battery saving and performance on default settings. One potential reason for ondemand governor being not very power efficient is that the governor decide the next target frequency by instant requirement during sampling interval. The instant requirement can response quickly to workload change, but it does not usually reflect workload real CPU usage requirement in a small longer time and it possibly causes frequently change between highest and lowest frequency.

    2) Ondemandx:
    Basically an ondemand with suspend/wake profiles. This governor is supposed to be a battery friendly ondemand. When screen is off, max frequency is capped at 500 mhz. Even though ondemand is the default governor in many kernel and is considered safe/stable, the support for ondemand/ondemandX depends on CPU capability to do fast frequency switching which are very low latency frequency transitions. I have read somewhere that the performance of ondemand/ondemandx were significantly varying for different i/o schedulers. This is not true for most of the other governors. I personally feel ondemand/ondemandx goes best with SIO I/O scheduler.

    3) Conservative:
    A slower Ondemand which scales up slowly to save battery. The conservative governor is based on the ondemand governor. It functions like the Ondemand governor by dynamically adjusting frequencies based on processor utilization. However, the conservative governor increases and decreases CPU speed more gradually. Simply put, this governor increases the frequency step by step on CPU load and jumps to lowest frequency on CPU idle. Conservative governor aims to dynamically adjust the CPU frequency to current utilization, without jumping to max frequency. The sampling_down_factor value acts as a negative multiplier of sampling_rate to reduce the frequency that the scheduler samples the CPU utilization. For example, if sampling_rate equal to 20,000 and sampling_down_factor is 2, the governor samples the CPU utilization every 40,000 microseconds.

    4) Interactive:
    Can be considered a faster ondemand. So more snappier, less battery. Interactive is designed for latency-sensitive, interactive workloads. Instead of sampling at every interval like ondemand, it determines how to scale up when CPU comes out of idle. The governor has the following advantages: 1) More consistent ramping, because existing governors do their CPU load sampling in a workqueue context, but interactive governor does this in a timer context, which gives more consistent CPU load sampling. 2) Higher priority for CPU frequency increase, thus giving the remaining tasks the CPU performance benefit, unlike existing governors which schedule ramp-up work to occur after your performance starved tasks have completed. Interactive It's an intelligent Ondemand because of stability optimizations. Why??
    Sampling the CPU load every X ms (like Ondemand) can lead to under-powering the CPU for X ms, leading to dropped frames, stuttering UI, etc. Instead of sampling the CPU at a specified rate, the interactive governor will check whether to scale the CPU frequency up soon after coming out of idle. When the CPU comes out of idle, a timer is configured to fire within 1-2 ticks. If the CPU is very busy between exiting idle and when the timer fires, then we assume the CPU is underpowered and ramp to max frequency.

    5) Interactivex:
    This is an Interactive governor with a wake profile. More battery friendly than interactive.

    6) Lulzactive:
    This new find from Tegrak is based on Interactive & Smartass governors and is one of the favorites.
    Old Version: When workload is greater than or equal to 60%, the governor scales up CPU to next higher step. When workload is less than 60%, governor scales down CPU to next lower step. When screen is off, frequency is locked to global scaling minimum frequency.
    New Version: Three more user configurable parameters: inc_cpu_load, pump_up_step, pump_down_step. Unlike older version, this one gives more control for the user. We can set the threshold at which governor decides to scale up/down. We can also set number of frequency steps to be skipped while polling up and down.
    When workload greater than or equal to inc_cpu_load, governor scales CPU pump_up_step steps up. When workload is less than inc_cpu_load, governor scales CPU down pump_down_step steps down.
    Example:
    Consider
    inc_cpu_load=70
    pump_up_step=2
    pump_down_step=1
    If current frequency=200, Every up_sampling_time Us if cpu load >= 70%, cpu is scaled up 2 steps - to 800.
    If current frequency =1200, Every down_sampling_time Us if cpu load < 70%, cpu is scaled down 1 step - to 1000.

    7) Smartass:
    Result of Erasmux rewriting the complete code of interactive governor. Main goal is to optimize battery life without comprising performance. Still, not as battery friendly as smartassV2 since screen-on minimum frequency is greater than frequencies used during screen-off. Smartass would jump up to highest frequency too often as well.

    8) SmartassV2:
    Version 2 of the original smartass governor from Erasmux. Another favorite for many a people. The governor aim for an "ideal frequency", and ramp up more aggressively towards this freq and less aggressive after. It uses different ideal frequencies for screen on and screen off, namely awake_ideal_freq and sleep_ideal_freq. This governor scales down CPU very fast (to hit sleep_ideal_freq soon) while screen is off and scales up rapidly to awake_ideal_freq (500 mhz for GS2 by default) when screen is on. There's no upper limit for frequency while screen is off (unlike Smartass). So the entire frequency range is available for the governor to use during screen-on and screen-off state. The motto of this governor is a balance between performance and battery.

    9) Intellidemand:
    Intellidemand aka Intelligent Ondemand from Faux is yet another governor that's based on ondemand. Unlike what some users believe, this governor is not the replacement for OC Daemon (Having different governors for sleep and awake). The original intellidemand behaves differently according to GPU usage. When GPU is really busy (gaming, maps, benchmarking, etc) intellidemand behaves like ondemand. When GPU is 'idling' (or moderately busy), intellidemand limits max frequency to a step depending on frequencies available in your device/kernel for saving battery. This is called browsing mode. We can see some 'traces' of interactive governor here. Frequency scale-up decision is made based on idling time of CPU. Lower idling time (<20%) causes CPU to scale-up from current frequency. Frequency scale-down happens at steps=5% of max frequency. (This parameter is tunable only in conservative, among the popular governors )
    To sum up, this is an intelligent ondemand that enters browsing mode to limit max frequency when GPU is idling, and (exits browsing mode) behaves like ondemand when GPU is busy; to deliver performance for gaming and such. Intellidemand does not jump to highest frequency when screen is off.

    10) Lazy:
    This governor from Ezekeel is basically an ondemand with an additional parameter min_time_state to specify the minimum time CPU stays on a frequency before scaling up/down. The Idea here is to eliminate any instabilities caused by fast frequency switching by ondemand. Lazy governor polls more often than ondemand, but changes frequency only after completing min_time_state on a step overriding sampling interval. Lazy also has a screenoff_maxfreq parameter which when enabled will cause the governor to always select the maximum frequency while the screen is off.

    11) Lagfree:
    Lagfree is similar to ondemand. Main difference is it's optimization to become more battery friendly. Frequency is gracefully decreased and increased, unlike ondemand which jumps to 100% too often. Lagfree does not skip any frequency step while scaling up or down. Remember that if there's a requirement for sudden burst of power, lagfree can not satisfy that since it has to raise cpu through each higher frequency step from current. Some users report that video playback using lagfree stutters a little.

    12) Lionheart:
    Lionheart is a conservative-based governor which is based on samsung's update3 source. Tweaks comes from 1) Knzo 2) Morfic. The original idea comes from Netarchy. See here. The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.

    To 'experience' Lionheart using conservative, try these tweaks:
    sampling_rate:10000 or 20000 or 50000, whichever you feel is safer. (transition latency of the CPU is something below 10ms/10,000uS hence using 10,000 might not be safe).
    up_threshold:60
    down_threshold:30
    freq_step:5
    Lionheart goes well with deadline i/o scheduler. When it comes to smoothness (not considering battery drain), a tuned conservative delivers more as compared to a tuned ondemand.

    13) LionheartX
    LionheartX is based on Lionheart but has a few changes on the tunables and features a suspend profile based on Smartass governor.

    14) Brazilianwax:
    Similar to smartassV2. More aggressive ramping, so more performance, less battery.

    15) SavagedZen:
    Another smartassV2 based governor. Achieves good balance between performance & battery as compared to brazilianwax.

    16) Userspace:
    Instead of automatically determining frequencies, lets user set frequencies.

    17) Powersave:
    Locks max frequency to min frequency. Can not be used as a screen-on or even screen-off (if scaling min frequency is too low).

    18) Performance:
    Sets min frequency as max frequency. Use this while benchmarking!

    So, Governors can be categorized into 3/4 on a high level:
    1.a) Ondemand Based:
    Works on "ramp-up on high load" principle. CPU busy-time is taken into consideration for scaling decisions. Members: Ondemand, OndemandX, Intellidemand, Lazy, Lagfree.
    1.b) Conservative Based:
    Members: Conservative, Lionheart, LionheartX
    2) Interactive Based:
    Works on "make scaling decision when CPU comes out of idle-loop" principle. Members: Interactive, InteractiveX, Lulzactive, Smartass, SmartassV2, Brazilianwax, SavagedZen.
    3) Weird Category:
    Members: Userspace, Powersave, Performance.
    View
    3
    B
    BusyPooping
    Tikerz said:
    Ever think that imoseyon didn't post his work on XDA for a reason? Did you get his permission to share here?

    Sent from my Galaxy Nexus using Tapatalk
    Click to expand...
    Click to collapse
    I have spoke with imoseyon and he is perfectly fine with it.

    I will update the thread to make a little more readable later on.




    Sent from my Galaxy Nexus using Tapatalk
    View
    3
    jonstrong
    jonstrong
    jesfreak said:
    Where did you get the stable release? Of 4.4.0?
    Click to expand...
    Click to collapse

    The live thread for the kernel is here, and if you look in post #1, you'll see links to get the latest stable version and also to a page with links to all the exp versions.

    Additionally, if you have franco's updater app on your VzW phone, you can use it to download and directly flash either franco's own kernels or the latest stable or exp versions of leanKernel (including 4.4.0) - very convenient!
    View
    2
    B
    BusyPooping
    wallendiaz said:
    that's a yes or no...or maybe???

    Sent from my Galaxy Nexus using xda premium
    Click to expand...
    Click to collapse

    Yes, they will work interchangeably.

    Also, updated links with experimental builds and changelog info
    View

New posts