yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] mark manning:
That iPhone guy gave me the best laugh I have ever had here on xda. Thanks for a wonderful morning, I owe you one bro!
[Samsung Galaxy Nexus] oldblue910:
Not yet. Historically Verizon does OTAs on Thursdays, so I'd expect to see some people getting it today and into tomorrow.
[Samsung Galaxy Nexus] tunerfreak:
So I pulled the gmail app from the image but when I try to install it in Root Explorer it says "Application not installed". this is the same error I was having the first time when I tried to replace it with the market version. Do I need to do something with the Gmail.odex file?
[Samsung Galaxy Nexus] miketoasty:
Wow man so they fix tons of issues coming from .2 to .4 but you still have to nit pick?

Did you try rebooting and or resetting (To factory stock, this is a major update after all) the device? Possible an app is causing the issue after the update as well.

My Bluetooth works fine but every time I connect it I have to raise the volume #Firstworldproblems

Maybe you live in an area that gets crappy reception? My device is getting an extra bar after the new radios and gets about ~80 dbm compared to ~95 dbm before hand.
[Samsung Galaxy Nexus] efrant:
Don't install it. Just delete the modified apk in /system/app, and replace it with the stock one. Don't forget to make sure the permissions match the other stock apks (if they are different).
[Samsung Galaxy Nexus] stevessvt:
I think I have a right to nitpick, its not like they rushed to push out an update a month after its release. its been 5 months, and stupid stuff like this should have been taken care of. Its not like they didnt have the time to button up these problems. And as far as my reception, my wifes RAZR can be holding 1-2 bars of 4G while mine is floundering between 1X and 3G. This is my second phone. The only thing that jumps out at me being fixed between .2 and .4 is it doesnt stutter nearly as much when scrolling screens. I am thankful for that. #Dontcareaboutfirstworldproblems.Wantmy$650paidincashphonetoworkright.
[Samsung Galaxy Nexus] miketoasty:
It's been said over and over that the radio's in this phone aren't as strong as in other phones, but there is only one place that I have seen my Nexus not get 4G when my girlfriends Razr Maxx has had it. Maybe get a replacement?
[Samsung Galaxy Nexus] stevessvt:
I guess. Maybe I would get lucky and get a .10 phone. Arent they suppose to be better?
[Samsung Galaxy Nexus] tunerfreak:
ahh ok it worked then thanks!!
[Samsung Galaxy Nexus] adrynalyne:
No. There are no reports in improvements on .10 devices.
[Samsung Galaxy Nexus] oldblue910:
This. I was under that impression too initially, but the more I read about it, the more I discovered that the difference between .09 and .10 is probably an extra dab of solder somewhere. ;)
[Samsung Galaxy Nexus] adrynalyne:
They actually changed the lte radio in .10 and not for our benefit.
[Samsung Galaxy Nexus] oldblue910:
Really? Do we know what they changed exactly?
[Samsung Galaxy Nexus] adrynalyne:
A different, less expensive radio. It performs the same but saves Samsung money.
[Samsung Galaxy Nexus] markd0wn:
Semi-related question... does this Verizon update mean that the OTA 4.0.4 version will be available soon for international/GSM versions of the Nexus and/or specific region versions (like yakjuxw build)?

I read that those builds get the updates from Samsung and not directly from Google (hence the delays) but I'm not sure if this means Samsung gave Verizon the 4.0.4 version and they're now rolling it out.

I have a yakjuxw build, not rooted, everything completely stock, but I'm not even sure where the phone connects to when I check for updates, I assume a Samsung server though.
[Samsung Galaxy Nexus] oldblue910:
No. The Verizon Galaxy Nexus gets updates from Google (after passing Verizon's testing). The yakjuxw and other non-yakju firmware gets updates from Samsung, so those updates come on Samsung's timeline.

The reason everyone is pissed off about Verizon is because Google gets these OTA updates ready for the VZW Galaxy Nexus, but then Verizon drags their feet testing everything. Meanwhile Google's hands are tied because Verizon won't allow the updates to be rolled out until the updates pass testing. This means that it adds delays. The GSM Galaxy Nexus got updated from 4.0.2/ICL53F to 4.0.4/IMM76I back in April. Here we are at the end of May and the Verizon GN is still on 4.0.2/ICL53F because of VZW's testing procedures.
[Samsung Galaxy Nexus] a1exus:
I heard it's Qualcomm who's dragging their feet and holding Verizon's back..
[Samsung Galaxy Nexus] oldblue910:
That's a new one to me. I can't possibly see what Qualcomm has to do with any of this...all they provide is the CDMA license...
[Samsung Galaxy Nexus] markd0wn:
Oh, that makes things clearer, thanks. I guess some of the international buyers will stay on 4.0.2/ICL53F even longer - that's the version I have and I'm not aware of a 4.0.4 version existing for yakjuxw, so we still have to wait indefinitely, or give up and convert to a yakju build.
[Samsung Galaxy Nexus] a1exus:
my guess its not just license, it's drivers for their radio i think google's part is all ready to go (long time ago), verizon doesn't really puts any customization into our phones other then: my verizon & vzw backup (which nobody really uses it)
[Samsung Galaxy Nexus] ATnTdude:
Source? Not doubting, I just want to read more about this.
[Samsung Galaxy Nexus] oldblue910:
I use My Verizon for the data usage widget, but yeah VZW backup is useless. haha
[Samsung Galaxy Nexus] adrynalyne:
Well, I had a Verizon friend of mine do research on it some months ago. Later, some sites started reporting it as well.

Naturally, I cannot find the blogs I did see reporting this now that I posted what I did which makes me look like a douche :(

I'll post URLs when I find them.

Edit:

http://www.eetimes.com/electronics-news/4236517/Samsung-chip-lowers-cost-of-LTE

Take it with a grain of salt of course. I cannot find any revision specific teardowns and the article isn't clear if previous version meant a different device/phone entirely. Reading it again, I could be entirely wrong. I am humble enough to admit it though :D
[Samsung Galaxy Nexus] a1exus:
i barely use my verizon (my data is unlimited) and never use vzw backup
[Samsung Galaxy Nexus] MMcCraryNJ:
See though, I feel as if people sometimes don't see that side of the coin. Everyone is pissed at Verizon for their extensive testing, but in general, wouldn't you prefer that things be as tested as possible before you get them? Sure the delays aren't cool, but at least you know they are QAing the hell out of the software.
[Samsung Galaxy Nexus] Smokeey:
This. We have Verizon to blame for these so called unannounced updates be "delayed". Or maybe we can blame the countless number of Android blogs who like to post a blog every time some random ass guy decides to say "hey I got an update!"

Until Verizon SAYS something and UPDATES us OFFICIALLY none of you should be *****ing.
[Samsung Galaxy Nexus] spectrumfox:
You're actually way better off wiping and converting to a yakju build. They will see updates sooner and more frequently.

---------- Post added at 07:12 PM ---------- Previous post was at 07:11 PM ----------

Its generally understood that you're better off converting to yakju.
[Samsung Galaxy Nexus] boe:
If Verizon had properly tested the phone the first time, it wouldn't have the mic, data or signal issues so I wouldn't care when the 4.04 update came. But since it is still having the issue 6 months after release, I don't really expect their "testing" team knows what they are doing and shouldn't be interfering with any updates.
[Samsung Galaxy Nexus] jkc120:
Too bad 4.0.4 doesn't fix the mic muting issue..
[Samsung Galaxy Nexus] spectrumfox:
I don't have this issue and I use my phone for long periods of time. Maybe you have bad hardware.
[Samsung Galaxy Nexus] jkc120:
Perhaps but it affects A LOT of people. And if it IS hardware, it just goes to show how ****ty Damsung's QC is. So I can get a phone with horrible display issues, or radio drops, or mic muting but not.one without any.of those flaws? Its like playing Russian roulette. What a joke.
[Samsung Galaxy Nexus] SilentO:
Still cannot receive the update over the air.

Verizon sucks

Google sucks

Switching to iPhone 5 when it comes out.
[Samsung Galaxy Nexus] spectrumfox:
My phone has none of those flaws... You may just have to keep trying until you get one that works for you. I went through like five or six Droid 3's that were all messed up in some way.

---------- Post added at 08:32 PM ---------- Previous post was at 08:32 PM ----------

Don't let the door hit you on the way out now! Heh, like iPhones don't have their own share of hardware and software issues. ;D
[Samsung Galaxy Nexus] SilentO:
Name some?

Who has actually received their 4.0.4 over the air?
[Samsung Galaxy Nexus] martonikaj:
FYP.

K have fun.
[Samsung Galaxy Nexus] spectrumfox:
Name some? Go read the Apple iPhone support forums. You'll see rage there so bad it'll give you hemorrhoids just reading it.

And 4.0.4 hasn't yet been officially pushed out in an OTA. You might also want to look up the word patience in another tab while you're browsing Apple's forums.
[Samsung Galaxy Nexus] jonstrong:
Not disregarding your problem report - or that of any of the others here. But I'm not sure that constitutes evidence that "a lot of people" are having these problems. Estimates are that Samsung sold something in the vicinity of 35 to 40 million smart phones in Q1.

In my experience, a disproportionately large group of people experiencing problems wind up in product forums - generally to try to find answers to their issues, compare notes, etc. People clearly also come to sites like this to learn, share, experiment and immerse themselves in the whole modding experience. But - no matter how you slice it, I'll be you find more problem reports collected in an online product-specific forum than you will in an average random cross section of users.

Maybe I'm unusually lucky - but in the 6+ months I've had my Galaxy Nexus, I've had none of the issues you list: no radio, display or mic muting issues. I wish the battery was bigger - but for the most part, it's a great device. Sorry to read about your issues, and those others complain about. But I suspect we'd be hearing / reading a lot more about the problems if millions of users were experiencing them.
[Samsung Galaxy Nexus] spectrumfox:
This.

While we do feel your pain regarding your Galaxy Nexus problems (lord knows most of us have also experienced the frustration of getting faulty smartphone hardware), your issues do sound like something a software patch might not be able to address.

Verizon Wireless will gladly keep substituting your device out with another until you get one that works for you. You just have to keep at it.

Have you also thought maybe its not your phone hardware, but maybe something wrong with a cell tower in your area?
[Samsung Galaxy Nexus] MMcCraryNJ:
Ah, correct. Here's the thing though, I'm not too sure if you were paying attention from the October unveiling of the Galaxy Nexus to the December Verizon release, but people were getting pissy and impatient. "Why isn't the phone out yet? What the hell are they doing? Just release the thing already!"

And then the rumors from somewhat trustworthy sources came out, saying the device had issues, and that it wasn't ready for prime time, and Verizon was still going back and forth with Google on software. But people said, "We don't care! Just release the phone! Work the software out later! This is a Nexus device, we're completely fine with it having issues, they will get ironed out eventually! Just release the damn thing!" Well, ask and ye shall receive! Everybody absolutely HAMMERED Verizon all throughout November about the Galaxy Nexus. They hammered sales people, support people, the twitter people. Everybody wanted it asap and didn't care about the issues, and we got it.

Impatience played a large part in that, and is also playing a large part here. Look, we all knew Verizon has high QA standards...maybe too high, but that's a different argument altogether. The fact that NO device on Verizon has had ICS pushed to them yet, not even the 3G/LTE Xoom, indicates to me that Verizon has an issue with the way ICS operates. Maybe it's still too buggy. Maybe there is an issue with ICS and LTE. For whatever reason, Verizon has held off in getting ICS to anybody.

The update will come when Verizon feels it's ready, plain and simple. The fact that we are seeing leaked builds on Google update servers is a good sign.

I'm not excusing them completely of delays, but you HAVE to see their side of the argument here.
[Samsung Galaxy Nexus] oldblue910:
Well said, good sir. We need more voices of reason like this on XDA!
[Samsung Galaxy Nexus] boe:
On the otherhand, people complained about the European model having a glitch and they had a fix in less than 2 weeks. Likewise with Sprint. Release the fix - let us complain if there is an issue and if we get the same response time 2 weeks sounds way better to me than 6 months.
[Samsung Galaxy Nexus] adrynalyne:
..and that glitch was not found in the Verizon or Sprint model so...
[Samsung Galaxy Nexus] Dan76:
Well, what ever the case there are a good many of us on VZW that have a definite glitch with outbound audio... one that has not been addressed in 4.0.4 IMM76K or the updated radios and we have been living with it since release date in December 2011.
[Samsung Galaxy Nexus] adrynalyne:
So...what is the cause of it?

Software? Radio firmware?

I've not had this issue. Neither has my wife. Neither has a friend of mine. So...are you certain it is a software issue addressable in an OTA update?
[Samsung Galaxy Nexus] boe:
Hard to say if Verizon never releases updates ;)
[Samsung Galaxy Nexus] adrynalyne:
Irrelevant to knowing the cause. The volume issue with GSM devices happened to EVERY ONE OF THEM. So I wonder what the cause is here.

This happened in 4.0.1 and 4.0.2, AFAIK. IMM30B doesn't address it, neither does IMM76K. IML74K, IMM6D/I on AOSP don't address it. Something major like that would have been a fix in one of the leaked updates, or at least AOSP, imo.
[Samsung Galaxy Nexus] BlackHoleSlam:
i have not had it either
[Samsung Galaxy Nexus] Dan76:
I'm not sure anyone knows the cause. I hope it is software able to be fixed OTA, but it certainly could be hardware.

I've read about so many other people with the same issues, some have swapped phones up to 7 times from VZW with every one having the same problem. Others have new phones that may be fixed.

There's speculation of problems related to whether or not the phone was manuf in China or Korea (see posts below), but nothing definitive.

There's some speculation that the issues are due to location and 3G 4G handoff and geographical location. I really don't know, but here are a few threads with many others testing and trying different radios, ROMs and no one appears to have found a resolution.

Mic cutting out issue - http://xdaforums.com/showthread.php?p=26519036#post26519036

IMM76K update - http://xdaforums.com/showthread.php?p=26529044#post26529044

Verizon quality control - http://xdaforums.com/showthread.php?p=26253497#post26253497

Poll of VZW problem location map - http://xdaforums.com/showthread.php?p=26527668#post26527668
[Samsung Galaxy Nexus] adrynalyne:
It would be interesting for someone to try an experiment:

Take a known working phone, and note the location/tower it is connected to.

Take a problematic phone, and try it in the location the other was known to work properly.

It would be difficult to setup, but it would be interesting to see the results.
[Samsung Galaxy Nexus] Dan76:
I don't remember which thread, but I remember one person a couple weeks back that has the problem and went to a different state for a week and did not experience the problem (I want to say Utah or somewhere...) then back home, he/she did have the problem again.

I've not been out of town yet to test for myself.
[Samsung Galaxy Nexus] adrynalyne:
Certainly not a large enough sampling but that would indicate a tower related issue, imo. I hope more people try it.
[Samsung Galaxy Nexus] ATnTdude:
Thanks. If it's a die shrink, you might MIGHT see a bit better battery life. Then again, if they just cut something out to reduce die size, you might get worse. Might just be a different vendor. It doesn't tell us anything, but it makes sense.

It makes sense. US carriers are so large, they buy from multiple vendors, and because there are multiple build outs, each vendor might supply multiple versions of their equipment. It might be that that Alcatel-Lucent uses a slightly different (though theoretically equally valid) implementation on the LTE standard than Ericsson. Thus you get a problem when your (literary "you", "your")phone connects to one and not the other.

If you fly across the country, there's a good chance you're flying into an area built out by a different vendor. Then again, there's always the chance that whoever built the tower next to your house half-assed it. We're dealing with 1st gen deployments and handsets, there's GOING to be problems. If your last LTE phone "had no problems at all" then it might have been the blind luck of picking the right model for your area. Your last phone is not enough of a sample to prove anything, so stop acting like it does and learn how networks actually work.

Or go to HoFo, where you (again, the literary "you") aren't expected to know the difference between a baseband and a baseball. The never ending b*tching by impatient neckbeards is ruing the vibe around here.
[Samsung Galaxy Nexus] TAWoody:
I've been waiting long enough.
[Samsung Galaxy Nexus] davidadavila:
i would not expect much from the update since the radios have been leaked already, i flashed the new radios from the 4.04

and it said that i have 3 bars, before i had 2 bars in the area, but the problem is that is not holding the 4g signal so you can have 4 bars but then it just dies and you have no signal. so its not like its a gradual thing, and if you have no signal it should switch to 3g seemlessly like you moved from 3g to 1x in older phones. i have a bad feeling that it is a hardware issue, by no means im n expert but it the razor is not having these issues why not just copy the radio from there on the nexus phone.....

I called verizon and their tech 1 support have no idea what they are taking about. the rep told me"why dont you just get a Razor" im like because i hate blur and i wanted a razor Google's flagship phone.why are they selling something that is not working properly....its so frustrating like selling a car that 6 gear doesnt work i mean you can still operate it but its not convinient
[Samsung Galaxy Nexus] xXTERMIN8RXXx:
OTA update is out
[Samsung Galaxy Nexus] TheLurg1687:
Still nada in NH
[Samsung Galaxy Nexus] WOLF26915:
I found this http://forums.androidcentral.com/verizon-galaxy-nexus/177456-3-clicks-im-4-0-4-a.html it worked for me now i am on IMM76K 4.0.4 :)
[Samsung Galaxy Nexus] Dan76:
Yeah, that's been floating around. It doesn't work for everyone, but it's worth a try!
[Samsung Galaxy Nexus] strongergravity:
Mine actually showed up this morning...here in south-central Virginia. No tricking required. Now I only need to see a unicorn for my bucket-list to be complete. :)
[Samsung Galaxy Nexus] x0lliex:
Worked on my 4th try in CA. Thanks, updated is DLing now.
[Samsung Galaxy Nexus] TheLurg1687:
I tried that about 20 times to no avail... :-(
[Samsung Galaxy Nexus] AntonC:
I received my update last night. Portland, OR
[Samsung Galaxy Nexus] lrs421:
I was pretty happy with the performance of 4.0.2 but 4.0.4 is incredibly fluid. I'm running stock and am very impressed with this update.
[Samsung Galaxy Nexus] robertf57:
Upgrade error?

Iam rooted unlocked but otherwise stock. The OTA update has been downloaded and when I try to install on the phone it re-boots shows the android guy with lue animated thing then he falls over with an erro sign> What do I need to do to get this to actually install. I have repeated it 4 or 5 times

:confused:
[Samsung Galaxy Nexus] oldblue910:
You have to use stock recovery, not Clockwork.
[Samsung Galaxy Nexus] eman3316@optonline.net:
Amazing to see that there are XDA users who were still unrooted and running a stock Rom.

I can understand if this was an HTC phone or Samsung phone, but it is a GNEX! Doesn't it say in the manual that step one is to root before using the phone so you will not lose your data later on?

Anyway, I ran the leaked radio's the last time this update was posted and did not notice any difference from the prior radio's I had running.
[Samsung Galaxy Nexus] efrant:
You have something that is not stock.

Yeah, but he could always install it from the link (instead of OTA) via CWM,

Rooting has no impact on data, or loss thereof. I think you were referring to unlocking the bootloader.
[Samsung Galaxy Nexus] eman3316@optonline.net:
Yeah, I was assuming the unlocking bootloader was understood to be part of the rooting process...But you are correct, that is the actual step that deletes your data.
[Samsung Galaxy Nexus] oldblue910:
Did it ever occur to you that some of us may just simply prefer the stock experience? Root offers me nothing. Once I figured out how to do it, my curiosity was satisfied.
[Samsung Galaxy Nexus] eman3316@optonline.net:
Can't imagine anyone preferring stock. Maybe people just do not know what they are missing? Run AOKP for a day and tell me that the stock experience is better. There are so many features from drop down toggles, to shrinking the size of the Nav bar down that just add to the overall experience of the GNEX.

It was more meant as a joke and not to put anyone down but people really need to give some of these custom Roms a try. I cannot see anyone going back to stock once running these. Oh, I did I mention you can fix the colors of the screen as well. That alone is even worth rooting and flashing!
[Samsung Galaxy Nexus] efrant:
I use a stock ROM as well, but I prefer to have root on a stock ROM so that I can use some key apps for me, such as Titanium Backup, Market Enabler and Quick Boot.

You say root offers you nothing -- do you not find any of the root apps useful? If so, then root would offer you at least a little something... ;)
[Samsung Galaxy Nexus] oldblue910:
Correct. I have no real use for any root app, especially now that ICS can take screenshots. On the contrary, having root annoys me because of the yellow warning you get in the Google Wallet app that you can't get rid of. Plus I consume some digital content like the live TV on the Time Warner Cable app which won't work with root. I know there are hacked versions that work around the root restriction but I'd rather have it just work. In the end, I like to actually use my devices more than **** around with them and part of that is not having to think about root, app hacks, stupid messages and the like. haha
[Samsung Galaxy Nexus] oldblue910:
I don't like AOKP because there is just way too much stuff, most of which I will never use. With stock, less is more, and that's the way I like it. If you like having everything AND the kitchen sink, then by all means enjoy AOKP. I'll stick to the stock experience.

The only custom ROM I ever actually liked was Android Revolution because all its changes are purely on the back end and there are no visual changes over stock.

Bugless Beast was pretty good too, but the there were a few UI customization I didn't like.
[Samsung Galaxy Nexus] eman3316@optonline.net:
Different strokes for different folks. I must say the one thing that would annoy me from running a non-rooted stock ROM is the size of the bottom nav bar. It is such a waste of space and I think it was made way to large. Being able to shrink it makes a huge difference. Also while AOKP may offer a lot, you do not have to make use of all the tweaks to enjoy it.

Also, I was just using that ROM as an example. There are plenty of other Roms worth noting.

I think the most shocking part to me is I thought that XDA folks are all about rooting, and then add the simplicity of rooting the GNEX, it just leaves me surprised people still run their GNEX un-rooted. Especially with Verizons update track record.