Related
Boeffla Samsung Kernel by AndiP
Ported and compiled by Hbohd and P$T
For i9305
Introduction
Note: The 4.x kernels are only for Samsung based 4.1.x roms!!! Do not install it on CM or AOSP based roms!!!
The 5.x kernels are only for Samsung based 4.3 roms!!! Also do not install it on CM or AOSP based roms!!!
After ausdim's contribution to porting variety of kernels to our phone, I am here to continue his work (he won't maintain it any longer because he simply doesn't own this phone now). Updates will be made as soon as Andi will push them to github.
Here is original thread of i9300 boeffla kernel - CLICK
Here is thread with boeffla ported by ausdim - CLICK
Info
Kernel is compiled using Linaro 4.9.1 with some required changes for our i9305:
No FM radio
No CMA_DMA
No flash and load in Boeffla App
New 'Hbohd preset' and 'PST preset' which are just our everyday use settings.
New 'Hbohd' and 'PST' equalizer preset - just our favorite.
Apart from that, everything is same as in i9300 version.
Please for any questions problems or anything else ask here and not on I9300 thread.
Credits
P$T (for helping hand with compiling and endless patience and time)
Ausdim (basing on his work and he always gives helping hand)
Yank (his endless patience and knowledge to help with any issue)
AndiP (for kernel base and another kind help)
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in CWM recovery and safely store your personal data before you flash a new kernel.
Source:
Here it is, github link! - CLICK
5.2 STABLE compiled with linaro 4.8.3 toolchain -->HERE
Newest version 5.3-beta7 compiled with linaro 4.9.1 toolchain (new ramdisk NE4) --> HERE
Camera bug info:
It appears that some people (like me) have problem with camera. In exactly THIS situation: do full wipe, flash sammy rom+boeffla kernel, reboot and launch camera. Effect? Camera closes with "camera failed" popup.
Possible solution:
1. Read this thread and follow steps --> click
2. Flash Sammy Rom with stock Sammy kernel, run the camera, take a photo, then reboot to recovery and flash my ported kernel
3. Flash Sammy Rom with stock Sammy kernel, run the camera, take a photo, grab file (SlimISP_XX.bin, where XX differs between phones) from /data/cfw/ and backup it where you want. Then if you can always copy it to /data/cfw if your camera doesn't work with my ported kernel. (ATTENTION: Unfortunately this file does not always appear - still don't know why )
Possible explanation, my own research:
I found out that people with ZD and GD will have camera working always. Why? Because these (SlimISP_XX.bin, where XX differs between phones) files are packed within kernel (zImage exactly) and ONLY THESE two are provided by Samsung in their opensource release... Interesting, isn't it? For example, I have GH version, which I may add to zImage manually, however adding more of them breaks the size limit for boot partition, so it's impossible to have all these versions together. However, stock kernel somehow has them, don't know how because zImages aren't extractable.
And just to confirm my theory, I've compiled a kernel with mine version of camera firmware, made full wipe, installed sammy rom+my kernel, rebooted, launched camera and voila - it worked
Thus, we has to live with this bug unless Samsung do something about it or someone else proves me that I'm wrong
Hbohd said:
I compiled it after adding my own script for zzmoove 0.5 settings, so you all have them in boeffla app. Therefore I need to explain what i changed (it is just for testing purposes, I don't know yet if it is better/worse etc).
I enabled early demand (new feature from 0.5 version):
And also enabled lcdfreq scaling with standard values:
Click to expand...
Click to collapse
Installed let see how it goes...
Good work
Tank's
Sent from my GT-I9305 using Tapatalk 2
Hbohd said:
I compiled it after adding my own script for zzmoove 0.5 settings, so you all have them in boeffla app. Therefore I need to explain what i changed (it is just for testing purposes, I don't know yet if it is better/worse etc).
I enabled early demand (new feature from 0.5 version):
And also enabled lcdfreq scaling with standard values:
Click to expand...
Click to collapse
Thanks.
Do you have any link or something where we can read about zzmoove governor tunables? I was searching, and searching and nowhere have I found a good explanation of all parameters.
I should probably look into sources you just gave a link for, but I am too tired atm.
Edit:
Oh that wasn't link to sources, but it doesn't matter, there has to be one somewhere in Boeffla thread.
Sent from my GT-I9305 using Tapatalk 2
My 'sources' are only one file - defconfig. The rest is completely same as Andi's sources
And for any explanation of zzmoove configurables - there is some documentation, quite well explained: https://github.com/andip71/boeffla-...48257af1b13/drivers/cpufreq/cpufreq_zzmoove.c
Cheers
Thanks for the port.
Over night I find this one better on battery than the last port. See how it goes with a bit of heavy usage today.
Sent from my GT-I9305 using Tapatalk 2
Hi Hbohd. So, let me see if I get it: this port will no longer be updated, and you are now the good guy that will continue to update Boeffla kernel to our beloved I9305?
kazoum said:
Hi Hbohd. So, let me see if I get it: this port will no longer be updated, and you are now the good guy that will continue to update Boeffla kernel to our beloved I9305?
Click to expand...
Click to collapse
Yes, you are completely right Ausdim has even mentioned in his thread that he no longer owns our device (i9305) so I decided to ask for his permission to continue his job here !
I am quite in love with usage results of Boeffla kernel, therefore you do not have to worry about frequent updates
Hbohd it will continue the port of the boeffla kernel since i moved to the i9505.
Also i see Andip make some changes to the boeffla sound driver so it will work better.
Thank's
After 1 day with new kernel I can say the battery improve are the best an till now. Great job
Sent from my GT-I9305 using Tapatalk 4 Beta
Nice.. good job man..
Sent from my GT-I9305
Hbohd said:
Yes, you are completely right Ausdim has even mentioned in his thread that he no longer owns our device (i9305) so I decided to ask for his permission to continue his job here !
I am quite in love with usage results of Boeffla kernel, therefore you do not have to worry about frequent updates
Click to expand...
Click to collapse
Well, I'm sad that a developer leaves this phone, but it is awesome to know that Boeffla will continue to be ported to I9305! The best part is the frequent updates Thumbs up!
I'm gonna try your port and will say something later.
beta6
I found 2.12beta6 very smooth on my wife's s3 (i9300) - is it possible to have beta6 for our device? (i9305)
dyy said:
I found 2.12beta6 very smooth on my wife's s3 (i9300) - is it possible to have beta6 for our device? (i9305)
Click to expand...
Click to collapse
What if I told you...
Beta7 is better than beta6
Thanks for your work.
Do you have any information about problems with distorted sound? It happens randomly here, and someone else reported the same here in this thread.
Have you used Perseus kernel? What do you think about 'Master sequence', that is calibrated colors? I am missing that feature (well, that colors.) a little, so I'm just asking if there is any chance we get it too, or you plan to stay strictly with pure Boeffla source?
Sent from my GT-I9305 using Tapatalk 2
kazoum said:
What if I told you...
Beta7 is better than beta6
Click to expand...
Click to collapse
Beta7 is with zmoove 0.5 which is unstable at the moment - beta6 with 0.3
Besides beta6 is so great on my wife's phone that I'm afraid of changing anything
Sent from my GT-I9305 using Tapatalk 2
!crazy said:
Thanks for your work.
Do you have any information about problems with distorted sound? It happens randomly here, and someone else reported the same here in this thread.
Have you used Perseus kernel? What do you think about 'Master sequence', that is calibrated colors? I am missing that feature (well, that colors.) a little, so I'm just asking if there is any chance we get it too, or you plan to stay strictly with pure Boeffla source?
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
Sincerely, I haven't experienced any random distortions of sound, everything works great. Obviously, if you raise headphone or speaker volume too high, it may be distorted, but it is understandable.
Or did you want to mention the problem with distorted/freezing/stuttering audio on screen-off? That was discussed and it might be caused due to too low screen-off frequency or too high sampling_rate and sampling_rate_sleep_multiplier. If it's the problem, try to change to zzmoove-optimised as it has this values changed a little bit.
About Perseus' screen calibration settings... As for now, introducing such thing would require adding multiple scripts to support variety of configurations for it (in boeffla app), change app to stweaks (which is quite tough task) or wait for new app which will come in some time, made by Andi (and in my opinion, will let us easily configure what we want).
What's more, personally I liked these calibrated colours, however, original colours also seem good to me So nowadays, I do not need it, although I might look at it in my free time and see what can I achieve
dyy said:
Beta7 is with zmoove 0.5 which is unstable at the moment - beta6 with 0.3
Besides beta6 is so great on my wife's phone that I'm afraid of changing anything
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
The fact is, that ausdim released beta4 or 5, I don't remember exactly, and then was my release beta7. And we somehow skipped beta6, you are right! However if I were you, I wouldn't take zzmoove 0.5 as 'unstable'. It introduces a great deal of new configurables that, I suppose will be really beneficiant in the future (when we all will learn what they mean ).
Version 0.5 is ONLY unstable when you are changing governors frequently. Otherwise, it is really efficient and bettery-friendly one (same as 0.3). In addition, it's my beloved governor since its start
Furthermore, new betas always consist of other updates (like Linux kernel upstream to 3.0.82, fixes, optimizations) so it is always worth to use the newest one!
As for now, you may stay with your actual beta version or wait for next update. Andi is testing comparison between zzmoove 0.3 and 0.5 right now, so he haven't pushed any sources, therefore I can't release any new update We are all impatiently waiting for the results i think!
Anybody experienced a problem when the phone CPU is stuck in the max CPU frequency when the phone is plugged in to the PC using USB connection?
I'm using zzmoove battery profile..
Sent from my GT-I9305 using xda app-developers app
inzomnia said:
Anybody experienced a problem when the phone CPU is stuck in the max CPU frequency when the phone is plugged in to the PC using USB connection?
I'm using zzmoove battery profile..
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Have the same problem, no matter the governor i choose.
I try zzmove battery and pegasusq boeffla battery saving
!crazy said:
Thanks for your work.
Do you have any information about problems with distorted sound? It happens randomly here, and someone else reported the same here in this thread.
Have you used Perseus kernel? What do you think about 'Master sequence', that is calibrated colors? I am missing that feature (well, that colors.) a little, so I'm just asking if there is any chance we get it too, or you plan to stay strictly with pure Boeffla source?
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
I had this issue with boeffla but only when i used rxtreme rom, i never have it with ripper rom!
Hello community,
I am a rookie in the subject of kernels/roms and I would love to have some precious help from any1 that knows even the smallest of information. I recently installed CM kernel and CM nightly 0422. The thing is, I read in many forums (in here as well) that there is a kernel that can boost battery life to its max, Franco Kernel. But I also read that it is somehow incompatible with CM 10+ and causes bootloop if you install it with CM already in phone. What I can't understand is why can't I just simply replace CM kernel (like stock kernel was replaced by CM kernel) by Franco Kernel? What is the fact that I am missing?
ALL (and I mean ALL) help will be highly appreaciated, thanks for your time
T.
f33d_me_plz said:
Hello community,
I am a rookie in the subject of kernels/roms and I would love to have some precious help from any1 that knows even the smallest of information. I recently installed CM kernel and CM nightly 0422. The thing is, I read in many forums (in here as well) that there is a kernel that can boost battery life to its max, Franco Kernel. But I also read that it is somehow incompatible with CM 10+ and causes bootloop if you install it with CM already in phone. What I can't understand is why can't I just simply replace CM kernel (like stock kernel was replaced by CM kernel) by Franco Kernel? What is the fact that I am missing?
ALL (and I mean ALL) help will be highly appreaciated, thanks for your time
T.
Click to expand...
Click to collapse
first off.. there is no magic pill to give your phone for battery life. battery life mostly depends on your personal usage, your personal setup, your apps used, and most importantly the quality of your phone/data connection. everything else is minor for battery life, including kernels.
cm uses CAF as its base now, they went away from aosp(like most kernels here). so everything that is aosp based is not compatible with cm anymore. franco kernel is aosp based(most kernels are). there are a few kernels that are CAF based built just for cm and cm based roms.
simms22 said:
first off.. there is no magic pill to give your phone for battery life. battery life mostly depends on your personal usage, your personal setup, your apps used, and most importantly the quality of your phone/data connection. everything else is minor for battery life, including kernels.
cm uses CAF as its base now, they went away from aosp(like most kernels here). so everything that is aosp based is not compatible with cm anymore. franco kernel is aosp based(most kernels are). there are a few kernels that are CAF based built just for cm and cm based roms.
Click to expand...
Click to collapse
Thanks for your time and your answer
First of all, I know for myself that there is no magic pill about battery life, I just read in too many threads that FK added a good portion of battery life (with same use of phone like when it had CM) ! Moreover it allows you to overclock (my) Nexus5 beyond 2.2GHz, something that CM doesn't allow you too (I know that overclocking kills battery, I just want to test something). What I don't understand is how can FK mess up with CM when both are different kernels and by installing FK over CM means that FK replaces CM. There is no CM in the end, only FK. Or not...? What have I understood wrong?
Thanks again
f33d_me_plz said:
Thanks for your time and your answer
First of all, I know for myself that there is no magic pill about battery life, I just read in too many threads that FK added a good portion of battery life (with same use of phone like when it had CM) ! Moreover it allows you to overclock (my) Nexus5 beyond 2.2GHz, something that CM doesn't allow you too (I know that overclocking kills battery, I just want to test something). What I don't understand is how can FK mess up with CM when both are different kernels and by installing FK over CM means that FK replaces CM. There is no CM in the end, only FK. Or not...? What have I understood wrong?
Thanks again
Click to expand...
Click to collapse
yes, franco would replace cm kernel if all worked right. but what you are doing is replacing cm kernel with franco kernel, but cm rom stays on your phone. franco kernel is incompatible with cm rom. since franco is aosp and cm is caf, your phone would never boot up all the way.
simms22 said:
yes, franco would replace cm kernel if all worked right. but what you are doing is replacing cm kernel with franco kernel, but cm rom stays on your phone. franco kernel is incompatible with cm rom. since franco is aosp and cm is caf, your phone would never boot up all the way.
Click to expand...
Click to collapse
So, if I am getting your point right, since one is aosp and the other is caf THAT is the reason why CM doesn't uninstall and will exist together with franco? Is there a way to permanently delete CM in order to install franco? Maybe to go back to stock kernel then install FK?
f33d_me_plz said:
So, if I am getting your point right, since one is aosp and the other is caf THAT is the reason why CM doesn't uninstall and will exist together with franco? Is there a way to permanently delete CM in order to install franco? Maybe to go back to stock kernel then install FK?
Click to expand...
Click to collapse
its not about the kernel, its about the rom. they are different things. when you flash a kernel(any), it replaces the kernel thats on your phone(kernels come with roms, cm kernel with cm rom). cm rom includes cm kernel, both are built from caf source. franco kernel is aosp, it is not compatible with cm rom. it has nothing to do with cm kernel, it replaces cm kernel when flashed. but you will never boot up your phone because it isnt compatible with cm rom.
simms22 said:
its not about the kernel, its about the rom. they are different things. when you flash a kernel(any), it replaces the kernel thats on your phone(kernels come with roms, cm kernel with cm rom). cm rom includes cm kernel, both are built from caf source. franco kernel is aosp, it is not compatible with cm rom. it has nothing to do with cm kernel, it replaces cm kernel when flashed. but you will never boot up your phone because it isnt compatible with cm rom.
Click to expand...
Click to collapse
ok, finally I got it, thanks to you Last question... is there a way to get FK now or am I just locked to caf due to CM "for life"? which way (if there is any at all) in your opinion is the best way to go from CM to FK? maybe go back to stock rom/kernel then flash FK? Will this work?
f33d_me_plz said:
ok, finally I got it, thanks to you Last question... is there a way to get FK now or am I just locked to caf due to CM "for life"? which way (if there is any at all) in your opinion is the best way to go from CM to FK? maybe go back to stock rom/kernel then flash FK? Will this work?
Click to expand...
Click to collapse
no, they arent compatible at all. you can not use franco kernel with any cm based roms. you can change roms and use franco kernel with it, any aosp rom or even the stock rom. but cm isnt compatible at all with franko kernel.
simms22 said:
no, they arent compatible at all. you can not use franco kernel with any cm based roms. you can change roms and use franco kernel with it, any aosp rom or even the stock rom. but cm isnt compatible at all with franko kernel.
Click to expand...
Click to collapse
Thanks man !!
f33d_me_plz said:
Thanks man !!
Click to expand...
Click to collapse
If your looking for a good CAF kernel to run with a PAC or CM based ROM. I'd recommend the ElementalX CAF kernel. It's very stable, rich features, great performance and great battery life. Make sure to read the OP for directions and if you decide to try it out download the ElementalX R38 version with the aromma installer (not the express version) As with running any new kernel run it for a few days minimum to allow for it by on settle in.
There is another option for you to explore too - http://forum.xda-developers.com/google-nexus-5/development/cm11-users-heres-how-aospnon-caf-t2626961
This allows you to run a script that will basically De-CAF your rom and allow you to run a AOSP kernel on CM11ROMs.. Be sure to read the OP. It works with many CM11 and CM based ROMs, but not on all the newest versions. Definitely worth checking out.
xdrc45 said:
If your looking for a good CAF kernel to run with a PAC or CM based ROM. I'd recommend the ElementalX CAF kernel. It's very stable, rich features, great performance and great battery life. Make sure to read the OP for directions and if you decide to try it out download the ElementalX R38 version with the aromma installer (not the express version) As with running any new kernel run it for a few days minimum to allow for it by on settle in.
There is another option for you to explore too - http://forum.xda-developers.com/google-nexus-5/development/cm11-users-heres-how-aospnon-caf-t2626961
This allows you to run a script that will basically De-CAF your rom and allow you to run a AOSP kernel on CM11ROMs.. Be sure to read the OP. It works with many CM11 and CM based ROMs, but not on all the newest versions. Definitely worth checking out.
Click to expand...
Click to collapse
Thanks for your interest and time! I will sure check both your ROM and the De-CAF script soon and post my opinion/experience ! For newbies like me that are reading this post, here is a quite enbrightening thread about CAF and qualcomm processors (although it's Reddit, it's quite explanatory).
Peace!
T.
f33d_me_plz said:
Thanks for your interest and time! I will sure check both your ROM and the De-CAF script soon and post my opinion/experience ! For newbies like me that are reading this post, here is a quite enbrightening thread about CAF and qualcomm processors (although it's Reddit, it's quite explanatory).
Peace!
T.
Click to expand...
Click to collapse
Sorry, I forgot to paste the link cheers ! http://www.reddit.com/r/Android/comments/1rt9md/eli5_what_is_caf_why_is_cm_going_caf_affects_the/
Hello all,
Very grateful for any help at all. I just flashed the latest AOKP nightly (20140907 v4.4.4) onto my Nexus 5 and I'm looking for a kernel that supports USB FastCharge (the default kernel, 3.4.0 Cyanogenmod g186e370r1 does not). So far I've tried:
Franco r63
Code Blue r350
TeamAT Next v0.10 & v0.11b
Flashing any of these results in failed boot (hung at initial 'google' boot screen). Thankfully it's easy enough to restore 'boot' and start over.
I've learned that I need a CM/CAF kernel but the last few I tried still fail to boot.
I *really* love my fastcharge option...but I'm running out of options...
Any suggestions?
Different rom.
If you need CAF, chaos and elementalx are kernels you should try. Been ages since I've used chaos but in use the AOSP version of elementalx so I can say that has fastcharge for sure.
Sent from my Nexus 5 using Tapatalk
rootSU said:
If you need CAF, chaos and elementalx are kernels you should try. Been ages since I've used chaos but in use the AOSP version of elementalx so I can say that has fastcharge for sure.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
elemental x works well you have the aroma installer to boot
Hello guys,
I'm new to Nexus 5 as well.
I have been using Chroma for few months now/
http://forum.xda-developers.com/google-nexus-5/development/rom-chroma-03-31-2015-layers-t3069105
The version I installed on mine is: 8-10-2015 built.
I have been following the post lately,
many people said, 'franco.Kernel' is a good Kernel.
how do I check if I already have franco kernel installed?
I went to About page, it says: 3.4.0-gbebb36b [email protected]#1
also,
if I want to go with franco kernel, what advantages will i get?
do i just need to download this app thru google play to install the franco kernel?
https://play.google.com/store/apps/details?id=com.franco.kernel.free
mrprince123 said:
Hello guys,
I'm new to Nexus 5 as well.
I have been using Chroma for few months now/
http://forum.xda-developers.com/google-nexus-5/development/rom-chroma-03-31-2015-layers-t3069105
The version I installed on mine is: 8-10-2015 built.
I have been following the post lately,
many people said, 'franco.Kernel' is a good Kernel.
how do I check if I already have franco kernel installed?
I went to About page, it says: 3.4.0-gbebb36b [email protected]#1
also,
if I want to go with franco kernel, what advantages will i get?
do i just need to download this app thru google play to install the franco kernel?
https://play.google.com/store/apps/details?id=com.franco.kernel.free
Click to expand...
Click to collapse
That is stock kernel. Recommend using blu_spark (aka code_blue) over franco.kernel. I won't say FK is abandoned, and it is a good kernel, but it's just not updated for the N5 much anymore. Same thing happened to the N7 2013. When the devs move on, you should also.
What do you get with a custom kernel? They say battery, performance, etc. Most of it is negligible at best. You'll need to read the kernel OPs.
hello,
thank you for your reply.
which kernal are you using for your nexus 5 right now?
Aerowinder said:
That is stock kernel. Recommend using blu_spark (aka code_blue) over franco.kernel. I won't say FK is abandoned, and it is a good kernel, but it's just not updated for the N5 much anymore. Same thing happened to the N7 2013. When the devs move on, you should also.
What do you get with a custom kernel? They say battery, performance, etc. Most of it is negligible at best. You'll need to read the kernel OPs.
Click to expand...
Click to collapse
I use elementalx. It is pretty much stock, but you can mod things. The dev's app is great, too.
mrprince123 said:
how do I check if I already have franco kernel installed?
Click to expand...
Click to collapse
Chroma used Franco as the built-in kernel in the past but zephik keeps Google's kernel for a few months.
mrprince123 said:
if I want to go with franco kernel, what advantages will i get?
Click to expand...
Click to collapse
Better battery life? Negligible.
New features like color control, governors (highest impact on battery life), S2W, DT2W, USB fast charge... It varies for each kernel.
mrprince123 said:
do i just need to download this app thru google play to install the franco kernel?
Click to expand...
Click to collapse
I suggest you to read (again & again) the kernel threads on XDA before flashing anything. Franco is a well known kernel but we have other awesome kernels.
so my nexus 5 is stuck on the bootloop or the chroma logo...
I flashed:
1) chroma_hammerhead-ota-2015-10-05.zip
2) tk_gapps-modular-nano-5.1.1-20150927-signed.zip
then the nexus 5 was able to boot fine, and I saw the phone already has SuperSU came with the Chroma ROM
3) I went ahead download the BusyBox, and installed
4) reboot to recovery , and flashed blu_spark_r30-6.0_hammerhead_40fbe53.zip
my phone is not stuck on the ChromaLogo .....
I have also tried,, on the step 3, I flashed without installing Busybox.. It's a no go either..
any help would be appreciated..
Thanks
Primokorn said:
Chroma used Franco as the built-in kernel in the past but zephik keeps Google's kernel for a few months.
Better battery life? Negligible.
New features like color control, governors (highest impact on battery life), S2W, DT2W, USB fast charge... It varies for each kernel.
I suggest you to read (again & again) the kernel threads on XDA before flashing anything. Franco is a well known kernel but we have other awesome kernels.
Click to expand...
Click to collapse
mrprince123 said:
so my nexus 5 is stuck on the bootloop or the chroma logo...
I flashed:
1) chroma_hammerhead-ota-2015-10-05.zip
2) tk_gapps-modular-nano-5.1.1-20150927-signed.zip
then the nexus 5 was able to boot fine, and I saw the phone already has SuperSU came with the Chroma ROM
3) I went ahead download the BusyBox, and installed
4) reboot to recovery , and flashed blu_spark_r30-6.0_hammerhead_40fbe53.zip
my phone is not stuck on the ChromaLogo .....
I have also tried,, on the step 3, I flashed without installing Busybox.. It's a no go either..
any help would be appreciated..
Thanks
Click to expand...
Click to collapse
Here is your mistake: blu_spark_r30-6.0_hammerhead_40fbe53.zip
This kernel version is for Marshmallow.
when i was using lollipop i always went with ak kernel but since ak kernel stopped supporting oneplus one when marshmallow roms began to come i became a bit confused as to which kernel i should use.
so i did a bit of searching with kernels that existed. and the kernels i found that i could use was
1. Sultan
2. Tyr Kernel
3. Andy Kernel
4. Radioactive Kernel
so i was wondering what kernel is the best alternative to ak kernel and if so does that kernel have any problems which makes so i should avoid it?
p.s im open to discussions and even having an idea of what i should do will probly help more then it hurts
calionte said:
when i was using lollipop i always went with ak kernel but since ak kernel stopped supporting oneplus one when marshmallow roms began to come i became a bit confused as to which kernel i should use.
so i did a bit of searching with kernels that existed. and the kernels i found that i could use was
1. Sultan
2. Tyr Kernel
3. Andy Kernel
4. Radioactive Kernel
so i was wondering what kernel is the best alternative to ak kernel and if so does that kernel have any problems which makes so i should avoid it?
p.s im open to discussions and even having an idea of what i should do will probly help more then it hurts
Click to expand...
Click to collapse
It's pretty simple actually CAF kernels usually stated in the title of the kernel thread work on CAF ROMs e.g. Sultan, and any ROM that states CAF in its title works with these kernels.
CM kernel such as Lightning, Boeffla and Andy all state specifically CM12/13 in the thread title and those work with stock CM and ROMs derived from CM source and kernel trees.
Finally Omni based kernels only one works properly (Donkey Kernel) also states Omni in the thread title.
The common denominator is that they all clearly state in the thread title what they are for so there's nothing to discuss on which ones to be used for which ROM. In regards to quality that's a bit trickier as we all like different things in a kernel and personally I'm a big fan of Boeffla when I'm on CM13 cause it works great and the app is very intuitive. I've also tried Andy kernel and its got a good mix of features. I'm on Omni 5.1.1 nightlies so I'm on the stock kernel but when I move back to Marshmallow I can update on kernels
Sent from my A0001 using Tapatalk
Renosh said:
It's pretty simple actually CAF kernels usually stated in the title of the kernel thread work on CAF ROMs e.g. Sultan, and any ROM that states CAF in its title works with these kernels.
CM kernel such as Lightning, Boeffla and Andy all state specifically CM12/13 in the thread title and those work with stock CM and ROMs derived from CM source and kernel trees.
Finally Omni based kernels only one works properly (Donkey Kernel) also states Omni in the thread title.
The common denominator is that they all clearly state in the thread title what they are for so there's nothing to discuss on which ones to be used for which ROM. In regards to quality that's a bit trickier as we all like different things in a kernel and personally I'm a big fan of Boeffla when I'm on CM13 cause it works great and the app is very intuitive. I've also tried Andy kernel and its got a good mix of features. I'm on Omni 5.1.1 nightlies so I'm on the stock kernel but when I move back to Marshmallow I can update on kernels
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
which kernels works with which rom i already knew but i still respect the answer i got. well the main concern i had was about the quality of the roms and which roms is good for what.
It depends on what you want. For example some devs here around merge a bunch of patches to improve sth. Sometimes i dont know what they are doing. I also started with that but soon i have learned less is more. Than there are kernels with gazillion oft features to choose. Thousond hotplugs and governors etc. Than there are small and simple kernels without such experimental features close to stock. I for example dont want to tune 5 days to improve me results i like it simple. So you have 3 or more different types to choose.
1. experimental maybe unstable kernels with lots of patches
2. kernels with lots of features
3. small and simple and more stable kernel close to stock
There is no best or better kernel. Choose the one you like best.
Its your choice.
You also missed the CAF lightning Kernel built off of AK's caf kernel. It's the best kernel for CAF right now IMO. It's basically all of AK kernel's great features just updated to support CAF marshmallow and bug fixes/ latest commits. Works with synapse and all of the original AK CAF kernel profiles.