We found 573 results for '"android 4.2"'
Those of you who decided to unlock the bootloader of your ASUS Transformer Pad 300 were likely pretty bummed when the 4.2.1 update started rolling out earlier this month (I know I was) since ASUS decided that unlocked devices shouldn't get OTAs. Thankfully, the company just uploaded the full ROM to its site for your flashing pleasure.
The TF300 marks the first non-Nexus tablet to get the bump to 4.2.x, which brings features like multi-user, quick settings, lockscreen widgets, and much more. Read More
It's been over four months since Google officially announced Android 4.2 and slightly less time since the initial round of new Nexus devices running it went up for order. Much like the gunshot that kicks off the 100-meter tortoise race, that launch signaled the silent contest to see which manufacturer could get out a non-Nexus update first. Today, we have our winner: ASUS, with a shiny new version of Jelly Bean for the Transformer Pad (TF300T). Read More
In the pantheon of devices bearing the name Nexus, there is one obvious black sheep. The Verizon Galaxy Nexus never really got the update love that GSM Nexus devices have, and there was that whole Google Wallet debacle. While the updates haven't been flowing quite like owners had hoped, a version of Android 4.2.2 is now rolling out to Verizon testers. It may only be a matter of time before the update is official. Read More
As the old saying goes, "when it rains, it pours down binaries for Nexus devices." That old idiom is proven true once again today, as Google has just uploaded the latest batch of binaries to the Nexus Device download page.
The binaries essentially contain the proprietary hardware drivers that you won't find in AOSP for their specific devices. This go around it's for Android 4.2.2 (build JDQ39) for all of the latest Nexus gadgets: the Nexus 4, Nexus 7 Wi-Fi, Nexus 7 3G, Nexus 10, GSM Galaxy Nexus, and VZW Galaxy Nexus. Read More
It's that time again, custom ROM fans. The oh-so-versatile Android Open Kang Project has released its fourth 4.2 build, this time updated to the latest 4.2.2 AOSP code. While feature additions beyond the ones added by Google themselves are few and far between, the list of supported devices for AOKP 4.2 has greatly expanded. Most of the phones in question come from Verizon's Motorola stable.
The full list of added phones includes the Motorola DROID 3, DROID 4, DROID Bionic, DROID RAZR (and by extension, the DROID RAZR MAXX),the international GSM Motorola RAZR (XT910), the HTC One XL, and Sprint's version of the Galaxy Nexus. Read More
With the Android 4.2.2 update finally rolling out for most Nexus devices (minus Sprint / VZW GNex), Google has posted factory images of each on the Nexus Factory Image page. These images are useful for flashing your Nexus device back to stock, whether to get an OTA update, or fix that brick you just caused.
These images are for the Nexus 4, Nexus 7 (Wi-Fi and 3G), Nexus 10, and Galaxy Nexus (Yakju / Takju variants). Read More
Good news, everyone! The Nexus 4 Android 4.2.2 OTA (JDQ39) is finally here, surprisingly late in the update cycle, following the Nexus 10 and older Nexus devices, such as both variants of the Nexus 7 and both variants of the Galaxy Nexus. Chances are you probably don't have the coveted update notification just yet, but who wants to wait if you can sideload it manually? Rooted, unrooted, stock or custom recovery - it matters not. Read More
A few days ago, Google pushed out the Android 4.2.2 (build JDQ39) update to the takju variants of the Galaxy Nexus. Takju Nexuses are the devices sold in the Google Play Store, whereas yakju ones can be found in other retail channels. Good news for those waiting on the latter - though a day after its sibling, we finally have the yakju OTA file that can be applied manually on any stock device, including unrooted ones with stock recovery. Read More
A small change in Android 4.2.2 has left one of the biggest ad-blocking app on Android basically dead in the water. Adblock Plus is one of the web's most popular ad-blocking tools, and has been available for Android since November of last year. So, why has Google effectively killed it? Security issues.
Adblock Plus relies on the internet permission in Android to function, but it relies on a rather specific subset of that permission in order to work: the ability to automatically set a device's proxy server to 'localhost.' As is pointed out on a thread in the Android issues section of Google Code, this is a pretty serious security flaw. Read More