[HTC Vivid, Raider, Velocity] GSLEON3:
I have had chat's with both guys at on point or another & in jest I probably started this, or some of it anyways.

However, the way I see it is that Android is a Linux fork complete with GPL requirements & in reality it is virtually impossible to Kang anything that is linux or Android related, aside from user side code.

Development at this stage is in it's infancy for the Vivid & Raider due to the lack of sources as well as the lack of developer involvement.

Android is all in all an open source project created with the intent of giving end users more fredom & choices. It is also a fairly easy platform to learn & develop for & on.

Kernels built are based partly on code from Google & sometimes the oem as well. Modifying a Kernel is a fun & sometimes brings us positive changes that improve our devices. How about the addition of the Bravia Engine & XLoud? Cool, right? But nobody thanks Sony in their posts. The whole point of opensource projects & a GPL is that we are supposed to work together to improve devices for ourselves & for end-users. We are supposed to share & collaberate in an effort to streamline our builds, WE ARE SUPPOSED TO BE A DEVELOPER COMMUNITY.

Yes, it's nice to see your name & be recognized for accomplishments, but that should be secondary, if an issue at all, to development. Let's be honest, most everyone cooking roms is "kanging" (for lack of a more accurate word) code from device chef's that have worked devices released before the Vivid, like the Sensation. We are all definitely "kanging' code from LG, Sony, HTC & Samsung.

Many of the Chef's/Cook's or whatever you want to call them, wouldn't even have an idea without work spanning back over a decade when XDA was truly a developer community forum. Look at all the work BuzzLightYear & itsme did & published for the betterment of the community. It's a different time now & instead of power users & developers being the owners of smartphones, now everyone that has a mobile pretty much has a "Smartphone".

Many of you don't even know that I cook roms. I don't publish them though, aside from a close friend or two, because of all this contention about what belongs to whom. Frankly, unless it is a program, more than likely the work has been done or modified somewhere in some forum on this planet. Unless you are truly rewriting a driver or an application, most everything else is part of the GPL & considered opensource.

I like Bananacakes rom. I like the graphics because the higher contrast makes it easier for me to read. I also like WildChild, bot the stability of his roms & him personally. We talk & razz each other at least once a week. I take both of their roms & mesh then into something I use for a daily driver. I use a modded version of the Rezound Incredikernel for my kernel & scripts from a dozen people. I will never publish it. I don't want to hear how I stole this or that, half of which was really stollen from the oem developer anyway, so I refuse to put myself thru that.

Most threads recognize people that have contributed & so many people contribute & there are so many parts to a rom that it's easy to overlook something that a member may have worked on. This crap all started around the time of the TouchPro & TouchPro 2. People stopped sharing source & started trying to lock down their roms & development stiffled. Sure, there were some cooks that made PRETTY roms, but there was no innovation, not truly.

Either this is a community working on an open source project, and like a family we all share from each others experiences & knowledge, or this is the death of development communities & everything might as well be an iPhone since everyone thinks their contributions are their intellectual property.

For this to remain a true development community, we need to share our work in the spirit of open source. This collaboration has to be a two way street though. If you borrow from someones work, then when you find way of improving upon it, you need to publish it, to share it.

And for criminies sake, knock off the 10 year old "I'm taking my ball home" crap. Kiss & make up, shake hands, get a room...whatever...Just share & share ALIKE & lets get on with making the Vivid the best device.

To all non-developing members

: Really, Android is easy to develop for. A ton of the work can be done in a good text editor. There are really goog resources available to help you setup a development environment & even help you learn & write a first simple application. I promise you, it is much less daunting & intimidating than many think. Wild Child is a self-taught developer whom is really not involved in development as a career. I have some professional programming experience, but it is very specific (LANWorks & BACNet). I am not a mobile developer by trade. I'd hate to see either of these guys leave the community, but if they do then step up & learn to help yourself. Start with something you want to change, read learn & then it's trial & error time. Cooking a rom is the easy part. Making it truly unique & perform better than stock is also easy on many levels. It can be as simple making a few changes in text files. We need that. We also need better drivers, our devices are capable of 5Ghz wireless-n connectivity, but the drivers & implementation from HTC prevent it. Better media native compatibility is also another big thing that is possible. Again, this is a community, or supposed to be at least, so get involved. Make an effort.