A few months ago I wrote "Stock Android Isn't Perfect," an article where I turned my usual harsh UX critique on stock Android, instead of just picking on TouchWiz and Sense all the time in my reviews. The article went over pretty well, and even got a few responses from Googlers! I didn't cover everything that was wrong with Android, though, and there have been a bunch of updates since the original article, so it's about time I wrote a sequel.
The lads at the Android Open Kang Project have been busy expanding the 4.2 version of their custom ROM, thankfully expanding on the three officially supported devices in the initial release. For Build 2, all four major US variants of the Galaxy S III are supported (but not the international version), as well as the Nexus 7 3G, and the Nexus 10 for good measure. Flash-ready ROM files are available on the AOKP website for the Galaxy Nexus, Nexus 4, and Nexus 7 WiFi as well.
Good news, ROM enthusiasts: the Android Open Kang Project has released the much-anticipated first build of 4.2. Bad news: it's a completely new ROM, built from the ground up. That means that it won't be quite as feature-packed as you remembered, and device support is limited to the more popular Nexus models, at least for now. You'll also need to install a recovery that's compatible with 4.2 ROMs (the latest ClockworkMod and TWRP should do the trick) and do a full data wipe of your previous ROM.
Apktool is a Windows/Mac/Linux utility for reverse engineering Android apps. It allows you to decode an app, change something, rebuild it, and pray it still runs. You're going to need something like this if you're into theming apps, hacking a feature onto someone else's app, finding security holes, or just want to hunt for info.
Apktool has been freshly updated to version 1.5.1, with the new headline feature being "Android 4.2 support." Here's the full changelog.
Another day, another round of nightly builds for the upcoming CyanogenMod 10.1. This time, the latest release of the custom ROM that brings Android 4.2 has been made available on a further 3 devices: the Google Nexus S, Nexus S 4G, and the ASUS Transformer Pad 300 (TF300T).
The Nexus line is still one of the few places you can find Android 4.2. The software on most Nexuses has zero interference from carriers and OEMs. That's great for Google as it gets to control the entire software experience. The downside is that there is no one else to point the finger at when something goes wrong. And something is pretty hilariously wrong in the startup wizard on the iPhone – I mean, the Nexus.
CyanogenMod 10.1 is continuing to bring Android 4.2 to more devices each day, and Samsung fans will be glad to know that nightly builds are now available for:
- Galaxy S (galaxysmtd, galaxysbmtd)
- Galaxy S II (i9100, i9100g)
- Galaxy S III (i9300, d2tmo T-Mobile, d2att AT&T)
- Galaxy Tab 2 7.0 and 10.1 (p5100, p5110, p3100, p3110)
If there's one thing that can be said of Dolphin Browser, it's that the dev team behind it stays on top of things. There's a steady stream of updates to the browser all the time, bringing new features, performance improvements, and all that other fun stuff that people usually like when they're favorite apps get.
Today's update is no different, though it is a little more notable. First - and most importantly - v1.2 brings support for Android 4.2.
It's time for another installment of Getting To Know Android, the series where we show you every polished pixel in Google's latest Android update. Today's target is the Gallery, which, in a rare APK Teardown whiff, is not white. I have no idea what was going on with our crazy 4.2 alpha version, but the Gallery is still black, and the icon is still the same. Sorry about that. There is lots of new stuff to talk about, though.
Earlier today, we noticed a bug report for a very strange issue with multiple user accounts on the Nexus 7. Apparently, certain applications are displaying the underlying screen - be it the wallpaper, app tray, or the Play Store (depending on where the app was launched from) - through the foreground app. But here's the kicker: it's only happening on secondary accounts. Yeah, it's confusing and strange.
There's also a Reddit thread that confirms this is happening, and it seems to only be affecting apps that call on some sort of transparency.