Verizon has announced that the Android 4.2.2 update for the Galaxy Nexus will start rolling out in phases today, March 19. No, this is not some sort of sick joke.

We’re assuming it’s the same build that leaked a couple of weeks ago as Android 4.2.2 build JDQ39. We’re still waiting for the support docs to arrive, so we won’t know for sure until that happens. But since JDQ39 is the most current version of Android, I’d assume it’ll be the one.

You can manually update to JDQ39 here with our instructions for all situations. If you just want the radios, you can grab those here.

Update:  The changelog is finally available and shows that the build is JDQ39. Feel free to manually update without worry!

Since the departure of Pete Alfonso and updates to his Bugless Beast ROM, folks have been on the search for a new minimal, stock AOSP build that brings smooth operation and vanilla Android feel. We received a few requests to make sure everyone new about a somewhat newcomer to the custom ROM scene called, Shiny. 

With the Android 4.2.2 update dropping tonight for the Galaxy Nexus LTE, we thought it was the perfect time to do a recap of some of the new features that came after 4.1. We know that not all of you jumped on to 4.2 ROMs as soon as they were released and instead stuck with official 4.1, so there is a chance that you may not know all that you were missing. And I hate to say it, but you were missing quite a bit, as 4.2 introduced all sorts of fun.

In this clip, we take a look at lock screen widgets (go get DashClock!), the new camera, the updated notifications panels, DayDream, and more. It may not touch on every single new aspect of 4.2, but these are certainly some of the bigger additions.

Full instructions for the update can be found here. The new radios are here. 

The new radios from the Android 4.2.2 (JDQ39) for the Galaxy Nexus LTE on Verizon that was released tonight are now available in .zip form. Thanks to XDA member mwalt2, this file should be flashable over any current G-Nex radios as it includes the full radio.img.

With little testing thus far, it’s tough to tell what kind of difference these can make it network connectivity, battery life, etc. If you are willing to take the risk and do not feel like leaving your current custom ROM, feel free to give them a look. Understand that the CDMA radio will take a while during the flashing process. 

Over the weekend, our buddy El Madhatter sent us a screenshot of his Galaxy Nexus test device which had received an update to Android 4.2.2 (JDQ39). This caused some excitement around the DL community, as in the past when we had seen leaks from him, they were quickly released for our own flashing. Unfortunately this time around, he had already taken the update and was unable to grab the file URL, thanks to a busy schedule. Well, folks, he finally found some time and wit ha little help from XDA member oldblue910 has grabbed the direct Google download of the update for your flashing pleasure. 

Earlier this week, Verizon’s official Twitter support account made mention of a new Galaxy Nexus update on the horizon. In fact, they said it would be here “soon,” prompting a little excitement from the G-Nex crew. What we weren’t sure about was whether or not this would be a 4.1.2 update or a big jump to 4.2.2, the current version of Android that almost all other Nexus devices are running. Thanks to a very special man with a very special version of the Galaxy Nexus, it looks like 4.2.2 might indeed be the build we see in the near future. 

It’s Friday, Friday, gotta flash ROM’s on Friday! Well, now that you all hate me for getting that stuck in your head, let’s start talking geeky ROM goodness. Today, we are featuring custom ROM’s for the Galaxy Note 2 on Verizon and the Galaxy Nexus on Verizon. 

Verizon’s Galaxy Nexus LTE is a full four updates behind other Nexus devices, that’s no secret. What we would love to find out, though, is when they plan on changing that status. And if they do, are we going to skip past all of the previous updates and jump right to Android 4.2.2 or will we be stuck back at 4.2.1 or something earlier?