Cyanogen clears up 'misinformation' about the future of its operating system

Cyanogen clears up 'misinformation' about the future of its operating system
Over the past week, there have been multiple reports about the future of Cyanogen Inc., the company behind the popular CyanogenMod Android fork. None were good.

Today, founder Steve Kondik addressed the "misinformation" and seems to suggest that Cyanogen is doing just fine:



I wanted to quickly address the circus of misinformation which has sprung up recently, particularly for everyone who uses CM or has been involved with the project.

tl;dr: CyanogenMod isn't going anywhere, nor has Cyanogen Inc. discontinued it's efforts towards the goal of bringing it to a larger audience.

It's been seven years since I released the first version of CM, and so much has happened. The speed of the mobile space is only accelerating. I co-founded the company three years ago, knowing fully the kind of response it might invoke- an epic mix of love and hate. We had a few successes at the Inc, but also our share of stuff which just didn't work at all. Anyone insane enough to do a startup will tell you that it will probably go wrong before it goes right, no matter how good your intentions are. All you can do is fix it, or it's the end. You find out what works and what doesn't work, and go towards the things which work.

CyanogenMod is something that works. Perhaps it doesn't need to "go big" to work. I'm still wildly inspired by the idea of a platform which forces participation. Whether it's the choice to hack your phone to bits and figure out how to install the damn thing to begin with, learning what's possible afterwards, or just having the confidence of being in control, it still serves an important role which hasn't been filled outside of the custom ROM community. Cyanogen Inc (including myself) will still be sponsoring the project and will continue to have an active role in it's development. Contrary to popular belief, we are not "pivoting to apps" nor are we shelving CM :) We'll have additional information on the Inc site soon.

Thanks for sticking with us and for all the awesomeness and support over the years.


Written by: Andre Yoskowitz @ 26 Jul 2016 21:16
Tags
Cyanogen
Advertisement - News comments available below the ad
  • 4 comments
  • Jemborg

    I use it

    Its a lot easier being righteous than right.


    DSE VZ300-
    Zilog Z80 CPU, 32KB RAM (16K+16K cartridge), video processor 6847, 2KB video RAM, 16 colours (text mode), 5.25" FDD

    27.7.2016 05:16 #1

  • Bozobub

    Same. The super-fine-grained privacy controls are a HUGE deal.

    1.8.2016 04:27 #2

  • KillerBug

    I would use it except it is STILL broken on the US Cellular version of the 2015 G3...kills all mobile services...text, talk, and data.

    3.8.2016 12:20 #3

  • Bozobub

    Sounds strongly like an APN issue. I had the same problem, using CM on a CDMA Galaxy S3, when using Ting (a Sprint MVNO), and fixed it with an APN change.

    If you're willing to mess with a bit, simply go to your (currently working) phone's "data" menu via the dialer (dial ##3282#; some phones make you press the "call" button afterward), go to the APN menu, and copy ALL the APN info (or simply google it). Then root (if you haven't already), make a full NANDroid backup so you can un-bork it easily if there's an issue, and install CM. You can then make a manual APN setting with the very same data within CM's settings.

    If you're not running stock but still have a non-AOSP ROM, the EPST dialer code (##3282#) should still work fine. AOSP ROMs usually break EPST, sadly; if you are using an AOSP ROM already or your current ROM doesn't suport EPST codes for some other reason, "True Phone Dialer" should allow proper EPST code entry.

    You can also do this with a simple .zip file install via recovery — that's how the fix for my S3 was handled — but that's beyond my ken ^^' .

    Feel free to get back to me here or via PM, if you'd like more detailed/additional assistance.

    Edit -> Rot, that app will NOT suffice any more (at least on my LG G2). Ah well; you should be able to read your APN data from your phone's settings, but if not, looks like a search for the proper ones is the only way to go.

    9.8.2016 22:40 #4

© 2024 AfterDawn Oy

Hosted by
Powered by UpCloud