Sorry for the clickbait title, but given today’s news cycle from most of the blogs, I couldn’t resist using their same tactic.
For those looking for a good read on Cyanogen Inc’s announcement, head over to AndroidCentral.
To highlight the one take away that matters to CyanogenMod users – We are not bundling or pre-installing Microsoft (or any Cyanogen OS exclusive partner apps) into CyanogenMod.
Edit: Those reading the AC article have asked about ‘ads’ showing up. No, those won’t be in CyanogenMod either.
And yes, that April fools joke is still a prank.
Your nightlies will not see a sudden influx of Microsoft applications – you can put the pitchforks down. CyanogenMod has historically stayed neutral on your services of choice, whether you use Google, Amazon or Fdroid; we leave that decision to you and we have no intention of changing that.
Part 2 of our dive into CyanogenMod Lollipop; let’s take a look at some of the more obvious user space changes and features that you’ll see in CM 12 and 12.1.
As we planned in the last blog post, the 5.1 code has officially migrated out of the staging branches and become the full fledge cm-12.1 branch. What does this mean? This means that we have fully merged in the upstream AOSP Android-5.1.0_r3 tag, implemented most (if not all) of the CM 12.0 features and begun focusing on hardware bring-up for our roster of devices. This also means that the buildbots can be switched over for CM 12.1 nightlies at any time. So what are we waiting for? We want you to ‘dirty flash’.
Dirty flashing is what some enthusiast have referred to as flashing one ROM zip on top of another. This is usually used to …
It seems Lollipop is on every enthusiast’s mind these days, as OEMs have started a steady stream of OTAs. With this multipart update, we’ll look at the most common questions (minus, “what about my device?”), Android 5.1, and what’s new and improved in CyanogenMod.
Let’s start with the latest and greatest Lollipop release, Android 5.1. Released in the second week of March, 5.1 has actually seen two releases – 5.1_r1 earlier in the month and 5.1_r3 just this week. The team has been plugging away at these releases, rebasing and merging like fiends. We’re not quite at the point where nightlies will cross over to being officially branded CM12.1, but as always, you are welcome to track our progress.
The CyanogenMod 12.1 (Android 5.1) source is available to sync, and up and running with few issues on various devices – including the latest developer device the Nexus 6. When …
Due to a change introduced this morning to our BusyBox source, to flash a new nightly moving forward you must do a one-time manual process.
Download tonight’s (2/14) nightly, unpack the zip and use fastboot to flash the boot.img.
Command: fastboot flash boot boot.img
This will allow you to resume the normal update process. Sorry in advance for the hassle, but this was a necessary change for how mounts are handled in BusyBox. As Sony devices use a combined boot and recovery.img (no separate recovery partition), fastboot is the only way to workaround this latest change.
“Today we have a guest post from CyanogenMod contributor, Cyanogen Inc. employee, and co-author of the new CM Theme Engine to provide a brief overview of how the Theme Engine works. Please welcome Clark Scheff. – ciwrl”
CyanogenMod makes it easy to quickly customize & change the look of your UI, allowing you to really make your device your device. As someone that loves to tinker, I like to know how things actually work and I wanted to explain how themes actually work in CyanogenMod.
At the most basic level, themes are simply a mechanism to allow resources to be replaced at runtime (as opposed to compilation time – the time when the build is created on the buildbots).
I’ll get into more details about resources, but for now just think of them as the elements which make up the application’s UI. Whenever an application is started, Android loads up the resources associated with …
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, …