CM9 Nightly Builds Are Alive!

May 4th, 2012

Our Jenkins instance is now creating CM9 nightly builds for a number of targets including the Nexus line, various Samsung devices, Asus Transformer, Galaxy Tab, and others. We’ll be bringing more targets online as they are ready.

CM7 nightlies are not currently being built due to the slow rate of patches going into this tree, but we plan to enable weekly builds for these targets.

If you find these builds useful, please consider dropping us a couple of bucks by donating. It does cost money to keep these systems online.

You can find all nightly builds at Get.CM.

New Build Servers Online!

April 18th, 2012

We put out a call for help back in February asking for support from the community to help us get our nightly builds back up to speed. The community answered our call in force! With the contributions, we were able to acquire three Dell R610 servers. Each server has dual Xeon X5675 CPUs (12 cores total) and 32 GB of RAM. These are some serious machines! We also purchased a few new devices for our team members with what was left. Your donations have helped us to grow immensely.

The servers have been installed and are now starting builds. These machines can build CM9 in about 9 minutes, pretty serious stuff. We still need to set up a scheduler to automate the process of building every target- I expect this to be done in the next few days. We’ll make another announcement when nightly builds are being made for all targets on a predictable basis.

Build Server Update

March 13th, 2012

Thanks to all of the contributions we recently recieved from the community, we were about to purchase three new Dell servers for taking care of nightly builds for all devices! The new boxes are pretty monsterous, 12-core Xeon machines with 32GB of RAM. Perfect for building lots of copies of CyanogenMod 9 (and 7!), with some power to spare.

I just got notification that the hardware shipped today and should arrive this week. Once they are configured, they will be sent to the TDRevolution colocation space and hooked up to our new Jenkins build system. After that, we will be back at full capacity. It should just be a few more weeks.

Again, thank you for all of the support as we go through some growing pains.

We’ve Reached Our Goal!

February 18th, 2012

I am absolutely amazed at the support we have just been shown. We’ve reached our goal, and maybe a bit more. We will be ordering the servers next week (Xeon-class boxes with lots of RAM), and should have the builds going again soon!

Thank you again for the support!

CyanogenMod Needs Your Help!

February 18th, 2012

As you may know, our nightly builds have recently been sporadic at best. The reason behind this is that previously, we had access to a large compute cluster to perform these builds. This was really great, and gave us all the power we needed to pump out 50+ builds a day. Unfortunately, we no longer have access to this cluster, and have not for quite some time. With CM9 coming up, and CM7.2 ready to go out the door, we are now in quite a bit of a mess. One of the most awesome things about CM in my opinion was the ability to get a fresh build, every day, with the latest and greatest features. And the stats don’t lie either- the community thinks so too.

With that said, we need to purchase new hardware to take on this task. A couple of solid, stable Xeon-class servers with large amounts of RAM and fast disks. Virtual private servers won’t cut it for build machines.

CyanogenMod is not a for-profit business. We are just a bunch of geeks, trying to make our phones more awesome. The donations we get currently cover our operating costs and occasionally go towards developer devices. This time, I need to ask for help from the community for something a bit larger. We need to purchase these servers in order to bring the build infrastructure back to full capacity.

An option I have considered is to charge for access to nightly builds. This seems like a really bad idea, potentially detrimental to the community, and likely to just increase the proliferation of unofficial builds in various states of brokenness. So, I am putting out a call to the community for help. Whatever you can spare will go directly to the server fund, and if successful, we will work to get back to full capacity as quickly as possible.

If you’d like to contribute, please use the PayPal donation link at the bottom of the page (you *must* use this link, rather than going through the links on the forum to contribute to this fund). Let’s show some community power!

Progress on CM9

February 7th, 2012

It’s been awhile since the last update and I just wanted to let everyone know about our progress with CM9. As I mentioned in the previous update, Android 4.0 contains many internal changes that require updated graphics drivers. Unfortunately, these drivers are almost always closed-source and don’t appear until a device or devkit is released with them. For many devices, our hands are tied. Some very clever workarounds have gone into CM9, but we’re still blocked on some subsystems like the camera.

Since Android 4.0 is such a major change from 2.3, we started with a fresh codebase from Google and have been forward-porting features from CM7 with an eye on design and better integration. This is a somewhat time-consuming process, but it allows us to rethink everything. We’ve eliminated the CMParts app, instead choosing to add our custom features directly into the main settings. We are also taking a “just works” approach when it comes to configuration- CM7 had too many options that just weren’t widely used. We hope to achieve a good balance between tweakability and a great out-of-the-box experience. I want your phone or tablet to feel like it should have come with CM9.

Currently, you can compile CM9 for a small number of devices- notably the Samsung Galaxy Nexus and Nexus S, the Samsung Galaxy Tab 10.1 (Wi-Fi and T-Mobile versions), the HP Touchpad and Motorola Xoom. The next devices to show up will likely be a whole array of Samsung phones (Exynos chipset), with devices based on the Qualcomm MSM8660 and 7×30 chipsets to follow. It’s still unclear if we can provide support for the QSD8x50 family of devices (Nexus One, HTC Evo, etc), but the answer almost always turns out to be “yes” for these kinds of things.

As our hardware support improves, I’ll keep this blog updated. As much as we’d like to stay ahead of the manufacturers, it may be a tie this time :) Thanks for the continued support, and please consider dropping us a buck or two using the link at the bottom of the page if you enjoy CyanogenMod.