> At its core, CyanogenMod is a best in class example of Open Source development.

Really? Why is it that they can't even bring themselves to fix trivial bugs like [1] let alone bigger deal-breaker bugs like [2]? I find the OnePlus One borderline unusable with all the Cyanogenmod bugs it has...

[1] https://jira.cyanogenmod.org/browse/BACON-2855

[2] https://jira.cyanogenmod.org/browse/BACON-736

Might be worth adding another note to one of those bugs in a few days when it's a year old.

That bug in particular is an enormous pain. I thankfully don't have to reboot - I can either physically shake it a few times (this feature is disabled and should do nothing) or press the power button a few dozen times to get the screen to turn on.

Yeah it's a pain alright. I I have a suspicion it's caused by an update, because I didn't use to get it until a few months ago. Do you have the same experience? Also, I never managed to get the power button to make it work. If it doesn't work I just have to reboot.

I'm not even sure they would fix it at this point. They'd probably tell me to upgrade to CM12, which I would definitely not want to do considering how much more buggy it seems to be.

From personal experience, 12.x on 4 completely different devices has proven to be far more stable, fast, and more efficient than 11.x was.

Of course these devices are Nexus 4,5,9 as well as OPO, so might be better supported.

> From personal experience, 12.x on 4 completely different devices has proven to be far more stable, fast, and more efficient than 11.x was.

Oh really now? Consider yourself lucky.

"People on the OnePlus One forums have already created 300 pages in the CM12S bugs thread, comprised of more complaints than solutions. Which is why this time, people experiencing CyanogenMod 12S bugs on their OnePlus One might be better off either not installing the update, reverting to the KitKat version of finding a different custom ROM to use." [1]

[1] http://www.geeksnack.com/2015/05/09/oneplus-one-cm12s-bugs-a...

Might be because I keep a very minimal install, such as no google apps + only apps I want and need. That said, the OPO is my daily phone these days, especially since I get a little more than 2 days of charge out of it.

Also, using nightly images, not the vendor supplied ones.

Not sure how much of a difference that is, but it works for me. :-)

Not my experience. My audio would skip, my screen would report its size oddly in odd cases, if you took it into an international setting it would just crash (thats when I moved to Oxygen), and I had so many more issues I can't even remember. I don't fully blame Cyanogen as part of the blame is on OnePlus, but I have found their software to be very un-stable. The phone was an amazing deal tho and I really like how they specced it out. I am not so stoked on how the One plus two is specced tho. I want NFC at the very least. I see it as just a nerdy hobbyist sorta thing.

Also I would like to say I find Cyanogen to be kinda snobby as most of their press is them whining about Android (the source code they built their OS on) not being truly open source. I find it be pretty ironic, as it must clearly be open source since, many people have taken it and made their own businesses based on it and its runtime is in so many different products...(Ie Amazon, Cyanogen, Various Chinese phone companies) Its odd the closed source parts are mostly the libraries used to communicate with Google's Cloud or using the play store, which would need to be replaced anyways.

Yea I totally agree. One Plus Cyanogenmod was sooo buggy. Oxygen OS was worlds better, but still pretty buggy.

>At its core, CyanogenMod is a best in class example of Open Source development.

Oh really?

"Rumors of plans to commercialize CyanogenMod as well as the subsequent announcement of Cyanogen Inc. has led to a certain level of discord within the CyanogenMod community. Several CyanogenMod developers have raised concerns that developers who had provided their work in the past were not being appropriately acknowledged or compensated for their gratis work on what was now a commercial project, further that the original ethos of the community project was being undermined and that these concerns were not being adequately addressed by Cyanogen Inc. Examples include "The "Focal" camera app developer Guillaume Lesniak ("'xplodwild') whose app was withdrawn from CyanogenMod allegedly following demands by the new company to adopt closed-source modifications and licensing."

hahah I thought of this exact thing, when I skimmed it. Cyanogen has turned into such a pompous circle jerk...

If you are a top tier handset integration provider for Android, there are soooo many things you can commercialize without fucking up the community-facing open source model. Hardware support. Advanced RCS and all-IP network support. FMI. Etc. It feels as if Cyanogen is taking a app developer's approach to value add when they should acquire some telecom knowledge because that's where their customers' pain points are likely to be.

This looks like a clean solution to the age old problem: how to support cm-features in a clean way, without working directly against the implementation.

Glad to see stuff like this coming.

Does it still phone home and give information to Google?

Not if you don't install Google Apps. You can even use an alternate wifi location service.

Even with the gapps installed, you could turn those features off if you want.

I liked CyanogenMod more when they were focused on supporting almost all devices and not on adding their own (usually buggy) code on top of AOSP...

CM have never focused on supporting almost all devices, its always been up to individual device maintainers to provide support for non-Nexus and CM core-dev-owned devices.

No proof in pudding. Proof is in the eating.

The original saying was "the proof of the pudding is in the eating." But like most adages it has been shortened over time to the now less-correct formulation.