CyanogenMod-6.0!
CyanogenMod-6.0 is hitting the mirrors right now! This is our first stable release based on Android 2.2, and we’ve hit our target list of devices. I’m completely amazed at what this project has become and the community that has developed around it, and it’s only just getting started.
You can get your CM-6 fix with ROM Manager, or head over to our forums and pick your device. You can also find all things CM-related on the relevant forums at XDA.
Thank you to everyone who’s contributed and everyone who’s supporting us!
CyanogenMod Games Clan
So, whilst we were talking in our IRC channel, a group of us were discussing about how a lot of us all love playing online games, on various platforms.
So, I came up with the idea of a CM Games Clan, that being -=CMC=-
It’s still early days at the moment, but the intention will be to have as many CyanogenMod users all forming a massive games clan, probably the biggest in the world? Who knows!
I’m currently working on a new section of the website that will be specifically for the clan. For now, I’ve also created an IRC channel dedicated to the clan, so discussion can take place there.
Moderators for each platform / game will also be required, come and join us on IRC @ Freenode #cmclan
Love or Hate? Feedback is appreciated.
*Edit: I’ve now created the Steam group : http://steamcommunity.com/groups/cyanogenmod
I’ll work on integrations and other coolness for the website shortly …… thanks for the feedback so far!
Gerrit Source Code Review
CyanogenMod has taken a huge step forward in terms of organization over the past few months. You may have noticed a recent move to a Github Organization, which makes administration of the source code repositories much easier.
Unfortunately, Github’s fork system doesn’t really work all that great when you have as many contributors sending code changes through as CyanogenMod does. Because of this, we have decided to implement our own Gerrit instance. Gerrit is developed by Google and used primarily for source code review for the Android project, so it should be familiar to anybody that has made code submissions to AOSP.
If you have contributed code in the past, or would like to help us review submissions, head over to http://review.cyanogenmod.com/ and sign up. We are using Gerrit effective immediately, and your changes will be reviewed and make their way into the CyanogenMod source much quicker if you use Gerrit.
If you need help, I’ve created a wiki article which is currently a work in progress, however it should help get you started.
Thanks for all your contributions! CyanogenMod wouldn’t be where it is today without the great community of developers that we have.
PS – I’ll be writing a blog post soon on our continuous integration setup using Buildbot, an amazing open source product.
CyanogenMod-6.0 Status Update
A new round of release candidates went out this weekend for all of our supported devices with a lot of new features. It’s time to switch to bugfix mode and get an actual release out. Head over to the download section/forums to get the latest release candidates and nightly builds.
Supported devices for 6.0:
Things that aren’t in 6.0. but may be in 6.1
CM6.. Coming soon to a phone near you!
CyanogenMod-6.0.0-RC3 – Nexus One
Latest version: 6.0.0-N1-RC3 – 08/15/2010
Download: CLICK HERE
Mirror: CLICK HERE
MD5Sum: e78d66969e4288877ea86bb6d1da9696
Google Addon: HDPI-20100814
Mirror: CLICK HERE
Mirror: CLICK HERE
Radio Firmware: 4.0.6.00.12_7 (FROYO RADIO, REQUIRED!)
Download: CLICK HERE
MD5Sum: 3321c196d8ec1cf748fd20c3c4068520
Check here: CM Forums | XDA Forums
Enjoy, and don’t forget there is also a newer version of Google Apps!
CyanogenMod-6.0.0 RC1
It’s been a few weeks of work, and a great effort from everyone involved! I’d like to present the first CM6 release candidates for the Nexus One, Dream, and Magic phones! Versions for other devices are on the way.
Check out the CHANGELOG for a full list of features and contributors.
It’s available for download via ROM Manager, or direct links can be found in the links below:
Nexus One: CM Forums | XDA Developers
Dream & Magic: CM Forums | XDA Developers
CyanogenMod-6 Progress
It’s been just under a week since Google released Froyo (Android 2.2) into the open-source world and we’ve made great progress on CyanogenMod-6 already. Approximately 20 of us on the CM team are working hard on merging all of the community-developed extras in, as well as porting to new devices. Google did a great job and really gave us the best foundation to start from this time around.
Here’s where we stand so far.. Most of the CyanogenMod extras have been merged. Some features are being reworked (like trackball settings), new device ports are well underway. The first devices to see CM6 experimental releases will most likely be the Nexus One and Droid simply because those are the devices that “just work”. The Dream/Sapphire port has everything working but one small issue remains. Wes Garner has the Slide port well underway. I don’t have a status report of the Desire, Incredible, and Evo versions at this time.
I’m expecting that we should have some experimental releases by the weekend, but please don’t spam us asking for ETAs.. We are just as excited to get this out as you are
You can follow our progress on Github or drop by irc.freenode.net in #cyanogenmod or #koush.
Regarding updates to CM5.. A small update will be coming this weekend to fix a few bugs but the focus will remain on CM6!
Thanks to everyone who has been supporting us with testing, bugfixing, code, new features, and of course donations. CM is what it is because of the community. Thank you!
New Website Design!
Well, without stating the obvious the CyanogenMod website has been completely re-designed with a custom theme.
The theme now blends in more in line with our Forum and soon to follow also the Wiki.
I’m now working on the integration and other features between the CM Web portfolio. These are taking longer to develop and may take a bit more time before the implementation is fully in place.
Until then, enjoy your new CyanogenMod website!


























Online Orders with Delivery by Download





- ICT (information and communications technology - or technologies) is an umbrella term that includes any communication device or application, encompassing: radio, television, cellular phones, computer and network hardware and software, satellite systems and so on, as well as the various services and applications associated with them, such as videoconferencing and distance learning. ICTs are often spoken of in a particular context, such as ICTs in education, health care, or libraries. The term is somewhat more common outside of the United States.






























Follow Us On Twitter









My search ended without having found something I really liked...
But while searching, I had an idea: Why not just use a spreadsheet hosted on Google Docs as the base for a CMS? It has a couple of advantages:
- Simple, everybody knows how to use a spreadsheet application
- you get an online editor for free
- Google Docs does versioning, so it's easy to roll back changes
- Backup/restore and import/export is simple
The GAE app would only need to pull the data from the spreadsheet, apply some post-processing and output it. Not really much for the app to do, so I decided to write a little prove-of-concept application. I was using the following ingredients- Google App Engine SDK for Python
- gdata-python-client, the Python version of the Google Data API to access the spreadsheet
- Mako, a templating system for Python
- and some code to glue these together
The app expects 2 tables to be present in the spreadsheet: pages and templates. Both need a content column, the templates table also needs a name column. That's it. It could look like this:templates:
pages:
There are 2 templates defined, main and defs. The template main is the base template for the html output, defs holds some Mako style methods (more on whose later).
The pages table holds 3 pages. The first one is used as the root document, the others can be got via http://<host>/page/<id>. The content is treated as a Mako template, references to other templates are resolved by looking up the name in the templates table. Therefore the first two lines load methods from the defs template and make the page inherit from main:
The page content invokes 2 methods, image() and page(). The methods make use of global objects that are injected into the global Mako template context:
db.<table>[<row_no>]['<col_name>']
Using the db object any table of the spreadsheet can be accessed. This way the system can be extended in a really easy way. In out little example this is used for the image() method. References to images are stored in a table called images and are referenced by an id:
When rendering the root url, this now results in:
Not really a useful page, but you get the idea.
The python code for the whole thing looks like this:
Of course this is not production-ready code. A lot of error handling is missing and one needs a proper way to handle the gdata login captcha requests (I guess storing a valid token would work). There is also no caching implemented.
This of course is not intended to replace a full-blown CMS. But I guess if you would spend some time fixing these things, this could be suitable for small web sites, where all content is more or less static.