Presenting, my HD2 NAND Android kernel!
Summary
To provide, stable, fast and up to date kernels for our HD2s running either DFT or CWM nand android
Features
- 1190, 1190 Undervolt auto scaling versions available. listed is kernel MAX speed, it will scale to anything less depending on demand and ROM installed. Default max seepd is 998 without the use of an overclocking app
- Faster IO tweak taken from hastarins kernel tree
- Latest YAFFS driver
- Always built from latest source tree
- Very responsive kernel configuration
- Battery efficient
- Supports EXT 2 / 3 / 4, depending our your chosen ROM
- RMNET / PPP both supported, depending on your chosen ROM
- Bluetooth, WiFi, LED notifications all working correctly
- Smartass (default), Interactive and all standard CPU governors supported
- CIFS supported
- MAX defualt speed is 998, use setCPU or similar to overclock if you so wish
- cLK supported
- Automatic Extended Battery Support
Choosing your kernel
1190Mhz
This should work perfectly on nearly every HD2. It offers good speed at a slight cost to battery life. It will, depending on how your chosen ROM implements it, scale anywhere between 245-1190 Mhz depending on load
1190Mhz Undervolt
Same performance as 1190Mhz above, but with lower CPU voltage settings. It will work perfectly on most phones, but not all. If you experience FCs or random reboots then chose one of the aforementioned versions. This kernel offers significant battery life improvements if it works for you.
About the source and GPL compliance
The kernel is built direct from main GIT. You can access the commit logs and sources here on gitorious
The changes and modifications as mentioned in the changelog, and my build .config are all in my separate patch file, which you can download here
Download
All the kernels are supplied on one zip package. Contained within the package are the 2 kernel zImages and the associated modules. Chefs and advanced users will know what to do with these.
Download v11 (files only) --> http://htcfanboys.com/CleanEx/Kernel/DISTRIBUTION KERNELv11.zip
Download CWM ZIPs FOR NON TYPHOON ROMS (*series A*)
http://forum.xda-developers.com/showpost.php?p=11968195&postcount=408
Download CWM ZIPs FOR TYPHOON ROMS / ROMS SHIPPED WITH TYTUNG v6 (*series B*)
these include the wpa_supplicant fix for Wifi / bootlooping
http://forum.xda-developers.com/showpost.php?p=11974837&postcount=471
(the RAM named ones are for typhoon ram build)
Flash under cwm.
Wipe Cache and Dalvik Cache.
~~~~IMPORTANT~~~~
If you are not sure you need the WiFi patch, flash the *series A* kernel. If you find your phone bootlooping / wifi crashing, flash the *series B* kernels
As a backup, the wifi patch remains attached to this post
Changelogs
v11
- Pulled new updates from GIT
- Automatic Extended Battery support
- cLK patches and support built in
- some cleanups
- config changes, more responsive (quadrant wont improve thats IO bound)
v10
- Bug fixes, WiFi should work for everyone without the patch
- Imported the i2c, gsensor, GPU decoupling driver patches to new build tree
- Removed all debugging from kernel (99.9% people dont need it)
- Some build config changes, little more responsive
v9
- Fixed WiFi driver for non GB builds
- Fixed default CPU speed @ 998 max
- Fixed crashes / bootloops / random reboots
v8
- Switch to main branch, import speed mods from previous version
- Fix WiFi for GB / non-GB builds
- config changes for better response times
v7
- Switched to tytungs branch
- Swapped tytungs GB only WiFi driver for main one from primary GIT
- Added CIFS support
- Removed 998 / 1536 speeds
- 1190 Normal is not undervolted and will work for everyone
- 1190 uv is undervolted and might not work for everyone
- Reverted to SLAB, should fix bootlooping
- Other minor config changes
v6
-First public release
Disclaimer
I am not responsible for any damage, loss of data or earnings resulting from the use of my kernels. Users who wish to use an overclock kernel do so on the understanding that running any device outside its normal operating parameters may have damaging consequences
Credits:
Cotulla, Bepe, Hastarin, Tytung, Rafpigna, Markinus and all other kernel source contributors as mentioned on the GIT Commit logs.
Fadzy, JoPlayer, Dave and Jan-Willem for their never ending support, friendship, help and good laughs.
First! This is in a kleandroid 2.55?
yes....and no
its just been recompiled, and i added pure 998mhz for people who have phones that cant take the faster speeds!
Awesome! This is the best kernel, have been using it for like three days and it gives me the best battery life and performance. I loved it. I'll pack this one into cwm zip when I get home and flash it.
Edit: how much does battery life actually improve with the uv one? Now I'm torn between the uv and oc to 1.5ghz. Battery or performance?
Sent from my HD2 running Android on NAND
Can anyone test this on sergio's coredroid 1.4 and post results? I would but dont have my computer for a couple days.
g.lewarne
Please add 998Mhz kernel to next update CleanDroid!
Derek0228 said:
Awesome! This is the best kernel, have been using it for like three days and it gives me the best battery life and performance. I loved it. I'll pack this one into cwm zip when I get home and flash it.
Edit: how much does battery life actually improve with the uv one? Now I'm torn between the uv and oc to 1.5ghz. Battery or performance?
Sent from my HD2 running Android on NAND
Click to expand...
Click to collapse
you might get maybe possible 15% more battery time out of the UV kernel. in ideal circumstances in a perfect world of course
CWM
How to use that? :-(
Any zip to use on cwr?
felipemadox said:
How to use that? :-(
Any zip to use on cwr?
Click to expand...
Click to collapse
Not yet, it is still underway.
I made some cwm zips, before going to sleep. I wasn't able to test them because it's late, but they should work. If g.lewarne wants to post them in the OP, i have no problem. Inside the zip, after you download, there are 4 more zips, one for 998, 1190, 1536(this one doesn't work for me) and 1190 UV. Just flash the one you like and enjoy!
http://www.multiupload.com/DPR3F7TW7J
http://www.mediafire.com/?sqg55hze9evgchb
If you find this useful donate me a click on my thanks button.
Thanks derek.
g.lewarne said:
Thanks derek.
Click to expand...
Click to collapse
Once tested, please update, i will test a rom on it.
raviluke said:
Once tested, please update, i will test a rom on it.
Click to expand...
Click to collapse
I can't test anything now as im off to bed . Its 2am and I did a 14 hour day. Yawn!
report
Derek0228 said:
I made some cwm zips, before going to sleep. I wasn't able to test them because it's late, but they should work. If g.lewarne wants to post them in the OP, i have no problem. Inside the zip, after you download, there are 4 more zips, one for 998, 1190, 1536 and 1190 UV. Just flash the one you like and enjoy!
Please give feedback, again I say, they should work but haven't tested them. I've made all his previous kernel versions cwm zip, and flashed them successfully.
http://www.multiupload.com/DPR3F7TW7J
http://www.mediafire.com/?sqg55hze9evgchb
Click to expand...
Click to collapse
Thank you!
1190Mhz Undervolt its working here.
1536 does not work for ne! Causes random reboot on boot. If you want to test it, do so, but i'm pretty sure it's a problem with the kernel, not with the zip, because the one g.lewarne uses on his rom had 1536 and caused random reboots too, cant be a coincidence . Also, youre welcome!
I flashed the 1190 to test, now off to flash the UV one!
Sent from my HD2 running Android on NAND
raviluke said:
Once tested, please update, i will test a rom on it.
Click to expand...
Click to collapse
It works, but not the 1536 one, or at least not for me.
Sent from my HD2 running Android on NAND
Might I just point out that in real world situations the 1190 kernels are just as fast. 1536 is really just a gimmick but some people want it so there you to. Myself, I run my own personal 1305
Sorry for spamming this thread, but I must ask, is uv dangerous? If so, what are some steps I have to follow to prevent my phone from getting fu'd? Like for example,i know that for the 1536, we shouldn't have it always o/c'd to the 1.5ghz.
Sent from my HD2 running Android on NAND
Derek0228 said:
Sorry for spamming this thread, but I must ask, is uv dangerous? If so, what are some steps I have to follow to prevent my phone from getting fu'd? Like for example,i know that for the 1536, we shouldn't have it always o/c'd to the 1.5ghz.
Sent from my HD2 running Android on NAND
Click to expand...
Click to collapse
Uv Isn't dangerous in the same way, the only problem is possible crash, cpu is safe
Derek0228 said:
I made some cwm zips, before going to sleep. I wasn't able to test them because it's late, but they should work. If g.lewarne wants to post them in the OP, i have no problem. Inside the zip, after you download, there are 4 more zips, one for 998, 1190, 1536(this one doesn't work for me) and 1190 UV. Just flash the one you like and enjoy!
http://www.multiupload.com/DPR3F7TW7J
http://www.mediafire.com/?sqg55hze9evgchb
If you find this useful donate me a click on my thanks button.
Click to expand...
Click to collapse
Installed the UV Kernel on Coredroid v1.4 TMOUS ver its getting stuck at GO GO GO
Related
Thanks to Leshak , AndSecTest, mimocan, Unhelpful, xan, Supercurio and husq510 for the help.
This project started based on information found here:
http://forum.xda-developers.com/showthread.php?t=740514
But is has soon revolved into more fixes, patches and hacks. Thanks to all the developers involved and do buy them beers so they can continue to work on the fixes.
I've tested it to work on my phone but i cannot guarantee it will work on yours or if it will damage your phone so use it at your own risk. See known issues below if the problems have been resolved
Primary Features
- ext2/3/4
- Support I/O Scheduling for CFQ (stock), Noop, Deadline and Anticipatory
- Overclock and Undervolt support
- Overclocking for better performance. If you do not want to OC, use SetCPU to set Max at 1Ghz and enable checkbox Set on boot
- User defined Undervolt to save battery especially at lower frequencies. Use Xan's app for easy GUI control - here
- Also use Xan's app to change IO scheduling
- Rooted ADB shell for Android commander compatibility
Requirement
- i9000
- For Eclair 2.1 Only (Will not work on Froyo firmware)
My setup for cross compile without wakeup lag
- Use ct-ng crosstool
- Copy config file from arm-unknown-linux-gnueabi
Download
See attachment
Stock Kernels for reverting
Stock JM3 v3 kernel
Stock JM2 kernel
Stock XWJM5 kernel
Instructions:
- Extract the tar file from .7z
- Load tar file in PDA using ODIN and flash
- Do not check repartition and do not use pit file
- Use SetCPU to adjust frequencies
Reporting Problems
Please provide information below to help me understand:
kernel version: (eg oc120uv2-ctng)
UVLF setting (if kernel supports): (eg 50)
UVHF setting (if kernel supports): (eg 25)
descriptions:
Known Issues
- ondemand setting is unstable (need more verifications)
TO DO LIST
- BFS scheduling
- kernel modules (submit request)
Changelog
oc120_voodoo_b4.2
- enable CWM support even with voodoo ext4. Caveats: CWM will unmount /data after nandroid backup, you will not be able to remount /data in ext4 until you reboot back to recovery. Also, restore does not work when trying to restore /data.
- fixed check for debug_mode (it used to create logs in /sdcard/Voodoo/logs regardless if you enable*debug in /sdcard/Voodoo/)
oc120_voodoo_b4.1
- BLN patch v4 from neldar (http://forum.xda-developers.com/showthread.php?t=772672)
- All credit goes to author
- Signed update.zip format so rename file to update.zip and copy to /sdcard
- use recovery to flash
oc120_voodoo_b4
- updated to voodoo b4 (http://project-voodoo.org) - please read Documentation/FAQ, if you have previous installed Voodoo Beta1, please uninstall before upgrading
- Excludes color patch for later release
- All lagfix credit included in this build goes to Supercurio, please buy him a beer or two so he can continue on working on the project
oc120_voodoo_b3.1
- fixed init.d not working
oc120_voodoo_b3
- remove performance governor from startup cos i9000 dont need that
- added init.d support
oc120_voodoo_b2
- Use stock GPU ~200mhz table
- Voodoo2 lagfix (http://project-voodoo.org) - please read Documentation/FAQ, if you have previous installed Voodoo Beta1, please uninstall before upgrading
- Excludes color patch for later release
- All lagfix credit included in this build goes to Supercurio, please buy him a beer or two so he can continue on working on the project
oc120uv2
- Unhelpful patch for GPU table (http://github.com/Unhelpful/linux-galaxy/commit/5a729d3e2189159a20b00e0c331f0b112490e075)
- Interactive governor (http://github.com/Unhelpful/linux-galaxy/commit/aea72a98a2f261901d6f28f2d1deae3921d35948)
- user configurable UV settings (default value = 0 for UVLF and UVHF) for conservative governor only
- /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVLF_mV (for 100-800mhz)
- /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV (above 800mhz)
- for example # echo 50 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVLF_mV (will UV by 50mV for 100-800mhz)
- for example # echo 50 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV (will UV by 50mV for 1-1.2ghz)
- Setting increment of 25 (eg 25,50,75,100). Anything out range may hang
- Anything above 100 will be set to 100 (but I doubt you can get 100mV without crashing)
- After setting, do ur benchmarks and if everything is stable, you can add the command above into your init script depending which lagfix you have, add into your script.
Thanks!
Some questions:
1) the first thread about oc mentioned 1.2ghz, was this unstable for you?
2) Is this over-volted, under-volted, or no changes in voltage?
3) I'm guessing if I update to this kernal, I will loose any features of other kernals, like the lag-fix kernal?
I hope you can persuade the other devs to include this in their roms.
It this just for the unbranded SGS or does it work for TMO vibrant too?
Novek said:
It this just for the unbranded SGS or does it work for TMO vibrant too?
Click to expand...
Click to collapse
the kernel is just for the international version
it is just a test, i hv not test the limit yet.. this is a new phone so want to take it easy
i kept the voltage stock so just overclock a little and if its stable, will do more . More testing and reading is needed before i touch on the voltage.
it does not include mimocan's mod, i will work on it next release
Not Work
Hi GS S user,
not work in XXJP3 rooted Firmware!
Flash, Boot and go in Recovery menu!
Sir-ay said:
Hi GS S user,
not work in XXJP3 rooted Firmware!
Flash, Boot and go in Recovery menu!
Click to expand...
Click to collapse
XXJP3 is froyo.. android 2.2
he clearly states it works in eclair... android 2.1
Nice job cant wait to see how high the new hummingbird cpu can go. The galaxy s 2 has same cpu and is running at 2 ghz (if the leaked info is correct). I hope we can push it up to 2ghz with out to much voltage/heat increase.
[[ Cold ]] said:
XXJP3 is froyo.. android 2.2
he clearly states it works in eclair... android 2.1
Click to expand...
Click to collapse
upps
I will OC!!!!!!!!!!
Do you notice the postive effects of the overclock in any way? What does it do with benchmarks? Also do you test for (temperature) stability with some games as well, as they use the graphics card a lot which is on the same chip. Even when not overclocked the SGS can get prettty warm.
Installs nicely, oc ok to, but dont see that much increase in linpack.
Nice work tho.
Any chance to have ext 4 support in next update?
Thanks :
updated to v2
raspdeep said:
updated to v2
Click to expand...
Click to collapse
you're fast, lol. Thanks.
INeedYourHelp said:
your fast, lol. Thanks.
Click to expand...
Click to collapse
update before i go to bed
Guys, how do I use SetCpu?
Was 1.2ghz unstable?
Sent from my SGH-T959 using XDA App
interested in this... Allthough the phone does seem to get hot during heavy use, it doesn't get 'too' hot.
I have seen about 47 degrees celcius max read from battery temp (which seems to be cpu temp on our phones as my battery was stone cold)
Hi any possibility get v1 without mimocan.
Got samset including it nd sgs wnt boot cause of mimocan included.
thanks
I am using JM2. Does this make my phone any faster? Does it maked it lag free?
After tested this oc.. i am bit unsure: i get no performance increase... Is it confirmed that its functional?
Introduction
After a year of developing, with many stalls due to studying, we finally reached a stable state with the 2.6.35 kernel port. It is a quite honour to introduce you all to the Las Venturas kernel for the GSM Hero. It is a kernel based on the Cyanogenmod sources with updates coming from the AuroraCode forums. (those lads from Aurora are just geniuses) The main idea behind the Las Venturas was well, a fun project. Let's be honest I love deving new things and this is a really a nice project. We always strife to get the best out of our phones and the kernel has a big influence on it.
The 2.6.35 kernel adds speed improvements but in general it provides more functionality than the 2.6.29 kernel (based on the official HTC sources). It also has newer drivers for the Framebuffer (speed), adds ext4, better USB stack for our ARM devices.
Instructions
Go to your favourite recovery. Always wipe dalvik-cache!. Flash the kernel like any other update.zip, reboot and take a coffee while it is booting. Well done! High five yourself, as you just installed 2.6.35 for your Hero!
Downloads
Las Venturas version 1.2
http://www.mediafire.com/download.php?7r5rcr70mh3ynb3
md5sum: c37c43566cf882f21d0f1dde9afeb37d
Las Venturas version 1.1
Links:
http://www.mediafire.com/download.php?p3csh7sajbolp13
md5sum: 25d0fad0ac42ebf20be47f97c0511406
Las Venturas version 0.5.0
links:
http://94.23.152.245/xda/rmr/Las_Venturas-0.5.0.zip (thanks to wupper!)
http://www.multiupload.com/U6KYEOCWEE
md5: fa1d0b5767caa68152fe8166a7f74f4b
The big compare list
Current advantages:
full ext4 support
Newer overlay code, apps tend to be displayed faster than the original .29 kernel
Newer usb-code, more suitable for newer ROMs like Gingerbread and ICS than the .29 kernels
More stable GPS (no more reboots!)
General faster IO than 2.6.29
Less latency for playing sound/music
For the rest, it contains newer drivers for a lot of stuff. As it is a 2.6.35 kernel of course
Current disadvantages:
USB is experimental. Usb-tethering might not work, for non-sense ROMs you can try Erasmus fix
SD-card IO is slightly slower than flykernel (around 0.5%)
Change-log
Changes of last Version 1.2:
Faster general IO output
Fixed some bugs concerning SD speeds
Fixes to the interactive governor
Newer vibration-code, less latency (small impact, but everything is welcome)
Ashmem flushing fix
Code cleanup
Full log:
https://github.com/riemervdzee/hero-kernel-2.6.35/wiki/Changelog
Source code
Config used is found under kernel/arch/arm/config/hero_defconfig
https://github.com/riemervdzee/hero-kernel-2.6.35 (0.5.0 and above)
https://github.com/riemervdzee/cm-kernel (Older repository. For pre 0.5.0 versions)
Thanks list:
--> Elemag -- Initial start of this project, great advisor and debugger
--> s0be -- working on the .35 fork of this project for the Hero CMDA. Good to see another dev'er at work, always inspirational
--> Erasmux -- For his flykernel and his work on getting the .35 to work
--> Ninpo -- Initial start of this project
--> Feeyo -- For general fixes. Great mentor to linux/kernel programming
--> And of course all CyanogenMod lads working on the CM-kernel
Note that I hijacked Elemag's thread (he first opened this topic). So things might sound a bit wrong if you read the first pages
Las Venturax
This post will contain the releases I do until Riemer has time to catch up with me: (Unless I see me and Riemer would like to go in different directions with this kernel I don't want to open another thread for "my" versions)
Las_Venturax-0.6.2.zip (mediafire) (multiupload)
Scheduler tweaks (restored latency to 6ms and enabled hrtick - this time for real!)
SmartassV2: a few bug fixes.
Some upstream updates (thanks arco)
This is a generic "smart updater package" which can also be used to do OC from boot, as explained in my FlyKernel post under
Boot OC and optional tweaks (first post).
USB tethering on this kernel is different from the .29 kernels most ROMs are compatible with. Fixes for CM6/7 are found on post #1029.
More information about SmartassV2 (for users) can be found on my FlyKernel post.
ROM Developers
Developers aiming to integrate this kernel into their ROMs, might find it more convenient to use the following regular update package as a reference:
Las_Venturax-0.6.2-Floyo.zip
In this package the kernel's ramdisk is the one compatible with Floyo 1.4.
If you prefer to recompile the kernel yourself, you are very welcome to do so, but please share your updated sources. Obviously you are changing something (maybe very very small) otherwise why are you recompiling it? Please share with us what changes do you find to work better for you. You are also required to this by the GPL license of the kernel.
Previous versions:
Las_Venturax-0.6.0.zip (multiupload)
Tweaked scheduler parameters (lowered latency to minimum - ROM developers please do NOT overwrite the scheduler params in your init.rc)
Added smartassV2 governor as the new default governor - more details below (since 0.5f, tweaked built in sleep in 0.6.0)
Added interactiveX governor (since 0.5c)
Some compiler optimization (stable since 0.5e)
Fix for jogball notification (since 0.5a)
Use frequency table from fly kernel (since 0.5a)
Based on Las Venturas 0.5.0
Las_Venturax-0.5f.zip (multiupload)
Added smartassV2 governor (set as default)
Las_Venturax-0.5e.zip
Added "Wireless RNDIS" - could this fix usb tethering?
Tweaked compiler optimizations and moved to new toolchain
Las_Venturax-0.5d.zip
This version is a "quick fix" version trying to solve the stability issues (spontaneous reboots) reported with the 0.5c version. Only thing is I have no idea what is causing these problems so this is really a bit of a shot in the dark. Please report any stability issues, and if possible also state which ROM, what you where doing at the time and for spontaneous reboots attach a last_kmsg (i.e. "adb pull /proc/last_kmsg"). Thanks in advance to all the testers.
Reverted part of the compiler optimizations from 0.5c.
Back to NOOP scheduler
Default governor back to smartass. interactiveX is still available and I am still very interested in feedback regarding it.
Additional kernel config tweaks.
Las_Venturax-0.5c.zip
Added interactiveX governor by Imoseyon - for now this is the default governor (most likely a temporary situation).
Use BFQ I/O scheduler
Voodoo compilation optimizations
Fix for cpufreq time_in_state (i.e. SetCPU frequency counters) - broken only in 0.5a version (commit).
Note regarding the "new" interactiveX governor:
From a very quick look at its code, this governor looks promising to me, and I hope that it might provide better battery life over the current alternatives.
I am very interested to hear about the battery and performance with this governor vs. smartass and/or ondemand.
Some philosophical discussion on the subject:
It seems there are quite a lot of smartass/interactive variants out there (in kernels for other devices). I also have some ideas of my own, that will hopefully manifest into a new governor someday soon (smartassV2?).
In the meantime, interactiveX seems relatively close to smartass (also discriminates between screen on/off states), and to the best of my current understanding, in theory, given the parameters I have selected for it, I hope it might improve battery life.
Las_Venturax-0.5a.zip
Fix for jogball notification (commit)
Use frequency table from fly kernel
Based on Las Venturas 0.5.0
All changes are on my github.
Cudos to riemervdzee for all his hard work on this excellent kernel, as well as to all others who have helped to develop and test this kernel.
Yeah any and all kernel devs, get on this. I was supposed to be working on this with Elemag but Froyd has been eating my time. Hopefully one more release should get it "stable" so I can get back onto this.
Elemag has done fantastic work.
Hmm seems like there is already a .34 kernel for the G1. Damn them
Elemag said:
Hello,
A lot of things are already working, including:
MTD
usb
adb
charger/battery
display
keypad+trackball
...and probably most thing not mentioned as not working
Click to expand...
Click to collapse
Do you have a config file with adb working, I am stuck with no ADB using the hero_defconfig.
Also which ROM do you use for testing with this kernel? EDIT: to be more precise, I am mostly interested in the ramdisk you are using to get ADB to work.
Any other ideas how I can get adb to work?
erasmux said:
Do you have a config file with adb working, I am stuck with no ADB using the hero_defconfig.
Also which ROM do you use for testing with this kernel? EDIT: to be more precise, I am mostly interested in the ramdisk you are using to get ADB to work.
Any other ideas how I can get adb to work?
Click to expand...
Click to collapse
quote. i'm very interested
erasmux said:
Do you have a config file with adb working, I am stuck with no ADB using the hero_defconfig.
Also which ROM do you use for testing with this kernel? EDIT: to be more precise, I am mostly interested in the ramdisk you are using to get ADB to work.
Any other ideas how I can get adb to work?
Click to expand...
Click to collapse
Played a bit with the config and I finally got it working. Would still appreciate the config file you are using.
I am using the ramdisk from CM6 default boot.img. The config is hero_defconfig. Testing it under my own CM6 build which should be more or less the same as the CM6-nightlies.
The touchscreen driver synaptics_i2c_rmi.c does it contain the AOSP fixes found in the 2.6.29 kernels ?
rbrucemtl said:
The touchscreen driver synaptics_i2c_rmi.c does it contain the AOSP fixes found in the 2.6.29 kernels ?
Click to expand...
Click to collapse
I think it doesn't - Can't find anything related to eventhub filters.
looks good. thanks for posting sources. I'll help out also
Way awesome. Great job. I'm not too well versed in all this but I'd love to lend a hand as well.
Decad3nce said:
Way awesome. Great job. I'm not too well versed in all this but I'd love to lend a hand as well.
Click to expand...
Click to collapse
Agreed, not my field of expertise but willing to help in any way I can and I'm willing to learn
Sent from my HTC Hero running froyo: take that, Sprint!
Please guys, post here your improvements, your tweaks ecc ecc
mr.bang said:
Please guys, post here your improvements, your tweaks ecc ecc
Click to expand...
Click to collapse
Yeh a "tweak" which would make the rest of the hardware actually work would be nice.... We are still far from getting this kernel to a usable state. Let first concentrate on this.
I personally, have done a massive porting of code from the .29 kernel which has obviously resulted in the kernel not booting now - yippee Now working on trying to get it to boot which could takes anything between days and never.... Is there any way to debug the kernel boot if adb is not working?!
Anyone else working seriously on this?
i'm trying to work on this but i have few building problems..
You can boot, then reboot into a working kernel and pull /proc/last_kmsg if you can't get to adb. It would be nice if you post the output to pastebin and link it here .
As for the massive porting from .29 -- I think that the microp driver needs to be ported first, cause it is probably the bottleneck right now.
I found that the touchscreen driver initializes as /devices/virtual/input/input0 but on the .29 kernel it is input1 and input0 is the headset. I don't know if this can cause it not to work though.
If you have building problems, write to me, preferably in github. I don't have time to work much on this, because I am trying to make my diploma, but will surely take a look if someone has an idea.
Anyway, getting the touchscreen to work will be a breaking point
I actually started working on the SD card not being recognized (seemed easier than fixing the touchscreen or so I thought). Somehow got pulled in to porting a whole lot of code from the .29 kernel's arch/arm/mach-msm directory....
I'll try the last_kmsg thing sounds very usefull
Guys I think porting more and more stuff forward from .29 is a bad idea. Instead the stuff we -need- should be adapted for 2.6.34. Otherwise we're going to end up with some messy 2.6.29/34 hybrid. Everything we need is there in the kernel apart from specific drivers, otherwise 2.6.34 wouldn't work with the G1, however it does.
Hacre said:
Guys I think porting more and more stuff forward from .29 is a bad idea. Instead the stuff we -need- should be adapted for 2.6.34. Otherwise we're going to end up with some messy 2.6.29/34 hybrid. Everything we need is there in the kernel apart from specific drivers, otherwise 2.6.34 wouldn't work with the G1, however it does.
Click to expand...
Click to collapse
I was obviously talking only about drivers....
Kernel 2.6.35.14 – OC-UV-NEON_FP (1.516GHZ) – G2
-based off of HTC's ace-2.6.35-gb-MR (developer.htc.com) and supplied msm7230_defconfig (2.6.35.10)
-merged up to kernel.org's 2.6.35.14
-merged in coolbh3k's/cyanogen's oc patch
-frequency range is from 806 to 1516; default bootup is 245-806.
-undervolt all frequencies (max mv is 1300)
-merged in zinx's GAN_ETH wifi calling module modifications
-merged in changes from cyanogen's htc-kernel-msm7x30, and pershoot's vision-2632
-optimisations based off of .32 release from Vision.
-added/amended a few things to the config (-xtra (please see below and in github)).
-import autogroup (session) from 2.6.38
http://droidbasement.com/db-blog/
.....
Previous:
Kernel 2.6.32.41 – OC-UV-NEON_FP (1.516GHZ) – G2
-based off of HTC's vision-MR-2.6.32-g9ab3677 (developer.htc.com) and supplied vision_defconfig (2.6.32.17)
-merged up to kernel.org's 2.6.32.41
-merged in coolbh3k's oc patch
-frequency range is from 806 to 1516; default bootup is 245-806.
-undervolt all frequencies (max mv is 1300)
-merged in zinx's GAN_ETH wifi calling module modifications
-merged in a few changes from cyanogen's github.
-optimisations based off of .35 release from Nexus/DS.
-added/amended a few things to the config (-xtra (please see below and in github)).
http://droidbasement.com/db-blog/
Will this be compatible with sense-based roms?
Stryder5 said:
Will this be compatible with sense-based roms?
Click to expand...
Click to collapse
it will, but your mileage 'may' vary in terms of camera use/functionality, etc.
Nice work.
I just flashed it through rom manager. Will let you know how my battery does
So far seems quite quick.
pershoot said:
it will, but your mileage 'may' vary in terms of camera use/functionality, etc.
Click to expand...
Click to collapse
Fair enough. I'll give it a try tomorrow and report back
Works fine here on my Desire Z. Thanks
Wifi, calling, 3G, camera, video.
Would love to see stuff like BFS, interactive/smartass scheduler and more intermediate speeds at the low end (if possible).
Might just try to build one myself.
*edit* Just noticed the -XTRA Nice.
Does it change the Wi-Fi Mac address like other overclocking kernel ?
jzhyok said:
Does it change the Wi-Fi Mac address like other overclocking kernel ?
Click to expand...
Click to collapse
No the MAC address doesnt get altered like one the other kernels. Most of the others have been fixed and dont do that anymore.
Nice work, pershoot! Everything seems to work together nicely. Hopefully, this might help with the battery life with the addition of my screen off profile clocked at 245...
can I install this via ROM Manager?
Yes, you can. read the instructions
Instructions:
Flash the .zip through recovery
Click to expand...
Click to collapse
put the zip file to your sdcard, open Rom Manager and select Install ROM from SD card
convolution said:
can I install this via ROM Manager?
Click to expand...
Click to collapse
Yes you can install with rom manager
Yea it can be installed via rm. Search for pershoot in rm, and you'll come to see it.
Kernel doing ok?
Pls report all issues with a dmesg in hand.
Thx.
pershoot said:
Kernel doing ok?
Pls report all issues with a dmesg in hand.
Thx.
Click to expand...
Click to collapse
No issues for me
working fine here as well, running CM NB#33
installed and now my phone is stuck in a boot loop... had to battery pull and do a restore
dietotherhythm said:
installed and now my phone is stuck in a boot loop... had to battery pull and do a restore
Click to expand...
Click to collapse
if you have setcpu set to on boot, flash back to stock, untick that option, then flash this kernel.
go up in 50/100 MHZ freqs and test at each spot. use ondemand cpu governor. tell me which freq(s) your device is having issues with.
thx.
Flashed over cm rc 2. Looks fine - glad this thing is finally getting undervolted. Cm kernel is not optimized enough.
However, this kernal has too many frquency sets. In setcpu most frequencies are at 0s total use tiime.
Sent from my HTC Vision using XDA App
Wifi hotspot appears to be broken.
Sent from my HTC Vision using XDA App
First is an O/C kernel that I built from the HTC source. This kernel is stable and with the right profiles setup in setCPU has given me very good battery life. I'm giving coolbho3000 credit here as his post in the G2 forums is what helped me to do this. I am also acknowledging gr8gorilla who helped me several times through this process. Second is a kernel built from the latest CM kernel zource from zinx. It has proven to be very stable (after tweaking the voltages).
Now for the boring part ... If you choose to flash this you do it at your own risk. I am in no way, shape, or form responsible if you flash this and your phone turns into a paperweight. Once again, flash this at your own risk.
There, now that that is out of the way we can get on to the good stuff.
Make sure you choose the right kernel. The stock kernel will break your CM install if you flash it.
Kernels for Stock and Stock based roms
Kernel 2.6.32.21grankin010OC0v0.05
http://t1mgmaps.com/file.php?id=24
Md5Sum: 72c3430177eeefc6ff4b2c658efa0949
Features:
adb root enabled by default
system set r/w at boot (no need to remount)
voltages tweaked
cacheflush hack from zodttd integrated
noatime for better FS performance
Kernel 2.6.32.21grankin01-OC-v0.04
http://t1mgmaps.com/file.php?id=20
Md5Sum: a8668bdb2c1c7ca6ef0d9fbdafbe6969
Features(+v0.03):
Same features as v03 but with different voltages
Kernel 2.6.32.21grankin-OC-v0.03
http://t1mgmaps.com/file.php?id=19
Md5Sum: a82111399a9a4d570def14dce563a073
Features(+v0.01):
Voltages tweaked - Hopefully this one is more stable for you guys.
Kernel 2.6.32.21grankin01-OC-v0.02
http://www.mediafire.com/?o216o3b6jea13f9
Md5Sum: 2fdcde29532339743f0c41daae32db7f
Features(+v0.01):
O/C'd to 1.8Ghz with several intermediate clock speeds
Voltages for 1.7Ghz have been turned up a little bit to address stability concerns
Kernel 2.6.32.21grankin01-OC-v0.01
http://www.mediafire.com/?bqbdgb38m15n789
Md5Sum: af73907d0f9d8fbc1b5dcc41ea6b9552
Features:
Ext4 support (if you want to play with it)
O/C'd to 1.7Ghz with several intermediate clock speeds
ADB has root privileges automatically
System is set R/W on boot (no need to mount anymore)
HTC Perflock is disabled (pre-requisite for over-clocking)
CPU Governors:
Performance
Conservative
OnDemand
UserSpace
PowerSave
Kernels for CyanogenMod and MIUI
Do not use these with CM7-GB. They will not boot properly.
Kernel_grankin01-CM-OC-v0.10
http://t1mgmaps.com/file.php?id=26
Md5Sum: 6c4f5b18ca5509cc83cf5eac0667b3e0
Features:
Same as v09 but video works
Kernel_grankin01-CM-OC-v0.09
http://t1mgmaps.com/file.php?id=25
Md5Sum: 63bcc734bf33cb30eb0dd335f807bf10
Features(+v0.08):
Wifi is fixed in this release
Kernel 2.6.32.27grankin01-CM-OC-v0.08
http://www.mediafire.com/?4hs3ix1b8rdmz36
Md5Sum: 7822eb4dcf547d712c455c72c83d4118
Features:
Noatime for better FS performance
Cacheflush hack by zodttd is integrated
Voltages have been tweaked (again )
Inludes all the standard features also
Kernel 2.6.32.27grankin01-CM-OC-v0.07
http://t1mgmaps.com/file.php?id=18
Md5Sum: 9273d9405e6bdb76f754c96916e36262
Features(+0.06):
System Permanent R/W Fix (edited code in v06 and left that out ... oops)
Video is fixed
Voltages changed (hopefully for better battery life)
Kernel 2.6.32.27grankin01-CM-OC-v0.06
http://t1mgmaps.com/file.php?id=17
Md5Sum: 55f04250126b6763db2f180b2829e4ac
Features(+0.05):
Newest Bluetooth fixes
Newest Video fixes - broken/missing code
System Permanent R/W - Broken (edited code and left that out ... oops)
Kernel 2.6.32.27grankin01-CM-OC-v0.05
http://t1mgmaps.com/file.php?id=16
Md5Sum: 026e5717311fa42da073ac8a9fc442d5
Features(+0.03):
Bluetooth fix
Charge issue fix
Kernel 2.6.32.27grankin01-CM-OC-v0.03
http://www.mediafire.com/?3g6yv8g9ypsu953
Md5Sum: 0424f5565387f86818c1e67ff636443e
Features(+v0.02):
New version of kernel includes fix for video
Kernel 2.6.32.27grankin01-CM-OC-v0.02
http://www.mediafire.com/?jsux5wtj7mgcvzo
Md5Sum: 8c243df7f53143a6a3be5292073f052b
Features:
Ext4 support (if you want to play with it)
O/C'd to 1.8Ghz with several intermediate clock speeds
ADB has root privileges automatically
System is set R/W on boot (no need to mount anymore)FIXED
HTC Perflock is disabled (pre-requisite for over-clocking)
CPU Governors:
Performance
Conservative
OnDemand
UserSpace
PowerSave
Interactive
CM7-Gingerbread Kernels
Do not use these with CM6-Froyo! They have different ramdisks and wifi options built in.
These kernels have no issue with video. If you are having trouble with youtube and such update your GB rom to one of the newest. There was a memory leak in the source for the rom itself that zinx has fixed. Thirty to Forty-Five minutes of straight youtube action and I had no problem at all.
Kernel_2.6.32.27grankin01-CM-GB-OC-v0.09
http://t1mgmaps.com/file.php?id=29
Md5Sum: 7565340ac31ff7560d45ab42e043acc0
Features(+v0.08):
Changed voltages a tad
I get great battery life with light to moderate usage on this kernel
Kernel 2.6.32.27grankin01-CM-OC-v0.08-GB
http://t1mgmaps.com/file.php?id=22
Md5Sum: b7b5fde8db99a01d827c3b7fc81a387e
Features:
Noatime for better FS performance
Cacheflush hack by zodttd is integrated
Ext4 support (if you want to play with it)
O/C'd to 1.8Ghz with several intermediate clock speeds
ADB has root privileges automatically
System is set R/W on boot (no need to mount anymore)
HTC Perflock is disabled (pre-requisite for over-clocking)
CPU Governors:
Performance
Conservative
OnDemand
UserSpace
PowerSave
Interactive
I have packaged this into an update.zip format that you can flash through your custom recovery. Simply choose to install a zip from the sdcard and pick the update package to install it. It will install the wifi driver at the same time so you don't need to worry about that. Everything works with this kernel so far for me if you have any problems please post them and I'll see what I can do to fix them.
Remember that you hardware is not the same as your neighbor's so while he may be able to max the settings out and run stable your device may need to be set to a lower clock speed to run stable.
Source code for both kernels has been added to github. If you want to play around with them download source from here: https://github.com/grankin01
Happy Modding/Devving!
wow, thank you sir
I was just about to start testing kernels with Zinx's CM6 anyway. Looks like yours is first.
hmmm... could not run update.zip through clockworkmod. I was looking to extract the files and push them manually, however, I don't see a zImage file to push.
No luck with the miui rom. Cant get past the splash screen.
Sent from my HTC Glacier using XDA App
monnietron said:
No luck with the miui rom. Cant get past the splash screen.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Yeah, its based off of CM. I'm working on one built fromthe CM source right now.
Christopher3712 said:
I was just about to start testing kernels with Zinx's CM6 anyway. Looks like yours is first.
hmmm... could not run update.zip through clockworkmod. I was looking to extract the files and push them manually, however, I don't see a zImage file to push.
Click to expand...
Click to collapse
There isn't a zimage. I wrapped it all up in its own boot.img and then packaged it in the update.zip with the wifi module.
Does this break the nightly CM ROM? I know gorilla's kernel does.
I appreciate your work!
TmobileDash12 said:
Does this break the nightly CM ROM? I know gorilla's kernel does.
I appreciate your work!
Click to expand...
Click to collapse
Yes, it breaks it horribly. I'm working on it now.
grankin01 said:
Here is an O/C kernel that I built from the HTC source. This kernel is stable and with the right profiles setup in setCPU has given me very good battery life. I'm giving coolbho3000 credit here as his post in the G2 forums is what helped me to do this. I am also acknowledging gr8gorilla who helped me several times through this process.
Click to expand...
Click to collapse
Thanks for this grankin01. Great work to you and the others involved.
So no miui or cm6 on this kernel correct I just dont wanna break anything.
Sent from my icey cold glacier 4g freezing every phone in its path.
jriv said:
So no miui or cm6 on this kernel correct I just dont wanna break anything.
Sent from my icey cold glacier 4g freezing every phone in its path.
Click to expand...
Click to collapse
Not yet. It will work with the rom that you have installed right now though.
hey guys. im a noob to android. every other phone i have had has been winmo. i wanted to try this oc kernel because it seems easier to install than the gorilla one. however i ran into a problem when installing. i have a stock rom 2.2.1, perm rooted s=off, using clockwork recovery. i backed up my rom and flashed via rom manager. it then began to send me into a boot loop never getting past the first screen. just kept turning off and rebooting. soooooo i rebooted directly into clockwork and tried to do it from there and the same thing happened. so i restored my recovery and now everything is back to normal. can anyone point me in the right direction? i did notice that in clockwork it gave me two options to flash the kernel or to flash an update from the sd card. should i have flashed the update zip instead of the kernel or flash both.. sorry im a partial noob. i know how to use adb a lil and the emulator, this is the first thing i flashed on my phone and nearly had a heart attack from thinking i was bricked! any help is appreciated
Do you already have setCPU installed? Not everyone's phone will be able to reach the maximum speed without bootlooping or locking up. Just the nature of the beast. Try setting your speed down in setCPU (if you already have it installed) and turn set at boot off and then flashing and rebooting. Then you can test the speeds one by one to know what is working for you.
Edit: New kernel for CM and MIUI is nearly ready. 1.8Ghz with over 3200 on quadrant!!!
grankin01 said:
Not yet. It will work with the rom that you have installed right now though.
Click to expand...
Click to collapse
Oh I'm running miui now just haven't changed my sig lol
Sent from my icey cold glacier 4g freezing every phone in its path.
Can't wait for your kernel for CM! I wanna see my phone unleash its true power! Lol thanks dude.
Sent from my HTC Glacier using XDA App
grankin01 said:
Do you already have setCPU installed? Not everyone's phone will be able to reach the maximum speed without bootlooping or locking up. Just the nature of the beast. Try setting your speed down in setCPU (if you already have it installed) and turn set at boot off and then flashing and rebooting. Then you can test the speeds one by one to know what is working for you.
Edit: New kernel for CM and MIUI is nearly ready. 1.8Ghz with over 3200 on quadrant!!!
Click to expand...
Click to collapse
thanks.... stupid me... duuhhh.... i have setcpu installed already and it is set at "set on boot".... thanks for the help man... will give it a go and let you know how that works out!
Edit: turning off set on boot in setcpu didnt work. still boot looped. i will try uninstalling setcpu, then flashing, then reinstalling. i dont get it though because my highest on setcpu is the stock 1024.... hmm maybe its the profiles i have set up... either way, gonna give it another go in a few. im gonna get this working today if its the last thing i do. so thankful for backups to restore lol
grankin01 said:
Do you already have setCPU installed? Not everyone's phone will be able to reach the maximum speed without bootlooping or locking up. Just the nature of the beast. Try setting your speed down in setCPU (if you already have it installed) and turn set at boot off and then flashing and rebooting. Then you can test the speeds one by one to know what is working for you.
Edit: New kernel for CM and MIUI is nearly ready. 1.8Ghz with over 3200 on quadrant!!!
Click to expand...
Click to collapse
That's...retarded. I can't wait to see how that handles. lol! Are you incorporating U/V's on the lower frequencies as well?
UV / OC?
Is this a UV / OC kernel? Thanks for the help.
Christopher3712 said:
That's...retarded. I can't wait to see how that handles. lol! Are you incorporating U/V's on the lower frequencies as well?
Click to expand...
Click to collapse
Yes, and O/V's in the higher frequecies for stability. This one was picky.
InvisibleHero said:
Is this a UV / OC kernel? Thanks for the help.
Click to expand...
Click to collapse
Only in the lower frequencies. The higher frequencies weren't stable running lower voltages.
Thanks OP. When you say the lower ranges, at which MHz did you not UV? Just curious. I am thinking of not OC'ing more than 1.4MHz and didnt know if I would get the UV benefit.
*EDIT* Meant GHz
Hey Everyone,
I'm by no means a pro at kernel building but I've put lots of effort into these kernels so I thought I'd share them with you. The Uber kernel will always be updated to the latest Kernel version and will be overclocked to 1890 MHz or 1998 GHz (2 GHz) you decide which option you are willing to do. Unlike some of the other T-mobile Galaxy S II Hercules developers out there, I actually have a Galaxy S II and plan on having it until Summer 2014. This means that EVERY KERNEL I POST HAS BEEN TESTED AND IS WORKING although it might not be perfect (few things in life ever are).
Even though I don't post anything unless it works I still don't want to be liable for user errors. In other words, if you flash one of these Kernels your warranty is void and I AM NOT RESPONSIBLE for any data loss or bricked devices etc. A Clean install is ALWAYS recommended. That does not necessarily mean you can't install these kernels on you current build it just means that you might have problems if you do. Recently apps have been getting corrupted for whatever reason whether on Stock or AOSP and in most cases they cause RRs and SODs. If you find yourself in one of those situations a clean install is the easiest fix. If you want to try and save you apps then connect to you phone while in recovery using adb. Then type adb shell. Now once you are in that shell you can run this command to fix your apps "e2fsck -yfDC0 /dev/block/mmcblk0p25" it could take anywhere from a few minutes to an hour depending on the state of your apps.
[AOSP 4.4.x UBER KERNEL LINK]
UBER 4.1 - 1.89 GHz RELEASE for AOSP 4.4 KitKat
UBER 4.1 - 2 GHz RELEASE for AOSP 4.4 KitKat
All old Kernels can be found on Dev Host via this link (be careful you read file names and descriptions carefully if you choose to take a peek around) http://d-h.st/users/Cl3Kener/
Installation Instructions
**** IMPORTANT!!! USE TWRP 2.6.1.0+ for 4.4 kernels!!! Failure to do so may result in bootloops due to changes made to TWRP to accommodate SELinux in 4.4 ROMs (Links include flashable TWRP installation zips credits to meekrawb. Just flash them in your current recovery! ) ****
1. For best results a install these kernel after a fresh ROM install (although it still should work if you don't do that)
2. Reboot into recovery (MAKE SURE YOU USE THE RIGHT ONE!!! (See red print above))
3. Flash Kernel Zip
4. Reboot and let Settle for ~10 minutes
5. Install Trickster MOD from the App Store for access to all of the options.
6. Change the settings to something other than INTERACTIVE (Especially if you run it with BFQ it will give you the worst screen lag ever). Then enable "Set at Boot" and push the check mark button at the top right hand portion of the screen or else you will lose your configurations.
7. Enjoy!!!
Error Reporting
I am always open to hearing about your errors although just telling me something went wrong without giving me details does me absolutely no good. So here are my expectations if you do want to complain about something not working:
1. Please list the ROM you are using,
2. The IO scheduler you were using
3. The CPU governor you were using
4. The CPU frequency range (192/1080 etc)
5. What you have done to attempt to fix it.
6. If you were able to simulate it again using the same settings.
7. Anything else you think is applicable to the issue
I would also hope that you would consider trying some of the following things to fix your issue before you ever report it because most of these things will fix the problem without me even having to change a thing.
1) Fix file permissions using a program that does a thorough job. I recommend using the fix file permissions in ROM manager because it is the best I’ve seen. For the record, I don’t actually use ROM manager for anything other than fixing permissions. Please consider trying this first because it tends to fix most of the FC/RR/SOD errors you might have.
2) Make a backup and install a clean version of the ROM you are running and see if you are still experiencing those same errors. You may have corrupted files if you’ve been dirty flashing.
3) If that doesn’t solve it, redownload and reflash, maybe something got corrupted but it still managed to flash. This happens sometimes and I can cause you grief.
4) For advanced users pull a logcat. I know not everyone knows how to do this but you can learn if you check out this OP or other ones like it
SPECIAL THANKS TO:
Android88 - because he is awesome and encouraged me to create this thread!
Samsung - for the source code to build these Kernel (and for making the phone)
Ayysir - for his wonderful tutorial on making a bash script to build kernels and for helping me out all of the time with everything!
Elbermu - For Bringing Thermal and Sweep2Wake to Hercules and for the help!
Bmg002 - For his extensive work fixing/rewriting my init.d scripts
Gruntparty - For completely redoing/fixing the build.prop injector I use for my AOSP Kernels
I Am The Frost - For being my first and best tester on xda. He's debugged several issues in these kernels for me
UBER Kernel Repositories can be found at https://github.com/Cl3Kener/HERC-KERNELS and are properly labeled for your convenience (see the branches)
Informational Links
Here is a fantastic guide on "Innards" of Kernels
Optimizing Linaro Keychains
Building a Bash Script to make Kernels
JOIN MY GOOGLE COMMUNITY IF YOU WANT INSTANT UPDATES ON ANY OF ANDROID STUFF I DO.
Reserved!
XDA:DevDB Information
[KERNEL][AOSP 4.4.x][2GHz/1.89 GHz] UBER 4.1 | LINARO 4.7.4, a Kernel for the T-Mobile Samsung Galaxy S II
Contributors
Cl3Kener
Kernel Special Features:
Version Information
Status: Beta
Created 2013-12-02
Last Updated 2014-01-30
Changelogs
Changelogs
Changelog UBER 4.1 Release
- ONLY FOR ANDROID 4.4.2 CM 12/16 Nightlies and beyond!!!!
- Kernel Version 3.0.101 - Linaro 4.7.4 2013.12
- USB fastcharge
- MORE TCP Options "Veno as default
- Fsync toggle - disable for better performance but beware that if your phone crashes you will lose data.
- Overclocked CPU 1890 or 2GHz/ GPU 3D = 320 2D = 266
- IO Schedulers - cfq, bfq, row, noop, deadline, sio, vr, FIFO, and zen
- CPU Governors - intellidemand, interactivex, lazy, wheatley, smartass, badass, lionheart, minmax, fantasy, savagedzen, scary, HYPER and samsung.
- Frandom Lag Reducer
- Smaller sized kernel due to xz compression.
- CPU link - elbermu
- Sweep2wake - thanks dennis rassmann (@show-p1984) for his awesome code and elbermu for modifying it to fit this device!
- Thermal - thanks once again to dennis rassmann (@show-p1984) for his awesome code and elbermu for modifying it to fit this device!
- IO Booster
- CPU Power - Vincent Guittot
- Frontswap Support
- Google "Snappy" compression/decompression
- KGSL GPU Control - carvsdriver
Additional Info
Terminal commands to enable/change a kernel features if you are don't like kernel tuning apps
Fsync
To enable - echo 1 > /sys/module/sync/parameters/fsync_enabled
To disable - echo 0 > /sys/module/sync/parameters/fsync_enabled
USB Fast Charge
To enable - echo 1 > /sys/kernel/fast_charge/force_fast_charge
To disable - echo 0 > /sys/kernel/fast_charge/force_fast_charge
Set Thermal Values
Go to /sys/kernel/msm_thermal/conf/ in a root file browser and change the values
Set MPDecision Values
Go to /sys/kernel/msm_mpdecision/conf/ in root file browser and change the values
Disable CPU Link
echo 0 > /sys/kernel/cpu_gov_sync/force_cpu_gov_sync
Recommended CPU Govs by Category
For Performance
Performance Governor - Full OC
HYPER - full oc
Lionheart - full oc
For good battery life with decent performance use
Intellidemand
Interactivex
Ondemand
Samsung
Lazy
Moderately Conservative
Badass
Conservative
Wheatley (debatable could be in the above category)
Very Conservative
Powersave
SavageZen
not sufficient info? checkout out this op
Sweet! New kernel!
Sent from my SGH-M919 using Tapatalk
Sweet! Will try this out right now :good:
Flashed beautifully thanks @CI3kener
Sent from my SAMSUNG-SGH-T989 using Tapatalk
gotta love the uber, thank you kener
Sent from my SAMSUNG-SGH-T989
Thank You !
Will this work on alpha 3??
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
JNMM said:
Will this work on alpha 3??
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Yes ?
Sent from my SAMSUNG-SGH-T989 using Tapatalk
3 New Performance Boosters
Hey Everyone,
For those of you who haven't heard I've been using "Koding" as my new kernel build server. Space is very limited with my free account but if you'd like you can click here and signup to help me get more free space. You'll also find that you can learn how to code just about anything (java, html5, php, to name a few). Many developers and adding tutorials and sharing their projects so if you are interested in that stuff make sure to sign up!
I've made two nightlies this morning which need testing. For those of you who were around for my 4.3 you might recall that somewhere along the line there was suddenly a curious SD Card Mounting/Unmounting that would happen after unlocking the phone. I had made so many commits in such a short time frame that I was unsure which one caused the error. I've gone back and added my top three performance improving commits from the questionable series to see if any of these three commits caused the error (I certainly hope they did not, I really hope it was caused by the LZ4 compression and not the performance boosters). Let me know if you see any problems as you use these nightly kernels!!! Remember these are for 4.4 ONLY!!!
Here are the links!
UBER 1.89 GHz
UBER 2 GHz
Cheers!
Cl3Kener
just to let you know i have not been getting the sd card error on the 4.4 uber
Signed up on Koding maybe you can teach me a thing of two (^o^)
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Confirmed working on almites cm build
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
BETA2 For 12/16 CM Nightlies and Beyond
Hey Everyone!
Well Team Chopsticks finally got video working although from what I can tell all of the work was actually all done by our very own @bryan2894 who went and found the patches that fixed the video!!! Great work @bryan2894!!! Part of this video fix included the kernel so here is an updated kernel with the patch needed. This kernel will only have fixed video on CM 12/16 nightlies and beyond. I bet it might work with earlier but you might as well update if you are a CM user so what's the point?
Anyhow, enjoy the updates!
Cheers!
Cl3Kener
PS since I know someone will ask, This actually does work great with the 12-14 HellKat build since it also has working video because we grabbed the patches from CM before they were merged.
Sent from my SAMSUNG-SGH-T989
Question: for official CM 11 update, i am currently using recovery CWM 6.0.3.7, because CM officialssaid so or phone will run into problems. but this kernel requires TWRP, i am wondering can i update CM 11 nighlies with the given TWRP recovery?
Please advise. Thanks.
syan8182 said:
Question: for official CM 11 update, i am currently using recovery CWM 6.0.3.7, because CM officialssaid so or phone will run into problems. but this kernel requires TWRP, i am wondering can i update CM 11 nighlies with the given TWRP recovery?
Please advise. Thanks.
Click to expand...
Click to collapse
That stuff is nonsense. The latest TWRP in fact is much better for this phone and flashing this or any other ROM here IMHO. I tested both CWM and TWRP on more than one occasion and results were identical. For me TWRP is also much easier to get into when you have an issue with a new ROM booting and you need to get into recovery via the power & volume up buttons.
syan8182 said:
Question: for official CM 11 update, i am currently using recovery CWM 6.0.3.7, because CM officialssaid so or phone will run into problems. but this kernel requires TWRP, i am wondering can i update CM 11 nighlies with the given TWRP recovery?
Please advise. Thanks.
Click to expand...
Click to collapse
I've flashed CM11 (my builds) about 10 times in the last month and have been using TWRP 2.6.1.0 since Sept. without issue.
Just don't try to flash TWRP from within GooManager, either flash from recovery or use Odin (best).
Since the video recording is working now I moved to CM11 using the @Almite (Rom) and @Cl3Kener (Uber 2GHz kernel) and I can tel you this is solid Rock combination in performance and stability even those are still in Nightlies/Beta so thank you all for this amazing team work...
Is it possible to add the BLN notification (I know some don't like it but usually this the feature can be disabled)
Thanks