A little more than a month removed from our last M-release, the 10.1-M2 releases are now landing on our servers. These builds are based on Android 4.2.2.
We’ve expanded the release list to include quite a few new devices since the M1; the full list is further below.
With this release, we’d like to remind you all that while bug reports on nightlies will get summarily dismissed, we accept and encourage reports to be submitted against the M2 release. By identifying issues in the M-release, you can help to make the eventual ‘stable’ release that much better. Note that our bug tracker has relocated to jira.cyanogenmod.org. Additionally, if you report a bug but fail to attach a log (logcat or adb bugreport), your report will be considered invalid, and closed. Even if your device bursts into flames: no attached log means it didn’t happen.
Devices receiving an M release today are as follows:
Acer Iconia a700
Google Nexus S (crespo, crespo4g)
Google Nexus 7 (grouper, tilapia)
Google Galaxy Nexus (toro, toroplus, maguro)
Google Nexus 4 (mako)
Google Nexus 10 (manta)
Google Nexus Q (steelhead)
HTC One X (evita)
HTC Incredible 4G LTE (fireball)
HTC Evo 4G LTE (jewel)
HTC One S (ville)
LG Nitro HD (p930)
LG Optimus LTE (su640)
LG Spectrum (vs920)
Samsung Galaxy S (captivatemtd, galaxysbmtd, galaxysmtd, epicmtd)
Samsung Galaxy SII (i9100g, hercules, skyrocket)
Samsung Galaxy SIII (US variants d2att, d2cri, d2mtr, d2spr, d2tmo, d2vzw)
Samsung Note (quincytmo, quincyatt)
Samsung Galaxy Tab 2 7.0 (p3100, p3110)
Samsung Galaxy Tab 2 10.1 (p5100, p5110)
As per usual, the code has been tagged in our Github as ‘cm-10.1-M2’. Any device currently receiving 10.1 nightlies, but not listed above, will continue to get worked on until they are ready. This includes the Kindle Fire, Galaxy R and Motorola Devices added yesterday.
The CyanogenMod Team