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...
Related
I have an extremely annoying issue. I've seen some posts reporting this on various boards, but it seems most people throw a default answer out there that it's a hardware issue. I'll explain why I don't think that's the case.
The menu that comes up with you press the "menu" capacitive key has been popping up and down rapidly and repeatedly when I'm in a low signal area. This didn't start happening until after Samsung/Sprint fixed the LOS issue. I'm thinking it has something to do with the way they fixed it, which I don't have any technical or general knowledge of. Most of the time, the screen and keys will not be responsive unless I hit the power key to turn the screen off and turn it back on. It's even more annoying since it vibrates everytime the key is "pressed". I don't think this is simply a hardware issue as the only time this presents itself is the same times the LOS issue used to. I'm sure it's tied to that fix somehow.
Is anybody else having this issue? This may be a long shot, but I installed the LOS Checker zip, (I forgot which dev created it), and never uninstalled it, but I've upgraded many roms since then and don't think it would still be installed.
If any of you do have this issue, did you ever install that LOS Checker zip?
Rom= Blazer Rom EL29 v3.8
Kernel = rogue 1.4.1
Started happening to me recently as well. Im running Calks still on GB with ICS theme. I haven't paid attention to my signal when it happens but you are right, turning off the screen does stop it momentarily. I agree this may not be a hardware issue as well. I've just been bearing it because I plan on changing phones soon anyway.
Edit: It just started happening after this post. Signal was at 1 bar...
Epic-ly tapped from my Galaxy S II
Zoidpilot said:
Started happening to me recently as well. Im running Calks still on GB with ICS theme. I haven't paid attention to my signal when it happens but you are right, turning off the screen does stop it momentarily. I agree this may not be a hardware issue as well. I've just been bearing it because I plan on changing phones soon anyway.
Edit: It just started happening after this post. Signal was at 1 bar...
Epic-ly tapped from my Galaxy S II
Click to expand...
Click to collapse
Did you happen to install this? http://forum.xda-developers.com/showthread.php?t=1326569
Happens to me too. Menu button hitting itself at random times.
Sent from my SPH-D710 using xda premium
I have this same issue. I never realized it correlated with low signal. The issue cropped up 3 times today and each occurrence was with low signal. Good eye sir.
Do any of you undervolt or use a kernel that runs less than standard voltages?
My device is undervolted quite a bit and was wondering if it may be part of issue as i don't remember having this problem prior to that.
I am removing my undervolts and will report back if i still have this issue.
Sent from my SPH-D710 using Tapatalk
I'm on stock rooted. Always happens on different occasions. I just turn the screen on and off and usually it'll fix the problem
Sent from my SPH-D710 using xda premium
I was gonna post the same thing I just realized this morning that it always coincides with low signal
Sent from my SPH-D710 using xda premium
I think its a hardware issue. Im running the same setup on my replacement phone and haven't had the issue since.
I experienced this ever since I got the phone back in september but I didn't wise up until the 14 day period ended. there are two threads in the Q&A section concerning this, one that i started and another that i contributed to.
I would be trying to text and the menu button would pop up and i would accidently hit something on the menu that came up bc the button spazzes out randomly and consecutively and sometimes for a solid 5 seconds, but like the rest of you im sure, it wasnt confined to any single app so it was impossible to find one thing to blame. it would have to be something system-related or hardware-related (btw i did flash the LOS checker some time ago)
I believed the low signal theory for a while, as well as having a corrupted flash. but I experienced the spasms with full bars of service AND after a complete Odin restore to stock everything without restoring any of my past data whatsoever. thus I deferred to the "default" that it is hardware-related.
that was months ago.
I got so fed up with it, i decided to do anything to make it stop. So, I recently opened up my device and took everything apart and found that the water indicator just above the capacitive buttons had been activated. keep in mind I DID NOT EVER have any encounter with water. in fact, the other water indicators were perfectly undisturbed. this pissed me off because that means there might have been an accident or something while they were being manufactured that would have damaged the button - idk just another theory.
This is my main piece of evidence supporting my claim that it is hardware-related:
I ended up breaking the screen trying to separate the glass from the digitizer (stupid, I know bc theyre fused together) so I ended up buying a new screen/digitizer. put it in myself. i haven't had it since. I'm running the EXACT same set up as before I replaced my screen and its been about a week and no instances. I would be experiencing the sporadic menu button randomly, several times a day but it has completely disappeared.
i suggest to you all: bring it in to Sprint if you bought it from them or invest in a new screen off ebay if you bought it from a 3rd party seller (Amazon, wirefly, letstalk), i got my new screen for $65 shipped and it was in pristine condition. now im living a happily-ever-after ending
i'll keep a close eye on this thread to help you all with your endeavors/theories though
if any of you plan on opening up ur device, i suggest you do some homework so as not to destory your phone - its still an amazing device. or you can just ask in this thread and i can give tips to everyone
good luck!!
Thanks for all the updates.. I've noticed I'll sometimes get this error, but my phone will be showing full bars where I KNOW I have a poor signal.. for instance, my elevator at work..
Is there any sort of logging app I could run and go into an area I know this will happen to find out what's going on?
IsThisOneTaken said:
Thanks for all the updates.. I've noticed I'll sometimes get this error, but my phone will be showing full bars where I KNOW I have a poor signal.. for instance, my elevator at work..
Is there any sort of logging app I could run and go into an area I know this will happen to find out what's going on?
Click to expand...
Click to collapse
sometimes the signal bars are inaccurate (like you described). your true signal is found in settings>about phone>status>signal strength. 0-1 bars is really about -90 to -100 dBm
devs use logcats to analyze issues with the internals
http://forum.samdroid.net/f38/tutorial-how-get-logcat-example-check-battery-drain-2543/
I just checked a few other boards and it seems a number of people have confirmed it correlates wih low signal. There are a few people that keep popping up on multiple threads stating it's a hardware issue, only because a new screen fixed it. I would be fine with that logic if there weren't so many people stating it correlates with low signal. Also, it seems most people haven't really experienced this issue until after the LOS fix. Now, at the same times I used to have LOS issues, I now have this. I'm guessing it has something to do with internals and whatever they did to update it may be separate from modems or roms, since people have gone back to stock and still experienced this issue.
I haven't done a search, but is there an information source that states exactly what Samsung did to address the LOS issue?
I'm going to ODIN back to the original shipped EG30 package and test it out.. I never did OTA updates.. always through ODIN, etc. I'm going to see if I update through OTAs if anything is different. I'll report back.
I had experienced it since around the 1st week of october. i didnt have los fixed until i flashed chris41g's experimental kernels, not sure when all that was though. i was convinced it was related to signal too, but i would still happen on the highway/in public with 3 bars of 4g and ~50-60 dBm
would be interesting if you figure it out though
Yea I ODIN'd back to EG30 and now OTA'd to EL29.. no issues yet but we'll see tomorrow when I'm in elevators. After doing all this, I realized I probably need to do a full EEPROM reset and then go through this... don't really feel like doing that tonight though.
Im pretty sure this is in fact a samsung phone issue in general. I came over to sprint and the e4gt from verizon and the fascinate. I loved that phone, but it had this exact same issue. I have not in fact had it happen to me so far with the e4gt yet. I have a sneaking suspiscion that this issue goes hand in hand with undervolting, but thats just my own personaly theory.
Sent from my SPH-D710 using Tapatalk
Happens to me on the rare occasion as well. Might be an issue with the phone?
I called this one during the LOS era. It definitely occurs in low signal areas. I could never get LOS so I went into known dead spots and sure enough those random pop ups happened
Sent from my Nexus S 4G using xda premium
*Luke* said:
Im pretty sure this is in fact a samsung phone issue in general. I came over to sprint and the e4gt from verizon and the fascinate. I loved that phone, but it had this exact same issue. I have not in fact had it happen to me so far with the e4gt yet. I have a sneaking suspiscion that this issue goes hand in hand with undervolting, but thats just my own personaly theory.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I noticed there were a few other threads on Samsung devices with issues.... hmmm. Did you ever try limiting your underclocking to a higher clock speed? This may be a noob question but for the EG4T, is anything less than 800mhz considered underclocking?
JohnCorleone said:
I called this one during the LOS era. It definitely occurs in low signal areas. I could never get LOS so I went into known dead spots and sure enough those random pop ups happened
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I believe I remember seeing your post haha... I'll see what I can do if I mess around with clock speed.
Hey guys ever since getting this phone ive been having to keep getting replacements for it and it still havent fixed the various problems that ive had with this phone.
1. microphone will cut out during calls and sound will stop working.
This problem has been resolved from getting a replacement through verizon's warranty program.
After receiving my replacement however, i am now getting the signal drop issue where the only way for the phone to work is putting it in CDMA mode. Ive researched online and found that various other people have been experiencing the same problem with their galaxy nexus. So i go to the store to order another replacement.
After receiving my 3rd replacement, still no luck. This phone is still experiencing the same problem has the last where the signal would randomly keep dropping. So i go back into the store and decide to switch out the sim card for the phone and order another replacement.
The 4th replacement comes in and to still no surprise the signal keeps dropping off. I found that both korean made phones and chinese made phones are experiencing the same problem. Ive changed my SIM card, rooted and unrooted, tried various roms, updated to the unofficial 4.1 jelly bean update and still nothing fixes this damn radio problem.
Im so fed up with this phone but if anyone has any suggestions it would be greatly appreciated as i have no idea how to get a working galaxy nexus and have never experienced a working one still. I would KILL to get a phone that actually keeps a 4g signal ><
This should not be in development.
Oi...
I don't quite understand the purpose of these threads...
For reference, this is the development forum despite the Verizon designation. Releases only here.
Sent from my Galaxy Nexus using Tapatalk 2
dmeadows013 said:
This should not be in development.
Click to expand...
Click to collapse
oops sorry will move my post to general.
Can't find download links for your rom.
oh wait...
There is nothing you can do except to keep getting replacements. No software will fix your issue at this time.
I just received a replacement yesterday as my phone's radios, voice and data would disconnect and only a reboot would fix it. Today I made it through the day without it happening once on my replacement. Still not convinced it is the device though until I go a few days without it happening.
If it happens with this one, I would say it is more of software radio issue and not the physical device and Samsung needs to do something about it.
So, I will see how it goes over the next few days. If this one continues to work, then it could possibly be the device. I My first GNEX though would not keep 4G for more then a minute and jump off, then on, then 3G, then 4G. To me that was the device. My next one would just lose it after a few hours, otherwise it was fine....
Let's hope the 3rd one is a charm.
Try updating the radio and is it possible you live in a area where signal is poor. I haven't had an issue at all with my nexus
Sent from my Galaxy Nexus using xda premium
tbis said:
Try updating the radio and is it possible you live in a area where signal is poor. I haven't had an issue at all with my nexus
Sent from my Galaxy Nexus using xda premium[/QUOT
currenly using the latest from official 4.0.4
tried the many hybrid radios too out there and its still doing this. you must have gotten lucky then, ive been experiencing this ever since i got the phone
Click to expand...
Click to collapse
"like new" replacement improperly tested
Jooining the club.... I had a relatively well functioning gnex until about 2 weeks ago, it did reboot once in a while, but oh well. Then it totally died suddenly. Tried to revive it to save data, but to no avail. So here you come Verizon "like new" replacement..... :fingers-crossed:
Oh no....well sure enough, started to have problems with dropped connectivity data + voice immediately after init.
Previous phone never did it. And it is doing this over a huge urban city.... I was careful in transferring my SIM as well.
there a slew of threads around forums discussing this issue and related (among others see through https://code.google.com/p/android/issues/detail?id=24345"]https://code.google.com/p/android/issues/detail?id=24345
Is is time for class action against Verizon for improper testing procedures and wrongly sending faulty devices as new (which they can pass along to Samsung since ultimately, it is probably Samsung who is playing dumb) ?
deejaycin said:
Hey guys ever since getting this phone ive been having to keep getting replacements for it and it still havent fixed the various problems that ive had with this phone.
1. microphone will cut out during calls and sound will stop working.
This problem has been resolved from getting a replacement through verizon's warranty program.
After receiving my replacement however, i am now getting the signal drop issue where the only way for the phone to work is putting it in CDMA mode. Ive researched online and found that various other people have been experiencing the same problem with their galaxy nexus. So i go to the store to order another replacement.
After receiving my 3rd replacement, still no luck. This phone is still experiencing the same problem has the last where the signal would randomly keep dropping. So i go back into the store and decide to switch out the sim card for the phone and order another replacement.
The 4th replacement comes in and to still no surprise the signal keeps dropping off. I found that both korean made phones and chinese made phones are experiencing the same problem. Ive changed my SIM card, rooted and unrooted, tried various roms, updated to the unofficial 4.1 jelly bean update and still nothing fixes this damn radio problem.
Im so fed up with this phone but if anyone has any suggestions it would be greatly appreciated as i have no idea how to get a working galaxy nexus and have never experienced a working one still. I would KILL to get a phone that actually keeps a 4g signal ><
Click to expand...
Click to collapse
This is the VZW development thread. You'll find better responses /answers to your questions in the proper forum.
XDA Mods please move to proper thread.
Thread moved. Please do not post general threads or questions in the development section. Thank you.
---Jay--- From the GNex
I just updated to 4.1 and can't seem to get a network signal on any of the ROMs I have tried. Anyone else had this problem or found or know of a solution?
Thanks.
Rarazuh said:
I just updated to 4.1 and can't seem to get a network signal on any of the ROMs I have tried. Anyone else had this problem or found or know of a solution?
Thanks.
Click to expand...
Click to collapse
Was this an OTA uprade? If you did an manual upgrade, you should make a backup before going forward.
Are you sure you used the correct ROM? Cross-flashing between a Toro/Maguro/Toro+ will often have the phone but up but with the radios not working
did you check your apn?
I just bought this phone on Thursday and the bestbuy rep had the same problem on two different phones and had to call the Verizon help desk. She managed to get it working and of course my signal went in and out as soon as I left the parking lot. I went home and immediately rooted and flashed 4.1 and had the same issue. I was on the phone with tech support and they couldn't find the problem.
I then did a quick search online and found that this is a common issue. The problem is that when updating to 4.0.4 the galaxy nexus has a hard time with the 4g connection. It then drops to 3g and then it realizes 4g is available and switches back just to start this never ending cycle. This causes a signal to be held for seconds at a time before dropping completely until it switches to the other.
The temp fix is to disable LTE and run your phone on CDMA full time. This worked for me and I have constant signal everywhere. Eventually I know a patch will arrive so I'm content with 3g for the time being.
What puzzles me is how come this doesn't happen to everyone? Its a big enough issue that I found the solution within 3min of searching for a fix but not big enough for Verizon to be aware of.
Sent from my Galaxy Nexus using xda premium
mclaughlin47 said:
I just bought this phone on Thursday and the bestbuy rep had the same problem on two different phones and had to call the Verizon help desk. She managed to get it working and of course my signal went in and out as soon as I left the parking lot. I went home and immediately rooted and flashed 4.1 and had the same issue. I was on the phone with tech support and they couldn't find the problem.
I then did a quick search online and found that this is a common issue. The problem is that when updating to 4.0.4 the galaxy nexus has a hard time with the 4g connection. It then drops to 3g and then it realizes 4g is available and switches back just to start this never ending cycle. This causes a signal to be held for seconds at a time before dropping completely until it switches to the other.
The temp fix is to disable LTE and run your phone on CDMA full time. This worked for me and I have constant signal everywhere. Eventually I know a patch will arrive so I'm content with 3g for the time being.
What puzzles me is how come this doesn't happen to everyone? Its a big enough issue that I found the solution within 3min of searching for a fix but not big enough for Verizon to be aware of.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have the same issue. it burns your battery as well by switching back and forth. I used to leave my nexus uncharged at night and the sleep mode would allow it to only lose a a few percentages but now if i leave 4g on with 50 percent battery.. Its almost alway dead when I wake up
Sad to say I have the same experience
The story told by mclaughlin47 is almost exactly what happened with me. Even rooted and running BAMF Paradigm 2.1, I still have the same problem. If anyone knows of a way to fix this, please let us know.
I can't believe Verizon isn't aware of this problem. I actually had better battery life and signal with my Thunderbolt running Vicious ROM. I may just be returning mine if I don't hear of a solution soon.
Thanks for any help, cause this is ridiculous!
I am rooted now, but even on stock ICS I was getting a problem where my radios just die. Requires a reboot to fix. But when I was seeing it, they always looked fine. You don't know they died until you try to use data or make a call.
Do you still have your imei
Sent from my SCH-I535 using Tapatalk 2
I saw the same issue with ics and jb roms. Tried several radios but always dropped data and voice when using 4g. From what I've been reading, it's a hardware defect.
Mine also works great and stays connected all the time when I leave it in cdma mode. Went back to my rezound since 3g mode there at least still let's me use data while talking on the phone. I like showering in as much radiation as I can
tbguy said:
I saw the same issue with ics and jb roms. Tried several radios but always dropped data and voice when using 4g. From what I've been reading, it's a hardware defect.
Mine also works great and stays connected all the time when I leave it in cdma mode. Went back to my rezound since 3g mode there at least still let's me use data while talking on the phone. I like showering in as much radiation as I can
Click to expand...
Click to collapse
Reflash the radio and the cdma radio. Samsung and Verizon Wireless both claim that hardware defects are not known issues.
Which hardware revision do you have? (looks on the label on the back should be 11.11, 11.12, or 12.0.)
i have 12.01
will try reflashing the latest radios
tbguy said:
i have 12.01
will try reflashing the latest radios
Click to expand...
Click to collapse
just to check back, did it work?
unknownzero said:
just to check back, did it work?
Click to expand...
Click to collapse
Have the same exact issue...just upgraded to a jelly bean Rom and my data drops completely and I barely have a signal, did a super wipe (radio-rom-Gnapps)...and went to my old rom of ICS and I still have the same problem...but for the most part I barely have any type of signal and calls are dropping, called Verizon and they told me something about a switch, and that there is no problem in ur area....I just called last night, I'm gonna call back today...wish there was a solution ...also tried that 3G switch I just read earlier and I still have a poor signal
Any updates? I'm having the same problem
Hi,
I'm having the same issue. I've had my Nexus for about a month now and have had nothing but horrible signal issues, while my old Droid 2 gets fantastic signal.
I'm using the latest Bugless Beast 4.1.1 with the latest radios that were released today.
People have mentioned it being a hardware defect. I'm assuming I should just go back to stock ICS and go into Verizon and exchange it for a different Nexus?
It may very well be a hardware problem, but my thought was a SIM card problem for the reason that rebooting often does not solve the problem for me. I have a passcode on my SIM card, so if my phone doesn't ask me to enter the code then I can assume it doesn't see the card. This often happens when I encounter the loss of data problem and reboot, and I usually have to remove the SIM card and fiddle with it a bit and put it back in and then it reconnects.
So I went to the Verizon store to try and swap my SIM card and they wouldn't give me a new card, saying that it's a known software issue that Samsung has already attempted to fix twice and they are working on another OTA update. I obviously made a ruckus about how I'm paying for service I can't access and I want a different device, blah, blah, blah. Basically he was incredibly unhelpful.
I've been on ICS AOKP and recently switched over the CM10 JB and that's when the problems started for me, but I switched because some type of battery issue (it lasted about 3 hours for a few days) caused my phone to reset itself and erase everything so it seemed like a good time to upgrade. So I may have unique hardware issues going on but according to vzw it is software-based. I'm not sure if this is something that can/will be addressed in a new nightly if that's the case.
PEOPLE, IT'S NOT A HARDWARE PROBLEM! IT'S SIMPLY A RADIO.IMG PROBLEM! A LOT OF PEOPLE WHO IS ON ICS, BUT FLASHED LATEST RADIO ARE SUFFERING FROM THIS!
What you can do is just flash to a older radio image. Not that hard. Will this stop the OTA? Probably, but you can either flash the latest version back or just manually flash it.
Have a good day.
I got mine the first week of Aug at Best Buy. The first one I got had all the problems described above. Radios dropping out and dropping every call I made. I returned it the next day, and the sales guy told me he was 100% sure it wasn't the phone. I asked him to exchange the phone and the card because I couldn't use a phone that couldn't make calls. He did the exchange, and the second phone was actually worse. Most of the time, I could not even make a call. So, the next day I took that one back. They gave me a third one that worked great for a week, then I started getting a no SIM card error message. The phone would reboot and work again for about 3 hours, then repeat error message. I took the card out, wiped down all the contacts with a soft cloth, and I have had no problems since. Great reception, no dropped calls. Great phone. I don't know if it is hardware or software, but I would keep returning the phone until you get one that works!
Once again, what is the point of having a phone that can't make calls.
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
My wife and I each bought our Nexus phones a couple of months ago from the Play store and signed up for Straight Talk. Overall everything has been great (except of course my wife cracking her screen, but that is another issue). A strange signal issue has happened to each of us a few times. Most of the time everything is fine. However we've both had the situation where the phone completely loses signal and it won't come back on its own. For me, it seems to happen when I am in an area with very poor to no signal. It's like the phone stops trying to get a signal completely. The signal meter shows the empty triangle and the lock screen says "Emergency Calls Only". Even when I get back to a strong signal area it doesn't pick anything up. My wife had no signal for a couple of days since she was on Wifi and didn't notice the lack of calls/texts. Rebooting the phone fixes it and switching the phone to airplane mode and back also fixes it. I am almost always in area with decent to good signal coverage so this doesn't happen too often.
Does anyone else experience this? I'm wondering if this is a Nexus or a Straight Talk issue?
EDIT: I didn't mention before, but I am running both phones stock and never been rooted. So this is definitely not a custom rom issue.
I have had the exact same issue with my nexus, same solutions as soon as I leave the poor signal areas(airplane cycle, reboot) . I am, however with at&t (just using my old s2's sim) and my wife has experienced the same issues with her s3. Leads me to believe that it is a signal issue. My two cents for the same experience, carrier or not.
I777 gets it done, gnex just for fun
I've been getting this issue for the past few days. I'm on T-Mobile. This never happened before and I don't think it's a rom/kernel issue as I've tried a few roms and was experiencing the same issue on all of them.
ragnarok12 said:
I've been getting this issue for the past few days. I'm on T-Mobile. This never happened before and I don't think it's a rom/kernel issue as I've tried a few roms and was experiencing the same issue on all of them.
Click to expand...
Click to collapse
Actually, I probably should have mentioned it, but neither of the phones are rooted. Just stock all around.
I got a similar issue from not flashing JB radios along with CM10, but........
Sent from my Galaxy Nexus using xda app-developers app
Both my nexus, and the wife's s3 are also unrooted, as well. Jb simply hasn't given me a reason to root, I'm not displeased with anything. My issue with signal stopped yesterday, and I confirmed it wasn't a phone issue for myself by popping my sim back in my rooted s2. Still had zero service. Hopefully your issues will also resolve themselves, if they haven't already
Sent from my broken screen swagga machine
My little brother had this same problem on all roms, though he had a cdma version, i don't believe this is a mere coincidence, we were able to replace his since it was within the thirty days. But i think this is a "needle in a haystack" hardware issue, and you're just the unlucky ones. Though I could be wrong, many people have had this issue before as I've searched on Google to try to fix my brother's phone.
Sent from my Galaxy Nexus using Tapatalk 2
I have same problem with both Galaxy Nexus and my previous phone, the Nexus S, only thing I have to do is reboot, after reboot, problem is gone, but it could come back in time, but I recently update radio, and haven't seen this problem quite while.
One other problem is, sometimes when i enable the airplane mode, was unable to disable it unless I reboot it...