The Galaxy Note II and its tablet big brother the Galaxy Note 10.1 were both released in 2012. That being the case, the odds of them getting an Android 6.0 update are about as good as the Chicago Cubs winning the Super Bowl. Of course, a lack of updates (even for hardware that might not meet the minimum requirements) is a big part of what makes custom ROMs so popular. So it is that the CyanogenMod ROM's version 13, based on AOSP code for Marshmallow, has come to a handful of older Samsung devices.

Relatively low prices and a wide-open attitude towards user customization make OnePlus phones popular with the ROM crowd. They're getting a big boon today, as official CyanogenMod support comes to the smaller, cheaper OnePlus X. The X is equipped with the custom Oxygen OS, but for those who prefer the community-built ROM, CM13 is now available in nightly build flavor. The first release is up on CyanogenMod's download page right now.

The Galaxy S III, first released back in 2012, only has official software support up to Android 4.3. No matter: the folks at the CyanogenMod development team are keeping the device alive long after Samsung threw in the towel. Today the AT&T, T-Mobile, and Sprint variants of the GSIII all get their very first nightly ROM builds for CyanogenMod 13, which is based on Android 6.0. You can find them at the d2att, d2tmo, and d2spr listings on the CM download page, respectively.

The CyanogenMod Team continues to expand its list of officially-supported devices, and now the LG section of said list is longer by four entries. Yesterday the CM servers started spitting out nightly builds for the LG G3 S, the LG G3 Beat, The LG G2 Mini, and the LG Optimus L70 smartphones. All of them are CyanogenMod 13 (Android 6.0), and they're all available for download and flashing right now. At the time of writing three of them have two nightly builds, while the G2 Mini has only one.

The CyanogenMod team continues to develop builds for new phones, and today we get support for two budget-oriented options that are popular with the unlocked crowd. The Moto E 2015, a phone with a relatively small screen and a tiny price, and the Huawei Mate 2, a phone with a relatively enormous screen and a price that's still pretty small, both have CyanogenMod 12.1 (Android 5.1) ROMs waiting for them on the official download site.

The CyanogenMod ROM development team continues to add to its ever-expanding range of officially-supported devices. Today we get a little-known variant from a huge manufacturer and a huge phone from a little-known manufacturer (outside of China, anyway): the dual-SIM version of HTC's 2014 flagship One M8, and Xiaomi's Mi4, respectively.

The Nexus Player is (so far) the only consumer device available that runs Android TV, which means a considerable portion of the people who own one are serious Android fans. It follows that they're prime candidates for ROM flashing (not to mention Android Police readership), so they'll be happy to know that they can now install CyanogenMod on their set-top box. CM 12.1 (based on Android 5.1) is now available in nightly form for the Nexus Player.

A custom ROM for a set-top box makes a little less sense than it does for a phone; Android TV is intended to be a rather encapsulated media-focused experience, with limited expansion via apps only.

Motorola's G series became a hit almost instantly thanks to solid build quality, clean software, and a fantastic bang-to-buck ratio. The second-gen version is no exception, and its upgraded hardware has also caught the eye of the enthusiast and aftermarket community. Though the standard model of the Moto G 2014 already has Android 5.0 (at least in some places), owners now have the option of installing the CyanogenMod custom ROM.

Here at Android Police, we're no strangers to digging around in Google's code and finding surprising stuff inside. Apparently some members of the CyanogenMod team did the same, and found a hidden feature in KitKat: Heads Up notifications. These floating notifications are meant to be used in full-screen apps or Immersive Mode, but for whatever reason, they aren't switched on in AOSP code. (Perhaps they're intended for the next major Android release.) You can probably guess what happens next.