Wow, this happened sooner than we expected - but Google just announced only minutes ago that the source code for Android 4.0.1 Ice Cream Sandwich is on its way to Google's AOSP tree right now. We'll update as we learn more. Here's the original post:
As we know, the source code for Android 4.0 "Ice Cream Sandwich" is going to be published fairly soon, which means developers of all trades will be able to download, modify, and compile it into ROMs. A few great examples of this are handset manufacturers (SE, Motorola, HTC, etc) working on incorporating ICS into new and existing devices as well as CyanogenMod developers merging the source with all the awesome modifications they've added into CM so far.
Since I'm seeing questions inquiring about Android 4.0's source code drop every 5 minutes here and there, I thought it would be a good idea to point out this blurb in a recent post by an Android engineer Dan Morrill, aka morrildl:
I'm curious to see what percentage of our readers who run custom ROMs are using AOSP (Android Open Source Project - something pretty close to vanilla Android, such as CyanogenMod), and what percentage are using something based on stock device ROMs. More specifically, I want to find out if people on certain manufacturers are more likely to go AOSP than others - in other words, is Blur/NinjaBlur pushing more people to AOSP than TouchWiz, or is there no difference?
If you've spent any significant amount of time with Honeycomb, then you know that it has its fair share of shortcomings. Not saying that I don't love Honeycomb -- I'm simply saying that it could use a few improvements. In fact, some of the bugs or missing features that I've come across in Honeycomb make me scratch my head, as I don't understand such simple oversights or how basic functionality can be missing.
Ladies and gentlemen, it appears that cvpcs has achieved the impossible: he's thrown together (but not yet publicized) a build of CyanogenMod 7 that works on the Motorola DROID X!
Naturally, since no one but cvpcs has the firmware yet, there are still a few kinks that need to be ironed out before the ROM goes public - for example, GPS, 3G, Bluetooth, and the camera/camcorder have not been proven to work just yet,
and audio (including phone calls, speakers, the microphone, etc.) definitely isn't functional at the moment.
We all want to squeeze every last little bit of juice out of our devices that we can, and if you happen to have a rooted HTC EVO 4G running an AOSP kernel (such as the one that ships with CyanogenMod), then XDA member -viperboy- just made your life a little bit better. Thanks to him, there is now an easy to way to undervolt your kernel, by way of four flashable .zip files.
Cyanogen has just announced via the CM blog that CyanogenMod 7 Release Candidate 2 is rolling out now for supported devices. The team has managed to work in the changes found in Android 2.3.3, and this is the first RC to pack WiMAX for the EVO (previously it was only found in nightlies). CM7 has been feature-frozen with RC2 as well, meaning the team will focus on fixing bugs from this point on.
Welcome to the first of a new series of polls, where every weekend, we'll ask your opinion on a timely Android-related topic. The goal is to see where the populus stands on issues and foster discussion to broaden our view. So without further ado, let's get into our first poll.
The Great Divide
Ever since the SDK was released, there's been discussion on whether Honeycomb would make it to phones or not.
Boy, do we ever have some fantastic news for the AOSP ROM-loving crowd: CyanogenMod nightlies are finally back, meaning the first official CM7 builds are rolling out as I type this. Sure, they're probably moderately buggy (although generally, CM nightlies are still pretty good), and yeah, they may be missing some features - but let's be frank: it'll still probably be one of the most solid Gingerbread builds around, regardless of what device you're using.