Related
Hey everyone, I looked around and didn't find anyone having my particular problem, but If I put this in the wrong place, or someone has already solved it, just let me know. Don't want to waste your time!
I got my DINC the day they came out in stores...the first one my local store sold in fact. It was working great, but I hated the bloatware and the fact that the Bluetooth stack was not up to date...couldn't connect with a new hands free speaker phone I just bought (Parrot mini-kit slim). I had occasional random reboots, but not too many. Once or twice a week maybe.
So when the unrevoked one-click came out I tried it. Worked great.
Then I started trying ROMs. With everything I've tried I get random reboots...a lot of them. Sometimes it reboots once and works fine for a couple hours. Other times, it will loop until I do a battery pull. When it loops it will sometimes make it all the way to the lock screen, sometimes it will only make it to the boot animation, and sometimes it won't get past the white HTC screen.
I've used a couple different nightly builds of CM6, with and without google apps. I've used Skyraider 1.8 and 1.9 with and without sense. I've tried "touch of photons". Same results and activity on all of them.
Last night I gave up and downgraded to unrooted 2.1 with sense...factory fresh. I reformatted my SD card with the phone, reformatted the phone storage, and I've done factory resets. It still isn't working right.
At this point, I'd be happy to get it back to pre-Unrevoked and just wait for the official OTA Froyo which is supposed to come out soon. Rooting and using a stable rom is fine with me too. I just need a phone that works consistently.
Any ideas? I'm pretty desperate.
sounds like you needed to return it and get a new one since it was doing random reboots from the day you bought it.
have you used any of the hydra kernels to try and OC it, the 1.15 OC would cause mine to reboot. a good stable rom that i tried was JagerRom, 1.7.4 is without sense, and chocolate is with sense. don't try the OTA one because that is for people who updated to the OTA leak and im going to assume you aren't one of thoes people. haha
http://incredibleroms.com/roms/jager/
hope this helps
Thanks Stroupified...
The weird thing is that the reboot issue wasn't that big of a deal before I rooted and started flashing roms. It happened, but not enough to be a problem.
Does the camera and camcorder work on Jager?
Does anyone know if there is something that could have gotten messed up with unrevoked or the roms I tried?
Is there another downgrade method I can use? I just installed the PB31IMG.zip you can find in a few places out there...is there a known reliable source for the downgrade zip?
If I can avoid fighting with Verizon on this I'd like to. I'm obviously outside my 30 days, and I don't want to wait a week or 2 or three or more for a new incredible (if I can convince them to get me one). I'm not even sure warranty or Asurion will do anything with this kind of a problem either...I fear I'm stuck with a $500 reboot roulette machine.
re
i have gone through 4 incredibles.
they all exhibited the same rebooting issues... completely stock with NO installed apps.
I have also tested the phones with 2 different batteries and with different sd cards and no sd cards installed.
I had done factory resets.
I get a ****ty cell connection where i live, -100 to -96 db.
Its looking more like a tower issue..
I also have had a reboot issue. I rooted the phone the day I got it and installed a senseless rom. It worked perfect the 1st day then started into a downward spiral of reboots till it went into a full boot loop. I did a nandroid back up of the original rom. No real issues since. Im still rooted and have only had one random reboot in about a week that I know of. I know the first issue was because of the rom but what causes the random reboots. Is it aloss of signal? Im a noob so Im just trying to get some insight.
Im on #2
I got my 2nd Incredible on Friday. Prior one would just get hotter and hotter (possibly due to signal issues) until it would enter a reboot loop. Hoping # 2 fares better.
johnsquared said:
Thanks Stroupified...
The weird thing is that the reboot issue wasn't that big of a deal before I rooted and started flashing roms. It happened, but not enough to be a problem.
Does the camera and camcorder work on Jager?
Click to expand...
Click to collapse
ya everything works in jager. but from what everyone else is saying it seems like it could be the signal (or lack there of) that's causing the reboots. have you tried the hybrid prl? it uses the verizon and altell towers instead of just the verizon ones. i haven't tried it because im in cali and there aren't any altell towers near me, but if your stuck with the phone you might as well give it a shot if you live in the supported areas. good luck man.
Link to PRL thread:
http://forum.xda-developers.com/showthread.php?t=723829
If you don't have problems with signal don't bother with the hybrid prl... it kills your data speeds because it switches you from Verizon data network to Sprints data in most areas. I know in the Carolinas phones randomly reboot a lot because thats Alltel country and phones don't work properly without the hybrid. But down south its mostly Verizon. Out west Texas/Ok is mostly Alltel.
But man honestly - I have the same issue on custom roms. My stock Sense rom does fine though. Sometimes I'll be on a custom rom typing a text and the keyboard just freezes and its over. lol nandroid time to me - I can't take the reboots but hate not having the features of newer software.
re
i have tried the hybrid prl and it did not help my rebooting issues.
i have also tried switching to the the cdma codec to -b the higher quality compression... with no luck in fixing the reboots.
I have also made sure there was not an issue with an app causing it, i have tested mine with a clean / factory reset with absolutely no apps installed.
I have had 100% good luck with the leaked ota update, the one upped the camera to 720p recording as well as a hand full of other fixes, and not once did my incredible reboot or crash.
I'm pretty confident that htc has fixed this issue for me, once they drop the 2.2 update that everybody seems to be speculating will be released in a handful of weeks.
Thanks for the input everyone, and I'm sorry others are having the same problem.
I went by my local Verizon store (actual Verizon store, not a 3rd part dealer) and told them my phone was rebooting repeatedly. They didn't even touch my phone...I was out of there in 5 minutes with a FedEx 2nd Day Air confirmation number for a new handset. And my wallet is intact also. I'm rarely impressed by Verizon's customer service, but this time...man... Between the new handset and the impending 2.2 update, I hope to be in good shape.
Me Too
johnsquared said:
Thanks for the input everyone, and I'm sorry others are having the same problem.
I went by my local Verizon store (actual Verizon store, not a 3rd part dealer) and told them my phone was rebooting repeatedly. They didn't even touch my phone...I was out of there in 5 minutes with a FedEx 2nd Day Air confirmation number for a new handset. And my wallet is intact also. I'm rarely impressed by Verizon's customer service, but this time...man... Between the new handset and the impending 2.2 update, I hope to be in good shape.
Click to expand...
Click to collapse
Same EXACT thing happened with me and telesales. No scripts, no hard reset, no task killer; NOTHING. Said "my phone gets hot and reboots" and they said (last Thurs), let's get you a replacement overnight so you can try the new one out of the weekend. No muss, no fuss. Got here 10:30AM the next day, and my evil super-heating 4-to-13-reboot-try prone phone is going back.
sprintrjm said:
i have gone through 4 incredibles.
they all exhibited the same rebooting issues... completely stock with NO installed apps.
I have also tested the phones with 2 different batteries and with different sd cards and no sd cards installed.
I had done factory resets.
I get a ****ty cell connection where i live, -100 to -96 db.
Its looking more like a tower issue..
Click to expand...
Click to collapse
I don't believe towers/signal would have any effect on shutting down or booting. Basically once you're on a current PRL, you really shouldn't even have to update it. Unless you're having that poor service deal where an Alltell/Vzw hybrid would benefit you.
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
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...