The Xperia E, Sony's low-end Jelly Bean-powered smartphone which was announced back in December may have another trick up its sleeve yet. The manufacturer is offering owners of the device the chance to test out Mozilla's fledgling Firefox OS on the device via a downloadable ROM. Meant for "advanced developers," the ROM comes with a few warnings from Sony, chiefly that you should know what you're doing before you get started.
Claiming the title of the first MSM8660-packing devices to get CyanogenMod 10.1 nightlies, LG's Optimus LTE and Nitro HD (su640 and p930) joined the lineup today.
In a post to Google+, CyanogenMod is sure to note that the introduction of the Nitro HD and Optimus LTE does not necessarily indicate the imminent support of other devices that use Qualcomm's MSM8660 chip. "What it does mean," the post goes on, "is that the first hurdle towards more devices has been achieved."
That said, the nightlies are still great news for Nitro HD/Optimus LTE owners who have been hankering for an AOSP-inspired Android 4.2 experience with the full CyanogenMod treatment.
After more than a month of unofficial CyanogenMod builds, the HTC Holiday (also known as the Vivid, Raider, or Velocity) has joined the ranks of devices with official CM support, receiving its first weekly CM10 build earlier today. It's not yet clear when or if the Holiday's build cycle will transition to a nightly schedule.
At the time of writing, the build's known issues involve Bluetooth Audio skipping, hardware video playback, tethering, and the inability to record video in 1080p.
In a post to Google+ today, it was announced that Cricket's Samsung Galaxy SIII (otherwise known as d2cri) had received its first official CM 10.1 nightly, meaning Cricket-connected SIII users can enjoy the Android 4.2-based ROM with all the tweaks and features CyanogenMod fans have come to expect. Those who have followed the Cricket GSIII's progress toward an official nightly build will also be happy to learn that the device's camera woes have reportedly been solved.
These guys work fast, don't they? After "noticing some demand" for third-party CM 10.1-based ROMs on the new Nexuses, the team decided to go ahead and start rolling out official nightly builds, beginning with the Nexus 4 (mako). This is the first official CM 10.1 build to be released thus far, and is currently based on 4.2, as 4.2.1 just hit yesterday.
The team noted on G+ that builds for the Nexus 10 (manta) should be the next on the list, and will roll out "as soon as it's ready." All other devices will continue to get CM 10 (Android 4.1) builds while they finishing merging the 4.2 code.
One of those features is a root-enabled file manager, which was announced on the Cyanogen Google+ page a few hours ago. Judging from the screenshots, it looks to blend in seamlessly with other CyanogenMod features and the rest of the Android OS, with a really nice looking interface.
Earlier this evening, CyanogenMod's Google+ page published an announcement that read "Who says Everest is in Nepal?". That's right – the Motorola Xoom 3G (GSM) variant has joined the list of CM-supported devices, getting its first experimental build dated 10-17.
Steady Hawkin, in a comment to the announcement, notes that the experimental build is "still a WIP," and encourages users to report any issues they may encounter.
If you're a Xoom GSM owner looking for some CM10 action, just keep an eye on the CyanogenMod download center's Everest page (linked below) for the latest builds.
Moments ago, CyanogenMod's Google+ page announced that Sony's Xperia T, the flagship device we first covered during IFA 2012, is joining the CyanogenMod device roster, offering a link to the device's Gerrit code review page and a quick James Bond reference.
What's more, the Xperia T's first (experimental) nightly build is already live in CyanogenMod's download center.
If you've got an Xperia T and have been itching for CM goodness "shaken, not stirred," keep a close watch on get.cm (linked below) for the latest nightly builds.
It could oftentimes be unstable and not properly tested, lacking any changelogs, but eventually evolving into alphas, betas, release candidates, and finally stable releases.