[Galaxy S II Original Android Development] pongster:
Ok.

I like our kernel of course... advantage is I can update it when I need to, want to or just because I can when I find a new feature I'd like and can backport/port/patch to it... without waiting for anyone else or worse, bug a dev to implement a feature just for them... (usually starts out by giving platitudes such as "Great work buddy! Kudos to the best kernel dev! I'm loving every moment except for 1 problem... could you implement this patch "X" as it will really help me in my problem... even if no one else needs patch "X") :D

Just like any other kernel guy, they probably won't be using other kernels other then their own else they negate the countless hours spent patching, debugging, testing, fixing.

Most users think the ROM is harder to build... I've been doing that for a while and I can say its easier to build and mod a ROM then it is to make a kernel... if it were the opposite, you'd have more kernel threads than ROM threads that don't give proper credit.

I'm happy that gokhanmoral has made his kernel thread as interactive as it is and actually gets appreciated for his kernel work. You see most kernel devs' work (the zImage for Samsung Users) are just cut and paste into themed ROMs and users think "Wow... amazing ROM! great job chef for copy pasting modded and themed apk's! Best ROM evahhh!!!"

...and some "Chefs" don't even bother to link to the Original kernel thread! They simply say... "kernel X included" without any credits or thanks given to the kernel dev... Don't believe me, check the Android Dev thread and look at each ROM that has a kernel made by Hacre, gokhanmoral or hardcore by default... see how many link to the original thread or give credit to the kernel guy... :)

Of course it takes time to build the ROM as well... BUT... Mistakes made in ROM building get you a bootloop at worst (framework/lib/bin related)... Mistakes made in Kernel building gets you softbricked (which lucky for Samsung owners is easy to get around fixing) or bricked (never seen a kernel guy brick his own Samsung phone as they probably wouldn't be using any .PIT files for the SGS2 for example or select "Repartition in ODIN")

"If the kernel is still going to have the "stigma" of being linked to Hyperdroid, it does make it's audience much smaller."

huh? :confused: I wouldn't call it a stigma... for me personally (and maybe for some users who used our stuff on the HD2... WinMo and Android until now on the SGS2) HyperDroid means awesomeness, openness and reliability.

I plan to open the thread with the intention of making sure bugs and issues are easily discussed in its own thread... with a specific focus on those advanced users who would like to learn more about the kernel by searching and researching before posting a question. The planned new thread is not intended to get more users to use the kernel... its for the current kernel users who want to read, learn and help make it better for all HyperDroid Users. If others choose to use the kernel, that's entirely up to them. Just like its entirely up to you to use whichever kernel you wish to use.

That said, (on this present and that possible future thread) any question that clearly shows a lack of reading the OP, or lack of information on the problem (things like: "the latest build feels slow... halp me pleaze!" without even trying to provide a logcat or dmesg) and or the last 10-20 pages of the thread will be answered as it deserves to be answered.

I personally don't want the future kernel thread to be filled with

"spoiled brats who want to show off their device to their mates" asking "hey what settings do you use? (shows that the user doesn't want to experiment and learn to tweak the device that they have) OR "I have the greatest settings in the world... PM me!" (shows that the user wants to keep the settings out of the public eye, cause if they don't work they'll blame me and clutter the thread... which then leads to the thread being cluttered with requests for the "secret" sauce to make the kernel better.)

Please remember that anything we do here is for ourselves first... we choose to share what we have built cause it may be helpful to others... that doesn't mean support you should actually expect from the manufacturer of the device or the carrier that gave it to you... Speaking from experience here on the forums, I would rather have a small band of users who eagerly want to learn, do their part in solving their own problems and look to provide help/support on the thread rather than a bunch of user who DON'T read, and DON'T follow instructions and then have the audacity to complain and NOT give more useful information.