Let’s face it, we love our CM9 ROMs and want to keep abreast of the latest news regarding any developments or updates, right? That’s why the developers of the great ROM wanted to give the masses a status and progress update on where the ROM stands and its future. Among the items highlighted is how much Android 4.0 has changed from previous platforms and the various changes requires updated graphics drivers. The relevance of the need for updated graphics drivers is that the drivers are almost always closed-source… meaning they don’t appear until a device or devkit is released with them. They’ve been able to make some workarounds, but are blocked on some subsystems like the camera.
Moreover, the developers decided to start off with a fresh codebase from Google and are forward-porting features from CM7, keying in on design and better integration by cleaning house on some unnecessary features. For starters, they’ve thrown out the CMParts app, instead electing to add the developer’s custom features directly into the main settings. In addition, the developers realized CM7 had many options that weren’t used, so they’re now taking a “just works” approach— meaning it should achieve a good balance between tweakability and a great out-of-the-box experience.
Of course many of you all are thinking “that’s great, but is my device supported??” Here’s the developers response to that:
“Currently, you can compile CM9 for a small number of devices- notably the Samsung Galaxy Nexus and Nexus S, the Samsung Galaxy Tab 10.1 (Wi-Fi and T-Mobile versions), the HP Touchpad and Motorola Xoom. The next devices to show up will likely be a whole array of Samsung phones (Exynos chipset), with devices based on the Qualcomm MSM8660 and 7×30 chipsets to follow. It’s still unclear if we can provide support for the QSD8x50 family of devices (Nexus One, HTC Evo, etc), but the answer almost always turns out to be “yes” for these kinds of things.”
There you have it folks, the status and progress of the CM9 ROM.
source: CM Blog