
Let’s get this out of the way right now – this subject is a bit geekier than much of what we discuss here at 40Tech. It involves serious hacking to your Android phone. Specifically, we’re going to discuss the pros and cons of flashing to a custom ROM on Android. Think of a ROM as a customized version of your phone’s operating system, including the kernel, apps, and just about everything else. Should you take the plunge?
Prior to deciding to install a custom ROM, I had upgraded to the long-awaited Froyo upgrade for the AT&T Captivate (AT&T’s version of the Galaxy S). Doing so gave me a taste of what I’d been missing all this time, and inspired me to find out what else was out there. I took the plunge, did a bunch of research, and am now running the Serendipity 6.2 ROM on my Captivate. The verdict? I wish I had done this long ago. Let’s take a look at what was holding me back, some of the pros and cons of updating, and whether my concerns were valid.
Stability
My biggest concern in installing a custom ROM was that my phone would be less stable. Do your homework on which ROMs work for your phone, but I’ve found that my Captivate is actually more stable than it was out of the box. Prior to installing Serendipity, my email app frequently locked up on me. That is no longer the case. I haven’t done any scientific testing, but my phone feels just as stable as it did with the original ROM, after 5 days of use. Again, though, do your research for your phone, to see what ROMs are considered to be stable. The xda-developers forum is a good starting point.
While stability hasn’t been an issue, that doesn’t mean that custom ROMs aren’t without issue. See below for some issues and other considerations.
Speed
You don’t want your phone to run like a dog after you update. In my case, this one was no contest. My phone is snappier now than it was prior to the update. The Serendipity ROM uses a different file system, that by all reports contributes to the speed. The ROM also defaults to using HSPA for its Internet connection, which is a bump up from basic 3G. Not to keep repeating it, but do you homework to learn how fast or slow a particular ROM is on your device.
Polish
You might wonder whether independent developers can touch the polish that (arguably) comes with the stock Captivate experience. They can. In fact, most of what the custom ROM offers is actually taken from stock Android, that was bastardized by AT&T.
When studying ROMs for my captivate, I found that they fell into two general categories. Some, like Serendipity, were based upon the “pure” Galaxy S ROM, making them more up-do-date and advanced, but lacking tweaks specific to the Captivate’s hardware (although tweaked to try to eliminate any issues). Others were based upon a leaked 2.2 build for the Captivate, and were hacked up to make them more modern.
Difficulty
I was also worried that installing the ROM would be difficult, and that I’d brick my phone. While the process wasn’t a walk in the park, it was easy enough that it could be done by someone with a bit of tech know-how and the ability to follow directions. My experience was actually made more difficult because I had updated to Froyo prior to getting the new ROM. I had to go through a process to get back to Eclair prior to installing the ROM, since the instructions required that. The second time that I did this (going from Serendipity 5.12 to 6.2, for which the recommended install included a wipe back to Eclair), I had a few nervous moments where I couldn’t get the restoration program to work. In the end, it all worked out. I followed these two sets of instructions when installing Serendipity:
Look them over, and if they make your head explode, or if bricking your phone would be a major disaster for you, then maybe a custom ROM isn’t your cup of tea.
Extras
As noted, Serendipity (and most custom ROMS) will get you closer to a pure Android experience. In addition, carrier bloat has been removed. Your device will no longer be littered with extra apps (dare I say crap?) that you can’t remove. Serendipity’s website also has a kitchen, where you can add additional features to your phone, such as a better battery indicator for the notification bar. These add-ons also allow you to restore some of the manufacturer’s apps, such as Samsung’s email client, that aren’t included in the ROM by default.
Issues and Other Considerations
Installing a custom ROM isn’t for everyone. First, while not overly difficult, it isn’t trivial, and you do run the risk of bricking your phone.
Most ROMs also are updated much more frequently than a carrier provides updates. In fact, after I initially installed Serendipity, three updates were released. While you aren’t required to apply updates, it can be very tempting. Minor releases are easy to apply, while rewrites (such as going from 5.12 to 6.0) are a bit more involved, with it often recommended that you follow the procedure you used the first time you installed a custom ROM.
You also should take stock of how important the carrier or manufacturer’s changes are to you, and look into whether your ROM supports those changes. As noted, Serendipity allows you to add most of Samsung’s apps back to your device, but the same isn’t true for AT&T’s apps. Also, I ran into a problem with, Swype, a free alternative keyboard on the Captivate. I had installed it as an add-on (trying to restore a feature that my phone had already offered), and after a few days got an expiration notice. I had to go through a fairly complicated process using command lines to uninstall Swype, and then install the Swype beta for which I am registered.
Conclusions
I’m still early in the process, but I would have a hard time going back to the stock ROM on my phone. The extra features and speed in a custom ROM are compelling. Let’s be honest though- part of the enjoyment of a custom ROM, for a geek, is in the successful tinkering, and knowing that you’ve made your phone your own.
Are you temped to install a custom ROM? Maybe you’ve already done so? How it is working out for you? Let us know in the comments.
Broken phone image by Robert Nelson
Hmm . . image by hobvias sudoneighm
Anthony Russo says:
I’ve been tempted but at this point the chance of bricking my phone is keeping me from taking the plunge.
This is a compelling argument to do so though.
hmmmm considering considering…
Anthony
March 16, 2011 — 1:44 am
Evan Kline says:
I was worried, too, and then saw and ordered a little gadget for my Captivate, just in case. Normally, with the Captivate, there is a way to get a bricked phone into download mode (a developer mode of sorts that you can use to load stuff onto it) by inserting some wires or something into the USB/power port in a particular way. Somebody sells a little plug that automates that, so I bought it for about $10 just in case I needed it (I didn’t need it in the end).
It was time consuming, but not overly difficult. The only part that had me sweating was when I couldn’t get ODIN to recognize my phone. ODIN is the program to restore a phone back to stock status, which is the starting point in the instructions mentioned in the post. By then, my phone was already in a non-usable state, so I was a bit worried. I finally re-downloaded ODIN from another site and put it on another machine, and it worked from there.
March 16, 2011 — 3:50 pm