A Request to Our Kernel Developers (All Users Please Read) - Optimus One, P500, V General
Well, there are only two kernel developers here in the P500 forum, franco and fserve. There is no doubt that the work both of you have done is off the charts, tweaking every little thing that can be tweaked to such an extent that there hardly is anything left to tweak. And there is no doubt that most, if not all, of the people using your kernels love the work you guys put out.
With that in mind, however, there are a couple of things (specifically bugs) that we request, not demand, to be fixed. As we all know, our phone is affected by two things that I, as well as many other users, believe are two major bugs: the cpu spiking to 100% when touching the screen and the axis inversion bugs. Even with both of your kernels as good as they are now, these bugs hinder their true capability, thus hindering the phone's true capability. Both of you might just be thinking, "Well, there is paolo's kernel, go use that." And as kernel developers, you have every right to think that and decline this request. But seeing how good both of your kernels are, why not make it better?
Please consider this, as many of us believe both of your kernels can be made better with these bugfixes.
The poll is there as an estimate and measure of how many users believe that these bugfixes will make your kernels better.
sweetnsour said:
Well, there are only two kernel developers here in the P500 forum, franco and fserve. There is no doubt that the work both of you have done is off the charts, tweaking every little thing that can be tweaked to such an extent that there hardly is anything left to tweak. And there is no doubt that most, if not all, of the people using your kernels love the work you guys put out.
With that in mind, however, there are a couple of things (specifically bugs) that we request, not demand, to be fixed. As we all know, our phone is affected by two things that I, as well as many other users, believe are two big bugs: the cpu spiking to 100% when touching the screen and the axis inversion bugs. Even with both of your kernels as good as they are now, these bugs hinder their true capability. Both of you might just be thinking, "Well, there is paolo's kernel, go use that." And as kernel developers, you have every right to think that and decline this request. But seeing how good both of your kernels are, why not make it better?
Please consider this, as many of us believe both of your kernels can be made better with these bugfixes.
Click to expand...
Click to collapse
Agreed
PES2012 is hard to play with the lags but suprisingly Pes2011 does not have lag...I read once that Sippolo said its a 2 minute fix for the cpu spike bug
i think its ok to fix bugs even when most users can profit.
but, what about users who have new/other phones now?
i know from franco he's not developing on .35 currently because he has a new phone
and the P500 is used by his father - no way to develop on every day. the next reason is as we
all know, the P500 is a nice device for android beginners but most of us have seen
the new things like Nexus S, Galaxy S-2, HTC devices or other high end phones. I'm sorry
to say that but the P500 is some old and almost used in countries where such high end
devices cant be payed for, or, in most cases too - most users who bought this device
are very young (when i think how old i'm) - and, good developers have a real job to get
enough money for high end devices ... so, these developers cant support such low budget
devices all the time.
For me this means, i'm developing on P500 because its most funny for me to see all these
**** LG hardware bugs, but decided too that there is no way to develop on P500 the next year
too, so the next phoenix-android gingerbread will be the last release for the P500 device too.
I dont know what mik_os is doing, i think he has a real job too and no time to develop all
the time for this device ...
But, ok, these words sounds very sad for most users - i think, there are other ways or users
who take the developers work and can support such devices for a few months. for me it
doesnt matter if users are coming to me and asking how they can develop on my code.
Android should be open source, that means for me there is a community who want to develop
on - and not everybody is a real developer but can learn something, and that can only be reached
with help and understanding each other. Everybody can say "I want Gingerbread on my phone, i want
ICS on my phone, i want a hell kernel on my phone" - but these work cant be developed by google,
its the task for the community, so lets start here and now and stop crying for franco, fserve, mik or
others! Learn to help your self! Be a part of a real community!
I understand what you are trying to say andy, and after reading your post, i must say that i have to agree with you.
As much as I want to start developing myself, I have no idea where to begin. Just a question, which language must I learn to start android development? (is it java or c++? ive seen both languages mentioned but i do not know which one. is there one specific for roms and one specific for kernels? because i think i might give kernel development a try once i learn the appropriate language)
sweetnsour said:
Ah, this thread was short-lived
I understand what you are trying to say andy, and after reading your post, i must say that i have to agree with you.
As much as I want to start developing myself, I have no idea where to begin. Just a question, which language must I learn to start android development? (is it java or c++? ive seen both languages mentioned but i do not know which one. is there one specific for roms and one specific for kernels? because i think i might give kernel development a try once i learn the appropriate language)
Click to expand...
Click to collapse
Developing on android doesnt mean you have to write code by yourself all the time.
Sure, its good to know about C/C++, Java, Shell scripting, makefile reading/writing and other things
but in most time we can copy or integrate existing patches. So, you only know about the bug and
where to fix it with what programming language. For the first time, search for the bug on google
and/or github - with some luck users can find a fix that needs only to copied in the local code.
To start developing on android, its a good choice to understand in details how android is working
and even a good thing is to know about Linux. On windows, you cant develop on Android OS so
you need at least a small Ubuntu/Linux Mint/RedHat or SuSE system with compilers and Java installed.
The next required knowledge is to know how Android is interacting with files:
What is Java for, what is C/C++ for, how Android is booting and what are JNI libraries.
We can open a thread so we can explain something or users can ask for specific things there.
andy572 said:
Developing on android doesnt mean you have to write code by yourself all the time.
Sure, its good to know about C/C++, Java, Shell scripting, makefile reading/writing and other things
but in most time we can copy or integrate existing patches. So, you only know about the bug and
where to fix it with what programming language. For the first time, search for the bug on google
and/or github - with some luck users can find a fix that needs only to copied in the local code.
To start developing on android, its a good choice to understand in details how android is working
and even a good thing is to know about Linux. On windows, you cant develop on Android OS so
you need at least a small Ubuntu/Linux Mint/RedHat or SuSE system with compilers and Java installed.
The next required knowledge is to know how Android is interacting with files:
What is Java for, what is C/C++ for, how Android is booting and what are JNI libraries.
Click to expand...
Click to collapse
Thanks for the info! I will keep this in mind.
andy572 said:
We can open a thread so we can explain something or users can ask for specific things there.
Click to expand...
Click to collapse
good idea (this sounds like sticky material)! would you like to open it? it would not make sense for me to open it since I'm not a developer
First of all i would like to thank andy, mik_os, franciscofranco, fserve, ciaox,knzo, docotornotor and many others who i may have forgotten for their impeccable work towards this community and for working their asses off. You'll are invaluable assets to the community and i could'nt imagine using my phone without you'll.
Reading andy's post i must have to agree with him because you devs have worked so hard towards our phone even though many of you''ll don't own one. Also you bared with the many spams, useless comments on your threads without saying a word. Also many of you have jobs in RL for which you have to work hard, and developing for a phone which you don't even own/primitive phone would seem to you as a waste of time and i can thoroughly understand that. Even though i dunno scat about developing, i do know that it is highly time consuming and resource oriented.
So as you'll probably know that the 2 most irritating bugs on our phone are the touchscreen driver lags, and the axis inversion bugs. Me, as well as thousands of p500 users can't thank franciscofranco and fserve for their dedicated work towards our phone and for developing two awesome kernels which made our p500 superfast. Any p500 user could match his phone's performance to our higher end phones and show its capablities off even though it being a low-ish end phone. I think i am speaking for the thousands of p500 owners all around the world and i would like to take this opportunity to request you kernel developers to fix these bugs and include them in your fanstastic kernels. India itself has the largest number of p500 owners all around the world and this phone is still popular as of today and if you'll didn;t know it is THE BEST SELLING SMARTPHONE phone in India. Therfore tons of us users would love if u fixed these two final bugs as they in my opinion are the biggest performance drainers all credits to ******y LG developers. As sweetnsour said, you devs have every right to decline this request as there is already the paulos kernel and plus you devs have worked your asses off to tweak our phones to its fullest extent and i don't think there may be any more tweaking left to do
However i do believe you devs collaborate in this one final project. Me, as well as every member of this community can't thank you enough for your hard work! We also have many talented devs [ciaox is 13 wtf? ] who can continue development of this phone. Looking at the dev section, many new roms have come up since mik's cm7 port and each rom outperforms the other[no disrespect to mik_os, he started the cm7 era!].
I hope fserve and franciscofranco take this post in regard and work towards fixing these bugs !
Thank you.
ps. sorry for my bad english.
@ andy572
Open ur own website and tell us more! I wanna build my own ROMs but i kinda fail it... With ur small free time? Can u exxplain?? It would be grateful to others!
Sent from my Nexus One using Tapatalk
Uhm... Fserve has already patched his Goldenleaf Kernel with Der_Caveman + Waleedq + Sippolo's workaround to fix axes inversion and cpu spikes.
The related Fserve's kernels are Goldenleaf 111107 and 111108 (I prefer this one). Cheers!
if u didnt know, axis inversion is not possible to fix 100% because it is a hardware issue.........
there is only little you can do about it in the coding part
Yes, I know it's an hardware problem, however a workaround is better than nothing!
Sent from my LG-P500 using XDA App
for me it
doesnt matter if users are coming to me and asking how they can develop on my code.
Android should be open source, that means for me there is a community who want to develop
on - and not everybody is a real developer but can learn something, and that can only be reached
with help and understanding each other. Everybody can say "I want Gingerbread on my phone, i want
ICS on my phone, i want a hell kernel on my phone" - but these work cant be developed by google,
its the task for the community, so lets start here and now and stop crying for franco, fserve, mik or
others! Learn to help your self! Be a part of a real community!
Click to expand...
Click to collapse
well said~
fserve's goldenleaf has added Sippolo's workaround
For me as a user, i would say THANK YOU to you guys for bringing this community alive. Thank you for your hardwork and effort that you put in. I would say that my p500 runs fastest than galaxy s stock 2.3.3. Im not joking as my phone is smooth thanks to you guys. no bugs for most of the roms i tested. I may not be a dev but i understand a lil bit. So once again thank you guys
Sent from my LG-P500 using XDA App
I agree with most of what Andy said, except the part that our phone is obsolete.
I'm not a dev but I found plenty of tutorials available that explained how to successfully compile a kernel from source and extract a .config from an existing kernel. I never found a perfect how to but by meshing various methods together I was eventually successful. After reading francos github commits I discovered the toolchain he was using which was the final ingredient.
From there I used a diff tool to compare franco and Paulos sources, this is how I found the camera flicker fix. When I saw big differences in the source I googled it and/or copied it over then compiled and tested it. It took about 5 tries before I found the flicker fix. This learning process took more than just a couple of hours, it was frustrating but eventually rewarding. I still don't know anything about C or Java, so Andy is right, read/research, copy/paste, trial and error actually works.
Considering that Paulos kernel has resolved these issues and franco hasn't means you should be able to use the same technique. These bugs seem to affect gaming the most, which I don't do, so I haven't had the motivation to look into it.
franco and fserve are more than willing to include fixes. fserve posted a test kernel that included my find within a day. Within a week franco had released a new version that included it.
Open a discussion thread, I think it's a great idea! This is a developers forum after all. Thousands of noobs should be able to combine their efforts to fix these issues. Let's make it happen instead of waiting for it to happen.
Thank You !!!
Suggestion : Why dont Fserve or Franco use and edit Paulo's V6 Kernel'?
is it possible'?
OT.. .
Mistakes are the PORTALS of DISCOVERY .. .
so Cmon.. . Lets commit mistakes
Why don't ask them yourself?
Btw: PaoloM70's 2.6.35.14 V6 Kernel source:
http://www.multiupload.com/18Y712HS9G
so there is no multitouch bug and screen touch lag in paolao kernel?
@sweetnsour . I feel like Ciao X would be a good person to ask about this one. He is young so I feel will continue to work on our p500. I could be wrong. But I also think you could learn much about your goal( which by the way I think it's WONDERFUL you want to learn to develope ) I KNOW I'm not cut out for it, and so I can be honest while I am no actually HELP to this community when it comes to developing. I AM. A HUGE fan, supporter and appreciate of all the passion and art and great works that come out of this wonderful community!!! Anyway, I digress CIAO CAN YOU WEIGH IN ON THIS???
Optimus T
OpenOptimus (froyo)
latest franco kernal
748/480
Interactive X
Jonny Green
"im not a Dev but I flash alot"
TL;DR
If you want to help me, post on MY thread about my kernel bugs. --REALLY--
(or dev something, lol)
(or donate me, i really love that )
FOR NOW, i need people to tell me which is the WORST game to play on p500 using gbs v19 kernel, AND it need to be free (or not if you give me the money).
So i can test this touchscreen bug.
Please, post, on my thread for .32 kernels and on franco thread for .35 kernel.
Thanks
fserve said:
TL;DR
If you want to help me, post on MY thread about my kernel bugs. --REALLY--
(or dev something, lol)
(or donate me, i really love that )
FOR NOW, i need people to tell me which is the WORST game to play on p500 using gbs v19 kernel, AND it need to be free (or not if you give me the money).
So i can test this touchscreen bug.
Please, post, on my thread for .32 kernels and on franco thread for .35 kernel.
Thanks
Click to expand...
Click to collapse
Thanks for weighing in! There are two apps you can try using:
For a game, try playing glow hockey (use the two player mode). When your fingers cross, you will be controlling the opposite puck.
To see what is really going on, check out the app "multitouch vis test". You will see the bug when you cross your finger either horizontally or vertically.
Sent from my LG-P509 using xda premium
EDIT: I was talking about the axis inversion bug, not the CPU lag bug. Not sure what the worst free game for that would be, but neocore would be good for testing this bug.
Related
[Discussion][Poll] Do you think we need "ROM Categories" for Gingerbread releases ?
[Discussion][Poll] Do you think we need "ROM Categories" for Gingerbread releases ? Hi all, building upon a conversation started on this thread regarding the different Gingerbread ROMs that are being currently tested/released by our much appreciated developers, I'd like to start a discussion and poll to get your opinion about the need for "ROM Categories", that is, a small group (probably 3 or 4) of "Guidelines" so developers could focus their ROMs to target specific group of users or usage of the ROM, something like: - Performance: Getting the most juice out of your phone and getting the best score for benchmarks, but perhaps with the sacrifice of stability and/or certain functions of the handset and battery life. - Gamer: Focused on the best graphics and GPU performance for best results in games and graphics apps, but perhaps with the sacrifice of battery life. - Stability: Stock-like ROMs that covers ALL the functions of the handset with the best battery life and stability, but with the added value of certain tweaks that gives you that "something extra" to justify rooting your phone and installing a custom ROM so you can enjoy those (I pretty much fall into this category) (Those are just the few that comes to my mind, I think that if this proposal actually goes through the actual categories should be agreed on by the community) I base this proposal on the following: 1.-) I've been testing many ROMs over the last few days and I've noticed that even though there's been many developers that have released custom ROMs over the last few months, only handful of them (those guys that we all know and love) have kept working on refining their work as the different Android versions had passed by, so at this point (with the official release of Gingerbread for the P500) I think it would be possible that developers could work together and focus their work with specific goals, like having a well polished ROM for each category and keep developing those. The idea is not to pretend that developers wouldn't have freedom to do their work exactly as they want to, essentially because they are doing this because they enjoy it, not because we're hiring them to do it. What I mean is that if developers "categorize" their ROMs then either themselves (or new developers) could easily spot what categories are being underdeveloped, and make the decision like "hey... nobody is doing anything for "X" category, so I'm going to do something about it". At this point they could agree to either work together for specific goals, or work individually knowing that one of them is working on fulfilling the need on a specific category. 2.-) As far as I can tell Gingerbread 2.3 is the last official version that LG is going to release for the P500 line, so I believe that once developers get to stabilize their custom versions of it (ROMs and Kernel) the P500 community will start to fade away as we all (developers and users) start to move on the newer handsets, so I guess that probably the best legacy that we can all leave for this community would be a handful of custom ROMs that we could keep using on our phones depending on the type of use that we give to it, until it's time to move on to another handset. 3.-) Having specific categories could help a lot when it comes to testing (and gathering results of those tests), essentially because most of us on the "user side" would surely focus their testing upon the way that they use their handsets, and that would translate on more people doing the testing for a handful of ROMs, instead of everyone testing everything (which usually translates into nobody testing anything). Well I guess that's enough to make my point, the rest is up to you all to either vote and give some comments here or just say: "Hey n00b, what the #(=$/# your're talking about dude!!!" LOL, don't worry I can live with that
We should definitely have this. Sent from my LG-P509 (Optimus T) with Void Gear using XDA App
Well actually we do have a thread like this. The repository sticky on dev subforum. It has all the roms, kernels, guides, mods etc sorted nicely with short and informative descriptions ( Repository ) and since ciaox started to maintain the thread it is always up to date with the latest stuff. If you got any suggestions or something for repository to become better you could just post it there.
A MUST-READ for aspiring ROM "Developers"
This article appeared today on the main page of XDA and I feel that it's a very important lesson for any/all new ROM devs. Sage Advice from Cyanogen Still Valid Today http://www.xda-developers.com/android/sage-advice-from-cyanogen-still-valid-today/ Excerpt: He had this advice to offer for those looking to make their own Android ROMs: Stop. Write an app or two first, learn how the system works from a developer standpoint. Learn some Java. Read the developer documentation. Learn how to use Git. Then learn how to build AOSP from source. Read the porting guides, and learn how the build system works….. Now try to put your new found skills to work on enhancing the platform by writing code or making theme overlays. And share! And put that s**t on your resume. There is a *ton* of information out there but any kind of “step-by-step rom cooking guide” is going to be a complete fail- it’s too broad of a subject.As XDA has grown right along with the meteoric rise of Android, so has a desire of users to create their own ROMs, kernels, themes, and so on. Much of this work classifies as “original development,” but there’s been a growing trend to what many are calling “derivative development.” This category covers most of ROMs based on stock releases from the manufacturers, applying patches and scripts aimed at optimization, theming and/or removing stock applications, and using “kitchens” that run a stock release through a list of scripts and then repackage as a recovery-flashable update.zip. This is what Cyanogen was expressing frustration about—shortcuts being taken to achieve a product that differs only slightly from stock (derived) and pushed out instead of building from source and delving into the core of Android and making something truly original. XDA-Developers exists first and foremost for developers. It’s at the core of who we are; it’s in our blood; and it’s in the air we breathe. There is a place for derivative works—they provide an entry to the scene which can help to introduce people to the wonders of Android. But let’s not stop there. Don’t be satisfied with just creating yet another derivative of someone else’s work. Instead, follow Cyanogen’s sage advice and learn about Android from the ground up, and create something truly original and innovative. Click to expand... Click to collapse
Guess I should continue with this hello world app... haha
Op just explained 99% of our roms lol Repackage, rename, reskin and ask for donations. Rinse lather and repeat. Now your a dev!
Ha. True software developers understand the wisdom of code reuse. So ,in my opinion, if a fledgling developer takes a set of code and applies addons, makes a few setting changes then calls it a ROM and provides users benefit...then they are on the path. Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
andrawer said: Ha. True software developers understand the wisdom of code reuse. So ,in my opinion, if a fledgling developer takes a set of code and applies addons, makes a few setting changes then calls it a ROM and provides users benefit...then they are on the path. Sent from my SAMSUNG-SGH-I717 using Tapatalk 2 Click to expand... Click to collapse Even if they fail to write a single line of original code? I'm with cyanogen on this one...
saddly alll this is sementic if the world of android was perfect then this would be true .by perfect i mean everything being open source ... but if everything was open source we woudlnt have things like arc touchwizz blurr or sense , it is my opinion and shared by many others that android would be very boring if we only had aosp . what does a coder brings to touchwiz sense or blurr device ? the market is filled with cool apps and launcher .. 99% of them coders will make apps for android and wont bother with anything else that brings me to my next point . building from source means on top of aosp , or in my terms vanilla android .. many devs love vanilla and its fine but what about those who dont ? 99% of the rom on xda are just that : either source compiled with apps added or stock deodex rom with a theme and apps added .. here is the but , and before i say it i wanna say everyone is entitled to his opinion and im not bashing anyone , without guys like me who just hack the code and spend countless hours looking at what the code is actually doing and port the nice stuff from sense to TW or form CM to TW and RE (reverse engineer all these nice codes) 99% percent of the android devices would be boring because lets face it there is only one aosp device / year.. so from what Cyanogen is saying we should all buy a gnex and stop supporting those that make android close source, but wait without them , many things woudlnt be in CM in the first place , what is cm without all these kangs? a glorified aosp ? ok maybe im pushing but you get my drift... how many true innovations by Cyanogen vs them Proprietary UI ? fun fact the head (or ex ) of Cyanoen now works at samsung and help make touchwiz better (close source) what about miui , they have so many innovations , and they dont share any of there code .. so as I said there is no black or white here thats what android is all about make your own thing play with it call it yours and make it a hobby , and maybe just maybe others will like it ... I have seen way to many devs get god like status on xda for deodexing a rom and injecting voodoo in there kernel (for example) i ve seen crazy talented themers have there work taken by others be ignored by the community and then vanished , and everyday we see a kik ass true developper on here and treat him like hes a nobody , because he doesnt have or because we havent heard of his rom ..... i completely understand where cm is coming form but my opinion differs slightly .. @op kik ass thread (as I never read the front page)
Hard to build an i717 ROM from scratch with all of the proprietary bits, Samsung framework, etc, as most of that is proprietary as DAGr8 says. AOSP/AOKP works, but lacking some SPen functions and still relying heavily on a binary kernel as there are no kernel sources for ICS yet. Hopefully the kernel situation changes, and we're back to the normal business of everything except the proprietary blobs that have to get copied from a stock ROM...... It'd be nice if all required code was released, but for some reason such things tend to be considered proprietary. Oh well.
Thanks OP. I also don't read the frontpage near often enough. I like what Cyanogen is saying, and agree with his points from his developer point of view. I also agree with DAGr8 and his points. The fact is that Android gives us so many choices and has so many options for exploration. I think that's why so many of us have moved to the Android ecosystem. There is enough room for everyone. Android is the most prevalent mobile OS in the world for a reason. We can all have our opinions. We can all have what we want on our devices. And there are more and more people willing and able to jump in and try to build. Call them developers, or hackers, or derivators. It doesn't matter to me. They all add value to Android.
[Q] Creating Kernel Source Not Kernel from source!!!!!!!!
Hello Everybody, I just wanted the ICS for my device as we are still running on GB and which is awful thing for an Dual-Core,Tegra-2 device(Micromax A85 a rebranded Mobile of K-Touch w700/Cherry Magnum 2X).We tried to create a ICS for our device but we failed as we are not having kernel sources for our device and they haven't released kernel for any device. And so i started asking developers that can they help us and the only answer i got was no and they kept saying no way , your situation is hopeless and all that. And Now I Just Wanted to know That when a mobile is manufactured first time they didn't have any kernel source for it they create it for the device or develop it for the device and when they can develop it then why we can't develop it as we all are humans and what they can do i can do.So Please Tell me now how to create kernels not that you can't,nothing can be done.And I think that Xda Is A Great Site and now i wanna know that are there real developers or there are some kind of script kiddies present in Xda. Now Show me What developers have got and i know deep inside my mind that there are developers which can help me.They are just needed to be discovered.!!!!!
Well....it is possible, but ts a ton of work and will take months...its something no one wants to do for free, as the end result isn't worth all the work. I'm no expert on kernels...I'm actually pretty new to them, but I'll tell you this: you have to identify every single chip in your device, you then need to implement there drivers...you need to make thousands of files....the end result is a folder that is over 100 MBS....almost completely "text" documents....I would never even attempt it unless I was getting paid a lot of money... The people who make these from scratch (manufacturers) typically have teams of people who are specialized who have gone through years of schooling and work to get where they are at now. And keep in mind there is different kinds of development....don't start calling people script kiddies if they don't know how to make kernels from scratch...for all you know thy could be one of the best app or game developers around...they are just specialized in a different area I really dislike the way you are asking for help...you seem to be indirectly putting down a lot of people in the OP...and basically saying if you can't build a kernel from no source then you're not a developer...these people have jobs and life's, they don't have the time to make a kernel from nothing. The reason manufacturers are able to is because that is there job...that's what they do for hours a day everyday... Anyways...try bugging the manufacturer for source...they have to release it or they are in violation of GLL (I think that's the name...) and they could get sued...as far as I know due to android being open source kernel source must always be released. Sent from my SGH-I997 using Tapatalk 2
mg its GPL v2.0
mg2195 said: Well....it is possible, but ts a ton of work and will take months...its something no one wants to do for free, as the end result isn't worth all the work. I'm no expert on kernels...I'm actually pretty new to them, but I'll tell you this: you have to identify every single chip in your device, you then need to implement there drivers...you need to make thousands of files....the end result is a folder that is over 100 MBS....almost completely "text" documents....I would never even attempt it unless I was getting paid a lot of money... The people who make these from scratch (manufacturers) typically have teams of people who are specialized who have gone through years of schooling and work to get where they are at now. And keep in mind there is different kinds of development....don't start calling people script kiddies if they don't know how to make kernels from scratch...for all you know thy could be one of the best app or game developers around...they are just specialized in a different area I really dislike the way you are asking for help...you seem to be indirectly putting down a lot of people in the OP...and basically saying if you can't build a kernel from no source then you're not a developer...these people have jobs and life's, they don't have the time to make a kernel from nothing. The reason manufacturers are able to is because that is there job...that's what they do for hours a day everyday... Anyways...try bugging the manufacturer for source...they have to release it or they are in violation of GLL (I think that's the name...) and they could get sued...as far as I know due to android being open source kernel source must always be released. Sent from my SGH-I997 using Tapatalk 2 Click to expand... Click to collapse It's GPL my friend. But to answer OP's question, taking the Linux kernel and configuring it to boot on a phone/tablet takes a HUGE amount of effort and time. This is something that paid developers do for companies like HTC or Samsung. It usually requires a whole team of developers who work on it months, or even years before the release of the device. Even then, the developers still continue to improve on the kernel and the manufacturer can release an OTA update. I'm not saying that it's impossible, but it is a task that is definitely not worth it. It's just better to ask the company for the kernel sources.
Ready for some WAVES...
Theres something that was pointed out to me by a new friend, that I had to vent about.. so HERE IT IS!!1 Why are some people too good to hang out in their threads and answer questions about the builds they post??? It seems to me that it builds credibility, to help the people using your build, so why not hang out and answer questions, address issues, help finding solutions, offer advice... BE HUMAN Sure its great that new builds are being pushed out constantly... BUT IF YOURE NOT TALKING TO THE PEOPLE RUNNING THE CURRENT ONE AND EXPERIENCING PROBLEMS WHAT GOOD IS IT???? Step down from the clouds, and walk barefoot on the grass with the rest of us.. its cool and refreshing on your feet
WOW Man.. pitbull8265 said: Theres something that was pointed out to me by a new friend, that I had to vent about.. so HERE IT IS!!1 Why are some people too good to hang out in their threads and answer questions about the builds they post??? It seems to me that it builds credibility, to help the people using your build, so why not hang out and answer questions, address issues, help finding solutions, offer advice... BE HUMAN Sure its great that new builds are being pushed out constantly... BUT IF YOURE NOT TALKING TO THE PEOPLE RUNNING THE CURRENT ONE AND EXPERIENCING PROBLEMS WHAT GOOD IS IT???? Step down from the clouds, and walk barefoot on the grass with the rest of us.. its cool and refreshing on your feet Click to expand... Click to collapse Could not have said it better.... You hit the nail right on the head.. People respect those who back their work with support:good::good::good: This DOES seem to be in SHORT reserve.. WELL STATED
Impressive I have noticed this too.. Its like these people are too GOOD for Q&A and sometimes even respond to questions like they are PETTY and an inconvenience.. There ARE some who DO help, and those people deserve to know they are appreciated.. You in particular, have helped me a ton, so thanks.. Maybe you'll start a movement, and more people will start doing their part to help their followers...
+1 There is a SERIOUS shortage of helpers and an overage of shovelers All these builds keep coming, and still the same problems on the one they put out before with a different NAME for the ROM.. Its like they change the name and recycled it.. I read through threads now, and if the OP doesn't hang out and help their users, I wont use their builds anymore.
Couldn't agree more!! Nicely said too Be proud of your work.. Stick around and make sure people can..ya know, enjoy it too.. It's quality not quantity that matters. Stepping on other teams and developers to rush something out just to say "FIRST" will get you no where.. So while timely updates are important, if that's the only thing you post in your own thread.. "New build is up" when there's been 10 pages of people asking questions... I'll never support you, both publicly or financially. I understand new enthusiast can be quite frustrating or maybe you just aren't a people type of person.. team up with someone that is... pass the q&a on to them, but do fricking something, people want support for YOUR roms and if you put out 20..that means all 20.
Exactly, how dare these developers not spend any time in the forums answering the same useless non-informative questions over and over. How dare they spend countless hours building a ROMs for free and then share it for others to use. How dare they spend time with their families and go to their actual job and have a life. How dare they….. (/sarcasm)
mapatton82 said: Exactly, how dare these developers not spend any time in the forums answering the same useless non-informative questions over and over. How dare they spend countless hours building a ROMs for free and then share it for others to use. How dare they spend time with their families and go to their actual job and have a life. How dare they….. (/sarcasm) Click to expand... Click to collapse Yea, I'm somewhere between this and the op. They shouldn't be 100% absent, but on the same note, some consideration for the above quote is in order too. While were venting, its possible the devs haven't figured out how to fix some of these issues, but it doesn't do a dam bit of good for 50 people to complain about the same thing and no one is posting logcats. So don't complain about things not getting fixed, if your not attaching logs to every post about issues. Just my 2c, add 97c more and go buy a cheeseburger. Sent from my G3, Unlocked by Team Codefire
mapatton82 said: Exactly, how dare these developers not spend any time in the forums answering the same useless non-informative questions over and over. How dare they spend countless hours building a ROMs for free and then share it for others to use. How dare they spend time with their families and go to their actual job and have a life. How dare they….. (/sarcasm) Click to expand... Click to collapse Then why put out 20 instead of 1 that they can handle is the point!!
Variety is the spice of life. I'd rather have 20 that will get fixed eventually than just 1 that works perfectly. If they are all too similar for you then just move on to another one, build your own, or just wait for fully featured lollipop which will be here soon enough. If a thread is maintained or not - I'm just happy to have a thread. A couple devs have walked away already and it'd suck if more left. Just be grateful for what we've got and be patient.
Kris Nelson said: Then why put out 20 instead of 1 that they can handle is the point!! Click to expand... Click to collapse The same person is not releasing 20 different versions. Also, most are all based off of the AOSP core source, but each dev might add their own touch/flare to it. But, since each one is based off of AOSP, then more than likely, they will all have the same issues, unless the dev has made some changes. I'd rather have a lot of choices than none. Believe me, when there is NO dev support (that is, a lot of ROMs being release), then you get even MORE whining of "Why isn't there any ROMs/dev support for this?" Maybe you're not a dev, but I am (not for ROMs but that is my full-time job). Development takes a lot of time. I do it at work and to do it at home as well, especially for something that is free, takes a lot of time and dedication. Especially, ROM development is NOT an easy task. Rebuilding ROMs takes at least 90 minutes or more, depending on the speed of your machine, the size of the source code, etc. Heck, I've pulled down the git for CM12 and it's 12gb in size (source code only, not compiled) and it took hours to download over my high-speed internet connection at home. I can understand wanting support if you PAID for it, but this is free, people. Free. They don't ask for anything in return monetarily, and yet, we see people demanding support as if they paid for it. You get what you pay for, and in this case, it's free. But I feel the support most devs give is very good, considering it's free. Also, for things like CM, it's usually not just one dev, but several who have responsibilities for different parts of the Android code base. So, just because one guy posts about it, doesn't mean he's the only dev on it. He might be sending your findings back to the other devs. Also, you DON'T have to flash these custom ROMs. They all have disclaimers that the dev is not responsible for any damages that may occur to your phone. They don't guarantee support, but it's there for you to use. However, who is to say they aren't monitoring the forums? Just because they don't respond, doesn't mean they aren't looking into the issues you report. Yes, I understand how you want a response from them, but in the end, it is your choice whether you want to flash or not. They didn't twist your arm to do it. Keep posting your defects. Most devs, the good ones, do monitor the forums and take note of the issues. However, they know about other major issues that they are probably trying to work on. Again, for most, it is done in their spare time. I myself would like to build and release ROMs, but right now, I don't have the time. it's not just "make a change, compile, release". There is a lot of researching, debugging, etc that must go on. Those that are programmers understand this. And, once you fix a bug, you don't just go and release it (under normal circumstances). You have to go through a complete testing cycle, retesting previous tests along with any new tests to ensure you didn't break something else. It's not that simple. However, with these free releases, WE are the testers. WE are the ones that report back the issues so they can be addressed. Post them here, or even some devs have Twitter pages where you can post defects. Not all, but some. In the end, be thankful you have so many choices. Yes, it may seem as if they are all the same, and in some cases they are and some are from people who just want to say "look I released a ROM" and then you never hear from them again. But, in the case of XDA, to post about a ROM in the dev forum, I believe you have to be an identified developer, so they do have to go through some vetting process. So, more than likely, they are legit developers, not a fly-by-night person. Just wanted to get that off my chest. I understand what people feel, but you have to understand, this is not an easy thing to do. Maybe a lot of you understand that, but I find that a lot don't. Or, they say they understand, when they really don't. They just "think" they understand. Wow. Off the soapbox. It just burns me as a developer when I see things like this. Yes, I understand where you are coming from, but sometimes, I think you need to hear it from the other side as well. Ciao!
If you're a good parent, when you bring a child into this world, you raise it, and nurture it... creating it is not enough... noun 1. the act or process of developing; growth; progress:
iBolski said: The same person is not releasing 20 different versions. Also, most are all based off of the AOSP core source, but each dev might add their own touch/flare to it. But, since each one is based off of AOSP, then more than likely, they will all have the same issues, unless the dev has made some changes. I'd rather have a lot of choices than none. Believe me, when there is NO dev support (that is, a lot of ROMs being release), then you get even MORE whining of "Why isn't there any ROMs/dev support for this?" Maybe you're not a dev, but I am (not for ROMs but that is my full-time job). Development takes a lot of time. I do it at work and to do it at home as well, especially for something that is free, takes a lot of time and dedication. Especially, ROM development is NOT an easy task. Rebuilding ROMs takes at least 90 minutes or more, depending on the speed of your machine, the size of the source code, etc. Heck, I've pulled down the git for CM12 and it's 12gb in size (source code only, not compiled) and it took hours to download over my high-speed internet connection at home. I can understand wanting support if you PAID for it, but this is free, people. Free. They don't ask for anything in return monetarily, and yet, we see people demanding support as if they paid for it. You get what you pay for, and in this case, it's free. But I feel the support most devs give is very good, considering it's free. Also, for things like CM, it's usually not just one dev, but several who have responsibilities for different parts of the Android code base. So, just because one guy posts about it, doesn't mean he's the only dev on it. He might be sending your findings back to the other devs. Also, you DON'T have to flash these custom ROMs. They all have disclaimers that the dev is not responsible for any damages that may occur to your phone. They don't guarantee support, but it's there for you to use. However, who is to say they aren't monitoring the forums? Just because they don't respond, doesn't mean they aren't looking into the issues you report. Yes, I understand how you want a response from them, but in the end, it is your choice whether you want to flash or not. They didn't twist your arm to do it. Keep posting your defects. Most devs, the good ones, do monitor the forums and take note of the issues. However, they know about other major issues that they are probably trying to work on. Again, for most, it is done in their spare time. I myself would like to build and release ROMs, but right now, I don't have the time. it's not just "make a change, compile, release". There is a lot of researching, debugging, etc that must go on. Those that are programmers understand this. And, once you fix a bug, you don't just go and release it (under normal circumstances). You have to go through a complete testing cycle, retesting previous tests along with any new tests to ensure you didn't break something else. It's not that simple. However, with these free releases, WE are the testers. WE are the ones that report back the issues so they can be addressed. Post them here, or even some devs have Twitter pages where you can post defects. Not all, but some. In the end, be thankful you have so many choices. Yes, it may seem as if they are all the same, and in some cases they are and some are from people who just want to say "look I released a ROM" and then you never hear from them again. But, in the case of XDA, to post about a ROM in the dev forum, I believe you have to be an identified developer, so they do have to go through some vetting process. So, more than likely, they are legit developers, not a fly-by-night person. Just wanted to get that off my chest. I understand what people feel, but you have to understand, this is not an easy thing to do. Maybe a lot of you understand that, but I find that a lot don't. Or, they say they understand, when they really don't. They just "think" they understand. Wow. Off the soapbox. It just burns me as a developer when I see things like this. Yes, I understand where you are coming from, but sometimes, I think you need to hear it from the other side as well. Ciao! Click to expand... Click to collapse Thank you.. Just to correct you though.. There ARE the same persons that are putting out 20 different versions (1 developer. releasing 20 different roms.) That was just the point i was making.. I do personally research before i ever flash a rom or anything..and trust me i donate!! LOL
Kris Nelson said: Thank you.. Just to correct you though.. There ARE the same persons that are putting out 20 different versions (1 developer. releasing 20 different roms.) That was just the point i was making.. I do personally research before i ever flash a rom or anything..and trust me i donate!! LOL Click to expand... Click to collapse I see who you are talking about. If you read the OP, at the bottom, he gives thanks to the devs on these ROMs. I don't think he's a developer at all. At least, his profile doesn't say so. I think he just finds all these ROMs and posts links to them. I could be wrong, and I apologize if I am if that person is reading this thread, but I don't see where the OP of the 5+ ROM threads is the actual developer for them. It's almost like he does the "announcing" for the devs of those ROMs. And since it does appear that you do not have to be a developer to post in the standard DEV forum, then that makes even more sense. I do know that in another forum I frequented a lot, you were given developer status and only developers could create new threads in the DEV/ROM forum. That was to prevent a lot of "spam" postings of ROMs. Makes me wonder if that's what is happening here.
iBolski said: I see who you are talking about. If you read the OP, at the bottom, he gives thanks to the devs on these ROMs. I don't think he's a developer at all. At least, his profile doesn't say so. I think he just finds all these ROMs and posts links to them. I could be wrong, and I apologize if I am if that person is reading this thread, but I don't see where the OP of the 5+ ROM threads is the actual developer for them. It's almost like he does the "announcing" for the devs of those ROMs. Click to expand... Click to collapse I wish you were correct but nope, he is the builder and maintainer. Trust me many more than 5+ when you include other carriers as well.. But not just the one, others have started as well... It's very frustrating that after 1 week, several messages of a very specific problem (not mine just someone i was helping) on different sites where they are posted.. I have to track down someone that i know can help but has NOTHING to do with any of these roms...and gets zippy cash.. Though he should..lol Anyway, i truly value great developers and have learned who to support and who not to. I like to help people so the developers can build awesome stuff and its my way of keeping the simple crap of your plate so you can do just that..but when i can't even find the answer, the developer should be available. Just saw your edit.. Yes i think that is happening too. I was always under the assumption that builders/maintainers did so for the actual devise and carriers they use.. I guess that's no longer the case.
Oadam11 is a builder of various roms for our G3's from source repositories available for anyone to build from, and anyone to commit to. He may or may not be doing any commits/merge requests - and even if he did those contributions might not be accepted into the various G3 forks. In any case, he might not be in a position to contribute to feature requests or bug fixes. He might not be running his own builds of all these roms, past checking to see if they will boot and more or less work. Say Team Vanir does a fork of their work for the G3, an official one. Ok, then you would ask for support from members of Team Vanir, sure, though you might not get much, depending on a lot of factors (including your attitude...) Then consider the possibility that someone just builds something like Commotio from publicly available sources, with just enough tweaks from somewhere to get it to compile and run, unofficially, on one or more G3 variants. I suspect that is where oadam11 is coming from. He doesn't create the roms, he builds them for G3's. He watches the repositories for each rom he has built for us, and when he sees that rom's devs have checked in and merged useful updates, then he rebuilds for us when he has time. Builds take a while. Then he makes them available for us users to download and install them, after some degree of testing. The point is that he is in no way responsible for supporting the builds he produces of these team's work. It would be impossible for him to anyway. I am sure he gets permission and some degree of cooperation from any team project he builds from, but he is NOT a team member, or major contributor, for all of them. He is a noble builder and distributor, and you should expect nothing more from him than What he is already providing. If you want to get a problem or new feature dealt with on any given rom, you must deal with the team's source contributers by raising issues on their gerrit or maybe working on an outstanding and team-prioritized bug as a contributor. Sent from my VS985 4G using Tapatalk
Thank you..you actually confirmed the point I was making. However, is the average person going to know all this? Of course not...should they do their research prior, of course but they don't... I see good teams being hurt by this as well.. Vanir just had an issue the other day.. Something is being lost in translation and by no means was i only referring to Adam.
I understand. It is interesting that in G+ just a little why ago someone asked David Kessler of Team Vanir who was their maintainer of the G3 Vanir and he replied that they don't have one. There was also discussion about someone providing support, like answering questions. The idea of supporting a clueless user who had tried to flash TouchWiz onto a Vanir device, by beating the user over the head with an iPhone6+ was suggested. The devs have no patience with such users, generally. That said, Holy Angel seems exceptional. Sent from my VS985 4G using Tapatalk
The problem I have, is that when a person POSTS a Rom, and are the OP, they need to support what they post, and help the people posting questions in the thread, or BOW OUT!!! There are people posting and dumping... DONT Post a ROM if you're not willing or able to help the team you are Posting links to... Dont post it and then say "Any problems, contact THEM" THAT PERSON mentioned, has a lot of them, all as OP, none supported other than.."New build up"
Raising the age limit for COPPA The amount of entitlement exhibited in this thread is phenomenal. Yes, by all means don't use a build if the developer (who has actually done some REAL WORK) won't support you to your liking. That will really teach those mean developers a lesson. Don't forget to complain about the slow speeds of free downloads as well. It's also a good idea to stop using a build if the developer won't add features you want, and soon, too.
DeanGibson said: The amount of entitlement exhibited in this thread is phenomenal. Yes, by all means don't use a build if the developer (who has actually done some REAL WORK) won't support you to his/her liking. That will really teach those mean developers a lesson. Don't forget to complain about the slow speeds of free downloads as well. It's also a good idea to stop using a build if the developer won't add features you want, and soon, too. Click to expand... Click to collapse Just because you want a feature, doesn't mean it's a good feature to add. If you did that, you would end up with something that could eventually become impossible to maintain. There are SO many bugs right now in the AOSP code that these devs are trying to fix to make it work on this phone. I would rather those get fixed first. And, do you think you are the only one to ask for features? I'm a developer, not for android, but I write code for a living. And what you are asking for is what we call "scope creep". We have to weed out the "must haves" with the "wants". Must haves are the things that they user must have in order to perform their job. This is usually adding functionality that isn't there currently that is needed to complete their job. The "wants" are "I would like to have the ability to clear out all background apps with a single button or swipe". That is NOT needed on this phone, but it's a nice "to have" option, but it doesn't affect the overall performance of the OS itself. Yes, you might say it does because you can clear out the background apps, but in reality, those apps are NOT running. I don't want to get into the specifics of android app management, but those apps you see in the "recent apps" history are NOT running. They are suspended and not taking up ANY CPU cycles, what-so-ever. If they happen to be, then it's a poorly written app, and it means the dev knowingly circumvented the Android OS app management process which is a big no-no. In that case, you should go back to the dev of the app and demand they fix that. But, you are free not to install the ROM. That's fine and that's your choice, but it just irks me when I see people make complaints like this who probably have no idea what the software development life cycle is all about. To me, fixing bugs right now is the main issue, not adding pretty enhancements to the OS. And who's to say they aren't working on what you ask, especially if you ask for fixes to major issues (such as battery life, radio, etc)? Remember, these are UNOFFICIAL releases. They are based off of AOSP source which is pretty much device-agnostic except when it comes to Nexus devices since those are Google devices and therefore, the AOSP source is built for those type of devices. Android is completely different from iOS. iOS is built for a set of hardware that doesn't have much variance like Android does. Hence, that is why Apple controls both the software AND the hardware of iPhones. It means less fragmentation across devices, but it also means, they decide what is best and you have no way of getting the source. Google releases the source for Android so you CAN have these custom ROMs built. But, because one Android device has a different hardware configuration from another (CPU and GPU's being the biggest ones), then anything that can take advantage of the hardware architecture for a particular phone means having to change the AOSP source to use any of those "advantages" from that hardware. Which then means, that source no longer works on other phones, only for the phone they modified it for. So, give the devs some slack, please. They are working hard on it and it's not one dev. If it were, then give the guy even MORE slack. The source for Android is over 12gb along. That is where it's not even compiled. And, compiling the android source generally takes about 90 minutes. So, each "fix" they do requires recompiling (90 minutes) and then testing. Then, more than likely, the "fix" either didn't work or it possibly broke something else. That means, going back, determining the issue, fixing it, recompiling (wait another 90 minutes) and test again. That all takes time, people. We developers are NOT magicians, even though it might seem like it. So, try to imagine trying to fix all the big bugs that you know about, then have to come here, read through ALL the posts and then log those requests down, prioritize them based on all the other work you have, make those changes, recompile, test, etc. It's not a easy and it gets frustrating. But believe me, when we do fix an issue or are able to give the users what they want, we get an extreme amount of satisfaction knowing that we were able to satisfy the "customer". So please, be careful what you state about devs. Those that do read here usually have thick skins, but complain enough, and they might just quit and then you have nothing. I understand where people are coming from, but you've been blaming the devs when it's not their fault. Again, the android source is huge and it takes more than one person to work on it. Especially if they are responsible for more than one device. Some devs are working on source for more than just this phone. So, add that to what I already stated and hopefully, you can begin to understand what the devs are going through.
Rom development stranger way
can someone tell me why the developers have 2.3.4 rom in development, with bugs and little support ??? when it is better to devote time to a single good and seriously attended !!!! Sent from my Redmi 3S using XDA-Developers Legacy app
Same question. There are a few devs who would work on one build then abandon the project completely, and make another build of a different ROM.
Because most of that So called Development is just copy paste job. those guys don't actually develop anything by themselves. otherwise they could have fixed it, instead they wait for actual developers to fix it and just copy from them. :silly:
kraatus90 said: Because most of that So called Development is just copy paste job. those guys don't actually develop anything by themselves. otherwise they could have fixed it, instead they wait for actual developers to fix it and just copy from them. :silly: Click to expand... Click to collapse agreed
[email protected] said: can someone tell me why the developers have 2.3.4 rom in development, with bugs and little support ??? when it is better to devote time to a single good and seriously attended !!!! Sent from my Redmi 3S using XDA-Developers Legacy app Click to expand... Click to collapse kraatus90 said: Because most of that So called Development is just copy paste job. those guys don't actually develop anything by themselves. otherwise they could have fixed it, instead they wait for actual developers to fix it and just copy from them. :silly: Click to expand... Click to collapse 1. You will know then answer when you try to compile one ROM (Not developing). 2. Compiling a ROM is not just a Copy & Paste work. If it's so... Do yourself.... (its just copy & paste nah..?) So here is a answer. I'm also started Android Development just 2 weeks ago. And i compiled 4 different ROMs : Lineage, Candy, Slim, Glaze. I'm not doing it for you. But for me. I wanted to learn, no one can start from "Coding Everything from Scratch" especially legacy softwares like kernel and other things. So we start from compiling.... When we successfully compiled a ROM by facing and fixing many Errors. We move on to a new ROM, Coz New ROM will give new errors and we can learn to fix them. You may ask "Why you cant learn from Improving a rom...?" and my answer is "NO ONE IS GONNA TEACH ME HOW TO IMPROVE A ROM". Self learning needs lots of trial and error. So we building many ROMs. If you don't like that or you are a cry baby who cries for "XXXXX is not working" or "Poor XXXX". Just stick with STOCK ROM. XDA is for Learning and Not Only for SERVING YOU A BUG FREE, FULLY OPTIMIZED, FULLY FEATURED CUSTOM ROM for FREE. Sorry.... if anything hurts anyone... I mean it.
dineshthangavel47 said: 1. You will know then answer when you try to compile one ROM (Not developing). 2. Compiling a ROM is not just a Copy & Paste work. If it's so... Do yourself.... (its just copy & paste nah..?) So here is a answer. I'm also started Android Development just 2 weeks ago. And i compiled 4 different ROMs : Lineage, Candy, Slim, Glaze. I'm not doing it for you. But for me. I wanted to learn, no one can start from "Coding Everything from Scratch" especially legacy softwares like kernel and other things. So we start from compiling.... When we successfully compiled a ROM by facing and fixing many Errors. We move on to a new ROM, Coz New ROM will give new errors and we can learn to fix them. You may ask "Why you cant learn from Improving a rom...?" and my answer is "NO ONE IS GONNA TEACH ME HOW TO IMPROVE A ROM". Self learning needs lots of trial and error. So we building many ROMs. If you don't like that or you are a cry baby who cries for "XXXXX is not working" or "Poor XXXX". Just stick with STOCK ROM. XDA is for Learning and Not Only for SERVING YOU A BUG FREE, FULLY OPTIMIZED, FULLY FEATURED CUSTOM ROM for FREE. Sorry.... if anything hurts anyone... I mean it. Click to expand... Click to collapse Why did you took it personally lol? it was just an observation. yes there are people who want to learn and they have to start somewhere. nothing wrong in that. but when you see same people doing exactly same thing for a long time and not improving upon that. it becomes clear what they are doing. and i never ask for fix this fix that, cuz i know who are actually developing and who are just waiting for fix to be developed by someone else. so no point asking. you sound like someone who wants to learn. but that doesn't mean everyone else is like you. there are people who as i said haven't learn anything but just copy paste cherry-pick for donation money. i rarely see anyone with their own piece of code. happens even more with kernel btw. and yes i have compiled cm13 2 year ago that's the reason why i know this, and currently using my own (copy-paste haha) kernel for both MG5/nexus 5x. although i haven't released it. nor i'll. (source is on my git if you don't believe). Anyway, best of luck for your learning, i hope you will learn a lot and will be able to fix problems by yourself instead of waiting for others. it's a long road ahead :good:
First of all, people always mistake ROM/Kernel etc development (not talking about app and other development which are indeed) as profession of devs, they do it in their FREE time because they like it, for example you play basketball because you like it. Secondly, when there is shortage of ROMs, you yourself would complain about it, please correct me if I'm wrong. Different ROMs have different flavours, and everyone of us likes tasting different flavours. If you're worried about why a thread owner isn't updating it, you can migrate to other one instead of complaining about it. Some guys have enough skills to compile ROMs, but not the ability to work on source code. So they wait for fixes by those who work on source, and update their ROMs as soon as bug is fixed. Also, compiling can be the start of learning development for guys. Although I agree with @kraatus90 on some points, there are some things that I don't. First of all, there's no point of redoing the whole kernel, vendor, tree source stuff when you can use the available code with some modifications, obviously the one who uses it have to give proper credits to the bringup dev and other contributors. Also it should be moral duty of the forker to improve the forked code, be it in small or big ways. Simply forking, compiling and PUBLISHING is certainly disheartening and condemnable.