yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] jonstrong:
I've rooted, but lean toward tweaking one feature at a time rather than using a complete custom ROM. I've been using IMM76K since it was available, use launchers to tweak the UI, use file explorers that understand root access, install posted apps as system apps when appropriate, etc. With Apex launcher, Beautiful Widgets, Notification toggles and apps like S Voice, my UI is quite nice. Adding in SetCPU let's me tweak performance. So far this general approach lets me do some customizations ...but only those I want to do. Quite happy this way for the moment.
[Samsung Galaxy Nexus] lrs421:
I'm no novice, I know what's out there, this is my 8th or 9th Android device. The Nexus is the one device that I felt was solid enough to leave as is. I don't have time to keep up with the latest roms/kernels/radio combos.

When I first got my phone I ran AOKP for a week, and while it was awesome I prefer to keep things simple. When the new bamf rom drops I will likely try it and the same for CM9 RC1 but stock is my daily driver.

I don't advocate a position either way. While my Nexus is stock my Kindle Fire isn't.
[Samsung Galaxy Nexus] ssbmg:
Worked on my first try in in Denver, CO. Hope this fixes the mic issue.
[Samsung Galaxy Nexus] miketoasty:
That is where you are wrong! It make's me feel like I actually have control over my phone, which we all know isn't true.
[Samsung Galaxy Nexus] adrynalyne:
Well...it does, but not until it is available to everyone instead of select batches.

I/CheckinTask( 2710): Checkin success: https://android.clients.google.com/checkin (1 requests sent)
[Samsung Galaxy Nexus] efrant:
LOL!!!!!!!!!!!!!!!!!!!!!!!!!
[Samsung Galaxy Nexus] oldblue910:
Looking forward to this update!
[Samsung Galaxy Nexus] DroidRC1:
Vzw reps are confirming the roll out!

follow me @DroidRC1
[Samsung Galaxy Nexus] stkiswr:
If you are on a stock rom just reflash the stock rom and don't wipe data. Just caches should be fine. Flash and enjoy the stock kernel. Very easy. No data loss and for sure will be on the stock stuff you want.

Either way the update should target stock 402 roms so you being on stock 404 isn't going to matter if you want this update.
[Samsung Galaxy Nexus] miketoasty:
Just called Verizon and while they couldn't tell me when I would receive it they said that it would be no later than the end of May. But of course they were more than happy to tell me that the RZR update is being pushed right now (Shoving it in my face maybe?).
[Samsung Galaxy Nexus] adrynalyne:
That translates "if I tell him yes, that is a quick way off the call and one more call towards my daily quota."
[Samsung Galaxy Nexus] bostonbassman78:
I read that the RAZR will not see it till late may if its rolling out its a soak test
[Samsung Galaxy Nexus] bostonbassman78:
Go to this thread if u have a rooted razr will help u revert to stock ti get the ota when it comes out

http://xdaforums.com/showthread.php?t=1599234
[Samsung Galaxy Nexus] adrynalyne:
Did you get lost, bro?
[Samsung Galaxy Nexus] adrynalyne:
Look at the forum title.

We user Razrs for skeet shooting here, not discuss updates for them.
[Samsung Galaxy Nexus] JayDaKissEP:
This is regarding the Verizon Galaxy Nexus... What's up with the Razr talk?
[Samsung Galaxy Nexus] axne1:
:mad:Wrong thread dude!

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] dmmarck:
Wait, you can root a RAZR?

;)
[Samsung Galaxy Nexus] spencer88:
I'm looking for the stock 4.0.1 or 4.0.2 ROM but can't seem to locate it. I want to revert to stock so that I can check for the update. Anybody know where I can find it? Quick searching through the dev section didn't reveal anything.
[Samsung Galaxy Nexus] oldblue910:
Check my website. Download fastboot images. http://randomphantasmagoria.com/firmware/galaxy-nexus/i515
[Samsung Galaxy Nexus] tat2messiah:
I talk to Verizon tech support and they have no knowledge of a update to our nexus
[Samsung Galaxy Nexus] adrynalyne:
https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz
[Samsung Galaxy Nexus] TiltedAz:
So much for the promise of no lock-ups. OTA 4.0.4 still loses contact with camera.
[Samsung Galaxy Nexus] androidtx:
Greatly improved reception

4.04 greatly improved my reception. My wife has a droid phone, and her reception is good at our house, and according to verizon we should be in solid 4g coverage. My GN could hold onto 4g for the most part, but there was one room in the house that both 4g and 3g would drop completely and I would have no signal there. After the update, I get 2 bars of 4g in that room, when I never did before. So I know for sure that the reception bars are not just a case of verizon messing with the bars, there has been a solid reception improvement with 4.04, at least in my case. I am really happy, this is the only thing I did not like about the phone was the shoddy reception at my house when I knew it should be better.
[Samsung Galaxy Nexus] adrynalyne:
It won't. We aren't even sure if that is fixable or caused by software.
[Samsung Galaxy Nexus] adrynalyne:
That sounds like a somewhat isolated problem. I've had the camera stop working, but it required a battery pull to fix it because no rom would make it work again.
[Samsung Galaxy Nexus] gfropr:
Use wug fresh nexus utility to return to 100% stock leave your boot loader unlocked, then you can update. I had the same problem when I used the utility that's stickied in development, I think that utility is coded wrong somewhere.
[Samsung Galaxy Nexus] adrynalyne:
No. Unlocking a bootloader is an internal process and it is designed to wipe all of your data. A toolkit won't change that.

The only way to avoid data loss on rooting is to exploit the OS and not unlock the bootloader (which requires 4.0.1, or 4.0.2), or use a backup program and move it out of the sdcard to an external location. Then restore data after the wipe.

Sometimes the unlock process does not wipe data, but that is a glitch and should not be expected to happen every time.
[Samsung Galaxy Nexus] gfropr:
I've had all the same issues since the OTA update, losts calls ( about 5 with 611) , robotic voice, lost data ( no connection) this happens every time I try to use my phone after waking it up, especially during large data transfers. The arrows on the bar will switch from up/down to just up, then the box greys out with an x. I told VZW after my 3rd replacement and they had the nerve to tell me phones are like computers and not every computer is going to perform as good, then she said "my friends have Nexus' and they work great, as she's hearing robot voice and saying she can't understand me in downtown MLPS a full 4g area!!!! They are in TOTAL denial.
[Samsung Galaxy Nexus] gfropr:
I was simply telling him how to get back on the OTA path since he couldn't update, I quoted the wrong post lol, but its the same person. That was his original issue not being able to update. I told him to leave his boot loader unlocked since he already unlocked it.

^thats what I was reffering to, I never told him you can root without losing data.
[Samsung Galaxy Nexus] adrynalyne:
Yeah, mixed signals, wrong quotes, and all that. My bad.
[Samsung Galaxy Nexus] gfropr:
"Its all good in the hood g." - Aqua Teen Hunger force, June 26th!!!!
[Samsung Galaxy Nexus] TiltedAz:
So far I've always been able to recover by powering down. It's only happened once with 4.0.4 and curiously it didn't ask if I wanted to send an error report like 4.0.2 did.
[Samsung Galaxy Nexus] Dan76:
The camera is certainly the least of my worries... mine crashes if used from lock screen, but from normal app it's fine. I'm more worried about the unsolvable mic cutting out / outgoing audio problem with the radios.

Didn't black_man_x say there was a possible fix in 4.0.5 for that?
[Samsung Galaxy Nexus] 3devious:
You know what is really funny? Back in late Dec, VZW said that the signal woes were just a display bug and that when they patched they'd make it so that the bars were more in line with what customers expected to see. (Made me think about Don Draper talking about "expectation management" in Mad Men.) To entertain myself, I looked at the signal strength on my phone, which was showing a nice pretty blue icon showing a full 4G wedge. I then took my hubby's GN that is still on stock 4.0.2 and he has a grey 4G wedge with just the tip of it being blue. For grins, I opened About Phone one both devices and navigated to Status. Both signal strength numbers were the same. My Speedtest.net scores and download times have nit changed. I guess expectations have been managed.

The good news is that I have not been cut off from the Market yet and large downloads have actually been dependable. That is all I really wanted. I suspect that I will still have to troubleshoot the rebooting issue (others still report problems with the phone locking up and such, but I am just glad not to have to explore getting rid of it entirely.
[Samsung Galaxy Nexus] razgriz08:
same damn problem with mic cutting out and people having to call me back...heading to verizon asap to swap it out
[Samsung Galaxy Nexus] Dan76:
Another North Carolina person... this speaks again to the regional tower problem/incompatibility possibility.
[Samsung Galaxy Nexus] spencer88:
Happens in SC too. I was talking to a guy and his phone did he same thing. He was using a thunderbolt though. Its not just this phone.
[Samsung Galaxy Nexus] apaxi:
Agreed. It is definitely an issue in Charleston, SC. Three different gnex phones... same issue (intermittent). Reported to VZW multiple times and they chalk it up to user error. :(
[Samsung Galaxy Nexus] Dan76:
Well, it sounds like Verizon outsources the same builders and used the same parts for their towers in North and South Carolina. And only us the the Galaxy Nexus radios and our experience to prove it.
[Samsung Galaxy Nexus] 3devious:
Does this mean that folks heading to the DNC this August are screwed or is this only GN users?
[Samsung Galaxy Nexus] Dan76:
LOL. Well, it would be only GNex users, although one person with a Thunderbolt reported the exact same symptoms... I haven't seen any reports directly from Charlotte Metro area; as big as that city is, it may not be a problem there.
[Samsung Galaxy Nexus] :
Yup, heard many reports of 4.0.4

NOT

fixing the audio reboot/one-way audio issue, even though Verizon said it would per their documentation. I haven't had it happen to me yet, but I've not used the phone heavily this past weekend so I can't say for sure. It's frustratingly random because I went almost a month without the problem and made quite a few lengthy phone calls with no issue, then it happened a few times one week with different length calls.

I was all ready to chew Verizon out but spousal unit reminded me that I'm eligible for an early upgrade in October. If I have the one-way audio problem again post-4.0.4, then I'm simply going to wait until October and buy a new phone. I'm tired of fighting Verizon so I'll suck it up and deal with it until then.
[Samsung Galaxy Nexus] TiltedAz:
I never experienced the one-way issue prior to this download. But my first call after the 4.0.4 download had my voice echoing loud in my ear and and a brief time when the other person didn't hear anything I said. I killed the call and tried again with no issues. Otherwise calls have been very clear and without issue.
[Samsung Galaxy Nexus] adrynalyne:
Verizon never said it would be fixed. They said one way audio noise would be fixed and largely, it has.
[Samsung Galaxy Nexus] TheLurg1687:
are people still getting updated? Nada here yet. NH.
[Samsung Galaxy Nexus] 3devious:
My husband is still waiting. He's not trying to reset the framework or anything. We're in VA.
[Samsung Galaxy Nexus] a1exus:
did you try this:

Samsung Galaxy Nexus OTA UPDATE (IMM76K) | alexus's blog
[Samsung Galaxy Nexus] martonikaj:
Um. They said they're not going to force it. That link specifically shows you how to force it...
[Samsung Galaxy Nexus] a1exus:
who's "they"? I spoke w/ Verizon and they're pushing this update out as we speak, people getting it left and right and for those who don't you can use that instruction in order to speed this up, you still pullin update from google and that's it.. i've done it on my phone and now i have 4.0.4 :)
[Samsung Galaxy Nexus] efrant:
3devious said she and her husband were not going to force it... and you were telling them to try to force it...
[Samsung Galaxy Nexus] Dan76:
"they" is the XDA user's post that you replied to. 3devious did not want to force the update using the clear data from Google service framework. Shameless link to your own blog though.
[Samsung Galaxy Nexus] a1exus:
oh, ok my bad... i'm not telling anyone to force anythin, its just an option and i took it, you dont have to go same route, feel free to make your own decision as it fits ))
[Samsung Galaxy Nexus] :
We're picking nits here, but yes, they did. Whenever I lose audio, the person on the other end reports a loud clicking noise then my voice is gone. That's what Verizon said would be fixed, so I assumed it would be fixed. Guess that's what I get for assuming.
[Samsung Galaxy Nexus] Yorb:
Got the notification this morning, but so far have been unable to install. Downloads ("IMM75K" I think), reboots, then freezes on the google logo screen. And yeah I've waited, 45 mins. Shouldn't take that long, right? :P

EDIT: It's IMM76K, as you probably surmised. But still can't get past the google logo screen. Pulling battery yields 4.0.2, exactly how it was. Even has to download the update again.
[Samsung Galaxy Nexus] someguy20:
Same here. I saw the update and wanted to get is on asap. I've got a picture of a droid on it's side opened up with a red "!" sign on it. It looks like bad news.

BTW: I had it rooted with the CM recovery on, but no custom ROM.

Edit 1: Pulling the battery did not brick it. Looks like nothing changed on the phone. Still at 4.02, no loss of data.
[Samsung Galaxy Nexus] adrynalyne:
I am sorry, but no they did not.

There was an issue where there were clicks and screeches on the line when initiating a call. Only you would hear it. This is what they were referring to plus there was no mention of call drop outs or microphone fixes.

On top of that, a member here saw this very same problem happen, on an HTC Thunderbolt.
[Samsung Galaxy Nexus] mmedley:
I got the update this morning. I am rooted and my bootloader was unlocked and it installed without issue. I think signal does seem to be much better. I will report back when I get to my typically low signal area and see if it improves. It would always switch from 4G > 3G showing no bars, but would typically still send data and no issues with call signal.
[Samsung Galaxy Nexus] adrynalyne:
Agreed on signal.
[Samsung Galaxy Nexus] 3devious:
My husband got the update OTA with no forcing. Then he says to me "so now what?" I told him he won't notice anything because he doesn't use it much but data might not cut off on him so much anymore. He shrugged and said "oh, OK" and sat it back down on the desk. I haven't had a dropped connection in places that I should have service yet *knock on wood.*
[Samsung Galaxy Nexus] vballrkc:
Ditto for me. Got the update this morning. Installed right away. Not rooted and not unlocked. Just stock.
[Samsung Galaxy Nexus] lrs421:
Dude, your phone is defective. There's a red arrow in your settings menu. I'm going to start a thread about it.
[Samsung Galaxy Nexus] adrynalyne:
LMAO!
[Samsung Galaxy Nexus] Beamer9408:
I'm pretty sure those soft keys don't come stock. Man you got screwed. Call Verizon.
[Samsung Galaxy Nexus] ryancmor17:
Same thing here. I tried re-enabling disabled apps, but that didn't help either.
[Samsung Galaxy Nexus] oldblue910:
Oh, and for all of you haters who are still convinced that Google dropped all support for the CDMA Galaxy Nexus...JBQ has just added factory images for IMM76K to the Nexus images page. You can all go crawl back under your rocks now.
[Samsung Galaxy Nexus] boe:
Did it fix the mic and radio issues - or are the results still mixed?
[Samsung Galaxy Nexus] oldblue910:
Definitely fixed a lot of signal and reception issues. The one-way mic audio cutoff that some people are experiencing has not been fixed, and many believe it's not a phone issue, but a network issue on Verizon's end. It'll be interesting to see how this one plays out.
[Samsung Galaxy Nexus] lrs421:
Cool. Thanks for sharing. Grabbing my PC now!!!
[Samsung Galaxy Nexus] vulturesrow:
I have the same issue. I used Wugs utility to unlock the phone but havent installed any custom ROMs unless Wugs does this and I didn't realize. Anyone have any insight on this issue?
[Samsung Galaxy Nexus] adrynalyne:
Yeah. Hit volume up, then power, and install it via Clockwork, which is hard because it doesn't look in cache. You will need to manually download it.

Or...flash stock recovery.
[Samsung Galaxy Nexus] vulturesrow:
So I take it to mean that Wug's installs a custom recovery then?
[Samsung Galaxy Nexus] adrynalyne:
I don't know. I do not use toolkits at all, so I know exactly what is going on my device. The thing is, that exact behavior happens when you have CM installed and I am pretty sure I saw someone in this thread with CM with that issue. You will know more once you actually get to the recovery interface.
[Samsung Galaxy Nexus] gizmonic:
Yup. no joy here on the update with cm and the phone unlocked. guess I'll just get back into woot's toolbox...
[Samsung Galaxy Nexus] fix-this!:
Didnt fix my signal issues and i just got a replacement device yesterday.
[Samsung Galaxy Nexus] matt30:
Google is being awfully supportive for an "unsuported" AOSP rom.

They just posed the stock imm76k for mysid.

https://developers.google.com/android/nexus/images
[Samsung Galaxy Nexus] oldblue910:
That's because the factory images have absolutely nothing to do with Google dropping CDMA support in AOSP. They will always keep the factory images up to date...they just can't support the devices in AOSP because CDMA devices require proprietary binaries that cannot be open sourced. That is a totally different animal than providing factory images.
[Samsung Galaxy Nexus] adrynalyne:
The only time they don't supply factory images is if they do not build the OTA/roms for the device. Such is the case with yakju variants and mysidspr.
[Samsung Galaxy Nexus] matt30:
Right, but the HSPA phones also have binaries that can't be provided open source (ditto for the gapps). The problem (according to the original google statement) was they they couldn't "provide" these closed source CDMA binaries like they could HSPA ones. Apparently they've found some work around.
[Samsung Galaxy Nexus] adrynalyne:
No, they haven't found a workaround. They are not supplying cdma proprietaries.
[Samsung Galaxy Nexus] matt30:
What do you mean by that? The binaries are contained within the factory images. They don't list it separately (like they do with the GSM ones) but you could just pull them from the factory images. Right?

I'm guessing that GSM props don't check for a google signature unlike their CDMA counterparts? But if that's the case how do you get custom roms with a working phone?
[Samsung Galaxy Nexus] adrynalyne:
They may be contained within factory images, but they are in OTAs Google sends out as well. However, they are not extracting them or packaging them for you. If you extract them, the license violation is all you, not Google.

There are plenty of AOSP How To tutorial threads out there, and a big one on here. That would probably be the best place to continue this discussion.

I will say this: There are no proprietaries that need to be signed to get AOSP working on the Verizon Nexus. Certain things will not work without signing proprietary apks, but main functions (data, phone, mms) will work without re-signing of anything. Google didn't give the whole story; there are blobs that don't need signing, yet also cannot be redistributed.

GSM doesn't have signature checking disabled or even need to check for them because they don't have any APKs needed.
[Samsung Galaxy Nexus] oldblue910:
So now you've got me curious...if data, phone, and s/mms work without signatures, what specifically are the things that WON'T work without signatures?
[Samsung Galaxy Nexus] Stizzo89:
Thanks :D
[Samsung Galaxy Nexus] adrynalyne:
Off the top of my head?

SIM Activations and RTN (radio functions accessible to user).
[Samsung Galaxy Nexus] thelasik:
I installed the OTA update.

Was running CM, and now my phone is no longer rooted! I tried running my Wifi Tether app and it no longer works. Anyone having similar issues?
[Samsung Galaxy Nexus] adrynalyne:
You can't install an OTA over AOSP (CM). It isn't possible.
[Samsung Galaxy Nexus] ryancmor17:
Tried it, says E: Can't open /sdcard/12f.......e7.zip (bad) install aborted. Manually rooted, unlocked boot loader flashed recovery.

Guess I'm off to reflash stock recovery.
[Samsung Galaxy Nexus] adrynalyne:
It was a corrupted download
[Samsung Galaxy Nexus] fix-this!:
called verizon today because my replacement device was having horrid signal issues and battery life with the new ota. did a crap ton of troubleshooting and they are shipping me a droid razr maxx, they say the signal and battery life is much better. i guess im the 10th person to call in today with signal issues with the new ota.
[Samsung Galaxy Nexus] lrs421:
Cool. Glad they found a solution for you. How are they going to fix gingerbread and motoblur?
[Samsung Galaxy Nexus] efrant:
ROTFLMFAO!!!!!!
[Samsung Galaxy Nexus] oldblue910:
Thread over. This dude wins.
[Samsung Galaxy Nexus] fix-this!:
Yeah i know, ill just root it and throw a custom rom on it. Good thing they have gummy and a few aosp roms. Love the nexus but i couldnt use it as a "phone" so its a no win situation. Its the 2nd time ive been cursed by bad radios from samsung.
[Samsung Galaxy Nexus] mmedley:
Well, after a few days of being on the new update I can report that my signal appears to have gotten worse I think. I never hardly had data drops but it occurs a few times a day now. Data connectivity is very intermittent. Often, it takes 2-4 seconds just to process the action to open a thread in Tapatalk (click open and 2-4 seconds later you see the arrows in the signal bars finally show activity). Unlocking the screen also is VERY sluggish. Almost like there is a memory leak or something. Any ideas? I think I might just go back to 4.0.2, but what a pain in the ass to reset the whole phone.
[Samsung Galaxy Nexus] spectrumfox:
You may wanna try booting into Recovery and wipe Cache. If you're running ClockworkMod Recovery, you may want to wipe the Dalvik Cache as well.
[Samsung Galaxy Nexus] ph00ny:
Oddly enough, my nexus is the only samsung device that i'm having issues with radio. All of my other devices including the vzw 7.7 works like a charm even on verizon
[Samsung Galaxy Nexus] Dan76:
Those have different radios. From what I've heard and read on here, the Galaxy Nexus is the only device on Verizon with this specific radio. Hence the isolated problem.
[Samsung Galaxy Nexus] mark manning:
For some of you all having signal issues I found this to be the best answer we have. Its a file I found somewhere on here but can't remember where. After trying all the different radios and patches we have had available this seems to work the best for me.

Its is the FULL 4.0.4 radios and bootloader not just the patches sent out by google. Not sure why this made a difference compared to all of the other 4.0.4 radios but it did for me.

Try at your own risk tho

http://db.tt/DaF3CEhU

Edit: only flashable through a recovery
[Samsung Galaxy Nexus] adrynalyne:
Patches worked ok for me.
[Samsung Galaxy Nexus] mark manning:
To bad your not everyone :p
[Samsung Galaxy Nexus] mwalt2:
Since google released the new factory image for our phone, that would be one easy place to get the radios :).

https://developers.google.com/android/nexus/images#yakju
[Samsung Galaxy Nexus] mark manning:
Not really, you should point out where the radio files are by themselves

Without having to unpack the image.
[Samsung Galaxy Nexus] Beamer9408:
You Sir win the Internets for the day.
[Samsung Galaxy Nexus] evolving:
Did you get lost, bro?

:cool: yeah son! Been better if he had an iPhone.however I enjoyed that line...ok back on topic :rolleyes: