CyanogenMod is Dead. Ok… so… NOW what?!
This is a real head shaker; AND a huge mess. As with so many small companies and/ or startups, what was once meant to concur the world, has ended in a flaming mess. It’s a common enough story, but one that bears a bit of telling, in that many – including myself – will find interesting.
It was announced a couple of days ago that CyanogenMod would shut down. By shutting down it’s not that the OS is going go back into a state of community driven development (at least not exactly), no. The entire company that came out of CyanogenMod is shutting its doors, its development, its services, etc.
The company is gone. Unfortunately, surprises like this often happen with internet properties. Unfortunately, you just never really know what’s going to happen. Sometimes, change comes suddenly and can be very jarring.
In 2015, the CEO of Cyanogen, Kit McMaster said they were going to kill Google. Two years later, they’re shutting everything down. It’s a common enough tale. Apparently, the company has burned through over $100M in venture capital and has burned down a number of bridges. The one real win the company got – their partnership with One Plus One, failed horribly.
In July of 2016, the company’s CTO and cofounder, Steve Kondik claimed that the company wasn’t going anywhere (meaning they were staying the course) and they haven’t put aside their intent to bring CyanogenMod to the world.
As often happens with organizations like this, the company lacked a single, centralized vision. There were serious conflicts between founders and senior management some of them got so “violent” between Kondik and McMaster (the CTO and the CEO, respectively) that McMaster swore to burn Cyanogen to the ground.
Which is exactly what happened.
Kondik’s power was reduced by October 2016 and Cyanogen announced it was switching from an Android fork – its original strategy – to an open sourced, modular OS. This would enable interested hardware manufacturers to put some, part or all of Cyanogen into stock or a home brew version of Android.
CyanogenMod, however, is dead. The company will shut down its nightly builds, its services as well as every other part of its OS on 2016-12-31. The dream, if you will, the brand, is dead. McMaster may have “won,” but Kondik is going to have the last laugh.
The OS will be forked. According to Kondik, as stated on the CyanogenMod Google+ list, the list’s moderators indicated that the OS would indeed be forked and continued,
“However, CM has always been more than the name and more than the infrastructure. CM has been a success based on the spirit, ingenuity and effort of its individual contributors – back when it was Kondik in his home, to the now thousands of contributors past and present.
Embracing that spirit, we the community of developers, designers, device maintainers and translators have taken the steps necessary to produce a fork of the CM source code and pending patches. This is more than just a ‘rebrand’. This fork will return to the grassroots community effort that used to define CM while maintaining the professional quality and reliability you have come to expect more recently.”
The reincarnation of CyanogenMod is going to be called LineageOS, and its believed that Kondik is leading the effort. The project, however, is still getting off the ground. Time will tell if the effort will be successful; and its likely to remain in this “stealth mode” for a while.
LineageOS is going to be built on parts of CyanogenMod 13 and 14. However, it’s not known when it may actually hit the streets. It’s also believed that Kondik is heading up the new effort. While they can’t actually assume any Cyanogen IP or intellectual property, they can build upon the idea of an Android OS that’s small, fast, easy to use. That’s the hope for LineageOS, if and when it is released.
Unfortunately, not much more is known. However, the LineageOS site – if you really want to call it that – promises more information will be released on Tuesday 2016-12-27. If you click on the Status link, you will see that some work, is indeed taking place.
LineageOS plans on putting in the following infrastructure:
- Jenkins for builds
- A Portal for downloads
- A set of download mirrors
- Gerrit Code Review for development
- Jira for defects and requirements management
- A statistics page
- A wiki for knowledge management
Jenkins is already up to some extent, but is listed with a partial outage. Gerrit Code Review is up, but is listed with performance issues. Everything else is currently down. The incident log indicates that LineageOS will be monitoring Gerrit over the next few days.
No other information is currently available.
It’s clear that everything is still in its infancy at LineageOS. It’s going to take a bit to get things going, so if you’re interested in seeing this on your Android device, you’re going to need to wait a bit. You’re also likely going to need to pre-root your Android device. You’re likely going to need to do a bit of work prior to LineageOS and its first public build are released.
How the OS will be structured and what features it will have, have yet to be revealed. However, if everything happens the way I think and hope that it will, Android users will be in for a treat. LineageOS is likely to pick up where the original CyanogenMod left off before it became a “big deal” and got ahead of itself.
Are you an Android user? Have you rooted your device and do you use a custom ROM? Did CyanogenMod interest you? Have you tried it before? Is LineageOS something that you’re interested in? Will you install it on your device – given that its supported – once its released? Why don’t you meet me in the discussion area below and give me your take on Cyanogen’s situation as well as what’s become of it and on LineageOS and its direction. I’d love to hear from you…