[Galaxy S I9000 Android Development] Kaik541:
Actually, you and I disagree on this quite heavily. While CM definitely has the AOSP look and feel and is based on the AOSP code... it is not AOSP. It's AOSP-ish (it's as close as you really need to go to AOSP, in my opinion... it has all the same benefits and infinitely more features and configurability).

Now onto the crux of what you said, CM7 is not pure AOSP. By it's very definition it isn't AOSP (as it's been heavily modified to run on a number of devices that AOSP cannot). There are more features added to CM that never had any plans to come to AOSP. For instance, with discussion of LED notifications, did you know the Nexus One had a blue LED? Google sure did, yet nothing utilized it and there was no way to enable it outside of third party hacks and trickery... guess what, the ability to enable that blue LED and put it to use is in CM. Now, we're sitting here without any type of notification LED's, codeworkx is of the mindset that if you want a notification LED, Samsung isn't the manufacturer to buy from (and I agree, I only know of two android devices they have that include them: Epic 4G and Epic 4G Touch), but that doesn't mean we can't add additional functionality to our phone that the community created. CyanogenMod describes itself as "community-driven" and "community-focused," and excluding features because you can't see the benefit does not encompass the entire community. I, for one, find the LED notifications to be a wondrous addition to this ROM so I don't have to constantly flip my phone on and off to see if I have a text message (shockingly, my phone does not sit in my pocket all day, so I may have gotten a message while I walked away, this makes my life easier). Add to the fact that the controls for this are 100% within the CyanogenMod settings and can be disabled pretty easily (quiet hours works, as does setting "force off" to LED notification settings). It's there for those who want it, and you can turn it off if you don't. On top of that, I for one have never experienced SoD caused by LED notifications (I did get the random touchkey locks with the original driver, but those have been eliminated thanks to Daneshm90's, techmik's, and pawitp's work).

Now onto the Voodoo Color discussion, you're right in theory. We had our fair share of color temperature arguments when the 2.3.3 merge happened (we were affected the same way the Nexus S was from Google) and we decided to leave the colors as they came from Google. There was a huge whiplash from the community complaining about these color temperatures and outcries and demands for Voodoo Color to be integrated. Eventually, atinm sat down and decided to return the color temperatures to a more pleasing value similar to what was set on a stock ROM. This was proceeded by ANOTHER whiplash from the community complaining how things now looked more blue and over-satured followed by even more demands for Voodoo Color to be integrated. Coming merely from the mindset of "you can't please all the people all the time," we said "Voodoo Color is incompatible with our goals for CM7" which is true as we also opposed the necessity of a third party application to enable features which should be native. It was also the same reason we held back so long on including Voodoo Sound (I've yet to hear a single person bemoan the fact that you have to use the Voodoo Control application to modify that at all, yet currently every single one of you are using the Voodoo Sound driver (v10) without even using the application), yet it's been integrated in a way that extends the original driver file without a secondary file clogging the source (and also removed the "voodoo" references, as it's not magic, just code). The sysfs was left in and you can all modify to your heart's content, but the default settings are more or less agreed to be the "optimal" settings and don't require the application to be initialized or even installed to take advantage of them. As for Voodoo Color, in supercurio's form, it won't be merged. Pawitp is taking his OWN stab at it, and to which he even says the "skeletal code is based on supercurio's implementation", but varies slightly. For one, the gamma hack doesn't work and it only supports RGB tuning. On top of that, the default color temperature is not modified at all. So we could add this commit tomorrow and you wouldn't notice a damn thing has changed UNLESS WE TOLD YOU or you opened the Voodoo Control application yourself and modified the settings. This will grant users the ability to modify their screen temperatures to their liking and, if you're like me and can't be bothered because you don't mind the way it looks now, doesn't impair anyone else's ability to use the ROM... then what's the problem? On top of that, adding this feature will encourage more people to use the stock kernel so we can stop having random complaints three, four, five times a day of people coming in going "so I installed Glitch Kernel M2k34 HGG L12 and now I'm bootlooping, what do?"

CyanogenMod is not about Google's AOSP. It is about a clean experience, with more configuration options than you can throw a stick it, while being stable and fast. Sure it's open source, and we label ourselves as "AOSP" because our developers do often submit patches back upstream to the Google code review (which doesn't always make it in, unfortunately). Our developers are proud of what they've accomplished, and there's a reason these ROM's exist on devices that *already* have a native AOSP, manufacturer (and sometimes, even Google-built) ROM. You think people running CM7 on their Nexus S's and Nexus One's are doing it for ****s and giggles? Or might there be something missing in AOSP that CyanogenMod offers?