TouchWiz getting you down? Of course it is, because it's TouchWiz. Now that we have the Samsung mocking out of the way, down to the news: there is now official support for CyanogenMod on the T-Mobile and Sprint variants of the Galaxy Note 4.
Prepare your eyes and ears, because CyanogenMod is introducing a new boot animation in today's nightlies (for CM 12 builds). Your eyes need to be ready because this time, the background is white. Your ears, on the other hand, need to be ready for all the inevitable whining about how some users wish it was still predominantly dark. Rather than tiptoe around it, here are the goods:
As long as you aren't offended by the color scheme, it is actually quite nice.
CyanogenMod supports a few new devices today, all of them Sony. Just head over to the CM download section and you can get nightly builds for the Xperia Z3, Z3 Compact, and Z3 Tablet Compact with LTE (that's Scorpion). This follows the WiFi version of this tablet getting support just a few days ago.
Xperia Z3 Tablet owners with a custom ROM addiction may be happy to know that CyanogenMod now has the hook up. If you're excited by this news, you can head over to CyanogenMod's crib, knock on the door, and ask for scorpion_windy. Just be careful. Scorpion_windy might not be in the mood.
On your way out, tell any DROID Maxx owners you know that CyanogenMod may have someone in the back working on obake again, because there are two freshly zipped files currently up for grabs.
Micromax's Yureka phone for the Indian market has been the center of quite a bit of controversy in the more passionate parts of the Android community, thanks to its official build of the CyanogenMod custom ROM. But if you happen to own one, said controversy probably isn't as important to you as the phone's ability to be tinkered with. So if you're ready to try another ROM on the Yureka, here's an official build of the Team Win Recovery Project to enable your tinkering.
Just a day after pushing Lollipop nightlies to over 30 devices for the first time, CyanogenMod has now added more devices to the fray: the gambit of Android One phones, the LG G3 D855 (international), and the Nexus 6. Android One devices, owing to the control over software and hardware that Google has in that program, share a single ROM under codename "sprout."
For now, the Android One builds are experimental.
We have been wondering for a while when we'd see Lollipop-based builds from CyanogenMod, and now is that time. For this first round of nightlies, 31 devices will be supported with many more to come in the near future. CyanogenMod 11, based on KitKat, will now be on a weekly update schedule until its M13 release, after which development will be frozen. While some bugs are to be expected, all supported devices should have core functions working smoothly right away.
Most of the news about CyanogenMod over the last month or so has been about Cyanogen Inc.'s very public spat with enthusiast manufacturer OnePlus. But believe it or don't, work continues on CyanogenMod 12, the custom ROM team's version of Android Lollipop. One of the more interesting changes to the new version was spotted over on the Android subreddit: starting with CM12, CyanogenMod will no longer require a separate app to manage root permissions.
The situation between allegedly independent manufacturer OnePlus and its former software supplier Cyanogen Inc. is... strained. After the software company signed an exclusive deal with Indian manufacturer Micromax, the company refused to supply its CyanogenMod ROM for the OnePlus One in India, then Micromax attempted to block sales of the One in that country, a situation that still hasn't been resolved. OnePlus has formed its own team of software engineers, and is now making its own phone ROMs independently.
It's been a long and winding road to find the truth behind the recent announcement that Cyanogen Inc. had signed an exclusive deal with Micromax in India. OnePlus made waves when it said that meant there would be no CM updates for the OnePlus One sold in India, but Cyanogen Inc. made a blog post saying all global devices would get updates, and all was well. Except it isn't. A new post on the Cyanogen blog expands on the situation.