AndroidOpenSourceProject
Latest
Run Android on an iPhone - with some heavy engineering and caveats
Familiar with cramming one operating system into somewhere it doesn't belong, developers at Tendigi have just created a homemade iPhone case that lets you run Android on your iOS smartphone. (Well, kind of). Fortunately, because of the Android Open Source Project, it gave Nick Lee the freedom to clone the mobile OS and build his own local hardware. Before he went that far, Lee decided to test the concept -- streaming Android across to an iPhone through a cable -- with a Nexus 5. He needed tools that could communicate with iOS, as well as services that let USB cables play nice with an iPhone. Lee also crafted software that transmitted what was happening on the Android devices' screen to the iPhone, while also send touch-input back. The next challenge: cramming it all into an iPhone "case". See it working after the break.
Android Open Source Project maintainer leaves role in wake of Nexus 7 open source issues
If you're upset that Google hasn't posted factory images for the new Nexus 7, you're not alone. Android Open Source Project maintainer Jean-Baptiste Quéru has just confirmed that he's leaving his role in the wake of legal issues that prevent him from publishing a Nexus 7 image with working graphics. While he isn't specific about the nature of the conflict, Android Police and others believe that Qualcomm isn't ready to offer its video drivers for use in AOSP builds. We've reached out to both Google and Qualcomm, and we'll let you know if they have any further insight. In the meantime, don't expect a Nexus 7 image anytime soon -- Google will likely need a new AOSP overseer, and Quéru doesn't see any progress on the horizon.
Broadcom introduces low-power WiFi and Bluetooth chips for the Internet of things
The Internet of things -- that nebulous term usually associated with interconnecting everyday objects in a meaningful way -- is in the news again. Yesterday, Broadcom announced that it's launching a couple cost-effective, power-efficient wireless chips geared towards appliances, home automation and wearable devices. The first SoC, BCM4390, incorporates a highly-efficient WiFi radio for embedded use in products such as weight scales, thermostats and security cameras. It fits into the company's range of Wireless Internet Connectivity for Embedded Devices (WICED) chips. The second SoC, BCM20732, features an ultra low-power Bluetooth transceiver and targets devices like heart rate monitors, pedometers and door locks. Broadcom's also contributing its Bluetooth software stack to the Android Open Source Project with support for both standard and Bluetooth Smart hardware. Does this mean our long-awaited smart toaster's just around the corner? We sure hope so. Follow the source links below for more info.
Google kicks Xperia S Android Open Source Project out of its nest, Sony takes it under its wing (video)
After just under three months of development, Google's wrapped up its experimental work on bringing the Sony Xperia S into the Android Open Source Project fold. According to Sony, AOSP Technical Lead Jean-Baptiste Quéru considers the effort a success, but the device is being taken off the project's roadmap so Mountain View can focus on its own hardware. Currently, an AOSP build boots on the Xperia S hardware with support for SD-Cards, Wi-Fi and its built-in sensors. Audio and the phone's modem are also operational, but they require proprietary binaries Hirai and Co. can't publish just yet. Work on polishing the handset's vanilla Android experience isn't over, however. Sony has moved the code to its GitHub account and is welcoming developers to pitch in and help with the open source effort. For more details and to see what code has already been laid down, tap the second source link or check out the video of the smartphone in action below.
Android 4.1.2 goes live, gives Nexus 7 owners landscape home screen
We've been seeing a mysterious Android 4.1.2 update mentioned in conjunction with a few unreleased devices in the past few hours, so it's only fitting that we're seeing the official release today. Google's Android Open Source Project lead Jean-Baptiste Queru has posted word that the 4.1.2 release should be available on Tuesday for at least those relying on pure AOSP builds of the mobile OS. While we haven't seen the update reach our own devices yet, some Nexus 7 owners already report getting 4.1.2 on their tablets with a pleasant surprise in store: in addition to the expected bug fixes and performance boosts, the software lets the home screen rotate to landscape mode on the smaller Jelly Bean slate. We're keeping an eye out for when other hardware gets the patch, although it's expected that the Galaxy Nexus, Nexus S and Xoom will follow quickly enough. [Image credit: EETimes]
Sony posts binaries to back Googler's AOSP project for Xperia S
When Google's Android Open Source Project lead Jean-Baptiste Queru promised an AOSP build for the Sony Xperia S, we didn't know just how much help he would get: Sony has been welcoming of the effort, but the lack of any immediate assistance didn't make for an auspicious start. Much to enthusiasts' delight, Sony says it wants to be more involved with the back-to-stock strategy than just well-wishing. The company is posting vital binaries like drivers to kickstart the process. It's also planning longer-term help by dedicating senior engineer Björn Andersson to monitoring and patching the project when needed. Sony is still wary enough not to get its hopes up, or ours -- it's not convinced that Queru's strategy will lead to a truly reliable build. All the same, the contribution is an important step towards expanding AOSP's scope beyond its usually Nexus-centric past.
Android Open Source Project targets Sony Xperia S, wants to get experimental
The Android Open Source Project has typically (and understandably) been a very Nexus-focused affair -- until now that is. Technical Lead for the AOSP, Jean-Baptiste Queru, announced this week that for a "new challenge" he'd like to target new hardware -- and Sony's Xperia S is the lucky benefactor. The choice of hardware is said to be due to it being a powerful, current device with an unlockable bootloader, with Queru noting that Sony has always been kind to the project. There's not a lot in the git project right now, but Queru appears keen to rally support from developers to get the ball rolling. Wondering how this might differ from CyanogenMod's device targets? Where CM might have a focus on stability, Queru believes that AOSP will head in a more experimental "bleeding edge" direction. Sound like something you can get behind? Head on over to the source for more info.
Android 4.1 Jelly Bean proven carrying rough but working code for multi-user support (video)
If there's ever been a persistent gripe among families sharing mobile devices, it's been the absence of multiple user profiles -- hand that iPad or Nexus 7 to Junior and you may have to play a spot-the-differences game when it comes back. Some long overdue testing of previously found code references in Jelly Bean shows that Google, at least, has explored ending that anxiety over who uses the family gadgets. Command-line code in AOSP-based versions of Android 4.1 will let you create a separate guest profile, complete with its own lock screen security, home screen layout and limited settings. To say that the code is unpolished would be an understatement, however. Apps and even some notifications cross over from the main account, which could prove more than a little embarrassing if the hardware is left in the wrong hands. At least it's easy to revert back, as the instructions (and video after the break) show. The real challenge will be waiting to see when -- or really, if -- Google gets to finishing multi-user code and turns that Nexus 7 into the communal tablet we want it to be.
Verizon Galaxy Nexus welcomed back into the AOSP fold, Sprint shunned by Google
Slowly but surely Google is bringing CDMA devices back into the AOSP fold after giving them the boot in February over driver issues. The Nexus S 4G was welcomed back last week and now the Verizon Galaxy Nexus is joining it over at the Android open source site. Head on over to the developer portal and you'll find binaries for Android version 4.1.1. The LTE GNex isn't quite a full-fledged member of the family yet though, driver support is currently considered "experimental." So, don't be shocked if there's a bunch of bugs. Unfortunately, we have bad news for Sprint fans. Google apparently has no intention of adding the carrier's LTE Nexus to the list of supported developer devices. Jean-Baptiste Queru, lead of the AOSP, told the Android Building Google group that there were no plans to bring custom builds of the open source OS to the Toroplus.
Nexus S 4G regains AOSP status, Verizon Galaxy Nexus owners left hanging
It wasn't just Verizon Galaxy Nexus owners who were hurt when Google dropped Android Open Source Project support for CDMA models -- officially, Nexus S 4G users had to depend on carrier-approved builds as well. At least one of those software dramas is coming to a close, as AOSP Technical Lead Jean-Baptiste Queru has just confirmed that the Nexus S 4G once again has a full AOSP build. Problems surrounding the phone have been sorted out to give it full CDMA voice and WiMAX-based 4G data while keeping true to Google's original, easily modifiable vision. The download is available right away for the Nexus S 4G faithful, but Queru has dashed any immediate hopes of this being the prelude to its Galaxy Nexus counterpart; the camera, GPS and NFC currently wouldn't work on Verizon's model, even if the cellular components checked out.
CyanogenMod nightlies reach Samsung Galaxy S III, Nature UX critics unite
Let's say you're a fan of the quad-core processor and giant screen of the international Galaxy S III, but Samsung's Nature UX just leaves you feeling cold. Thankfully, the first CyanogenMod 9 nightly builds have arrived to warm you up. They both bring the OS closer to the official Android Open Source Project version while adding the extras that we've seen before, such as theme support, an audio equalizer and gesture shortcuts on the lock screen. Nightlies are well away from becoming polished releases, so don't be surprised if your Galaxy S III goes awry -- the team is already advising starting from a completely blank slate. But if that desire to get more control over the OS is still strong enough to throw at least a slight amount of caution to the wind, the source will provide all the downloads and details needed to give Samsung's interface the boot.
Android 4.0.4 rears its head again, this time over at AOSP
It hasn't made its official open-source debut yet, but Android 4.0.4 should be hitting the repositories very soon. Leaks of the next Ice Cream sandwich update have been circulating since early February, and Moto's Xoom was given the first taste today. Now Jean-Baptiste Queru, an engineer on the mobile OS, has posted over at the Android Open Source Project forums to let us know that the appropriate files are being pushed as we speak. Of course, this doesn't mean that 4.0.4 will hit your handset any time soon... or ever, for that matter. But, it does mean that more custom ROM devs will be incorporating its pile of bug fixes into their products. Watch the source links to be alerted the moment it goes live.
Galaxy Nexus and other CDMA devices removed from Google Support pages
Some of you may have noticed that the Verizon version of the Galaxy Nexus is no longer listed as a supported, official developer device by Google. Despite rumors to the contrary, it doesn't appear this has anything to do with the kerfuffle over Wallet, but instead centers around technical issues relating to the APK files required for CDMA connectivity and the signing of those libraries. Other devices have also disappeared from the support pages, including the Nexus S 4G and the Verizon-branded Xoom. Google has posted an update explaining that, "for various technical reasons" CDMA telephony is handled by binaries provided by the carrier in newer devices. The result is different signatures being associated with those APKs than a pure AOSP builds and, thus, those essential components don't function properly.Google explained the disappearance by saying "we aim to make sure that we are as clear as possible about the degree of support that devices have," before going on to promise all Nexus devices would continue to have unlockable bootloaders and that as many of the closed-source binaries as possible would be made available. For the complete statement hit up the source link.
Ice Cream Sandwich source code released, sync pending go-ahead from AOSP
If you're champing at the bit waiting to get your hands on a nice cool piece of Android 4.0, your wait may soon be over. Pending a final go-ahead from the Android Open Source Project, you'll be able to sync the now available Ice Cream Sandwich source code. Due to the "large push" (presumably because of all the changes), the roll out is going to take some time to complete -- project members will give the final word when things are good to go. If you try to sync prematurely, be forewarned that you'll get an incomplete copy that will be useless. The available flavor is 4.0.1 which will be the version to ship on the Galaxy Nexus, the first ICS device. This release also includes "the full history of the Android Code," signaling the first time Honeycomb source has seen daylight. Can't wait for a taste? The extremely impatient can hit that coverage link below, but we prefer our frozen treats to be properly chilled before consumption. [Thanks to everyone who sent this in]
Google keeping Honeycomb source code on ice, says it's not ready for other devices
Itching to put some sweet, crunchy AOSP Honeycomb on your hardware of choice? You might have quite a wait, as BusinessWeek reports that Google will not release the Android 3.0 source code in the near future, and we just received confirmation of the same. Google forwarded us the following statement, which pretty much says it all: Android 3.0, Honeycomb, was designed from the ground up for devices with larger screen sizes and improves on Android favorites such as widgets, multi-tasking, browsing, notifications and customization. While we're excited to offer these new features to Android tablets, we have more work to do before we can deliver them to other device types including phones. Until then, we've decided not to release Honeycomb to open source. We're committed to providing Android as an open platform across many device types and will publish the source as soon as it's ready.It's fairly clear that the company's motivation here is the same as it's been all along -- Google wants to restrict Android to the devices it was designed for. Though the company long insisted that earlier versions of Android were not for tablets, manufacturers quickly adapted the source code to slates anyhow, and we can imagine the company wasn't thrilled some of the middling results. At that time, Google's only weapon was to deny access to Gmail, Maps and Android Market, which it did liberally (with a few exceptions to the rule) but this time it sounds like it's simply withholding the "entirely for tablet" source code instead of sending cease-and-desist letters out. Another explanation, however, could just be that Honeycomb's not ready for primetime without some OEM help -- last we checked, smartphone support was a far cry from final, and even the finished Motorola Xoom still has a few software kinks to work out. Here's hoping a nice cold bowl of Ice Cream will smooth things over with the open source community before long.
Android 2.3 Gingerbread's source code now available
Want to dig through 2.3 and see what all the fuss is about for yourself? Well, you're in luck, because Gingerbread has just hit the Android Open Source Project's repository, which means you can set up your machine to download the code. It's great news for hardware companies that don't care to get Google's certification to include Android Market access -- but it's also great news for casual and serious hackers alike who are looking to craft some seriously wild, wacky custom ROMs. So, what are you waiting for? Get to it, folks. [Thanks, Mike] Update: Eager coders are being asked to "wait a few hours or a few days" before downloading to balance out the server load -- and while you're likely not interested in doing that, it's probably in your best interest to heed the advice.
