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.
Related
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.
Go here and see the issue. http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=28133
I don't believe this is the fault of any ROM but actually a problem with Android/Google. So post in this thread and maybe when Google wakes up one day they will fix the issue. It killed me to see they rate the issue as Medium and not critical or at least Major!
this is a radio issue specific to quality control by samsung. issue has been addressed method of fix is to call in for replacement device
Thanks for the input, can you please supply me the official Google or Samsung news that this is a bug by Samsung and we should RMA it.
gaming09 said:
this is a radio issue specific to quality control by samsung. issue has been addressed method of fix is to call in for replacement device
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=26009296#post26009296
I found your post and sorry to say but I don't buy it. Google has already stated they know about the problem with data drops, I posted the actual thread tracking the issue. I suggest that others post there too and say they have the problem. More posts = more attention. There is absolutely nothing there saying Samsung is at fault. But please, I am open to any ticket or comment from Samsung acknowledging that my phone is a lemon.
Qualcomm makes the radio in the Nexus. Don't see how Samsung is at fault at all.
Not to mention, Google chose it and closely monitors development.
Sent from my Galaxy Nexus using XDA
noticed the problem the first time i accessed the play pen. i have had my phone for only a few hours.
I just spoke with a Samsung rep over their Live Chat line on their site. They have no such issue with radio's for the Nexus model. No recall and no news announcements about this issue. She said to me that they are unaware of any problems of data drop with the phone, she apologized for the problems and suggested that I contact Google about the problem. I wanted to confirm after that guy responded here about RMA'ing the phone. Did not make any sense and there are LOTS of people with the problem. It all started with 4.0.4. I imagine we will see a fix for this issue soon. Like I said, more people who post they have the issue the faster it will get resolved.
Flukester69 said:
I just spoke with a Samsung rep over their Live Chat line on their site. They have no such issue with radio's for the Nexus model. No recall and no news announcements about this issue. She said to me that they are unaware of any problems of data drop with the phone, she apologized for the problems and suggested that I contact Google about the problem. I wanted to confirm after that guy responded here about RMA'ing the phone. Did not make any sense and there are LOTS of people with the problem. It all started with 4.0.4. I imagine we will see a fix for this issue soon. Like I said, more people who post they have the issue the faster it will get resolved.
Click to expand...
Click to collapse
lots of people is relative. usually people with problems scream the largest, but what is the % of those people in relation to the total number of phones sold.
samsung/google are the only ones that know that magic number.
Has anyone tried this? I will give it a go when I get off work....
Edit.sorry wrong link
http://forum.xda-developers.com/showpost.php?p=24545086&postcount=73
Sent from my Galaxy Nexus using Tapatalk 2
Smokeey said:
Qualcomm makes the radio in the Nexus. Don't see how Samsung is at fault at all.
Not to mention, Google chose it and closely monitors development.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Actually, Samsung has branded the CDMA radio, and VIA makes the LTE radio. Not sure who does the GSM one.
It might have licensed Qualcomm tech in it, but they arent Qualcomm radios.
Zepius said:
lots of people is relative. usually people with problems scream the largest, but what is the % of those people in relation to the total number of phones sold.
samsung/google are the only ones that know that magic number.
Click to expand...
Click to collapse
the problem is pretty rampant and probably more so for GSM users. I doubt Samsung can tell you how many GSM vs CDMA user there are. I don't just frequent this site, I frequent dozens of others sites and the problem is reported on all sites. That tells me MANY people are having the problem. I'd like to keep this thread on topic rather than detract from the problem at hand. Thanks.
Flukester69 said:
Go here and see the issue. http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=28133
I don't believe this is the fault of any ROM but actually a problem with Android/Google. So post in this thread and maybe when Google wakes up one day they will fix the issue. It killed me to see they rate the issue as Medium and not critical or at least Major!
Click to expand...
Click to collapse
You know this article was addressed in IMM76I, right?
adrynalyne said:
You know this article was addressed in IMM76I, right?
Click to expand...
Click to collapse
All I know that I'm on 76I and still getting massive signal drops. Very frustrating. Tried dozens of different ROMS, kernels, radios, clock speeds, etc.
Sent from my Galaxy Nexus using XDA
What if you go back to 4.0.2?
Have the same issue as those that are complaining about the data drop issue.
1, after upgraded to stock 4.0.4, the reported issue starts happening.
2, I tried custom ROM, AOKP. Same issue.
3, I reverted back to 4.0.2 stock. The issue does not persist.
4, I upgraded back to 4.0.4 stock. The issue exist.
5, I flashed AOKP again and installed GetRIL from Google Play. Downgraded the RIL to 4.0.3. Issue seems to be resolved.
For about a month now, I haven't noticed data drop issue. Seems to be a valid workaround for the time being until Google fix the bug.
I'm on:
- GNex Maguro Yakuju, UK version.
- T-Mobile US
- LA area
Hope this helps.
adrynalyne said:
What if you go back to 4.0.2?
Click to expand...
Click to collapse
Its to my belief that prior versions whether it be 4.0.2 or .3 does not have this issue. I think its mainly the fact that we no longer cannot change our settings under the *#*#4636#*#* to GSM auto from WCDMA which I believe is partly at fault here.
Correct me if I'm wrong. I really want to be able to change it to GSM auto since it still forces HSPA+ even in bad signal areas instead of reverting to edge.
Sent from my Galaxy Nexus using XDA
chlehqls said:
Correct me if I'm wrong. I really want to be able to change it to GSM auto since it still forces HSPA+ even in bad signal areas instead of reverting to edge.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I believe it's the opposite> GSM auto will revert to EDGE sooner. WCDMA preferred will try to stick to 3G even with very low signal
Wow, a lot of people posted in that thread. I wonder if Google even reads that stuff or even cares.
I've suffered data drops since 4.0.1... tried lots of roms and kernels, but it keeps happening. GSM, Orange network, Madrid.
Sent from my Galaxy Nexus using XDA
gbalerdi said:
I believe it's the opposite> GSM auto will revert to EDGE sooner. WCDMA preferred will try to stick to 3G even with very low signal
Click to expand...
Click to collapse
Yeah that's what I meant, my sentence came out wrong since I was rapidly typing on the phone. Where I commute, I have pockets of low HSPA+ signals and currently it refuses to go to edge because of the changes on 4.0.4..
Sent from my Galaxy Nexus using XDA
I'll try to be succinct here. I got a replacement Nexus from Asurion when my screen cracked earlier this month. Incidentally, this was also around the time I started flashing Jelly Bean ROMs rather consistently. I have been experiencing (what I would actually refer to as) a crippling issue where my phone's signal will just completely drop. As in, no calls, no texts, no anything. Mobile network connection is gone. And while it does do it in my apartment, which has shoddy reception in the first place, it's doing it just as much when I'm in the middle of Best Buy, or a bar, or anywhere with FULL 4G. It will simply go from 4 bars to no service and then back to 4G (once the radio presumably cycles).
Do you guys think this is a hardware issue or a Jelly Bean issue? I've run two different ROMs overall (Jelly Belly and PARANOIDANDROID), so I've hit both the CM10 and non-CM10 ends of the spectrum and they're both doing it, so that leads me to believe that it's not a specific ROM issue, but either an overall Jelly Bean issue or a hardware malfunction. Any advice would be greatly appreciated. Thanks in advance.
enigmaisdead said:
I'll try to be succinct here. I got a replacement Nexus from Asurion when my screen cracked earlier this month. Incidentally, this was also around the time I started flashing Jelly Bean ROMs rather consistently. I have been experiencing (what I would actually refer to as) a crippling issue where my phone's signal will just completely drop. As in, no calls, no texts, no anything. Mobile network connection is gone. And while it does do it in my apartment, which has shoddy reception in the first place, it's doing it just as much when I'm in the middle of Best Buy, or a bar, or anywhere with FULL 4G. It will simply go from 4 bars to no service and then back to 4G (once the radio presumably cycles).
Do you guys think this is a hardware issue or a Jelly Bean issue? I've run two different ROMs overall (Jelly Belly and PARANOIDANDROID), so I've hit both the CM10 and non-CM10 ends of the spectrum and they're both doing it, so that leads me to believe that it's not a specific ROM issue, but either an overall Jelly Bean issue or a hardware malfunction. Any advice would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
I have the same issue with my phone. I have actually gotten 3 new phones only to have them all do the same thing. I flashed to Jelly Bean hoping it would fix the issue but no luck.
Sounds like a hardware issue. I have flashed many roms, ICS and JB and all are good for reception. Once we got new radios 5 months ago it fixed my 3g to 4g handoffs when I would lose data for minutes if not an hour. All good now.
It's common issue for Google nexus. I am also having same problem. You may ask a replacement or switch network mode to "CDMA only" instead of "LTE/CDMA".
Sent from my Galaxy Nexus using Tapatalk 2
It happens to my Galaxy Nexus too. >_<
Happens to me too. From HSPA (which should bei constant high-quality in my area) down to 2G, and if I am in areas with bad coverage, it looses signal completely.
Finally, after several ROMs, and basebands haven't fixed it, I'm going to send it in, as soon as possible now.
Sent from my Galaxy Nexus using xda app-developers app
This is a hardware issue. I515.10 is the one I have and it does this as well, the I515.9 however does not seem to be affected. The .10 was made in china and the .9 in korea... or maybe the other way around, hell who cares... Bottom line is, its a huge issue that samsung should have addressed long ago.
For more info check out the samsung forums. I'm waiting on a replacement to come Monday.
Sent from my VS910 4G using xda app-developers app
Same thing
This is happening on mine too. I installed the stock rom on my Verizon GNex and the signal has deteriorated significantly, almost like 4.0.2
I'm hoping a fix, or the new binaries fix this issues and put it back to it's 4.0.4 state.
I am still plagued by this. Anybody know of any fixes in the works? I have exchanged my phone 4 times to no avail.
Crandolph2001 said:
I am still plagued by this. Anybody know of any fixes in the works? I have exchanged my phone 4 times to no avail.
Click to expand...
Click to collapse
It's an issue with a certain batch of phones. All the ones I had that had issues were either manufactured in January or February (says 12.01 or 12.02 under the battery). I was finally able to get a new replacement at a Verizon store thanks to knowing the manager and it was just manufactured in July (12.07) and has worked like a charm (except a single stuck pixel in the upper right-hand corner, but I don't see it unless I'm looking for it, so I'll deal).
enigmaisdead said:
It's an issue with a certain batch of phones. All the ones I had that had issues were either manufactured in January or February (says 12.01 or 12.02 under the battery). I was finally able to get a new replacement at a Verizon store thanks to knowing the manager and it was just manufactured in July (12.07) and has worked like a charm (except a single stuck pixel in the upper right-hand corner, but I don't see it unless I'm looking for it, so I'll deal).
Click to expand...
Click to collapse
My current phone says it was manufactured 7/11/12 in China. I thought it was going to behave at first but the problem showed it's ugly head several days later.
Crandolph2001 said:
My current phone says it was manufactured 7/11/12 in China. I thought it was going to behave at first but the problem showed it's ugly head several days later.
Click to expand...
Click to collapse
That's strange. In my experience, it should either be screwed up totally or not at all. It shouldn't gradually onset. You sure it's not a ROM and/or radio issue this time that's just exhibiting similar symptoms?
enigmaisdead said:
That's strange. In my experience, it should either be screwed up totally or not at all. It shouldn't gradually onset. You sure it's not a ROM and/or radio issue this time that's just exhibiting similar symptoms?
Click to expand...
Click to collapse
When it started acting up I hadn't rooted / romed yet. I am now rooted and have flashed to 4 different roms and every single one of them still had the issue. I may have had the issue on the first couple days and not noticed it for whatever reason...
I updated to jellybean on my VZW nexus and have been dropping my signal a bunch randomly. I just got a refurbished phone from verizon and I flashed it first thing so I don't know if it is a problem with the phone or the stock AOKP radios I have installed. I was wondering if anyone knew if I can use the radios from 4.0.4 on jellybean or not?
rustid said:
I updated to jellybean on my VZW nexus and have been dropping my signal a bunch randomly. I just got a refurbished phone from verizon and I flashed it first thing so I don't know if it is a problem with the phone or the stock AOKP radios I have installed. I was wondering if anyone knew if I can use the radios from 4.0.4 on jellybean or not?
Click to expand...
Click to collapse
I don't know the answer to your question, however...
Got my wife a free Galaxy Nexus from Best Buy last week (verizon)... and instantly had problems w/ the 4g. After a ridiculous period of time at Best Buy to get the phone activated (they tried multiple SIM cars) and her contacts downloaded, we finally left being assured that the 4g problems were due to the activation process, and were told to give it a day or two. I was skeptical.
So we flipped off the LTE/CDMA mode, and went just to CDMA and used 3g for a few days. Called Verizon, they refreshed the network / cleared out the lines (whatever that means), and still no 4g. Every time we'd turn on 4g mode, it would connect, then drop moments later. When it dropped, it also dropped the phone line. After a week, my wife had finally worn me down. I conceded to her that a very very very very remote possibility had occurred, and we had gotten 'a bad phone'. Dear lord, did I want her to go to Best Buy w/o me. But i got suckered (she's pregnant).
So after another 2 hours at Best Buy, a new phone, and a new SIM card... we walked out w/ the same problem as before. Apparently, there's something going on w/ Verizon's latest software version ... our only option is to use 3g for a bit. I called Verizon to try and get some free money towards my bill out of them, and the customer support rep told me my best option at this point was to return the phone and choose a different device. Talk about horrible support.
So now i've come here to pretty much try what i think you'er aiming for... maybe by going to CM9 or CM10, her phone will be able to keep a constant 4g connection... only time will tell.
rustid said:
I updated to jellybean on my VZW nexus and have been dropping my signal a bunch randomly. I just got a refurbished phone from verizon and I flashed it first thing so I don't know if it is a problem with the phone or the stock AOKP radios I have installed. I was wondering if anyone knew if I can use the radios from 4.0.4 on jellybean or not?
Click to expand...
Click to collapse
There is no such thing as "stock AOKP radios." The baseband version is independent of the ROM, so whatever baseband you had after flashing was the exact same one you had prior. The signal drops are a common issue and could be attributable to the fact that there are no JB basebands released for the i515 as of yet.
The issue is with your device and not the radio's or the OS version you are on. Nothing you do will fix it or make the issue disappear. There are good GNEX's out there that do not have the radio problems, it took me three tries to get one.
Don't believe anything else you hear about fixing what you have. It is all BS.
Occam's Razor is applicable here. When the problem is persistent on 4.1.1 and is not present after reverting to 4.0.4, it's a software issue. That's not discounting the ones put there with hardware issues, but the fact of the matter is that signal problems are to be expected for vzw users running JB. We have updated binaries, but until a new baseband drops for the i515, it's not going to play especially well with JB. Such is the price for us early adopters.
Sent from my Galaxy Nexus using Tapatalk 2
[email protected] said:
The issue is with your device and not the radio's or the OS version you are on. Nothing you do will fix it or make the issue disappear. There are good GNEX's out there that do not have the radio problems, it took me three tries to get one.
Don't believe anything else you hear about fixing what you have. It is all BS.
Click to expand...
Click to collapse
I've seen two types of issues on the gnex.
1) 4g drops out and either drops to 3g or 1x for a period of time, in which it reconnects to 3g/4g shortly after. This seems to be a once in a while type issue. This seems to be more radio related.
2) 4g drops and your phone drops signal, period, for that time and then reconnects quickly. Easiest way to tell if its doing that is to check the battery stats graph and look for red slivers in your data connection. This issue from what I've seen is more hardware and I'd suggest replacing the device within your 14 days.
Sent from my Galaxy Nexus using Tapatalk 2
The ongoing theme is it's a great phone other than noisy calls, occasional drops, data signal/connection issues, and fragile glass.
And we're partly to blame. Short life cycles and youthful koolaid drinking consumers enable phone manufacturers to continue to build with a style over function mentality.
najaboy said:
Occam's Razor is applicable here. When the problem is persistent on 4.1.1 and is not present after reverting to 4.0.4, it's a software issue. That's not discounting the ones put there with hardware issues, but the fact of the matter is that signal problems are to be expected for vzw users running JB. We have updated binaries, but until a new baseband drops for the i515, it's not going to play especially well with JB. Such is the price for us early adopters.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
My 3rd replacement says otherwise. I have been on JB for 3 weeks now with this device and have not had any issues with 4G.
If every LTE GNEX had the same issue on JB I would agree with you but that is not the case. I wouldn't believe it either until I finally received a perfectly working GNEX. Always thought it was the software but I was proven wrong.
rustid said:
I updated to jellybean on my VZW nexus and have been dropping my signal a bunch randomly. I just got a refurbished phone from verizon and I flashed it first thing so I don't know if it is a problem with the phone or the stock AOKP radios I have installed. I was wondering if anyone knew if I can use the radios from 4.0.4 on jellybean or not?
Click to expand...
Click to collapse
Go here and get the FC04/FC05 radios.
Radios are independent of the ROM, so you can install any radio you want on any ROM. FC04/FC05 are the latest basebands.
jpinsl said:
Go here and get the FC04/FC05 radios.
Radios are independent of the ROM, so you can install any radio you want on any ROM. FC04/FC05 are the latest basebands.
Click to expand...
Click to collapse
His device should already have these radios if he recently received it.
My suggestion is do not play games with radio swapping, keep excahging until you get one that works.
Also, why not restore to ICS first and see that it is your phone and not the software.
najaboy said:
Occam's Razor is applicable here. When the problem is persistent on 4.1.1 and is not present after reverting to 4.0.4, it's a software issue. That's not discounting the ones put there with hardware issues, but the fact of the matter is that signal problems are to be expected for vzw users running JB. We have updated binaries, but until a new baseband drops for the i515, it's not going to play especially well with JB. Such is the price for us early adopters.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
My old phone with the blown speaker on the same 4.1.1 rom does not have this issue. I never tried stock ICS, I flashed this phone as soon as I got it. I think it is the phone.
I have the drop issue sometimes but in my case I'm sure its not the phones fault as it doesn't happen at home (only at work)
Sent from my Galaxy Nexus using Tapatalk 2
Running jellybean now, but my 4g has always been erratic at connecting. Sometimes its fine and sometimes it switched back and forth in the same location.
Sent from my Galaxy Nexus using xda premium
I am on my sixth nexus. I am running Vicious's 4.1.1 rom rooted and not running any weird power saving apps and turning off my wifi when not at home. The radio signal either turns off completely for a few seconds or cannot connect to data services constantly when trying to use the phone. There is nothing I am doing that creates this problem consistently. It is random. Sometimes i can make a call and talk for an hour and have no problems sometimes i can be in the same area and make a call and it continually drops the call after a few seconds to a few minutes. 4g rarely works though it shows its connected. I am running what i believe to be the latest radio for verizon I515.10V.FC04/I515.FC05. I am open to suggestions on radio's app's anything to get this corrected. I even tried going back to stock and letting Verizon update the phones to start and the problem still persists. i travel a lot and it does not seem to do it in any area more than another. but It has become a constant nu sense when talking to my customers on the phone. or trying to connect to data services. PLEASE HELP
Verizon Galaxy Nexus LTE
4.0.5?
Sent from my Stock AOSP Android 4.1.1 Galaxy Nexus
Look under your battery. Is your nexus made in China or Korea? Korea ones generally are much more reliable
Sent from my Galaxy Nexus using Tapatalk 2
tacosrdelicioso said:
Look under your battery. Is your nexus made in China or Korea? Korea ones generally are much more reliable
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
China!!! hey own our country and apparently they just owned me... lol
tacosrdelicioso said:
Look under your battery. Is your nexus made in China or Korea? Korea ones generally are much more reliable
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It's hit or miss with either. I just sent in a Korean handset for this issue.
Sent from my Galaxy Nexus using Tapatalk 2
so I guess
So I Guess i'm a minority when it comes to this issue since no one else seems to be responding
Sdalton19 said:
So I Guess i'm a minority when it comes to this issue since no one else seems to be responding
Click to expand...
Click to collapse
I had the same issue, finally my 3rd gnex works perfect on Verizon, my signal would drop for about 30 seconds and come back hardly ever worked my first gnex didnt work at all. Theres another thread on here with the same issues, Just need to keep replacing them till you get a good one.
supercobaltss said:
I had the same issue, finally my 3rd gnex works perfect on Verizon, my signal would drop for about 30 seconds and come back hardly ever worked my first gnex didnt work at all. Theres another thread on here with the same issues, Just need to keep replacing them till you get a good one.
Click to expand...
Click to collapse
thank you. I kinda thought the same thing. But i'm dealing with Asurion phone insurance and they aren't very concerned with getting me one that works... Talked to them a little bit ago and they are sending me another new one again...