That sure didn't take long. Just two days after the official announcement - and still a few days away from retail availability - the Droid DNA has already been rooted and gotten some goodies from famed Android modder/hacker dsb9938. Apparently the DNA is unlockable using HTC's official bootloader unlock tool, which allows a custom kernel to be flashed. The first available kernel has only been slightly modified to allow root in adb connections - a requisite in order to flash the custom recovery and root the device.
While Android 4.2 is now making its way into AOSP (Android Open Source Project), support for one device in that code is not, and won't be for some time: the Nexus 4. Android maintainer JBQ (an awesome guy we quote a lot on days like this) has confirmed that the "Nexus 4 is not supported in AOSP at the moment: no source files, no binaries."
JBQ is not able to comment on why this is the case, or when we might expect the Nexus 4 to join Google's big happy AOSP Nexus device family, though obviously if Google could merge it into AOSP today, they would.
Today, with the official release of the Nexus 4, Nexus 10, and Nexus 7 HSPA+, Google has released the Android 4.2 SDK, "a new and improved Jelly Bean."
Along with the SDK release, Google has made available SDK Tools r21, the Android NDK, and of course some helpful API documents. Highlighting some of the benefits of the new SDK (and, by extension, Android 4.2), Google touts "Renderscript computation directly in the GPU" for the Nexus 10, "a first for any mobile computation platform," lock screen widgets, Daydream, incredibly enhanced support for external displays, and optimizations for international users.
With all the excitement of Nexus availability and the Android 4.2 source code being pushed into AOSP this morning, one little statement by Android developer JBQ regarding 4.2 device support in the AOSP announcement was easy to overlook.
-There is no support for 4.2 on Nexus S and Xoom. Those devices should continue using 4.1.2.
Yep, that (very, very likely - it's intentionally vague) means exactly what you think it does: it's the end of the road for software updates on the Nexus S and Motorola XOOM (and yes, that means all variants).
Hot on the heels of the official retail availability (and now non-availability) of the Nexus 4, Nexus 10, and Nexus 7 3G, Google has updated the Android Developers Nexus images page with brand-new builds based on Android 4.2. The images, for now, are limited to the Nexus 10, Nexus 4, Nexus 7 (Wi-Fi and 3G), and Galaxy Nexus (Takju) Play Store variants.
In addition, driver binaries for the aforementioned devices (except the Nexus 4 / Nexus 7 3G) and more have also been posted here.
After numerous nightly and monthly builds, CyanogenMod 10 is finally ready for its stable release. The custom ROM is already available to download for the Samsung Galaxy S II LTE, LG Optimus Black, and the Samsung Galaxy S III (both Verizon and Sprint models).
As part of a statement on the general state of software updates at Motorola, VP of Product Management Punit Soni has revealed that a new early update testing program will be unveiled, known as Test Drive.
We know it’s important for many of you to get the latest Android software upgrades onto your phones as quickly as possible. With that in mind, we’re also introducing Test Drive, a new program that will allow consumers to take our major software upgrades for a trial run and provide valuable feedback before we launch the upgrade publicly. Starting with Android 4.2, the next iteration of Jelly Bean, we will release a preview of our software to a few hundred consumers that sign up for Test Drive. More details on how to sign-up and participate will be announced on the blog soon.
Sony announced today on it's official Sony Mobile Developer blog that the Xperia S "experimental AOSP support" project, first announced by JBQ back in August, is no more. It was an interesting idea, to be sure - a non-Nexus device that would be supported both with the help of members of the Google developer community, as well as AOSP maintainer JBQ, on the AOSP main branch.
The project did see some success, too - Android was booting, and according to Sony, Wi-Fi and sensors were up and running.
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.