Database Info

[KERNEL][JUL.17]Bricked-3.0|3.0.36|v1.4|cmdline|Sweep2Wake|mpdecision|bad ass

SENSE Bricked-Kernel-3.0 Sensation (pyramid)
The first kernel with kernel mpdecision & 3-phase kernel thermal control
no need for those binaries anymore ​
Highlights:
Default clocks: 1566Mhz max / 192Mhz min
OverClockable till 1944Mhz !NOT ALL DEVICES CAN HANDLE THIS!
3D GPU Overclock @ 320Mhz (if selected during install)
2D GPU Overclock @ 266.667Mhz (if selected during install)
5 Stages 3D GPU scaling, variable io_fraction
3 Stages 2D GPU scaling, io_fraction 100
Increased bus bandwidth
L2 Performance Boost
cmdline options!
maximum screen off frequency
(configurable through cmdline options)
Sweep2Wake! (if selected during install)
>badass governor<
3-phase kernel cpu thermal control
>100% kernel based mpdecision<
The first kernel with interactive install using Aroma Installer by amarullz
with more customizations than you can dream of on any other kernel!​
Features:
Code:
[U]* CM (AOSP) compatible version: See below![/U]
* 3.0.36
* based on HTCs-3.0.16-Sources
* Tested with Sense 3.6 ICS (no known problems)
* Tested with Sense 4 ICS (animations work, thx to virtuous)
* Command Line Options - innovative!
__ Rename the zip to change your settings!
* Sweep2Wake
* badass governor
* 3-phase kernel cpu thermal control
* 100% kernel based mpdecision
* Optimized
* Built with highest Optimization Level (O3)
* Strongly improved UI-performance
* KGSL Early Suspend GPU slumber
* Increased 3D/2D-Performance (GPUOC)
* CAF Bluetooth stack (newer) - faux123
* CIFS
* UTF8 encoding (included for CIFS)
* wifi pm=fast
* Tweaked ondemand governor
* Undervoltage
* Overclocking to 1566Mhz default
* Min Clock @ 192Mhz default
* Boot time optimization. CPU will have 1566Mhz clocks during boot to ensure a fast bootup
* Flashlight and Camera-Flash will now be useable until battery reaches 5%
* Tree-based preemptible RCU
* Fast scheduler for CPU hotplug
* optimized preemptive settings
* basic NTFS support
* Userspace driven configuration filesystem
* Allow CPU-supported unaligned accesses
* Global CPU Voltage table used for adjusting voltage table for SnapDragon Dual Core. Inspired by Snq- modified by faux123 for SnapDragon fixed by show-p1984
* Improved Mobile Connection (fixed possible freezes introduced by HTC)
* ~8% Undervolted till 1566Mhz
* L2 Performance Push
* 3D GPU Overclock @ 320Mhz
* 2D GPU Overclock @ 266.667Mhz
* 6 Stages 3D GPU scaling, variable io_fraction
* 3 Stages 2D GPU scaling, io_fraction 100
* Tweaked ondemand to raise frequencies with higher load only (should contribute to battery life)
* Increased writing performance (lowers that annoying lag when updating 2 apps at the same time)
* Git's Sha1 implementation significantly decreases boot time
* CRC-optimizations
* ZRAM
* Fudgeswap
* PPP over standard asynchronous serial ports
* PPP over synchronous (HDLC) tty devices
* [URL="http://dl.dropbox.com/u/44206202/CallRecorder_v.1.0.20_alpha_2.apk"]Two-Way-Call-Recording[/URL]
* basic NTFS support
* increased bus frequency
* Improved WIFI - WLAN detection
* Automatic process group scheduling
* Lowered wifi-voltage
* cleaned code, improved performance
* Dropped debug code, was slowing things down
Changelog @ bricked.dehttp://bricked.de/compat.php?action=changelogs&device=pyramid&type=sense
What is sweep2wake?
Since this function collides with HTC's screenshot function (PWR+HOME) it will be disabled. Use the AOSP screenshot instead. (PWR+VOL.DOWN at the same time and hold it for about a sec)
This has a few advantages, one is a nice animation the second would be that it is hardcoded by google into any ICS firmware you can find. That means: no matter which device you will pick up, as long as it has ICS this function should work out of the box.​
How to change your frequency/governor before flashing?
That's new. Sounds strange, but it works. I am proud to present a truly innovative concept:
cmdline_khz / cmdline_gov / cmdline_maxscroff
What does this do for you?
Have you ever wished you could set the default min/max/gov/scroff frequency on your own?
Without having to rely on the dev to recompile?
Or doing it yourself?
Or even bothering to learn how to do that?
Or using OC apps that are just in the way?
(governor set able in setup from version 1.0)
Well, your prayers have been heard!
It simplifies any kernel install to the bare minimum. You download the zip, and just change the values to your liking. The kernel will obey you, it's magic!
you will download this file for example:
Bricked-3.0-v0.61-ics-maxkhz=1566000-minkhz=192000-maxscroff=432000.zip
now it is possible that you don't want to oc to 1566Mhz, or your preferred min freq is higher, or or or...
Just rename the file!
Bricked-3.0-v0.61-ics-maxkhz=1188000-minkhz=384000-maxscroff=540000.zip
The kernel will now boot from second 0 with this settings:
Max freq: 1188Mhz
Min freq: 384Mhz
maxscroff: 540Mhz
Cool, isn't it?
Now one could say, hell that's too dangerous, what if I write something wrong in there? No problem, your show-p1984 thought of everything. I have built in that much security measures that it is not even remotely imaginable that something could go wrong. I am serious. Whoever manages to break it gets a golden pile of **** from me.
Now what does it "autocorrect" exactly?
It corrects mhz instead of khz values for you, so you can actually flash this:
Code:
Bricked-3.0-v0.61-ics-maxkhz=1188-minkhz=384-maxscroff=540.zip
and it will still work.
Or it corrects wrong acpu frequencies. You can find a table @ the second post, but if you mistype sth, no fear, it will still work!
Code:
Bricked-3.0-v0.61-ics-maxkhz=1190-minkhz=390-maxscroff=545.zip
for example will let the kernel boot with 1188Mhz max and 384Mhz min (maximum screen off frequency 540Mhz). It always falls back to the next lower step. Actually you won't need to bother for the acpu table anymore, just type anything in there, it will automatically correct it for you! If you still want to enter the correct values, just look in the second post
Now what if you write a letter in there? Like this:
Code:
Bricked-3.0-v0.61-ics-maxkhz=II88000-minkhz=38A000-maxscroff=5A0O00.zip
Well, the kernel will detect that and fall back to default settings read out of my .config. Which means the kernel will boot @ 1566Mhz max and 192Mhz min and maxscroff will be set to 1566Mhz (=disabled).
What to do if you just want to change your clocks?
Rename the zip file, boot into recovery, flash, and enjoy
There is also a sysfs interface for the maxscroff frequency, for simplicity I kept the common name for it.
/sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq
Currently there is only one limitation:
You can't have two files with the same base on your scard. that means:
Code:
Bricked-3.0-v0.61-ics-maxkhz=1566000-minkhz=192000-maxscroff=432000.zip
Bricked-3.0-v0.61-ics-maxkhz=1188000-minkhz=384000-maxscroff=540000.zip
are not allowed to be on the sdcard at the same time, the kernel would boot with defaults: 1566/192 if you flash either one of those files.
The "base" of the filename is this: Bricked-3.0-v0.61-ics-
So you can have 2 files (or more) on the sdcard with names like this:
Bricked-3.0-v0.55-b4-ics-****
Bricked-3.0-v0.7-ics-****
Bricked-3.0-v0.8-ics-****
(****=etc etc etc etc)
Furthermore it must be followed by maxkhz=VALUE-minkhz=VALUE-maxscroff=VALUE.zip It is not possible to switch the positions of the options. But you can leave them out of there completely, the kernel will then boot with 1566/192/1566.
Ah btw: We now see our set max mhz under Settings->About Phone->HW->Cpu (it actually changes when you change your maxkhz)
This is genuine innovative code from me. I didn't even occasional glance at someone elses work. So if sth like this is already out there, SCREW THE DEV because I did not see it and wrote it from scratch!
And since 0.6 comes with the awesome Aroma installer you can now choose from 3 gpuoc versions!
GPU OC disabled, [email protected] & [email protected]
GPU low overclock, [email protected] & [email protected]
GPU high overclock, [email protected] & [email protected] + Bandwidth push
The source for this is split into two parts, Kernel & bash script. The script finds the zip on your sdcard, parses the filename and modifies the kernels cmdline inside the boot.img. The Kernel is parsing the cmdline, checking if everything is valid and setting your options.​
How to install?
Just flash from recovery. Because it creates a boot.img out of the one on your phone while flashing, it should work with the majority of ROMs out there.
Interactive install, enjoy the ride! ​
Where to complain about errors/bugs?
Please use the Issuetracker for bugs/errors/feature wishes!
Issuetracker @ https://code.google.com/p/bricked/issues/entry
[email protected]
IRC Chat: Freenode IRC #bricked​
Download:
No Guarantees! If it kills your grandmother or your device, I am NOT responsible! If you understand this:
(If you download, please hit Thanks below my post! Thank you!)
>>> DOWNLOAD <<<
XDA Discussion/Download for AOSP (ICS): Click me
Old Downloads (gcode): Click Me
​
Use System Tuner to undervolt!
Setting min/max frequencies should be done over the zips name instead.
​
Donor List:​
> Hall of fame <
With special thanks to all piggy bank donators!
Thank you very much!​
Source:
​

Changelog moved to bricked.dehttp://bricked.de/index.php?action=changelogs&device=pyramid&type=sense
What does PREEMPTIBLE mean?
Preemptive built kernels are favoring the userinterface over everything else! That means: An app in the background is using 50% of you CPU to spy on you. You want to move fast through the user interface/watch a video, whatever. The kernel will now favor your action over the app in the background. That's all the magic that's happening ​What is badass?
Well good question. With ICS I decided to rework my gb badass which never got released because it was always pushed aside. To break down what it is:
Badass removes all of this "fast peaking" to the max frequency. On a typical system the cpu won't go above 918Mhz and therefore stay cool and will use less power. To trigger a frequency increase, the system must run a bit @ 918Mhz with high load, then the frequency is bumped to 1188Mhz. If that is still not enough the governor gives you full throttle. (this transition should not take longer than 1-2 seconds, depending on the load your system is experiencing)
Badass will also take the gpu load into consideration. If the gpu is moderately busy it will bypass the above check and clock the cpu with 1188Mhz. If the gpu is crushed under load, badass will lift the restrictions to the cpu.
Please remember: Due to it's nature, this is not a benchmark governor. It is meant as a governor that gives you a smooth experience while saving battery, lots of it ​What is msm_thermal?
Kernel based 3-phase thermal control!
This replaces your /system/bin/thermald binary which is renamed by the installer to thermald_backup.
Check /sys/kernel/msm_thermal/conf/ for the thermal configuration
allowed_max_high = highest threshold (phase 3)
allowed_max_low = remove the throttling if we cooled down to this (clr_thrshold)
allowed_max_freq = max frequency if throttled (limit)
[...]mid[...] = same as above, just for phase 2
[...]low[...] = Lowest threshold (phase 1)
check_interval_ms = how often shall we check? (sampling rate)
Default: 1000ms (=1sec)
If you want to see msm_thermal doing it's job:
Code:
adb shell
cat /proc/kmsg | grep 'msm_thermal'
What is msm_mpdecision?
100% kernel based multi core decision! (should cpu1 be online or not?)
This replaces your /system/bin/mpdecision binary which is renamed by the installer to mpdecision_backup.
Check /sys/kernel/msm_mpdecision/conf/ for the configuration.
startdelay = time until mpdecision starts doing it's magic (70000)
delay = time between checks (500)
pause = if something else plugs in the cpu, fall asleep for 10000
scroff_single_core = if the screen is off, don't plug in cpu1 (1)
nwns_threshold_up = runqueue threshold, if this is reached cpu1 will be hotplugged (35)
nwns_threshold_down = runqueue threshold, if this is reached cpu1 will be unplugged (5)
twts_threshold_up = time threshold, this amount of time must have passed (250)
twts_threshold_down = same as above (250)
enabled = enable(1) or disable(0) mpdecision. This does not affect scroff_single_core!
idle_freq = a value against that will be checked if a core +/- is requested. (486000)
If cpu0 is below that value and a core up of cpu1 is requested, nothing will happen.
If cpu1 is above that value and a core down of cpu1 is requested, nothing will happen. (otherwise it would now put down cpu1 even though it is still working)
(all times are in ms)
If you want to see the mpdecision magic happening:
Code:
adb shell
cat /proc/kmsg | grep 'MPDEC'
Frequency/Voltage Table:
192000: 800000
310500: 825000
384000: 825000
432000: 850000
486000: 850000
540000: 875000
594000: 875000
648000: 900000
702000: 900000
756000: 925000
810000: 950000
864000: 975000
918000: 975000
972000: 1000000
1026000: 1000000
1080000: 1025000
1134000: 1025000
1188000: 1050000
1242000: 1075000
1296000: 1100000
1350000: 1125000
1404000: 1150000
1458000: 1150000
1512000: 1175000
1566000: 1175000
1620000: 1200000
1674000: 1225000
1728000: 1250000
1782000: 1275000
1836000: 1300000
1890000: 1325000
1944000: 1350000​Available CPU governors:
badass <-- !recommended!
lazy
interactive
lagfree
conservative
userspace
powersave
ondemand
performance​
Stock Kernel for ICS. Unsecured boot.img.

Want a beer?

Znuff said:
Want a beer?
Click to expand...
Click to collapse
two, at least! xD

show-p1984 said:
77 virgins? I would rather have 77 *****es who know what the **** to do!
Click to expand...
Click to collapse
hahaha that made my morning
Sent from my HTC Sensation 4G using XDA App

I have a couple questions, why still use governors or give options when ondemand is the only one that works properly on aSMP?
Or have you found a way to make governors still on both cores?
And this line:
Code:
Synchronous Multicore Threading
Android itself doesn't support true Multi threading at the core OS level, though it allows for apps to be multi-threaded.
What changes have you made to make this statement true.

BrokenWall said:
I have a couple questions, why still use governors or give options when ondemand is the only one that works properly on aSMP?
Or have you found a way to make governors still on both cores?
Android itself doesn't support true Multi threading at the core OS level, though it allows for apps to be multi-threaded.
Click to expand...
Click to collapse
1. Because ppl asked me to include Smartassv2. (ppl = baadnwz xD)
2. Android 2.3.4 has a bit of Honeycomb in it. It supports Multithreading.

Smartass doesn't seem to work as well as it used to on Bravo. Ondemand seems to be the way forward, plus CPU load balancing once threshold is reached. IMHO.
Sent from my HTC Sensation Z710e using XDA App

Re. your post in IC thread. With 0.2 I was getting 13k+, and other values higher than yours, just can't remember what they were exactly. How do I revert to 0.2, just flash it on top? Just for test purpose.
Again. No UI improvement over stock with either of them.
Sent from my HTC Sensation Z710e using XDA App

tinky1 said:
Re. your post in IC thread. With 0.2 I was getting 13k+, and other values higher than yours, just can't remember what they were exactly. How do I revert to 0.2, just flash it on top? Just for test purpose.
Again. No UI improvement over stock with either of them.
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Yes, just flash it on top.

tinky1 said:
Re. your post in IC thread. With 0.2 I was getting 11k+, and other values higher than yours, just can't remember what they were exactly. How do I revert to 0.2, just flash it on top? Just for test purpose.
Again. No UI improvement over stock with either of them.
Edited, sorry, typo.
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Oh crap, why do i keep quoting myself when I want edit. 11k+ that was.
Sent from my HTC Sensation Z710e using XDA App

Ok.
v0.2
ondemand 11568,1946(???),5794 (392-1.5); 11744,1982,5886 (1.3-1.5)
performance 11621,3368,6669 (1.3-1.5) 11399,3010,6365 (392-1.5)
BTW, System Tuner is able to adjust frequency
Damn, Cf is killing my battery. Mind you, been flashing, benchmarking, xda-ing etc since 7am, so 10.5h in and i'm still at 21%.

tinky1 said:
Ok.
v0.2
ondemand 11568,1946(???),5794 (392-1.5); 11744,1982,5886 (1.3-1.5)
performance 11621,3368,6669 (1.3-1.5) 11399,3010,6365 (392-1.5)
BTW, System Tuner is able to adjust frequency
Damn, Cf is killing my battery. Mind you, been flashing, benchmarking, xda-ing etc since 7am, so 10.5h in and i'm still at 21%.
Click to expand...
Click to collapse
i feel advertising for IC :B

Great job on the kernel, I just wanted to ask if you can include call recording maybe in the next release? That would be nice. Thanks and keep up the great work!
Sent from my HTC Sensation Z710e using xda premium

baadnewz said:
i feel advertising for IC :B
Click to expand...
Click to collapse
Well, score maniacs are going to jump the wagon lol.
IC 2.2.5 remember?

tinky1 said:
Well, score maniacs are going to jump the wagon lol.
IC 2.2.5 remember?
Click to expand...
Click to collapse
well 2.2.5 is still IC )

baadnewz said:
well 2.2.5 is still IC )
Click to expand...
Click to collapse
Baad, seriously, revert to 2.2.5 and close the thread LOL
Just ran bench on v0.2 with 2.2.5 again
noooooow, i'm shocked actually.
ondemand, (392-1.5 default freq) 11662,3376,6690
Will run it for few days, and if battery is close to stock (which it should be) it's a keeper for me, will replace my current stable nandroid

smartassv2 is working good

show-p1984 said:
1. Because ppl asked me to include Smartassv2. (ppl = baadnwz xD)
2. Android 2.3.4 has a bit of Honeycomb in it. It supports Multithreading.
Click to expand...
Click to collapse
it added features for better support, but the OS is still not anything close to what Honeycomb can do with multiple cores. 2.3.4 mainly improved support for multithreaded apps.

vladnosferatu said:
smartassv2 is working good
Click to expand...
Click to collapse
set the governor and then run a bench like cf-bench then in adb shell type this:
cat /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
it should return the set governor if it still says ondemand then its not setting it for both cores. Also if you change cpu1 to cpu0 it will show you what the primary core is doing.

[KERNEL][GB SENSE][05/10-2011]tristan202-gb-desire v05 (OC/UV/HAVS/BFS/CFS/V(R))

This is my personal kernel, that I decided to release now. It is extremely lean to minimize memory footprint and optimize perfomance. It is built from HTC official GB sources, with some of bananacakes, siberes, snq-s and my own patches. I intend to keep it at 2.6.35.10, as I see more problems than advantages in upstreaming to newer revisions.
Features:
-Hybrid adaptive voltage scaling (HAVS)
-V(R) i/o scheduler
-TinyRCU
-Overclock up to 1190
-Undervolt
-Ondemand, Virtuous and SmartassV2 governors (I use Virtuous for wake and Ondemand for sleep)
-AXI
-Lowered WiFi voltage
-EXT4 support
-snq-'s Autobrightnessmod (Enable all 10 levels)
-sibere's Battfix
-USB fast charge
-Optional 2 way call recording
-Hardcoded SD Speed Patch to 2048. No need for init script anymore
-Hardcoded highly tweaked Lowmemkiller (3584,4096,8192,20992,23040,25088). Throw away Autokiller and/or init scripts.
To make it more lean, I have disabled EXT2 support. SWAP isn't supported either, as I find it completely useless.
I have added CIFS and TUN as modules. To install, download and extract the file and push it to /system/lib/modules like so:
Code:
adb remount
adb push cifs.ko /system/lib/modules/cifs.ko
adb push tun.ko /system/lib/modules/tun.ko
And add the following line to your modules init script:
Code:
insmod /system/lib/modules/cifs.ko
insmod /system/lib/modules/tun.ko
The kernel comes in 2 flavors. BFS and CFS. Differences between them are here:
BFS - Brain F**k Scheduler
The scheduler essentially handles CPU resource allocation. It controls how the CPU ramps up in frequency and down again when not needed. The BFS version is generally very snappy (possibly more so than CFS) but is an older scheduler. It is designed to minimise latency on low spec'd machines (desktops generally)
Further details here:
http://en.wikipedia.org/wiki/Brain_****_Scheduler
CFS - Completely Fair Scheduler
This particular scheduler is newer than BFS. It is designed to make the best of High end machines (desktops again). In the early days, CFS seemed much laggier than BFS but now there is not too much in it. I am quite happily running a modern CFS kernel and I don't experience any lag issues.
Further details here:
http://en.wikipedia.org/wiki/Completely_Fair_Scheduler
I am aware that the BFS version throws some errors about 'bad cgroup data' in logcat, I haven't been able to get rid of them. I have disabled everything cgroup related in the kernel, but vm still throws the errors. Don't know why. Doesn't seem to impact performance.
I personally use the BFS version, as I find it somewhat faster than the CFS one. I have absolutely no wake lag, and I get good battery time.
Thanks go out to: snq-, bananacakes, sibere, tobi01001, thalamus, eviollet. If I forgot anyone, pls inform me.
CHANGELOG:
V05:
XZ compression
Fixed Wifi sleep
Tweaked OJ settings for better responsiveness (bananacakes)
Changed ramdisk compression method to gzip.
Rebuilt tun.ko and cifs.ko
v04b:
Fixed WIFI. (My bad. Forgot to adapt install script after including new ramdisk.)
v04:
Added Lowmemkiller tweak to ramdisk (3584,4096,8192,20992,23040,25088) No need for Autokiller or init scripts anymore. Over time I will move more tweaks into the ramdisk to minimize the need for init scripts.
Updated BFS to 0.406
Reverted battery gauge polling to 60 secs.
Added Virtuous governor. Virtuous is a highly tweaked SmartassV2.
Removed Lagfree governor again, as I found OndemandX better.
v03:
Hardcoded SD Speed Tweak to 2048. No need for init script anymore
Made 2-way call recording optional. Check downloads
Reduced battery gauge polling from 60 to 5 secs. (Untested)
A few bits more, can't remember it all.
v02:
Added Lagfree governor. Gives me a wee bit better battery, but sometimes lags when listening to music. Maybe I'll remove it again. Tell me what you think.
Added a minor change from tobi01001 to the lightsensor driver. Details here
Hopefully fixed USB fast charge.
Compiler optimizations
Link to my github: https://github.com/tristan202

Earlier i heard lot's of people complaining about reboots / hang up's when browsing internet with lowered WIFI voltages, i will give it a try today anyway thanks.

k3lcior said:
Earlier i heard lot's of people complaining about reboots / hang up's when browsing internet with lowered WIFI voltages, i will give it a try today anyway thanks.
Click to expand...
Click to collapse
I have been running with lowered wifi voltage for a few days without any problems at all. Doesn't browse much though, but market another wifi stuff have been working fine.

I'll give you feedback soon.
Thx and congratz.
Tapatalking.

tristan202 said:
I have been running with lowered wifi voltage for a few days without any problems at all. Doesn't browse much though, but market another wifi stuff have been working fine.
Click to expand...
Click to collapse
I've been using your kernel for several weeks now (tried all the rest) is this the same as your other one or have you tweaked it some more? and is there any chance you can add Sib's battfix?

Thanks a lot mate the combination of HAVS, BFS, 1190 OC with UV to 825 working very nicely for me
beanbean50 said:
is this the same as your other one or have you tweaked it some more? and is there any chance you can add Sib's battfix?
Click to expand...
Click to collapse
Just ask HTC they know everything about your phone

beanbean50 said:
I've been using your kernel for several weeks now (tried all the rest) is this the same as your other one or have you tweaked it some more? and is there any chance you can add Sib's battfix?
Click to expand...
Click to collapse
siberes battery fix is included, and I have been making some tweaks to since the last release. Some minor stuff, but still some improvement.

tristan202 said:
siberes battery fix is included, and I have been making some tweaks to since the last release. Some minor stuff, but still some improvement.
Click to expand...
Click to collapse
wow, many thanks....
is there much difference between the 2 governors ondemandx and smartassV2...?

Autobrighness mod is included (10 positions in arrays.xml)???
Tapatalking.

ziggy1001 said:
Thanks a lot mate the combination of HAVS, BFS, 1190 OC with UV to 825 working very nicely for me
Just ask HTC they know everything about your phone
Click to expand...
Click to collapse
haha...!
Yes, HTC, Google and every other Tom, **** and Harry...

beanbean50 said:
wow, many thanks....
is there much difference between the 2 governors ondemandx and smartassV2...?
Click to expand...
Click to collapse
Ondemand:
The ondemand governor is the default option used by Android. It scales the CPU speed between the minimum and maximum speeds depending on CPU load. If the system needs more speed, the kernel will rapidly scale up the CPU speed. This is available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point, ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
Smartass:
This is based on the concept of the interactive governor. This is included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
Interactive:
The 'interactive' governor has a different approach. Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when 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 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down to.
This is available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.

ironjon said:
Autobrighness mod is included (10 positions in arrays.xml)???
Tapatalking.
Click to expand...
Click to collapse
tobi's autobrightnessmod is included. Adding to OP.

Thanks, I'll be testing this! I've been using snq-'s kernel builds but since the OC/UV ones have freezing problems, and gingercakes won't work for me without MASSIVE lag, I look forward to seeing how this works out.
ironjon said:
Autobrighness mod is included (10 positions in arrays.xml)???
Tapatalking.
Click to expand...
Click to collapse
It seems to work, yes. I've just pushed my patched framework-res.apk, and auto-brightness seems to do exactly what it did on snq-'s patched kernel.
EDIT: Ah, ninja'd. Well, there you have it then.

tristan202 said:
Ondemand:
The ondemand governor is the default option used by Android. It scales the CPU speed between the minimum and maximum speeds depending on CPU load. If the system needs more speed, the kernel will rapidly scale up the CPU speed. This is available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point, ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
Smartass:
This is based on the concept of the interactive governor. This is included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
Interactive:
The 'interactive' governor has a different approach. Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when 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 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down to.
This is available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
Click to expand...
Click to collapse
but we only have the first two governors to choose from, Interactive is not an option (in setcpu) or am I being stupid as per usual ...?

is usb fast charge enabled?

ZeGuitarist said:
Thanks, I'll be testing this! I've been using snq-'s kernel builds but since the OC/UV ones have freezing problems, and gingercakes won't work for me without MASSIVE lag, I look forward to seeing how this works out.
It seems to work, yes. I've just pushed my patched framework-res.apk, and auto-brightness seems to do exactly what it did on snq-'s patched kernel.
EDIT: Ah, ninja'd. Well, there you have it then.
Click to expand...
Click to collapse
where can I find the patched framework ?

beanbean50 said:
where can I find the patched framework ?
Click to expand...
Click to collapse
You have to patch your own framework-res
Tapatalking.

ironjon said:
You have to patch your own framework-res
Tapatalking.
Click to expand...
Click to collapse
can you guess my next question ...? hehe

Here you go i like helping the aged especially when, poor eyesight, liver damage, and tropical diseases have taken their toll
[How to] Adjust auto-brightness on GB Sense ROM

beanbean50 said:
where can I find the patched framework ?
Click to expand...
Click to collapse
You can't find it anywhere, you need to patch your own framework. The framework apk differs for each ROM, and contains each individual user's UOT kitchen mods too... So to be safe, you really shouldn't use someone else's framework.
Anyway, here's how to do it:
http://forum.xda-developers.com/showthread.php?p=17713587
It's pretty easy, as long as you know where your ROM's framework apk is (in internal /system, or in /sd-ext). Also, the thread suggest you put your framework mod in a flashable zip, but it's easier to just boot in recovery, and use adb to remove your old framework and push the new one.

[KERNEL][DEFUNCT]CM10/CM9/AOKP Kernel v6.3.6 [8/23] - UV/OC/GPU-BLN-Governors

This kernel no longer works with current CM10/AOKP ROMS - PLEASE DO NOT USE
PLEASE READ THIS ENTIRE POST THOROUGHLY BEFORE PROCEEDING...
This is a customized kernel built from SGH-I727 (aka Skyrocket) source code. This ROM has all the fixes from CyanogenMod & Team Chopsticks tree along with some other stuff.
It's very simple to install.
Ensure you've already installed a working ROM
Install Zip from CWM.
Wipe both caches (just to be safe)
Reboot
FSync Control - Courtesy of Ezekeel
FSync Control which can be used to disable the fsync system calls for single files and filesystems (echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled). These fsync syscalls are used by kernel modules and user space programs to flush an I/O buffer (which is in RAM) to disk to make sure that this data is actually savely stored on the disk before executing the next step. Disabling fsync can result in data loss on a crash/freeze since the data is still in the I/O buffer and has not been saved to disk as it should be and can also lead to problems due to race conditions if two or more processes access the same file. On the other hand disabling fsync reduces the number of I/O operations which potentially could reduce the battery drain and also improve I/O performance.
Click to expand...
Click to collapse
Governors
Wheatley Governor - Courtesy of Ezekeel
http://rootzwiki.com/topic/14685-kernel27-jul-glados-v20-for-jb/page__st__90__p__405813#entry405813
Badass (default)
Badass removes all of this "fast peaking" to the max frequency. On a typical system the cpu won't go above 1080Mhz and therefore use less power. To trigger a frequency increase, the system must run a bit @ 1080MHz with high load, then the frequency is bumped to 1350MHz. If that is still not enough the governor gives you full throttle. (this transition should not take longer than 2-5 seconds, depending on the load your system is experiencing).
You can tweak the Phase 2 (1080MHz) and Phase 3 (1350MHz) via sysfs (if you don't know, then just leave it alone).
NOTE: Due to it's nature, this is not a benchmark governor. It is meant as a governor that gives you a smooth experience while saving battery.
InteractiveX
Created by kernel developer "Imoseyon," the InteractiveX governor is based heavily on the Interactive governor, enhanced with tuned timer parameters to better balance battery vs. performance. The InteractiveX governor's defining feature, however, is that it locks the CPU frequency to the user's lowest defined speed when the screen is off.
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.
GPU Overclocking
GPU is stock clocked at [email protected] & [email protected] (default).
Example: To increase maximum GPU frequency in 3D mode to 320 MHz:
echo 320000000 > /sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/max_gpuclk
Example: To increase maximum GPU frequency in 2D mode to 266 MHz:
echo 266667000 > /sys/devices/platform/kgsl-2d0.0/kgsl/kgsl-2d0/max_gpuclk
echo 266667000 > /sys/devices/platform/kgsl-2d1.1/kgsl/kgsl-2d1/max_gpuclk
Available frequencies:
3D: 320000000, 300000000, 266667000, 228571000, 200000000, 177778000, 27000000
2D: 266667000, 228571000, 200000000
Kernel-based MPDecision
100% kernel-based multi-core decision! (should cpu1 be online or not?)
This replaces your /system/bin/mpdecision binary which is disabled by the CWM flashable.
Check /sys/kernel/msm_mpdecision/conf/ for the configuration.
startdelay = time until mpdecision starts doing it's magic (70000)
delay = time between checks (500)
pause = if something else plugs in the cpu, fall asleep for 10000
scroff_single_core = if the screen is off, don't plug in cpu1 (1)
nwns_threshold_up = runqueue threshold, if this is reached cpu1 will be hotplugged (35)
nwns_threshold_down = runqueue threshold, if this is reached cpu1 will be unplugged (5)
twts_threshold_up = time threshold, this amount of time must have passed (250)
twts_threshold_down = same as above (250)
enabled = enable(1) or disable(0) mpdecision. This does not affect scroff_single_core!
(all times are in ms)
CURRENT
Version 6.3.6 - http://tinyw.in/L1BW <-- JB: CM10 or AOKP 4.1.x
Version 6.3.4 - http://d-h.st/L8K <-- JB: CM10 or AOKP 4.1.x
Version 6.2.1 - http://d-h.st/NWo <-- JB: CM10 or AOKP 4.1.x
Version 6.0.3 - http://d-h.st/hEI <-- ICS: CM9 or AOKP 4.0.4 <- Updated 8/22 - WiFi fixes
Version 5.4.5 - http://d-h.st/ngT <-- ICS: CM9 or AOKP 4.0.4
Governor scripts
NOTE: Not needed for v6.0.2 or v6.2 and beyond
These scripts will set the CPU0 & CPU1 governors correctly. Using a tool like System Tuner only sets CPU0 to the selected governor, but leaves CPU1 running the default. This was the only way I found to ensure both CPUs had the correct governor set. Basically this overwrites your init.qcom.post_boot.sh script with one that sets both CPUs to the same governor.
SmartAssV2 - http://d-h.st/zeQ
Badass - http://d-h.st/2CU
OnDemand - http://d-h.st/GAH
Non-CM9 Camera Fix
http://db.tt/vvMoadEo <-- Thanks endlessevo for this and thanks eliminat for pointing it out!
Battery life problems?
Read this first...http://forum.xda-developers.com/showthread.php?t=1759541
Then go here to grab Better Battery Stats (BBS) ... http://forum.xda-developers.com/showthread.php?t=1179809
Mega thanks to...
Team Chopsticks
Cyanogenmod Team
showp1984
gokhanmoral
faux123
TamCore
Ezekeel
FraciscoFranco
h0tw1r3
...and the other many countless kernel devs that I've Kang'd from

I don't claim credit for any unique code. I've managed to cobble this together from the following sources with various tweaks of my own to get it all running.
Faux123 (OC/UV code) - https://github.com/faux123/msm8660-htc-ics
Tegrak (Lulzactive governor) - http://tegrak2x.blogspot.com/2011/11/lulzactive-governor-v2.html
Erasmux (SmartAssV2 governor) - https://github.com/erasmux
showp1984 (BadAss, mpdecision, some very cool stuff here) - https://github.com/showp1984
TamCore (GPU OC) - https://github.com/TamCore
Hope I'm not violating any form of informal code of conduct in grabbing your guys' code.
CHANGELOG
Version 6.3.4
Removed Governor's that just plain do NOT work on our devices
Upgrade Adreno GPU drivers
Removed WiFi PM
Various CAF updates
Added ROW I/O scheduler
OnDemand Governor enhancements to support better battery usage - Applied to OnDemand-based governors (Badass, Wheatley, Lazy).
Added Gallimaufry, Aggressive, and Scary governors
Version 6.2.1
Merged Kernel up to 3.0.41
InteractiveX and Interactive screen off max freq set to 594Mhz
ram_console added to help debug CM10 - post /proc/last_kmsg to pastebin and link here
Version 6.2
Added new Governors: Lazy, Lagfree, InteractiveX (this is V2), Interactive updated to V3 (Imoysen didn't change the name for V3)
Fixed governor change not setting CPU1 (thanks to Imoysen) - No more governor setting scripts!
Added BFQv4 i/o scheduler
Version 6.1
Merged Kernel up to 3.0.40 (works great this time)
FSync control
WiFi PM control
Added fixes from Team Chopsticks git to get Alpha 2 working...not everything, but some of the juicer pieces
LMK from 3.4 kernel
Wheatley governor added - Please test and report back
As always see Github for all the bit/bytes
Version 6.0
Reverted back to 3.0.8 kernel core
Incorporated JB necessities
See Github for the bits/bytes
Version 5.5.3
Disabled ZRAM, Westwood, and LZO kernel compression
Removed some frequency steps - UnderVolting should be a little easier since there will be less knobs to turn
Changed some GPU iofractions
Updated pegasusQ governor - Works pretty good. Disable mpdecision, though. See OP to set "enabled" to 0.
Added some JB compiler options - Would be curious to see if this works OOB if someone wants to try on JB ROM
Version 5.5.1
Big update - Merged Linux kernel up to 3.0.39 (latest and greatest fixes/enhancements)
Enable ZRAM
TCP congestion control changed to Westwood (Google it)
jRCU for small systems
WiFi tweaks for battery life and flexiblity
Check out my Github commit log for a complete list - There's just too many
Version 5.4.5
Fixed 2D GPU bus speed
Implemented fixed ala Team Chopsticks to prevent emmc erasure to prevent bricking
Minor tweaks - Trying to fix vbus_present wakelock
Version 5.4.4
Added kernel-based 3-phase thermal management
OC GPU by default
DVFS disabled
Version 5.3.2
Updated OC code to default to 1.512Ghz, but OC up to 1.89Ghz (doesn't work for me very well, but ymmv) - Thanks to jjiggens for the help!
Volume bug fixed (would remain max or silent)
New BLN code
Check Github commit log for full details
Version 5.3
Really removed 1.836Ghz OC this time
UTF-8 support added back in
Reverted voltages back to the default - should fix instabilities for some. I would suggest under-volting as they start pretty high
Version 5.2z
Removed 1.836Ghz OC - Use 5.2 if you reallllly want that extra juice.
Version 5.2
SGH-I717 (Note) Source code base
GPU Overclocking support (see OP)
Upped max OC to 1.836GHz (defaults to 1.782Ghz)
Version 5.1
UTF-8 support
Various fixes
Compiler optimizations
BLN support
Version 5.0
UCLF6-based Source (e.g. official SGH-I727 from Samsung)
BadAss, SmartAssV2 Governors
OC to 1.782Ghz
Added GPU-level control to BadAss
Lowered BadAss Phase 2 Freq to 702Mhz (you can chance ala sysfs)
Hopefully reduced wifi wakelocks by filtering more unnecessary packets
VR and SIO schedulers added (let me know how they work out)
Version 3.3
RAMDISK updates from CM9
Badass tweaked for better battery (e.g. lowered phase2/3 frequencies)
Installs init.qcom.post_boot.sh with badass set as default for CPU0 & CPU1 and disables mpdecision <-- IF YOU MADE CHANGES TO THE ONE INSTALLED, MAKE A BACKUP OF YOUR'S AND COPY OVER MINE AFTER YOU INSTALL
Added support for HFP 1.6 wideband speech
Disabled GENTLE_FAIR_SLEEPERS
Version 3.2
BLN added back in
Governors: Badass (thanks showp1984), PegasusQ, SmartAssV2, standard ones
Toolchain updated to 4.6.3
Compiler optimizations
Raised max OC to 1.782Ghz
Kernel-based MPDECISION (thanks showp1984)
Various fixes (you can check my github commit log)
WiFi: WiFi wakelock reductions (tell me if things are out of whack)
WiFi: Power off wlan interface when wifi disabled to save battery
Touchscreen lock fix (ala Team Chopsticks)
Version 2.8
Non-standard governors removed - Not really aSMP aware and caused all sorts of funky weirdness
Underclocking enabled
Clock voltages tweaked - UV for some battery savings
Version 2.5e
Reverted back to fixed max freq @ 1.728Ghz (temp until I get some other things fixed)
SmartAssV2 tweaks
Fixed L2 Frequency inconsistencies (I think this was causing the freq to stick at 1.242Ghz)
Updated PegasusQ code
Version 2.4d
Added Pegasusq governor
Version 2.3
Min/Max CPU Frequency can now be set
SmartAssV2 Governor tweaked for battery life
Version 2.2.1a
Reverted early suspend/late resume driver mod
Version 2.2
Tweaked SmartAssV2 and Lulzactive governors
Added some other power tweaks
Disabled BLN - I think this is causing some problems atm. Will add back once they're ironed out.
Version 2.1
Tweaked Lulzactive and SmartAssV2 governors
Added OC/UV code from Faux123 repo
Version 2.0
Added Lulzactive governor
Version 1.0
Stock Kernel compiled from source with SmartAssV2 governor
My Github - https://github.com/InstigatorX

First good work
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Downloading. Will report back in a few minutes.
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php

Downloading! Gonna test this on Chimera beta 2 flashed over CM9 A5. Will report back shortly, stay tuned...
Sent from my SGH-I727 using xda premium
Edit/Update.... Running GREAT! Set to smartass V2 and set min freq to 192. I used NSTools to set and double checked the govenor and frequencies with Rom Toolbox pro and Set Cpu, everything is sticking and running smooth. Been running this for an hour now, will report back if I find any issues in the future. Thanks again for the kernel, InstigatorX, GREAT WORK!!!!!!!!! (high 5)

Nothing broken
Set to smartass v2 min 192
Feels smooth. Really smooth. Hopefully this means i can leave my charger at home now
Edit: holy crap! Phone is on usb charging from laptop. This is the first time on cm9 its actually charging FAST while I'm using it!
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php

I know it says that to be on a cm9 from but could I possibly flash this on sky ics?
Sent from my SAMSUNG-SGH-I727 using xda premium

No.
Btw-loses backlight after screen off. Not every time though, weird.
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php

Kole_Ackerson said:
I know it says that to be on a cm9 from but could I possibly flash this on sky ics?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
dont do it.
But yeah this kernel rocks!

Ok I'm on chimera flashed over aokp where are the performance settings at on here?
Edit: Using rom toolbox to set it. It seems to be sticking..
Sent from my SGH-I727 using Tapatalk 2

Should i be able to underclock? Not sticking.
If not, is it a PITA to enable?
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php

mindmajick said:
Should i be able to underclock? Not sticking.
If not, is it a PITA to enable?
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php
Click to expand...
Click to collapse
Works for me on CM9. Will check it out.
Sent from my SAMSUNG-SGH-I727 using xda premium

Am running cm9 too. I can set it, but when i go back in to performance its back to 1512.
--
SGH-I727 using XDA premium, running cm9.
Questions? look here: http://forum.xda-developers.com/search.php

wow i flashed this and i was on stock gingerbread rom.... now i'm bricked!!!
thanks for not putting cm9 only!!!!! What am i going to do.... Shifty eyes
haha no but i'm going to flash this tonight!!!
thanks for all the hard work!!!!!

tacotino said:
wow i flashed this and i was on stock gingerbread rom.... now i'm bricked!!!
thanks for not putting cm9 only!!!!! What am i going to do.... Shifty eyes
haha no but i'm going to flash this tonight!!!
thanks for all the hard work!!!!!
Click to expand...
Click to collapse
Dude I read the first line and was like holy shi-....oh thank god
Sent from my GT-P7510 using xda premium

BaconStep said:
Dude I read the first line and was like holy shi-....oh thank god
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
hahaha

So this is good to flash with aokp? I know it says for cm9 but someone posted up about aokp

softballjunkee13 said:
So this is good to flash with aokp? I know it says for cm9 but someone posted up about aokp
Click to expand...
Click to collapse
I'm running it just fine
Sent from my SGH-I727 using Tapatalk 2

tacotino said:
wow i flashed this and i was on stock gingerbread rom.... now i'm bricked!!!
thanks for not putting cm9 only!!!!! What am i going to do.... Shifty eyes
haha no but i'm going to flash this tonight!!!
thanks for all the hard work!!!!!
Click to expand...
Click to collapse
Are you kidding? The title of the thread says cm9 kernel. I really hope you are joking....
Sent from my SAMSUNG-SGH-I727 using XDA

sk8erwitskil said:
Are you kidding? The title of the thread says cm9 kernel. I really hope you are joking....
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Read the last two lines, he's obviously kidding.
You change/add a color filter btw? Noticing the colors are a bit warmer than usual.
Sent from my SAMSUNG-SGH-I727 using xda premium

[KERNEL][S4][CM9] Fusion Ultimate v1.1 ***OBSOLETE*** No longer supported.

Fusion Ultimate Kernel for AOSP-based ICS ROMs
Latest Version: v1.1 (8/9/12)​
This kernel is no longer supported due to the lack of interest in CM9 now that CM10 is out. Check out my new CM10 based Fusion Ultimate Kernel.
Thanks for all the support!!
Disclaimer:
Code:
#include
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. :P
* blah blah blah you get the point.
*/
As I promised, this is the Fusion Ulitmate Kernel for ICS AOSP-based ROMs. I forked intervigilium's repo and then incorporated all the changes from my other Sense-based kernel. Thank you for your patience; I was working on fixing things up before finally releasing an AOSP version. I decided to create a separate thread so it would be easier to report issues without the thread getting messy.
Click to expand...
Click to collapse
Post #1: Release, Features, and Downloads
Post #2: Changelog
Post #3: How to compile from source
Post #4: Frequently Asked Questions
This kernel is only compatible with CM9 and other AOSP ICS based ROMs. Sorry, no Jellybean support for now. I will wait until CM10 is a bit more stable.
Features
[*]CPU frequency control from 192Mhz <---> 1.89Ghz
[*]kernel defaults to min 192Mhz and max 1.5Ghz
[*]voltage control (use System Tuner Lite/Pro)
[*]SmartassV2, Interactive, Conservative, LagFree, and Lionheart CPU governors added
[*]Simple IO (SIO) and V(R) scheduler added
[*]capacitive LED lights dimmed to 2mA
[*]improved media scanning times (increased readahead buffer)
[*]changed minfree and ADJ values for good multitasking and performance
[*]zip package with modified init.qcom.post_boot.sh and thermald.conf
[*]enabled zRam (see FAQ for a detailed explanation of what it does)
[*]overall good battery life and performance
[*]optimized and tweaked
[*]much more; check the changlog or my GitHub if you want to know the specifics
Click to expand...
Click to collapse
Downloads
v1.0 (boot-080212.zip): http://d-h.st/f5F
v1.1 (boot-080912.zip): http://d-h.st/IjB
How to Install
For hboot 1.09 and below:
Just flash the zip in TWRP recovery. It will automatically flash the boot.img for you.
For hboot 1.13 and up:
you have two options
Option #1
Use TWRP's HTC Dumlock feature. It is a pretty neat workaround that allows you to flash boot.imgs in recovery even on a higher hboot.
Look here for instructions from TeamWin. If you are not comfortable with this method, then follow option #2 to manually flash in fastboot.
Option #2
In addition to flashing the zip, you will have to extract the boot.img from the package and flash it manually with fastboot. Blame HTC for the half-assed 'unlock bootloader' offering they give us. Hopefully we will get S-OFF soon...
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot
Look here for a guide.
Sources
initramfs: https://github.com/klin1344/initramfs_ville_cm9
kernel: https://github.com/klin1344/android_kernel_htc_msm8960
*special thanks to intervigil and xkonni for their awesome work on CyanogenMod! Seriously, without them we wouldn't have any AOSP ROMs!*
Enjoy

Changelog/Complete Feature List
Changelog
v1.0 (Initial Release 8/2/12)
re-wrote overclock code
completely re-based on the TMOUS source
init.d scripts support with Busybox run-parts
overclocked up to 1.89Ghz
added 192Mhz step
added SmartassV2 CPU governor (still finicky; needs more testing)
enabled Conservative and Interactive CPU governors
added SIO scheduler and enabled as default
increased readahead buffer
various tweaks for UI responsiveness
stable
v1.0
cleaned up CPU code (all frequency issues should be gone by now; check github for full details)
added LionHeart CPU governor
added LagFree CPU governor
reduced capacitive LED brightness to 2mA (looks better)
tuned Interactive CPU governor parameters
many optimizations; check github for more details if you want
v1.0
added voltage control capabilities (use SetCPU or similar app to UV)
cleaned up CPU code again to try to get frequencies to stick
v1.0
added V(R) IO scheduler
change to a zip package
modified init.qcom.post_boot.sh and thermald.conf
added modules in the zip so it shouldn't break WiFi on EU ROMs anymore
allowed undervolting minimum of 400mV
tweaked minfree and ADJ values for multitasking and performance; the used values were from the V6 OOM Calculator
Conservative CPU governor as default for battery life (use an app to change it if you want)
defaulted CPU frequencies to 192Mhz 1.5Ghz on boot
v1.0
enabled zRam
adjusted VM ratios
added NEON and Snapdragon optimizations
v1.1 (8/9/12)
updated modules; hopefully fixes WiFi issues
Click to expand...
Click to collapse
basically has all features of the latest Sense version.

For Developers
How to build this kernel from source:
This is assuming you already have your Linux environment setup and installed the required packages for compiling a kernel. Make sure mkbootimg is installed your /bin/ directory.
1. Clone my initramfs and kernel sources.
Code:
git clone git://github.com/klin1344/android_kernel_htc_msm8960.git
git clone git://github.com/klin1344/initramfs_ville_cm9.git
2. Compress the ramdisk into a gzipped archive. First navigate to the initramfs_ville_cm9 directory, then:
Code:
find . | cpio -o -H newc | gzip > ../ramdisk.gz
3. Grab the toolchain from DoomLord's handy repo:
Code:
git clone git://github.com/DooMLoRD/android_prebuilt_toolchains.git toolchains
4. I have created an easy build script. Modify the top four lines to be applicable to your setup. Make sure CROSS_COMPILE is set to the directory of the toolchain we just downloaded earlier (there are two; not the Linaro one). And change INITRAMFS_DIR to the directory of the ramdisk.gz you created earlier.
5. Build. First navigate to the android_kernel_htc_msm8960 directory.
Code:
./build.sh ville_defconfig
The script will detect the number of cores of your CPU and automatically make with the optimal -j#.
6. If all goes well you should end up with a boot.img in the android_kernel_htc_msm8960 directory.

FAQ.... Please read this before posting questions!!!
FAQ​
Frequently asked questions. Please read all of this first, and then if it doesn't answer your question, feel free to ask in the thread. I just don't want to have to keep answering Is this kernel SENSE based? or How do I jailbreak my HTC One S??? type of questions. Lol. :silly: Thank you.
Click to expand...
Click to collapse
What ROMs is this kernel compatible with?
As stated in the OP, this kernel is compatible with all S4 devices running an AOSP-based ICS ROM (CM9, AOKP, ParanoidAndroid). Will probably work with MIUI AOSP-based as well.
What is the best governor for me to use?
It really depends on what you're looking for. If you want performance, go with Lionheart or Ondemand. If you want battery life, go with Conservative. And if you are looking for a balance between battery life and performance, then use either SmartassV2, Interactive, or LagFree. These are just my opinions. Look here for a great reference of all the CPU governors. Test them out and decide which works best for you.
Which I/O scheduler is the best?
I personally use SIO, but you can test and decide which is the best for you. Read here to find the pros and cons of each one.
How do I overclock?
The kernel should default at 192Mhz 1.5Ghz CPU clocks. You can overclock directly from Performance Settings in CyanogenMod. Additionally, you can use SetCPU, No-Frills CPU, System Tuner Lite/Pro, or any similar CPU control app. However, be aware some apps don't allow the settings to stick properly.
How do I undervolt?
Right now, the only app that works for voltage control is System Tuner. Both the Lite and Pro versions allow you to change the voltages. Do not use SetCPU as it doesn't work.
Here is the voltage table I am currently using:
Code:
1890mhz: 1250 mV
1809mhz: 1225 mV
1728mhz: 1200 mV
1674mhz: 1175 mV
1512mhz: 1150 mV
1458mhz: 1137 mV
1404mhz: 1125 mV
1350mhz: 1125 mV
1296mhz: 1100 mV
1242mhz: 1100 mV
1188mhz: 1075 mV
1134mhz: 1075 mV
1080mhz: 1025 mV
1026mhz: 1000 mV
972mhz: 1000 mV
918mhz: 975 mV
864mhz: 975 mV
810mhz: 950 mV
756mhz: 950 mV
702mhz: 900 mV
648mhz: 900 mV
594mhz: 875 mV
540mhz: 850 mV
486mhz: 800 mV
384mhz: 725 mV
192mhz: 650 mV
Please just take these as a grain of salt; not all chips are created equal! Some devices can become an ass when it comes to undervolting, while others can starve the CPU to death and still run fine. Experiment little by little until you find your perfect voltages.
What is zRam and how does it work?
Originally Posted by faux123
ZRAM (aka CompCache aka RAMZSwap)
ZRAM is an updated version formally known as CompCache and RAMZSwap. It was originally designed for 2.6.38.xx kernels, I have backported to our 2.6.35.xx kernel. ZRAM allows real-time compression of memory objects in RAM thus reducing memory pressure for the Linux kernel and can keep more apps in memory longer (more apps in RAM == better performance, less fetching from slower MMC or SDCard). Compression, however, is not Free. Some CPU cycles are required to do the compress/decompression, so there's a slight penalty for it. The original CompCache / RAMZSwap required a user space binary to control its behavior which adds additional penalty to performance, but the new version ZRAM eliminated the need for a separate dedicated daemon, thus reducing the overhead and increased performance from the old CompCache by 20%. Therefore, with the newer implementation of ZRAM interface, the performance penalty is almost negligible.
Click to expand...
Click to collapse
Something doesn't work???
Please reproduce the error a couple of times and include a logcat.
Code:
adb logcat > logcat.txt
It will say "waiting for device", but it is actually recording a logcat. Reproduce the issue several times, and then you can close the Terminal or Command Prompt window. The logcat.txt will be in the directory you opened the Terminal/Command Prompt in.

Cool. Gonna try this out too.
Sent from my HTC VLE_U using Tapatalk 2

Thank you for the aosp love
Sent from my Nexus 7 using XDA Premium HD app

mteezey said:
Cool. Gonna try this out too.
Sent from my HTC VLE_U using Tapatalk 2
Click to expand...
Click to collapse
blackhartct said:
Thank you for the aosp love
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
No problem.
Sent using Tapatalk

Don't think undervolting is working. I can set everything to ridiculously lowl value and it would still work.

c19932 said:
Don't think undervolting is working. I can set everything to ridiculously lowl value and it would still work.
Click to expand...
Click to collapse
SetCPU? If so, wont work as stated in the FAQ.

Is this working on CM10? I know that is ics based but has someone tested?

c19932 said:
Don't think undervolting is working. I can set everything to ridiculously lowl value and it would still work.
Click to expand...
Click to collapse
phoenixita said:
Is this working on CM10? I know that is ics based but has someone tested?
Click to expand...
Click to collapse
Are you guys trying to test my patience or what? Both your questions are clearly answered multiple times in the OP and FAQ.
If I spend countless hours developing for you guys, wouldn't it be more fair if everyone could just take a few minutes to thoroughly read through my posts? If you can't do that, then maybe xda isn't for you. I post stuff for people to actually read, you know.
It's because of one after another of redundant questions like these that devs lose their patience and leave. Thats how the galaxy player community lost every single dev they had.
Sent using Tapatalk

Pheroh said:
SetCPU? If so, wont work as stated in the FAQ.
Click to expand...
Click to collapse
No I'm using system tuner pro

i love you for this man thanks a lot!
Sent from my HTC One S

Thanks Klin!
Sent from my HTC VLE_U using Tapatalk 2

I know using the minmax gov has fallen out of favor a bit, but I'm still a big fan of it; would it be terrrible if I asked if you could incorporate it?

blinksilver said:
I know using the minmax gov has fallen out of favor a bit, but I'm still a big fan of it; would it be terrrible if I asked if you could incorporate it?
Click to expand...
Click to collapse
Sure I'll add in the next release.
Sent using Tapatalk

c19932 said:
No I'm using system tuner pro
Click to expand...
Click to collapse
I have tested it out more, and it seems like changing the voltage in system tuner pro doesnt take immediate effect after you changed it. For example, I can change the voltage to a really, really low value (lets say 500mV for all frequencies) and the phone would still work. Then after I browse around on the phone for 1-2 min the phone would reboot. When I use system tuner on my HTC Sensation I dont have that issue. only in this kernel. Hope I'm explaining it clear enough

c19932 said:
I have tested it out more, and it seems like changing the voltage in system tuner pro doesnt take immediate effect after you changed it. For example, I can change the voltage to a really, really low value (lets say 500mV for all frequencies) and the phone would still work. Then after I browse around on the phone for 1-2 min the phone would reboot. When I use system tuner on my HTC Sensation I dont have that issue. only in this kernel. Hope I'm explaining it clear enough
Click to expand...
Click to collapse
Ok thanks for explaining the issue in more detail. Do any other apps (e.g. voltage control, setcpu) work?

Wifi Broken After Flashing
I noticed that wifi wasn't working after flashing, so checked the zip for modules. They're not there.

kundica said:
I noticed that wifi wasn't working after flashing, so checked the zip for modules. They're not there.
Click to expand...
Click to collapse
I will try to address the problem tomorrow.
Sent using Tapatalk

[HOW TO / POST] Your KERNEL Settting / Undervolting for JB (KingKang/h0tcakez) 10/31

So thanks to the devs DAGr8 and flappjaxxx, the Skyrocket has two new kernel! I want to use this thread so that people can post their preferences for their kernels.
Please post in the following order:
1- kernel you are using
2- governor you are using
3- i/o schduler you are using
4- best for [battery life, performance, or mix of the two]
5- Optional - if you have stable overclocking and undervolting, please feel free to share!
I'll post mine as soon as I install the new kernels, but for those who already have flashed their new kernels, please feel free to share! :good:
--------------------------------------------------------------------------------------------------------------------------------------------------------------
How To:
** I am not responsible for anything that goes wrong with your life or phone when you follow this how to! You are undervolting at your own risk! I am just sharing that I have done**
1 - You will need a custom kernel what supports undervolting.
For Skyrocket users, these are the kernels for JellyBean AOSP DAGr8 and flappjaxxx
2- Now, the only tool I know to allow voltage changes is the app called System Tuner. Download and Install. In addition, download an app called the stabilitytest and install it.
3- Click on Voltages and opening the app.
(For fllappjaxxx's Kernel, I learned that you have to set the CPU0 to CPU1 in order to change the voltages)
4- Start with one CPU speed and undervolt by 12.5 (one minus button click) | Do this for each CPU speeds. From my experience, undervolting by more than 75mV causes instability
5- If your phone freezes during undervolting, the phone will reboot itself and reset to its default settings. (SO WRITE DOWN YOUR NUMBERS)!
6- Do this until you achieve some sort of stability.
7- If you phone isn't freezing up or rebooting after changes, save this voltage table.
8- End everything and start the Stabilitytest app.
9- For pure stability of you undervolting, you will need to run the stability test of the classic run for a day. I'm too lazy and I don't care so I just do 15 cycles of the CPU.
10- If everything works, make the undervolt tweaks your default in the system tuner.
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Here are my Kernel settings
on the gs2usr's Paranoid Adnroid
1 KingKang
2 **Edit** Interactivex or Wheatley
3 **Edit** Noop with interactive or Deadline cfq with Wheatley
4 Battery Life
CPU -- mV
192 -- 725
310 -- 725
384 -- 725
540 -- 725
702 -- 725
864 -- 887.5
1.02 -- 975
1.18 -- 1000
1.35 -- 1100
1.51 -- 1150
1 h0tcakez
2 Interactive
3 Noop
4 Battery
Cpu -- mV
192 - 700
310- 700
384 - 700
432 - 700
486 - 700
540 - 700
594 - 700
648 - 725
702 - 825
756 - 875
810 - 900
864 - 925
918 - 950
972 - 975
1.02 - 987.5
1.08 - 1000
1.13 - 1025
1.18 1037.5
1.24 - 1050
1.29 - 1075
1.35 - 1087.5
1.4 - 1100
1.45 1125
1.51 - 1150
:good::good: If I've helped, Thanks would be appreciated! :good::good:

1- H0tzakes Kernel
2- Interactive
3- i/o schduler (Not sure what that is, I am a newb to all this stuff, only flashed ROM's)
I am using SlimBean 2.8 ROM
I was able to change the voltage values without setting the CPU0 to CPU1. Did I do something incorrect still? How do you change the CPU0 to 1? Also When I click on CPU it says CPU1 is offline, but shows CPU0 speed changing. Should CPU1 be offline, or will it come online when more power is needed?

Julian713 said:
1- H0tzakes Kernel
2- Interactive
3- i/o schduler (Not sure what that is, I am a newb to all this stuff, only flashed ROM's)
I am using SlimBean 2.8 ROM
I was able to change the voltage values without setting the CPU0 to CPU1. Did I do something incorrect still? How do you change the CPU0 to 1? Also When I click on CPU it says CPU1 is offline, but shows CPU0 speed changing. Should CPU1 be offline, or will it come online when more power is needed?
Click to expand...
Click to collapse
changing the values of one core should set the voltage. check it yourself. change between cpu0 and cpu1 and see if the voltage settings are the same. offline means that the cpu is not in use, that's all.

If you set voltage for cpu0 should cpu1 voltages be the same?
Sent from my SGH-I727 using xda app-developers app

evocalante said:
If you set voltage for cpu0 should cpu1 voltages be the same?
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Stole my question! +1
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

I have tried to save the settings in system tuner and then load them and it tells me I can't load them. I am trying to save them on boot, but do I click the on completed boot or the init.d script? I can the volts to stick
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

evocalante said:
If you set voltage for cpu0 should cpu1 voltages be the same?
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Yes, by setting the cpu1, it should set the cp0.

Smittiegee19 said:
I have tried to save the settings in system tuner and then load them and it tells me I can't load them. I am trying to save them on boot, but do I click the on completed boot or the init.d script? I can the volts to stick
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
are you sure you are changing voltage in cpu1?
I would say take the battery out for 2 minutes, power on the device and change the voltage settings in system tuner. Save 2 version of the voltage table. go into boot settings, click "on completed boot" for cpu settings and sd settings.

jee'sgalaxy said:
are you sure you are changing voltage in cpu1?
I would say take the battery out for 2 minutes, power on the device and change the voltage settings in system tuner. Save 2 version of the voltage table. go into boot settings, click "on completed boot" for cpu settings and sd settings.
Click to expand...
Click to collapse
Thanks finally got it to stick.Thanks for the response though.
Running The collective
Kernal: king kang
Governor: on demand
I/o : noop
Shooting for battery life. I work 12 hour shifts in an er, so in between dying patients i like to surf the web and game, etc
I use these settings
700 mv for the 1st 5
887.5 mv
900 mv
1000 mv
1100 mv
1150 mv
Seems stable no random reboots, or sod.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app