It's easy to be overshadowed in the news today by Samsung. Even if you're Samsung. Today, Samsung released the ICS source code for the Galaxy Tab 2 7.0 and 10.1. We already think the Galaxy Tab 2 7.0 is the best cheap Android tablet around. With the source code available for this device, as well as its super-sized $400 counterpart, we're looking forward to what the dev community will do with it to make it even better.
Sony released the Xperia S open source archive today, providing all the tools necessary to build a kernel and start cooking up ROMs for the Xperia S from Sony's source code. In a post to Sony Mobile's developer blog today, the company also noted that the opening of the Xperia S archive marks the first time Sony has published source code for a product built around Qualcomm's Snapdragon S3.
The post goes on to advise that in order to flash the software, users will need to complete a few extra steps and run a special script (which is linked, along with a proprietary firmware file, in the original post).
Source code. Galaxy Note. AT&T.
What do you get when you combine those three things? If you said "source code for the Galaxy Note on AT&T," then you win a cookie. Go wait over there and we'll bring it right out.
Samsung just pushed the source to its Open Source Release Center for all to grab, but there is a catch. For some reason, there are three different versions of the code, all basically identical, save one line (thanks for digging through the code, JCase).
Unlike some vendors which shall remain unnamed (*cough*, HTC, *cough*), Amazon didn't make us wait for the mandatory open source bits of the Android Fire's kernel and released them over at their Source Code page the same day the tablets themselves started arriving in consumers' hands. The download, which comes as a compressed tar.gz, weighs in at a whopping 809MB.
The source code should allow for custom ROMs and tweaks to the OS, which we can hopefully expect soon, considering the Fire has already been rooted.
With Ice Cream Sandwich on the horizon, we at AP thought it would be a good idea to give you a roundup of what Google's been cooking up in Building 44. We actually know a good deal about the future of Android; I'm talking real, solid facts. These are features Android engineers have demoed or talked about, and acquisitions Google has made related to Android technology. We even have pretty clear timelines for most of them.
Remember the Samsung Infuse 4G? Yeah, the one with 4.5-inch screen and 1.2GHz processor that just hit AT&T shelves two days ago. Well, continuing with its newly-found source-code-release motif, Samsung dropped the code for the Infuse 4G over at the Open Source Developers Center.
Let the homebrewing begin! Hit the link below for download.
Beginning and experienced developers will appreciate the latest altruistic move by the core Android team member Roman Nurik who, now that the Google I/O conference is over, revealed the full sources for the I/O 2011 Android app for everyone to see.
If you haven't used the app yet, I am here to tell you that it's an Android masterpiece, in both UI/UX (user interface/usability) and coding paradigms. The app utilizes the new Fragments API heavily, so the source should provide plenty of implementation guidelines for those just picking it up.
Update: Linux devs are not happy about this.
Update #2: And just like that, only a few hours after this article, HTC released the Thunderbolt kernel source.
If you've been following the "drama" around Android kernel source release timelines and device manufacturers (such as HTC), you should be already aware of 2 forces pushing in opposite directions:
There has been quite an uproar as of late over Google's handling of the source code for Honeycomb, their most recent version of Android. The company announced this week that it would be delaying the release of the Honeycomb source in order to iron out some issues, specifically ones involving running it on small-screen devices (i.e. phones). Andy Rubin gave an explanation as to why these issues exist:
Prepare your party gear and break out the keg, people: Google is officially starting the push of Gingerbread to AOSP (Android Open Source Project) as we speak. Jean-Baptiste Queru just announced that fact, saying he was going to begin pushing the code to the AOSP, and the process is expected to take a few hours.
What does that mean for you? ROMs built on AOSP code (such as CyanogenMod) will now have access to Gingerbread, so expect CyanogenMod for Gingerbread (CM7?) to start cooking shortly.