Related
I am currently tethering over a 4g connection, and my internet is working fine, BUT I have a complete LOS for the cell signal. I think this could be a very important fact because we should be able to know some things by the fact that WiMax is working while the cell signal is altogether lost.
Hopefully, with this info, a solution is a little closer at hand.
Ok...when people say LOS do they mean Loss Of Service? Or Loss Of Signal?
Because if its the latter, that sht aint that bad. But if its the former...I'm glad I don't have it.
ms79723 said:
Ok...when people say LOS do they mean Loss Of Service? Or Loss Of Signal?
Because if its the latter, that sht aint that bad. But if its the former...I'm glad I don't have it.
Click to expand...
Click to collapse
It is bad. People that get it have to reboot phone for it to come back and it kills battery life. Nit to mention missed calls and texts. It is a complete loss of service.
Sent From My Evo Killer!!!
Its 2 separate radios..
I had pandora going over 4g earlier for hours...but lost signal with a crossed out circle after about an hour. Pandora kept going but u couldn't make a phone call, ths.falls in line with the other poster. Im running eg30plus over latest 2.1 midnight.
Sent from my SPH-D710 using xda premium
As WhiteWidows stated, it's 2 different radios. The LOS people have posted over and over about is the ability to make/receive calls (which is what the OP posted about). The Wimax radio (4G) doesn't transmit phone calls. That's why you can do data on 4G and still make a call at the same time.
.....
Hi guys, this is one of my first posts but I've been a long time reader coming from the Evo 4G forums. I'm rooter using Zedomax v3 and experienced multiple LOS as well.
Last night I tried limiting the clock speed to 1ghz and setting the min at 400mhz. Strangly I now get slightly better reception and never had a LOS yet. Will continue to test out this theory and see if it's clock speed related.
I came about testing this since I ran mine at 1.6 for a while and not only would I get more LOS occurances, I would also get phone freezes lol. I tether and stream music a lot so wanted to keep it slightly underclocked to keep the temps down. Hope this helps as a temporary band aid for the LOS bug
It definitely makes sense that the two radios are separate...the point of my post was just to offer some more information to help figure out a fix.
If one radio fails while the other stays working, do we know that the problem is phone-related? Many posters have speculated that the issue may be on Sprint's end, so I wasn't sure if this info did anything to challenge or support that theory. Maybe it does nothing, though -- just throwing it out there!
Someone posted a log cat of a LOS. There's still some coding in the radio files that thinks there is a sim card. Says sim disconnected and result radio off
sent from my DAMN ET4G!!!!
Hopefully a solution is found soon, I've seen similar issues posted on various android forums. Androidforums, Sprint community and here. Wish I waited a bit to hear more user experiences....
Success100 said:
Someone posted a log cat of a LOS. There's still some coding in the radio files that thinks there is a sim card. Says sim disconnected and result radio off
sent from my DAMN ET4G!!!!
Click to expand...
Click to collapse
Has anyone tried editing the build prop to manually change the preferred network from wcdma to CDMA auto? Maybe that'd fix that issue
I have been on my current SGS2 stock out of the box for over a week now and have not had any LOS issues, or missing texts, or data not working, or missing phone calls, etc.....
I have been using wi-fi, 4G, 3G, have an Airaive, went to an area where there is no Sprint service and phone roamed fine and then went back to Sprint service when available.
I have been unable to replicate the LOS issue on my current phone through all possible ways of using it.
My first SGS2 was also fine until I rooted it which then gave me an LOS within 12 hours of doing so.
If someone has a another sure way to get an LOS, I am willing to try it on my stock, never rooted phone but I don't think there are any other situations I can try that I haven't already......
Time.I have went 3 days without a los then 2 in same day.It is all random
As many, many other users of the galaxy nexus have reported, I am having some miserable signal problems. Obviously, CDMA nexus here.
I wish the issue was only that the signal on my phone is bad, but unfortunately it extends beyond that: my entire signal is lost at times. Usually it's intermittent and will happen 4 or 5 times a day for only 30 seconds at most at a time, but sometime (Usually late at night), it will lose its signal for even an hour or two, and I'll watch the battery plummet from as high as 54% to 0 as it searches for a signal the whole time.
I realize this is nothing new for some, but I almost feel like the problem went away for the whole world except for me, due to the low volume of threads related to the issue at all on the boards here. At least, recent ones.
What are my options? I don't really like the idea of trading in my nexus for a refurbished phone. Is 4.03 supposed to solve this problem? I had also read that rooting and flashing radios doesn't make much of a difference. To those of you with the CDMA nexus, what have you done to alleviate this problem? Or are you waiting patiently for an update?
Thank you in advance.
If bought new then return as faulty. Easiest solution.
sent from my Nexus Prime using XDA app
Daramue said:
I realize this is nothing new for some, but I almost feel like the problem went away for the whole world except for me, due to the low volume of threads related to the issue at all on the boards here. At least, recent ones.
Click to expand...
Click to collapse
The problem didn't go away. Most people had to make the decision to either live with it or trade it in on a RAZR or Rezound.
Daramue said:
What are my options?
Click to expand...
Click to collapse
You could:
1. Trade it in for another GNex, on the "hopes" that yours is defective.
2. Trade it in for something else.
3. Live with it & wait it out on the hopes that someday Verizon will ship updated radios that will help. Current rumors say that could still be a couple of months away...
I am on the option 3 plan.
The leaked 4.0.3 radios have had limited & mixed results. For those who they do help, they don't seem to do a whole lot. There are a couple of people who had really good luck. Pretty much the same story for those of us who got Hardware version 10 phones - Haven't noticed any appreciable difference between it and the 9 I got on opening day.
Good luck!
strongergravity, thank you, that was extremely helpful; I was curious to how my fellow Nexus bretheren were dealing with the issue.
If a potential update can fix the radio, then I too will stick with number 3 as you have. Call me a masochist, but this thing is just too nice to part with.
Thank you very much for the detailed response.
Daramue said:
strongergravity, thank you, that was extremely helpful; I was curious to how my fellow Nexus bretheren were dealing with the issue.
If a potential update can fix the radio, then I too will stick with number 3 as you have. Call me a masochist, but this thing is just too nice to part with.
Thank you very much for the detailed response.
Click to expand...
Click to collapse
I just saw your thread right after I created the exact same one today! I was just wondering what you ended up doing. No one has answered definitively as to whether or not this is happening on all phones. If an exchange will fix it, I would gladly go tomorrow. I know most phones are having trouble with the 3g/4g handoff but that is not the same issue we are having. What do you think!?
Mike
Same problems I've experienced. I'm on my second gnex, same issues.
Also I pulled speed tests next to other Verizon 4g phones (razor,rezound,TB) they all had significantly higher speeds than mine . I did multiple tests around our site, they had at least twice the speed as mine.
The razr pulled three times my speed most the time. 30+mb/s vs 10
The thunderbolt was around twice as fast downloads but uploads were even.
And the rezound was double on both uploads and downloads
I used the speed test app and speakeasy online.
Sent from my Galaxy Nexus using Tapatalk
Another comparison I did was turning on airplane mode on and off on all phones simultaneously. And switching 3g only on/off. To see which phones would latch on to 4g first.
Again the gnex was the slowest.
I really wish we received an update to fix this I love this phone!
Sent from my Galaxy Nexus using Tapatalk
I posted this earlier on another thread hoping it will get more views here.
So, I'm having the same exact problems but i did a log cat to see what might be culprit.
I have narrowed it down to this:
02-08 11:21:51.912 E/IMSFW (415): IIL: Disconnected from '7467' socket
still have no idea what can cause it yet.
also if you switch to 3g it seems it doesn't happen so maybe its a sim problem on verizons lte network end?
11:22:40.029 E/IMSFW (415): ImsSMSInterface: Registration failed, go for retrying if isim nounce present
that's what i found so if anyone can clarify and maybe see if it is really on Verizons end as this is the 4th phone that has had this problem
I will be going to verizon tomorrow to "try" and get a new 4g sim card and see if that helps somewhat.
that1techguy said:
I posted this earlier on another thread hoping it will get more views here.
So, I'm having the same exact problems but i did a log cat to see what might be culprit.
I have narrowed it down to this:
02-08 11:21:51.912 E/IMSFW (415): IIL: Disconnected from '7467' socket
still have no idea what can cause it yet.
also if you switch to 3g it seems it doesn't happen so maybe its a sim problem on verizons lte network end?
11:22:40.029 E/IMSFW (415): ImsSMSInterface: Registration failed, go for retrying if isim nounce present
that's what i found so if anyone can clarify and maybe see if it is really on Verizons end as this is the 4th phone that has had this problem
I will be going to verizon tomorrow to "try" and get a new 4g sim card and see if that helps somewhat.
Click to expand...
Click to collapse
I just went to the store and swapped out my 4g sim card... I dropped two calls on the way home from the store so I'm not sure it helped at all. Hopefully it didn't make it worse though!
I also checked my speeds and service against some other phones in the store and the Droid Razr destroyed my nexus and some other stock nexus that were there usually 12mpbs vs my 8 and 1mbps upload vs their 3.
Well I got my issues fixed today I was on tech support for an hour and he suggested to go to a store and get the sim card replaced. And that solved all my issues
Another problem I had was when using the headset for calling the person on the other line would here themselves. This has also gone away, I am so relieved I love this phone and did not want to abandone it.
Well, I did a bit of a test.
I kept my phone on 3g the whole day: Signal did not drop even for a single MOMENT in the entire day. Sure, there are times where it was bad, but my connection never entirely dropped. This leads me to believe that the problem lies with transitioning between 3g and 4g, or perhaps is just entirely related to 4g.
With the LTE network, I will have anywhere between 3% - 50% time with "no signal." It's extremely annoying and I'll always watch as my battery tanks extremely fast.
Maybe it's worth replacing the SIM card or at least, pulling it and putting it back in. Posting this here for others that are troubleshooting this same problem. I'll report back.
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.
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.
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...