All Cyanogen Services Are Shutting Down (cyngn.com)
Long-time Slashdot reader Nemosoft Unv. writes: A very brief post on
Cyanogen's blog says it all really: "As part of the ongoing consolidation of Cyanogen, all services and Cyanogen-supported nightly builds will be discontinued no later than 12/31/16. The open source project and source code will remain available for anyone who wants to build CyanogenMod personally." Of course, with no focused team behind the CyanogenMod project it's effectively dead. Building an Android OS from scratch is no mean feat and most users won't be able to pull this off, let alone make fixes and updates. So what will happen next?
Cyanogen had already laid off 20% of its workforce in July, and in November announced they had "separated ties" with Cyanogen founder and primary contributor Steve Kondik. One Android site quoted Kondik as saying "what I was trying to do, is over" in a private Google+ community, and the same day Kondik posted on Twitter, "Time for the next adventure." He hasn't posted since, so it's not clear what he's up to now. But the more important question is whether anyone will continue developing CyanogenMod.
UPDATE: Android Police reports that the CyanogenMod team "has posted an update of their own, confirming the shutdown of the CM infrastructure and outlining a plan to continue the open-source initiative as Lineage." The team posts on their blog that "we the community of developers, designers, device maintainers and translators have taken the steps necessary to produce a fork of the CM source code and pending patches."
UPDATE: Android Police reports that the CyanogenMod team "has posted an update of their own, confirming the shutdown of the CM infrastructure and outlining a plan to continue the open-source initiative as Lineage." The team posts on their blog that "we the community of developers, designers, device maintainers and translators have taken the steps necessary to produce a fork of the CM source code and pending patches."
One of my criteria for buying a phone was that it had CM available -- my latest being the OnePlus X. Every Android phone I've owned has run CM. This is very disappointing.
sig: sauer
I'm glad this information is finally coming to light. I was looking for a good place to have dinner.
Damn, I've been using CM nightlies on my phone for the last year. Now what am I supposed to do? I was actually going to spend my day redoing my phone with 14 so I could get Android 7.
What's a good alternative OS, given that I can not go back to stock? (No, really, there's a lock so I can't reflash the stock OS)
---
ECHELON is a government program to find words like bomb, jihad, plutonium, assassinate, and anarchy.
Remember LibreOffice? Someone will pick this up and keep developing it.
Corruption is convincing someone that the selfless ideal is the same as their selfish ideal.
So not 100% dead, just not using the CyanogenMod brand any more because it's become tainted.
Cyanogen Inc. the company is dead and bankrupt. Good riddance. This has of course repercussions for the community project cyanogenmod as well. Especially for the name "cyanogen" itself, which belongs to the company but also infrastructure like servers which were used by the community project.
But the people behind cyanogenmod, the ones doing the actual work for many phones, not the guys who wanted to simply sell that work, will continue:
A quote from a blog entry at https://www.cyanogenmod.org/bl...
"Embracing that spirit, we the community of developers, designers, device maintainers and translators have taken the steps necessary to produce a fork of the CM source code and pending patches. This is more than just a ‘rebrand’. This fork will return to the grassroots community effort that used to define CM while maintaining the professional quality and reliability you have come to expect more recently."
So the name cyanogen/cyanogenmod is dead, the project itself is hopefully not.
Once MS got involved, it was going to be game over, man.
I'm hoping Sailfish continues to evolve....
Obama is still the president for another month, so this is his fault. :-p
Ever notice how the FBI never goes after Google/Android/Samsung/etc. for access to their phones? Apple has a much smaller market share and the feds are all over them?
Because Android is like a screen door. The feds don't need to sue, they just walk in.
No, it is because Android doesn't do encryption by default - the "why" beats me. Enable it and it is as strong as any Apple offering.
New devices, since Android 6.0 Marshmallow, do encrypt by default. Custom ROMs often turn this off, CyanogenMod left it on.
Has that project actually gone anywhere?
You're a mean one....Mr. Grinch.....
Got Geometrodynamics? Awe, too hard to figure out? Too bad.
Now if only there was a Mobile Platform that has a longstanding history of providing Updates for reasonable periods of time...
Oh, wait...
Ever notice how the FBI never goes after Google/Android/Samsung/etc. for access to their phones? Apple has a much smaller market share and the feds are all over them?
Because Android is like a screen door. The feds don't need to sue, they just walk in.
No, it is because Android doesn't do encryption by default - the "why" beats me. Enable it and it is as strong as any Apple offering.
While I agree it would be significantly stronger than not having encryption enabled, how much stronger it is entirely dependent on the particular device's hardware.
And in any event, it is not likely to be "as strong as any Apple offering", sorry.
While I agree it would be significantly stronger than not having encryption enabled, how much stronger it is entirely dependent on the particular device's hardware.
Wrong. Android uses AES via dm-crypt, which is the same cipher used by iOS - the difference is that not all devices have hardware crypto support. IIRC this is one of the reasons Android doesn't enable it by default; it comes with a performance hit.
While I agree it would be significantly stronger than not having encryption enabled, how much stronger it is entirely dependent on the particular device's hardware.
Wrong. Android uses AES via dm-crypt, which is the same cipher used by iOS - the difference is that not all devices have hardware crypto support. IIRC this is one of the reasons Android doesn't enable it by default; it comes with a performance hit.
I was thinking about the Secure Enclave chip that Apple uses. How many Android devices have that sort of thing?
https://en.wikipedia.org/wiki/... . Any device using Android 6.0 onwards.
It's Christmas, so take that Christmas chill pill and relax. There will always be free ROMs as long as Google doesn't shut off AOSP completely. And unlike the article says, you don't need an Android system most people can build from scratch: what you do need is Android free as it is today, OEMs providing open drivers or at least driver packages that can be bundle with custom ROMs, and the dedicated developers on XDA that will have your back because they love what they do and they have the time. I know how selfish that sounds, but I have been spoiled and I know the official CM team has long done nothing different than what other non-CM based ROMs have.
wish I had points to mod the parent up. Not everything is an evil M$ plan.
wish I had points to mod the parent up. Not every evil is a M$ plan.
https://en.wikipedia.org/wiki/... . Any device using Android 6.0 onwards.
It sounds like that is half of the system that Apple has implemented. Apple's Axx SoC's have a TEE, but they also have the "Secure Enclave" (SE) CHIP. What is still missing in Android's implementation is the SEPERATE Secure Enclave chip.
I'm not a security expert, but from what I understand, the SE holds the key (literally) to decryption, and there is no direct or even indirect path to that key. That provides an important additional level of abstraction and security that no "on chip" solution can provide. And, according to those who ARE Security Experts, that is a significant advantage.
wish I had points to mod the parent up. Not everything is an evil M$ plan.
Yup, there is sometimes an evil M$ coincidence...
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
They're literally the same thing. Apple's "secure enclave" uses the ARM A7's TrustZone/SecurCore tech, which is basically an independent CPU in the same die. There's nothing magical about it - Android's been supporting it for eons now: https://source.android.com/sec...
They're literally the same thing. Apple's "secure enclave" uses the ARM A7's TrustZone/SecurCore tech, which is basically an independent CPU in the same die. There's nothing magical about it - Android's been supporting it for eons now: https://source.android.com/sec...
Sorry, still incorrect. Although Android is (gradually) getting better, slowly, it still is hit and miss, depending on which SoC your device OEM decides to use.
The only thing I was incorrect about is that I was under the impression that the SE was a separate component, rather than being implemented on-die in the Axx SoC. Other than that, my assertion that iOS' Security is more robust than Android's, stands.
Tomorrow may be different; but we're living in today...