Translate

Thursday, January 15, 2015

Steve Kondik on India, Micromax, and OnePlus






Cyanogen's Founder clears the air


If you've been following the misadventures of OnePlus and Micromax over in India, you know that there's been a bit of a disagreement over who gets to use Cyanogen OS (as opposed to the totally open-source CyanogenMod) due to an exclusivity agreement that was created alongside the launch of the Micromax Yu brand. It's been a pretty big mess that has resulted in some unfortunately vague language regarding software support for the OnePlus One in India, and even got the OnePlus One banned from being sold in the country for a bit. While Micromax and OnePlus have clearly drawn their battle lines and are prepared to let the Indian courts settle things, the folks over at Cyanogen, Inc. have been deafeningly silent on the entire matter. Until now. In India yesterday, a statement has been provided to the courts from Cyanogen Inc. that better explains the company's position as the creator of the software for both devices.


Since this whole mess started, there's been general unrest regarding what this will mean for devices running Cyanogen OS in the future. The court documents and public statements from both OnePlus and Micromax have painted a grim picture regarding the deals being struck with Cyanogen. We've seen what looks like an agreement terminated with all the respect of a text message break up, references to a great deal of money being involved in securing exclusivity, and then there's the strange way the company addressed whether or not they would be continuing to update the OnePlus One.


Out of context, none of this looks good on a open source software company whose mission statement has been to get as much Cyanogen out there as possible. Fortunately, for those who care, the company has decided to talk with Android Central about what has been happening behind closed doors.























from Android Central - Android Forums - News - Reviews - Help and Android Wallpapers http://ift.tt/1ygM1dc

via IFTTT

No comments:

Post a Comment