But this probably means no more OTA updates for current OnePlus's
Is there a way to "upgrade" to oxygenOS? Or even re-install with oxygenOS?
Given this news will probably try this.
This blocked the sale of OnePlus One phone in India until this could get resolved. OxygenOS was the answer to this. Fork of Cyanogenmod with some rebranding and a few added things.
Personally I bought the OnePlus One because it came with Cyanogen. I wasn't happy with all the added cruft in CyanogenOS, so I reflashed to Cyanogenmod soon after a stable version was available.
I'm currently using OxygenOS on my OnePlus 3, but will flash to Cyanogenmod eventually to run more bleeding edge and get some features back that I miss.
This shouldn't effect OnePlus 3 as they terminated thier agreement with Cyanogen Inc after the India licencing problem.
It's boggling there has been no official word from Cyanogen Inc on why this happened. I never liked the OnePlus marketing or press, plus I had a OnePlus One with that terrible grounding/touchscreen crazy issue.
Just judging from OnePlus's support, I have a feeling Cyanogen was getting sick of them too. I'm sure there's much more to their fallout than what's been made available. Considering my experience with OnePlus's product, I'd probably side more with Cyanogen.
There was a lot of controversy in the open source community about Cyanogen's partnership with Microsoft. It seemed like good idea when you think of Microsoft pushing more Android products and their internal divisions trying to break away from their own failing phone market. But I guess that effort failed as well. Did they ever release any phones with CyanogenOS + Cortana?
that isn't exclusive to OP, though, of course - every other vendor I can imagine does the exact same to any non-hardware customizations they apply to the OS.
I used to switch phones pretty regularly and since getting my OnePlus 2, the only phone I'd upgrade to would be the 3 or the new 3T.
The one thing I absolutely loved was not having all of the bloat of the carrier apps on the phone when you get it. Totally stripped down and fully customizable.
OnePlus has had some build quality issues when they were first setting up their supply line, but lately I've had very good luck with their devices. Great specs for cheap, like the Nexus line used to represent.
http://en.miui.com has some nice UX
http://paranoidandroid.co is nice if you want security
http://aokp.co has been around for years and stays cutting edge
CopperheadOS is what you want if you're concerned about security.
While I am happy Copperhead OS is around, it only supports a very limited set of Nexus devices. Back in the pre-Signal days Open Whisper Systems started their own work on an Android fork called WhisperCore. I'm curious if any of the features from WhisperCore ever made it into a new ROM, or if it was all quietly abandoned.
The former, FDE key separation, feature is gone and you'll need to either use adb or a 3rd party application  to achieve it.
It shouldn't be too hard to pull kernel patches from CopperheadOS and apply it to a clean AOSP tree for different devices -- this is obviously after they have done all the heavy lifting.
Steve Kondik wrote:
It costs a lot of money to keep the servers running at this scale, and I figure we have about two months to GTFO.
There is some speculation that Lineage Android Distribution might be the new name. LineageOS on github also uses that name and mirrors CM repositories.
I'm planning to get a new phone sometime in the next 6 months, but I don't plan to check for Cyanogenmod compatibility this time. I have no idea what's going on with that company these days. The future of Cyanogenmod seems to be getting more uncertain and less open every time I hear an announcement like this.
We have no need for the Year of Linux on the Desktop anymore, because Linux on the Phone already commands a very large market share. Unfortunately, every year the Android ecosystem feels less like the Linux I know and love, and more like just another proprietary platform. I hope I'm wrong. I hope Cyanogenmod and other Android forks thrive. But in the meantime, I'll have to use a non-Cyanogenmod phone.
"Yesterday, Cyanogen Inc (Cyngn) announced that they were shutting down the infrastructure behind CyanogenMod (CM)."
A close reading of the original blog post (which mentions "Cyanogen-supported nightly builds" being stopped and provides a workaround to "anyone who wants to build CyanogenMod personally") clearly suggests that the post is primarily about the CyanogenMod build servers, and not about CyanogenOS.
All of this is so sad. At least for me.
I've used Steve Kondik's CyanogenMod on my ADP1 and have used CM until I got a Nexus 5. It was just so much better than anything the OEMs could produce at that time and had great customization features. Only Android 6.0 has stopped my yearning for CM. I think it had a profound impact on Android or at least it's technically oriented community. Even MIUI started as a CyanogenMod Mod, afaik, before Xiaomi even produced Android smartphones.
I couldn't understand the rage in the community when Steve wanted to create a business around CM and to this day think that their business model has only benefited CM. pfSense and nginx seem to do just fine with a similar approach.
Did Cyngn (Cyanogen Inc.) fuck up? Did Steve make mistakes along the way? Were his business partners toxic to the company and CM? - Probably yes and no to some degree to all of these questions but hey, it was mostly great I think.
Sad to see the company go and sad to see CM probably die slowly. At least in the form it exists in today. Hope dies last so I hope that CM will somehow survive...
It doesn't say very much, does this mean that CyanogenMod will no longer be available? Or just the nightly build service will stop, therefore actual releases will still be available?
The domain is registered, github organisation created and currently tracking with CM's repos, and the channels are registered on freenode.
Android is a beast to build by hand.
Was posted in hn
The question now is how this will affect the open source version. I understand they have become quite reliant on infrastructure from the commercial company. I also think the founder sold all the trademarks and so on, but should they have to change their name it can only be for the better. A poisonous gas might be a cool name for a certain demographic, but it's not likely to mainstream very well.
1. aka Steve Kondik: the original founder of the open source project which preceeded Cyanogen Inc, of which he was a co-founder before he bailed.
But I guess this gives more space for the new OSs like Sailfish, nextbit Etc.
Also in IMHO, AOSP was useful majorly because of CM. Even though this decision might not close CM. It's affect on the self hacking Android community would be interesting
What does OnePlus have to do with this? I'll admit I'm not down in the trenches on ROMs, etc. but my understanding from what I've read over time is that it runs like this:
CyanogenMod is a popular and widely used ROM
Core developers of CyanogenMod and possibly some business folks decide to turn it into a company and provide said ROM (with customer-desired tweaks) to small hardware vendors who don't want to do their own in-house development
Two of the client companies are OnePlus and someone in India, but contract screwups mean that because of this OnePlus can't sell their phones in India. Displeased with losing a huge market for inexpensive phones, they drop Cyanogen and go their own way for future products.
Further drama and possibly not enough sales ensue
Internal drama at Cyanogen leads to the founder of CyanogenMod leaving
Cyanogen the company shuts down.
I'm sure there's a ton of nuance, hurt feelings, betrayal, etc. involved (aka "drama"), but blaming OnePlus for Cyanogen shutting down makes no more sense than blaming Cyanogen for OnePlus shutting down if they'd gone under due to the whole "can't sell in India" thing.
They have nothing to do with this. I was merely stating that out of the 2 biggest AOSP forks, OnePlus bought the entire PA team to make OxygenOS
CyanogenMod was the official ROM of OnePlus One till they signed a side deal which brought about OxygenOS.
They have done nothing here directly. But the AOSP project could sure do with some diversity which this move just might bring in.
As for a full buyout, I didn't see anything indicating that.