[KERNELS] Looking for Kernel Developers for Kernel Manager!

[KERNELS] Looking for Kernel Developers for Kernel Manager! - Wildfire Android Development

Hey everyone! I wanted to introduce a new project with a very simple but ambitious goal: create a place where all kernel developers can submit kernels easily and reach a much wider audience with ease.
Using Kernel Manager to flash kernels takes less than 30 seconds, generally, and it is extremely simple for end-users to find a kernel, filter by kernel features (BFS, CFS, HAVS, SBC, etc) download/install kernels, and submit ratings for their favorites.
We need from kernel developers like YOU! Submitting a kernel to Kernel Manager is totally free and we even provide hosting for you! Submitting kernels is easy!
If you use IRC, join us in freenode in #kernel-manager!
THIS LINK IS FOR KERNEL DEVELOPERS SPECIFICALLY! Go to http://kernels.teamw.in and register for an account! Once it's approved, you can easily enter new kernels, which immediately show up in the app. The app is currently available in the market.
Please feel free to provide me with any feedback you have, or feature requests in order to make this a great tool for all of android to utilize!

Also, I posted the official CyanogenMod kernel in Kernel Manager!
So if there aren't any kernel devs who have uploaded their kernels to KM yet, you can at least see the flashing process and if it's something you'd use .
Enjoy!

Related

[Q] Kernel Vs rom - which have the most impact ?

Hello people.
I've been here for 3 months, reading, downloading and learning allot about our great machine and the android system. The one thing i cannot understand is that : people writing allot about the smoothness and fastness of their system. some says this is the kernel, some says this is the rom they installed. What part of smoothness is the quality of the rom and what part is depended on the quality of the kernel ? how many times have your read here "smooth and fast" on the responses of people, not matters if that rom or kernel ?
hope someone can clear this up for me.

A rom includes the kernel .
A rom is the whole OS just like win 7 is an OS .
Kernel is the bit that communicates with the OS at base level between CPU and other components and the OS .
Both have a part to play .
jje

I understand that, but i saw some responses of people, after changing their kernel, says : "ohh.. this is smooth.. and etc..".. how u can tell that this is the kernel ? maybe just by rebooting your phone it gets smoother like when you do it to your computer :}
The only thing i can spot is maybe the sound quality (like on voodoo sound).
how much the stability of your phone depends on the rom itself or the kernel ?

Well it's a good start to get your hands dirty and cook something.

in my opinion, kernels are basically very identical in the sense that they all convert the file system from rfs to ext4 which they just call "lagfix"
all other extras are dependent on developers on what they want to add.

Again, I am not a developer but a user. On the basis of my experience and reading, I would say there are two misconceptions here: (1) roms and kernels are not the same. Many roms embed a kernel as part of the package but both the kernel and the modem are distinct elements that may or may not be packaged within a rom -- the rom may be pre-packaged with a kernel and a modem, or these may be discrete components in and of themselves. (2) kernels are definitely not all identical, especially in terms of source code and modifications, which is the genesis of the dispute on xda which has seen the departure of at least one kernel developer. Compare this list:http://forum.xda-developers.com/showthread.php?t=966646 for kernels with this list for custom roms http://forum.xda-developers.com/showthread.php?t=886000
Most kernels require development, i.e. coding, whilst most roms are a packaging of existing applications and their organization within the framework of the firmware. The phone functions most effectively and efficiently when the kernel and the rom are complimentary. Problems arise when the kernel and rom are not 100% on the same page.
Last element is then the theme which is the visual display of the rom: again there is a separate thread for themes as one can use any number of themes with most roms.

Linus developed the kernel that was passed on then an operating system was laid on top of the kernel .Giving Linux/GNU
Kernel
http://en.wikipedia.org/wiki/Kernel_(computing)
jje

lgsshedden said:
Again, I am not a developer but a user. On the basis of my experience and reading, I would say there are two misconceptions here: (1) roms and kernels are not the same. Many roms embed a kernel as part of the package but both the kernel and the modem are distinct elements that may or may not be packaged within a rom -- the rom may be pre-packaged with a kernel and a modem, or these may be discrete components in and of themselves. (2) kernels are definitely not all identical, especially in terms of source code and modifications, which is the genesis of the dispute on xda which has seen the departure of at least one kernel developer. Compare this list:http://forum.xda-developers.com/showthread.php?t=966646 for kernels with this list for custom roms http://forum.xda-developers.com/showthread.php?t=886000
Most kernels require development, i.e. coding, whilst most roms are a packaging of existing applications and their organization within the framework of the firmware. The phone functions most effectively and efficiently when the kernel and the rom are complimentary. Problems arise when the kernel and rom are not 100% on the same page.
Last element is then the theme which is the visual display of the rom: again there is a separate thread for themes as one can use any number of themes with most roms.
Click to expand...
Click to collapse
Do roms devs do any coding to their roms? i.e. actually changing the coding of the framework etc or do they mearly just "rearrange" things? If not why not seeing as kernel devs actually do some coding to their component.

They do. Start up script is the most common example. Resizing the SD card read partition is also a common feature in many roms (the default read partition is quite small, hence slow media scanning speed.) It also takes quite a bit of effort to make sure that all the features introduced in the rom does not conflict with each other. (Over scroll glow, CRT shut down, extended power menu, etc.)

snapper.fishes said:
They do. Start up script is the most common example. Resizing the SD card read partition is also a common feature in many roms (the default read partition is quite small, hence slow media scanning speed.) It also takes quite a bit of effort to make sure that all the features introduced in the rom does not conflict with each other. (Over scroll glow, CRT shut down, extended power menu, etc.)
Click to expand...
Click to collapse
thank you for the clarification: my choice of words was not as clear in my original post and is no way was intended to diminish the task of compiling and developing a rom -- I also recognize that many tweaks can be approached from changes in either or both the rom and the kernel, but there are elements that are distinct to each.