Hi all,
Can you explain the different of kernels? (tytung, Dorimanx, fikret, seadersn, ...)
Which kernel is best for battery, performance, ...
I heard somewhere
Dorimanx kernel is best for performance.
seadersn kernel is best for battery.
tytung kernel is best for stable.
Is that right? I need your experience about these.
Thanks all.
PS: I use HTC HD2 both ICS & GB.
So, "what is the best rom" people now evolved into "what is the best kernel" people?
Kernels/ROMs are subjective, what works for me may not AND DOES NOT HAVE to work out for you. Try each and every Kernel, and settle for the one YOU like.
I have tried tons of different roms and kernels, and settled (provisionally) to slim bean ROM and franco kernel. However, I have noticed that while slim bean includes several scripts ini init.d, franco kernel does not support init.d scripts by default (I have read that this depends on its default initramfs), so that these scripts are not executed at boot. What should I do? Is perhaps the idea that those scripts are for slim bean stock kernel and that actually they should not be run with franco kernel, leading perhaps to some potential conflict? Or am I loosing some functionality in the rom, so that I should resort to one of those several ways to add init.d support to any kernel (such as uni-init and others: http://forum.xda-developers.com/showthread.php?t=1933849)?
Please note that I do not need to add other personal scripts to init.d, I wonder only if I am facing some kind of conflict between rom and kernel. Note also that I am not observing any practical negative effect ATM, I am only wondering if this general situation (rom with init.d scripts, custom kernel disabling them) is on purpose or something that I should fix.
Hi,
Quick question I am still having trouble wrapping my head around the concept about kernels. I am planning to root my nexus 4 and flash a custom rom (purity rom) but am i required to also flash a custom kernel? Or am I suppose to leave the kernel as is?
Thanks!
Next123 said:
Hi,
Quick question I am still having trouble wrapping my head around the concept about kernels. I am planning to root my nexus 4 and flash a custom rom (purity rom) but am i required to also flash a custom kernel? Or am I suppose to leave the kernel as is?
Thanks!
Click to expand...
Click to collapse
Depends upon your requirement .
As an example i use Fast USB charge a lot and is not available in any custom rom .
I also use Headphone volume boost which is yet again a kernel level change.
I would suggest you to use a custom kernel since it also gives better battery than stock .
If you are happy without it then forget about kernels . And in case u plan on flashing one make a CWM backup just in case.,
You could if you want to since you're already flashing custom roms. However, most custom rom come with custom kernel, so when you flash a custom rom it will replace your kernel with it's own. You can manually flash back your stock kernel if you want, using fastboot, but there is a flashable package as well in the Dev section.
Just know that due to codes and drivers, different kernels work with different roms. If you flash a 4.3 kernel to a 4.4 rom, it might lack certain necessary driver, such as PRIMA, so your wifi will no longer work. (You can fix this by flashing dePRIMAtor). CyanogenMod use Code Aurora Forum drivers, so if you use a kernel that doesn't support CAF, the screen colors will be messed up (you can lash a colorfix package which replace it with the non-CAF liboverlay.so).
A lot of people get wrapped too far up into flashing kernel and thinking it determine everything (performance + battery life) in their phone. As much of a heavy flasher that I am, I am willing to bet that you generally get the best battery life and stability just running stock. I did my own trial for this, with stock rom and kernel, the phone staying cooler and screen on time was longer. This is just my personal experience, it varies for each person.
But I mainly use custom kernel for features. Such as kernels that incorporate Faux color and sound, this allows changing their settings for much a better screen color and making the speaker louder. I also use the sweep2wake/sleep feature to turn on and off the screen.
If you intend to use custom kernels, I recommend using TricksterMod, it's the best app for modifying kernel settings.
Also just to mention this ahead of time, it's against XDA rules to make threads about what is the best rom/kernels.
What are your recommendations for the best kernel for AOSP roms that provide the best performance/battery life? I would also like to be able to overclock and undervolt.
Thank you
I've been mucking around with Android for a while but basically stay with a ROM and what it comes packaged (or recommended) with.
Recently I've been looking around at Custom Kernels and I see they offer different options and functionality, but I lack some basic information:
I am guessing that the Kernel and ROM have to be compatible?
Is, for example a Kernel like Blu Spark or Lighting (all for OP5 and Nougat) compatible with all OP5 Nougat ROMs or is it ROM by ROM?
I looked over the pages for both Kernels and also for xXx Freedom OS and didn't see any information concerning compatible ROMs or compatible Kernels, is there any place/list that shows the compatibility of ROMs and Kernels?
Any information, or guidance to where I can find it would be appreciated.
Very simple.
There are 2 types of kernels. One which only works on an OOS based (custom) Rom, and one which will only work on a LOS or AOSP based Rom. Most custom kernels will work on every LOS or AOSP based ROM. But... There's one negative thing about flashing custom or OOS based Kernels. You will never know how the Kernel and/or ROM will behave. There's no 100 percent guarantee if a custom Kernel or ROM are made for each other. Even if a Kernel which comes with the ROM is no guarantee for working properly. There's no such thing as "Stable" even with ROMs. Because stable doesn't exist in a Dev World. It will always be a never ending story.
Long story short, search for yourself an satisfying combination. If you found one combination you like, stick with it and motivate the Custom ROM Developer and or Kernel Developer.
Edit: as you can read i cannot give a proper answer to your questions. The reason why a Custom ROM Dev doesn't show a list in their OP for working Custom Kernels, is mainly based on the fact that they don't like if a user flash another Kernel that didn't came with their ROM. Mostly to avoid non related ROM issues. Besides that, if you made a decision to flash a Different kernel, along with their ROM, you're on your own.
Sorry for being off-topic.
Each kernel needs to be build for each rom. Well not each rom. Each rom based on the top three. OOS, AOSP, and LOS. As each has their own kernel.
If you use LOS 14.1 or RR, then youll need a los kernel. If you run stock OOS. Freedom or xXx, youll need an oos based kernel
Not all devs build their kernels for los or aosp. Me as an example. I only have mine built for OOS and It wont work on los or aosp (well it may but you are 99.999% likely to run into a lot of problems)
I hope that clears it up a tad bit
lekiaM said:
Very simple.
There are 2 types of kernels. One which only works on an OOS based (custom) Rom, and one which will only work on a LOS or AOSP based Rom. Most custom kernels will work on every LOS or AOSP based ROM. But... There's one negative thing about flashing custom or OOS based Kernels. You will never know how the Kernel and/or ROM will behave. There's no 100 percent guarantee if a custom Kernel or ROM are made for each other. Even if a Kernel which comes with the ROM is no guarantee for working properly. There's no such thing as "Stable" even with ROMs. Because stable doesn't exist in a Dev World. It will always be a never ending story.
Long story short, search for yourself an satisfying combination. If you found one combination you like, stick with it and motivate the Custom ROM Developer and or Kernel Developer.
Edit: as you can read i cannot give a proper answer to your questions. The reason why a Custom ROM Dev doesn't show a list in their OP for working Custom Kernels, is mainly based on the fact that they don't like if a user flash another Kernel that didn't came with their ROM. Mostly to avoid non related ROM issues.
Click to expand...
Click to collapse
@lekiaM You provided a great answer and thank you. I did notice that some developers (xXx NoLimits) provide the option to select various Kernel during the install. I pretty much expected that matching a Rom to Kernel was a crap shoot to certain degree. I am going to try a few out and see how it goes.
One final question, if a Kernel offers functionality that is not offered in the original Kernel, how do you go about taking advantage of the added functionality?
Will the Kernel add those selection to the settings or will I need a different app to access them? I was thinking in particular of the don't wake on plug/unplug. I utilized some ROMs (CM) that had this feature in the setting, I use Freedom OS now and don't see that in the setting, but I see that the Blu Spark Kernel offers access to that function.
Zombie said:
Each kernel needs to be build for each rom. Well not each rom. Each rom based on the top three. OOS, AOSP, and LOS. As each has their own kernel.
If you use LOS 14.1 or RR, then youll need a los kernel. If you run stock OOS. Freedom or xXx, youll need an oos based kernel
Not all devs build their kernels for los or aosp. Me as an example. I only have mine built for OOS and It wont work on los or aosp (well it may but you are 99.999% likely to run into a lot of problems)
I hope that clears it up a tad bit
Click to expand...
Click to collapse
It does thanks. Prior to selecting some ROMs to try, I read that AOSP required a specific ROM so I steered away from it, for now. Until I am able to become a little more familiar with the entire subject.
noncomjd said:
It does thanks. Prior to selecting some ROMs to try, I read that AOSP required a specific ROM so I steered away from it, for now. Until I am able to become a little more familiar with the entire subject.
Click to expand...
Click to collapse
An aosp based rom will install and run like any other rom you decide to flash. It comes with the stock kernel built in
Each rom has their advantages and disadvantages. Currently Im running xXx 4.0 which is OOS based with extra features and then of course my own kernel for better performance and battery
@noncomjd Good question. And honestly I've been wondering that too (most of the time) i could gave you a simple answer on that, but i wont.
A Kernel can interfere with the ROMs behavior (for example manipulate the vibration, sounds, led light strength, button behavior and so on.) But a Kernel has their limits too and also the Kernel Dev in question. Besides that , i did saw some very strange things a Kernel Dev can do to manipulate a ROMs behavior. But i wont go further in that.
Answer to your question:
Yes. A good kernel dev can overwrite or add some tweaks in the ROM itself (you won't see it while flashing, but believe me after that, some things in settings are missing or added in the build.prop) . But as i earlier said it has their limits. A good Kernel Dev is aware of their capabilities. And they mostly play save. If a kernel Dev mentioned or added a feature or something in their changelog, than the feature is there. But to enable or disable that feature, you mostly need an 3rd party app(like a Kernel Manager) to activate or deactivate their added feature.
You need a kernel tweaking app in order to change kernel settings.
You can change those settings even if you run the stock kernel, but it won't offer as much features.
There are many kernel tweaking apps available and some kernels even provide their own apps.
Thanks all for some great information. Have a good base to set out exploring a little more.