Develop Bugs

[Q] Having Signal Issues with UK GSM Galaxy Nexus on TMO Network

I've been reading this forum for the past two days trying to see if there is a similar thread with this issue. Please point me in the right direction if there is a similar thread resolving this issue (this forum is colossal!).
I recently bought a UK version GSM Galaxy Nexus running Modaco 4.0.2 Ir8. I'm using it on T-Mobile's network (The GN is replacing my HTC Sensation).
The gentleman that sold it to me had already unlocked, rooted, and flashed it with Modaco. It works blazing fast. The only thing is that when ever I make a phone call it literally drops in less than 5 minutes. The signal seems to be switching like crazy from 3G to HSPA+ as well.
I've called TMO and they have no clue what the issue is (4 different reps told me 4 different things from needing to factory reset to the towers being down etc.).
Again the phone works great besides the fact that I can't make a phone call for more than a couple of minutes before it drops.
Has anyone seen this with their GN? Is it the phone? The Mod? Are T-Mobile's towers not able to pick up this phone's radios because it's from the UK?
How can I go about fixing this (Factory reset? etc.)? I'm literally about to factory reset this thing this morning when I get home from work.
I don't really have too much experience as far as rooting goes but willing to learn and get this issue resolved.

What radio version are you using?
I'm on T-Mobile and xxkk6 works well for me.
If you don't know what you have, I suggest u go to the dev section and start reading for a while

xxkk6 at the least should be on there. i think there is xxkl7 possibly. the xxkk6 is the stock radio, but if there is a kk7 or kl7 might want to try that as it would be a later version.

How can I tell which radio version I'm on and does it give me the option to switch it?
dwang said:
What radio version are you using?
I'm on T-Mobile and xxkk6 works well for me.
If you don't know what you have, I suggest u go to the dev section and start reading for a while
Click to expand...
Click to collapse

Jjonlife said:
How can I tell which radio version I'm on and does it give me the option to switch it?
Click to expand...
Click to collapse
Settings, about phone.
I had similar problems until I switched to KK6.
This thread has all the different basebands:
http://forum.xda-developers.com/showthread.php?t=1405345
Sent from my Galaxy Nexus using XDA App

I've been reading the forum for a minute and haven't noticed any threads regarding this issue. Bear in mind this forum has like 1 thousand threads to go over.

Jjonlife said:
I've been reading the forum for a minute and haven't noticed any threads regarding this issue. Bear in mind this forum has like 1 thousand threads to go over.
Click to expand...
Click to collapse
I was using KK1 before and it was absolutely fine until about a week ago, then I started to get dropped calls etc.
Sent from my Galaxy Nexus using XDA App

Jjonlife said:
How can I tell which radio version I'm on and does it give me the option to switch it?
Click to expand...
Click to collapse
I'm on xxk1. How do I switch to kk6?

Thanks for sending me that link. Which baseband set up would be good for the US (NYC specifically). They all look like they are designed for European areas.
And once I put in my Sim card, why didn't the phone just figure out with Radioband to attach itself to?
pnnorth said:
Settings, about phone.
I had similar problems until I switched to KK6.
This thread has all the different basebands:
http://forum.xda-developers.com/showthread.php?t=1405345
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse

Jjonlife said:
Thanks for sending me that link. Which baseband set up would be good for the US (NYC specifically). They all look like they are designed for European areas.
And once I put in my Sim card, why didn't the phone just figure out with Radioband to attach itself to?
Click to expand...
Click to collapse
Basebands beginning with UG are for north America. I think there are a couple of threads in the dev section about UG basebands, it might be worth have a look at those.
KK7 Thread:
http://forum.xda-developers.com/showthread.php?t=1382699
Sent from my Galaxy Nexus using XDA App

Thanks for the link. After reading through a couple of pages I'm starting to realize that I have no idea what the hell is going on with switching radio bands. Even worse, I have not read about any instances where one or the other will work very well in NYC (my area).
Is there a grid which shows which radio band is for which area? Anyone know of anywhere that shows the step by way to do this?
pnnorth said:
Basebands beginning with UG are for north America. I think there are a couple of threads in the dev section about UG basebands, it might be worth have a look at those.
KK7 Thread:
http://forum.xda-developers.com/showthread.php?t=1382699
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse

Jjonlife said:
Thanks for the link. After reading through a couple of pages I'm starting to realize that I have no idea what the hell is going on with switching radio bands. Even worse, I have not read about any instances where one or the other will work very well in NYC (my area).
Is there a grid which shows which radio band is for which area? Anyone know of anywhere that shows the step by way to do this?
Click to expand...
Click to collapse
See section 3 in the first post of this thread for a step by step guide:http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my Galaxy Nexus using XDA App

I appreciate that. Will be looking into it later this morning when I get off work.
For anyone who had to do this process: Is this a normal thing when rooting and flashing, to have to find a better baseband etc.? Is it because my phone is a UK version that TMO is having an issue dropping my calls?
And lastly, anyone know what the best baseband/radio is suitable for NYC? And why doesn't the phone just figure out which is the best baseband?
pnnorth said:
See section 3 in the first post of this thread for a step by step guide:http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse

Jjonlife said:
I appreciate that. Will be looking into it later this morning when I get off work.
For anyone who had to do this process: Is this a normal thing when rooting and flashing, to have to find a better baseband etc.? Is it because my phone is a UK version that TMO is having an issue dropping my calls?
And lastly, anyone know what the best baseband/radio is suitable for NYC? And why doesn't the phone just figure out which is the best baseband?
Click to expand...
Click to collapse
the baseband should work. it's gsm, the world standard. but i'm guessing since i don't know exactly what is tweaked, but that the specific baseband for your region will bias your phone for the known networks. ugkk7 works great for me. atnt. i think there is a ugkl6 or 7. sometimes you have to test them. some will work better for others. some will work great and not eat battery. if it eats battery, try another one. i think samsung is decent about releasing different radios for different regions. it can be confusing. now when it's comes to updating their roms, that is a different story.

Ok,
The baseband def has to be affecting my battery. I'm getting not even 10 hours on a full charge from moderate use.
I don't really know exactly what the first owner did to it, only what he told me.
My plan is to bring it back to factory settings (found an article about how to restore the GSM version, but have yet to find any youtube videos abou it....I only see LTE videos on rooting and unrooting, and I'm not sure if it's the same process so I'm not touching those).
If that doesn't help it then I'll go about flashing and changing the baseband.
Again this whole baseband business is really new to me. The input you guys have been giving so far is much appreciated.
pukemon said:
the baseband should work. it's gsm, the world standard. but i'm guessing since i don't know exactly what is tweaked, but that the specific baseband for your region will bias your phone for the known networks. ugkk7 works great for me. atnt. i think there is a ugkl6 or 7. sometimes you have to test them. some will work better for others. some will work great and not eat battery. if it eats battery, try another one. i think samsung is decent about releasing different radios for different regions. it can be confusing. now when it's comes to updating their roms, that is a different story.
Click to expand...
Click to collapse

Update:
Ended up coming home early from work and staying up all morning trying to figure this out. I decided on using this link first: (http://www.addictivetips.com/mobile/restore-galaxy-nexus-to-stock-how-to/)
to re-lock. That took about 4 hours of troubleshooting and getting to know the lingo and terminology. Then from a combination of other youtube videos I spent another 4 hours trying to figure out how to lock the bootloader. Believe it or not the Xda link about this (http://forum.xda-developers.com/showthread.php?t=1392310) saved me from losing my mind. I literally didn't go to sleep until I made sure I brought the phone back to factory settings.
After I finally got the phone back to factory settings (believe me, it wasn't fun figuring this out especially when I've never rooted before) I noticed the wifi wasn't working, or had a very weak signal. Content with the phone at least being back on factory settings and locked, I go to sleep and wake up today seeing the same issue with the wifi (mean while, I now have good signal/service...didn't even have to mess with the baseband radio config).
I restart the router in our house and power down the phone and restart. Problem fixed.
Not really sure why or how, but bringing the phone back to factory settings seems to make it work just as fast as it worked when Modaco Ir8 4.0.2 was on it. Except now I have amazing Service signal.
I can honestly state that rooting really isn't for me especially with the notion that with every new mod that comes out you have to be flashing on a constant basis. Even though I almost lost my mind trying to figure this out, I would still rather have this approach vs Apple's walled garden approach though. Any day.
One of the reasons I like the Nexus line of phones is that it's pretty much the only Android phone that gets all the updates first and on a constant basis. Which makes it such an awesome phone in that it's also the phone that Google allows any and all capabilities to be customized. I have true respect for all the devs out there who attack this stuff daily.
Just be sure to get enough exercise in and healthy meals along with rest lol.

Jjonlife said:
Update:
Ended up coming home early from work and staying up all morning trying to figure this out. I decided on using this link first: (http://www.addictivetips.com/mobile/restore-galaxy-nexus-to-stock-how-to/)
to re-lock. That took about 4 hours of troubleshooting and getting to know the lingo and terminology. Then from a combination of other youtube videos I spent another 4 hours trying to figure out how to lock the bootloader. Believe it or not the Xda link about this (http://forum.xda-developers.com/showthread.php?t=1392310) saved me from losing my mind. I literally didn't go to sleep until I made sure I brought the phone back to factory settings.
After I finally got the phone back to factory settings (believe me, it wasn't fun figuring this out especially when I've never rooted before) I noticed the wifi wasn't working, or had a very weak signal. Content with the phone at least being back on factory settings and locked, I go to sleep and wake up today seeing the same issue with the wifi (mean while, I now have good signal/service...didn't even have to mess with the baseband radio config).
I restart the router in our house and power down the phone and restart. Problem fixed.
Not really sure why or how, but bringing the phone back to factory settings seems to make it work just as fast as it worked when Modaco Ir8 4.0.2 was on it. Except now I have amazing Service signal.
I can honestly state that rooting really isn't for me especially with the notion that with every new mod that comes out you have to be flashing on a constant basis. Even though I almost lost my mind trying to figure this out, I would still rather have this approach vs Apple's walled garden approach though. Any day.
One of the reasons I like the Nexus line of phones is that it's pretty much the only Android phone that gets all the updates first and on a constant basis. Which makes it such an awesome phone in that it's also the phone that Google allows any and all capabilities to be customized. I have true respect for all the devs out there who attack this stuff daily.
Just be sure to get enough exercise in and healthy meals along with rest lol.
Click to expand...
Click to collapse
some people actually recommend factory resetting your device from the get go. i would, but i always just run with the hardware just to make sure the hardware and stress i throw at it will handle all the roms and stuff. and to exchange my phone if finding there is a problem.

Good to hear that you got it sorted out in the end
Sent from my Galaxy Nexus using Tapatalk

Rooting/Flashing is great IMO for people who will never have the luxury of getting updates like Nexus phones get. Take control in your own hands on when you decide you want to update(s) etc.
I'm sure any Devs out there (like on this forum) also love tinkering. To each his own.
pukemon said:
some people actually recommend factory resetting your device from the get go. i would, but i always just run with the hardware just to make sure the hardware and stress i throw at it will handle all the roms and stuff. and to exchange my phone if finding there is a problem.
Click to expand...
Click to collapse

Indeed. I def learned a lesson: Never let anyone ever root your phone for you. The guy who rooted it for me was nice enough to say I could email him for questions but the more I kept emailing him the more I could tell he was probably getting frustrated at all my worrisome questions ("I'm dropping calls", "Is it because of the rooting?", "My wifi isn't working", "is it because of the rooting?..." etc.).
Just glad to know there are tons of available options for one to seek out help when issues like this arise.
pnnorth said:
Good to hear that you got it sorted out in the end
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse

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

Hi everyone. I, as many others, have been having an issue with my microphone cutting out during a phone call. I have a roooted Verizon Galaxy Nexus running the 4.0.4 leak, but it appears that for everyone who is having this issue it doesn't matter which ROM you're running or even if you're rooted or not.
[EDIT]: It per one of the posters below, this is not so much a "microphone" issue as it is an "outbound audio" issue. Unfortunately I can't edit the subject name to refer to this, but for me personally when I've been doing google searches on this issue the first word that came to mind anyway was the word "microphone" or "mic" anyway.[/EDIT]
People have been trying different things like flashing different radios, muting and unmuting, turning off voice privacy, etc., but it seems that nothing helps. Not even several hardware replacements or sim card replacements.
However, I did notice a pattern from different forums, etc. It seems that some people either have the problem all the time, or not at all, and it seems that some people reported that traveling to different metro regions affected whether or not they had the issue.
So I was curious to see if the pattern has to do with geographical location as an issue with Verizon's network, vs. hardware/software issues.
This poll has 50 possible answers, 1 for each state. Please answer this poll ONLY if you ARE experiencing this issue, and please only vote for your state if you live in the state's capital. For example, I live in the Denver metro area, so I would vote for Colorado. However, if I lived in Fort Collins or Grand Junction, I would NOT vote at all.
If you have traveled and visited another state's capital and have had this issue there, you can go ahead and vote for it as well.
It will be interesting to see if we have a lot of hits in certain major metro areas and none in others.
[EDIT2] Also, if you don't have the problem at all, go ahead and post a comment with your location. In fact, it would be interesting to see if people don't have the problem but others in the same city do. [/EDIT2]
Thanks!

I thought I had this issue just turns out my pinkie was covering the microphone its king of poor positioning watch, the way u hold the phone after changing the way I hold it no one complains they can't hear me
Sent from my Galaxy Nexus using XDA

TLDR: I kept having people telling me that I sounded like a robot.
Sent from my Galaxy Nexus using XDA

I had this problem on back to back to back phone calls this morning. Horrible.
Sent from my Galaxy Nexus using Tapatalk

My wife and I are both having the issue in Richmond, VA but I could only vote once for myself. She has reverted to an old droid x as she cant rely on the phone anymore.

Might be a little late, but maybe we should collect ZIP codes instead? Then we could use this tool: http://batchgeo.com/

Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Sent from my Galaxy Nexus using XDA

I voted. I'm in South Carolina. I'm pretty sure it's NOT a regional problem though.

twiztidninja said:
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
If holding the phone different worked for you, then you don't have the issue this is referring to. This issue can happen with a wired headset, Bluetooth headset, on speaker phone, which none of these would be affected by how you are holding the phone considering you aren't using the mic on the phone. The people on the other end hear a series of clicking sounds, then no audio.

twiztidninja said:
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I realize you're trying to help, but you really don't understand the issue. The OP really didn't describe it properly, as it's not a "microphone" problem, but rather an "outbound audio" problem. I use mine at work as a speakerphone with it sitting on my desk, and I lose outbound audio all the time. Others have the problem with a bluetooth headset. I don't doubt that there are some people who have had an issue with covering the microphone hole, but that is not what this thread is about. This is an ongoing issue that people have been troubleshooting for months, and Verizon/Samsung is supposedly working on a software fix to resolve it (I'm not holding my breath).

I had the same problem on my 2 rogers GNs(GSM version)
after I upgrade my baseband to i9250xxkk6, the problem gone

I like the OP enthusiasm, but I don't think you will be able to glean any info on location. Owners are too spread out. Maybe in a few months.

I'm in Raleigh, NC.
I got my phone on release day and noticed this problem a few days later. I've since replaced the phone, then the SIM card (a theory that it was SIM-card related was floated over at AF).
After changing the SIM card the problem seemed to go away for a couple of weeks, but it came back with a vengeance.
I hate the idea of getting a "refurb" from Verizon (I put refurb in quotes because, based on the FIVE refurb'ed Incredibles I had, I'm pretty sure they don't do anything except replace the glass if it's scratched), but I guess a functional refurb would be better than an aggravating semi-functional new phone.
twiztidninja said:
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Click to expand...
Click to collapse
I can't help but be reminded of Steve Jobs.... "You're holding it wrong!"
I'm glad your phone is working properly but, as others have noted, this is most definitely not the problem we're talking about.

gabe23 said:
I realize you're trying to help, but you really don't understand the issue. The OP really didn't describe it properly, as it's not a "microphone" problem, but rather an "outbound audio" problem. I use mine at work as a speakerphone with it sitting on my desk, and I lose outbound audio all the time. Others have the problem with a bluetooth headset. I don't doubt that there are some people who have had an issue with covering the microphone hole, but that is not what this thread is about. This is an ongoing issue that people have been troubleshooting for months, and Verizon/Samsung is supposedly working on a software fix to resolve it (I'm not holding my breath).
Click to expand...
Click to collapse
Thanks for clarifying, I edited my original post, unfortunately I can't edit the subject name, but you're right, it's outbound audio and not mic. Thanks again!

adrynalyne said:
I like the OP enthusiasm, but I don't think you will be able to glean any info on location. Owners are too spread out. Maybe in a few months.
Click to expand...
Click to collapse
You're right, I was caught up in it at the moment and thought it would just be interesting to see how the issue maps out, but this little poll in no way is a troubleshooting tool, more of a type of infographic maybe?
The only fix is going to be a software update from el goog. can't wait for it!!!

I just got off the phone with Tech Support about this.
The Level 2 agent found an internal support document about the problem and read me what it said for the fix.... It says that the upcoming software release is going to cover this. It goes on to say that the tentative (dammit) release date for the software release is late March.
I don't want to trade in the new phone that I've babied since day 1 for a refurb of unknown quality if a fix is coming within the next couple of weeks.
If they don't release the update soon (which wouldn't surprise me at all), I'll probably just flash a new ROM & radio.

Flashing a new rom/radio does not help. I'm running nothing stock (leaked radios, CM9 Kang Nightly, Franco Nightly) and I still have this issue.

Good to know I'm not alone, Minnesota is currently winning! :-\ :-(

AnotherHiggins said:
I just got off the phone with Tech Support about this.
The Level 2 agent found an internal support document about the problem and read me what it said for the fix.... It says that the upcoming software release is going to cover this. It goes on to say that the tentative (dammit) release date for the software release is late March.
I don't want to trade in the new phone that I've babied since day 1 for a refurb of unknown quality if a fix is coming within the next couple of weeks.
If they don't release the update soon (which wouldn't surprise me at all), I'll probably just flash a new ROM & radio.
Click to expand...
Click to collapse
I was told the same thing by VZW support, but mid-march... which is NOW! I'm really getting sick of this. Ready for the fix and some info.

I have the same problem on the GSM version. Also Raleigh, NC.

Has 4.0.4 been pulled?

Just want to know if there is any news about the latest GSM update because I have not received it and yes I'm on Google build.
With all the reports of signal problems and others have they pulled the update?
Sent from my Galaxy Nexus using xda premium

Nope.
http://code.google.com/android/nexus/images.html

as OTA it seems that yes, it has been pulled

I don't think its being "pushed" per say, but the OTA link usually stays up.
Search around for it.
Sent from my Galaxy Nexus using XDA

spamlucal said:
as OTA it seems that yes, it has been pulled
Click to expand...
Click to collapse
That's just speculation. It's more likely that they are collecting feedback from the first wave of updates as JBQ said. After all, the entire reason for not rolling it out to everyone at the same time is so that they can see that the updated devices come back up and seem to work normally.
Think of it this way. If you push out the update to 100 phones and 70 of them never come back up (ie. they don't login to Google within a certain amount of time), then you have a potential problem with the update.

Maybe not pulled since you can still get the factory image but OTA rollout has been stopped according to a vodafone rep: http://forum.vodafone.co.uk/t5/Google-Nexus/ICS-4-04-Update/m-p/1073311#M13631

There is no OTA 4.0.4 update for more than one week for yakju build devices.

I wouldn't complain if it has. A lot of GSM users complaining of radio troubles during sleep.
Does not affect CDMA users though
Seems like the tables turned on radio issues in 4.0.4. CDMA is better, GSM...not so much.

I don't know if it's been pulled as I've already updated to 4.0.4 but I can say that mine is problem free (thank god).
I find it strange that it doesn't affect everyone.... Anyone have any idea why?

adrynalyne said:
Does not affect CDMA users though
Click to expand...
Click to collapse
That's because most CDMA folks are still on 4.0.2
Sent from my Galaxy Nexus using XDA

ronak47 said:
I don't know if it's been pulled as I've already updated to 4.0.4 but I can say that mine is problem free (thank god).
I find it strange that it doesn't affect everyone.... Anyone have any idea why?
Click to expand...
Click to collapse
There are multitudes of factors to account for when diagnosing or replicating problems across all devices that are not equal per se. I didn't think I had the problem until my text stopped sending after clicking enter. The signal dropped out as well as other radios were gone for a brief moment.
I think it's only a matter of time before it happens to most people.
Sent from my Galaxy Nexus

I can definitely say my cell network data connection has refused to function on multiple occasions on 4.0.4. Possibly the sleep issue. Once restarting the phone fixed it, once not even doing a battery pull could fix it. It started working again at some random time later. I was trying to nail down if walking far enough that being a different tower fixed it or not.
Definitely given the amount of people complaining and the fact I've seen some wonky data connection issues it seems there is a bug.
I bought mine from Negri back in November, it came with yakju. On TMo in NYC.
Sent from my Galaxy Nexus using Tapatalk 2

I'm guessing a rushed 4.0.5 is soon to be released to fix the sleep and signal issues.

ericshmerick said:
I'm guessing a rushed 4.0.5 is soon to be released to fix the sleep and signal issues.
Click to expand...
Click to collapse
When you say rushed, that means at least a month from now, right? It is Google after all.
But I'm not going to complain about 4.0.4; it works fine for me. What I still hate is the poor communication from Google.

rubiconjp said:
That's because most CDMA folks are still on 4.0.2
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
According to AOSP we are on 4.0.4....not everyone is a victim
I haven't been on 4.0.2 since December of last year.

Evangelion01 said:
When you say rushed, that means at least a month from now, right? It is Google after all.
But I'm not going to complain about 4.0.4; it works fine for me. What I still hate is the poor communication from Google.
Click to expand...
Click to collapse
Yeah, I know the .001% of the population on XDA wants weekly massive improvement updates streaming to their Nexi, but it is simply unrealistic. This stuff takes time.
Silence is aggravating, but our phones get updates a LIGHT SPEED vs. any other Android phone. I'll take that any day of the week despite not getting an hourly update from the Android developers working on the inside. They're busy, believe me.

4.0.4 Data Drops Problem - Google doesn't care about this problem.

It is 20 days since we report a problem with drops after update to 4.0.4 . I judge that it is already too long and we should already have a fix. Now when all customs roms are using a new base, people who have this problem are forced to use an old 4.0.2 because with 4.0.4 phone useless. I think it would be good to start ask Google for any official statement because it is embarrassing for me that that they have such approach to theirs flagship phone.
This thread https://code.google.com/p/android/issues/detail?id=28133 shows that Google has completely no respect to us because there is now prove information that they even try to fix the problem.
Whats a shame Google.
Maybe should we start inform all gadget sites about this behavior?

Hey kid, stop being such a drama queen.
This is not how software development works. It takes time to iron out bugs. It takes time to first find out what causes the bug and then fix the bug and then it takes three times longer than that to make sure that the bug does not cause other bugs in the system.
Let's not forget how long 4.0.4 took to arrive in the first place. They originally released 4.0.3 and then discovered some bugs. Fixing those bugs apparently caused issues in 4.0.4 that no one saw coming, this means that the bug is not easy to find and is difficult to test for. They are doing it as fast as they can.
And let's not forget that not all devices are even affected. I've been on 4.0.4 ever since it was released and I've not experienced a single data drop. So it does not happen with all devices and may be region or carrier-specific. This makes it even more difficult to test for.

you honestly think they are able to push another update to a fix in 20 days?

kara mustafa said:
I judge that it is already too long and we should already have a fix.
Click to expand...
Click to collapse
You seriously think 20 days is too long to identify the problem that doesn't affect all devices, develop a fix, test the fix, and push it out?

Just started noticing I have this problem.
I just reboot and it fixes, a hassle, but whatever. reboots pretty fast lol and only happens rarely

luftrofl said:
You seriously think 20 days is too long to identify the problem that doesn't affect all devices, develop a fix, test the fix, and push it out?
Click to expand...
Click to collapse
You don't, apparently.
1. It does not affect all devices.
2. Lets rush a fix and not test it so other issues can occur?
3. If the issue is a radio problem, Samsung needs to fix it for Google to push it.
Even if developers worked 24/7 including weekends and holidays, that is pretty humorous to think that.
Re #3:
Samsung does nothing fast other than fatten their wallet. Yep, I said it, Google does not code radio firmware.

adrynalyne said:
You do, apparently.
1. It does not affect all devices.
2. Lets rush a fix and not test it so other issues can occur?
3. If the issue is a radio problem, Samsung needs to fix it for Google to push it.
Even if developers worked 24/7 including weekends and holidays, that is pretty humorous to think that.
Re #3:
Samsung does nothing fast other than fatten their wallet. Yep, I said it, Google does not code radio firmware.
Click to expand...
Click to collapse
The radio seems fine since I tried stock 4.0.2 with the XXLA02 radio (from the 4.0.4 package) and everything worked wonderfully.

adrynalyne said:
You do, apparently.
1. It does not affect all devices.
2. Lets rush a fix and not test it so other issues can occur?
3. If the issue is a radio problem, Samsung needs to fix it for Google to push it.
Even if developers worked 24/7 including weekends and holidays, that is pretty humorous to think that.
Re #3:
Samsung does nothing fast other than fatten their wallet. Yep, I said it, Google does not code radio firmware.
Click to expand...
Click to collapse
I do?

Same problem here, have to reboot to fix it, any alternative suggestion?
Sent from my Galaxy Nexus using XDA

To be honest I think it does affect all devices. I say this because I was away on business when 404 came out. Where I was I was in a lot of cinder block buildings and frequently without full signal. I had hspa and umts during that time but it wasn't a 21 or 42 mbps area like where I live. I often dropped signal on 404 that I didn't when I had 403 there. Now, after coming home back to my area that has a better coverage and such, I've not had one drop in signal. I really think its dependent on the towers and saturation whether you have the problem or not. I would still like to see a fix from Google. In the process of gaining battery life, I think they messed up smart reflex in respect to how it powers the antenna.
Sent from my Galaxy Nexus using xda premium

luftrofl said:
I do?
Click to expand...
Click to collapse
Lol, he must have misunderstood you.

No, it was a typo and I corrected it.
I meant to say, apparently, you do not. As in, he believes it only takes 20 days to diagnose, text, and implement a fix, which is funny
No fix is diagnosed day 1.
There is time to needed to find the problem.
There is time needed to create a fix.
There is time needed to properly test it, else other bugs show up.
Developers do not work 7 days a week.
Not every Android developer will be assigned to the fix.
There is time needed to ramp up an OTA again in two flavors, ICL53FD_to_IMM76D, and IMM76D_to_whateverthebuildnamewillbe.

Jayrod1980 said:
To be honest I think it does affect all devices. I say this because I was away on business when 404 came out. Where I was I was in a lot of cinder block buildings and frequently without full signal. I had hspa and umts during that time but it wasn't a 21 or 42 mbps area like where I live. I often dropped signal on 404 that I didn't when I had 403 there. Now, after coming home back to my area that has a better coverage and such, I've not had one drop in signal. I really think its dependent on the towers and saturation whether you have the problem or not. I would still like to see a fix from Google. In the process of gaining battery life, I think they messed up smart reflex in respect to how it powers the antenna.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
No it does not.
It does not affect CDMA devices, and I have found some GSM users on this forum it does not affect. Folks here just think that XDA is the hub of the world, and therefore if there is a large amount of issues being noted, it must be everyone. Because you know...everyone posts on XDA and other phone geek sites. I am not saying the bug isn't real, just that it isn't happening to EVERYONE.

Theshawty said:
The radio seems fine since I tried stock 4.0.2 with the XXLA02 radio (from the 4.0.4 package) and everything worked wonderfully.
Click to expand...
Click to collapse
It still could be the radios. There is a reason they change radios with each release.
For example, 4.0.4 by itself for CDMA users does not see a signal improvement. 4.0.4 radios on a 4.0.2 or 4.0.3 rom does not see signal improvements. However, 4.0.4 rom and 4.0.4 leaked radio firmware sees a signal improvement.

luftrofl said:
I do?
Click to expand...
Click to collapse
It was a typo, but you knew that.

Theshawty said:
Lol, he must have misunderstood you.
Click to expand...
Click to collapse
reading is difficult..

Some people have reported getting the IMM76I update starting about an hour ago, so for those with the issue, it may help you.

adrynalyne said:
You don't, apparently.
1. It does not affect all devices.
2. Lets rush a fix and not test it so other issues can occur?
3. If the issue is a radio problem, Samsung needs to fix it for Google to push it.
Even if developers worked 24/7 including weekends and holidays, that is pretty humorous to think that.
Re #3:
Samsung does nothing fast other than fatten their wallet. Yep, I said it, Google does not code radio firmware.
Click to expand...
Click to collapse
He was saying it with sarcasm. You should probably learn what that means before replying.

hotleadsingerguy said:
He was saying it with sarcasm. You should probably learn what that means before replying.
Click to expand...
Click to collapse
He wasn't being sarcastic. Nice try.

luftrofl said:
reading is difficult..
Click to expand...
Click to collapse
Sure is, considering I said several times it was a typo and you still didn't comprehend.

Verizon LTE just quit. Can anyone help diagnose?

Hey everyone...Yesterday, on my stock, 4.0.4 GNex, I noticed I was getting terrible 3G speeds, and no 4G data whatsoever (even though the 4G signal existed). I thought maybe there was a temporary outage, but no dice...VZW support said there were no issues. Today, the issues still remain, and I have no idea what the problem could be. I took some screen shots, so if anyone could offer some advice, I'd really appreciate it. I'd love to try and resolve this myself instead of bringing it to some of the inept VZW techs at the local store. I'm located in Western NY and there is normally a great 4G signal here.
I can post screenshots once I am allowed since I'm a newbie here.
THANKS!
EDIT: I should add, I've experienced the 4G dropping to 3G for a while, and I know this is an ongoing issue with GNex users, but this is completely different.

rms2219 said:
Hey everyone...Yesterday, on my stock, 4.0.4 GNex, I noticed I was getting terrible 3G speeds, and no 4G data whatsoever (even though the 4G signal existed). I thought maybe there was a temporary outage, but no dice...VZW support said there were no issues. Today, the issues still remain, and I have no idea what the problem could be. I took some screen shots, so if anyone could offer some advice, I'd really appreciate it. I'd love to try and resolve this myself instead of bringing it to some of the inept VZW techs at the local store. I'm located in Western NY and there is normally a great 4G signal here.
I can post screenshots once I am allowed since I'm a newbie here.
THANKS!
Click to expand...
Click to collapse
Another case, same awnser, considering what you said, the device is running the latest official release, and it seems 4g never works at all: return it and get a new one, probably has a bad radio.
If we can get a NYC vzw user as yourself who doesnt have the issues you're describing, i think that would kill it as faulty hardware.
Sent from my i9250

bk201doesntexist said:
...and it seems 4g never works at all: return it and get a new one, probably has a bad radio.
If we can get a NYC vzw user as yourself who doesnt have the issues you're describing, i think that would kill it as faulty hardware.
Click to expand...
Click to collapse
Meaning the radio just went bad? I've had this since launch day and never experienced a problem until yesterday. Also, I'm far from NYC, so if anyone in Western NY (Rochester/Buffalo area) has the same issue, let me know please.

Well, you said you have a stock phone and it doesn't sound like yourself have made any changes to cause this. So, what is it that you want to do? Flash the radio firmware? Root the phone and try different ROMs? Go through all this so in the end you take it to the store anyway? If your description of the problem is accurate, then it does sound like you have a hardware issue. Just take it in and deal with the inept VZW techs.

netbuzz said:
Well, you said you have a stock phone and it doesn't sound like yourself have made any changes to cause this. So, what is it that you want to do? Flash the radio firmware? Root the phone and try different ROMs? Go through all this so in the end you take it to the store anyway? If your description of the problem is accurate, then it does sound like you have a hardware issue. Just take it in and deal with the inept VZW techs.
Click to expand...
Click to collapse
No I didn't want to do any of the things you listed. I was asking if anyone here could help me diagnose the problem, in other words, see if there's any way to prove it's a hardware issue. I wasn't sure if there were any applications I could get to run diagnostics checks.

rms2219 said:
Meaning the radio just went bad?
Click to expand...
Click to collapse
If you never experienced these issues before, yes.
I would eliminate a few things (simcard, check another 4g capable phone, side by side, see if it works fine) first and do some testing.
Sent from my Galaxy Nexus using Tapatalk 2

It ended up being the SIM card. They replaced it, and instantly the 4G worked again.

Galaxy S3 in midtown NYC and I've been having the same issue for the last day and a half....
bk201doesntexist said:
If you never experienced these issues before, yes.
I would eliminate a few things (simcard, check another 4g capable phone, side by side, see if it works fine) first and do some testing.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse