OnePlus handsets in India will get Cyanogen updates after companies resolve legal dispute
Micromax & OnePlus resolve legal dispute; OnePlus handsets will get Cyanogen updates — OnePlus said that all legal proceedings have been resolved and both the cases have been withdrawn through mutual consent.
Context & Ripple Effects
The dispute traces to December 2014, when Micromax's complaint over its claimed Cyanogen exclusivity in India halted OnePlus sales days after launch, before the Delhi High Court lifted the ban. Caught in the crossfire, OnePlus started building its own software — shipping an alpha Lollipop build without Cyanogen in early January.
Two developments then converged: Cyanogen publicly ended the OnePlus partnership in late April to chase bigger Chinese vendors, and now both companies have withdrawn their legal cases by mutual consent — clearing the way for Cyanogen updates on OnePlus handsets in India despite the formal split.
First-order effects
- OnePlus owners in India get Cyanogen OS updates restored, removing the update freeze that followed the sales halt.
- Micromax exits the fight with its exclusivity claim untested in court, since both cases were withdrawn rather than adjudicated.
Second-order effects
- Cyanogen is freed to execute its stated pivot toward larger Chinese vendors, no longer entangled in Indian litigation over a partner it had already dropped.
- OnePlus keeps two parallel software tracks in India — its own non-Cyanogen builds alongside resumed Cyanogen updates — reducing dependence on any single OS supplier.
Third-order effects
- If exclusive-software claims remain enforceable enough to trigger sales bans but settle quietly before trial, they function less as durable moats than as entry tolls for new vendors in India.
- Vendors burned by licensing disputes are pushed toward owning their software stack, eroding third-party OS partnerships as a differentiation strategy.
The trend: Android handset makers in India are learning that licensed-software exclusivity can be contested legally but not relied upon commercially, accelerating the shift toward in-house software ownership.