In July, Koush announced that CyanogenMod would be seeing integrated, system-wide secure messaging integration with compatibility with TextSecure. For those unfamiliar, TextSecure is an open-source cross-platform (iOS and Android) client that encrypts your SMS messages both locally, and over the air when sending to other TextSecure users. The application is maintained by Open WhisperSystems, and lead engineer Moxie Marlinspike.
Moxie is a veteran of open source software, cryptography and good encryption practices, and a privacy advocate. To learn more about him and his accomplishments check out his personal site and Wikipedia page. He’s also spent time as a speaker at DEFCON on multiple occasions.
Moxie has been the lead engineer on the CyanogenMod implementation of TextSecure, making sure the CM version is both secure and compatible with his existing services. Unique to the CM implementation is our SMS middleware functionality. This is …
As promised in our CM 11 M1 – Nexus release, we’ve enabled nightlies for devices stated as ready for CM11 by their maintainers. This list will continue to grow, but this post serves as a snapshot of the current nightly status for all devices, across all active CM branches.
First things first, as this is what most of you will be itching for in terms of ‘bleeding edge’, Ricardo (arcee) has done the necessary voodoo to get Android 4.4.1 rebased and merged into our code stream. That code should be pushed up later this evening (PST) and available for the next round of nightlies. Once merged, our device maintainers will perform any necessary adjustments to make their devices work with the refreshed code.
We’ll update this post in the event we decide to delay this, but at this point it looks all systems normal.
No, that’s not a typo – you read that correctly. Today we release CM 11.0 M1 for all actively AOSP-supported Nexus devices – all variants of the Nexus 7, the Nexus 4, Nexus 5 and Nexus 10.
Some background on this change of order. Normally, this would be the point in time where we turn on CM 11 nightlies. From there, we would spend the next few weeks (or longer) in the nightlies, all the while not allowing you guys (the users) to offer support in the form of bug reports. Taking reports against the constantly changing nightly codebase is too resource intensive, but at the same time, waiting another month to get them going is, in all honesty, wasted time. So, with this change, we are going for the best of both.
The AOSP-supported Nexus devices should have minimal to no device specific issues (as their hardware code comes mostly from Google). We’ve …
With the release of CM 10.2.0 we end our foray into Android 4.3-land and planned releases based on that code. We will of course continue to provide hot-fixes, security patches and similar as needed. The device roster for this initial run includes all devices that received an RC1.
Echoing the RC1 post, make sure you update your third party addon zips. As a cursory note, for those of you coming from 10.1 or earlier, if you notice your Phone app reports as ‘not installed’: simply remove the shortcut and re-add it from your application drawer.
As we’ve done with similar ‘end of branch’ releases, this marks the point where the team will shift focus solely to CM 11 and Android 4.4 (KitKat) code. CM 10.2 nightlies will continue and as we ramp up CM 11 nightlies, device maintainers will signal which devices are ready to make that jump as well. Whether you prefer stable, almost stable …
Today, we were contacted by the Google Play Support team to say that our CyanogenMod Installer application is in violation of Google Play’s developer terms.
They advised us to voluntarily remove the application, or they would be forced to remove it administratively. We have complied with their wishes while we wait for a more favorable resolution.
To those unfamiliar with the application, it has a single function – to guide users to enable “ADB”, a built in development and debugging tool, and then navigates the user to the desktop installer. The desktop application then performs the installation of the CyanogenMod on their Android device.
After reaching out to the Play team, their feedback was that though application itself is harmless, since it ‘encourages users to void their warranty’, it would not be allowed to remain in the store.
We’ve seen hundreds of thousands of installations of the application, proving the …
It’s that time again! The bug reports on the 10.2 M1 have been greatly helpful, so a well earned ‘Thank You!’ to all of you that made your way over to our JIRA BugTracker and submitted your issues, ideas and logs!
The entire team has been plugging away at both 10.2 and 11.0 code branches – porting fixes and features back and forth to try and bring you the best CM 10.2 experience! Since the M1 we’ve also added a handful of new maintainers and devices to our merry roster.
Today we ship the initial wave of 10.2 RC1 builds. For those new to our build sequencing, these builds are release candidates. These allow for some final polish and fixes to take place before we release 10.2 for general usage.
To get ahead of the normal round of questions:
You can safely flash this on top of CM 10.2 M1 (or earlier 10.2 nightly) …