yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] fix-this!:
im pretty upset we didn't get newer radios than the leak.
[Samsung Galaxy Nexus] adrynalyne:
I am happy with the radios. I think a lot of folks have misconceptions about them.

1. You can't run a different version of telephony code and get full benefit of new radios.

2. Radio firmware cannot make sucky radio hardware become awesome.

3. The mic issue may not be radio related (or fixable via radio) at all.
[Samsung Galaxy Nexus] Dan76:
I'll speculate here:

The mic issues are not software at all, they are because of old or faulty equipment on the Verizon LTE towers; not all towers, but a select few across the US. This has caused many users that have the specific radio used in the LTE Galaxy Nexus phone to have problems with voice calls: mic cutting out, complete audio loss, crackling, digital chirping noises, etc. This is why many have come to the conclusion that the problems are geographical (widespread, but specific to location). Verizon is aware of this issue and the problem but rather than admit to and announce failure, they are covering up the problem. Not putting false blame on software or hardware, but generally ignoring that there is a problem at all.

I just totally made that all up, but it's not far fetched.
[Samsung Galaxy Nexus] adrynalyne:
It is also not far-fetched to believe that there is NO fix to be had for the audio/mic drops if it is tower equipment. The GN is the only device on Verizon with this LTE radio.

For a spread out issue like this, I really don't foresee Samsung offering a recall. I could see Verizon offering others to switch devices though (which I have head they have been doing that).
[Samsung Galaxy Nexus] oldblue910:
A lot of people in NC are experiencing that one-way mic issue. Have you experienced it out in Asheville? I haven't had any problems here in the Durham area...
[Samsung Galaxy Nexus] kyoteqwik:
Asheville here, and yes I experience it frequently.
[Samsung Galaxy Nexus] fix-this!:
there is a thread on rootzwiki that claims people with hardware revision 10 phones do not have the signal issues that some of us have. i just checked and i have a version 9 device.
[Samsung Galaxy Nexus] adrynalyne:
I can lay this rumor to rest. I have both revisions here, and they are identical in form and function.

I even spent a night travelling around town, using them side by side and watched the signal dbm, bars, how fast they transitioned networks, and to what network they favored.
[Samsung Galaxy Nexus] fix-this!:
never said it was true i just posted what was claimed. i guess the only solution for me is too wait for the sg3 to come to verizon and see how the radios perform on it.
[Samsung Galaxy Nexus] adrynalyne:
Undoubtedly better.

Qualcomm > VIA and Samsung radio hardware.

Assuming the S4 is what will be used (chances are that will be the case).
[Samsung Galaxy Nexus] fix-this!:
now all i need is a release date lol.
[Samsung Galaxy Nexus] mizatt14:
For those still waiting for the update, try the old Google service framework trick. Just worked for me that way.
[Samsung Galaxy Nexus] boe:
Could you let us know how to do that?
[Samsung Galaxy Nexus] spencer88:
I believe you just stop it and start it again. Or clear the it's data.
[Samsung Galaxy Nexus] lrs421:
What did you do exactly?
[Samsung Galaxy Nexus] mizatt14:
Clear the data and force stop it then just go check for updates. Might have to try it a few times, fortunately I got lucky on the first attempt. (The service framework is located under apps>all btw)
[Samsung Galaxy Nexus] lrs421:
Yeah, thanks. I was hoping there was something I was missing. Tried that about 20 times this morning. Sigh.
[Samsung Galaxy Nexus] dco717:
Didn't work^
[Samsung Galaxy Nexus] cmdrfrog:
Success!!

Worked like a charm!
[Samsung Galaxy Nexus] Big Cam:
What is the app called that we are to force stop and clear data?
[Samsung Galaxy Nexus] sstang2006:
Google Services Framework
[Samsung Galaxy Nexus] boe:
Thanks
[Samsung Galaxy Nexus] TheLurg1687:
Tried about 15 times..nada
[Samsung Galaxy Nexus] stkiswr:
Home/menu/settings/apps/all/google services framework/

Touch this.

Once it opens clear data and force stop it. Hit home/settings/about phone/check for updates.

May take a few tries. I have not done this method but have read about it many times. Seems easy.
[Samsung Galaxy Nexus] boe:
It is not listed under all apps? I'm guessing I accidentally disabled it when I tried to stop it. How do I enable it again? I've already tried rebooting.

Whoops never mind - listed at the bottom.

---------- Post added at 11:58 AM ---------- Previous post was at 11:52 AM ----------

Tried about 10 times - I guess it isn't available in Los Angeles yet.
[Samsung Galaxy Nexus] spencer88:
Well everything I thought I knew about this outgoing audio problem was just thrown out the window. I was just on a conference call at work and we lost one of the guys on the phone, but we just heard the

same clicking noise

as we have been experiencing. When we dialed him back on the call the first thing I said was "I bet I know what phone you have, the Galaxy Nexus on Verizon right?"

He was using an HTC Thunderbolt.

I now think we're all screwed and they'll never figure this thing out.
[Samsung Galaxy Nexus] lrs421:
I'm in NYC, I wonder if it's by region or serial number?
[Samsung Galaxy Nexus] Snakehn:
oh great going back to 2010 now (3g) lol
[Samsung Galaxy Nexus] adrynalyne:
Wow.
[Samsung Galaxy Nexus] Dan76:
A guy on the VZW community just had this to say:

"I Have confirmation that the update went live yesterday and that it will be rolling out to all customers with in the next 10 days. It is released in batch based on phone serial numbers. If you have not received the update by then you can manually update by going into settings after day 10."

---------- Post added at 04:03 PM ---------- Previous post was at 04:01 PM ----------

This is not a good turn for the emotional GNex roller coaster I've been on today. Thanks for the info. This is crazy, for sure.
[Samsung Galaxy Nexus] spencer88:
Yeah. He said he could hear us just fine but we obviously couldn't hear him.

The complexity of the problem just grew a **** ton.
[Samsung Galaxy Nexus] bstealthy:
I've been thinking the same thing for a couple of weeks now that it just may be that Verizon actually has no idea how to fix the audio/mic issues on these devices. I think they haven't even come close to pinning down troubleshooting the issue.
[Samsung Galaxy Nexus] boe:
another let down

So I'm guessing since we've seen virtually no activity on this thread that again, there is no update for the Verizon GN.
[Samsung Galaxy Nexus] billykxda:
Good to hear/see evidence of the OTA.

Thanks!

-bk
[Samsung Galaxy Nexus] oldblue910:
Huh? I got the OTA earlier this morning.
[Samsung Galaxy Nexus] lrs421:
Yes but you appear to be in the minority.
[Samsung Galaxy Nexus] oldblue910:
VZW doesn't roll updates out all at once. They do it in batches. Patience, grasshopper.
[Samsung Galaxy Nexus] lrs421:
I realize...
[Samsung Galaxy Nexus] shizat63:
The Koreans can't make a decent radio. I wish I kept the RAZR MAXX.
[Samsung Galaxy Nexus] lrs421:
Radio quality aside, this post is soooo wrong on so many levels.
[Samsung Galaxy Nexus] adrynalyne:
Lets not be racist...
[Samsung Galaxy Nexus] boe:
That's like telling a guy whose been dating a girl for 6 months just be patient even though he STILL hasn't gotten any nookie. I'm thinking most people don't have that kind of patience and frankly neither should we.
[Samsung Galaxy Nexus] @rbiter:
I'm korean. You can't make decent posts.

That metaphor really does not make any sense. It kind of says i wish verizon was nasty and would just you know what all up in my phone. :what: NOW!

...
[Samsung Galaxy Nexus] adrynalyne:
This is how the Android world works and is not specific to any model or carrier. I don't see how you will get around not being patient unless you move to an iPhone.
[Samsung Galaxy Nexus] ckoadiyn:
Lol what the other two said but maybe that's why they don't have nukes yet either.....
[Samsung Galaxy Nexus] boe:
It would make sense if English was your first language - it appears to be Korean, then Ebonics, then English...

JK - I guess I'm too old to decipher what you are trying to say.
[Samsung Galaxy Nexus] fix-this!:
You should of said samsung makes crap radios. Then i would of agreed with you.
[Samsung Galaxy Nexus] Dan76:
The GS3 better have different LTE radios for the US version.
[Samsung Galaxy Nexus] ckoadiyn:
Well seeing how it should have the s4 chip in it id say that's a huge difference....
[Samsung Galaxy Nexus] billykxda:
As reported on another forum, VZW has confirmed that the roll-out started on 5/30, "in small batches", and will take the next few weeks to fully roll-out.

As of June 9th (10 days after release) users can pull it from VZW manually by checking for updates from the GNex.
[Samsung Galaxy Nexus] efrant:
Hopefully that will also mean that those on IMM30B could check-for/receive their update after that date as well.
[Samsung Galaxy Nexus] rjenk:
Fayetteville here and it happens frequently as well.
[Samsung Galaxy Nexus] :
I'm in Rocky Mount and it's really intermittent for me. I went a couple of weeks recently without any problems - even making a few lengthy phone calls - and then it happened in rapid succession over the last few days. It's strange. I thought it had something to do with the tower I was connected to because I live about two miles from work, and even less than that as the crow flies. That means I make 98% of my phone calls while connected to the same tower. But I was in Raleigh a month ago which is a strong 4G market and I had it happen then, so that shoots that theory in the foot.

If the 10-day rollout thing is true, I'll stop spamming the "Check now" button. :) The update will get here when it gets here. I will, however, call Verizon tech support and gently remind them they

WILL

be putting me into a different device should this update not fix the one-way audio issue for me.
[Samsung Galaxy Nexus] ATnTdude:
2 Points:

1) LTE has nothing to do with voice.

2) Virginia may have been built out with the same equipment as your local area, which is why you have issues in both areas. We don't know where Verizon installed what. It is likely a patchwork of different vendors across the country. It is unlikely that they would mix two vendors in one city, there would be a clean cutoff between providers.

In short, you have given us a little information, but not nearly enough to decide the issue one way or another.

[/COLOR]

There's usually a generic download for Nexus devices in additon to one targeted at people with the main OS version, like ICL-53F. These capture people on leaked ROM's and people who activate new phones that still have 4.0.1 on them.
[Samsung Galaxy Nexus] MileHighG8:
What will your phone do when it's updating?

Last night I woke up to my phone stuck on the screen that is shows when you first turn the phone on. I left it for a few minutes, then took the battery out and powered the phone back on. I still have 4.0.2. Hopefully it was not updating when I removed the battery.
[Samsung Galaxy Nexus] oldblue910:
Did you get the notification on your phone telling you that you had a system update available?
[Samsung Galaxy Nexus] efrant:
Yeah, that was the case on the Nexus One but, to date, I have yet to see any generic updates (i.e., an update that will update any build number to the current one) -- all of them have been specific, i.e., IMM76K-from-ICL53F, so I would expect a specific IMM76K-from-IMM30B update file.
[Samsung Galaxy Nexus] MileHighG8:
No message, just the colorful spinning squares that happens when you boot up the phone. Left it for several minutes before removing the battery (buttons did nothing).
[Samsung Galaxy Nexus] oldblue910:
That means your phone probably randomly rebooted itself in the middle of the night. You have nothing to worry about regarding the update. The update doesn't install automatically. You will get the notification on your phone, then you have to tell it to install.
[Samsung Galaxy Nexus] :
Good point; forgot that 4G/LTE is data only and has nothing to do with voice calls. Thanks.
[Samsung Galaxy Nexus] stickerbob:
I was under the impression that LTE was voice and data. But after reading this post I did a little research only to find out that is has not rolled out that way yet (looks to be 2013). No wonder LTE phones use so much battery, they run two radios simultaneously. I can't believe I didn't figure this out sooner! :confused:
[Samsung Galaxy Nexus] 3devious:
He could be talking about white/black/Hispanic/native American citizens of Korea who make bad radios you know? ;-)
[Samsung Galaxy Nexus] adrynalyne:
Riiiiight;)
[Samsung Galaxy Nexus] danzini:
Best Way to Backup a Locked Bootloader

What's the best way to back up my Nexus that is locked and not rooted? I want to unlock and root then restore a backup of apps and what not. Any help is appreciated.
[Samsung Galaxy Nexus] lrs421:
look in the development section for the Nexus toolkit. It can make a backup for you using adb. It can also restore the backup later.
[Samsung Galaxy Nexus] stkiswr:
Root first. Install cwm. Make a backup. Transfer all files to PC. Unlock boot loader. Transfer back to phone. Unlocked and all data kept
[Samsung Galaxy Nexus] spencer88:
You do know that you can't install cwm without unlocking the boot loader first right?
[Samsung Galaxy Nexus] efrant:
If you are on 4.0.1 or 4.0.2, you CAN root and install CWM WITHOUT unlocking your bootloader.

---------- Post added at 06:03 PM ---------- Previous post was at 06:00 PM ----------

Follow these instructions to root, then install ROM Manager from the Play Store, use that to flash CWM, reboot into CWM, run a backup, pull the backup OFF of your device, then unlock, push back the backup to your device, and restore. Done.
[Samsung Galaxy Nexus] TiltedAz:
Got it this morning. Seems a bit faster probably from the fresh reboot. More time needed to assess..
[Samsung Galaxy Nexus] bozzykid:
You don't need to root to make a backup. That's overkill for such a simple task.
[Samsung Galaxy Nexus] shizat63:
If the phone was engineered in Brussels and I had said the Belgiums can't make a decent radio, you wouldn't have batted an eye lid. And If I said Chinese you would be cheering.

Nothing racial was intended. You're too sensitive about Korean engineering being inferior to the Taiwanese or Motorolla (American?).
[Samsung Galaxy Nexus] efrant:
Not sure what you are talking about. If he unlocks his bootloader, ALL of his data will be gone. So making a nandroid backup is the easiest way to make sure you have an EXACT copy of your current ROM. It is not overkill - it is being thorough. No other way to do it without root. (And yes, I am aware of the ADB backup feature, but that does not do the same thing - it does NOT give you an exact copy of what is currently on your system.)
[Samsung Galaxy Nexus] adrynalyne:
I don't know what your issue is, but I would have called racist on your posting if you mentioned any of the others as well.

Suckage is due to companies and employees that work in them, not races, heritage, or locale.
[Samsung Galaxy Nexus] oldblue910:
Getting this back on topic...I noticed in my aLogCat when I got the OTA, the filename that the OTA software links to isn't 12f767e7a5d0.signed-mysid-IMM76K-from-ICL53F.12f767e7.zip, but instead 12f767e7a5d0.incremental.zip. The files are identical, just different names. Odd.
[Samsung Galaxy Nexus] lrs421:
You are correct, but for those who do not wish to unlock a bootloader or root their device the adb back up feature works good enough for simple backup of your apps and corresponding data. Nandroids are great and easier but you need root or temproot to restore it.

I used adb to backup and restore where's my water, I did it manually rather than using the toolkit and it worked flawlessly. I wasted too many hours at my office mastering that game to start over :)
[Samsung Galaxy Nexus] adrynalyne:
Just confirmed. Very strange.
[Samsung Galaxy Nexus] oldblue910:
Isn't it? Both links are live though. That's what's even stranger! haha
[Samsung Galaxy Nexus] efrant:
Interesting. Thanks for posting.
[Samsung Galaxy Nexus] oldblue910:
Interestingly, Google abandoned the IMM76K-from-ICL53F naming convention on all ICS updates for the Nexus S too. All the 4.0.3 and 4.0.4 OTA incrementals and full ROM packages are just twelve-character filenames, almost like a base64 hash or something. The only exception was the IMM76D from GRJ22 and full IMM76D files for the Korean Nexus S...those two files use traditional naming conventions.
[Samsung Galaxy Nexus] stkiswr:
The backup was to retain info if for any reason wanted to go back w everything there. Thats just how I do it. :) ymmv
[Samsung Galaxy Nexus] lrs421:
I think we've beat the backup horse to death. Let's just move on.
[Samsung Galaxy Nexus] Wyveryx:
using p3droid update to imm76k and lost 4g

I think the title says it all.

I used Droidmodderx's update guide to get to imm76k using P3Droid's version. Everything went smooth and I cleared everything. Data/Cache, Factory Reset.

Activated it and had 4G for the first day. I even maintained root through the whole process, however, after the first day I have yet to get a 4G signal.

I've tried everything short of reinstalling the old radios and reversing things with a backup.

Has anyone else experienced this? Anyone have any suggestions?

Thanks all.
[Samsung Galaxy Nexus] oldblue910:
I think they're better than the 4.0.2/ICL53F radios but not as good as the 4.0.4/IMM30B radios.
[Samsung Galaxy Nexus] adrynalyne:
There is a factor we are not seeing that is causing it. Neither me, nor my wife has this call audio issue.
[Samsung Galaxy Nexus] emcd4:
From a poll taken regarding this problem in this forum, about 30% of users seem to experience this issue. It appears to happen in some areas more often such as North Carolina, Minnesota, etc.

Galaxy Nexus Q&A[Q] POLL: Verizon Galaxy Nexus In-Call Microphone Issue - Location Map

My daughter has a GN and lives in Tucson and has not ever had the problem. Not sure if it is a hardware, tower or software issue.
[Samsung Galaxy Nexus] nsutherl:
Can someone post a brief write-up/explanation of how to apply this update if you are rooted/unlocked with CWM? I have all the basic knowledge of flashing ROM's, Kernels, etc... Is there anything special you have to do with this 4.04 update, or just return back to to stock 4.02 and flash the 4.04 zip file from CWM?

Thanks in advance.
[Samsung Galaxy Nexus] oldblue910:
You just need to flash back to stock 4.0.2. Then just put the file on your USB storage, reboot into clockwork and flash it. Simple as that.
[Samsung Galaxy Nexus] adrynalyne:
I am in Tucson too, so maybe you are on to something.
[Samsung Galaxy Nexus] oldblue910:
Next time I'm in Tucson (I have close family there), you and I are having a beer. :D
[Samsung Galaxy Nexus] adrynalyne:
Word!
[Samsung Galaxy Nexus] :
Can you post a link to the poll? I'm in NC and I'm having the problem, and have spoken to many other NC folks having the problem as well. Thanks!
[Samsung Galaxy Nexus] oldblue910:
Luckily I haven't had that problem. I live just south of Durham.
[Samsung Galaxy Nexus] :
Glad you haven't had that issue cause it's really annoying, trust me.
[Samsung Galaxy Nexus] kyoteqwik:
Same here, and it has seemed to have gotten worse recently.
[Samsung Galaxy Nexus] emcd4:
Search for "Galaxy Nexus Q&A[Q] POLL: Verizon Galaxy Nexus In-Call Microphone Issue - Location Map" in the XDA Galaxy Nexus General Forum.
[Samsung Galaxy Nexus] eman3316@optonline.net:
I have no mic issues in NC. I'm in the Cary/Durham/Morrisville area.

What I do have is issues when my 4G will just stop working and all data and voice is dead until a reboot.

Can't find any pattern that causes it. It just happens randomly from time to time.
[Samsung Galaxy Nexus] oldblue910:
You live right in my back yard! haha
[Samsung Galaxy Nexus] TeeRom:
I'm just south of Raleigh as well and one of the family Nexus' (Nexii?) has the issue and mine does not. Going to see if the update fixes the other one.
[Samsung Galaxy Nexus] emuneee:
When I had my Verizon GN. I often had the mic cut out issue. I installed the leak IMM30B and IM74K firmware and the problem went away. Note sure if it was a software fix or if it was on the network side. I am IN Cary, NC too. It was indeed super irritating.

Moved on to an unlocked play store GN on ATT though.
[Samsung Galaxy Nexus] Bateluer:
Still waiting for that OTA to actually go live, and Verizon to pull its head from its ass.
[Samsung Galaxy Nexus] Smokeey:
Until Verizon or Google announce an OTA this should all be taken as speculation/rumors/leaks. Maybe all of you should pull your heads out of your asses.
[Samsung Galaxy Nexus] spencer88:
Maybe you should stfu if you're not contributing to anything on this site whatsoever.
[Samsung Galaxy Nexus] jimmyhook:
If it means anything at all, and it may not, I just got off the phone with a Verizon rep,she told me she had a corporate email about upcoming updates for various devices and the GNex wasn't on it...
[Samsung Galaxy Nexus] Bateluer:
Well, since the 4.0.4 code went into AOSP in March, and since Google has updated the Nexus S GSM, Nexus S 4G, Galaxy Nexus GSM, and Sprint's Galaxy Nexus CDMA to 4.0.4, I will call Verizon out for bull ****. I can and will take my business elsewhere if they are unwilling to release an update that's been available for three months.
[Samsung Galaxy Nexus] jimmyhook:
To be honest though, I don't see much of a difference between 4.0.4 and 4.0.2. LTE is exactly the same, excellent in some areas and just ok in others. The OS seems exactly the same. I really don't understand why the update is so badly desired. my theory is that most of the problems I am reading about are hardware problems, and no update in the world will fix a hardware problem.
[Samsung Galaxy Nexus] Smokeey:
Yet the only announcement was for the GSM version of 4.0.4 via Google+ and a twitter post from JBQ. A Verizon 4.0.4 was never announced, nor spoke about by Google, everything you've been seeing are leaks and hype from stupid Android blogs looking for more people to visit their site. It's real funny how riled up people get over rumors and unfinished, untested, "leaks" and builds. Until Verizon and Google say "4.0.4 OTA Rollout has begun" no one here is at fault. Verizon is probably in-cahoots with Qualcomm testing the **** out of new LTE radios and Google is probably hard at work at a new revision ANYWAYS. Everyone just needs to calm the **** down about stupid .0.1 revision changes. It's really not work spending $375+ to get out of a 2 year contract when all you have to do is go in to cmd and type "fastboot oem unlock". Get over yourselves.

/rant

Sprint Galaxy Nexus also SHIPPED with 4.0.4. If you don't like quality service and aren't patient enough to wait for such a tiny update, (its not even 20mb) maybe you should leave Verizon.
[Samsung Galaxy Nexus] flintfirewalker:
Dude, Google is not announcing because they have to wait for Verizon to ok it. They can't announce ota rollout until Verizon OKs it.

And the question is, how long does it take to test a software? I'm ok with Verizon taking their sweet time as long as they can ok a solid product. But that didn't seem to be the case when the phone was first released. Verizon Ok'd gnex's release full of bugs (but that was when Verizon was ok with getting the phone out as soon as possible so they can start selling 2 yr contracts regardless of user satisfaction). And now that they won't be making any money off this update, they've suddenly become super testers.

point is, if it takes them 3 months to test a software, there's an issue in Verizon's quality assurance department.

as for the size of update, ppl paid top dollars and continue to pay top dollars to Verizon to get the device that's suppose to get updates first. that was what we were promised and that agreement is in beach right now. Sometimes it's more about the principle.
[Samsung Galaxy Nexus] adrynalyne:
I recommend you do so. It is like this for every one of their devices.
[Samsung Galaxy Nexus] adrynalyne:
Where was that promised for the Verizon Galaxy Nexus? There are some yakjuxx variants still on 4.0.1!!!