Share this Story

It’s Official: Verizon Announces Android 4.2.2 Update for the Galaxy Nexus

galaxy nexus radios

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!

Here is our first look at Android 4.2.2 on the Verizon Galaxy Nexus:


Via: Β Verizon

  • AndroidPBC

    Galaxy Nexus no longer connects with HANDSFREE profile in car after 4.2.2
    installed. Anyone have a solution? Anyone else having same problem?

  • Thomas Fogle

    I use my mobile hotspot on my android galaxy nexus to play on Xbox live. Last night I was on Xbox live just fine, I got offline to go to bed and then my phone got the new update I wake up today and I can connect my PC to my hotspot just fine,but my Xbox 360 slim will not connect anymore. The Xbox still shows that my network exists under the wireless connection setting but it refuses to connect wirelessly. However I can connect to Xbox live when I bridge a LAN network from my computer to my Xbox via Ethernet cable. Someone please I beg you read this and help me connect wirelessly to Xbox live once again.

  • Henry Babcock

    Just got it. Second try force stopping & clearing cache of Google services framework and checking for updates did it. Did a reboot in between for good measure, dunno if that helped. Was not on WiFi, just very slow 3G.

    I will see about battery life later, but immediate good news: PdaNet+ with paid Foxfi Key WiFi hotspot still works! Typing this through my Nexus7 tethered right now. (I know a WiFi tether app isn’t probably necessary on the G.Nexus but I already paid for it for my old S3, which it only sorta worked on after Jellybean btw, but works flawlessly on the G.Nexus.)

    AND, so far signal seems improved, although actual dBm is exactly the same, here at home. I only have very weak 3G signal here and only that with an elaborate amplifier & external antenna setup (-93dbm). No 4G. Before this update I would typically get 0.2 Mbps down and under 0.1 up, now I just got 0.47 down, 0.12 up. A very good improvement for me, and roughly in line with what I got with the S3.

    If signal improvement holds up in town, one negative in going with this phone from my S3 will be gone. Bad batterly life I assume I will have to live with. And certainly the lack of SD card. _Everything_ else, I prefer the G.Nexus to the S3. And I pocketed over $300 difference selling my S3 and getting this G.Nexus on Ebay, to save towards the next great Google phone on Verizon, hopefully the Xphone.

  • Anthony Saylor

    I got the update, but now my Google play won’t let me download anything.. Anyone else having this issue?

  • Melissa A. Polk

    uptil I saw the receipt of $6570, I be certain that…my…
    father in law had been realie earning money in their spare time on their apple
    labtop.. there uncle haz done this less than 6 months and at present repaid the
    mortgage on there place and bought Lotus Elise. this is where I went,
    jump15.comCHECK IT OUT

  • jerry13

    I got a different phone months ago. My gnex is a video game toy for my friends 6yo.

  • BigDaddyBioShock

    anything good happening in texas?

  • Bryan

    I am curious to know how the latest updates have been for the Verizon GNex. Have they improved the radios or battery life?

    I had a GNex and loved it, except for the poor reception and battery life. I could barely get over an hour of screen on time before my battery was low enough I couldn’t go out for the remainder of the day without charging first. And the reception and constantly losing 4G was an issue.

    I replaced it hesitantly with a Razr MAXX and having 3-4 hour screen on time with good reception was a revelation. I also giggle a little knowing that I had a newer version of JBean even if only for a few months (Xmas leak).

    But, I still always wonder if I had waited it out if those issues would have been fixed.

    So GNex owners, have the updates fixed these issues for you assuming you had them?

    • I’ll let you know after I get the update.

    • Jeff

      So far the battery seems to be holding up better. Took it off the charger around 6:15 and as of now still have 72%. Haven’t used it much in the 6 hours but before the update it would have been around 50%.

  • Jeff

    Just pulled my update. Update is 88.8 MB

  • Michael Lewis

    Meh. If you’ve been on Verizon and not rooted your phone, than you either are not tech savvy enough to know how to do it, Don’t care being releases behind, like the bloatware or you are simply lazy (in a bad way). You should have rooted your Verizon phone ASAP, making this bit of news OLD!

    • rooted != flashed. “tech savvy” indeed.

      Also, several of the “stable” roms had dealbreaker bugs (bluetooth, etc) that actually matter. And furthermore, the flash+restore-settings process is a tad different than the OTA-update process, in terms of disruptiveness.

      There are completely legitimate reasons to want the actual Nexus-update experience.

    • Ian

      shut up

    • Artune

      There’s nothing wrong with wanting to be on the official OS from google, I could get into rooting but don’t see the need to, benefits don’t appeal to me. Doesn’t mean you should knock people for it.

    • umataro42

      I root so I can use root-required apps, but I don’t flash any ROMs because I prefer to keep stay stock, so I’m still on 4.1.1. I’m only one release behind (not “releases”), so I don’t fall into any of those categories. But that’s the beauty of Android, you’re more free to do what you want with it.

  • I looked at calendar and thought it must be April 1st.

  • This was actually pretty damn fast for Verizon. JDQ39 came out for the GSM models on February 12. Today is March 19…a little over a month. That’s the fastest the VZW Gnex has ever seen an update.

    • geedee82

      Yeah but they were already 3 updates behind by the time 4.2.2 came out.

      • Blame Google for that, not Verizon. Google never released 4.1.2, 4.2, or 4.2.1 to Verizon for testing. If it had, the same guy that leaked 4.2.2 would have informed us about it.

  • Shawn Phelps

    What was that method to delete system settings cache or something to force the update?

  • I wonder when my Galaxy Nexus will get the update to 4.2.2, because early Friday morning I just got the OTA for JB 4.2.1. I am in Canada by the way, so Verizon isn’t here.

    • You have a GSM model running a Samsung-maintained software variant called “yakjuux”. That 4.2.1 update came from Samsung just recently, so who knows when you’ll get 4.2.2. Your updates, sadly, don’t come from Google. So, once Google releases an update, Samsung takes it, makes whatever changes they have to make, and then release it. Normally 1-2 months after the fact. In this case, if you just got an update to 4.2.1, don’t expect 4.2.2 until at least May.

      • The funny thing about that is that Samsung said we’d be getting the 4.2.1 update around November, it’s now almost 4 months later…seems Samsung is pulling a Sony.

  • Tom

    these updates just keep rolling out today. just got 6.0.1 Lard

  • Tom

    I got the AOKP for Key Line Pie. Let me know if you all are interested.

    • geedee82

      Key lyin’ pie…

      • Tom

        fu prick

  • Kristy

    Hey!! I just got the update too!!! So in love with it <3 <3 <3 4.2.2 here I go! =D

    • What state are you in and were you on wifi?

  • joejoe5709

    Wow. I’ve nearly forgotten what stock nav keys look like. I’ve been using PIE for far too long. Lol. That giant black bar at the bottom is actually very ugly when you’re used to a large screen.

  • umataro42

    I’ve waited this long, I can wait a little longer to make sure the currently available download is the “official” release. And after reading about some of the issues people had with 4.2.1, I can’t entirely blame Verizon for holding off until 4.2.2.

  • jessie

    just got the update – new york

    • City? I’m in Buffalo, going to check the wife’s phone tonight!

      • Jessie

        Long Island, Suffolk County.

        • N

          no luck yet, nassau.

    • Abgar Musayelyan

      can you confirm the build number, baseband and kernel versions?
      just want to make sure everything is still the same.

    • Were you on wifi?

  • hyperbolee

    maybe someone can help me – i’m on Mmmuzzy jellybean Rom right now – when the OTA update comes through would it be OK to accept it if i want it? My wife now has my GNex and I think it’s better if she’s not on a custom ROM, but i’ve never thought about what would happen if she accepted it.

    • If you’re on a ROM, you won’t get prompted for the update. It checks to see if you’re still stock first.

  • NorCalGuy

    I wonder how many people who have a GNex have not unlocked and rooted it. Not saying that every one has to do it or your stupid but just wonder what the split is.

    • I was going to do it way back when I got it for wireless tethering, but FoxFi was working at the time so I didn’t need to bother. I was about to do it for the leaked 4.2.2 package but I’ll wait for the official OTA now. I think this will probably be the last update VZW puts out so I’m thinking I might want to unlock and root after this update and really learn more about roms, etc.

      • Tim242

        Unlocking should be the first thing you do on a Nexus. The main reason is because it erases everything on the phone. You can be unlocked and still get the updates.

        • When the phone first came out it took I feel like it took a while for the unlock and root stuff to come out so obviously you have to start using the phone, and then you don’t want to wipe your phone, so I never did it. If I could find a way to reliably back everything up, unlock, and put everything back on, I’d do it.

          • Tim242

            Nexus phones are unlocked by ADB fast boot OEM unlock. So, you can do that as soon as you get it. I never had unlocking wipe any other phone. I think it’s just the Nexus. If you don’t have a Nexus, you should be OK. Just check the info for your phone.

          • Bryan

            You can use the ADB backup feature to back up all of your app data. That’s usually the biggest pain – losing all of your game progress, etc. Then after unlocking, you can use the ADB function to restore the backup. You’ll still have to set up some stuff, but you won’t lose nearly as much doing it this way.

          • What do I use to do that, or how do I go about that? I’d love to do it, just to get it out of the way, even if I still wait for the OTA update?

          • Bryan

            You need to have the Android SDK installed on your computer. I did it from a Win7 64 bit machine when I had the GNex.

            Then follow these instructions from one of these sites. I don’t have any affiliation with these sites, just found them with a google search.



            Installing the Android SDK


    • I rooted/rom’d right after getting my gnex. Left it that way for probably 8 months or so. Got tired of flashing routinely, dealing with random issues, etc. So I went back to stock once GNow was sent out by Verizon. Haven’t looked back. Really, as long as its vanilla Android, its perfect for me.

    • Eye4Detail

      My rule has been simple: As long as my Nexus gets the major releases before my Infinity, I’ll leave it bone stock. The first time Asus beats Big Dread to the punch, my Nexus is getting the full unlock/root/ROM treatment.

      I’m probably not as impatient as most though, as I have other Androids laying around rooted if I want to play with ROMs. It isn’t as important for my primary phone.

      • NorCalGuy

        I ran my nexus 7 for a while stock and it was cool but I just enjoy all the customizations you can do while rooted and my GNex gets every little mod ported over and being a flashaddict I just can keep from getting them all

        • Eye4Detail

          I’ve been having my fun lately playing with Android x86 on a Lenovo Ideapad S10-3T. Not the smoothest experience (pre-butter 4.0) but it’s fully functional and it’s cool being able to pop an SD card into my little net-vertible and turn it into a full-on Android tablet-PC. Reminds me, I’ve gotta go check how they’re progressing with the Jellybean build.

  • I’ve been running 4.2.2 since this weekend thanks to adb sideload. Very nice to not have to unlock, root, etc. Also no lost data.

    I will say I’ve run into a little bit of bugginess. The biggest thing is that six apps (out of 180) somehow became corrupt and were no longer installed. Re-installing from Play Store fixed them, and some kept their data while others didn’t. I also tried backing up my phone with Carbon. Things went smoothly for awhile (despite my large number of apps). Eventually, however, I started getting strange behavior from the phone. The status bar at the top and the on-screen buttons at the bottom kept disappearing and reappearing. The phone went to sleep and wouldn’t turn back on. Let it sit for a bit before finally pulling the battery. This could be an issue with Carbon, but I tend to direct some of the blame at an OS that can’t intercept an application before the entire device has a “meltdown.”

    The other issues are minor cosmetic quips. The carrier name shows sometimes and not others when looking at the notifications. I’ve had apps that usually show up in recent apps not show up or have a delayed response (not show up for awhile and spontaneously show up later on). I’m not sure if this is a bug in DashClock or the OS itself, but I’ve had finicky behavior on the lockscreen as well. It is rare, but I’ve had it not show any extensions. That or the extensions get stuck at the top even though the pattern unlock section has been lowered. Again, I realize these are minor issues, but the whole experience gets changed when you run into enough of these and you start to question where the next issue will pop up. You start to subconsciously question the reliability of the device. It also reminds me just how stable 4.1.1 was on my phone and how solid that update was.

    I’ll be curious to see if similar things are noticed by others. I also wonder if the same version that was leaked goes out to everyone now. I am enjoying the new lockscreen, quick access to settings in notifications, etc. I also dig things like the new clock font that is used in several built-in apps/widgets. There are tons of tiny tweaks throughout the OS that will most likely be ignored by those not as OCD as me (they put a colon after “Draw an unlock pattern” when you set your pattern!)

    • Tim242

      I tried Carbon. Titanium Backup is much better.

  • Radgatt

    The second I get rid of this phone is the second the update finally arrives. You all are welcome lol

    • Eye4Detail

      Oh, it’s greatly appreciated!

  • Drummer62

    Where exactly did Verizon announce this? I can’t find anything on their web site.

  • Mallahet

    Guys, you’re just under 2 weeks off of April Fool’s. Are you still on the Mayan calendar?

  • Karl Wooster

    Now just to wait for it to hit the s3!

  • Randie Rosa

    Has anyone received the update? How is it behaving? I was such a fan of BB and since he’s left I only come across buggy ROM’s. The only reason I even rooted was fit the JB update. Can anyone also offer a near stock, near bugless ROM.

    • jelly belly, mmuzzy vanilla, shiny(non root only)

    • Just go back to stock. I did that months ago and overall happier. ROMs were all good and such, but they all came with something one way or another. Simply too much effort to flash all the time.

      In reality this update wasn’t that far back as its only been a few weeks since 4.2.2 launched and the previous builds had issues from Google. So, I’m better off never getting them.

    • Mowgli73

      Former BB fanatic here as well. I recommend MMuzzy Vanilla ROM. Outstanding and stable.

  • Cory Parker

    Can’t wait to use photo sphere in Met Life Stadium for Wrestlemania

  • As an unrooted/un-romed GNEX owner, this is good news but I think after I update I will root and unlock – chances are this will be the final update VZW provides and I’d like to be as current as I can while I still have the phone.

  • Does anyone else thing verizon is doing this because they made a deal with Google to have a next nexus on their network?

    • I would certainly hope so.

    • Tim242

      No. Verizon doesn’t want another Nexus.

      • Tirionfive

        So sure about that? They sure do love that Chromebook Pixel.

    • Verizon didn’t realize what they were signing onto when they got the exclusive launch on the Nexus, they just thought it was the new big thing and they were gonna get it first.
      They thought they could sneak in the bloat and lock down the bootloader but Google gave them the smackdown on that, so they just quietly launched it to get rid of it and instead advertised the hell out of the first RAZR.

      Of course, I would love to see what happens if/when a Motorola Nexus materializes, since Motorola has seemed to be Verizon’s favorite child of the bunch.

  • now the process of “settings->about phone->check for update->be disappointed->wait 10mins->repeat” begins….

    • Anthony Saylor

      Does this actually work? im a skeptic on the whole thing
      EDIT: sorry i was thinking of the whole “clear Google Services Framework” thing

      • Hasn’t worked for mine yet…

      • mondeca

        It has worked for me in the past. I haven’t tried it yet because I’m not sure that the roll-out has actually started. I also wasn’t sure if there was news that I missed that Google nerfed that method.

  • Guest

    Yawn… Sorry, just teasing you Nexus folk.

  • mondeca

    Anybody know if the “clear Google Services Framework” trick still works to force an update?

    • what’s this evil magic?

      • You used to be able to do the following:

        1. From your phone, head into Settings>Apps>All.

        2. Search for Google Services Framework.

        3. Once found, tap on it and choose β€œForce stop.”

        4. Then choose β€œClear data.”

        5. Back out of Apps to your About page in Settings and check for the System update.

        You may have to repeat the steps a couple of times. Good luck!

    • NBJake

      It worked for me. Updating now in NY

  • Is it me or has Verizon been pushing out a lot of updates lately? Maybe they are starting to get on the ball here????

    • Havoc70

      One can hope, but i highly doubt it

  • Wtf about the Rezound?


      Reasons to not buy the DNA and the One if they get it.

      • Exactly why I’m jumping to a Galaxy S4

        • Tirionfive

          A wise move. HTC is ALWAYS to blame. I had that hunk of brick they call the rezound… Never again.


    There’s more popup ads on DL than ever

    • Austin Warren

      Gotta have money to keep the site alive

    • They should ask for some donates, i’m sure many people would donate.

      • michael arazan

        Droi-Life-Pro.com a subscription service with no ads, buy a year membership and get their apparel for free

      • KOBALT

        I would!

    • J. Gilbertson

      Popups? I aint got no stinkin popups. Just adds on the side. You should stop looking at porn /s

      • Your sidebar can add? Impressive.

        • J. Gilbertson

          haha oops… ads

      • KOBALT

        You’re SO RIGHT! I might as well throw my degree in computer science out the window because you obviously know how to use a PC better than I. Thank you, sir.

        • J. Gilbertson

          You mad bro?

          • KOBALT

            Furious! >.<

  • Austin Warren

    Dear Jesus. Its a miracle.

  • RW-1

    And? good news for the non rooting masses though …

  • I lol’d at your “no this isn’t some sick joke”

    I felt the pain in that sentence.

  • el-R

    This post made me check my ROM status, for some reason I’m on 4.1 (JRN84D)? Is there somewhere I can download the 4.1.1 update without wiping my phone?

    • 4n1m4L

      You might be able to flash /system if you open up the factory image from https://developers.google.com/android/nexus/images

      Probably still need to wipe cache though. Oh! And flash stock recovery too. This update installs a new recovery and checks for the old

      • el_R


  • Consequence


  • schoat333

    I still have mine. Might put it back to stock, and let it update for the heck of it.

  • oaxican509

    Shame on you Verizon, its not April Fools Day just yet……

  • Abgar Musayelyan

    any way to verify that this is the same as the leaked version?

    • Still waiting for Verizon to post the support docs. Once they do, we’ll know for sure.

  • Zach Armstrong

    About time

  • randompsychology

    If that photo above is correct, it’s still running a 3.0 kernel, unlike the Nexus 4, which is running version 3.4 (or higher?) of the kernel. I think there were a lot of improvements since 3.0, and I was really hoping for a newer kernel. :-/

  • Tirionfive

    All these comments. I understand people are mad at verizon, but you have to look at it from their side. They didn’t want to release 4.2.1.. It was too buggy. 4.2.1 was terrible and I can’t blame Verizon for putting it off. Despite popular opinion, Verizon has very good QC. I am willing to wait the extra 2 months for a stable update. If you want someone to blame, Blame AOSP for waiting so long to deploy 4.2.2 from 4.2.1/4.2. 4.2 was released in Nov? right? well 4.2 and 4.2.1 were total crap. It is now march. If I recall correctly 4.2.2 wasn’t released till mid/late Jan.

    • Thing is they never spoke out as to why they never kept us up with the GSM version of the Galaxy Nexus. Verizon likes to keep its customers in the mushroom kingdom. Any attempt to guess why Verizon did what they did is just pure speculation.

      • Tirionfive

        Already stated above. QC. Verizon is very good at it. I hate phones that are buggy as hell. They aren’t looking out only for the Tech savvy, as they know we can flash to our hearts content. They have to cater to the soccer moms as well.

        • That is your statement though…they never stated it. Besides Verizon signed up for this device knowing OS updates were expected from Google directly. We never expected to be treated this way. I don’t much care as the first thing I did was unlock my phone and put Cyangoenmod on it the day I got it. But I feel bad for the others who stuck with stock from VZW.

          • Tirionfive

            They don’t have to state it. Its a given. Verizon has the best network in the US. Hands down. If you have the best network, you also want the best handsets. It’s called capitalism for a reason. And you nor I know the terms set upon by Google and Verizon. Google really wanted this handset on their network, and Verizon wanted to control it. They had to both make a compromise. Something I am fine with, because I know I can just get CM10.1 if I want the latest goodies. AT&T may be a more open network, but their coverage just can’t compare.

          • Having the best network != best customer policies. I get it you are a VZW fanboy and that is fine πŸ™‚ Everyone supports something with heart and soul which is a good thing. However in this case I just don’t agree with your assessment that we are to “trust” Verizon to make choices that are good for us. I am the type of person who wants to know why I’m told something…not just trust it is right because I am told it’s right.

            Example being VZW wont allow us to have access to Google Wallet from the Play Store on our phones. Is that to protect us or to protect their investment they have with ISIS? Sure they gave a BS answer to the FCC that Google is still searching to find a way to get through the VZW special NFC approval process…ISIS did not have any issues getting certified though. Then again VZW is pushing that…they have no vested interest in Google Wallet so no rush. This is surely not a case of VZW protecting us from the evil money stealing Google Wallet but more so of protecting them from us not using ISIS over using Google Wallet that already works in all places with NFC support. Google Wallet already has a massive footprint..ISIS does not.

            Your analysis on “best handsets” is not accurate though in my opinion… an example is the Bionic was a disaster with its dropping calls…black screen of death…not staying connected to towers for data. Before you argue, I have had 3 of them and my wife had one. I switched to my GNex and my wife switched to the Razr. Never been happier. Verizon QA is not flawless and they wont admit a problem with the Bionic.

            Point is trust is something you earn from me. As a customer I think I am entitled to accurate answers to questions. I feel that if I buy a Galaxy Nexus, and it was promised to be supported like all other Nexus’s, then I deserve an explanation as to why its not. Verizon never once stated why…they just feel we should be grateful since we have access to such a large LTE network. I honestly would leave if i didn’t pay $29.99 for unlimited data…plus having a Nexus (possibly the last one due to VZW’s attitude towards Nexus and unlocked bootloaders) means I do not have to wait for Verizon to update it and I do not have to worry about VZW telling me whats best for me.

          • Tirionfive

            I agree. Their policies are crappy. But it is the way it is. The whole Wallet fiasco pisses me off as well, but what am I to do? Go to AT&T? No thanks!

            As for the Bionic, I’ve heard slew after slew of crap about that device. I think that was more Motorola’s problem. Motorola used to be terrible till the Razr and Google Acquisition. Motorola seems to be getting much better, and headed towards an AOSP feel for their skins.

            Verizon is in it ultimately for the money, but you can’t say with 100% truth that the only reason that these devices don’t have updates are because Verizon. Verizon doesn’t act like a dumb pipe as we’d like, but they will approve a STABLE update, regardless of age (Read: Droid Inc 2 recent update).

            Verizon isn’t the one to be mad at for this late of an update. It’s Google. First of all, Google should have had more balls and told Verizon where to stick it, and they should have released a stable version of 4.2 to start with. Preferably both.

            EDIT: In response to their denial of problems with the Bionic, I agree. Verizon will lie about existing problems. Yet they have the highest customer satisfaction. I guess it doesn’t take much to beat AT&T eh?

          • Well we are starting to agree on some points which is good πŸ™‚

            However your reply states Google should have more balls but Verizon is not to blame? Who is to blame then? If Google is to have more balls then that means Verizon is being a bully…that is never a good thing.

            Earlier you stated how great Verizon’s QA is…yet they let the Bionic pass through with flying colors to the masses and promoted it as the Droid to rule them all. Then quickly pushed out the Razr then left their customers in the dark as to the stability issues of the Bionic…they still sold it as if it was a brick of pure gold.

            You state that Moto is now better that they have Google yet you state Googles QA process is not good?

            I have ran pure AOSP roms on my phone since the day I got the phone and I have not really experienced these horrible issues that would keep Verizon from pushing out an update to us. No more than any issue I have had running Verizon approved OS updates on my other Android phones/devices such as my previous Bionic’s and my Xoom.

            I think Verizon has way too many devices to maintain and they want too much control over their devices for the good of themselves, not us. This is causing significant overhead in providing timely updates to all of their devices. They should have let Google handle the Nexus, after all its their designed phone.

          • Ronaldo

            What? A rational, well thought out argument on Droid-Life without resorting to name calling or trolling????

          • Its rare i know but there are some of us on here that like to have an intelligent debate πŸ™‚ I enjoy it actually so long as it doesn’t go the troll route. That is normally when I start ignoring replies.

          • Tirionfive

            I agree. Verizon is a big bully. One of the things that piss me off about them.
            Hell even Apple couldn’t get the iPhone on Verizon first. Verizon had with tee AT&T’s report before they finally wanted it.

            As for their QA/QC for the bionic, I never said their QA was flawless. The bionic fiasco may or may not directly correlate with your last statement of having too many devices. Verizon knew that phone was DoA after all the problems people started to have. Yet verizon will lie their way though anything. Just to make themselves look better

            As for the mysterious QA of moto, I think a lot of things factor that. One being ICS/JB less buggy. Another being the the death of blur. Both of which we have Google to thank.

            As for stable roms: you have to remember these rom devs have a lot of one on one time with these individual devices to test and fix bugs. This also ties in with the last paragraph: too many devices.

            Verizon shold hire more QA people. I agree. Too many hands in everything.

          • Well i can agree to that πŸ™‚

          • Tirionfive


            I am in no way saying Verizon is flawless, but updates being solely their fault is not one of their issues. Delays, yes. They are looking out for the 99% of consumer’s interests, Not some geek/nerd/techie like me and you.

          • Jordan Harrell

            You don’t have to trust Verizon to make the choice. If you want to update to a buggy OS, you’re more than able to do that with the Galazy Nexus. But the folks that just wants their phone to work, like myself, don’t want to be updated to a buggy OS. I use bluetooth day-to-day, I would have been pretty upset if they updated me to a new version & it broke it.

        • Scott H

          Not to mention that a vast majority of customers know nothing about these updates. They don’t know what Ice Cream Sandwich or Jelly Bean are. They just want to use their phone, and to be able to rely on it. I know that’s hard to believe. πŸ˜‰

          • Vast majority of those customers bought a Droid Razr or an S series device from Samsung. Nexus owners, by far, bought the device for support directly from Google as was expected.

    • 4n1m4L

      I just wish accessibility wouldn’t break quick controls. Which it does in 4.2.2. So no light flow for me πŸ™

      • RWW

        I’m using Lightflow and quick controls in 4.2.2. (in Mmuzzy rom). Not sure what you mean.

        • 4n1m4L

          Stock it’s busted

      • triumphtriple

        Is that why it’s been like that!? The quick controls still work, but it leaves a glitching bar at the top of the screen?

    • Dain Laguna

      then explain the delay between ics and 4.1….which was massively better in virtually every way

      • Tirionfive

        Quality Control, as stated above. Verizon may be late to the game, but at least they check to make sure everything is working. 3 Months is a bit excessive, but you have to look at it from the standpoint that they have more than just this phone to check. I love Google and all, but their checking is sub-par, compared to other companies. Take the 4.2 rollout: as soon as it came out, they had to release a fix for the bugs.

        Google needs to stop the Ready, Fire, Aim strategy and check their stuff before it ships. 4.2 was a disaster.

        • So you honestly believe that the Thunderbolt’s slow ICS release was due to QC? Give me a break. Big Red doesn’t give a crap about updates. They want you to get a new phone every 24 months. By extending the life of a device with updates they see themselves shooting their own foot off.

          Regardless of “quality” of 4.2.x this is NEXUS device. Not a DROID branded device. It should be updated like one.

          • Tirionfive

            Guess what? That was HTC’s fault. HTC is terrible at updates. That’s like comparing apples to oranges. The Gnex has received over 3 updates. That’s impressive for something solely under Verizon’s control.

          • There were HTC leaks for TBolt months ago. Don’t go blaming everything on HTC. Their Droid Incredible 4G seems to be getting plenty of updates. If it isn’t DROID branded Verizon just doesn’t care.

          • Tirionfive

            Months ago? As in 2-3 months? Yup, sounds about right. It takes Verizon 2-3 months to check everything (ridiculous, I agree). Sounds like it was right on time from Verizon’s standpoint. (Not on time from an AOSP standpoint, but that’s HTC for ya)

            The Inc 4g has received 1 major update and maybe a few minor bug fixes. I haven’t followed that device closely. Once again, HTC’s deal. You can bet if the Rezound got a update from HTC, that it would be pushed out 2-3 months after the final build. This is not a carrier problem, this is a lazy manufacturer problem. (not to say that Google is lazy, it’s just that they didn’t check 4.2, so Verizon told them to get something more stable.) Verizon will decline unstable updates, something which is much appreciated outside of the tech world. The Rezound is fully capable of JB. It doesn’t have it because HTC mostly dropped support for it.

          • coolsilver

            Granted the data connectivity bugs were real and the update was much better than the leak. Verizon did keep it back… HTC was ultimately the issue.

          • zepfloyd

            Didn’t the Thunderbolt only have 768mb of RAM? Didn’t HTC say ICS would best be supported with 1gb or more (no doubt thanks to Sense)? In some ways it was lucky it happened at all…

        • Thing is this is a Nexus device…its supposed to have OS updates directly from Google…for better or for worse this was the expectation. The Galaxy Nexus was not a huge seller for VZW over all compared to Galaxy S2, S3, and Droid Razr series…I can see your argument for those devices but not a Nexus.

          • Tirionfive

            And as stated in above comments: Google really wanted this device on Verizon, and Verizon really wanted to control it. They both had to come to a compromise. This is still a nexus device. It’s openness is unparalleled by other Verizon handsets, and it has the most recent update. Sure Verizon put a minimal amount of bloat on it, and are a bit Draconian with their update cycle, but at least it doesn’t have 101 different bloat applications.

          • I would like to know from where you get your information. Verizon never stated anything like this….

            As for the bloat…there should be none at all. Just cause they put a “minimal amount” on the only Nexus they ever had does not mean we should be thanking them for this reprieve. Their update cycle is horrid for devices….Droid Bionic is still waiting for JB whereas Razr already got it. How is that fair?

          • Tirionfive

            I am not getting my information from anywhere. It’s logical conclusions and thinking alike a company business sense. I may be talking out my ass, but you can’t deny that there is at least a grain of truth. Verizon has a track record, and it’s not hard to deduce who is the problem.

            As I don’t have an explanation for the Bionic, I’d imagine that they (Moto) are still ironing out the bugs within the device. Moto might have announced it some time ago, but Verizon will continue to bounce that back till its in a working condition. As you your self have stated, the Bionic was laden with bugs. Update: upon reviewing the Bionic release date from the AP document, There is no solid release date, Just a part saying that it will get it.

            As for the Xoom: According to the document on AP, The Xoom should have the update by Q1 2013. We are still in Q1, so who knows. The Rezound was promised an update from HTC to ICS. HTC later announced Q2 2012. It didn’t hit till the first month of Q3. Verizon or HTC’s fault? Who knows. 9 times out of 10 it’s the manufacturer’s bugs.

            EDIT: and I agree about the bloat on the Gnex. It shouldn’t have any. But at least we have a Gnex, and are not stuck with some locked-down piece of crap.

          • Fair enough to the first two paragraphs…but as for the Xoom people on the WiFi version of the Xoom are loving their JB update. The only real difference between the Xoom LTE (stingray) and the Xoom WiFi (wingray) is one has an LTE radio and the other does not. AOSP based CyanogenMod 10 works just fine on the Xoom LTE (stingray) so I don’t really see the hold up other than choking through QA process.

          • Tirionfive

            Well according to the document on AP, it’s slated release is Q1 2013. Moto could still be fixing bugs, they could have held off on the update for that one or just entirely forgot about it till later. No one will ever know. Xoom Wifi was an easy case because no carriers and no radios. Add ~3 months from the initial build if it’s on Verizon. Who knows, Moto may have held off building an initial update for it till Nov/Dec. They have their hands in too much as well. Programming for radios and carriers are sometimes difficult, and time consuming. Wifi doesn’t require such rigorous testing and programming.

    • jim

      Could not agree more. Thanks for stating it. People forget that the gingerbread update went TERRIBLY for many who had the Droid X (non-rooted users). Verizon understandably is making sure the updates are stable. ( My gingerbread update went fine because I factory reset my Droid X before taking the ota.)

    • Bootleg Zani

      Your exactly right. 4.2 and 4.2.1 were horrible. Those two updates wrecked havoc on my Nexus 7 battery. 4.2.2 is the best update for Android since the original Jellybean build.

  • Kenny Larson

    Yet another reason I left Verizon and two-year contracts…

    • JoshGroff

      Yet another reason I rely on the dev community for my updates…

      • Google Nexus πŸ™‚ no effort required, half the price πŸ™‚

        • JoshGroff

          On the second hand market, the VZW variant is actually cheaper, and I’d root and ROM it either way, so it really doesn’t affect me.

          Waiting to hop off VZW until I see what’s coming out at I/O.

  • RobotiX

    dat nexus. lulz

  • sean.yesmunt

    Yawn. I’ve been running 4.2.2 AOKP since it came out.

    • pookietookie


  • Wires

    Its about time right?

  • Bastards, took them long enough, they didn’t even bother answering the 4.1.1 break in the Enterprise Wifi. I ended up Rooting and getting another OS, AND ONLY NOW THEY COME OUT WITH AN OFFICIAL UPDATE?

  • 4n1m4L

    It updates recovery. You’ll have better luck having stock recovery installed

  • [insert i’ve been on 4.2.2 for months using X rom comment]

    • sean.yesmunt

      lol. I just posted that without looking at your comment….damn.

    • Tony Allen

      [insert “It’s still not a real Nexus because x comment”]


    • Ronaldo

      [insert Rodeojones’, DDevito’s, or Tim242’s comment about how if you waited for the update you bought the wrong phone]

      • ddevito

        quit the bellyachin and root your Nexus

        • Ronaldo

          congrats to you and Rhea getting back together!

    • Dain Laguna

      [insert ‘verizon sucks’ comments. that are totally merited.]

      • Austin Warren

        It’s a nexus for a reason.

    • Hector

      Any ROMs that bring back USB Charge Only and USB Mass Storage modes? I really want those options back. MTP isn’t cutting it.

      • The only problem with USB Mass Storage on the GNex is the way the data store is partitioned on the phone, you can’t easily unmount it from the system since all the data the phone uses is mounted there.

        The only way around it is some kind of Mass Storage emulation, which is why they didn’t bother with it and went to MTP.

      • Butters

        I don’t know what your issue with MTP is, but I was having an issue where I couldn’t see the pictures that I had just taken through MTP. Using the app SDrescan I am able to get them to show up on my PC. As far as USB charging, you could get a kernel that allows fast charge and then use the app Fast Charge to charge via USB at 1A. I think that also disables MTP when using fast charge.

        • dgarcia

          I had the same problem with pics. Im gonna try that app.

    • UndergroundWire

      [Insert [Insert comment] here]

  • Anthony Saylor

    Any news if this is a “wifi only” OTA update like it was for the jump from ICS to JB?

  • moelsen8

    idiots. *slow clap*

  • motta2003

    Too late…got mine thanks to CarbonROM.

  • I just peed my pants a little!

  • ki11ak3nn

    This made my day. Thank you Verizon it only took you a million years. But better late than never.

  • maratu

    Maybe there was something internal holding up their update process that got cleared up, because this flood of updates lately just keep on churning to even the most unlikely of candidates.

    • Finally got VZ Navigator working on Cupcake! YES

  • There is a god!:)

    • JoshGroff

      If there were a God, the VZW G-Nex would get updates straight from Google.

  • wow, wonder if gnex starts getting updates faster now.

    • John

      I imagine that’ll be the last one the Verizon model officially receives

      • 4n1m4L

        I hope not, bit I wouldn’t be surprised.

      • palomosan

        Well the phone is almost two years old, I wouldn’t expect anymore from Verizon.

        • Ytrams

          It’s closer to one year old.

      • Alex

        Usually the updates stop because the hardware maker stops updating the phone. Google will keep updating the Gnex, so we’ll likely just keep seeing this phone updated a few months after the GSM version.

        If not, worst case scenario its a nexus so you can root and rom it.

      • Abgar Musayelyan

        didnt the original droid get a minor security update about 2-3 months ago?

  • LucasMonroe


  • Yoderz

    And the clouds clear to the glorious sound… Ahhhhhhhhhhhh