I finally did it. I rooted, and took the plunge. This past week, Cyanogen release CM6.0, based on Android 2.2, aka Froyo. What the heck is this rooting business about? One of the nifty things about Android is the open source nature of the beast. Since the source code is all out there, users are free to modify, remix & reload to their heart’s content. Now, I’ll grant you that you’re not likely to find a lot of kernel hackers out there who really want to squeeze the last bit of performance out of their phone. However, that’s not to say that there aren’t users who want to serve up the phone “their way,” be that simply changing the look & feel of the device, swapping out the kernel for one that underclocks the CPU to save battery, or even simply gaining more control over the device (especially true in carrier-subsidized devices).
Right now, CM6 is available for a handful of HTC devices, as well as the original Motorola Droid. For a complete list, check the wiki to see if your phone can use CM6. First up, you’ll need root access to your device, as you’re going to need to flash a custom recovery image onto your phone. Don’t worry, it’s not as scary as it sounds. Again, back to the wiki, look at the detailed directions for your device. For some devices, like the Nexus One (what I’m using), you may want to grab the “Universal Androot” package. It works for the N1, as well as a bunch of other devices, and is available from the developer’s site. And yes, Virginia, there is enough of the pages written in English that you’ll be able to figure it out. If you’re a phone that’s not supported by the Universal Androot, you’re not sunk yet. There’s either a manual process, which will be described on the wiki, linked above, OR if you have an HTC Evo, Desire, Incredible, Wildfire, Aria (aka Liberty) or Hero, you can use unrevoked. It’s pretty painless.
Warning: once you root, there may be no going back, especially if you do something like unlock the bootloader. Officially speaking, once you unlock the bootloader (which isn’t always required), your warranty may be void. I’m not responsible if you blow up your phone, start a small war, or your cat runs away.
Another warning: If you’re using a device that uses the HTC Sense UI, flashing CM6 will cause the UI to revert to the standard Android UI.
Got root? Ok, now it’s onto the easy parts. Install ROM Manager from the Android Market. You can use the free version without any troubles. Got that loaded? Go ahead and flash the Clockworkmod Recovery to your phone. ROM Manager should autodetect what type of phone you have, but it will ask for confirmation before it does anything.
Ready to roll? Ok, grab the CM6 ROM image from a mirror. While you’re at it, grab the latest Google Apps zip file for your phone type as well. Stash those on your SD card. Here we go. First up, a full backup. Back into ROM Manager, and “Reboot into Recovery”. In the recovery? Ok, now do a backup. This is also called a “Nandroid Backup”. What the heck is that? Put simply, it’s a full backup of your current ROM image. You want to do this. REALLY.
Once you’re in the recovery menu, just do a backup. Navigating the recovery menu uses the trackball to go up, down & select, and the power button acts as a “back button”. Your backup will take 3-5 minutes, and will require about 300-500 MB on your SD card. Make sure you’ve got the space available! For your reference, my Nexus One’s backup of the stock 2.2 image was 303MB.
All backed up? Ok, let’s go. Do a factory reset/wipe and wipe the cache as well. Next, install a zip file from the SD card, specifically the CM6 ROM. Repeat the steps to install the gapps image as well (if you’re planning on using the gapps, and you probably are). All done? Reboot. Your phone will come up like it’s all brand new.
I’ve take some additional steps, going a bit further than just stock CM6. I also added the HTC_IME Mod keyboard, which replaces the standard Android keyboard with the HTC Sense keyboard. Once you get it installed, selecting it is as simple as doing a long press on a text field, and changing the input method to HTC_IME mod (assuming you’ve already turned the mod on in the system keyboard preferences!).
So back to the review. So, was it all worth it? I’d have to say yes. Absolutely. There was certain a small amount of inconvenience, associated with backup & restore of data, re-creating accounts and sync mappings, as well as the little things like prefs for ringtones, etc. That was far and away outweighed by the good stuff I got – better performance, enhanced feature set – especially the use of ADW.Launcher by default, and the enhanced power control widget.
Ok, so now suppose you want to go back to where you started, how do you undo all of this? Simply boot back into the recovery image, do another factory reset/wipe, wipe the cache and then restore. Reboot, and you’re back.
Android is still in many regards somewhat of a wild west affair with regard to software updates, especially given the open source nature of the OS. Will there be bumps along the way? Probably. Are you the type wants a phone that “just works” and doesn’t like to tinker? CM6 probably isn’t for you, nor is pretty much any custom ROM.
Recently, the nice folks at WOMWorld sent me an N97 Mini to review. Thanks guys. I received the Euro model, the RM-555, which supports UMTS on the 900, 1900 and 2100 Mhz bands, in addition to quad-band GSM and a 802.11g WLAN radio. Living in the US, I’d have preferred to have looked at a US model that included the UMTS 850 Mhz band, but beggars can’t be choosers, right? Right. So, on to the show..
The device’s size is great. Nice and small. I had an N97 for a (very) short time not long after it came out, and I was not a fan of the form factor. It felt almost like carrying around an old 9500. What a brick that thing was. Contrasted with this, I’d be totally satisfied with the form factor. Obviously, thinner would be better, to a point, but I’m not unhappy with the thickness. In terms of construction, there’s just enough metal to make it feel solid in your hands, like it’s not going to snap in half while you’re typing on it.
One problem I had with the layout – the position of the headphone jack. On my train ride home from the office yesterday, I had my headphones plugged in while listening to some tunes. Typing a couple of emails and texts was awkward. It would have been better if the headphone jack had moved toward the top, but the camera assembly would then need to be relocated. Typing on the keyboard wasn’t bad, took a bit of getting used to, but nothing ridiculous.
I’ve said it before, and I’ll say it again. S60 is really showing its age. Yes, S60 v5 has some advances over v3, even FP2, but it’s still got a lot of the baggage that’s accompanied S60 devices over the years – mostly speed related. This phone won’t win any UI races. The device lacks any form of multi-touch capabilities, due to its use of a resistive touchscreen. Yes, I’ve heard all the arguments about how you can use resistive screens while wearing gloves. Frankly, I don’t often find myself trying to use my phone while wearing gloves. I’d rather have a capacitive screen – much more responsive.
As it’s big brother does, the N97 Mini includes Ovi Maps, and is compatible with the new version of Ovi Maps that includes free navigation. I love the free navigation concept, and expect others to follow suit. That said, I much prefer using Google Maps. I find it faster and more responsive than Ovi Maps overall, and think it’s much better at finding things in the area because of its hooks into the Google Search infrastructure. I’d use something like Ovi Maps in my car for navigation, but I’ve owned a Garmin Nuvi for several years now, and I’m not quite ready to get rid of it.
For email, I’m using Mail for Exchange. The latest version for S60 v5 does not include HTML mail support, something I miss from my E72. I’m planning on trying out RoadSync on this phone as well, but since I already know that it doesn’t support network destinations (i.e. access point groups), I’ll be disappointed there as well, though I will get my HTML mail.
In the browser arena, as expected, I found the Nokia browser to be adequate, but not really as good as I’d like to see it. I tried out Opera Mobile on the device, and was generally more pleased with its functionality, though I found it to be slightly less responsive than the stock Nokia browser.
I ran a some speed tests from a variety of sites, using both AT&T 3G data as well as via the WLAN in my home. Over the air, I saw download speeds ranging from 500 – 780 kbps. Over the WLAN, I saw speeds around 1.2 Mbps. On my Mac on the same WLAN, I see about 18 Mbps down and 4.2 Mbps up (I have 20/5 FiOS at home). These performance numbers are consistent with my tests with other S60 phones, like the E71, E72 and my wife’s E75. It’s also close to what my iPhone toting friends in the area see.
In summary, the N97 Mini is definitely a better choice than the bigger N97. It’s more pocketable, and has the same features, with a better form factor. If all you’re after is an S60 v5 touch device, you’d probably be better off with the 5800 Nav Edition, but if you can’t live without a qwerty keyboard, the N97 Mini is a winner. Will I buy one? Probably not – I’m satisfied with my E72. Right now, Android 2.1 has ActiveSync that gets email and contacts. If they add calender support to it, I’ll be on an Android device before too long. Why? Newer devices, more innovation, actual integration with Google Voice – something I actually use on a daily basis and more than one vendor really interested in using it. Hopefully S60 can turn things around before my next phone purchase. As a co-worker said the other day, the call quality on Nokia devices is better than anything else I’ve ever used.
My trusty E71 finally took a dive for the last time onto a nasty floor. I was using a Nokia N85 for a bit as a stopgap. Great phone, fantastic camera, but typing email with T9 drove me nuts. The N85 is now hosting my home phone’s SIM. But this review isn’t about the N85, so back to the topic at hand..
Between the N85 and the E72, I tried out the Blackberry 9700, which was lovely, as much as a Blackberry can be, but lacked some of the features I liked, such as a working SIP stack, and especially the ability to tell when my data is moving through the corporate network/BES, vs. WLAN, vs. carrier data that’s not via the BES – I found that utterly impossible on the BB 9700. Otherwise, a nice phone. But again, back to the topic at hand.
First, I’ll start with the physical attributes of the E72. The E72 is a tiny bit wider than the E71, but is the tiniest bit lighter than the E71. The E72 trades in a good bit of the metal housing for plastic, but gets new & improved features like a 3.5mm headphone jack, instead of the 2.5mm mess that’s on the E71. Radios are mostly equivalent to the E71. Mine is the US variant, the E72-2, so it’s a quad-band GSM/EDGE device, with works on UMTS 850/1900/2100 Mhz bands. The 2100 Mhz band is a nice addition to the device, for users who travel abroad, as is the support for HSPA 7.2 Mbps. The WLAN in the E72 is essentially the same as the E71 – 802.11b/g. The camera is a nice bump in the E72 as well – a 5MP cam, a step above the E71′s 3.2 MP cam, with a single LED flash.
My favorite part about the phone? The messaging experience. At work, one of our options is Exchange ActiveSync, so I’ve been a Mail for Exchange user for quite a while now, even with its deficiencies, like the lack of ability to sync folders other than the Inbox, HTML support, and lack of ability to create a meeting request from the phone. The device works with Nokia’s Messaging service, which I’m not using at this time. For my personal mail (hosted by Google Apps), I use the Google Gmail app, which works just as well on the E72 as it did on the E71.
Overall, the E72 is a worthy successor to the E71. Right now, Amazon’s got it for $369. If you’re going to buy, please consider using my link to it.