The new “milestone” release from the Android Open Kang Project (AOKP) is starting to roll out today. So far, we’re seeing builds available for most Nexus phones including toro (Verizon Galaxy Nexus), toroplus (Sprint Galaxy Nexus), mako (Nexus 4), and maguro (GSM Galaxy Nexus). We’re told that a post detailing the full changelog is in the works, but for now, you can expect changes to the nav/statusbar for tablets, “rewritten” RomControl, custom toggles, and a ton of bug fixes.

To grab the latest builds for your devices, hit up the source link below. 

Ever since Verizon approved the Android 4.2.2 update for the Galaxy Nexus and Google started pushing it out, our inbox has filled up with users who are running into all sorts of issues. The most common appears to be battery life, but others are noticing issues with Bluetooth audio, the camera, tethering, and more. While we aren’t yet aware of specific fixes for each, in most cases, Verizon is actually recommending that you perform a factory reset.

I know that sounds like the worst option, since it wipes your phone of every last setting, but it may do the trick, especially if you are experiencing horrific battery life. The Bluetooth audio fixes on the other hand were supposed to be included in 4.2.2, but there is still a running AOSP thread that suggests a different scenario.

If a factory reset doesn’t work, you can also flash the 4.2.2 factory images that were released today.

Are you experiencing issues? If so, what are they? Have you tried a factory reset yet?

The Android 4.2.2 (JDQ39) factory images for the Verizon Galaxy Nexus have been posted. For those not familiar, factory images allow you to flash your phone back to a 100% stock state, as if you had just pulled it out of the box. You’ll find instructions for flashing factory images here.

The new 4.2.2 binaries are available as well.

Update:  They also added 4.2.1 factory images for the Sprint Galaxy Nexus.

Via:  Google Developers [Binaries]

This week, the CyanogenMod team announced that their newest nightly ROM builds of CM10.1 would include Pie Controls. We have been a fan of Pie since we first saw it being used in Paranoid Android, so it made us happy to hear it was coming to the more widely-used CyanogenMod. To help show some folks how to enable Pie Controls and set them up, we put together this nice little video that you see below. 

This week, there was an overwhelming cry for us to feature BAMF’s Paradigm v3.1 for Custom ROM Friday. We touched on the original Paradigm last year, but it looks like there has been some major updating going down since then. It is based off of Android 4.2.2, and brings some killer custom features, coupled with great speeds and long battery life. What else could you ask for in a custom ROM? 

I’ll admit that I’m one of Verizon’s biggest critics when it comes to the rate at which they update their Android smartphones to new software. They are unbelievably  slow for the most part. In fact, I’ve pointed it out a handful times, particularly with the Galaxy Nexus and the amount of time it has taken to update a device that should be the easiest of all. But we also know that Verizon stands firm on their update practices, which have a reputation for being the slowest in the business. Their network is reliable, maybe even the most reliable after all, and they attribute parts of their success to their testing practices. But something seems to have changed in 2013. I ran through a list of updates released by them this year, and the number is impressive. 

The day has come, the official Android 4.2.2 update for Verizon’s Galaxy Nexus is rolling out. We’re hearing from readers who are already able to force it to appear through the trusty ol’ Google Services Framework trick, while others have had it pop up without any work. 

After approving the Android 4.2.2 update for the Galaxy Nexus this morning, we were waiting patiently for Verizon to post up their official changelog, to make sure that the update was build JDQ39 and around 88MB in size. Thankfully for our sake, it is indeed JDQ39 and the same update as the build that leaked a couple of weeks ago, so for those who already updated, you are golden. And for those who wish to manually update instead of having to wait for the update to be pushed to their devices, you can go ahead and do that without worry.

Manual instructions here.