Android One represents Google’s attempt at reaching “the next billion users” – starting today, CyanogenMod 11 (KitKat) builds are available for the ‘sprout’ devices. As the devices are currently setup for CM11 only (work on CM12 is in progress) these builds will trickle once a week, every Sunday.
This release represents a few firsts for us. Not only are these the first Android One devices and first official release of CM for these devices, the Android One device is the first ever officially supported Mediatek device. Mediatek (MTK) devices have been notoriously difficult for the developer community to complete fully functional bring-ups, and this marks a milestone in that effort.
The kudos for this goes to a young upstart CM contributor Varun Chitre, who had the beginnings of CM on the Android One kicked off within two weeks of Google’s launch. He’s dedicated his time since October to bring this device to Android One users, …
Happy New Years (for all you Gregorian calendar folks)! Hope everyone enjoyed the holidays and month of December.
In the CM11 M12 post, we mentioned that we were entering the beginnings of CM 12 work, based on Lollipop. Today, we are enabling CM12 nightlies to showcase how far we’ve come since. The full list of devices ready for tonight’s first rollout is further below.
We would like to note that at this point we consider ourselves 85% complete for our initial CM12 M release. We’ll spend the remainder of this month bringing up additional devices and finishing up the features you’ve come to love from CM11 – implementing them into the new Material UI.
At this point, the following large items are not implemented, but should be in the next few weeks. Some additional smaller tweaks are also missing, but left off this list:
Taking a breather from all the work on L, we snuck in another M release yesterday against the CM 11.0 (KitKat) branch. This release is less heavy on features, instead focussing on stability for various device trees and security fixes.
Notably on the security topic, this release incorporates the upstream Google patches against last months POODLE vulnerability in SSLv3. You can read more about the POODLE vulnerability on Google’s Security Blog. Users are strongly encouraged to update to the latest available build to keep in line with the latest security patches.
Multi-sim users should also see added improvements throughout the OS experience, and there has been similar polishes of improvements and features throughout the system as we look towards sunsetting CM11; CM12 looms over the horizon.
For those of you hopping between M and nightlies, the branch point was November 3rd.
No doubt the big news at the beginning of November was the …
There are a number of issues we could point out regarding the nature of this report – the least of which was the lack of contact regarding this topic prior to publishing. Our followup request to the author for direct references to his claims (or a retraction) has gone unanswered, so we are left to refute this article on our own. This is odd as The Register has historically had good messaging with respect to CM, but mistakes happen.
First, JSSE is not used in Android 4.4, which would mean any vulnerability would be applicable to Android 4.3 or below only.
Second, CyanogenMod does not customize this particular level of code – meaning if such a vulnerability …
Hot off the presses, the 11th M build of CM 11 is making its way to the download portal. With it comes the latest round of bug fixes, improvements and features to our Android 4.4.4 codebase. A high-level changelog is provided below – take a look!
For our nightly users, to avoid conflicts on taking this update please do not apply an M11 build on top of any nightly beyond September 30th, as that was when this code was branched for testing and verification prior to release.
* New Devices: Galaxy S4 Active (jactivelte), Galaxy S4 SK I-9506 (ks01lte), Galaxy S5 GSM (klte), Galaxy Tab 10.1 (picassowifi), Galaxy Player 4.0 (ypg1) * Re-introduce Samsung Galaxy Relay 4G (apexqtmo) support * Fix signal strength showing ’2147483647′ on certain devices * Frameworks & Core Apps: CAF and other upstream updates * Lockscreen: Do not play sounds while a phone call is active & MSIM …
A little late due to the US holiday at the start of the month and some higher than average patches for review and acceptance, but none worse for the wear the M10 release of CM11 is upon us. The M10 code was branched on September 9th, with additional patches merged over the course of the last 6 days to fix identified gaps. A changelog is provided towards the end of this post.
As always, we are not infallible, and there may be items that we have not yet resolved (or know about). To help combat this issue and make things easier for you and us, we’ve introduced a new tool into the CM arsenal, the CM Bug Tracker application. Whenever you crash a system application, you will be prompted with an option to upload a snippet of a log to us – namely the actual crash reported by the system and the stacktrace that accompanies it …