CyanogenMod updates on CM11 builds based on Android 4.4 KitKat


CyanogenMod updates on CM11 builds based on Android 4.4 KitKat

It looks all the developer communities started working on builds based on Android 4.4 KitKat. Yesterday we reported on what AOKP says about Android 4.4 builds and now CyanogenMod also updated their plans on Android 4.4 builds for supported devices.

CyanogenMod team pushed the Android 4.4 code within 4 days of the release and they already started working on integrating the existing CM features into new builds. They already have milestone builds for bunch of devices like HTC One, S4 Mini, Nexus 10, Skyrocket etc.

Cyanogenmod also says though Android 4.4 KitKat is optimized for devices having low memory, it does not mean that CM will now work on builds for the earlier devices that they already dropped the support. Any device with memory of atleast 512MB and currently supported by CM should get new CM11 builds too. There is no time frame on when will the nighlities or the stable versions be made available, but it looks some of the devices already got builds (with some bugs ofcousre ) based on CM11,

Here is the complete post from cyanogenmod

Speaking of CM11…

The source code for Android 4.4 began its release on October 31st (yay Halloween!). From there, it took us roughly 4 days to get the code whipped up into shape and pushed up to our Github repository, with amanifest to match. So what does this mean for you actually running KitKat on your device? By merging in the core projects and overall Android 4.4 code, our talented team of contributors have begun the process of integrating (or reworking) all the CM features that you have come to love. This milestone also kicked off the bulk of the device bring-up efforts, and we are already seeing good results. Just to showcase a few:Xperia THTC OneS4 MiniGalaxy TabNexus 10Skyrocket and many  more (yes, including the Galaxy Nexus, Nexus 4, Nexus 7 (12/13) and Nexus 5).

To the larger question of device support, we have two general comments. First, and we’ve said this previously, just because KitKat is touted as being better for lower RAM devices doesn’t mean we will be bringing back support for devices that we’ve dropped in the past. We were already operating under a 512MB RAM minimum, so that point is moot. The thing Google was trying to say with the lower requirements was directed to OEMs, not end users. There were still OEMs out there shippingnew Gingerbread (2.3) devices because they believed that ICS and higher were too memory hungry. The new minimum requirement is to tell these OEMs to stop Gingerbread devices and instead focus on KitKat for new low end devices moving forward. This in no way means the Moto Droid or Nexus One will suddenly see the necessary OEM cooporation to jump to KitKat. Sorry to burst that bubble, but perpetuating that misconception would just drive further confusion.

Second, there is no list of devices that will get CM11 – statuses change daily and we wouldn’t be able to provide one at this stage anyways. Our goal is everything that got 10.2 will at the least be attempted to be brought up to 11 – but this is not a promise and goals can be missed. Notably, OMAP support is lacking, so those Moto devices that rely on that SoC may not make the jump. I’m not saying one way or another at this moment (again, its too soon to tell), but do be prepared for some future post outlining what devices, and more importantly why some devices, will not be making the jump to 11.


Inevitably some of you skipped the above and jumped directly here :p. The goal is to have things moving in full force for CM 11 nightlies by the end of this month. In the meantime, individual maintainers have started the ‘unofficial alpha’ process to reach a larger test audience and to satisfy those that need to flash asap. Don’t know your maintainer? You should get to know themBy no means am I saying nag them for a build, but many run their own threads to discuss their own status updates – worth following for those interested in that day to day information.

Want to learn?

I suppose to most people the process of moving a device from 10.2 to 11 is a black-box, something that someone extra talented just ‘does’. Well, we’re all about education and the learning process here at CM, so on that note, fattire has taken the extra step of documenting out the process to updating the Nexus 7 (grouper). He has two threads, the first a ‘why should I learn’ and general info and the second is specific to the the CM11 code. Worth a read even if you aren’t going to go through with the process.

We’re also working on a document geared towards common issues our devs have run into with tips/tricks to help resolve them. We’ll share that next week :)

Got a suggestion for a topic you’d like to see in the next round-up? Let us know in the comments below. All device/port requests will be ignored.

Source : @Cyanogenmod

Unofficial CM11 builds for many devices popped up on XDA. check here for a consolidated list.

About Praneeth Kancherla

I work as an Oracle Database Administrator & love the most customizable smartphone operating system - Android. At AFN I try to bring you latest on android/smartphone news.

Loading Disqus Comments ...
Loading Facebook Comments ...