With yesterday’s M4 release all wrapped up, this is the perfect time to ‘talk shop’ about the releases in general and some of the comments we are seeing.
What are the M’s for?
The M-releases are our best effort to provide an actual ‘release cycle’ for ourselves and users alike. In previous generations of CM, we were super active but released sparingly, with months between releases and with an unpredictable cycle. This was bad for users, specifically those less likely to use nightlies, and bad for developers on our team – never knowing in advance when we’d collectively say “Okay, let’s do a release now”.
M-releases exist on a monthly cycle to force our hand at not only releasing, but addressing bug-fixes in a timely manner. These releases are scheduled for the first week of every month, usually the first Friday/Saturday. Every M release for CM 11 has gone through a very specific code …
It’s that time again – time for another M-release to make its way to our servers.
This release sees the following updates:
Immersive Mode – prevent accidental clicks on swipe gesture (EdgeGesture service) Bluetooth LE – Wipower SDK apis, various fixes System NavBar – Left Hand mode (landscape only – not available on tablets) Motion Accelerometer support (device dependant) Volume Panel – transparency support Translations – new language additions, localization and long-string fixes MediaPlayer – new apis for Suspend/Resume CM Easter Egg QuickSettings – volume Tile sync fix, Quick Config, Alarm tile shows alarms, User Profile fix Recent Apps Panel – low-end device tweaks Theme Engine – Fix crashes Performance – Speed up booting on multi-core devices, add option to force high-end graphics option on low-end devices Trebuchet – decouple icon mask and background (should fix some icon packs) Settings – multiple hands-free device support Privacy Guard – confirm on permission reset Profiles …
Users who took the most recent update for the CM Installer channel for d2 (Galaxy S3) and jf (Galaxy S4) devices may have seen their devices reboot into a broken state. We take full responsibility for this issue. Items such as non-boots are to be expected to occur in nightly or ‘experimental’ builds, not the stable channel of the installer – the issues were simply unacceptable.
Last week, we made the preparations to generate new incremental over the air updates (OTAs) and full builds for the CM installer release channel. Test builds were generated early in the week and QA tested against all of the Nexus devices and a couple other devices. Builds were cleared for release and regenerated on Friday, for a roll-out on Saturday.
The failures seen arise from unaccounted for repercussions of the recent effort to unify the d2 and jf device trees. The unification process itself was a success, …
First, we’re proud to announce that the Motorola G is now an officially supported device in CyanogenMod. This popular budget phone will carry the designation of ‘falcon’ – with a unified build for both the xt1032 and xt1034 variants. We are in the beginning stages of supporting the multi-sim capable xt1033, so please be patient as we work through that process.
Additional Motorola devices are also seeing the benefits of unification, and in the spirit of our last batch of unified builds, a handy list is provided for the newest batch:
Previous Motorola X and Droid Maxx Dev Edition: xt1053, xt1058, xt1060, xt1055 & xt1080 (latter two previously unreleased)
Previous RAZR HD, Photon Q, Atrix HD, etc. : xt897, xt901, xt905, xt907, xt905, xt925, xt926, mb886 (and the former xt897c)
The new ‘msm’ designations are based on the common architecture used in these devices. As always, source …
Last month we began the process of reducing our usage of carrier specific releases in favor of a ‘master’ release for specific devices. The process has proven successful, with m7ul, m7att, and m7tmo all being retired as designations and replaced by a ‘m7′ (GSM) build.
Beginning with the next round of nightlies (tomorrow), we are extending this unification process to the d2, jf, and htle families (S3, S4 and Note 3, respectively). This unification goes one step further than the m7 example, bringing in both the GSM and CDMA variants into one single package. A handy list is provided to show the old versus new designation for these devices.
Happy February everyone! Another month brings us another CM 11 ‘M’ build.
M3 includes the return of Trebuchet, now based on Kitkat’s Launcher3 code base, and has been completely rewritten by its maintainer Nebojša Cvetković (nebkat). Additional work has been included to provide universal icon pack support by Danesh M (devatwork). If you are coming from 10.2 or on a previous 11-M build, the new version of Trebuchet will preserve your home-screen data (assuming you were using Trebuchet or Launcher3 and don’t wipe when flashing), allowing an easy transition. We have a lot of cool things planned for Trebuchet, including icon mask support, better themes integration, even experimenting with Google Now-like experiences. Look for that in the next few months.
Back to the topic of this post however, M3 begins our focus on user experience and feature integration within CM11 code. You can see the beginnings of this with the new Privacy Guard feature to control …