CyanogenMod 11.0 M6 Is Now Available By Staff Reporter | May 05, 2014 11:03 AM EDT CyanogenMod 11.0 M6 Is Now Available. The âMâs reliability ensures that users can see their next batch of fixes will arrive 4 weeks after the last. This release also allows CyanogenMod to collect JIRA tickets more frequently and track progression or regression of features in smaller windows. Like the âstablesâ before it, âMâ releases are built off the âstable/CM-##.#â branches â the only difference is now frequency and label. CyanogenMod describes that release that it doesnât mean bug free and it certainly never meant feature complete; but with the name âstableâ it gave the false impression that it did mean those things â especially to those risk-adverse from âstableâ to âstableâ. M6 Changelog:Quiet Hours â Fix longpress QS tile optionVoice+ â Integrate into settings (under Wireless and Networks > âMoreâ)Blacklist â Add provider permissionsLockscreen â Fix custom wallpaper crashes and album art issuesDisplay â Consolidate screen-off animation options (remove checkbox)Bluetooth â Upstream updates and fix issues with audio routing to select car makes/models and disconnect issuesMultiSim â Additional support patches (15+) and UI/UX modifications Lockscreen â Disable elements when in custom lockscreenQuick Settings â Options to show smaller tiles; add BT device name to tileQuick Settings â Fix QS tiles layout in landscape modeUsage Stats â Fix screen on stats after bootResolve memory leaks in FrameworksSettings â Show âeject cardâ action for USB storageTheme Engine â Introduce new Engine capabilities (chooser to arrive in nightlies this week)Parallel Shutdown â Decrease shutdown timeAddress security vulnerability for iconsDownloads â Add pause/resume support Trebuchet â Hidden apps and labels supportRemove parallel boot dexopt from stable/cm-11.0 branchAnd more (all changes from Mar 29th to April 30th)*CyanogenModSpeed is also a key priority. The goal is to get a release out every 2 weeks with the same quality and expectations in which their users would have of a âstableâ release (label for that yet undecided). According to CyanogenMod, the current M cycle is every 4 weeks; to get it to 2 weeks is ambitious, but we can do it, and it would benefit everyone. The 2 week cycle allows them to collect and act on JIRA reports with more immediacy. New devices or those that miss a release due to being withheld can also enter the release cycle again at the next build (assuming issues are resolved). The user also has the choice to take or ignore an update.