Week Ending: April 12, 2014
“This Week in CyanogenMod” is an ongoing feature that aims to serve as a one-stop shop for weekly updates. Topics discussed are culled from our social media accounts, gerrit, status updates and general thoughts.
Heartbleed, devices, theme engine and more – plenty to discuss this week.
As a somewhat lucky coincidence, the Heartbleed OpenSSL vulnerability was disclosed during the period of time our data center was offline (Note: downtime was unrelated to Heartbleed). What this did allow us to do was patch all appropriate web assets susceptible to Heartbleed before we brought services back up. Do note, that due to the nature of this vulnerability if you use a common password it is wise to change your passwords once all the other affected sites have signalled the all clear.
On the Android side of things, CM 10.1, 10.2 and 11 builds are unaffected at a core OS level (your apps may use their own OpenSSL implementation). Android 4.1.1 was known to be susceptible, however heartbeats were disabled in Android 4.1.2; if you happen to be on a nightly corresponding to Android 4.1.1, an update is recommended. CM 10.0 stable was released based on the 4.1.2 code and is not impacted.
HTC One Mini (m4)
Not to be confused with our monthly ‘M’ builds, or its bigger brother the HTC One 2012 (m7) – the HTC One Mini is now receiving nightly builds. Your maintainers are veteran CM maintainer h8rift and newcomer Jurica Vukadin (u-ra).
HTC One 2014 (m8)
Marketed as The New HTC One, this device (m8) is the successor to the m7. H8rift, toastcfh, deck, invisiblek and other CM maintainers have already taken up the challenge to bringing CM to this device. No builds yet to share, but we will keep you updated as things progress.
Amazon Kindle Fire HD
Thanks to the efforts of Hashcode (with bootimg setup by verygreen), the Kindle Fire HD 8.9″ (jem) and Kindle Fire HD 7″ (tate) have officially been merged into our Github repository. These OMAP based devices are waiting on one final kernel repository change (really just a rename) prior to making their debut on nightly rotation. Look for builds later this week.
A couple weeks ago, we started a limited alpha test of a new and improve theme engine for CyanogenMod. This new engine pulls together previous contributions from Sony Mobile & T-Mobile and is supplemented by nearly 5 months of work from Cyanogen Inc engineers Andy Mast and Clark Scheff. This week, we merged the core pieces of this new engine into our Github.
So just what is better about this engine? We’d like to think just about everything.
The new theme engine allows the following:
1. Simple creation of themes by compiling on the device
2. System level icon packs.
3. Font packs
4. Swappable boot animations
5. Lockscreen wallpaper
7. Of course all the things the previous engine could do including skins, ringtones and notifications. There is also legacy support for old themes.
Prior to the public alpha, we reached out to theme creators to give them a head-start in playing with the new engine and creating themes to utilize the new features. We are also working on tools to make themes easier for everyone to create. Lots of fun stuff is just around the corner
A quick stroll through our recent features merged in to CM 11 mainline:
* Lockscreen: custom wallpaper
* Lockscreen: third party keyguard support
* Translations: migrate to Crowdin support
* Blacklist: add explicit permissions
* SMS: support for “mark unread”
* Voice+: migrate options to settings menu
* Quiet Hours: 4-state support(timed active/inactive, forced on/off)
Patches still needing review include custom grid layouts and hidden applications in Trebuchet and OpenCNAM caller ID support in Dialer.
We’ll do a wrap-up of the joint giveaway between CyanogenMod, Cyanogen Inc. and OnePlus – but first, a very special thank you to CM contributors Bumble-Bee, Dvtonder, and mad-murdock. We couldn’t have pulled off the international pieces without their assistance.
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.