yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] zerocool79346:
Mmuzzy is a completely stock ROM and what of it isn't you won't ever notice. You don't have fast updates though, and never will on Verizon so your options are to continue using 4.1 which makes this thread pointless and the griping even more so, or root and ROM it.
[Samsung Galaxy Nexus] oldblue910:
Mmuzzy uses a custom kernel which is a dealbreaker for me. I get squeamish running a kernel that has been tweaked by someone who has no documentation on the hardware they're writing for. Plus, Mmuzzy has customizations to the experience. Extra settings, whatever else. I don't want any of that. I want the straight stock ROM exactly as it comes with the stock kernel with absolutely zero customizations.

If someone released a "custom ROM" compiled from source that was Android 4.2.1, but contained the exact same apps that come stock on the phone, including the VZW apps, the mysid build signature with 4.2.1 release keys (harvested from yakju or takju), the stock kernel, and absolutely ZERO user interface customizations (even leaving the WiFi-tethering check in there), unrooted, etc. I might think about using it. Basically if someone created mysid 4.2.1 while we're waiting for Google to push it out, that'd be awesome. Short of that, color me disinterested.

4.1.1 runs absolutely flawlessly on my VZW Gnex, so I'm fine waiting for 4.2.1. Especially because I have 4.2.1 on my N10 and N7. And as far as the updates not being "quick", they're quick enough for me. Waiting 2 months for Verizon to approve an update from Google is fine, because I know it WILL get the update. The Verizon Galaxy Nexus will receive updates all the way until Google decides to stop supporting it. It's already received 4.0.2, 4.0.4, 4.1.1, and will receive 4.2.1. In addition it will most certainly get one more update before the Gnex is end-of-lifed, possibly two. That's more updates than most phones get in two lifetimes. I'm totally fine with that.
[Samsung Galaxy Nexus] Jonny:
Ok, I've cleaned all the off-topic trolling and flaming. You guys get one last chance before I close this thread, ie all posts from now should be on topic and not toll or flame posts.

Jonny
[Samsung Galaxy Nexus] oldblue910:
Thank you.
[Samsung Galaxy Nexus] nitsua98:
No he didn't he's just trying to gather posts so he can post in the development sections.
[Samsung Galaxy Nexus] ironside2011:
Man! Got me botton mashing like a mad man ! What an ass!
[Samsung Galaxy Nexus] ntb81:
Now that we've all had a day to play around with this, just wanted to send a big thank you once again to OldBlue and El Madhatter for making this happen once again. It's just plain cool that both of you took the time to get this done for everyone despite your busy schedules. One thing I noticed today looking around at some of the ota-related threads on this and other forums is that you guys were both thanked or mentioned in a lot of places, which I don't think happened quite as much with the 4.1 update. Well deserved. Thanks again.
[Samsung Galaxy Nexus] klobkelosh:
Hear hear!
[Samsung Galaxy Nexus] efrant:
QFT
[Samsung Galaxy Nexus] efrant:
Not gonna happen with posts like that. He'll never reach 10.
[Samsung Galaxy Nexus] robogoflow:
I think Verizon and Sprint are pretty even. The time Sprint customers spent waiting for downloads evens out to the time spent by Verizon customers waiting for OTAs. Granted both have ups and downs like showing off brand new software on a old device or googling an answer quick to win an arguement, but one day the two will truly even out and by then I'll be long gone to pure GSM and buy phones off Play because it's insane waiting for a company take months for an update when devs do the same within hours.
[Samsung Galaxy Nexus] ironside2011:
I hope to do the same in the near future! I love Verizons reception quality but they care little to none about customers
[Samsung Galaxy Nexus] nitsua98:
Sprint and Verizon are still scumbags. :p
[Samsung Galaxy Nexus] ironside2011:
I forgot to ask after I side load the update. Will I still recieve the official OTA notification when it finally arrives?
[Samsung Galaxy Nexus] oldblue910:
No because you'll already be running Rhee latest software.
[Samsung Galaxy Nexus] techspecs:
... Assuming this leak becomes the final approved version.
[Samsung Galaxy Nexus] oldblue910:
Well yeah. If it doesn't, then no, we probably won't see an OTA to whatever the public release is. That's what happened with IMM30B.
[Samsung Galaxy Nexus] xeene:
Neither of two working for me. :(
[Samsung Galaxy Nexus] The_other_ray:
Go here.

http://xdaforums.com/showthread.php?t=2176954
[Samsung Galaxy Nexus] ntb81:
apologies if i missed this somewhere, but is the sideload option in stock recovery new? I don't remember having that option for the 4.1 update
[Samsung Galaxy Nexus] :
Once verizon goes VoLTE, voice over lte this CDMA and lte fiasco with updates just might go away and we'll be like the GSM version. *pray*
[Samsung Galaxy Nexus] oldblue910:
Yes, that was a new option that they added onto the stock recoveries in 4.1. So this would have been the first time that you would have seen it.
[Samsung Galaxy Nexus] pyrobo0by:
F&&$ waiting for Verizon to update I'm already on 4.2.2 carbon rom
[Samsung Galaxy Nexus] oldblue910:
Yeah. Some of us like the stock ROM though.
[Samsung Galaxy Nexus] y2jdmbfan:
Well tethering to my laptop and Playstation Vita work fine on 4.1.1, but don't work on 4.2.2. If anyone else has run into this and has any solutions, I would really appreciate it.
[Samsung Galaxy Nexus] Winesnob:
Definite improvements with the radio. 4g holds a signal much longer before falling to 3g, and the connection seems more reliable even in low signal areas (been plagued with this since I bought the phone due to where I live). HI seems smoother also, but that could be placebo in all of my excitement to finally get the update.
[Samsung Galaxy Nexus] El Madhatter:
Thank you, ntb81.
[Samsung Galaxy Nexus] twan69666:
HUGE thanks for this! Been waiting forever and was considering switching from my 4.1 stock rom, Glad I waited now!
[Samsung Galaxy Nexus] Big ZD:
Does anyone have feedback on the gps lock times with stock 4.2.2?

Sent from my Verizon Galaxy Nexus
[Samsung Galaxy Nexus] oldblue910:
For me it's no better or worse than its ever been. That's never been an issue for me.
[Samsung Galaxy Nexus] ironside2011:
Anyone know how install the drivers for the Gnexus on a computer that runs windows XP
[Samsung Galaxy Nexus] oldblue910:
I spent 2 hours getting this to work with El Madhatter to get that 4.2.2 link. PM me and I'll help you out.
[Samsung Galaxy Nexus] jasondowning85:
Who knows when the official one will role out... ahah. Until then, running 4.2.2 Vanir which has a stock feel and runs like a bat out of hell
[Samsung Galaxy Nexus] Winesnob:
And thankfully the media scanner stopped sucking my battery at boot. I keep a large database on my phone for work, and on 4.1.1 any boot/reboot would cost 10-20% of my battery. Now it loses a mere 5%.
[Samsung Galaxy Nexus] johnhimm:
Jump right in this stock 4.2.2 build blows Vanir out of the water.
[Samsung Galaxy Nexus] jt3:
I'm assuming you mean the drivers for USB Debug or bootloader? If so, honestly, I found the easiest way is just to install PDANet onto your WinXP computer. You'll get the drivers that way. If you don't want it, you can uninstall PDANet afterwards, and you'll still retain the drivers.

On another note, I sideloaded this JDQ39 update today, and I gotta say, this update is working great for me. The new radios are giving me about a 10dBm increase, give or take, and even though I typically only have 1 bar at work, it's not flip-flopping from 3G/4G/NS like it usually does. Time will tell, but I'm betting my battery life will be amazing because of this.

I did have one issue that I thought I'd share. After the update, my GNex was running REALLY hot, and my battery was draining so fast I could almost watch the percentage drop like a countdown timer. I found that some 80% of my battery was going to "Exchange Services." Apparently this happens sometimes. The fix was to delete my Exchange accounts on my GNex, and re-add them. Once I did that, my phone ran cooler, and the battery drain shifted out of turbo. Although my issue was with Exchange, I've heard that sometimes this happens with "Google Services" too... with the same fix. Delete and Re-Add the account.

Quick question... If this update does NOT turn out to be the final OTA version... is it going to take an unlock/root/restore back to 4.1 in order to get the update, or is there usually a way to upgrade from the leak version to OTA version?
[Samsung Galaxy Nexus] oldblue910:
You would either have to revert back to 4.1.1 and apply the final OTA, or wait until JBQ releases factory images on the Nexus Images page and just flash those. But either way you'd have to have an unlocked bootloader.
[Samsung Galaxy Nexus] ironside2011:
Where do I get PDAnet
[Samsung Galaxy Nexus] jt3:
http://pdanet.co/

The free version is all you need to get the drivers. As I said, if all you need are the drivers, then you can uninstall PDANet after you've connected the GNex (in each of the modes you're going to use, since each uses different drivers), and seen Windows load the correct driver.

---------- Post added at 04:41 PM ---------- Previous post was at 04:30 PM ----------

Thanks, I figured as much. I don't mind unlocking, but since that would wipe my phone, I thought I'd ask. I'm no stranger to unlocking/rooting, but just got tired of dealing with all that. Kept my GNex stock. I just ADB Sideload so I don't have to wait for my turn in the OTA line, since I always manage to be toward the back somehow. I've just been waiting for so long for this update that I couldn't wait for the final OTA confirmation. Finally getting 4.2.2, even if only a week or two early, is worth any hassles I may have later on because the final version changes. Damn you N7 for getting me used to 4.2.2!!!
[Samsung Galaxy Nexus] ironside2011:
as soon as i go to recovery the MTP wont install even with PDAnet
[Samsung Galaxy Nexus] ericaraj:
I had that problem and solved it by using the USB cable that came with the phone. I have no idea why it made any difference, but the drivers would not install when I used a generic cable.
[Samsung Galaxy Nexus] AuroEdge:
Use NakedDriver 0.72 (on the XDA forums)
[Samsung Galaxy Nexus] ironside2011:
Maybe I try that soon,but for now I'm done! I don't know anyone gets anything done on windows xp

---------- Post added at 04:45 PM ---------- Previous post was at 04:43 PM ----------

I don't have the OEM cable that came with my phone anymore. Damn thing broke like a month after I got it. I'm using my brothers bionic cable
[Samsung Galaxy Nexus] techspecs:
Do you know about putting a .nomedia file in the folders you don't want to scan?
[Samsung Galaxy Nexus] Winesnob:
Yes, but beginning with 4.1.1 Android ignores those due to changes in the file indexing. Google's explanation was better compatibility with file transfers when plugged into a computer. The 4.2 code was updated to only give a quick look at files with wildcard characters (mostly affecting database files).

I tried sticking .nomedia files everyplace I could think of, but in 4.1.1 it was futile. There's a Google bug report on this exact issue, and folks with a GS3 and a lot of media are not happy.
[Samsung Galaxy Nexus] ironside2011:
where can i find WinUSBCoInstaller.dll . everything work expect i nned this file
[Samsung Galaxy Nexus] ironside2011:
I'm through trying to side load ! Windows so refuses any sort of driver help! The toolkit was useless ,villain driver was useless, naked driver was no help. The nexus driver's from Samsung didn't help either. I'm stuck waiting for Verizon. Thanks for trying to help guys
[Samsung Galaxy Nexus] Winesnob:
Get an OTG cable and use a USB thumb drive. There's a stock recovery option for this, and it's far faster than typing ADB commands. No drivers required. :)
[Samsung Galaxy Nexus] spencer88:
There's actually drivers in the android sdk for adb and recovery interfaces.

Sent from my DROID RAZR MAXX HD
[Samsung Galaxy Nexus] mcgoo99:
could this be why my CM10.1 3/6 Nightly VGN gets blazing ****ing hot when recharging on the USB port of my Win7 PC, but not the wall charger??
[Samsung Galaxy Nexus] ironside2011:
Where do I find them?
[Samsung Galaxy Nexus] spencer88:
I can't remember the file path off the top of my head. You'll come to a directory with two folders, one is called android and the drivers are in the other folder. Wish I could remember more for you. If it was at home I could give you screen shots.

Sent from my DROID RAZR MAXX HD
[Samsung Galaxy Nexus] spencer88:
So you have to launch the SDK manager first (I forgot about that) and download the drivers. Attached is a screenshot of the sdk manager. You also need Java installed in order to even launch the SDK manager. If you don't have java you'll just get a black command prompt window open and close really fast and won't know what's going on.

After you do that the drivers are in the extras folder. I've attached a screenshot for that also. Those are the drivers you'll need for adb interface as well as recovery interface.
[Samsung Galaxy Nexus] ironside2011:
Thanks man! I'll definitely give that a try! Maybe 4th times the charm
[Samsung Galaxy Nexus] ironside2011:
Anyone know how to fix the INTF1 Driver on windows xp?
[Samsung Galaxy Nexus] sanjurotsubaki:
I've never rooted/updated/etc on any of my devices.

I have a Mac mini with bootcamp, was about to do the ADB sideload in windows, but read that you could do the same thing from the Mac OS. Was incredibly easy. No drivers needed, everything done natively in the terminal.

Just did it a hour or two ago. New update is very fluid on the device. So, if you're having trouble and have a Mac/know somebody you can borrow one from, it's very easy.

EDIT: Could do the same from Ubuntu/Linux I imagine as well.
[Samsung Galaxy Nexus] ironside2011:
Unfortunately I don't
[Samsung Galaxy Nexus] JPBeard21:
I think those INFT devices show if fast charge is enabled. Check to make sure it's disabled.
[Samsung Galaxy Nexus] ironside2011:
I'm totally stock,but I'm using a droid bionic cable to side load
[Samsung Galaxy Nexus] JPBeard21:
I was thinking you were possibly on a custom kernel. Cables can make a difference as well. I have no more xp machines, I'd recommend using Ubuntu, if you don't want a dual boot, run it as a live CD.

Edit: Or if you don't want to order an OTG cable or buy an overpriced one from Best Buy (not even sure they have them in store) they are easy enough to make if you are semi-proficient with wiring and have a spare micro-usb cable and a spare USB extension cable.
[Samsung Galaxy Nexus] ironside2011:
Will that allow me to install 4.2.2 to my nexus?
[Samsung Galaxy Nexus] JPBeard21:
Ironside, sent u a pm.

Edit: check this post, method 4a.

http://xdaforums.com/showthread.php?p=28181832
[Samsung Galaxy Nexus] JPBeard21:
Have you tried toggling USB debugging on/off? ;)
[Samsung Galaxy Nexus] y2jdmbfan:
Along with the mobile Hotspot not working I also have a weird bug when charging, after it charges completely and is still plugged in, say overnight, when I check the phone in the morning it says "Connect Your Charger" and the battery appears empty and the phone turns off. However, when I turn the power back on it shows fully charged. I am flashing to 4.1.1 stock with the Galaxy Nexus ToolKit and then using the toolkit to temp boot into clockwork mod recovery and flash the update. I have confirmed that 4.1.1 doesn't exhibit the mobile hotspot issue or the charging issue. Maybe I am not flashing the 4.2.2 update correctly. Any help is appreciated.

Y2J
[Samsung Galaxy Nexus] johnhimm:
Flash "Native Tethering Patch" for hotspot to work.

http://xdaforums.com/showthread.php?t=2176954
[Samsung Galaxy Nexus] ironside2011:
So far so good for me with 4.2.2 had absolutely 0 issues! Actually it works better now then it did right outta the box or with 4.1
[Samsung Galaxy Nexus] oldblue910:
My Gnex came shipped with 4.0.2/ICL53F so I suffered through that atrocious build, but then the phone got progressively better. The 4.0.4/IMM30B leak ran as good as any ICS build ever did for that phone. When the official OTA came out (4.0.4/IMM76K), it ran good, but the radios weren't as good as the ones included with IMM30B in terms of call quality. IMM76K's radios also introduced issues with 3G/4G switching where it would sometimes take 5 minutes for my phone to recognize there was a 4G signal available.

In September, when JRO03O was released, I was over the moon with how well that ran. Those radios really improved the call quality for me even though the 3G/4G switching problem still existed. Also, the Jelly Bean user experience just ran SOOOOOOO well. I was actually cringing a little to flash that 4.2.2/JDQ39 update because JRO03O ran so amazingly well.

Thankfully, I have not regretted updating. JDQ39 is the best this phone has ever run for me. The interface is nice and smooth, the radios have finally fixed the 3G/4G switching issues, and I love the additional features in 4.2 like the photo editing tools and the better camera app. I really hope Verizon approves this build for public release because this is seriously the best build ever created for this phone.
[Samsung Galaxy Nexus] ironside2011:
How would we load the public update, if we have the leaked one?
[Samsung Galaxy Nexus] oldblue910:
Well if Verizon approves JDQ39 for release then you won't have to worry about it. It'll be the same update. If they don't approve this and Google ends up releasing something else, then chances are high that we would have to flash back to JRO03O and apply whatever the official OTA turns out to be. That's what happened with IMM30B. It's the risk you take running bleeding edge builds.

That said, though, JDQ39 was the official OTA for the GSM model, as well as the Nexus 4, 7 and 10. IMM30B sort of came out of nowhere with no real precedent. The only other place that we ever saw an IMM30 build in public was IMM30D takju, which shipped on the first round of GSM models sold from the Play Store in April 2012... a whole two months after IMM30B leaked for the VZW model. And even then, those GSM takju phones had an update to IMM76I waiting as soon as you turned it on for the first time.

I would be shocked if JDQ39 didn't see official release.
[Samsung Galaxy Nexus] sanjurotsubaki:
One thing I've noticed with this update is that sometimes when I hit the power button to unlock the phone, it doesn't do anything until I hit it a second time. At first I thought I just wasn't hitting the button fully.
[Samsung Galaxy Nexus] y2jdmbfan:
I pay for the hotspot from Verizon. The problem is not all devices can successfully connect to the Internet through the Hotspot on 4.2.2.

Y2J
[Samsung Galaxy Nexus] Winesnob:
Pretty much the same experience here. 4.2.2 just seems to flow (probably why some say there's lag, because instead of snapping it just glides). Radios are much improved, and haven't had the random reboots when on fringe signal areas like I did on 4.1.1. Battery life seems a touch better also, with the device hitting deep sleep pretty quick after screen off. Definitely wouldn't trade this for any earlier Android build.

And if anyone hasn't installed DashClock and its growing collection of extensions for the lock screen, now is the time.
[Samsung Galaxy Nexus] oldblue910:
You might want to do a factory reset. I had that problem with 4.1.1 where the device would connect to the Wi-Fi hotspot but the phone wouldn't actually route the connection. Updating to 4.2.2 fixed it for me.
[Samsung Galaxy Nexus] Phoenity:
Order of operations for flashing...

i know this isn't necessarily the best place for this question, but I don't have 10 posts yet so I can't put it in the thread for my rom yet. You guys might know though. I'm a toro gnex running Paranoid 3.0 (4.2.1) w/ the stock kernel. I wanna update to PA 3.10 (4.2.2) and run the AK Cylon 731 kernel that everyone is raving about. But I'm not sure of the order I should do this. Apparently I may need to update the radios as well, so I have the rom, the gapps, the kernel and the new vzw 4.2.2 radios, but I'm not sure what order to do them, and if I need to flash after a full wipe or if i can just wipe the dalvik/cache.
[Samsung Galaxy Nexus] oldblue910:
ROM, gapps, kernel, radios
[Samsung Galaxy Nexus] Phoenity:
"Yer my boy oldblue" thanks. wipe/no wipe?
[Samsung Galaxy Nexus] ironside2011:
I'd say wipe everything
[Samsung Galaxy Nexus] Phoenity:
cool, i'll probably wipe anyway. and one last ?uestion. I don't necessarily need to update the baseband, do I? (toro gnex)
[Samsung Galaxy Nexus] johnhimm:
Wrong forum, ask in the PA forum.
[Samsung Galaxy Nexus] EvilDobe:
You don't NEED to but it can't hurt to do it.
[Samsung Galaxy Nexus] ravenofdoom:
Tethering on Stock 4.2.2

The wisdom on this forum has been to turn to the following patch to enable tethering on the 4.2.2 official leak:

http://xdaforums.com/showthread.php?t=2176954&page=9

However, I want to remain "un-modded" to allow for receiving updates when they arrive (I last learned the hard way by having installed the leaked 4.2 camera, clock, etc. on stock 4.1 and being unable to use stock recovery to flash the 4.2.2 leak - it threw errors and I flashed a stock clean image of 4.1).

Is there a way to get wifi tether to work other than flashing a mod (or is there a way to undo/revert the mod if I want to install an official OTA)?
[Samsung Galaxy Nexus] oldblue910:
Yes. Download this app: https://play.google.com/store/apps/details?id=com.fattin.togglewidget.hotspot

It will enable the WiFi hotspot bypassing the check that it does if you enable it through phone settings.
[Samsung Galaxy Nexus] ravenofdoom:
Just installed it and tried the app... didn't seem to work. It bypassed the carrier check, so that it was broadcasting the wifi signal, but when I had my laptop connect to it (and authenticated with the password), it looked like I should have internet, but I couldn't connect (e.g. via HTTP to any website).
[Samsung Galaxy Nexus] porlo:
Just use the mod you linked to. It works great. When you see the news of offical OTA, you can always roll back everything from the factory images. https://developers.google.com/android/nexus/images
[Samsung Galaxy Nexus] wastedlife:
3.0 to 3.1 didn't require a wipe of anything other than cache/dalvik. Baseband is recommended, but so far I haven't noticed any difference after installing the update. I'm running the stock PA kernel, but I think I might give either AK Purity or AK Cylon a shot.
[Samsung Galaxy Nexus] JPBeard21:
I have this same issue tethering, I have to allow the connection at least 5, maybe up to 10 minutes before I can browse on PC. Been that way on all 4.2.x ROMs I've tried.
[Samsung Galaxy Nexus] oldblue910:
Oh. I had that problem on 4.1.1 but the 4.2.2 leak fixed it for me. You may want to try a factory reset.
[Samsung Galaxy Nexus] diobando:
I was having issues connecting once to the hotspot, I would get my PC to connect but it never let me access any website, then while connected, I disabled the network adapter and then re-enabled it. That solved my problem, hope it helps
[Samsung Galaxy Nexus] ravenofdoom:
Seems like the native tethering functionality is spotty.

http://code.google.com/p/android-wifi-tether/issues/detail?id=1751

Looks like others are also having problems with the wifi tether app. Anybody with more technical knowledge know what's going on with our beloved wifi tether app?
[Samsung Galaxy Nexus] DroidedMFer:
You don't have to, but it's worth a shot. I live in Southern California and tried the new radios and didn't have much luck with em. Could hardly hold onto a 4G signal and had slower speeds in my area(about 5 down and 3 up on avg.). I tried all of the radios and ended up on the 4.0.4 IMM76K FC05/FC04 radios and noticed a HUGE difference. In my brief experience with radios it's seems like the only way to see what's best for you is to try them out, run speed tests, and keep an eye on your signal strengths for each one. Good luck bud!
[Samsung Galaxy Nexus] :
Are you in LA? I'm from fresno and my gnex had the same problem on 4.1.1 stock radios.