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....
Related
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
Donning a new name in favour of the new delicious version of Android... Welcome to the ThunderKat Project!!
Heavily based of my Flaming Monkey kernel configurations and the stock AOSP kernel source, here's my standalone kernel for the Nexus 10. I will maintain this independently.
It will always remain close to the AOSP exynos kernel for manta (Nexus 10) with a few useful tweaks and additions, but will not have any OC/UV, colour controls and any advanced customisation options. It is a stable kernel and will not have frequent updates.
This kernel uses the AnyKernel method and is ROM independent. I have tested this on 4.4 (Stock & AOSP) based ROMs.
Features:
1. Linux Kernel 3.4.39.
2. Based on AOSP KitKat MR1 kernel source for exynos/manta.
3. Built using the Google ARM GCC 4.8 toolchain with -O3 CFLAGS & AFLAGS optimisations & ARM Cortex A15 build optimisations.
4. Enabled Conservative & Powersave CPU frequency governors (in addition to Interactive, Performance & Userspace). Interactive set as default.
5. Preserve correct sysfs permissions on governor change.
6. KSM (Kernel Samepage Merging) support.
7. NTFS, F2FS, EXT4 xattr (extended attributes) support.
8. Networked file systems support (NFS V3, NFS V4 & CIFS).
9. HIDRAW support (supports non-conformant HID devices).
10. Support for more input devices (keyboards, mice & joysticks) including Logitech Unifying devices.
11. Support for USB serial modems (PPPOE).
12. Support for multi-card readers (multi-lun devices). This allows you to mount multiple cards using a multi-card reader. May need an app like StickMount. (Credit @nvertigo67)
13. Removed SWAP support.
14. Removed some un-needed debugging.
15. Increased thermal throttle limits
16. Scalable CPU frequencies
Changelog [2014/08/24]:
1. Built using Graphite optimized GCC4.8 toolchain
2. Added ROW & SIO I/O schedulers
3. Set ROW as default I/O scheduler
4. Upstream F2FS changes
5. Miscellaneous I/O improvements
Changelog [2014/06/05]:
1. Update to AOSP 4.4.3 kernel source (kitkat-mr2)
2. Added F2FS filesystem support
Changelog [2013/12/15]:
1. Update to AOSP 4.4.1/4.4.2 kernel source (kitkat-mr1)
Changelog [2013/11/21]:
1. Initial release
Information:
1. Flash using a custom recovery (TWRP/CWM).
2. This kernel is ROM independent and uses the AnyKernel method. Hence it uses the current ramdisk. You may have issues if this is flashed after a kernel with a custom ramdisk. If so, reflash your ROM and then flash this kernel.
3. Needs an unlocked bootloader.
4. Make sure you have at least 50% battery charge before flashing this.
Download:
ThunderKatKernel-4.4.4-20140824 (AndroidFileHost)
ThunderKatKernel-4.4.4-20140824 (Goo.im)
Archive (4.4.x) - (AndroidFileHost)
Archive (4.4.x) - (Goo.im)
Archive (4.3.x) - Unsupported
Archive (4.2.x) - Unsupported
Source:
GitHub
Disclaimer:
While I have extensively tested this and even though it is heavily based on the AOSP kernel, you may encounter issues. I will try to help you, but I will not take any responsibility if anything goes wrong. Please exercise caution.
Credits:
Google, Samsung, CM, AOKP, PA, ktoonsez, morfic, franciscofranco, Goo.im, AndroidFileHost
Reserved. Just in case
craigacgomez said:
Reserved. Just in case
Click to expand...
Click to collapse
Very cool! I will be trying this tomorrow, will have time to play with it. Nice to see KSM in it.
Nicely done. I'm running your kernel as we speak--snappy, snappy! No issues so far. :good:
Only thing left to do now is give it a catchy name like: "The CRAIGINATOR"
Wow, great news, thanks craig!
brGabriel said:
Nicely done. I'm running your kernel as we speak--snappy, snappy! No issues so far. :good:
Only thing left to do now is give it a catchy name like: "The CRAIGINATOR"
Click to expand...
Click to collapse
Thanks...and yes, I will be renaming my ROM and kernel to something more... well, appealing... when I restart the ROM project...
Once I'm at 50% I'll be all over this like a rash
Sent from my Nexus 10 using xda premium
Great job, runs great! Only issue is it defaults to cfq scheduler on boot even when I have it set to run deadline.
More of a preference than an issue.
This kernel is really good, I was very impressed by your previous Rom and look forward to the new Rom you said will be released later in the year (hopefully!). Your hard work is much appreciated. Using your kernel with Carbon Rom right now and it seems very stable.
Sent from my Nexus 10 using XDA Premium HD app
Yep, snappy, snappy!
Sent from my Nexus 10 using Tapatalk HD
this kernel works best on my N10. no reboot, no SOD and no battery drain.
my tablet is 10 days up without a single problem or recharge! :good:
i hope it will be continued in the future!
Yes, I will continue supporting this kernel... though there will not be many updates... the aim to to remain close to AOSP, yet provide some useful tweaks and additions... I will be building a newer version soon (having problems with the cross compiler on my work laptop, else I would have done it today)...
Hi!
Can I flash this kernel to the stock ROM?
And revert back when new android version comes out to OTA update?
Thank you
teodor_ch said:
Hi!
Can I flash this kernel to the stock ROM?
And revert back when new android version comes out to OTA update?
Thank you
Click to expand...
Click to collapse
Yes, this will work fine on stock...and you can easily revert back using the boot.img from the factory images provided by Google...
Updated release in OP...
Does this have the latest wifi and or gpu drivers? I know wifi drivers are kernel level, not sure about the gpu though. Anyways, its a very nice and smooth kernel. It's been a baron wasteland in mantaland. I guess Google didn't sell many of these.
I just installed the kernel, very smooth, I was having shutdowns on Trinity latest and RootBox. Hopefully is not a ROM problem and this kernel fixes it, I really like RootBox.
Thanks for the awesome work and support.
Erik
situman said:
Does this have the latest wifi and or gpu drivers? I know wifi drivers are kernel level, not sure about the gpu though. Anyways, its a very nice and smooth kernel. It's been a baron wasteland in mantaland. I guess Google didn't sell many of these.
Click to expand...
Click to collapse
I have yet to incorporate the updated wifi and gpu kernel level drivers... I will be working on these soon...
Anyone here with sufficient kernel knowledge to merge the updated mali graphics drivers (http://malideveloper.arm.com/develo...n-source-mali-t6xx-gpu-kernel-device-drivers/)... There are a few updates that are beyond my kernel & C/C++ capabilities... like osk has been replaced by kbase... Please PM me if you can help!! Thanks!
Great work on this kernel! First time reaching 9 hours on screen time. Paired with Mr Robinson AOKP.
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
A day may come when the courage of men fails, when we forsake our friends and break all bonds of fellowship.
But it is not this day! Today, we PIE!
Kernel755Let the adventure begin!
KEWL FEATURES:
1,7 GHz OC!
Lots and lots of governors!
3 extra schedulers!
-O3 optimized!
Moar to come!
AWESOME DOWNLOADS:
The newest release (release, not alpha): http://bit.ly/1jccQXY
More downloads, including alphas and old releases in the changelog in the 3rd post!
FUNNY DISCLAIMER!
Code:
You are free to use this software, but it's not my fault if (when) you mess something up.
Please be careful and beware of being late to work, exploding cows and eating radioactive pie.
Kernel sources: https://github.com/someone755/Kotato/tree/jb_mr2_chocolate_rmfx
XDA:DevDB Information
Kernel755 - PIE, Kernel for the Sony Xperia S
Contributors
someone755
Kernel Special Features:
Version Information
Status: Abandoned
Current Stable Version: N/A
Current Beta Version: a1
Beta Release Date: 2013-12-16
Created 2013-12-16
Last Updated 2014-07-30
And now, a FAQ. @franciscofranco's FAQ, updated to fit our device.
F.A.Q. - Read this before complaining!
1. My phone exploded, HALP!
A: I don't answer to problems without a log. The log file is in /proc/last_kmsg. Paste it on pastie.org and link it on your post. Logcats are useless for Kernel purposes, don't bother posting them.
2. OMG BETTARY SUCKZ, IT DEAD IN 45 MINUTAS, HALP!
A: As you can imagine I don't build kernels to decrease battery life. All the battery life problems come from your apps, either Facebook, or Maps, or some Location Service being enabled etc etc. Check your damn wakelocks and fix them, the kernel is not responsible for them.
3. How do I flash this?
A: Since it's an .elf file, it's only flashable through fastboot. The general command is "fastboot flash kernel.elf"
4. OP is arrogant, I'm gonna call the Internet Police?
A: Deal with it.
5. Touch Control doesn't work in rXXX release, you suckas, fix plixe!
A: I don't know who you are. I don't know what you want. If you are looking for a fix, I can tell you I don't have the solution. But what I do have are a very particular set of skills; skills I have acquired over a very long career. Skills that make me a nightmare for people like you. If you leave now, that'll be the end of it. I will not look for you, I will not pursue you. But if you don't, I will look for you, I will find you, and I ignore you.
6. What's up with the kernel's name?
A: Well I have '755' in my name. So there's that...
7. I'm on stock/CM10/CM9/GB and this kernel doesn't work.
A: This kernel is ONLY for CyanogenMod 10.2 and any ROMs that came of it (like AOKP, for example). Don't flash on anything else unless you are SURE the ROM is based off of OpenSEMC's CM10.2.
8. My Locked-bootloader phone won't boot with this/I can't flash it.
A: This is a custom kernel. It requires an unlocked bootloader.
9. What app do you recommend for dealing with CPU settings?
A: Use TricksterMod. For 2D GPU OC and setting the 2nd core's governor, I recommend Kernel Tuner. Both are feature-packed and free, and if you don't mind an extra icon in your drawer, I say get both.
10. What is the difference between releases marked as a# and r#?
A: The r# releases are considered the most stable, but do not pack all the features. Because my work is rather slow, I'll add an alpha, an a# release, every time a minor change is introduced. But even if they look and feel stable, do not consider them as such. Most of them are dirty builds!!! Meant for advanced users only, so distributed in fastboot-flashable format ONLY!
11. I want to support you and your work!
A: Putting a subtle sign in your signature that you're using my kernel (or like it or have used it). Please, no big banners or anything, just the name of the kernel. That would be appreciated the most.
And now, thanks!
@RaymanFX -- helping me with nearly all issues and, of course the kernel sources. Also for an old project from which I learnt how proper GPU OC is done.
@abcdjdj -- writing a neat tutorial on how to compile kernels, and telling me about the -w flag
@letama -- adding a few new words into my dictionary (initramfs=ramdisk, did you know that!? )
@hei1125 -- for the NOVA kernel, and its' sources
@Forzaferrarileo -- for his kernel, Forzaferrarileo
@IAmTheOneTheyCallNeo, @fusionjack and @DJLamontagneIII -- for detailed toolchain and compiler flags explanation
@franciscofranco -- for inspiring me to get this done
@Wendigogo -- for SCSI and USB fixes help
@cronot -- for new logo and bringing in .96 fixes
@aebob -- for awesome logo idea
@thicklizard -- for helping with -O3
Sony and Google -- Android rules
HTC -- Inventing S-ON, forcing me to buy a Sony phone :3
@all -- for being an awesome community! C:
Changelog!
Code:
a1: [URL]http://bit.ly/1jccQXY[/URL]
-initial release
--O3
-CPU OC
-All governors from POTATO (4.2.x) kernel (lots of 'em)
-All schedulers from POTATO (4.2.x) kernel (zen, fifo, fiops)
I'll give it a try in Letama's dual boot as soon as I have time
I trust you know what you're doing, Wise one.
Still, it is dangerous to go alone. Here, take this. *Hands free pie*
Hey someone755,where are the potatoes??
Well I gotta change something from release to release
many people are moving to a cm11 based rom...
will you make a kernel for that as well?
No, not just yet.
I see 4.3 more stable, while KitKat is still in its early stages.
Also, I see KitKat will be updated more frequently, but I'm lazy, so no.
someone755 said:
No, not just yet.
I see 4.3 more stable, while KitKat is still in its early stages.
Also, I see KitKat will be updated more frequently, but I'm lazy, so no.
Click to expand...
Click to collapse
I see Kitkat gotten more stable than 4.3.. Since video recording and other issues from 4.3 are solved in it.. So probably its best either if Rayman releases a BETA version of 4.3 fixing the bugs or u switch to 4.4 kernel.. :silly: Just an opinion..
I tried your potatoes 4.2.2 kernel and it was great
Waiting for your kitkat kernel since I'm running cm11
Sent from my LT26i using xda app-developers app
Hi,
Just to be sure : this is a kernel for CM10.2 or JB-4.3 roms right ?
You ask it's an optimized -O3 built kernel. Did you solve your problem with /cache size and -O3 optimisations ? Will you build a potatoe kernel (for JB-4.2) including these optimisations ?
Cheers
Yes, it's for CM 10.2/Android 4.3 (OpenSEMC, of course),
Potatoes already have -O3
And just saw that KK is in Beta stage. Might give that a shot, Pie isn't all that popular, as it would seem.
Just need to hang in there for another week, my last part for my custom rig is just around the corner (hopefully).
Thank you for your kernel and for smooth video recording.
I very like OmniROM with your kernel.
I have only two small problems:
- TWRP is little slower than with other kernel (backup taken about 20 minutes)
- I'm not able to select "smartass v2" governor (I thik you have typo in your script, because there are two names in one row (see screenshot)
Lol sorry, I must've derped the Makefile. It'll run nightmare, not smartassv2 if you select it...
About TWRP, I don't have a clue, I never even used CM10.2...
I'll look into fixing it tonight, if I find the time.
hi guys
i finally was able to make a custom kernel with permissive selinux
it seems that my previous roms were having some missing files thats why the kernel did not function well with them
anyway, now it is working properly and so far no problems
i already included the V1 in my rom
so i made a different thread so that it will not be confusing
changelog:
V1: initial release
permissive selinux
V2: 06/02/2016
added init.d support
links to the kernel
mediafire
http://www.mediafire.com/download/l6cuhlevy799l8g/Teflanzy_Kernel_P905XXUABOL2_V2.zip
google drive
https://drive.google.com/file/d/0B_-JMtGLOAd3LU9pRS1iUXhKdGc/view?usp=sharing
MD5 checksum: E958AAD584A25FFB395249CDF8A7D116
kernel source on github
https://github.com/Teflanzy/viennalte_p905_kernel_source
kernel ramdisk with init.d support on github
https://github.com/Teflanzy/viennalte_p905_kernel_ramdisk
use this program from @osm0sis for create boot.img from ramdisk and zimage
http://forum.xda-developers.com/showthread.php?t=2073775
please report back with any problems you are facing
Glad to be the first to thank you for your great job @Teflanzy ?
Really happy to see the P905 getting the attention it deserves!
ADM!RAL said:
Glad to be the first to thank you for your great job @Teflanzy
Really happy to see the P905 getting the attention it deserves!
Click to expand...
Click to collapse
thanks for your reply
but do not expect much from me
I am just a beginner and wanted a permissive kernel for my device
I will try to add more features but it might take a long time for me to apply them
Teflanzy said:
thanks for your reply
but do not expect much from me [emoji14]
I am just a beginner and wanted a permissive kernel for my device
I will try to add more features but it might take a long time for me to apply them
Click to expand...
Click to collapse
Great things don't have to be big and bulky bro [emoji4]
I made a post when i first bought the device asked how to make rom deodexed so xposed could be installed and how hard is the process!!
What I'm trying to say is we just wanted the simplest of things [ofc i don't mean it's easy but things that are straight to the point]
Your kernel is just doing that [emoji111]
Opens the door to further mods!
Best of luck bro [emoji106]
Thank you very much for your work, I'll try.
Hello. First, I wanted to thank you for a job well done!
I am using the kernel for something like one and half a month with KOKO ROM and it is *stable*. And I mean stable as hell! - I don't remember even a single random reboot so far! Of course, switching selinux mode with setenforce command is working like a charm, as well as init.d support. Great, great job!
I personally find P905 (and probably other qcom-based variants) *still* the best tablet on the market so far (in my opinion, ofc ).
I am also really *not* interested in custom CM13 developement as stock ROMs has far more Sammy's specific features like *stable* MultiWindow support or S-Pen stuff and even if it is a good experience, I still find using it a waste of device's potential...
That is why I was personally thinking about adding some most popular custom features, like smartmax governor (which I personally find the best option for Snapdragon 800 devices, but opinions may vary ofc...), some custom hotplug driver (MPDecision sucks...) and first of all - enabling CPU overclock/undervolt (I find default maximum horsepower a little too short for handling more advanced tasks on this awesome but resource-hungry QHD screen; also battery-life is not as awesome as it was two years ago...).
So, I wanted to ask you if you are considering further developement of this stock-based kernel?
Also, if you don't have time/will/attitude to continue this great job, I wanted to ask if you have released any sources on github or something which one may sync and continue the developement?
Thank you in advance for the answer.
Best regards.
esgie said:
Hello. First, I wanted to thank you for a job well done!
I am using the kernel for something like one and half a month with KOKO ROM and it is *stable*. And I mean stable as hell! - I don't remember even a single random reboot so far! Of course, switching selinux mode with setenforce command is working like a charm, as well as init.d support. Great, great job!
I personally find P905 (and probably other qcom-based variants) *still* the best tablet on the market so far (in my opinion, ofc ).
I am also really *not* interested in custom CM13 developement as stock ROMs has far more Sammy's specific features like *stable* MultiWindow support or S-Pen stuff and even if it is a good experience, I still find using it a waste of device's potential...
That is why I was personally thinking about adding some most popular custom features, like smartmax governor (which I personally find the best option for Snapdragon 800 devices, but opinions may vary ofc...), some custom hotplug driver (MPDecision sucks...) and first of all - enabling CPU overclock/undervolt (I find default maximum horsepower a little too short for handling more advanced tasks on this awesome but resource-hungry QHD screen; also battery-life is not as awesome as it was two years ago...).
So, I wanted to ask you if you are considering further developement of this stock-based kernel?
Also, if you don't have time/will/attitude to continue this great job, I wanted to ask if you have released any sources on github or something which one may sync and continue the developement?
Thank you in advance for the answer.
Best regards.
Click to expand...
Click to collapse
Thanks for your words
As i said before
I am a beginner so i do not know how to add the features like other governors or enabling volt control
Furthermore i deleted my source but i can remake it because there are small changes that i made and i remember them
I am currently trying to port features from other snapdragon 800 devices kernels like note 3 and note 10.1 2014 edition
But i still get error on compiling
I will prepare the github source then post a link for it
@esgie
i just uploaded the kernel source with ramdisk each in seperate link
hope it is useful to you
i need help with adding synapse support to the kernel
if you know how to do let me know
Thank you.
I have just configured my developement environment.
I will try to proceed with compilation this weekend. I will also check how to implement synapse support
Hear you soon.
Hi.
I want you to know that I am absolute kernel-beginner, too.
Anyway, I have managed to add some basic features to the kernel.
Here you can download img file and test:
https://drive.google.com/folderview?id=0B2TnsPjj6dl4dHNZN3dBb3o1Zlk&usp=sharing
(as of TWRP 3 img files can be flashed directly to boot partition from recovery; P905 only!!!).
Features:
- setenforce working + init.d support (by Teflanzy)
- some custom schedulers (bfq, fiops, sio)
- custom governor (zzmoove with hotplugging support - I recommend to tune it with Kernel Adiutor using profile_number = 5, disable_hotplug = 0 and disabling mpdecision).
So not much at the moment.
It looks like it's hard to automatically cherry-pick a lot of interesting CM12-compatibile commits, as the samsung kernel source differs a lot from the CM one... I failed to add synapse support as for now but I am looking into the issue. Also, I will post and sync my sources not later than tomorrow.
Sorry, my time is limited and experience is not very big.
I am posting a test version here and if there will be enough feedback we may think about creating a separate topic and try to start some constant developement
Sources:
https://github.com/esgie/viennalte_p905_kernel_source
esgie said:
Hi.
I want you to know that I am absolute kernel-beginner, too.
Anyway, I have managed to add some basic features to the kernel.
Here you can download img file and test:
https://drive.google.com/folderview?id=0B2TnsPjj6dl4dHNZN3dBb3o1Zlk&usp=sharing
(as of TWRP 3 img files can be flashed directly to boot partition from recovery; P905 only!!!).
Features:
- setenforce working + init.d support (by Teflanzy)
- some custom schedulers (bfq, fiops, sio)
- custom governor (zzmoove with hotplugging support - I recommend to tune it with Kernel Adiutor using profile_number = 5, disable_hotplug = 0 and disabling mpdecision).
So not much at the moment.
It looks like it's hard to automatically cherry-pick a lot of interesting CM12-compatibile commits, as the samsung kernel source differs a lot from the CM one... I failed to add synapse support as for now but I am looking into the issue. Also, I will post and sync my sources not later than tomorrow.
Sorry, my time is limited and experience is not very big.
I am posting a test version here and if there will be enough feedback we may think about creating a separate topic and try to start some constant developement
Sources:
https://github.com/esgie/viennalte_p905_kernel_source
Click to expand...
Click to collapse
nice work
now I can check your commits and understand how to add extra governors
gonna download your version and test and report back after usage for a couple of days