yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bfroehlich:
Make sure you take out the "-w" when executing the "fastboot update" command. The -w flag means wipe.
[Samsung Galaxy Nexus] kakarla87:
Hi There i'm trying to update my phone. N when i download the 4.0.4 file by my google services is about 37.4MB.when i reboot to install it i get a android with "!" exclamation mark. what should i do Please help me.
[Samsung Galaxy Nexus] efrant:
You have the wrong recovery image flashed. You need the recovery from the version of Android that you are currently running (which I believe is ICL53F if I am not mistaken).
[Samsung Galaxy Nexus] onthecouchagain:
Random rebooting from pulling down the notification list is happening to others as well:

http://androidforums.com/samsung-ga...s-off-when-pulling-down-notification-bar.html

... This vexes me, because ICS is supposed to finally bring the stability Android users so want.

Sigh.

EDIT: I see it's been a known issue (http://www.stuff-review.com/2012-01...e-to-plague-the-galaxy-nexus-how-about-yours/) and that, indeed, 4.04 is supposed to fix this. Alas, it's still around. :T
[Samsung Galaxy Nexus] overhc:
I'm still having the issue after the update too. It doesn't happen as often, but it still happens. This is really frustrating.
[Samsung Galaxy Nexus] footboydog:
I was having no signal drops on IMM76D and when I got IMM76I I started to see them. Turning the screen on I saw I had no bars and a little 'x' and then after a second or two the signal would come back. To try and work around this yesterday I set my phone to WCDMA only (it was WCDMA preferred) and I have had no issues since:

Go to the phone app and dial *#*#4636#*#*

Tap on Phone information

Scroll down to the dropdown list called "Set preferred network type"

From the dropdown choose "WCDMA only"

Press home

I am on the UK mobile network three which is pretty much 3G only anyway. Its not a proper fix I know but for me it beats a factory reset.
[Samsung Galaxy Nexus] guard3:
Thanks this sorts out my 3g drops too. now i have to switch to gsm only or wcdma only. i think there is a software bug when device is set to wcdma preferred.

Is there any other shortcut to set device btween wcdma only or gsm only
[Samsung Galaxy Nexus] footboydog:
Use Any Cut in the market. Add the widget to your homepage and choose the phone info activity from the list.
[Samsung Galaxy Nexus] trickyrickxx:
Just got my new sim card and lost signal within a hour starting to hate my phone
[Samsung Galaxy Nexus] NIK516:
I just got the update, GSM gn imported from mobicity to Australia Google build. I'll let ya know if I notice dropout because I did on 4.0.2
[Samsung Galaxy Nexus] [hfm]:
I have not had a reboot since upgrading to 4.0.4. It used to happen once in a while on 4.0.2. Also I had the problem where I would lose connection on IMM76D, it seems to be fixed for me on IMM76I, yet to happen again.
[Samsung Galaxy Nexus] hasher.dk:
I'm seeing reboots too. Quite a few times since upgrading to IMM76I, actually.

But it's not when I pull down the notification bar. Once, it happened when I pressed a button in Facebook. All other times, it has just been in sleep mode, and I only see it because Skype is no longer running. Of course, I've seen it happen a few times...

Funny thing is that it reboots quite fast and does not ask for my pin code.

I'm starting to regret moving from yakjuxw to yakju. The old build had its issues, but it was way more stable.
[Samsung Galaxy Nexus] efrant:
There is nothing preventing you from going back...
[Samsung Galaxy Nexus] bandit_knight:
Is there a way to do it if you hadn't taken a backup?
[Samsung Galaxy Nexus] efrant:
If you haven't done a nandroid backup, you can still go back, but you will have to redo your settings again. You can easily pull all your data in /sdcard to off of your device, and then just flash the ICL53F images. That will get you back. Now you have to set up everything again (home screen icons, email settings, etc...)
[Samsung Galaxy Nexus] sawihsiwi:
Galaxy Nexus CDMA

I am having the same lying bot error when trying recovery mode. I am attempting to install the MoDaCo ROM ([4 Apr Ir13 (IMM76D / 4.0.4 / CDMA + GSM)).

I cannot locate the two files you recommend to delete. I have my nexus connected to a mac, using the Android File Transfer. Cannot find any 'system' folder or mentioned files. Thanks in advance.
[Samsung Galaxy Nexus] efrant:
You will not see those files that way.

Is your device rooted? If yes, the easiest way is to just use something like Root Explorer and delete them.
[Samsung Galaxy Nexus] Rashy:
Thanks for that. It worked, however, for some reason, the update stops in between and gives me an alert symbol (red triangle). It stops responding at that point.

I'm unlocked and rooted, on Yakju build.
[Samsung Galaxy Nexus] sawihsiwi:
Using root explorer I get the following when trying to delete:

"recovery-from-boot.p cannot be delted because the file system is read-only."
[Samsung Galaxy Nexus] efrant:
The /system is mounted read-only by default on Android devices. If you are using root explorer, go to the directory, and you should see a button near the top right saying "Mount R/W". Click it. :)

EDIT: Don't forget to click it again after you finish deleting the files.
[Samsung Galaxy Nexus] sawihsiwi:
Thank you for your help. Problem solved.
[Samsung Galaxy Nexus] sawihsiwi:
Files were deleted but installing ROM fails again as I am unable to get it into recovery mode. Again, lying not with red triangle.
[Samsung Galaxy Nexus] efrant:
As I said before, you need to re-flash CWM after you delete the files.
[Samsung Galaxy Nexus] kakarla87:
Now what should i do, Please help me. I dont have any idea.

Thanks in advance
[Samsung Galaxy Nexus] efrant:
I posted the ICL53F recovery in this thread. Flash that in fastboot mode, and then try the update again.
[Samsung Galaxy Nexus] SirRomie:
It seems that everyone is talking about being on .4 or still on .2. I am still stuck on 4.0.1... does anyone have any information on why this is? I am on yakjuux.
[Samsung Galaxy Nexus] digweed4me:
I am in Texas updated 4.04 2 days ago and I love it. Amazing battery life I got almost 5 and half of on screen time on this new update . No Los at all
[Samsung Galaxy Nexus] adrynalyne:
This.
[Samsung Galaxy Nexus] greeced:
Ya, strange with those Canadian Devices... I had a friend that was stuck on 4.0.1 too... after getting him to do various things, it simply wouldn't update at all...

I finally convinced him to update to 76i 4.0.4 yakju, and he's been happy ever since.

Personally I think all non-yakju/takju devices should make the switch... I was apprehensive myself about doing it, but I'm completely stock 4.0.4 now (even with the LA2 radio) and have been loving it.

Seems like there really isn't any need for all these variants... not that I can tell anyway...
[Samsung Galaxy Nexus] SirRomie:
I have been considering making the switch, but it seems that being stuck on 4.0.1 is my only concern. If I am updated eventually I would not mind as much but I have no guarantee that I will even get this update as it seems that yakjuux nexus owners have the same problem as me. Correct me if I am wrong but most never even got the update to 4.0.2. This is my biggest concern. It is rather frustrating coming from another android phone that ran a lot smoother and this one is 100% stock android and is laggy and buggy.
[Samsung Galaxy Nexus] greeced:
Well, I had 4.0.2 and was never stuck on 4.0.1, So I'm wondering if it got pulled somehow...

Yet both my friend and his girlfriend, like you, were stuck on 4.0.1. His main concern was signal issues and the like...

He then switched to 76i with efrants instructions and says the phone hasn't cut out on him since, the rotating is definitely much nicer and his GNex experience is overall better.

So there was a 4.0.2 update way back for the Canadian Devices (I got mine when I first bought it and turned it on back in January/February I think), and I got it OTA... no idea why its not pushing through now.

And consequently, it could be the very reason why those of you who are on 4.0.1 are not receiving 4.0.4 at all.
[Samsung Galaxy Nexus] SirRomie:
I doubt that the support for this device would just stop. It is rather annoying waiting for this update when I bought a Nexus so I would get the updates first. Yet for some reason their are two versions of the same phone and one has yet to get either 4.0.2 or 4.0.4. This waiting game is a little concerning.
[Samsung Galaxy Nexus] trickyrickxx:
Does anyone know if Google will be sending out another update for the people who wasn't helped with this newest update if so do we know when as I lost signal around 20 times today and do really like the phone
[Samsung Galaxy Nexus] tneRRot:
I was stuck on yakjuux 4.0.1 like you and made the switch to yakju 4.0.4. All I can say is 4.0.4 runs like a dream compared to 4.0.1. Battery is way better, no more crashing and most (not all) of my signal problems are gone. And I received the OTA IMM76I update promptly - no waiting. Yesterday I went to AOKP M5 and am loving it even more.

Make the jump, if not to a custom ROM at least go to Yakju. You will like your phone again :)
[Samsung Galaxy Nexus] overhc:
Those of you that are having problems with data being dropped, could you visit the android bug tracker and star it? It's issue 28474. I'd post a link but apparently I haven't posted enough here yet.

Sorry if this has been posted already. Hopefully they will see this and release a fix soon.
[Samsung Galaxy Nexus] matthewr87:
I am still stuck on 4.0.1 as well. Bought my phone in February and have not received any notifications. My cousin bought his in January and at the end of March randomly received 4.0.2 OTA. Now he doesn't have NFC. I too am disappointed that Canucks are getting shafted once again!
[Samsung Galaxy Nexus] Matridom:
Blame this one on Samsung, they are the ones that made the variants, and google was not even aware of it until after the phones shipped. Switch to yakju (it's easy) and be done with the samsung BS on delayed updates.
[Samsung Galaxy Nexus] dewess99:
This interesting. How do you know this?
[Samsung Galaxy Nexus] Matridom:
when it was first discovered, one of the Google programmers commented on it. I'll see if i can dig it up.

Ask, and ye shall receive:

http://groups.google.com/group/android-building/browse_thread/thread/2dde45a058a737b9
[Samsung Galaxy Nexus] dewess99:
Thanks. When I bought my nex I was´t aware of the build difference. Also it is really strange that Samsung does different version. Do you know why?
[Samsung Galaxy Nexus] Matridom:
Regional differences/Carrier requests

For example, the modem in yakjuux (canadian) is different then the AOSP version. Carriers might request this for a variety of reasons. They could want the modem throttled to stem network congestions, they may want the modem tweaked to give best performance on their network. Application may be added/removed based on carrier requests, Features might be removed (Tethering?) etc.

My view on it though is that it comes down to carrier certification. If samsung is more willing to cater to the needs of a provider, certification will happen more quickly and as such, get wider peneration into various countries more quickly. In the US and Canada (and i'm sure elsewhere), we mostly buy phones on contract with a carrier subsidy, so it's *very* important to have a phone in said carriers store to make money.

I tend to do a lot of research into a phone i'm planning on getting so that i know what to expect. For example, i knew to expect something other then yakju, so on first power-up, i flashed it (the original OS never booted once).
[Samsung Galaxy Nexus] efrant:
No one (that I'm aware of anyway) has done any comparison of the builds to see what the actual (if any) differences are.

Someone took a stab at it in this thread, but didn't get to the system partition...
[Samsung Galaxy Nexus] Matridom:
I can't seem to find the reference link, but the same google developer went on to say that they where regional builds.
[Samsung Galaxy Nexus] efrant:
I'm not disagreeing with you. All I'm saying is no one has indicated what those regional differences are (if any).
[Samsung Galaxy Nexus] bozzykid:
Since Google only releases the yakju build no one can say except Samsung and the carriers. And they will never release this information.
[Samsung Galaxy Nexus] efrant:
Did you even look at the link I posted here:

I wasn't suggesting that Samsung or the carriers will release any info. All I was saying, is that it would be good if someone compares say, a yakju ICL53F and a yakjuux ICL53F, much like what nexusfracker did for the boot and recovery images in the thread I linked above (look at post #11 here). But do it for the system and data images as well.
[Samsung Galaxy Nexus] Theshawty:
To be honest, I don't think there are any changes at all. Just Samsung wanting control of the phones they make. If you ask Samsung, they say Google control the updates and if you ask Google, they say Samsung manage them.

A dead end is what it is.
[Samsung Galaxy Nexus] Pentium:
When I got my Galaxy Nexus, I didn't know all that information about Samsung build as I was using a Nexus One and Nexus S before I thought it was just like them and everything come directly from Google...

but when the first update came out, and I never got it....I searched and found that my build is yakjuxw from Samsung....so I switched to Google yakju directly and the updates just come in time!!

Samsung takes forever to push an update! their entire line is still on Gingerbread!
[Samsung Galaxy Nexus] diegodbm:
Lag lag everywhere... with new ota I also have lag...

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] SKYLINESSUCK:
The DoCoMo ROM was certainly different.
[Samsung Galaxy Nexus] jiangheng:
3g data signal seems improved for me, much less connection loss time then before.
[Samsung Galaxy Nexus] ruimoura:
Just got the update last night. Vodafone Portugal.
[Samsung Galaxy Nexus] dynamikd:
Interestingly enough, I never experienced any drop calls with this update and when I went into "Phone Information" WCDMA was already chosen for me.
[Samsung Galaxy Nexus] NCguy:
I'm on 4.0.2 and mine is set to gsm/cdma auto (PRL)?

I have no idea what this means but my calls are ok. This is the gsm phone so why is it referencing cdma?
[Samsung Galaxy Nexus] Andie00:
Is anyone still getting data drops/connection issues after this OTA? I just noticed that I dropped my connection again (makes two) since I updated to IMM76I. :-/
[Samsung Galaxy Nexus] NCguy:
The short answer is yes. Some people are. I sense it is less than before the update and no one can determine what differentiates the victims.
[Samsung Galaxy Nexus] Andie00:
Thanks for the quick confirmation. Makes me feel a little better knowing I'm not the only one still having connection issues albeit less frequent.:p
[Samsung Galaxy Nexus] Theshawty:
I can't tell if my connection issues is because of this or the ****ty reception my carrier has in this area.

Makes me feel like I'm living in a bunker.
[Samsung Galaxy Nexus] NCguy:
No problem. I've been following it closely. I am on 4.0.2 with no connection issues and trying to determine when it's safe to take the plunge to 4.0.4. :)
[Samsung Galaxy Nexus] twitchyzero:
hello

less than a week ago I was on 4.0.2 yakju build then it prompted the 4.0.4 IMM76I update OTA. My network is Rogers.

Since then I've lost my 3G data connections three times and the only way to get it back is to reboot the phone. Any temporary fix or must I wait for Google?

Very disappointed considering this build was supposed to fix the signal drop issues.
[Samsung Galaxy Nexus] NCguy:
Why don't you just flash back to 4.0.2?
[Samsung Galaxy Nexus] Sveke:
Try toggling the data on the power widget. Way easier than a reboot.
[Samsung Galaxy Nexus] mike freegan:
Why is there not more uproar about this?

This is much, much more than a slight inconvenience as I rely on IM and email. Rebooting my phone 6 or 7 times a day is not much fun.

Honestly, I WISH this was like antennagate so I could just hold my phone differently to make it work. It's been months now. I'm embarrassed for Google.
[Samsung Galaxy Nexus] efrant:
What is strange is that it doesn't affect all users on 4.0.4. Myself, along with others, have never had this issue. The logical conclusion would be that there is something in the combination of 4.0.4 + one's network + installed apps + whatever else, that is causing it. It's not 4.0.4 by itself.
[Samsung Galaxy Nexus] NCguy:
Do you agree that this is probably why the non-yakju 4.0.4 is yet to be pushed?
[Samsung Galaxy Nexus] efrant:
It would be pure speculation on my part, but yeah, what you said seems logical.
[Samsung Galaxy Nexus] mike freegan:
I had an almost identical problem with my SGSII on the 3 network here in the UK. Data would freeze when switching between masts or connection types. It was much worse with custom ROMs than the stock (supposedly unaltered) 3 rom.

They finally conceded that it was a known incompatibility problem that only affected a few providers, and that after 5 months, Samsung were not making an effort to fix it as it was so intermittent and on so few networks worldwide. I got a refund.

EDIT: If it helps anyone, since 4.0.4 this now happens to me almost every day when I'm driving to and from work. With my phone on standby, going from HSDPA > no signal > HSDPA. The phone re-connects but data doesn't. It seems to be worse when I have bluetooth A2DP streaming to my car stereo.
[Samsung Galaxy Nexus] micflair:
Add me to the problem list, never had the 3G drop out issue on 4.0.2, since upgrading to 4.0.4 I get it 2 or 3 times a day and only reboot fixes it. Pain in the ass.
[Samsung Galaxy Nexus] dubeyy:
+1

I'm getting it sometimes too on 4.0.4 IMM76I if my screen is off for extended periods of time

I'm also using AOKP Milestone 5 not sure if that has anything to do with it
[Samsung Galaxy Nexus] micflair:
Ahhh, funny you should say that - when I goto work in the morning its fine, when I get a break about 4 hours later the 3G is gone. Its always after my screen has been off for ages also.. Hmmm!
[Samsung Galaxy Nexus] NCguy:
I wonder if this happens in the US? Are you in the US by chance? Seems like most of the people I've seen reporting this are in Europe. That may be because that's where the most gsm GNs have been sold.
[Samsung Galaxy Nexus] omrij:
I still have serious signal issues

It drops several time a day

May have to revert to 4.0.2.

Hope that Google will release a new fix soon
[Samsung Galaxy Nexus] micflair:
Nah mate Im in the UK. Damn its a strange fault!
[Samsung Galaxy Nexus] acstua:
I've started getting this quite abit now ever since going to IMM76I

Its bloody annoying :/

i thought this was the version that fixed signal drops etc :/

had no data connection this morning, and hadnt recieved any texts..

took me reconnecting to the network to get it to reconnect to the data network and recieve my missing text messages
[Samsung Galaxy Nexus] demeics:
Same shait for me , I hate it .

Fking nexus on the brilliant Vodafone network
[Samsung Galaxy Nexus] efrant:
I think the OP should change the title of the thread. There is no need to mention "Fixes signal drops!"
[Samsung Galaxy Nexus] Reviz:
I've experienced signal drops exclusively with 4.0.4 roms (stock or not).

Now I'm on a stock 4.0.2 and everything works well.

I think that I will sell the galaxy nexus :( is this issue still remain in the next factory image release.

I've bought a Google phone to be the first to get the updates and now I can't update...
[Samsung Galaxy Nexus] adrynalyne:
Stay away from Nexus devices then, because they don't speed 6 months testing releases before updating you...

No company is perfect.

HTC for example broke voice mail notifications on the Thunderbolt...took them 1-2 months to fix it, and they pulled the OTA the second day it was released.

The fact the signal drops are not happening to everyone leads me to believe that it might be carrier specific. Wouldn't you agree? What other reason would it be?
[Samsung Galaxy Nexus] Reviz:
I agree with you but however we are talking about expensive phones. For me, this issue is a big problem, i would like to install some 4.0.4 custom rom but I can't...

I just changed phone company and there is no change about the signal drop. (Wind and 3, I'm from Italy).
[Samsung Galaxy Nexus] adrynalyne:
Just curious...were you on a non-yakju rom when you first got the device? Like yakjuxx (Insert xx variant).
[Samsung Galaxy Nexus] tneRRot:
I agree this is frustrating. Being my first android phone I've been having loads of fun with it but these data drops are super frustrating. Especially being so wide spread. Even some comments from google on possible causes would help give some confidence that a fix is coming...
[Samsung Galaxy Nexus] adrynalyne:
Someone on a 4.0.4 rom try a 4.0.3 kernel and see if it fixes the signal drops.

Just temp boot it so that on reboot you go back to your old kernel.

adb reboot bootloader
fastboot boot boot.img
[Samsung Galaxy Nexus] efrant:
I would, but I'm not having any signal drops... :D
[Samsung Galaxy Nexus] adrynalyne:
LOL!:D
[Samsung Galaxy Nexus] Reviz:
I really don't know, I got the NEW phone (GSM) with the 4.0.1, instantly updated to 4.0.2 on first boot.

Then I unlocked/rooted it and tried some custom rom or the stock IMM76I...

I made any possible test, but nothing seems to work...

If I want to use the phone I have to keep a 4.0.2 (i tried only the stock one).
[Samsung Galaxy Nexus] NCguy:
I think it is still a mystery. I can't seem to find hardly any complaints from 4.0.4 US users including the new play store phones. That would imply "region" specific but I suppose it could be carrier. :confused:
[Samsung Galaxy Nexus] Armuro:
I'm on 4.0.4 IMM76I in US, on T-Mobile network in LA area. I'm also plagued by this issue. Go to below link & follow the status on this issue:

http://code.google.com/p/android/issues/detail?id=28474

This is a freaking annoying issue. Have to toggle airport mode couple times to get data connection back... tho there's report that using custom kernel, there's no such issue...

Fingers crossed that Google fix this asap...
[Samsung Galaxy Nexus] adrynalyne:
The issue you linked is sprinkled with folks that had it fixed in IMM76I. Makes sense a kernel would fix it, considering IMM76I is a kernel fix.

Try the 4.0.3 kernel I linked.
[Samsung Galaxy Nexus] bogdi1988:
Try this one:

http://xdaforums.com/showpost.php?p=24308497&postcount=362

Seems a lot more stable for me now after I flashed this...
[Samsung Galaxy Nexus] NCguy:
Thanks for that info. Looks like US users are also victims:(. I still haven't heard mention yet of a play store phone with this problem and I believe most of them are on the latest 4.0.4. Wonder if that new play store rom is really just a yakju clone with wallet?
[Samsung Galaxy Nexus] Chaosin1983:
I have complete loss of signal even after IMM76I...it works for a while and then it drops and can't get signal at all...

Android : 4.0.4

Baseband: i9250XXLA2

Build: IMM76I
[Samsung Galaxy Nexus] NCguy:
Do you mind if I ask which country you operate your phone?
[Samsung Galaxy Nexus] Chaosin1983:
Nicaragua, carrier is Movistar.

Here's my story:

Everything was working perfectly until about two weeks ago, when out of the blue my phone started loosing signal, and it's been hell ever since... it started as a few minutes, then a few hours, then full days without signal, I was running AOKP M5+Franco Kernel...I tried every radio available, with no luck, so I went back to google stock images..

Tried 4.0.1...works for a while then signal drops randomly.

Tried 4.0.2...works for a while then signal starts to drop randomly, a bit less than with 4.0.1, the signal drops and comes back quickly after a few seconds. Also on my latest try, the screenoff signal drop started happening.

Tried 4.0.4 (IMM76I)...works for a while, then randomly looses signal and it never comes back, I have to reflash the image for the signal to come back. I just tried reflashing 4.0.4 and it has been working so far, only a couple of drops, but still it is not a solid signal...who know how long it will last this time.