CyanogenMod

» see cyanogenmod.org as it lived, on the wayback machine

~ the eulogy ~

CyanogenMod was on every spare android in the engineer-friend group around 2012. The way you got it onto a phone was a small ritual. Unlock the bootloader, install a custom recovery (TWRP or ClockworkMod), download the ROM zip and a Google Apps zip from xda-developers, drop them on the SD card, reboot into recovery, wipe, flash, flash again, reboot. If you did it wrong, you got a brick. If you did it right, you got a phone that was two Android versions newer than your carrier would ever ship.

The project was a community fork of the Android firmware that a developer named JesusFreke had been modifying. When he stopped in 2009, Stefanie Jane (then publicly known as Steve Kondik, handle "Cyanogen") took it over. The fork added what stock Android did not have at the time: full theme support, FLAC playback, advanced privacy guards, OpenVPN, equalizer settings, lock-screen customization. Every feature that eventually shipped in stock Android between 2010 and 2014 had a CyanogenMod equivalent that ran a year or two earlier.

By March 2015, CyanogenMod was running on something like 50 million phones, and that was just the devices that opted into the reporting telemetry. The actual install base was higher. The ROM officially supported over 150 device models, and unofficially supported anything someone with patience and a soldering iron could get a port to boot on. The XDA forums were the operating manual for the whole community.

~ the dossier ~

~ the origin ~

In 2013 the project got incorporated. Cyanogen Inc raised $7 million in a Benchmark-led seed round to monetize what had been a free community ROM. The pitch was that carriers and phone manufacturers wanted a clean Android alternative to Google's increasingly heavy services bundle, and that Cyanogen could provide it. For a while it worked. OnePlus shipped its first phone with CyanogenMod preinstalled in 2014. The hardware was great and the price was unbeatable.

~ the unraveling ~

Then Cyanogen Inc signed an exclusive distribution deal with Micromax for India, which kept OnePlus from selling its own phone in its largest target market. The relationship with OnePlus broke publicly and bitterly. CEO Kirt McMaster gave interviews about putting "a bullet through Google's head" that read as posturing rather than strategy. The company started laying off staff in July 2016. McMaster stepped down in October. Stefanie Jane left in November. The Cyanogen Inc infrastructure went dark on December 23, 2016.

~ what it became ~

The community had seen this coming. Within days of the shutdown announcement, the project was forked again. The new name was LineageOS. The codebase and the maintainers were almost identical to what had been there before. By January 2017, LineageOS nightly builds were available for the major CyanogenMod devices, and the migration was mostly painless. The ROM itself never really died. Just the company that had tried to own it.

~ the inheritance ~

The features CyanogenMod added are now standard. Stock Android has dark mode, granular permission controls, theme support, native VPN integration, plus a hundred other tweaks the community proved people wanted before Google added them. LineageOS is still maintained as of 2026 and supports current-generation devices. The custom-ROM scene is smaller than it was, mostly because the things you used to flash a ROM for have been merged upstream. CyanogenMod won by being absorbed.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »