yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] cdexsw:
4.2 is/has been released to AOSP. You can wait on vzw.... but our talented devs will have ROMs based on 4.2 out way sooner than one could speculate about vzw. Custom and stock flavors to your liking soon :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Smokeey:
Does it matter? If you made the account here you might as well root.
[Samsung Galaxy Nexus] Eddog4DROID:
The Dev's here I believe had 4.1 on the Verizon Galaxy Nexus about 2 days after it was released.
[Samsung Galaxy Nexus] binglejellsx2:
I just saw a 4.2 AOSP ROM posted on the "other" site. There aren't any linked GApps included though, so there might be a few things missing until a new package is created.
[Samsung Galaxy Nexus] PoXFreak:
Yes, and the OTA hit the Nexus about 8-10 weeks after some of the first "usable" firmwares started rolling out from developers, especially CM10, which devs jumped on fairly quickly.

My question...

How soon from release will AOSP become usable firmwares that devs can release to the wild?

You would think it would be fast, but I beg to differ. One compound word........ Roadrunner.
[Samsung Galaxy Nexus] dcowboys2184:
Source is being pushed anyway I'll just wait for that
[Samsung Galaxy Nexus] Big ZD:
It took Verizon approximately 2 months and 14 days to start OTA'ing 4.1. So my guess would be...January 24th.
[Samsung Galaxy Nexus] BackInA88:
I loaded up MMuzzy's 4.2 a few hours ago and so far it's running fine.
[Samsung Galaxy Nexus] Winesnob:
I toss out Christmas. Maybe the candy cane was Google's forecast of Verizon's approval time frame for 4.2.:D
[Samsung Galaxy Nexus] puothy:
February 14th. Running Pure Android and it is very good once I used MMuzzy's GPS fix.
[Samsung Galaxy Nexus] I Am Marino:
I say January or February.
[Samsung Galaxy Nexus] LaWolfe:
Yes please to that! I am also a Verizon GNex victim and was thinking the same thing! I'm switching to T-Mobile and getting a Nexus directly from Google from now on...when I can afford it. This Verizon behavior is too much violation for me.
[Samsung Galaxy Nexus] esilac:
March sounds like a good estimate, it's sad. I contemplated leaving them too.

Instead for now though, I just went and unlocked/rooted/flashed MMuzzy's AOSP rom and it's rock solid. No more waiting.
[Samsung Galaxy Nexus] oldblue910:
We will see the update, but since Verizon is sunsetting this phone, I expect it will go the way of the other "Nexus" device Verizon had...the Motorola Xoom. Once a device becomes a non-priority at VZW, basically they'll test the updates whenever they get around to it, thus the updates take longer to test and approve than they used to. Sadly this is what happened to the Xoom. The Wi-Fi version got 4.1.1/JRO03H in July and its final update to 4.1.2/JZO54K in October. The Verizon version is still on 4.0.4/IMM76L and Motorola doesn't expect Google's 4.1.2 OTA to be approved by Verizon until some time in Q1 2013.

That said, the Galaxy Nexus almost certainly sold exponentially more units than the Xoom did, so hopefully that means the Galaxy Nexus won't become quite that much of a bastard child. Time will tell.

With all that in mind, Vegas currently has the over/under on a 4.2.1 OTA at February 1. I'm taking the under. I say mid January... assuming Google can cool their jets on the update schedule. If a 4.2.2 OTA comes out before Verizon approves 4.2.1, our wait counter starts over. That's why the VZW Galaxy Nexus never got 4.1.2/JZO54K or 4.2/JOP40C. They came out too fast. 4.1.2 came out in October, followed by 4.2 in mid November, followed by 4.2.1 two weeks later.

I wrote a blog post on the subject of VZW Gnex updates last week. You can view it here. http://www.randomphantasmagoria.com/myths-about-android-updates-on-the-verizon-galaxy-nexus/
[Samsung Galaxy Nexus] Winesnob:
Maybe Verizon nexus owners will see 4.2.2 first on this round. Wouldn't surprise me to much, since the testing team tends to get a lot of subtle tweaks made (we are on JRO03O and not version C like the takju/yakju variants). At worst someone should be leaking some version in the coming weeks.
[Samsung Galaxy Nexus] oldblue910:
Google
[Samsung Galaxy Nexus] mechapathy:
Google's.
[Samsung Galaxy Nexus] kake:
another quick question, may be a dumb one. but do the updates have a specific url on the servers where we could download them or is there a process where your device id is sent in order to unlock it and let it be downloaded?
[Samsung Galaxy Nexus] oldblue910:
They have a specific URL but we have no way of knowing what it is until someone gets the OTA and provides us with the URL.
[Samsung Galaxy Nexus] Beauenheim:
My apologies if this has already been posted on this threat but it seems your update is imminent.

http://www.androidpit.com/verizon-galaxy-nexus-android-4-2-2

At least from the article. Verizon users rejoice!
[Samsung Galaxy Nexus] Winesnob:
From Google after Verizon gives approval.

---------- Post added at 09:55 PM ---------- Previous post was at 09:50 PM ----------

Just reading this http://www.theverge.com/2013/3/4/4061824/android-4-2-for-asus-transformer-pad-available-today and remembering that 4.1.1 rolled out for the Asus transformer before the Verizon GNex was updated. Depending how quickly Verizon pushes this one, the Transformer may win again.
[Samsung Galaxy Nexus] locofocos:
Alright, I think I have the solution to all of our problems, lol. We know what the URL will look like, since they follow a pattern (see http://xdaforums.com/showthread.php?p=20843237). Assuming we know the build number and device model, there are only 20 hex digits that change. We just need a brute force wget attack! 16^20 gives us 1208925819614629174706176 possible URLs. If we could only try 1 URL per second, that gives us about 38334786263782000 years. But 1 URL per second is pretty measly, even for a single device. Let's say we could gather the collective armies of XDA, Rootzwiki, Android Central, Droid Life, and Droid Forums and every cellular data/wifi connection at their disposal. Scratch that. I'm being optimistic. Let's suppose every android device ever activated joined our forces, and we had a force of 190 million strong (http://en.wikipedia.org/wiki/Comparison_of_Android_devices). It would only take 201.8 years! But that's still a conservative guess, because even the slowest of 3G connected G1's could produce, what, a few dozen connections per second? Considering the adoption of 4G networks and the miniscule size of an HTTP get request, I'll make up a reasonable number and say we could perform on average 2018 connections per second per device. And that brings the total down to... 1/10th of a year! 36.5 days! If we start today, we could have the OTA update URL by April 9th!!!!!!! What are we waiting for, my comrades!?!?!?!?!

(completely joking, for those who might not have realized. This would crash Google's servers. Although otherwise the math does check out)
[Samsung Galaxy Nexus] Winesnob:
I had actually thought about this tactic a few months ago, but didn't do the math nor have the know-how to launch such an attack. While I get that you're just kidding, if someone did pull it off, it would still be faster than Verizon.:D
[Samsung Galaxy Nexus] slagg3r:
You can always have him do this 20x

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.

it does work just takes a little
[Samsung Galaxy Nexus] oldblue910:
Just so you know, that "trick" breaks the Play Store temporarily and also breaks push notifications in apps.
[Samsung Galaxy Nexus] trparky:
I just want the radio firmware. Maybe then these God forsaken radios won't drop a phone call whenever a squirrel in my backyard runs around the tree.

And don't tell me to either chop down the tree or shoot the squirrel. LOL
[Samsung Galaxy Nexus] crookedview:
Alright, then chop the squirrel and shoot the tree!

I get a lot of complaints from people that I talk to on my Gnex that my voice sounds muffled or like I'm in a tunnel, so hopefully the radios fix that. Probably a hardware issue, but one can hope.
[Samsung Galaxy Nexus] techspecs:
HW issue. Sorry to be that bearer of bad news.
[Samsung Galaxy Nexus] trestevenson:
I'm eagerly awaiting that release!
[Samsung Galaxy Nexus] Flapjack:
I've learned to expect, from one device to the next, that new radios never seem to solve the issues I want them to.... and usually present new ones as well. I can't think of one device (at least three back) where the latest radio was the greatest. I've always had one a few versions back.

I'm not holding my breath, but I would be pleasantly suprised if this one turns out to be different.
[Samsung Galaxy Nexus] ironside2011:
Not really sure but I'm gonna say Verizon
[Samsung Galaxy Nexus] mechapathy:
The updates come from Google. Refer to this thread: http://xdaforums.com/showthread.php?t=1419170
[Samsung Galaxy Nexus] :
I don't have these issues and I live in backwoods Alabama where no other carrier has reception and there is a plethora of trees and squirrels. :confused:
[Samsung Galaxy Nexus] JHadley:
Not that I'm complaining about the wait, or saying that this isn't real..but I'm really surprised that no one else has seen or heard about this update. You'd think there would be at least one other test phone out there in the hands of someone that frequents these forums.
[Samsung Galaxy Nexus] oldblue910:
El Madhatter has provided OTAs a month or more before a public OTA in the past. He provided us JRO03O 4.1.1 a month prior to release. He has a Verizon Galaxy Nexus, but his phone is one that was, at one point, used for testing inside Verizon. He has posted pictures of his phone...it has a serial number etched above the earpiece. Because of that, when a potential update is released to testing, his phone gets the OTA whereas 99% of us don't. If the OTA gets approved, only then will we actually see it. Somehow, he got his hands on this phone but from what I gather, he's not the original owner. But anyway, clearly that phone's IMEI number is still on VZW's list of "testing devices".

He's in a unique situation, but he's a perfectly credible person and has been providing us goodness for a while. First, he provided us the IMM76K -> IMM76Q OTA which never got released publicly (it was just an update to break the device-wide search due to patent litigation. IMM76Q shipped on new phones but never got released OTA to older phones), then as I said, he provided us 4.1.1/JRO03O a month before the public OTA. The guy is the real deal. He's just a very busy man and has a hectic work schedule.
[Samsung Galaxy Nexus] Easton999GS:
Do you think he will be willing to sell this device... i may make an offer of my own galaxy nexus, in great condition and $100-$150 for his nexus. I dont have a hectic work schedule and can do this everytime day 1.
[Samsung Galaxy Nexus] ntb81:
Well one thing has become very clear at this point: requiring root for logcat viewing is the worst feature of Jelly Bean
[Samsung Galaxy Nexus] oldblue910:
Amen to that! For the IMM76Q and JRO03O OTA updates, he had just used the aLogCat app to get the URL. Very quick, very simple. :(
[Samsung Galaxy Nexus] John Markley:
Could you not use adb logcat without root? (Have not tried it myself). http://developer.android.com/tools/help/logcat.html

---------- Post added at 02:14 PM ---------- Previous post was at 02:08 PM ----------

follow-up - I just tried it on my old not-rooted GNex (now use Nexus 4) and it gave me the log cat just fine. I use a Mac, so the command is

./adb logcat
[Samsung Galaxy Nexus] oldblue910:
Yes, the problem is he doesn't have adb drivers or the actual adb executables on his computer. He's away from his place for a while and all he has is a laptop with none of that stuff on it. That's why I need to walk him through it.
[Samsung Galaxy Nexus] John Markley:
10^9 thanks for this.
[Samsung Galaxy Nexus] GatorsUF:
I just got a replacement phone from Asurion, any chance it is a "tester" phone? Any way to check besides relocking and trying to OTA?

I am on custom ROM so OTA isn't going to come through AFAIK
[Samsung Galaxy Nexus] Winesnob:
If there is a identifying number/serial number imprinted on the face of the phone above the speaker bar, then you may well have a tester. I think we all hope for this, but doubt that you do. Would love to know how the device fell into El Madhatters possesion, but that's neither here nor there.
[Samsung Galaxy Nexus] animal24:
More specifically how it got out with a good ESN. If it was lost or damaged or a terminated employee the ESN should have been invalidated. Maybe there is a mole in Verizon. A benefactor.
[Samsung Galaxy Nexus] oldblue910:
idk Now with 4G LTE phones, that's all done based off SIM card now. They don't shut off ESNs anymore...though I suppose they could have invalidated an IMEI number so that the SIM couldn't activate.
[Samsung Galaxy Nexus] brchickery:
After watching this thread and repeatedly face palming, why not just use join.me or teamviewer take over his computer and finish this already?
[Samsung Galaxy Nexus] oldblue910:
It's a matter of him finding time to do it. He said he'll have to bum hotel wifi to do it, so I'm really at the mercy of his schedule, no matter what solution we employ in the end.
[Samsung Galaxy Nexus] ntb81:
Verizon didnt make clear that the full "Google Experience" could involve everyone depending on one guy to pull the latest version of Android from a single phone
[Samsung Galaxy Nexus] Easton999GS:
He can't use 4G?
[Samsung Galaxy Nexus] sirgoob:
What's a couple more days when vzn made us wait over 3 months
[Samsung Galaxy Nexus] oldblue910:
I'm done posting in this thread until I actually have something useful for you guys. I'll get it to you as soon as I can.
[Samsung Galaxy Nexus] Winesnob:
Patience young Skywalker. Demanding you are. Solution will present itself in due time.
[Samsung Galaxy Nexus] gkaurin:
Well said
[Samsung Galaxy Nexus] marnett2005:
I can't help but feel like everyone is being exceedingly demanding here. I've seen a number of posts complaining about how long this is taking, when none of us know what this guy's schedule is like. I'm excited the same way as all of you are, but I'm not going to sit here and demand that this man alter his day and his life so I can install something on my PHONE. Y'all need to calm the hell down, we'll have it soon enough.
[Samsung Galaxy Nexus] scarsofthumper:
Well said.

He's doing everyone here a favor by trying to get an OTA URL for all of us. He doesn't have to do it, so the fact that he's even willing to do that favor for us in his schedule he gets my everlasting thanks.
[Samsung Galaxy Nexus] animal24:
Shucks you're right. Maybe they can't do that anymore...
[Samsung Galaxy Nexus] El Madhatter:
Going live with oldblue910 in five...
[Samsung Galaxy Nexus] JHadley:
I just came
[Samsung Galaxy Nexus] oldblue910:
I'm waiting by the phone. :D
[Samsung Galaxy Nexus] Adartilth:
YAY! =]
[Samsung Galaxy Nexus] kake:
well.... im pumped:D
[Samsung Galaxy Nexus] ironside2011:
Good luck!
[Samsung Galaxy Nexus] kake:
so to get this clear hes already downgraded and is attempting to upgrade again correct? sorry if this was already posted.... but im not reading though 200 posts to find it haha:D

and by the way El Madhatter, thank you for doing this!
[Samsung Galaxy Nexus] ntb81:
I think the same could be said for everyone on this thread :D
[Samsung Galaxy Nexus] JHadley:
I think at this point El Madhatter has recieved and unzipped the files that oldblue910 sent to him. Oldblue910 is going to run him through flashing the factory 4.1.1 image and then see if he recieves the 4.2.2 update message again. Could still be a while depending on El Madhatter's set up. I've got my fingers, toes, legs, arms and eyes crossed that this works :good:
[Samsung Galaxy Nexus] kake:
thanks for the reply, im about the same way right now.:highfive:
[Samsung Galaxy Nexus] ironside2011:
Me too
[Samsung Galaxy Nexus] veritas718b:
waiting patiently but the computer. been following this since I saw the threads start! keep up the amazing work guys
[Samsung Galaxy Nexus] cms5423:
What if we were just getting Te'o-ed right now haha

(just a humorous thought)

anyways, can't wait to see if this works out :D
[Samsung Galaxy Nexus] ntb81:
Just a question while we are all losing it in anticipation...

I am, like everyone else, seriously excited about getting this ota. I am excited for the 4.2 features we're getting, but then again we've all had them for months now. Really, at the end of the day, like others, I am mostly looking forward to the new radios.

But I'm not sure why. The first set of radios we got out of the box were awful. So bad that I was just about to return it and save my upgrade for the S3. But then things got a bit better with the first 4.04 leak, much better with the final 4.04 radios, and really since 4.1.1 I've had absolutely no reason to complain. But still I can't wait for the new radios. Does this sound familiar to anyone and if so can someone explain to me what I am excited for?
[Samsung Galaxy Nexus] JHadley:
HAHA, I've thought about that too...would be pretty hilarious
[Samsung Galaxy Nexus] open1your1eyes0:
Even if you had perfect radios. Newer radios could always increase speed and/or shorter 3G/4G handoff delay. Who wouldn't want that? ;)
[Samsung Galaxy Nexus] kake:
now that you put it like that im not sure what there is to be excited over for you(not being a smart a**, just saying) but for me the battery life on stock is wayyyyy better than any custom rom out there with a custom kernel. dont know why but thats how it is on mine. and secondly i cant wait for the radios.... i have the radios that came with 4.1.1 and they are AWFUL.... i dont see how people say they are good. i had better luck on the 4.04 radios.
[Samsung Galaxy Nexus] ynksbsbll2:
I think Barney's Stinson's one rule sums it up: https://www.youtube.com/watch?v=x7_KFazcb3w
[Samsung Galaxy Nexus] ntb81:
See, that's interesting. I've had the exact opposite experience with the radios. Though I totally agree slot about battery on stock
[Samsung Galaxy Nexus] wavedashdoc:
I think the updated radios affect depends on what hardware revision you have and where your phone was made. My first GN was made in China and had the radio revision 10 at the end. This particular unit was not able to stay connected to 4g for more than 3 min, constant drop calls and what not. Returned the next day. Second brand new phone was made in Korea and had the revision 09. And with every radio update since it's had better battery life and no signal loss. Now I could just be speculating but that's my 2 cents.
[Samsung Galaxy Nexus] veritas718b:
for some reason (but i think its just my area new england) when I switch to a 4.2 rom i get weaker signal but when i switch back to a 4.1.1 or 4.1.2 rom i get full 4g no dips into 3g. i'm running a 4.2 rom and where i am i used to get 3 bars of 4g but now i just have 2 of 3g
[Samsung Galaxy Nexus] kake:
im not sure. ive flashed back to stock 4.1.1 like 2 times(cause im a rom whore) so can you have a "bad" radio flash? ive never heard of it but anything is possible on these things
[Samsung Galaxy Nexus] JHadley:
My first GNEX was HW version 09 and it constantly dropped the full signal. My CLN replacement is HW version 10 and most radios have worked very well. There was one set of "leaked" radios though that had my data bouncing between 3G and 4G constantly. It was a battery killer! All of the official radios have been great. We have to remember though that while it's likely this combo will be what Verizon approves, they could still change a few things before we get the official OTA.
[Samsung Galaxy Nexus] tiny4579:
I've posted about why this is a while back when 4.2 first released. Looking directly at the code, it's just a change in how they report signal. The actual dBm, which what should be read when testing signal, didn't change from 4.1 to 4.2 but only what signal ranges were assigned a certain number of bars and how the number of bars were calculated from signal.

In short, the signal didn't change from 4.1 to 4.2.

Not sure how 3g/4g handoff would be affected. That should only be controlled by the radio firmware and nothing in the ROM.
[Samsung Galaxy Nexus] Flapjack:
I've had the best luck with the FA02 radio. It's the only one where hands-free bluetooth calling has been usable. The newer radios have a warbly screechy sound in the background... like electromagnetic interference.
[Samsung Galaxy Nexus] veritas718b:
I figured maybe there was something within the rom making it funky because my friend running cm10.1 was getting atleast 1 to 2 bars more then me and were on the same network and same 4.2.2. but it was just an observation.
[Samsung Galaxy Nexus] kake:
i guess this thread stalled out until we get word from oldblue or el madhatter:confused:
[Samsung Galaxy Nexus] animal24:
Yup. Maybe in the morning. I just hope its before work.
[Samsung Galaxy Nexus] JHadley:
El Madhatter mentioned in his other post about a half an hour ago that they were having some driver issues.
[Samsung Galaxy Nexus] kake:
i was hoping to get word tonight. but what can you do. your on their time right now. not complaining just saying.
[Samsung Galaxy Nexus] JHadley:
I'm gonna call it a night, have to get up early in the morning. Thanks for the continued efforts gents...they've been on it for nearly two hours now. Sounds like the environment is less than ideal, so I'm sure they're getting pretty frustrated. We all really appreciate it!!!
[Samsung Galaxy Nexus] GohanBurner:
Yes, I can't wait until I can try out the new radios! Thanks so much El and Old! You guys are awesome!
[Samsung Galaxy Nexus] Frixtion:
If you haven't tried mskip's galaxy nexus toolkit and are on a windows operating system it installs drivers http://xdaforums.com/showthread.php?t=1614827
[Samsung Galaxy Nexus] JPBeard21:
Here are the drivers for windows, the Samsung exe has regular drivers and the USB driver zip has the bootloader driver. In bootloader mode, you will see an android 1.0 device without driver, just update driver manually pointing to unzipped files. It will say unsigned driver, u just have to proceed anyway. Links:

https://www.box.com/shared/2bmyonqbbb6zh1vznutp

https://www.box.com/shared/oui7wqlb22d0tn9oobim
[Samsung Galaxy Nexus] oldblue910:
El Madhatter and I are on the phone. I hope to have an OTA link in the next 20 minutes.
[Samsung Galaxy Nexus] Frixtion:
Where were you an hour ago.. You sure one uped me
[Samsung Galaxy Nexus] Adartilth:
My heros!
[Samsung Galaxy Nexus] veritas718b:
is this a link we all can receive?
[Samsung Galaxy Nexus] ironside2011:
May the Android gods be with you!
[Samsung Galaxy Nexus] oldblue910:
Yeah we finally got that sorted out. He's flashed back to 4.1.1 now.
[Samsung Galaxy Nexus] AuroEdge:
Is the OTA like the factory nexus images at https://developers.google.com/android/nexus/images#mysid?
[Samsung Galaxy Nexus] animal24:
So now we just wait for the update to appear and log cat to get the URL? Wonder if the clear framework trick will work
[Samsung Galaxy Nexus] open1your1eyes0:
Nope, it should be similar to this thread.

It's just an OTA update and not a complete image. That has to be provided/uploaded straight from Google.
[Samsung Galaxy Nexus] mwalt2:
It will be a link just like the ones in this thread. It will be a .zip that can be applied in recovery to patch your system to the newest version (probably set for JRO03O to JDQ39).
[Samsung Galaxy Nexus] oldblue910:
Ladies and gentlemen, thanks to XDA forum member El Madhatter, I present you the JDQ39 from JRO03O OTA file for toro:

http://android.clients.google.com/p...6.signed-mysid-JDQ39-from-JRO03O.5939ff98.zip
[Samsung Galaxy Nexus] mechapathy:
Woooohoooo! Thank you both!
[Samsung Galaxy Nexus] open1your1eyes0:
Big thanks to all the time you spent on this guys! Beats waiting for Verizon to chime in. ;)

Now we can finally be up-to-date. :)
[Samsung Galaxy Nexus] oldblue910:
I've decided not do dump radio and system images. I spent 2 hours on the phone with him trying to fix driver problems, etc. I'll let someone else dump the radios.