As with all modding and hacking, I am not responsible for any damages, pregnant wives/gfs, or missing items from your phone, or bedroom.
***For those having issues with WiFi, flash the latest nightly, let it boot, then flash my kernel. There were some issues that have been fixed.***
***For FC's with Google Goggles insmod ipv6.ko. It relies on the ipv6 and FCs without it. The module is there you just have to insert it***
-All governors installed, including the new interactive governor.
-Configured very close to what the CM kernel would be.
-Includes all modules. Not all maybe used but all modules from the compile are included.
-Includes the IP Tunneling modules. I do not use VPNs or Tunneling, so I can not verify if this works.
-Low Voltage values for the stock Speeds, as well as What I think are low for the Overclocked Speeds.
-Every kernel has 7 slots.
-Supports Temp reading from the on-die sensor
I want to give a huge thanks to:
Dustin Jorge (Temp Monitor Support)
and the author of the interactive gov. (who ever you are)
VERSION 1.6 adds Compcache. Also new wifi module, and has ipv6 fix, and TUN.
Download Compcache script to allow it to work with CM. Here
If you are having issues with "Wifi Error" try this driver Put it in /system/lib/modules
IF you are Having BOOT LOOPS Install this zip Wifi Fix
NEW! Download 1200 Now Version 1.6
NEW! Download 1100 Now Version 1.6
NEW! Download 1000 Now Version 1.6
NEW! Download 900 Now Version 1.6
NEW! Download Stock Now Version 1.6
Download 1200 Now 300,500,700,900,1000,1100,1200
Download 1100 Now *Also known as the CEnnis91 Special* 250 to 1100 <------ =)
Download 1000 Now 250,400,500,600,700,900,1000
Download 900 Now 300,400,500,600,700,800,900
Download 1200 Standard Voltage Now
Download 1100 Standard Voltage Now
Download Stock Speed/voltage Now
Alittle info about interactive gov:
The CPUfreq governor "interactive" is designed for low latency,
interactive workloads. This governor sets the CPU speed depending on
usage, similar to "ondemand" and "conservative" governors. However
there is no polling, or 'sample_rate' required to scale the CPU up.
Sampling CPU load every X ms can lead to under powering the CPU
for X ms, leading to dropped framerate, stuttering UI etc..
Scaling the CPU up is done when coming out of idle, and like "ondemand"
scaling up will always go to MAX, then step down based off of cpu load.
There is only one tuneable value for this governor:
min_sample_time: The ammount of time the CPU must spend (in uS)
at the current frequency before scaling DOWN. This is done to
more accurately determine the cpu workload and the best speed for that
workload. The default is 50ms.
Edited by slayher, 27 August 2010 - 04:33 PM.