Kicking the tires
The next part, and in some ways the hardest, was finding out just how good the modded phone was for everyday use. Outwardly, everything seemed solid: I could make and receive calls, install applications, and get on Wi-Fi networks -- in short, do nearly everything I expected without trouble. Most of the differences between the old and new versions of Motoblur were not significant enough to throw me off.
Then I started to run into snags -- little ones, but problematic all the same. When trying to supply a password in certain contexts -- mainly, in a Web browser -- the cursor would jump to the beginning of the input field when I tried to type a number. This made it all but impossible to type directly into those fields. I had to type the password in another place, then copy and paste it in. Obviously this wasn't going to work if I was being constantly confronted with password fields.
Sure enough, after being confronted with this problem for the third time in a row (it's amazing how many times you need to supply passwords to set up an Android phone), I decided to give another ROM a whirl. Besides, Motoblur itself had limitations that I had never been all that happy with, and after dealing with it for a while I could see why people had called it "Motobloat." I didn't have the option of not using it -- until now.
Switching to the Cyanogen ROM
After some more casting around, I decided to go with a custom version of Android I'd heard a great deal about: CyanogenMod. In fact, I felt a little foolish that I hadn't started with CyanogenMod to begin with, given how professional and polished it is. I'd been trying too hard to stick with something familiar (some only slightly modified versions of the stock Cliq XT ROM).
The differences between Cyanogen and the more "stock" versions of Android (Motoblur and so on) are apparent pretty quickly. For one, Cyanogen doesn't ship with Android Marketplace or the various Google tools, such as Voice Search and Maps; those are packaged separately to avoid copyright issues. But getting around that hurdle wasn't difficult at all; I just had to download the appropriate package, dump it onto the phone's memory card, and use the bootloader to apply it as if it were a ROM.
Another major difference is the way Cyanogen has a great deal more flexibility of function -- and that many more low-level features exposed directly to the user. An entire subset of the Settings panel is devoted to Cyanogen's own behaviors. Audio, for instance: You can tweak an incredible number of behaviors devoted to sound, such as how notifications override other sounds in the system. The same goes for battery and CPU management, interface behaviors, and on and on. The vast majority of the defaults are sane, though, so you don't need to do a lot of poking around just to make the system useful (thank goodness). Cyanogen is also updated constantly, so chances are my phone won't be left out in the cold yet again.
Using the phone on a day-to-day basis with Cyanogen was pretty satisfying, although there were a few shortcomings that I think were more about the limitations of the phone's hardware than anything else. Some software -- the Kindle application for Android, for instance -- ran really slowly on the Cliq no matter what hardware speed tweaks I applied. Video applications like YouTube or Crunchyroll worked fine, though. And the most common crucial stuff, like the dialer or the Web browser, ran A-OK. On the whole, there was nothing stopping me from using the phone as I normally would.
Even better, I was able to tweak CPU usage to the point where the phone routinely used less than 10 percent of its battery power over the course of a normal day, and without significantly impacting performance. With the stock ROM, the Cliq XT had barely been able to last the day without a recharge.
Was it worth the effort?
The whole reason I embarked on this exercise was to see how much more life I could pump into a phone that wasn't going to be given any more leases on life by its manufacturer. No Android updates for the Cliq XT were going to be provided by Motorola, so it was either hack the Cliq or get a new phone. While I did get a new phone anyway as a safety measure, hacking the Cliq was more than worth the trouble. I now have a phone capable of running newer versions of Android, even if some of the applications don't run as well as they should.
The real test will be how well my hacked Cliq lasts through the rest of this year, through changes I haven't been able to foresee and with software that I haven't installed (or hasn't been released yet). For instance, if app developers begin restricting certain programs to run only on nonjailbroken phones, that'll limit the ultimate usefulness of those devices. So far this hasn't started happening across the board, but people are worried it might become standard procedure for apps that involve protected content (Netflix or Kindle, for example).
Many phone makers are also not crazy about the idea of allowing their phones to be extended by unauthorized third parties for reasons that have nothing to do with protected content. If you continue to use the same phone, that's one fewer opportunity for your carrier to sell you another phone -- and another two-year contract to go with it. That said, I suspect the carriers and handset makers alike will learn to live with it, since the total number of people who mod their phones, Android or otherwise, are unlikely to pose a major threat to the economics of phone sales or upgrade cycles.
Here's hoping my jailbroken and modded Cliq XT -- and all those other phones that haven't received an extended lease on life -- will live long and prosper.
This article, "Jailbreak! Upgrading a non-upgradable Android," was originally published at InfoWorld.com. Follow the latest developments in mobile technology at InfoWorld.com. For the latest business technology news, follow InfoWorld.com on Twitter.