CyanogenMod has been due for a new issue tracker for a while now.
The existing Google Code tracker was started when we only supported 2 devices and Cyanogen was the only developer. Now we have about 150 devices and almost as many developers/maintainers, across 3 major versions of Android. There are almost 500 open issues on the tracker and nearing 7000 submitted in the last 3 years. The logcats and screenshots (and the occasional mp3 or video) attached to all the issues take over a gigabyte of space, and each increase in that quota has to be asked for manually. Google recently silently removed the RSS feed for all project updates, making issue tracking a bit harder for me.
The last two points there indicate the need for our own hosted solution. As several project members have worked with it before, JIRA was chosen. They provide a free licence for open-source projects (just like Google …
Many of you may not give it a second glance, but among all the furor and concern about permissions requested by market apps and privacy, all Custom ROMs (CyanogenMod included) ship with one major security risk — root!
We have been struggling with how to handle this for quite a bit, and took a first step with the first public CyanogenMod 9 alpha builds, by disabling the previously-default root access over USB. You can still get adb root access by running “adb root” in terminal, should you ever need it.
Every good open source software project grows. With that growth, it sometimes becomes difficult to communicate with people within that project. This is true for the CyanogenMod project as well. With our continued growth, change is coming as well. A major change is to make it easier for outside developers to communicate with the CyanogenMod project.
This is where I, and this blog post, come into play. Are you maintaining a device that is not currently maintained by the CM team? Do you wish for that device to be added to the list with your support? Have you found a vulnerability that you discovered that needs to be disclosed? Is there a problem with code used that needs attention? There is now a face for you to communicate with to get these things taken care of.
I’ve been in the background of the CyanogenMod project for just over two years now. With the knowledge I’ve …
I asked my friend Russell Holly to write a short blog post about how CM will never contain Carrier IQ. Enjoy.
Everybody with access to a web browser over the last week or so has undoubtedly seen the recent upheaval about Carrier IQ. The truth is, Carrier IQ has been around for quite some time. It is one of the nastier examples of bloatware installed by carriers, and it is more than likely something that will always be there in some form or fashion. That is, as long as your phone is running the OEM provided version of Android.
As this version of Android is based entirely on work from the Android Open Source Project, the CyanogenMod team would like to assure everyone that Carrier IQ has never, and will never be a part of our Operating System. There is no risk of this kind of software to ever be shipped as a …
The CM Touchpad team has decided that they feel an Alpha is in order. The following is what one of the members, dalingrin, sent me to post here on the main site. I hope you enjoy this build that countless hours have gone into. However, please realize this is not a final product nor does it indicate the performance of upcoming stable build.
The full source will be released when the 8×60 tree is merged in the upcoming weeks. In the mean time, enjoy this developer preview.
After many near-sleepless nights, we have an early sneak peak at the CyanogenMod 7.1 port for the HP TouchPad. This initial alpha release is, as they say, rough around the edges. There are still plenty of bugs and a few non-working features, but overall it should be in a state that you can at least play around with Android on your TouchPad.
I’ve been reading rumors that CyanogenMod’s core philosophy is changing, that we’ve been sold, or that we’ve given up and I want to go on record saying none of this is true at all. As you may know, there are only a handful of people that can approve changes for CM but a lot of developers for it. You may have noticed that we are operating at a slightly slower pace than normal, but that’s simply because we’ve been busy and real life responsibilities come before this project. No one is getting paid to work on the product.
You have most likely become aware that Cyanogen has been hired by Samsung, as that news is traveling through the Android community like wildfire. He is not leaving the project. Samsung is aware of his involvement in CM and there are no qualms from that end. He hasn’t been active recently because he is in the process …