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.
Related
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....
-- DEPECATED -- DEPECATED -- DEPECATED -- DEPECATED -- DEPECATED --
Please follow this link to the new thread for the Semaphore Kernel for the I9000B, now maintained by rubervalrfl. This thread and builds herein are now deprecated and kept here for historical purposes only. Thanks for your support!
-- DEPECATED -- DEPECATED -- DEPECATED -- DEPECATED -- DEPECATED --
----
This is stratosk's Semaphore JB kernel compiled for the GT-I9000B (Latin america variant of the I9000). Stratosk doesn't support this variant, and being an owner of this device, I thought I'd share my efforts on compiling his excellent kernel for the I9000B variant.
With that said, here comes the disclaimer: By flashing this kernel, you accept that it comes without any support, neither mine and even less so from stratosk, since he doesn't support this variant on his own releases. So please don't bother him with support questions regarding this specific build. IOW: you'll use this kernel at your own risk.
There were reports of data loss during testing on early builds of the 2.8.x (kernel for Android 4.2) series - there were no more bad reports on later versions, but this needs to be said: Always do a nandroid backup before installing or updating any of the kernels posted here. I won't be held responsible if you lose data while using these kernels!
I *may* be able to help depending on whatever problems you might have, but don't expect timely answers, or any answers at all if I'm not technically able to figure out your problem - I'm a beginner on kernel development, all I did with this really was just some slight tunings and then recompile it for the I9000B. Also, I'm doing this on my free time, which is not much these days, so for now I'm just going to focus on following stratosk builds and recompile them for the I9000B as they come. I can say though, as far as problems, I don't have any with it on my device - it works fine and fast for me, at least the builds prior to 2.8.x, i.e.: kernels for Android 4.1 - I don't use Android 4.2 (yet) and hence I haven't / don't test the 2.8.+ builds myself - I rely on rubervalrfl's report for this; if the kernel boots without problems or data loss for him, then I deem it stable enough for release. Hence the glaring warning above about backups.
Now, on to the goodness:
This kernel is exactly the same as stratosk builds (hence, the exact same features and changelogs, including compiler versions and configuration), but with the following modifications:
Swap enabled;
ZRAM enabled as module (To configure it (on CM10), go into Settings / Performance / Memory Management);
KSM support enabled (Disabled on system by default, to enable it (on CM10), go into Settings / Performance / Memory Management)
Note about build version 2.7.0
Stratosk is no longer maintaining the 2.6.x builds that are meant for Android 4.1. But I was using Android 4.1 before I sold my SGS (yeah, I'll soon be retiring from compiling this kernel, read recent posts on this thread for more information), and looking at some of the latest 2.9.0 features I felt like having some of its features on the 2.6.x builds, and so I did it. Those features are really just some cherry-picks from Stratosk's 2.9.0 branch on his repository, so all credits to him, as always. Since there are quite some important changes I thought it would be better to bump the version number to 2.7.0 - I suppose it shouldn't be a problem to anyone, since the original 2.6.x builds are no longer maintained anyway, and it still sets it apart from the newer 2.8/2.9 builds. The 2.7.0 build contains the following cherry-picks from 2.9.0:
Reduce number of frame buffers for more RAM (on my ex-SGS I'm now at 383Mb, up from 377Mb);
Updated Interactive governor;
ROW I/O Scheduler
Known issues
The kernels posted here are compiled exclusively with BLN support, whereas stratosk's put out a 2.6.5 version with CM LED support. I haven't built versions with CM LED support because they simply didn't work on my own testing - the LEDs wouldn't light up at all with it, which effectively broke LED notification for the I9000B. Because of that my builds are compiled exclusively with BLN, which at least lights up the LEDs for notifications.
Blinking LEDs with BLN doesn't work (?) - they just keep alight: I'm still not sure why, although I suspect it may be something specific to my own phone because it doesn't work on DerTeufel's Hellybean kernel either. Feedback is welcome on this (let me know if it does in fact work for you). I've read in a few places that that's how it's actually supposed to work (blinking only actually works with the BLN Control App, "Pro" version), but I'm still not sure, so PLEASE DO GIVE A LITTLE FEEDBACK, PEOPLE!
What works
Everything else, as far as I could see.
Usage
Just flash it on CWM like any other kernel. Normal version and 's' version are provided just like on stratosk's release. Use the Semaphore Manager app on Google Play, from stratosk, to setup the kernel features.
All instructions and documentation from stratosk's original Semaphore kernel applies to this one, so look into his own thread for more information.
Source
Github repository
Thanks
To stratosk, of course, for his awesome work on his kernel, and for letting me post this here for I9000-B users;
Everyone who is/was involved on the development of the Semaphore kernel - basically, anyone on stratosk's "thanks" list
rubervalrfl, for testing the 2.8.0 version. If you want a 4.2 ROM for the I9000B to go with the 2.8.+ kernels, check out his CM10.1 Preview for the I9000B over here.
I'm sooooooo happy
Work on 4.2?
I don't think so.
I think just devil works on it
Dimabr10 said:
Work on 4.2?
Click to expand...
Click to collapse
I haven't tested, so feel free to. If stratosk's release works on it, then this most likely will too. I'm not a "bleeding-edge" kind of guy, though - I've upgraded to CM10 only a couple weeks ago (from CM7), and I see many other kernels don't yet work with 4.2, and if the other kernel devs around here are anything like me, they're probably not going to bother getting their kernels working on 4.2 until CM10.1 gets out of alpha status, since most kernels around here are derived or use parts of the CM kernel, and CM is the most popular Android anyway.
Thanks for this, cronot.
I'm happy that I9000B users can have Semaphore kernel.
Although, I can't official support I9000B, due to lack of free time, I'll do my best for any help.
stratosk said:
Thanks for this, cronot.
I'm happy that I9000B users can have Semaphore kernel.
Although, I can't official support I9000B, due to lack of free time, I'll do my best for any help.
Click to expand...
Click to collapse
Thanks for your support, Stratos
I still hope your help isn't needed specifically with my build, though. You've already got your hands full with your own releases Apart from the Known Issues list on the OP, I have no problems at all with your kernel, it's working really nice! The only problem I would report for 2.6.0 is something that's mentioned here in your thread (hence, not something specific to my build), about some stuttering during video recording - I do have some of those too (although when the record is played back, there's no stutter, so I figure the problem is only in preview), but I'm not sure if this problem started on 2.6.0 or if I had it before and didn't notice - I'd have to rollback to 2.5.0 and take a look, but then I'd have to rebuild that version also since I've deleted the previous version, and I can't spare the time to do it right now; I'll post back on your thread once I can confirm this.
Thanks! , i will install it to give feedback
My congratulations, sent a mp for you.
Nice to see new kernels around here! thanks!! .
This kernel is awesome! The best I've tested in my i9000b !!!
Any chance of a version designed for Android 4.2 ?
wanna know if us is gonna get semaphone for 4.2
@Gurx & @Dimabr10:
Check the OP.
Thanks! We're here to help! Take a look at my website for a fresh version updated for I9000B.
@cronot thanks!!!
I'll test this kernel with some 4.2 version.. Maybe the one from @rubervalrfl !! But I only can do that at night, I'm at my work now....
Thanks!
i'll be glad in receive feedback for my port ROM for i9000B on site.
There is a updated from 12/03/12 cyano's repo version there.
OMG thanks alot
Thanks for your hard work in owr i9000b I would be glad if you can take a look why the mic on the wired headset doesnt work only in owr i9000b :/. Thanks soo much
dancris said:
Thanks for your hard work in owr i9000b I would be glad if you can take a look why the mic on the wired headset doesnt work only in owr i9000b :/. Thanks soo much
Click to expand...
Click to collapse
I am now without the microphone, but once you get home, you can pass a test and feedback, ok?
The wired mic doesnt work on calls or programs. I dont know if the problem have to be solve in the kernel or in rom:/. Hope you can help xD. Thanks.
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.
[KERNEL][4.4] Kernel755 | KerKat | 30/7/2014
Welcome again, to the magical world of kernels.
Kernel755
Adventure time!
AMAZE FEATURES:
CPU OC to 1890 MHz
-O2 optimized!
GPU OC, both 3D and 2D
Over- and undervolting supported!
Moar to come!
WOW! DOWNLOADS:
http://bit.ly/cm11kernel
You are encouraged to add this to your own Drive -- it makes downloading way easier.
SIRIUS DISCLAIMER!
Code:
You are free to use this software, but it's not my fault if (when) you mess something up (because let's face it, you will mess something up).
Please be careful, KerKats are a rare new creature. They might bring lots of fun. Or explosions. Exploding cows not covered in warranty. Also, there is no warranty.
Kernel sources: https://github.com/someone755/android_kernel_sony_msm8x60/tree/cm-11.0
XDA:DevDB Information
Kernel755 - KerKat, Kernel for the Sony Xperia S
Contributors
someone755
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: r2x
Stable Release Date: 2014-07-27
Current Beta Version: a4x
Beta Release Date: 2014-07-30
Created 2013-12-21
Last Updated 2014-08-01
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 or, preferably, post all of that under the "Bugs" section of DevDB and either post a memo of that in the thread or PM me. 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: It's zipped so it's flashable via recovery, though you may also extract the kernel and fastboot flash it. Some alphas come in the form of .elf, though it is recommended that you flash them via fastboot regardless of that.
4. OP is arrogant, I'm gonna call the Internet Police?
A: Deal with it. Especially if asking a question already answered on the first page.
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... KerKat is something like "Kernel" plus "KitKat". This was my best idea at midnight.
7. I'm on stock/CM10/CM9/GB and this kernel doesn't work.
A: This kernel is ONLY for Cyanogenmod 11 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 CM11.
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 CPU 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 newest 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, despite some of them being flashable through recovery. Most of them are dirty builds!!! Meant for advanced users 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/had used it). Please, no big banners or anything, just the name of the kernel. That would be appreciated the most.
12. EYE NEEDZ A DISCUSSON THRED; ARHGAHGHAGHHAHGH!
A: This thread serves as both the development and discussion thread for this kernel. Non-dev discussion is allowed, but please do stay on topic.
And now, thanks!
@RaymanFX -- helping me with nearly all issues and, of course the kernel sources. Also for an old project from which I learned 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!? ) and a heap of other stuff
@hei1125 -- the NOVA kernel, and its' sources
@Forzaferrarileo -- 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 -- lots of helpz
@aebob -- awesome logo idea
@thicklizard -- helping with -O3
@deedwar and @DooMLoRD -- their work on CPU overclocking
Sony and Google -- Android rules
HTC -- Inventing S-ON, forcing me to buy a Sony phone :3
@all -- for being an awesome community! C:
LOL, it's a changelog.
Code:
a4x:
-compatible with OpenSEMC CM11 Beta 3.5 only
-remove all features except for CPU, GPU OC, reboots (supposedly) fixed
-A: all features except for voltage added back
-A: (figured out a way to not make the changelog confusing as fook)
-B: Intelli_plug working and updated
-B: simple GPU governor next to the stock ondemand and performance ones
-C: features added back again
-C: kernel-based MP-Decision, enabled by default
a2c-a3a:
-failed attempts at WiFi module compatibility for Carbon and new Unofficial CM11 builds by whitexp -- need to flash original CM11 modules to use kernel for both (thanks to @piyush95)
-enabled FSync and added fixes for it
-fix for CPU1 jumping around and not sticking with settings
a2b:
-compatible with OpenSEMC CM11 Beta 3.5 only
-*experimental* optional fastcharge
-ye olde potato logo
-MP-Decision now disabled by default
-^brings a TODO: update/fix intelli_plug/incorporate kernel-based MP-Decision
r2b:
-compatible with OpenSEMC CM11 Beta 3.5 only
-*experimental* enabled intelli_plug (disable MP-Decision to enable intelli_plug)
-hopefully fixed reboots and SOD
-downloads moved to public Google Drive folder
r2: [URL]bit.ly/r2kitkat[/URL]
-compatible with OpenSEMC CM11 Beta 3.5 only
-CPU OC back thanks to work by @deedwar.
-both 2D and 3D GPU OC
-GPU governor -- again, note that there is only one so leave that setting as it is!
r1: [URL]http://bit.ly/1aae0xy[/URL]
-no CPU OC
-removed extra schedulers
a1: [URL]http://bit.ly/1ckwMnR[/URL]
-initial release
--O3
-CPU OC (1.7GHz)
-All governors from POTATO (4.2.x) and PIE (4.3.x) kernel (lots of 'em)
-All schedulers from POTATO (4.2.x) and PIE (4.3.x) kernel (zen, fifo, fiops)
You be cray bro! Can't wait for your first r#!
Sent from my amazing Xperia S running RaymanFX's 4.4
Don't know what's wrong but this Kernel made my phone lagging as hell and unusable..
My rom is untouched cm11.
---------- Post added at 04:01 PM ---------- Previous post was at 03:50 PM ----------
Okay looks like the "Hyper" governor caused all my problems.
But also with other governor it laggs and cpu always stays at 384 mhz and gpu always on 177 mhz. This happens even with "performace" governor.
Even recovery laggs as never before. This kernel has many, many problems for me.
Also flashing just the open semc zip takes verry long, it's flashing for five minutes now!
FAQ, points 1, 4 and 5.
You should show some respect, I didn't say anything against you I just reported my problems.
FAQ number 4.
There's a reason DevDB exists. You wanted to report a problem? Use what is to be used.
I give respect where it's due. And so should you.
I'm here with my phone and can't use DevDB.
Hi
Can you make it as a flashable zip please
Sent from my Xperia S using xda app-developers app
zaidx said:
Hi
Can you make it as a flashable zip please
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
Read F.A.Q. #10 xD
Sent from my Xperia S using xda app-developers app
moe18 said:
Read F.A.Q. #10 xD
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
Haha thanks
Just noticed
Sent from my Xperia S using xda app-developers app
androidlover007 said:
I'm here with my phone and can't use DevDB.
Click to expand...
Click to collapse
I'm here with my phone too and I can use DevDv. Please use browser.
Sent from my LT26i using xda app-developers app
bitoyz13 said:
I'm here with my phone too and I can use DevDv. Please use browser.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
Comic sans as main font wtf
Great
Good work
@someone can u please provide me link to kernel for ( android 4.2.2 ) plzzzzz
Do a search. Not my rules, XDA's.
I make a new thread for every version, if that's what's confusing you...
someone755 said:
Do a search. Not my rules, XDA's.
I make a new thread for every version, if that's what's confusing you...
Click to expand...
Click to collapse
I tried but I can't find it, cmon man please just provide me the link
Edit: never mind I tried the search button again and whhoooop... "there" I found kernel
Antutu score??
Xperia S1
Benchmarks are a way of wasting time. AnTuTu, at least. And Quadrant.
You are free to test and compare, scores vary by device, so a score of mine means nothing to you,
Hi oneplus2 people!
This is my modified kernel with some kernel optimizations and some compiler optimizations.
The goal of abyss is to achieve improved performance/battery without the cost of stability.
I will not be overhauling this project with changes that are not logical to add.
This kernel should work on the latest 7.x.x roms like CyanogenMod.
It might work on other roms, but there will be little support for them.
How does one achieve this?
- build kernel with an optimized toolchain
- use compiler optimization flags (experimental)
- remove redundant code
- improve existing code with more efficient code
- etc. (most are not so easy to explain)
This kernel is built with mdalexca's latest UBER GCC 4.9.
Is there actually a performance improvement?
With all the changes added up, there should be. Whether or not one notices the difference is another thing.
For those interested in how the kernel optimizations will benefit/work, please look at my github source and read the commit messages.
For those interested in how the compiler optimizations/hacks will benefit/work, please look at this article.
Downloads:
Latest release
BasketBuild
Source:
GitHub
This was made by request from dsst22 who also tested this bad boi like crazy.
XDA:DevDB Information
abyss kernel for the OnePlus 2, Kernel for the OnePlus 2
Contributors
kwoktopus, dsst22, OnePlus, grarak, The Flash, arter97, Lord Boeffla, frap129, Linux, Google, CAF, a bunch of other major OEMs
Source Code: https://github.com/abyss-kernels/oneplus2
Kernel Special Features:
Version Information
Status: Nightly
Current Stable Version: 1.20
Stable Release Date: 2016-12-05
Created 2016-12-05
Last Updated 2016-12-13
Key Changes:
- upstream interactive governor (with Flash 1.0 profile by The Flash) (Google and CAF)
- upstream cpufreq driver (Google and CAF)
- upstream cpu-boost driver (Google and CAF)
- upstream random driver from Linux 4.1.31 (performance..!)
- slub/slab/slob/vmalloc patches
- flar2's slightly modified thermal driver
- using Linaro's power efficient workqueues throughout kernel
- using Adreno idler by arter97 to reduce frequency scaling without performance cost
- using power efficient "relaxed" macros throughout kernel (assembler)
- KCAL Control Driver by Savoca
- Android-Keyboard patch, use your device as an external keyboard!
- too many to list here, check out my source
How to install:
Place zip in to your internal storage
Place current ROM zip on to your storage
Boot into TWRP recovery
(If you're coming from a different kernel, dirty flash current ROM)
Flash kernel zip
Reboot
Don't like the defaults?
Use Kernel Adiutor to change the settings!
Frequently Asked Questions:
Is this a custom kernel?
I was asked this question once, and it posed as a real good question. I do not consider abyss to be a "custom kernel" per se, but more so as a modified kernel. The patches and features that go into this kernel do not make it customizable. What they do is improve what has already been implemented. It is like swapping a car's engine for a better one rather than just adding LED flooring lights and fancy car mats.
Can you add [this] and [that] feature?
Something I pride myself with this kernel is that it does not have a bunch of random, useless features or patches mashed into it. Everything put into this kernel is thought out and tested. I see a lot of works being made popular because it has [this] and [that] feature when really, it's nothing revolutionary. As a matter of fact, most things added to any kernel will not make it 5x better than any other kernel. Most of the time, simple is better; and in this case it definitely is!
For me
Thanks! I'll give it a go.
Giving it a go
Yess! Been waiting for this ever since i saw your OP2 repo!
Does this kernel install on a f2fs formatted system?
suraj.das said:
Yess! Been waiting for this ever since i saw your OP2 repo!
Click to expand...
Click to collapse
You can thank @dsst22 for helping with testing, or else you would have waited a very long time :silly:
socialdistortion said:
Does this kernel install on a f2fs formatted system?
Click to expand...
Click to collapse
I have not made any file system changes to the kernel. If the stock CM kernel supports, then this one will too.
Is kcal support present..??
chl1810 said:
Is kcal support present..??
Click to expand...
Click to collapse
unfortunately no.
good to see new kernel for our device, thanks and good luck
suraj.das said:
unfortunately no.
Click to expand...
Click to collapse
I wish it had
chl1810 said:
I wish it had
Click to expand...
Click to collapse
I can remember the YoshiShaPow falcon kernel
chl1810 said:
I wish it had
Click to expand...
Click to collapse
In the future
PeterImmel said:
I can remember the YoshiShaPow falcon kernel
Click to expand...
Click to collapse
You can probably see how much I've grown as a developer since then too :angel:
Works on a f2fs filesystem based rom. Testing it now...
Edit: No obvious bugs at the moment. Is it possible to implement some sort of charging control. The USB charging speed is super slow (on both this kernel and stock CM kernel).
kwoktopus said:
In the future
Click to expand...
Click to collapse
Nice!! thank you!!
Pretty smooth haven't found any bugs. Love the simplicity.
I can't imagine what it would be like with a little over clock.
adame09 said:
Pretty smooth haven't found any bugs. Love the simplicity.
I can't imagine what it would be like with a little over clock.
Click to expand...
Click to collapse
I trust the engineers that designed the chip to choose a safe maximum clock speed. Here's a pretty good article on the risks vs benefits, which outline some strong points.
But, if I were to add it, I would set the max value at boot to stay as stock values; so I'll leave it up to @dsst22 to decide.
I'll try this out for you dude. Impressive what you've done.