CyanogenMod 11.0 M6 Is Now Available

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 option

Voice+ – Integrate into settings (under Wireless and Networks > ‘More’)

Blacklist – Add provider permissions

Lockscreen – Fix custom wallpaper crashes and album art issues

Display – Consolidate screen-off animation options (remove checkbox)

Bluetooth – Upstream updates and fix issues with audio routing to select car makes/models and disconnect issues

MultiSim – Additional support patches (15+) and UI/UX modifications

Lockscreen – Disable elements when in custom lockscreen

Quick Settings – Options to show smaller tiles; add BT device name to tile

Quick Settings – Fix QS tiles layout in landscape mode

Usage Stats – Fix screen on stats after boot

Resolve memory leaks in Frameworks

Settings – Show ‘eject card’ action for USB storage

Theme Engine – Introduce new Engine capabilities (chooser to arrive in nightlies this week)

Parallel Shutdown – Decrease shutdown time

Address security vulnerability for icons

Downloads – Add pause/resume support

Trebuchet – Hidden apps and labels support

Remove parallel boot dexopt from stable/cm-11.0 branch

And more (all changes from Mar 29th to April 30th)

*CyanogenMod

Speed 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.