Almost a month ago, I wrote a raving review on Android 4.2. In the post, I commented on how important it is for Android to have these incremental updates and even praised the bunch of features introduced in the new iteration of Jelly Bean. However, after a month of using 4.2 as a daily driver, I am afraid I can’t say the same about it today.
In fact, I was already annoyed by a few bugs 2 weeks ago but had been preoccupied with a lot of stuff, so I didn’t find enough reason to roll back to 4.1. Plus doing a fresh install is always a painful experience for me. I typically have about 100+ apps installed on my device at any time and re-installing and re-configuring the majority of them is extremely tedious.
Of course, I’d like to point out that what I mention in this post is by no means conclusive and the issues may be device-specific or even subjective. Or maybe not.
Deal-Breakers:
1. Battery Issues
2. Screen of Deaths and crashes
3. Less responsive than 4.1
Battery Issues
This is a deal-breaker for most people, I am sure. But I am not one who blindly complains about battery life while doing everything wrong with charging and maintaining. By “battery issues”, I don’t just mean poorer battery life but the fuel gauge is completely messed up. This is no baseless gripe. I always practice the habit of keeping the battery level between 40-80% and only charge it fully once or twice a week. In Android 4.2, the battery fuel gauge acts up no matter how much I’ve conditioned the battery. In extreme cases, the device would auto-reboot and the battery % would drop all the way down to 8% from initially 60+ % or so before the reboot. I am sure this is nothing new to the community of Android flashers. Such a thing doesn’t really happen when I was using Android 4.1.2, except once or twice when I really mis-calibrated the battery. Also, battery drain is humongous. To put things into perspective, same number of apps, same usage, same kernel, I get 10 hours of standby + at least 2 hours of screen time on Android 4.1. On 4.2? 7 hours of standby + 1.5 hour of screen time if I am lucky. The standby drain is far too obvious and do I even need to mention the screen-on drain?
Screen of Deaths and Crashes
This part annoys me to no end. Really. Imagine scrolling through your contacts, whatsapp conversations, tweets, and the screen just went ice cold. There are also stability issues with the camera and gallery app that have no proper fixes. Although much later builds are claimed to have the problem fixed, I have been more annoyed than impressed to give 4.2 another shot. Also as I mentioned earlier, those random reboots could also mess up the battery %, making it very difficult to get a clear picture of realistically how much % is left.
Responsiveness
This is purely from a user-experience standpoint. I am very very particular about device performance especially in terms of responsiveness. Not that I am saying I must have a ROM that is lag-free but that if there’s a lag, even a very minor one, I notice immediately without fail. On numerous occasions, 4.2 gave me lags while switching from one app to another, while typing, while launching apps. This wasn’t really a deal breaker for me when I was using 4.2 for over 3 weeks but when I rolled back to 4.1.2 last night, the difference was almost striking.
To sum up, again I am by no means bashing Android 4.2 or the work developers have put into the Cyanogenmod project to make it possible for us to get a taste of 4.2 so early. Quite the opposite actually; I have tremendous respect for the devs who put in time and effort to make it work for us, even when they have no proper support, such as source code or documentation whatsoever to work with from the official channels. I am just saying that I’ve had a much better experience using Android 4.1.2 than 4.2 and that I won’t likely return to 4.2 anytime soon. If you have a different experience or if you have any advice on how to make 4.2 work perfectly for you (especially in performance and battery departments), please kindly do share!
John Beaves
/ February 4, 2013Good fair review,I have experienced similar problems,wish they would concentrate on getting a stable version of Jelly Bean out rather than continuously adding features to unstable Roms,what version of 4.1 have you gone back to? Post a link if you have time.
Valent Turkovic
/ March 5, 2013I’m in the same boat as you. What are you using right now? I would like to switch also back to 4.1.2…
richxiong
/ March 5, 2013I am not using official CM, but this http://forum.xda-developers.com/showthread.php?t=1891222 I am on MCM’s CM 10 20130202 build for now and I don’t foresee myself flashing anything else in the near future. Stable and almost issue-free.
Valent Turkovic
/ March 5, 2013Thanks. Installing it right now. Does 4.1.2 have butter or not? Does it even matter if it doesnt?
Valent Turkovic
/ March 5, 2013Hmm, I have formated /data, cleared dalvik cache a also cache partition but after installing MCM’s cm-10-20130202-MCM-i9100-vsync_sysfs.zip but after install Android Keyboard just crashes and I can’t use this ROM
((
richxiong
/ March 5, 2013Buttery smoothness is definitely there. If you have already tried 4.2, 4.1 is a much more stable and smooth version. Didn’t you use 4.1.2 before? I mean before trying 4.2.
richxiong
/ March 5, 2013Try getting back into Recovery. Wipe Dalvik Cache, and Fix Permissions then reboot. If all else fails, clear data, wipe cache, wipe dalvik cache and re-flash the ROM again. Should work.
Valent Turkovic
/ March 5, 2013I had no stability issues with MCM CM10.1 and also no issues with official CM10 nightly builds, just battery issues on MCM CM10.1 that is my primary reason to switch back.
Valent Turkovic
/ March 5, 2013I can’t seam to get rid of Google Apps and they are causing the issue. I thought that formatting /data gets rid of them… but they are also somewhere on internal usb memory that I can’t format because all of my data is there…
http://rootzwiki.com/topic/38319-fixed-unfortunately-android-keyboard-aosp-stopped/
richxiong
/ March 5, 2013Hmm did you flash the wrong GApps? You’re aware the 4.1.2 and 4.2 GApps are different packages right? If you really have run out of fixes, I suggest you go back to what works for you before? Official CM 10 maybe? I haven’t encountered such issues before. Hard for me to visualize how to fix. Normally re-flashing a ROM fixes most issues for me.
Valent Turkovic
/ March 8, 2013Nope. Issue happened BEFORE I even installed GApps. I had GApps even if I didn’t install them. That was the issue.
Valent Turkovic
/ March 8, 2013It was really strange issue, usually after formating everything (expect internal sdcard) and installing CM based ROM I have to install GApps afterwards. How it seams that GApps persisted somehow… but after few flashes and install of older GApps and then formatting and flashing again I finally got to point that CM10 has no preinstalled Gapps and keyboard doesn’t crash…
Installed Gapps (right version) and now finally everything works, except I still have same battery issues
AndroidOS process is still draining my battery, same issue I had on ICS
I’ll try different Syah kernel, I’m using V4 right now, I’ll try V5…
Valent Turkovic
/ March 8, 2013Sorry, I misspoke… I HAD Siyah V4 kernel on ICS and still battery issues, now I have stock kernel that comes in MCM’s ROM and issue still persists. I’ll flash V5 right now on MCM’s JB ROM and report back.
richxiong
/ March 8, 2013To be honest, I have battery issues here and there. Sometimes the fuel gauge was bad. But my battery has never been replaced in over 2 years, I think, and I’ll be upgrading soon so I won’t invest in a new battery. You can try discharge/charge cycle and see how it holds up. Let everything settle in a couple of days.
Valent Turkovic
/ March 12, 2013Now that I have Siyah kernel things seam better than with stock CMC’s CM10 stock kernel…
Does Siyah show splash boot image also on CMC’s CM10.1 ? Because I didn’t see it, so maybe I had tried installing but failed for some reason because I didn’t see that splash logo during boot until now.
valent
/ March 15, 2013Have you tried http://www.slimroms.net/ ? Friend who has S2 uses their 4.2 rom and told me that it works perfectly… Haven’t tried it myself yet…
richxiong
/ March 15, 2013Not yet. I am finding too much comfort in my current setting with 4.1.2. Don’t think I’ll likely change. Only a few months left on contract with S2.