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. 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
Following the ATRIX HD, the recently announced Electrify M destined for U.S. Cellular is Motorola's newest member of the bootloader unlock program. The Electrify M is basically the RAZR M with minor visual tweaks but, unlike its Verizon sibling, won't come in a separate, more expensive developer-friendly flavor. Instead, like the Photon Q on Sprint and the RAZR i/HD outside of U.S., it's unlockable out of the box.
An unlocked bootloader means Electrify M owners will have full blessing of US Cellular and Motorola to customize software on their devices and flash custom ROMs, in exchange for losing the warranty, of course (in case there is any confusion, Motorola specifies: "Once you get the unlock code, your device is no longer covered by the Motorola warranty; in other words, please don't blame us if things go wrong, even if they appear unrelated to unlocking the bootloader."). Read More
It never rains, but it pours. Yesterday Samsung posted the Android 4.1 Jelly Bean source code for both new Galaxy Tab models and the AT&T Galaxy Note II. Today they're keeping the open source train rolling with the first available code for the new Galaxy S III Mini, the flagship model's 4-inch brother-from-another-mother. The 4.1 code is available now from Samsung's developer website.
If you're wondering why the GSIII Mini needs separate code from the standard Galaxy S III, remember that it's actually quite a different beast under the hood. Read More
Welcome to the newer, friendlier Motorola, where every would-be Android modder is catered to. After creating developer editions of both the new Droid RAZR M and Droid RAZR HD for Verizon (the first from the manufacturer-carrier combo since the XOOM) Google's new acquisition is spreading the love to AT&T. The company announced the ATRIX HD Developer Edition, complete with unlockable bootloader, via its Twitter account today. There's currently no price or date available, beyond the fact that it will be available soon. Read More
Now that we've seen Samsung's Galaxy Note II go up for grabs at T-Mo, Sprint, and US Cellular, it's time we began expecting to see Samsung drop kernel source code for the carriers' respective variants. That's just what Sammy has done, recently releasing the open source kernel files for SGH-T889, SCH-R950_USC, SPH-L900_SPR, and a bonus device – AT&T's Galaxy Rugby Pro, lovingly called SGH-I547_ATT. 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
Update 2: The Android Developers blog has just posted on this, nearly a month later, officially (and finally) announcing the addition of India to the list of supported merchant countries, meaning Indian developers can now sell their apps and games on the Play Store. See the original story for more information.
Update: India has since vanished from the list of support countries for merchants. We've reached out to Google to shed some light on the situation, but for now, it appears merchant support for India has been put on hold. Read More
Many of you probably already know how I feel about CyanogenMod – I swear by it, especially on my EVO LTE. Nothing beats it in terms of bringing a (mostly) stock experience to your device with just the right amount of tweaks and extra features. Plus, there are nightly updates that satisfy my need to stay on the bleeding edge and get a daily fix of… fixes. The only downside to this is that each nightly update (for my EVO, anyway) hovers around 180MB, a download that takes just a little more time than I care to spend sometimes. Read More
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. Read More