CyanogenMod

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 ... [More] all active CM branches. Android 4.4.1 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. Buildbot maintenence Just before the 10.2.0 release we ...Read the Rest... [Less]

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 ... [More] 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 ...Read the Rest... [Less]

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 ... [More] 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 ...Read the Rest... [Less]

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 ... [More] 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 ...Read the Rest... [Less]

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 ... [More] 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) ...Read the Rest... [Less]

Today we are exiting the ‘beta’ status phase and providing the CyanogenMod Installer for general release. The Play store application is now available, and the PC client component will be available shortly is now available. A special “Thank You” to ... [More] all of the beta testers, which at current count, is a community with over 7000 members. The reception and demand we’ve received for the installer shows the value in breaking down the barrier to entry that we sought to address. We will continue to work on supporting additional devices beyond the initial set, but we are proud to say that we are supporting the majority of flagship models currently on the market. For a list of currently supported models, please see our Installer wiki page. After this release, we will also refresh the layout and design of our Download Portal, making it easier to find the builds for your devices. By visiting Read the Rest... [Less]

Week Ending: November 9, 2013 “This Week in CyanogenMod” is an ongoing feature that aims to serve as a one-stop shop for weekly updates. Topics discussed are culled from our social media accounts, gerrit, status updates and general thoughts. Just a ... [More] bit of CM 10.2 news, and then we’ll jump right into CM 11 discussions. CM 10.2 M1 Released In the midst of all the KitKat news, we released the first ‘M’ build for CM 10.2. This means that our JIRA Bug tracker is now open to take reports against 10.2 code. If you flashed the M1 release and experienced some issues, please do let us know (and provide a log). Our plan is to incorporate the fixes for and bugs you bring to our attention via JIRA and add in the backlog of outstanding patches that were not ready for the M1 release – including the new AppOps ‘always ask’ functionality. From ...Read the Rest... [Less]

With all the Android 4.4 hype, we haven’t forgotten about CM 10.2. Tonight the buildbots will focus their efforts on building and shipping out CyanogenMod 10.2 M1. Builds are already hitting the servers (please be patient, this will take a while). We ... [More] are targeting over 70 devices for this initial M-release. As we mentioned yesterday, we will continue to work on the 10.2 code branch, in parallel to all of our Android 4.4 efforts. For those that will inevitably ask, we have not made any decisions with respect to what devices will make the leap to the KitKat code base and likely won’t have that information for a few weeks. In the meantime, enjoy some of the hard work our contributors have placed into bringing you Android 4.3 and look forward to additional functionality as we move towards M2 and the eventual ‘stable’ release. Happy Flashing, The CyanogenMod Team [Less]

Week Ending: October 26, 2013 “This Week in CyanogenMod” is an ongoing feature that aims to serve as a one-stop shop for weekly updates. Topics discussed are culled from our social media accounts, gerrit, status updates and general thoughts. DroidCon ... [More] UK Shane and I just wrapped up the DroidCon weekend and have to say we had a blast! The event offered a unique opportunity for us to communicate with users, device manufactures, network operators, and application developers all in one place, giving a great insight to the larger Android community outside of the custom OS space. We were treated great, welcomed with open arms (even if we didn’t fit into the traditional ‘app developer’ mold) and being asked to give the Keynote was an honor (we’ll link the video when it becomes available). Shout-out to the organizers and sponsors for the event – looking forward to next year! Intel SDP Intel’s representatives sat with ...Read the Rest... [Less]

Week Ending: October 19, 2013 “This Week in CyanogenMod” is an ongoing feature that aims to serve as a one-stop shop for weekly updates. Topics discussed are culled from our social media accounts, gerrit, status updates and general thoughts “I’m ... [More] late! I’m late!…No time to say ‘hello’, goodbye!” These past few weeks, I appear to be channeling my inner White Rabbit. Let’s recap last week’s activities shall we? Saying goodbye to some old friends With all the excitement surrounding the BBQ, one crucial piece of information got lost in the shuffle. Michael Scott (aka Hashcode) has succumb to the pressures of life and been forced to withdraw from supporting a handful of his Motorola OMAP devices, namely the Droid 3, Droid Bionic, Droid RAZR and Droid 4. He will continue to support the other devices he has, but given the time crunch he is feeling, it only makes sense that he focus on ...Read the Rest... [Less]