Hi titan 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 and maybe 6.x.x roms like CyanogenMod and any other AOSP based rom.
Source links lead to my falcon source because they share the same source
How does one achieve such a compromise?
- build kernel with an optimized toolchain
- use compiler optimization flags (experimental)
- remove redundant code
- improve existing code with more efficient code
- reduce/increase speed of timers (depends on what type of function)
- etc. (most are not easy to explain)
This kernel is built with Linaro GCC 4.9.4 that is optimized for Cortex A7 processors.
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.
Personally, I do feel the performance difference. It is easier to notice the difference with lower level specs like ours.
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 build
BasketBuild
Source:
GitHub
I do not mind if there's some non-development/off-topic discussion here, just no discussion about other works that is nowhere near related to mine.
Also, please refrain from comparing works here; it really kills the spirit of development. Go do that in some other thread.
XDA:DevDB Information
abyss kernel for aosp roms, Kernel for the Moto G 2014
Contributors
YoshiShaPow, arter97, flar2, Christopher83, Cl3Kener, frap129
Source Code: https://github.com/abyss-kernels/falcon
Kernel Special Features:
Version Information
Status: Nightly
Created 2016-05-14
Last Updated 2016-12-09
Main Patches and Features:
- KCAL Control Driver
- kexec hardboot patch for Multirom
- USB Force Fast Charge
- Abyss Optimizations (compiler)
- disabled debugging for more performance throughout
- lots of patches for better performance here and there... too many to list
How to install:
Download kernel from Basketbuild
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 kernel 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 well 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!
First
I'll test
Do you have any preferred settings to tweak the kernel or does it come tweaked out of the box? Thank you.
Ashok Menon 101 said:
Do you have any preferred settings to tweak the kernel or does it come tweaked out of the box? Thank you.
Click to expand...
Click to collapse
Everything is good to go after flashing. The most you could do is increase the Read-ahead size to 258kB or 384kB but there's really no point; it won't do much.
YoshiShaPow said:
Everything is good to go after flashing. The most you could do is increase the Read-ahead size to 258kB or 384kB but there's really no point; it won't do much.
Click to expand...
Click to collapse
Alright, thank you.
Which ROM do you think is the best for this btw? No offence to anyone. I understand that egg-caf goes with everything but which do you prefer? Thank you.
Ashok Menon 101 said:
Alright, thank you.
Which ROM do you think is the best for this btw? No offence to anyone. I understand that egg-caf goes with everything but which do you prefer? Thank you.
Click to expand...
Click to collapse
My current setup is Exodus 6.0 and egg-caf kernel. Sometimes I forget that I'm using a phone (Moto G 2013) that costs less than $200 USD.
New build with modified values; it should improve multitasking performance.
egg-caf-titan-nightly-20160515.zip
YoshiShaPow said:
..... I do not mind if there's some non-development/off-topic discussion here, just no discussion about other works that is nowhere near related to mine.
Also, please refrain from comparing works here; it really kills the spirit of development. Go do that in some other thread. ......
Click to expand...
Click to collapse
As you kindly allow some non-development/off-topic discussion I´d like to ask a question about kernel flashing.
You write in your installing explanation
Boot into TWRP recovery
(If you're coming from a different kernel, dirty flash current ROM)
It´s a thing I often heard before. As an example: When I´m coming from a different kernel (I flashed a custom rom and then changed the kernel) and want to go back to the "stock" one why isn´t it enough to unzip my custom rom and flash the boot.img inside?
Where is the difference to dirty flash the whole rom?
Thx in advance.
Wolfcity said:
As you kindly allow some non-development/off-topic discussion I´d like to ask a question about kernel flashing.
You write in your installing explanation
Boot into TWRP recovery
(If you're coming from a different kernel, dirty flash current ROM)
It´s a thing I often heard before. As an example: When I´m coming from a different kernel (I flashed a custom rom and then changed the kernel) and want to go back to the "stock" one why isn´t it enough to unzip my custom rom and flash the boot.img inside?
Where is the difference to dirty flash the whole rom?
Thx in advance.
Click to expand...
Click to collapse
Your question is not even close to what I mean when I say off-topic :highfive: (it is on-topic). Some kernel developers add scripts, patches, ramdisk modifications, etc in their zips to tune different types of values. The easiest way to get rid of all of that is by dirty flashing the rom, which replaces the /system partition and ramdisk with fresh ones from the dirty flash.
YoshiShaPow said:
Your question is not even close to what I mean when I say off-topic :highfive: (it is on-topic). Some kernel developers add scripts, patches, ramdisk modifications, etc in their zips to tune different types of values. The easiest way to get rid of all of that is by dirty flashing the rom, which replaces the /system partition and ramdisk with fresh ones from the dirty flash.
Click to expand...
Click to collapse
Thx for your fast reply and good to know that my question was on topic.[emoji6] Some devs are very delicate when someone hijacks their thread.
Your answer declares the other files, that can be found in some flashable zip kernels.
Is there something to pay attention of when dirty flashing the same ROM again? Ok,don't wipe data is a clear thing but I think of unmounting partitions etc to don't mess up.
Sent from my Moto G 2014 using XDA-Developers mobile app
Wolfcity said:
Thx for your fast reply and good to know that my question was on topic.[emoji6] Some devs are very delicate when someone hijacks their thread.
Your answer declares the other files, that can be found in some flashable zip kernels.
Is there something to pay attention of when dirty flashing the same ROM again? Ok,don't wipe data is a clear thing but I think of unmounting partitions etc to don't mess up.
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
The Roms updater script will mount the partitions it needs. Just make sure after flashing that you wipe cache and dalvik/art cache. Most gapps have a backup script that prevent it from being removed during dirty flashes. If your gapps are retained, you know you've done it correctly.
YoshiShaPow said:
The Roms updater script will mount the partitions it needs. Just make sure after flashing that you wipe cache and dalvik/art cache. Most gapps have a backup script that prevent it from being removed during dirty flashes. If your gapps are retained, you know you've done it correctly.
Click to expand...
Click to collapse
If someone (a friend oft mine or my cat, not me!) [emoji41] has deleted this backup script because he thought he doesn't need it anymore I think he has to flash gapps again too?
Thx for making things more clear and reminding me not to delete files flippantly.
Sent from my Moto G 2014 using XDA-Developers mobile app
Wolfcity said:
If someone (a friend oft mine or my cat, not me!) [emoji41] has deleted this backup script because he thought he doesn't need it anymore I think he has to flash gapps again too?
Thx for making things more clear and reminding me not to delete files flippantly.
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes you will need to flash gapps again. Make sure that if you still have the backup script to not reflash gapps because I've had conflicts with that before. Not very fun.
YoshiShaPow said:
New build with modified values; it should improve multitasking performance.
egg-caf-titan-nightly-20160515.zip
Click to expand...
Click to collapse
always good to test the new features! downloading :laugh: :victory:
Answer me a question, why should change decipher kernel for egg-caf kernel?
Sent from my Moto G 2014 using XDA-Developers mobile app
DeluxeMark said:
Answer me a question, why should change decipher kernel for egg-caf kernel?
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
Well you should choose:
Decipher: stable,enough features, battery.
Egg: Stable, no extra features, performance.
Performance is much better with egg than decipher.
But in terms of battery, decipher is the clear winner.
I've been using the egg kernel for a few days now with cm13 and it's good enough for me.
Performance is really good. I don't really care about the battery as I always have a charger with me always so I don't really mind.
Overall, egg kernel is pretty good.
DeluxeMark said:
Answer me a question, why should change decipher kernel for egg-caf kernel?
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
How about you answer me this.
OP said:
Also, please refrain from comparing works here; it really kills the spirit of development. Go do that in some other thread.
Click to expand...
Click to collapse
How does one get people to not do something in a thread? Back in the older days, that would be by writing something boldly in the OP. Guess that does not work anymore.
Honestly, you can do whatever the heck you want anywhere else, just not in my thread where I have my posting guidelines set.
Edit: also, I clearly state what is different in my kernel from others in the OP
It was just a question,not a comparison
Sent from my Moto G 2014 using XDA-Developers mobile app
Related
THIS OP IS OUTDATED! WIP!
Hello everybody!
You might or might not have already heard of MultiROM, THE multi-boot mod for the Nexus 7. I have recently found it and have decided to port it for our device.
First of all, it is a very initial release now. Though I have tested multiple cases and didn't find any problem except those in the bug list, bugs can arise. Do have a backup! Also, do read through the whole OP and 2nd post! If you don't understand something, rather read again and/or ask!
For more information on how it works and what it does, I suggest that you read the first few posts in the original thread. Those are very detailed and well-written posts that explain MultiROM in general. Installing roms to USB and Ubuntu/Ubuntu Touch of course doesn't work for our device atm.
Installation
The device must not be encrypted!
You need to flash the modified TWRP recovery that has MultiROM extensions. My version is based on the latest sources with gordon0001's device-specific modifications included. You can keep this recovery if you don't want to use MultiROM anymore and you like TWRP, because the MultiROM extensions don't interfere with other functions, even if the boot sector is not injected.
You have to flash a kernel that is capable of Kexec-hardboot. I compiled iodak's v07 CM kernel and official CM kernel with the patch, choose one of them. I have noticed an approx. 3 sec. vibration at boot with iodak, that's why I have included official CM kernel too.
Finally you have to flash MultiROM.
Links
You can find everything at http://d-h.st/users/Adam77Root/?fld_id=22980#files.
MultiROM_TWRP_X3.zip: The modified TWRP recovery from latest sources with gordon0001's device-specific changes and MultiROM support.
CM_kernel_patched.zip and iodakX3_v07CM_patched.zip: Official and iodak CM kernels with Kexec-hardboot patch.
iodakX3_v07_patched.zip: iodak stock kernel with Kexec-hardboot patch.
MultiROM_P880_v12.zip: The actual MultiROM package. Contains the latest version of Trampoline (the init binary of the system) and MultiROM binaries with all the needed device-specific changes. Even Pong works pretty smooth.
x3_hardboot.diff: Kexec-hardboot patch for 3.1.10 kernel.
mrom_p880.patch: Device-specific changes for Trampoline and MultiROM.
ui.xml: UI layout definition for TWRP for 720x1280 screens with MultiROM additions.
Known bugs
Reboot to recovery doesn't work.
USB tab doesn't do anything. This is because USB host mode (OTG) doesn't work on our device. Will reach out to kholk regarding this.
Sometimes in landscape mode, the default selected rom gets booted on the first touch. This is yet to be investigated.
Changelog
14 August 2013: Initial release
Credits
@Tasssadar for MultiROM, Kexec-hardboot for Nexus 7 and his help with debugging and porting
@mkasick for original Kexec-hardboot implementation
@iodak for his kernel
@gordon0001 for the device-specific TWRP modifications
Every custom modification to devices have risks. Flash these at your own risk!
Have fun and enjoy!
General use
Some notes and instructions regarding general use
For now, I have only provided patched 4.2.2 CM kernels. This means, you have to be on CM or CM-based rom with Android version 4.2.2. Don't try it with stock at the moment in any way. It won't work, but is on the to-do list. As Kexec-hardboot will reach out to devs, it will be supported in every rom ultimately.
In the next two examples, I will refer any official, unofficial, or CM-based roms as CM. Keep this in mind.
I use the word 'injected', because MultiROM is actually injected into the boot partition. It works on any kernel that is capable of doing Kexec-hardboot (and if you don't want to use different kernel (i.e. you will use kernel sharing), it will work on unpatched kernels as well).
I may refer to non-shared kernel method as Kexec(-hardboot) method.
Example scenario of multi-booting CM with CM and kernel sharing
You are on CM with MultiROM-capable recovery, patched kernel and MultiROM-injected and you want to install e.g. CarbonRom as second.
Boot into TWRP, navigate to Advanced->MultiROM and select 'Add ROM'. Since the base rom is CM, you can share the same kernel. It will be faster as there will be no hardboot needed.
The installation steps are easy and it doesn't take more time than a normal installation.
Example scenario of multi-booting CM with CM and different kernel
You are on CM with MultiROM-capable recovery, patched kernel and MultiROM-injected and you want to install e.g. CarbonRom as second.
Boot into TWRP, navigate to Advanced->MultiROM and select 'Add ROM'. Select 'Don't share'.
Continue with installation.
Now, since the target kernel (that is installed with the rom) is very likely not patched, you will have to flash one of my linked kernels to that rom. Do this by selecting 'List roms', selecting the desired rom, than 'Flash ZIP' and flashing one of the kernels I have patched.
You can only share the kernels between the same Android version (i.e. stock base->only stock rom can use shared kernel, 4.2 base->only 4.2 rom can use shared kernel, 4.3 base->only 4.3 rom can use shared kernel, etc.), but this is not the case with the Kexec method. Just keep in mind that for example even if your base rom is CM, for a stock secondary rom you have to flash a stock patched kernel.
The build
Some notes about the build
x3_hardboot.diff: This is the Kexec-hardboot patch for the 3.1.10 kernel. Since it is needed for target kernels as well, I would like to reach out in this post to @arararagi, @demetris_I, @iodak, @kholk, @laufersteppenwolf and @Pesach85 (in no particular order, this is how your threads are in order in Original Android Development forum right now). I and fellow users would be grateful if you could include the patch in the kernel so they can be used as both host and target kernels as well. UPDATE: It doesn't reserve one more megabyte before ram_console from now on.
mrom_p880.patch: This contains all the device-specific patches that are needed to get MultiROM booting and working on the P880. It is built on top of the latest git changes as of today. It also contains some comments about multiple devices compatibility, those are reminders for Tasssadar.
ui.xml: UI layout definition for TWRP for 720x1280 screens with MultiROM additions. Needs to be put into TWRPdir/gui/devices/720x1280/res/. The recovery I have created is based on the latest MultiROM TWRP with @gordon0001's device-specific changes.
You can find links to the upstream MultiROM and MultiROM TWRP in the original thread.
Simply incredible!!! :thumbup:thanks a lot man. I always wanted to try dualboot
Sent from my LG-P880 using xda premium
Awaiting the Patched Stock Kernel to dual boot stock and AOSP Good Work man, hopefully @iodak will be able to patch his kernel by today so i can get modding :3
Nice work man! I have also seen hardboot kernels in the N7 section, but got into the hospital then....
But i will include it for sure when i'm back home
Sent from my Nexus 7 using XDA Premium HD app
tnx for your very nice work
how i can flash twrp ?
i want to flash it on cwm but i cant
edite : thats my fault i am so sorry
penguin449 said:
Awaiting the Patched Stock Kernel to dual boot stock and AOSP Good Work man, hopefully @iodak will be able to patch his kernel by today so i can get modding :3
Click to expand...
Click to collapse
If anybody won't be faster, I will provide it tomorrow.
laufersteppenwolf said:
Nice work man! I have also seen hardboot kernels in the N7 section, but got into the hospital then....
But i will include it for sure when i'm back home
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks! Take your time, rest and get better!
Sent from my LG-P880
Adam77Root said:
If anybody won't be faster, I will provide it tomorrow.
Sent from my LG-P880
Click to expand...
Click to collapse
Don't get me wrong, i would be more then Happy to do it myself, however till my new PC Arrives i wont be able to use a Linux Distro for some time, if there's a method to do this on windows (Natively, can't even run anything in VM's) then point me in the right direction! Sorry for the inconvenience!
penguin449 said:
Don't get me wrong, i would be more then Happy to do it myself, however till my new PC Arrives i wont be able to use a Linux Distro for some time, if there's a method to do this on windows (Natively, can't even run anything in VM's) then point me in the right direction! Sorry for the inconvenience!
Click to expand...
Click to collapse
I didn't get you wrong buddy. I have no problems with making a stock version, just didn't have time for that today.
Sent from my LG-P880
giantic hack
ohhh well the one big giantic hack is coming to our O4X! that`s very nice
thank you for this port and thank you for your fast work? tomorrow with stock and on saturday with android 4.3 ?
Donation sent
Whaaaaaattt?
Just were browsing N7 forum few days ago and saw MultiROM and thought "Ahh these lucky nexus guys, I wanna have it to! " and here we go hahahah
Sent from my OptimusX4HD using xda app-developers app
how can install rom to ext-sd ?
in next version can we have stock rom and miui rom or other custom rom?
tnx
Hey guys, heres iodak stock kernel with kexec patch: https://www.dropbox.com/s/ko752pu1akuvfzh/iodakX3_v07-realms.zip
Btw i theres a problem with the twrp zip package, im gonna try fastboot flash it. Has anyone had success?
Say Whut?
@Adam77Root, you just made me wanna flashing and flashing and flashing one day before I go into vacation, I will try to get some time today and test it!
Thanks so much!
Afro said:
Say Whut?
Adam77Root, you just made me wanna flashing and flashing and flashing one day before I go into vacation, I will try to get some time today and test it!
Thanks so much!
Click to expand...
Click to collapse
You can flash 10 different roms and play with them over your vacation. Thats what vacations are right?
Hehe @JoinTheRealms , you understand me
Wow, I just saw your Iodak Stock Kernel with Kexec patch, verrry nice, now I can use Stock ROMs, too!
Did you already test it?
JoinTheRealms said:
Donation sent
Click to expand...
Click to collapse
Thanks very much!
m.homauon said:
how can install rom to ext-sd ?
in next version can we have stock rom and miui rom or other custom rom?
tnx
Click to expand...
Click to collapse
You can't install to external SD. It could be modified to allow it, but there would be a huge performance decrease. Literally, roms would be lagging too much.
JoinTheRealms said:
Hey guys, heres iodak stock kernel with kexec patch: https://www.dropbox.com/s/ko752pu1akuvfzh/iodakX3_v07-realms.zip
Btw i theres a problem with the twrp zip package, im gonna try fastboot flash it. Has anyone had success?
Click to expand...
Click to collapse
Just was about to reply to your PM.
What kind of problem is with the zip package?
I will update the first posts in the afternoon.
Afro said:
Hehe @JoinTheRealms , you understand me
Wow, I just saw your Iodak Stock Kernel with Kexec patch, verrry nice, now I can use Stock ROMs, too!
Did you already test it?
Click to expand...
Click to collapse
Nah i couldnt get the twrp package to flash so im gonna try with fastboot. But the kernel works, i just swapped the ramdisk from Adam77roots patched kernel with iodak's stock kernel, it should work though
---------- Post added at 07:21 PM ---------- Previous post was at 07:19 PM ----------
Adam77Root said:
Just was about to reply to your PM.
What kind of problem is with the zip package?
I will update the first posts in the afternoon.
Click to expand...
Click to collapse
My twrp failed to flash your twrp.zip package, most likely something on my end though, no one else has reported issues
Notice: Probably won't be keeping up with this much longer. CM has a slew of other commits, but I've only been including the two responsible for the discoloration...
Franco:
I've compiled franco's kernel with two cherrypicks from CM's github: c53fb6d134 and 07cbfb9a9c
These are required for recent nightlies of CM and its derivatives (caveat: if your rom specifically has commits reverted to not require such a workaround, then of course this isn't pertinent to you).
No changes to ramdisk or .config. Compiled using arm-linux-androideabi-4.7 from android ndk r9.
It should go without saying that you shouldn't flash this unless you understand what those commits are for and have a need for them. Those using the "colorfix" zip or otherwise reverting to an earlier liboverlay.so will find that method no longer "works" with newer builds (it spewed errors in dmesg nonstop when it worked).
IMPORTANT: Make sure you update to the new liboverlay.so if you're currently using the old one or you will have problems. Flash this on a rom that doesn't have the corresponding rom-side commits and you will of course have problems too (and I will laugh at you). As well, make sure to remove any addon.d script that you may have been using, if applicable. I don't know if there are multiple "colorfix" zips in circulation, but the one that I came across looks like it creates /system/addon.d/95-cm.sh. After deleting this file, you should be able upgrade/reflash the rom to bring liboverlay.so back up to date. Or if you're lazy/inept, wipe /system and reflash your rom+gapps.
Because of ramdisk customizations (incompatibilities) among roms/kernels, this zip will attempt to patch your existing ramdisk with franco's changes during flash. Things can obviously go wrong, so be ready.
4.4: 2013.11.29 1411ET: [franco-r195-cm-ziddey.zip]
4.4: 2013.11.25 0257ET: [franco-r194-cm-ziddey.zip]
4.3: 2013.10.26 2049ET r193: [JWR] [JSS/JLS]
-------------------------------------
Faux:
I built faux's kernel with the two commits as well.
4.4.1/4.4.2:
Faux: [030u-CM] [030m-CM]
4.4:
Faux: [029u-CM] [029m-CM]
4.3:
Faux: [028u-JSS] [028m-JSS] [028u-JWR] [028m-JWR]
Faux: [027u-JSS] [027m-JSS] [027u-JWR] [027m-JWR]
Note this is an "anykernel" and uses whatever the existing ramdisk is. If switching from Franco (or another kernel that includes a ramdisk), a "reset" kernel is recommended (reflash rom).
Built with arm-linux-androideabi-4.7, with bfd linker instead of gold.
Same as cm10_colorfix.zip?
Thanks alot! I will see if I can comment on any improvement in battery life or performance.
Sent from my Nexus 4 using Tapatalk
I don't think that these two patches will improve performance or battery life.
droidjam said:
I don't think that these two patches will improve performance or battery life.
Click to expand...
Click to collapse
But the use of incompatible library and the constant stream of errors caused by it may impact negatively on them.
Sent from my Nexus 4 using Tapatalk
Thanks alot for doing this.
Will be flashing this soon, all of @ziddey's mods have worked great!
Using this kernel for a while now. Working good if not better.
Thanks ziddey , for filling in such gaps whenever needed. That helps in keeping the ecosystem open to choices
Sent from my Nexus 4
Just flashed will test battery ect
Sent from my Nexus 4 using xda app-developers app
Is there a specific build I should be on when using PAC? I'm on the 16 and even with colorfix I can only use one other kernel that I know of, hells core. Others don't let me pass the boot animation. The same thing happens with this kernel. No colorfix and I used jss
Sent from my Nexus 4 using Tapatalk 4
Thanks a lot, it works great! I hope you will keep this updated when Franco releases a new version.. I should definitely learn how to compile it by myself
Inviato dal mio Nexus 4 con Tapatalk 4
NUNsLAUGHTER92 said:
Is there a specific build I should be on when using PAC? I'm on the 16 and even with colorfix I can only use one other kernel that I know of, hells core. Others don't let me pass the boot animation. The same thing happens with this kernel. No colorfix and I used jss
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
link to kernel source for pac
ziddey said:
link to kernel source for pac
Click to expand...
Click to collapse
RoliSoft said:
According to this https://github.com/PAC-man/android_vendor_pac/blob/cm-10.2/dependencies/mako.dependencies dependency list, the complied kernel for mako is this: https://github.com/zyonee/android_kernel_google_msm
Click to expand...
Click to collapse
And you said as of which build did it stop working, 10/16? There haven't been any new kernel commits since 10/3: https://github.com/zyonee/android_kernel_google_msm/commits/cm-10.2
Further, here's the cm kernel git for comparo: https://github.com/CyanogenMod/android_kernel_google_msm/commits/cm-10.2
https://github.com/PAC-man/android_vendor_pac/blob/cm-10.2/dependencies/mako.dependencies
It uses cm's mako repo.
ziddey said:
And you said as of which build did it stop working, 10/16? There haven't been any new kernel commits since 10/3: https://github.com/zyonee/android_kernel_google_msm/commits/cm-10.2
Further, here's the cm kernel git for comparo: https://github.com/CyanogenMod/android_kernel_google_msm/commits/cm-10.2
https://github.com/PAC-man/android_vendor_pac/blob/cm-10.2/dependencies/mako.dependencies
It uses cm's mako repo.
Click to expand...
Click to collapse
I haven't been able to since I used the 10/9 nightly. If there haven't been any other changes then I don't know why it won't work. I wiped data before going to the nightly on the 16th and it would boot if I didn't flash a different kernel, but if I did then it'd stay on the boot animation forever. It does that for the 20th too, although I didn't wipe data before going to the nightly.
Sent from my Nexus 4 using Tapatalk 4
Thank you thank you thank you!
Stock camera wont start with this kernel for me on latest 2013-10-21 nightly for me.
Fine here. Referring to gallerygoogle and not gallery2
Sent from my phone. Please forgive typos and brevity.
build r192 is available on Franco's thread
http://forum.xda-developers.com/showpost.php?p=46663872&postcount=50533
Uh huh
Sent from my phone. Please forgive typos and brevity.
NEXT RELEASE: 27 AUGUST 2014 GMT+8 0900
With the introduction of so many kernels in the forums, every user just wants his/her phone to enjoy the crisp experience of their device. With ASKP, you get to enjoy the brilliant works of all developers into one small kernel. ASKP, is a modified kernel that merges many tweaks together, just like P.A.C.
ASKP is only run by me and pattyboi for now. Please bear with the slow speed of updates. I'm working on 3.4 for the Galaxy Nexus and also for you guys at the same time.
I promised before, ALL ROMS WILL BE SUPPORTED. But when I say ASKP is fully released. For now, I'll be releasing slowly. So please bear with me.
Supporting Devices:
LG G2
Samsung Galaxy Nexus
Variants of ASKP released for per-ROM basis statuses: http://forum.xda-developers.com/showpost.php?p=53569650&postcount=6
READ THIS FIRST
- There's always a name in each file right? The word at the end is the most important. And of course, make sure the model number is correct.
ONLY TWO WORDS ARE GIVEN FOR SIMPLICITY. STOCK and CAF.
- CAF kernels are for AOSP ROMs. A N/CAF (Non-CAF AOSP) Kernel will also be present upon full release of ASKP.
- ASKP has just started venturing into G2's development, please be patient if there is no support for your ROM yet.
- I am not responsible for any problems incurred on your device. This kernel is not fit to be a daily driver YET. Still in pre-alpha stage.
Changelog To Be Released after Alphas.
Downloads: http://forum.xda-developers.com/devdb/project/?id=4678#downloads
Savoca's Mirror: http://savoca.co/Amperific
Source: https://github.com/AmperificSuperKANG/G2-Kernel.git
Credits:
Everyone. From XDA.
As well as savoca for his awesome file transfer access to me.
Special Thanks to Dorimanx for the help in packing up the boot.img.
Based on: Dorimanx's Stock v20D Source. (Pulled from him as the internet connection I have is incapable of pushing a 1GB+ Source). This is a CLEAN LG Source.
I also want to thank him for his own build script, without it, I couldn't have built kernels as fast as before.
If you'd like to donate to me, Please do so, It'll be used for creating a tracker and an FTP site.
So you're buying yourself a beer. Heheh.
I really thank you!
Donors Hall of Fame:
- nope
XDA:DevDB Information
Amperific SuperKang Project, Kernel for the LG G2
Contributors
Amperific, Dorimanx, pattyboi
Kernel Special Features: Advanced Memory Hotplugging System
Version Information
Status: Testing
Created 2014-06-21
Last Updated 2014-06-21
XDA:DevDB Information
Amperific SuperKang Project, Kernel for the LG G2
Contributors
Amperific, Dorimanx, pattyboi
Kernel Special Features: Advanced Memory Hotplugging System
Version Information
Status: Alpha
Created 2014-06-21
Last Updated 2014-08-26
Nice! And the important advice for You right now: You REALLY SHOULD write which ROMs do You support and which G2 variants.
There are some ROMs based on dr87 sources like SlimKat, and Mahdi ROM itself, there is CarbonROM and PA which use other sources.
Aaand there is CM which didn't even get updated to KK sources, lol.
reas0n said:
Nice! And the important advice for You right now: You REALLY SHOULD write which ROMs do You support and which G2 variants.
There are some ROMs based on dr87 sources like SlimKat, and Mahdi ROM itself, there is CarbonROM and PA which use other sources.
Aaand there is CM which didn't even get updated to KK sources, lol.
Click to expand...
Click to collapse
I don't care. Like I said. I'm a welfare guy, EVERYONE GETS THEIR ASKP DESSERT.
For now, on wich ROMs will this work? I am a noob and don't know about sources and compatibilities...
Sent from my G2 running CloudyG3 on ART
reas0n said:
Nice! And the important advice for You right now: You REALLY SHOULD write which ROMs do You support and which G2 variants.
There are some ROMs based on dr87 sources like SlimKat, and Mahdi ROM itself, there is CarbonROM and PA which use other sources.
Aaand there is CM which didn't even get updated to KK sources, lol.
Click to expand...
Click to collapse
Amperific said:
I don't care. Like I said. I'm a welfare guy, EVERYONE GETS THEIR ASKP DESSERT.
Click to expand...
Click to collapse
NEO2598 said:
For now, on wich ROMs will this work? I am a noob and don't know about sources and compatibilities...
Sent from my G2 running CloudyG3 on ART
Click to expand...
Click to collapse
I think that this is for stock roms as its based on dori's sources.
Sent from my LG-D801 using Tapatalk
NEO2598 said:
For now, on wich ROMs will this work? I am a noob and don't know about sources and compatibilities...
Sent from my G2 running CloudyG3 on ART
Click to expand...
Click to collapse
You're using Cloudy's G3 eh. You're on luck. That's the first one.
Releases In order for Stock G2 and Ported G3 ROMs,
D802 (Released)
D800 (Released)
D801 (Released)
D803
VS980
LS980
After this,
Releases for All devices for Paranoid.
Then,
Releases for All devices for CM.
Also,
Releases for All devices under Mahdi's Sources.
Finally,
Releases for the next MOST requested ROM.
After this, expect features to fly in.
@nimrodsv Go ahead and ask him.
Guys, once again. THIS IS NOT A COPY OF DORIMANX.
I only copied his RAMDisk with his permission. Without it, I wouldn't be able to boot on the majority of ROMs.
The kernel source itself will be different from his indefinitely.
Wow, I am so lucky ☺
I will test it and let you know how is it. Thanks for replying.
Sent from my G2 running CloudyG3 on ART
Can't wait for the d800 PA release. Going to flip my ****.
Sent from my LG-D800 using XDA Premium 4 mobile app
@Amperific i flashed the kernel on CloudyG3 and I see that it has everything what @dorimanx kernel has... Also STweaks.
Sorry to say that, but for now it looks like the Dorimanx Kernel with other name
EDIT: not only STweaks. Governors, Hotplugs, etc, everything is the same, I think You should delete it for now. I think that STweaks can be used by everyone, but well, for now it looks like u copied his kernel and changed the name lol
reas0n said:
@Amperific i flashed the kernel on CloudyG3 and I see that it has everything what @dorimanx kernel has... Also STweaks.
Click to expand...
Click to collapse
Sigh. STweaks is from his ramdisk. And I'm reverting all his commits. by r5, Whatever I don't want won't be there.
Sent from my LG-D802 using Tapatalk
Please read up guides on what comes with a ramdisk and a zImage itself. A boot.img is made from a ramdisk and a zImage. Even though the STweaks app exists, it doesn't mean everything works. I don't have Intelli features inside. so use your eyes please. I'm trying to be kind and patient.
reas0n said:
@Amperific i flashed the kernel on CloudyG3 and I see that it has everything what @dorimanx kernel has... Also STweaks.
Sorry to say that, but for now it looks like the Dorimanx Kernel with other name
EDIT: not only STweaks. Governors, Hotplugs, etc, everything is the same, I think You should delete it for now. I think that STweaks can be used by everyone, but well, for now it looks like u copied his kernel and changed the name lol
Click to expand...
Click to collapse
Amp is a well known dev in the galaxy nexus forum (last that's where I know him and his work from) he's already stated he's using Dorimanx ram disk. So telling this guy to delete his thread is a **** move.
Sent from my LG-D800
YoungDaddy said:
Amp is a well known dev in the galaxy nexus forum (last that's where I know him and his work from) he's already stated he's using Dorimanx ram disk. So telling this guy to delete his thread is a **** move.
Sent from my LG-D800
Click to expand...
Click to collapse
Thank you.
But if you really don't appreciate my work, It's fine. I'll stop.
Not like I don't have other plans.
Anyways, Every development has its start. I admit. I have some dorimanx's commits. I'm reverting them currently till r5. Once we go past r5, I'll start working on pushing commits in.
If you see my development style in tuna, I do things part by part, in a systematic way.
YoungDaddy said:
Amp is a well known dev in the galaxy nexus forum (last that's where I know him and his work from) he's already stated he's using Dorimanx ram disk. So telling this guy to delete his thread is a **** move.
Sent from my LG-D800
Click to expand...
Click to collapse
You guys misunderstood me, meh. I didn't even say anything about the THREAD. It's the first one. The second one is, I just report to the dev what I see, I didn't say that it's a steal or anything, I just said that situation like that exists. Because i saw that there's everything like in dorimanx kernel, than maybe something went wrong with making the kernel.
Oh and about Intelli features, i see there are Intellidemand/Intelliactive govs, EcoMode, Intelli HotPlug, I REPORT it, REPORT, not ACCUSE.
Dang i hate misunderstandings. I appreciate every work and never want to make someone stop his work. Duh.
If dorimanx allowed to share everything with features he added like this now, then it's alright, I just reported in case he didn't allow it and You wouldn't see that or something.
So @Amperific keep going and sorry that u understood me wrong
Finally. We need more kernel devs. Thanks for joining the party!
Amperific said:
Thank you.
But if you really don't appreciate my work, It's fine. I'll stop.
Not like I don't have other plans.
Anyways, Every development has its start. I admit. I have some dorimanx's commits. I'm reverting them currently till r5. Once we go past r5, I'll start working on pushing commits in.
If you see my development style in tuna, I do things part by part, in a systematic way.
Click to expand...
Click to collapse
Keep on doing what you do bro. Can't wait to try some askp goodness on my d800 [emoji1]
Sent from my LG-D800
Sorry. Apologies from me too.
Next few builds,
- Mitigate commits that are not needed
- Bring in ASKP's tweaks
Sent from my LG-D802 using Tapatalk
Amperific, please don't stop your build. Coming from a gnex us users know your kernels are gold. I can't wait to try it out. I'm sure once non gnex users install the kernel they will see the magic. My request for you is a kernel that works with vanir on my d800. I'm a flashaholic so I jump from vanir, aicp, mahdi ect but just can't wait to try this bastard out??????
Sent from my LG-D800 using XDA Premium 4 mobile app
Guys before I sleep,
All Stock variants are up.
And I apologise about the CAF guide.
I briefly scanned through the source and realised that there are different variations of CAF. CMs, and etc. Even LG.
So all variations will be made available as well.
Nights
Do I need to go back on dalvik before flashing this kernel?
Currently i am on ART. If I stay on ART installation is the same? (wipe cache and dalvik then flash the kernel).
Thanks.
Sent from my G2 running CloudyG3 on ART
I was told that dalvik /ART is rom related not kernel
Sent from my VS980 4G using XDA Free mobile app
RealONE Kernel for Moto X 2014!
Only CM or based CM versions like RR,NX...
And only Android M too
Features:
Compiled with UBERTC 4.9.4
Optimized Entropy
FauxSound
Power Suspend
Improved accuracy of MultiCore
CRC disabled by default( 30% extra perfomance on I/O)
Swappiness reduced to 15%
UnderClock CPU (268 Mhz)
Activated Power Eficcient Worqueues
#Governors:
ZZmove
Intellidemand
Smartmax Extreme Power Saver (eps)
Intelliactive
#Hotplugins:
MSM_Hotplug
Intelliplug
Alucard
MSM MP Decision
#I/O Schreduler:
Added Zen
All credits goes to Michel Borges
Thanks Leonardo Augusto
Thanks Faux123
Source of the Kernel on github:
https://github.com/RealOne-Kernel/RealOne-Victara-Kernel
could you give instructions on how to flash a kernel in our device?
marquesini said:
could you give instructions on how to flash a kernel in our device?
Click to expand...
Click to collapse
This is not the place for that.
jlink38 said:
This is not the place for that.
Click to expand...
Click to collapse
oh, ok.
then I dunno, pm me an external link for that ? i really want to try change the kernel, but don't want to mess up the device, i could google it but preffer a recommendation of a tutorial by someone who understands more about it than i dunno.
anyway, thanks.
Hello, your kernel is very good, very fluid and good battery consumption in CM13, it would be possible in the future to add support KCAL?, can change the saturation, contrast, etc., thank you for your work.
[DEV][PATCH] KCAL - Advanced color control for Qualcomm MDSS 8x10/8x26/8974/8084/8939
Great kernel. Has improved battery life quite a bit !
Thanks!! Testing on CM13... Looks good
Good battery consumption.
Sent from my XT1095 using Tapatalk
Great kernel so far, thanks for making a custom kernel for 6.0, I've been waiting for one.
Would it be possible for you to add support for DriveDroid to your kernel?
http://forum.xda-developers.com/showthread.php?t=2196707
https://play.google.com/store/apps/details?id=com.softwarebakery.drivedroid&hl=en
Thxx , give me more feedbackk ! And I'll take a look at suggestions at the weekend guys !!
Can't wait to see what this can do..bout to flash now!!!
some people say they are taking random reboots .. anyone had ? maybe a log for me ?
MichelBorgess said:
some people say they are taking random reboots .. anyone had ? maybe a log for me ?
Click to expand...
Click to collapse
Yes i had that issue, but i reflashed cm, I'll retry tomorrow and get you some logs (hopefully i have time, I'm doing my finals now...).
MichelBorgess said:
some people say they are taking random reboots .. anyone had ? maybe a log for me ?
Click to expand...
Click to collapse
I'll try.its happened a few times to me
---------- Post added at 08:47 AM ---------- Previous post was at 08:39 AM ----------
Where can I post my logcat?
http://pastebin.com/ try this
Your kernel its a dream hahahaha I was waiting for a kernel with fauxsound since I've bought this phone. So, first of all, thank you very much for your kernel and we appreciate your work and your time spent with this kernel. But lets get to the facts:
1) In RR 5.6.0 your kernel cause bootloop;
2) In CM13 (specifically 2015-12-12 build) I had a lot of random reboots and the sound (specifically Play Music and Deezer) sometimes was cracking or just not played;
3) In CrDroid I had the same thing in CM13 but the rom has some serious bugs, so we don't count it;
4) In Nexus Experience 10.0.4 I just had ONE random reboot (take note: the first boot, so lets blame the instability of the rom) and, since then, my phone is working completely perfect.
5) With kernel auditor all of my preferences are saved and sticked after a reboot (in Nexus Experience 10.0.4)
Note: All of the Roms was fresh installed, wiped everything (including internal storage) then installed ROM->GAPPS (NX GApps in Nexus Experience and OpenGApps in the other roms)->KERNEL
Maybe with some work in your kernel and in the newer roms, this phone will gain some fresh air!
Thank you again!
Ps.: not an american guy, so please, I'm sorry for any english mistake
victor19 said:
Your kernel its a dream hahahaha I was waiting for a kernel with fauxsound since I've bought this phone. So, first of all, thank you very much for your kernel and we appreciate your work and your time spent with this kernel. But lets get to the facts:
1) In RR 5.6.0 your kernel cause bootloop;
2) In CM13 (specifically 2015-12-12 build) I had a lot of random reboots and the sound (specifically Play Music and Deezer) sometimes was cracking or just not played;
3) In CrDroid I had the same thing in CM13 but the rom has some serious bugs, so we don't count it;
4) In Nexus Experience 10.0.4 I just had ONE random reboot (take note: the first boot, so lets blame the instability of the rom) and, since then, my phone is working completely perfect.
5) With kernel auditor all of my preferences are saved and sticked after a reboot (in Nexus Experience 10.0.4)
Note: All of the Roms was fresh installed, wiped everything (including internal storage) then installed ROM->GAPPS (NX GApps in Nexus Experience and OpenGApps in the other roms)->KERNEL
Maybe with some work in your kernel and in the newer roms, this phone will gain some fresh air!
Thank you again!
fix in next build
Click to expand...
Click to collapse
Yo guyss ! I redid the kernel, and apparently restarts stopped .. is still simpler, more 'll keep updating
zzmoove
intelliplug
IO Zen
https://www.androidfilehost.com/?fid=24340319927533603
I don't understand this thread. The OP has a different username the one above who has released v2? And why hasn't this been moved to 'original development'?
floepie said:
I don't understand this thread. The OP has a different username the one above who has released v2? And why hasn't this been moved to 'original development'?
Click to expand...
Click to collapse
I just asked for Vinicius post for me , since I had not yet allowed to post in section ...
Hi falcon 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 (and maybe 6.x.x) roms like CyanogenMod and any other AOSP based rom.
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
- reduce/increase speed of timers (depends on what type of function)
- etc. (most are not easy to explain)
Built with Linaro GCC 4.9 optimized for Cortex A7 with vfpv4 technology
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.
Personally, I do feel the performance difference. It is easier to notice the difference with lower level specs like ours.
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:
Discontinued
Source:
GitHub
Asking for ETA's won't be necessary because I use this kernel as my daily driver.
I do not mind if there's some non-development/off-topic discussion here, just no discussion about other works that is nowhere near related to mine.
Also, please refrain from comparing works here; it really kills the spirit of development. Go do that in some other thread.
XDA:DevDB Information
abyss kernel for aosp roms, Kernel for the Moto G
Contributors
YoshiShaPow, arter97, flar2, Christopher83, Cl3Kener, frap129
Source Code: [url]https://github.com/abyss-kernels/falcon[/URL]
Kernel Special Features: MAJOR KEY
Version Information
Status: Nightly
Created 2016-05-10
Last Updated 2016-12-18
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 to abyss?
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 well 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!
Main Patches and Features:
- intelliplug (default hotplug)
- intelliactive governor
- KCAL Control Driver
- kexec hardboot patch for Multirom
- USB Force Fast Charge patch
- Abyss Optimizations (compiler)
- disabled debugging for more performance throughout
- lots of patches for better performance here and there... too many to list
How to install:
Download kernel from Basketbuild
Boot into TWRP recovery
(If you're coming from a different kernel, dirty flash current ROM)
Flash kernel zip
Reboot
Nice job bro ! [emoji3]
Thank you for this awesome kernel [emoji6]
Sent from my Moto G using XDA-Developers mobile app
this work with both cm and aosp or aosp only
zydes said:
this work with both cm and aosp or aosp only
Click to expand...
Click to collapse
It will work on any 6.x.x AOSP based rom (CyanogenMod included). The only roms it will not work with to my knowledge are Omni and SlimSaber.
edit: turns out it works with them
nx rom based cm work?
Can you add OC made be @h2o64 ? Really is a the difference if you do the benchmarks and in real life just a little so is true OC..
zydes said:
nx rom based cm work?
Click to expand...
Click to collapse
Yes, most likely.
Eurofighter_ty said:
Can you add OC made be @h2o64 ? Really is a the difference if you do the benchmarks and in real life just a little so is true OC..
Click to expand...
Click to collapse
I will look into it.
YoshiShaPow said:
It will work on any 6.x.x AOSP based rom (CyanogenMod included). The only roms it will not work with to my knowledge are Omni and SlimSaber.
Click to expand...
Click to collapse
Works just fine with Omni so far, SlimSaber would probably work also. Nice to see another kernel for us from you, Thanks!
amarc78 said:
Works just fine with Omni so far, SlimSaber would probably work also. Nice to see another kernel for us from you, Thanks!
Click to expand...
Click to collapse
Updated the OP and my earlier post. Thanks for testing
Thanks ? this kernel work perfeft
Sent from my Moto G using XDA-Developers mobile app
Carlos Arriaga said:
Thanks this kernel work perfeft
Sent from my Moto G using XDA-Developers mobile app
Click to expand...
Click to collapse
in androidfilehost you have kernel for falcon or condor carlosarinaga
zydes said:
in androidfilehost you have kernel for falcon or condor carlosarinaga
Click to expand...
Click to collapse
Perfect example of OT that development threads should not have. No more of these type of posts^ please.
YoshiShaPow said:
Perfect example of OT that development threads should not have. No more of these type of posts^ please.
Click to expand...
Click to collapse
soory for my post
can u add feature underclock for yuor kernel
zydes said:
soory for my post
can u add feature underclock for yuor kernel
Click to expand...
Click to collapse
Sorry, I won't be adding underclocking to this kernel. There really isn't much of a need for underclocking a phone. In the long run, battery consumption will not be changed, maybe only at the slightest.
Also, the more frequencies added, the slower a CPU governor works. Most governors run calculations based on cpu load, checking whether or not it needs to move up or down a frequency step. By adding more steps, the cpu will throttle slower.
Just updated the kernel with frandom support. Also added some ramdisk modifications to support it.
More entropy == better performance.
egg-caf-falcon-nightly-20160513.zip
Battery backup is good...give a try
It's great to see feedback from the users. New build with modified values; it should improve multitasking performance.
egg-caf-falcon-nightly-20160515.zip
navaneethkom said:
Battery backup is good...give a try
Click to expand...
Click to collapse
Yes, the battery is great, 18 hours standby and i get almost 4h sot, left with 52% right now. Anybody looking for great battery should go for it.