Android

Custom ROMs for Jelly Bean, are they really necessary?

Nexus Jelly bean

So I’ve always loved flashing custom ROMs on all of my Android devices, but during the past two weeks I’ve come to a bit of a revelation. I think Android has matured to a point where custom ROMs aren’t really necessary any more. SHOCK! RECOIL! HORROR!

Now, please don’t misunderstand me. There is validity to its existence, because it offers some fantastic additional functionality over Google’s stock offering, but do we NEED the custom ROMs? No, I don’t think so, not any more. Let me explain.

In the past, Android devices were, let’s be honest, slightly underpowered. Speaking from my own experience, the HTC Desire and Nexus S were fantastic devices, but they needed customisation to really make the most of their capabilities.

I’ve tried it all

So I tried all the custom ROMs, kernels, radios, etc to maximise battery life and of course the speed of the devices. With my Nexus running Android 4.1.1, I don’t need to flash custom ROMs, because what Google has created is the most polished, fastest and easy to use version of its open-source operating system yet.

That said, there are some very good custom ROMs out there for those keen to give them a go. I’ve found a few that I really like, and it’s not the most feature packed offerings, but it’s pretty much bug free and all of the ROM’s offer improvements over stock, but like I said, the improvements are minimal and in my opinion flashing ROMs has become something to do for fun, whereas in the past it was essential.

The Bugless Beast

Peter Alfonso’s Bugless Beast is the first. I’ve used Bugless Beast on all of my Android devices and Pete’s work really, which practically speaks for itself. The ROM is clean, fast and offers slightly better battery life than stock. He has replaced the stock Jelly Bean browser with Chrome, which isn’t exactly to my taste, but reverting is pretty easy, so it’s a minor inconvenience.

Rascarlo’s RasBeanJelly is the only themed ROM I’ve ever tried and really liked. He keeps it close to AOSP, so it’s fast, and light on battery. The main theme differences are that some menu icons are blue instead of white and the gradient background has been removed and replaced with black backgrounds, and that of course helps save a little bit of valuable battery juice. Support for the ROM is definitely some of the best around as it’s hosted in the Trinity kernel thread, one of the most helpful I’ve found on the Nexus forums over on XDA.

CdtDtroid impresses

Finally I came across a developer whose work I’d never used, but as soon as I did, I was impressed. CdtDroid currently has three ROMs that he builds and supports for the Nexus. The main ROM is AndroidME, it’s got everything you want from a ROM and the best part is that he offers OTA style updates, meaning an update is only about 30MB to download, as opposed to 200MB for an entirely new ROM. The two other ROMs are AOSP Light and his CM10 Kang, both hosted and supported in the same thread.

AOSP Light is exactly what the name says, it’s a very lightweight, minimalist ROM based of the latest source code from Google. It’s the custom ROM I ran the longest on my Nexus and I highly recommend giving it a bash as it’s close to stock and super responsive. His CM10 Kang (a Kang is “The process of creating a code based off someone else’s code or reapplying code that someone else created into your own code”) equally fast, but it’s based on the latest CyanogenMod source code which is optimised and tweaked, pretty well I might add. I must add that swipe to clear notifications, introduced first in CyanogenMod 7 may be one of the best tweaks of the custom ROM.

It’s fun to flash

There are a good few other ROMs out there at the moment though, the Android Open Kang Project is very popular, Liquid Smooth is another one I see a lot of people raving about and of course the king of the custom ROMs, CyanogenMod 10 is also in the works.

There are certainly are a lot of ROMs to try out on your Nexus Prime (I don’t like to refer to my Nexus with Samsung branding, I know, strange right?), and they’re all pretty unique, however, I do think that with a good custom kernel, you can completely eradicate the need for any custom ROM flashing. That doesn’t mean you shouldn’t though, because trying new things is fun, right? So as I’ve said a few times now, you don’t need to flash any custom ROMs if your Nexus is running Android 4.1.1, but it sure is fun.

  • SJ

    Hey Rick, agree mostly… I was on stock JB and it was great. That said, there is still some basic functionality missing which requires either installing separate widgets or ultimately rooting and flashing roms/kernels. One small example is the percentage of batt left. I know there are several widgets for it in the mkt but I shouldn’t have to get one for something which should just appear on or where the battery icon is for a one look update. Then there are the bigger things like better batt life and OC, CPU scaling etc. I’ve been running CDtDroid’s AOSP lite with a simple batt % mod and Franco’s kernel. Have all the stability of stock with power when it’s needed and small tweaks to increase functionality. and 4hr50min screen on time.

    Infact, I would argue that with increasing ease of use of the whole rooting, flashing and modding process plus the brilliant forums for help like XDA,, as witnessed by a relative ‘Noob’ like me, there might well be a time soon when this should be the default way to go and not just for tech geeks lol

  • http://twitter.com/rickbosch Rick Bosch

    Thanks for the comment, SJ, I am also running AOSP light, but with Trinity at the moment, I am a huge fan of Morfic’s work.

    It’s all personal preference, especially when it comes to battery percentages, notification toggles, etc, I personally don’t use either, but I do believe that those omissions could be included in coming versions of Android.

    Look at the “swipe to clear notifications” that’s obviously from CM9, so the custom Android world undoubtedly influences what Big G does with it.

  • Pingback: Custom ROMs for Jelly Bean, are they really necessary? – gearburn | 100 Blog Strong

  • Eric

    Um, actually, “swipe to clear” notifications were in stock ICS, too. CM9 did not make that up. And, if AOSP has not incorporated the option for the 1% battery mod by now, I don’t think it’s going to happen.

  • http://twitter.com/rickbosch Rick Bosch

    Yip, right you are. Sorry, I meant to say CM7. It was in Gingerbread when the CM team first baked in the swipe to clear functionality.

    And you never know about the battery percentage, it might still pop up, someday.

  • Stephen Phillips

    This might be slightly off topic as you are talking about Nexus phones, but for some of us, the custom ROMs are essential. If it weren’t for the custom ROM makers, we wouldn’t have Android on our HTC HD2 phones. It’s a Windows Phone, but it has a nice Android community.

    Also, I wonder if some of custom ROMs purpose in life is to keep us up to date when carriers or hardware manufacturers do not. I first started flashing my G1 because it was the only way I could get Froyo on it.

  • http://www.facebook.com/jason.gomez.3114935 Jason Gomez

    I put cm10 on my AT&T HTC One x and everything works awesome – except the camera is a definite downgrade from the Sense camera, and Beats is gone… that’s the best audio i’ve EVER heard from a phone, esp with headphones. Any way to get these awesome pieces back without the rest of the Sense bloat and lag/stutter?

Related articles


Topics for this article

[ advertising enquiries ]

MORE HEADLINES

Gadget News

VIEW MORE

games

VIEW MORE

iPhone

VIEW MORE

tablets

VIEW MORE

blackberry

VIEW MORE

iPad

VIEW MORE

mobile apps

VIEW MORE

android

VIEW MORE

More in Android

Nikon Coolpix S800c is world's chunkiest Android Gingerbread camera

Read More »