And the nightlies come in the niiiight! Or, in this case, in the middle of the afternoon. Today, the fine folks over on the CyanogenMod team have seen fit to release CM10.1 nightlies for several Nexus devices including both CDMA variants—the Verizon version named 'toro' and Sprint's 'toroplus'—as well as the brand new 3G Nexus 7 hardware. ROMs for all three of the variants are available for download on get.cm Read More
After Google's release of "experimental" binaries for Sprint's Galaxy Nexus variant, Jean-Baptiste Queru (Chief Android Release Engineer) confirmed that the binaries represented not full AOSP support, but the "taking down [of] many hurdles that were preventing [AOSP support]," citing bugs in the network stack as one of the issues yet to be addressed.
Less than one month later, it would appear that those issues have been sorted, as Google today published the toroplus' factory image for the first time. Read More
The Galaxy Nexus variant on Sprint might actually have a chance of being officially supported by Google in AOSP after all, which would be a big step in the right direction for carrier-branded Nexus devices.
If you remember, neither Verizon's nor Sprint's Galaxy Nexus was supported by the Android Open Source Project at launch, with the Verizon's version joining the program over half a year after its release. Even though the Nexus S 4G is fully supported, Sprint's GNex variant remained absent from the Nexus Binaries page and was therefore completely unsupported by the Android team. Read More
OK, OK, that's actually Linus Torvalds expressing his feelings about NVIDIA, but there's no better way to articulate the continued frustration with the complete lack of Sprint Galaxy Nexus support in AOSP. Verizon is [almost] there. Sprint, however, is not. Try finding it (hint: its codename is toroplus) - specifically, the CDMA/LTE binaries.
If you still have doubts about the above notion so eloquently conveyed by Linus' gesture, Jean-Baptiste Queru's comment confirms:
As far as toroplus, the situation is unchanged: there are no plans to support it as a target device for custom AOSP builds.