CM 14.1 rolling out for the 2014 Moto X, Galaxy S3, HTC One Max and more

The incessant CM 14.1 rollout continues unabated, with a big bunch of new supported devices added to its warm Nougat embrace. CM 14.1 is based on Android 7.1 Nougat, delivering the latest and greatest Android has to offer with some CyanogenMod specialties on top to devices that would otherwise languish back on Lollipop or worse.

Nightlies are now available for the following devices: Verizon Galaxy S3 (D2VZW); international Galaxy S3 (I9300); Verizon HTC One Max (T6VZW); HTC One Max (T6); LG G3 (Canada)(D852); Moto X 2014 (Victara); Redmi Note 3 (Kenzo); Redmi 3/Prime (ID0); Xiaomi Mi Max (Hydrogen); BQ Aquaris E5 4G (Vegetalte); Oppo N3 (N3); Oppo Find 7a (Find7); Oppo Find 7s (Find7s).

To download the firmware and CyanogenMod recovery, just hit the CM Downloads page and look for your device’s codename on the left. When CM 14 dropped, Steve Kondik said CM was pushing for a return to its community-driven roots. With this level of support for various aging devices, they’re certainly on the right track for regaining any fans they might have lost along the way.

When was the last time you flashed CyanogenMod? Will you be jumping on CM 14.1?

CyanogenMod 14.1 now available for Nexus 5, Galaxy S3, Nextbit Robin and more

CyanogenMod 14.1 support has reached even more devices. The latest version of CyanogenMod, based on Android 7.1, was made available for the first time on November 8 for ten-or-so popular handsets. Since then a number of additional devices have made the ‘nightlies’ roster.

The most recent handsets to receive nightly builds include Google’s Nexus 5 [Hammerhead] from 2013 and Samsung’s Galaxy S3 [i9300] from 2012, as well as:

CyanogenMod 14.1 is a custom ROM which delivers an experience similar to that of Android Nougat. It’s still a work-in-progress, so flashing any of the nightly builds mentioned below means you may encounter bugs and missing features.

When announcing the first wave of CyanogenMod 14.1 devices, Cyanogen Inc. co-founder Steve Kondik said: “Now is a great time to get involved with the project […] – CM is returning to its community-driven roots.”

See also:

CyanogenMod 14.1 arrives for the HTC One A9, One M8, LG G3 Beat, and others

4 days ago

Several days ago, Cyanogen announced that the company would be going forward without Kondik, following a post in which he revealed problems he’d experienced while at the company.

Cyanogen Inc. co-founder Steve Kondik speaks out about company failings



Cyanogen Inc co-founder Steve Kondik has posted a statement regarding news this week that the company is closing its Seattle office and laying off staff. In the statement, published on the private CyanogenMod developer Google+ community, Kondik offers his thoughts on what happened at Cyanogen and what the future holds.

“We started the Inc with the intent to bring CM [CyanogenMod] to more people and ship on devices out of the box. I hired everyone I knew, including a lot of community folks, moved everyone to Seattle and we got to work. We got the project in order after years of technical debt, and started to have some successes with our first devices,” Kondik wrote.

“Unfortunately once we started to see success, my co-founder [Kirt McMaster] apparently became unhappy with running the business and not owning the vision. This is when the ‘bullet to the head’ and other misguided media nonsense started, and the bad business deals were signed. Being second in command, all I could do was try and stop it, do damage control, and hope every day that something new didn’t happen.”

Cyanogen Inc. co-founder Steve Kondik speaks out about company failings 

Cyanogen Inc’s Kirt McMaster (above right) has come under fire several times in recent years, notably for making provocative remarks like “we’re attempting to take Android away from Google,” and his interactions with OnePlus found Carl Pei when the companies ended their partnership in 2015.

As well as referencing McMaster’s role in Cyanogen Inc’s recent problems, Kondik also acknowledges his own contribution. “I fucked up and got fucked over. It’s the Silicon Valley way, isn’t it? First world problems in the extreme? It hurts, a lot. I lost a lot of friends, and I’m truely [sic] sorry to everyone I let down. I wish I had made different choices and trusted different people (especially one in particularly early on), but all I care about now is figuring out what to do next.”

See also:

CEO denies rumors that Cyanogen is shifting focus to apps

July 25, 2016

Whether Kondik will stay at Cyanogen Inc remains to be seen, however he stated: “It’s been a huge part of my life for 8 years now and I don’t want to let go of it,” before asking the Cyanogen community about what direction to go in from here.

“1. Should we keep going? Is it worth it? I’m sure I can crowdfund the project, especially if we did something like “Darkside” and really revitalized it. I’m not sure of the endgame yet, though.

2. The main IP is the brand and trademarks. I don’t know if I can get it back without a fight, and I’m tired of fighting. We will likely need to fork and rebrand, which might not be a bad thing. Would you support it?

3. If we reboot, what should we do differently?

4. The rest of the ROM community seems to be highly dependent on us, but simultaneously wants us dead. How on earth do you fix this?


What are your thoughts on the current situation at Cyanogen Inc? Let us know in the comments.

Nougat is coming to the Nexus 4 courtesy of CyanogenMod 14

You’ve got to give credit to the loyal CyanogenMod ROM team, not only are they still hard at work despite the garbage fire Cyanogen Inc has become, they’re still so committed they are about to breathe new life into the ageing Nexus 4 courtesy of CyanogenMod 14 nightlies based on Android 7.1 Nougat.

But it’s not just the Nexus 4 getting CM 14.1 love right now, with six other devices getting official nightly support already. The Chinese clone of the Nexus 5 (CAF), T-Mobile LG G3, LG G Pad 8.3, Asus ZenPad 8.0, Sony Xperia M and Samsung Galaxy S5 (AU) already have nightlies available, and there’s an experimental build for the Nexus 4 if you want to go even more bleeding edge than nightlies.

Nightly builds are pushed out each and every day and contain all the latest code the CM ROM developers have worked on during the day. Things might be glitchy, broken or unstable, but that’s the price you pay for the latest and greatest. If that doesn’t sound like fun to you, you’re better off waiting for a stable or release candidate build instead.

Do you still have a Nexus 4? How many older devices do you have running custom ROMs?