For those who missed it, Steve Kondik, the founder and lead developer of CyanogenMod, along with several other members of the CM team gave a compelling talk in San Francisco at the start of Google I/O. Delivered during the SF Android User Group Meetup (hosted at Yelp), Kondik's talk took a look at CyanogenMod's role in the Android world, some of the project's goals, solutions, and the challenges the CM team faces in getting CM to new devices, explaining everything from conflicts with proprietary drivers to locked bootloaders and more.
Today is a good day, I think, for source code drops! Samsung has just released the source code for an update for the Epic 4G Touch, Sprint's variant of the Galaxy S II. The update (FF18) is said to be rolling out to devices right now as an OTA. If you want to get your hands on the kernel code to fiddle with it yourself before the update arrives, however, you can head to Samsung's download page here.
The Android development community couldn't be more on fire today now that Android 4.1 has been fully open sourced. While the Jelly Bean flavored CyanogenMod 10 is not just here just yet (though work has already begun), the CyanogenMod team released a fantastic treat for new Galaxy S III owners on AT&T, Sprint, and T-Mobile - official nightlies, available for downloading and flashing right now:
Earlier today, the Jelly Bean source code rolled into AOSP (Android Open Source Project). This is a big deal - one we've been waiting for since the great Google I/O unveiling. What does it mean exactly?
It means that ROMs that are built from AOSP, like CyanogenMod, can now start integrating the Jelly Bean code and release the first true JB nightlies. Not broken ports from the Galaxy Nexus builds - real ROMs.
Jelly Bean was announced at Google I/O just recently, but a posting from Google's Android open source guru, Jean-Baptiste Queru has confirmed that Android 4.1 is hitting the Android Open Source Project (AOSP) repository right now. Time for the developers among you to update your clients to get all the official bits.
This release will be tagged as android-4.1.1_r1 in AOSP. While the source is going live now, the full proprietary binaries for Google-blessed devices won't be rolled out until later.
Nobody does app roundups like AP. If you like this post, consider voting for it on Reddit.
It's time for the Android Police Week In Review, your source for the most important Android bullet points of the week. You can catch a lot of this news in our podcast as well.
- 11 modern Android devices compared with 13 storage benchmarks (spoiler alert: the Transformer doesn't do well).
Android at Arms (legal news)
Welcome back to another week of the Android Police Podcast. Spoiler alert: this one is really long. We're talking about Jelly Bean, Galaxy Nexus banhammering, and the Nexus 7. So at least it's interesting. We think (hope).
Subscribe to the Android Police Podcast:
Android at Arms (legal news)
When Jelly Bean was announced, it's as if you could hear the entire Android community speak in unison: CM10! Anyone who has been around the block a time or two knows, though, you just don't ask for ETAs on CM builds. Of course, it wouldn't really matter if you did at this point - the JB source code isn't even available yet. However, the CyanogenMod Team took the time to address many of the questions on everyone's minds on their G+ earlier today, and we have to admit - it all sounds pretty good.
In a post to the Android Building group earlier today, Jean-Baptiste Queru announced that Samsung's Nexus S 4G has officially and fully been brought into the AOSP fold. The device is now fully supported by AOSP, meaning its CDMA – and WiMax – binaries can now be "properly" distributed. Here's the full text of the announcement: