Please Help - Signal Drops + Forced Calls to voicemail - Samsung Galaxy Nexus

This issue seems to be all over the place, but I'm having extreme problems getting it fixed.
My GSM galaxy nexus regularly loses all signal everywhere I normally get full bars.
Also, sometimes I'll look at it WITH signal, and it enables Call forwarding and leaves that on until I go into the settings and try to disable it. (There is no option to disable it tho...it just automatically disables after it takes a minute to load call forwarding settings).
Has anyone else been having these problems and been able to fix it? I flashed new radios, roms, kernels....everything! And I just can't get the problem solved. Recently I flashed the UGLC1 radio and that worked for a couple days but now it's just as bad as it ever was.

MarkB709 said:
This issue seems to be all over the place, but I'm having extreme problems getting it fixed.
My GSM galaxy nexus regularly loses all signal everywhere I normally get full bars.
Also, sometimes I'll look at it WITH signal, and it enables Call forwarding and leaves that on until I go into the settings and try to disable it. (There is no option to disable it tho...it just automatically disables after it takes a minute to load call forwarding settings).
Has anyone else been having these problems and been able to fix it? I flashed new radios, roms, kernels....everything! And I just can't get the problem solved. Recently I flashed the UGLC1 radio and that worked for a couple days but now it's just as bad as it ever was.
Click to expand...
Click to collapse
if youre on stock just update to IMM76I thats the build just released to solve these issues
if your on a custom rom you may want to flash a kernel that has incorporated these fixes GLaDOS 1.30 for example

Related

[Q] Call Disconnected - Any Advice?

I've been seeing this problem for a few weeks now, with several different ROMs, including the original rooted stock ROM now. In nearly all of my recent calls, I get disconnected one or more times with the message "Call disconnected" and a "Dismiss" button. I'm thinking that this is because of my EVO and not the other side, since usually if they accidentally hang up or something the call just ends without a message box. As far as I can tell, I have good reception (at least according to the bars), and this is happening at home, where I've not had the problem before.
Does anyone know what could be causing this? My wife's EVO is not rooted, and she does not seem to be having this problem. But then again, I've not had the problem until fairly recently either. I've tried updating my profile and PRL with each new ROM, but it doesn't seem to have made a difference. Anyone have any suggestions as to how to stop this from happening?
Go into the settings menu andbupdate both your PRL and your profile. That *should* help with reception related issues.
posting & replying via the XDA Premium app.
Unfortunately, I've tried both of those things. I just did some testing today, and it seems that my phone is unable to stay connected during a phone call for more than five minutes before disconnecting, even if I don't touch the phone and just leave it sitting on a table.
Any other ideas? As far as I know, I haven't ever flashed my radio away from its default (2.15.00.11.19), and I'm currently using the leaked stock gingerbread ROM (build number 4.12.651.1 CL41771 release-keys and kernel 2.6.35.10-gaa602b7 [email protected] #1).
Maybe it's time to unroot and contact Sprint?
You can try downgrading from 2.15.00.11.19 to 2.15.00.09.01. You can download it from http://www.mediafire.com/file/jyedjkp1bm5amwm/EVO_Radio_2.15.00.09.01.zip
Afterwards, go into recovery, wipe cache & dalvik cache then flash the zip. You will be taken to the radio update screen and appear to hang. don't worry or get impatient. After it is finished, you will reboot into recovery and see the words "clearing cache" at the top of the screen. Simply select reboot and then you will boot to your homescreen. The initial boot will take a tad longer since it will be rebuilding the dalvik.
Hmm... I'm hesitant to downgrade my radio because my wife has an EVO with the same radio version number and hers doesn't have this problem. Granted, she is not rooted...
I understand. I've downgraded and upgraded everything several times for testing purposes and troubleshooting purposes and have never had a problem. The only hing about flashing radios is patience and not to pull the battery. Anyway, you can always call Sprint and see if they can troubleshoot it for you from their end.
posting & replying via the XDA Premium app.
I would contact sprint @ 877-809-6696 (advanced tech supp). Ask them to push a full reprovision to your device. See if that helps any. I was having issues when when on the airave, I was unable to receive incoming calls. This corrected it. I did try all the other steps listed above without any success.
This is interesting. I unrooted to test things out before calling Sprint, and the problem went away. I was able to stay connected for an hour (where before I couldn't last longer than 10-15 minutes). Yay, fixed, right? So, I rooted again and didn't install any ROMs or anything, just rooted, and the problem came back.
So, I have a solution, but I don't like it very much because it means I need to stay unrooted. Anyone have any idea why simply rooting the phone with Unrevoked 3 (and doing nothing else) could cause calls to disconnect? I'd love to be able to root again, but I can't deal with a phone that randomly disconnects all the time.
I am interested in this as well as I am rooted using unrevoked and get disconnected as well. I do find that it mainly happens though talking to people who have service on AT&T.. Quite wierd. All I hear is a beep then disconnected. This happens when I first place a call and it rings once or twice then beep, disconnected...
This may not be related to rooting. I'm still communicating with Sprint about this issue, and along they way they replaced my phone entirely, and the problem is still happening. Very frustrating, but it makes it very clear that the problem actually has nothing to do with the hardware. I'm pretty sure there is some network configuration problem on their end now. I'm waiting to root my new phone until this issue has been resolved. It is killing me!
KingFunderberk said:
This may not be related to rooting. I'm still communicating with Sprint about this issue, and along they way they replaced my phone entirely, and the problem is still happening. Very frustrating, but it makes it very clear that the problem actually has nothing to do with the hardware. I'm pretty sure there is some network configuration problem on their end now. I'm waiting to root my new phone until this issue has been resolved. It is killing me!
Click to expand...
Click to collapse
So whats the final call on this ..?
Is it Rooting , Is it network .. i am too getting psyche with this .
I'm pretty sure it is not rooting. But I don't yet know for certain what it is. Sprint thought there might be something wrong with the antenna on my phone, but they had already replaced the phone, so I think that is unlikely. They gave me a femtocell range extender to use in my house. Basically, I plug it into my broadband connection, and it is like having a mini cell tower in my house, giving me a very strong connection. Sure enough, when connected to that, I haven't had any calls drop. However, my phone still sometimes doesn't connect to the femtocell and instead connects to some other tower for some reason. My wife's phone doesn't do this, so I still think there is something wrong with my phone. I may contact Sprint again about this. ...sigh...
What is your area some area evo don't work properly like on rahim yar khan in this time connection don't work properly some signal drop and some time up i sure after few day signal work properly then problems will be solve.
My phone EVO is doing this now as well. Has anyone heard/read a solution?
greg_99 said:
My phone EVO is doing this now as well. Has anyone heard/read a solution?
Click to expand...
Click to collapse
I am having the same issue, out of the blue. No problems up until a few days ago. I'm wondering if it is maybe an issue with a certain version of the Evo. I have a version 002. Thoughts?
Greg_99 any progress on what might be causing this issue?

[Q] Signal Lost with Screen Sleep

So first a little bit about my phone:
It's a GSM Galaxy Nexus on Telus in Canada. It's rooted and running AOKP M4. I had just flashed Franco Kernel M2, but that's when my trouble started to I just wiped my data, reflashed AOKP M4 and restored from a back-up from before I flashed that kernel. I've never flashed a new radio.
The problem is as follows: when the screen goes to sleep, I lose signal altogether. I don't receive calls, I don't receive texts, nothing. But as soon as I wake the screen, the signal comes back (and it's strong - 3 or 4 bars so it's not a service issue).
Has anybody else had a similar problem? What's the fix?
Any help would be appreciated...thanks!
------------UPDATE--------------
Confirmed that I had no issues after flashing back to 4.0.2 stock. Went back to stock 4.0.4 and the problem surfaced again. Tried B29 of AOKP and utilized a minimum CPU setting of 700 MHz which resulted in no issues with the phone signal after going to sleep. I was able to duplicate the problem when I set the CPU to a minimum of 350 MHz. Went back to 700 MHz minimum and everything is working fine.
I'm wondering if the stock 4.0.4, in an effort to squeeze more battery life, lets the processor speed dip down below the threshold require to keep the phone "listening".
-------------------------------------
I've had the same issue after upgrading my phone to 4.0.4. It started life as a 4.0.2 GSM GNex with the Samsung ICS build on it. I flashed the Google version, then manually updated to 4.0.4. I've been searching the forums and found quite a few people with the same problem, but no real solution yet. I'm going to try a few things before taking a swag at a new radio.
I have the exact same problem
I have a GSM Samsung Galaxy Nexus on Vodafone, and within about 2 minutes of the screen sleeping, it loses connection to the network. When awakened, it will re-establish the connection within 5 seconds or so, but it is intensely irritating as I have missed lots of phone calls with this bug.
It has occurred on both my 4.0.2 patched to 4.0.4 and a clean install of 4.0.4 from google's website
I am about to revert back to 4.0.2, but if anyone can fix it in the meantime I would be eternally grateful.
-------------------------------- UPDATE ---------------------------------------------
I concur with warhummer. After rooting my Nexus again after the 4.0.4 update, and installing CPU Tuner from the Market place, I increased the minimum CPU speed to 700mhz (up from 350mhz) and it appears to be keeping its signal now. This would also tally with the fact that while my Nexus was doing things in the background it would maintain signal, but as soon as it was idle, within a few minutes the signal would die.
--------------------------------------------------------------------------------------
memoreks said:
I have a GSM Samsung Galaxy Nexus on Vodafone, and within about 2 minutes of the screen sleeping, it loses connection to the network. When awakened, it will re-establish the connection within 5 seconds or so, but it is intensely irritating as I have missed lots of phone calls with this bug.
It has occurred on both my 4.0.2 patched to 4.0.4 and a clean install of 4.0.4 from google's website
I am about to revert back to 4.0.2, but if anyone can fix it in the meantime I would be eternally grateful.
Click to expand...
Click to collapse
I've confirmed a fix (for myself anyways) that if you can get a CPU app that can modify the processor speed, try that via the stock 4.0.4. I'm going to flash mine now.
I have the exact same problem. I was on a Rom stock 4.0.2 with root, and after flashing the OTA, I had the problem when the screen is off.
To be sure I flashed the factory image in 4.0.4 but I still had the problem.
I looked at logcat and I had this error that seems to be the problem:
Code:
03-30 15:58:16.639 E/ConnectivityService( 186): Exception trying to remove a route: java.lang.IllegalStateException: Unable to communicate with native dameon to add routes - com.android.server.NativeDaemonConnectorException: Cmd {interface route remove rmnet0 default 10.114.222.1 32 0.0.0.0} failed with code 400 : {Failed to remove route from default table (No such process)}
03-30 15:58:16.639 E/ConnectivityService( 186): Exception trying to remove a route: java.lang.IllegalStateException: Unable to communicate with native dameon to add routes - com.android.server.NativeDaemonConnectorException: Cmd {interface route remove rmnet0 default 0.0.0.0 0 10.114.222.1} failed with code 400 : {Failed to remove route from default table (No such process)}
I'm going to send my phone to repair and hope they change it, or if someone has a solution.
Right now I flashed the 4.0.2 factory image to be able to use my phone.
PS : maybe someone know how to contact a Google dev ? To report the problem to them ?
SetCPU fixes it
How to sort out the problem of losing signal when GNexus goes into Standby:
1. Install 4.0.4 Stock ROM
Either use the OTA patch or do a clean 4.0.4 install from the Google Stock ROMs page.
2. Root your GNexus
There's lots of info about rooting you GNexus. I used CWM to root mine.
3. Install SetCPU
4. Run SetCPU, and raise the minimum CPU speed from 350mhz to 700mhz. Then tick "Set on Boot". (see attachment)
This should now mean your phone functions perfectly well again, and you benefit from the other good stuff in 4.0.4.
Thank you for the solution, but I don't want to achieve it that way for me there is a real problem with probably a hardware piece or something.
I contacted Jean-Baptiste Queru on Twitter, and he said that he will see who can talk to for this.
In the meantime, my Galaxy Nexus is going for repair in the hope I will have a brand new one
mephissto said:
Thank you for the solution, but I don't want to achieve it that way for me there is a real problem with probably a hardware piece or something.
I contacted Jean-Baptiste Queru on Twitter, and he said that he will see who can talk to for this.
In the meantime, my Galaxy Nexus is going for repair in the hope I will have a brand new one
Click to expand...
Click to collapse
i'm having this problem too. but would it be a hardware problem? i don't remember this happening in 4.0.3. you might just be returning it for another phone with the same problem if you update to 4.0.4
It might be a harware problem caused by a some code that was not in Android 4.0.2
I tried CyanogenMod 9 which is on Android 4.0.4 (same bootloader and radio as stock 4.0.4) but AOSP and I had the same issue.
It's really stranged because there are not a lot of people that have this issue.
Let's hope we will have news from Google soon
I stopped having this problem in 4.0.2 and 4.03, when I updated to 4.0.4.
mephissto said:
It might be a harware problem caused by a some code that was not in Android 4.0.2
Click to expand...
Click to collapse
then that's called a software problem lol
mephissto said:
It might be a harware problem caused by a some code that was not in Android 4.0.2
....
It's really stranged because there are not a lot of people that have this issue.
Let's hope we will have news from Google soon
Click to expand...
Click to collapse
I also have exactly the same errors in logcat.
Sent from Galaxy Nexus
I have raised a bug report with Google
I have raised a bug report with Google.
Unfortunately I cannot post a URL, so you need to go to:
code.google.com/p/android/issues/list and search for issue 28133
It might help if those of you who are experiencing this problem add comments to the post, try and raise its profile with Google somewhat.
@ceejay83 : I know, but only a few devices have this issue, that's why I assume it's also related to hardware.
@memoreks : Thanks for the link, I'll go there to also post a comment.
---------- Post added at 11:17 PM ---------- Previous post was at 11:08 PM ----------
Here is the link to the issue on Google code : http://code.google.com/p/android/issues/detail?id=28133
Please star this issue so Google notice it
I've starred the issue at the link posted, and I'm trying radio UGLC1 from the link below to see if it helps to use a newer radio.
http://forum.xda-developers.com/showthread.php?t=1405345&page=37
I found this thread about radios days ago, where you can find all existing radios, if you want to try others.
http://forum.xda-developers.com/showthread.php?t=1405345
Found your thread on google code. This is what I posted there:
I have a similar issue. My phone doesn't lose signal for good, it just drops and comes back on 5 seconds later and this loop keeps repeating with random times between drops(1 minute intervals most of the time). It started right after updating to 4.0.4. I installed an app to help track when signal drops, I attached and screen of the app. I also tested with AOKP build 28 based on 4.0.3 and the problem was still there. I will test a 4.0.2 build soon.
does it only happen in a weak 3g area? i noticed my phone having signal problems after updating to 4.0.4 too. In the secret menu, *#*#4636*#*# the preferred network type is set and stuck to wcdma preferred and if you are like me and are in a weak 3g area the phone will still prefer a weak 3g to a strong 2g signal. it prefers 3g so much that it will still hold on to it for hours even when the signal is too weak to make or receive calls. With 4.0.2 it was set to gsm/cdma prl which prefers a strong 2g but will switch when there is a strong 3g signal. unfortunately you cannot change this setting in 4.0.4.
i tried ugkl1, ugla4,, xxla2 and now using uglc1. they all had similar signal strength and will hang on to a weak 3g, so i dont think the radio is at fault here. an option for those running aokp is to go into the power saver settings and you can set your phone to go to 2g when the screen is off.
I have been having this issue since 4.0.3 on my GSM Nexus. I have tried multiple radio's and multiple kernels. I was having to change the min cpu to 700mhz. I tried FuGuMod's Kernel and it seems to have fixed my signal issues. I am able to keep the min cpu at 350mhz. If you search the thread he explains what he thought was causing the issue. Once he disabled that feature in the kernel my signal issues went away.
http://forum.xda-developers.com/showthread.php?t=1438417
I think its a mix between software and hardware issues. There is some software setting that the hardware doesnt like. But since this doesnt happen to everyone running a certain kernel and only some people there must have been a bad batch of hardware from samsung.
I think I am going to try a warranty exchange with Samsung.
For me at least, it is occurring in both 2G and 3G areas. I have tested it in both, and also in strong and weak reception areas.
Memoreks
Sent from my Galaxy Nexus using xda premium

Sprint Galaxy Nexus - Modem Stability Issues

So, I figured I'd share since I couldn't find much information on the forums about this.
I recently, within last few weeks, started having issues with the modem on my GNex.
I had been running a ROM derived from AOSP Jelly Bean without issue, except the modem seemed to get poor signal quality.
I tried to upgrade the modem once the official Sprint JB release of FH05 started spreading.
At some point afterwards it seemed the modem would inexplicably start to die periodically... (By die I mean the status would change to searching and/or not connected and the status icon would change to no service icon). I could sometimes trigger life back in at times by toggling CDMA/LTE or CDMA Only options or the data enabled options or rebooting...
I went through a period of continually trying to reflash the various radios FD02, FC12, FH05... all in an attempt to get stability.
I had persistent issues even trying to flash the radios. The LTE radio would always flash fine, but the CDMA radio would often hang in flashboot forcing me to sever connection and restart.
This never seemed to fix the issue and I began to think I might either have bad flash memory on the radio partition or there was a problem with the radio hardware causing this issue.
I then remembered I had dropped the phone on concrete and it landed on the modem side of the phone... phone seemed fine besides a few new dings, but operated ok. I considered maybe this had something to do with the state of things.
Last night I took my phone back off using these instructions: http://www.ifixit.com/Teardown/Samsung-Galaxy-Nexus-Teardown/7182/1
I basically just jostled the internals a bit hoping to fix maybe a simple misalignment...
It has been a solid 12 hours and everything seems to be running strong.
This is purely speculation, but given that I haven't been able to consistently replicate any scenario other than it not working... I am hoping this is the fix.
I hope it might help someone else, or someone else with a similar problem can confirm or provide alternate conclusion.
I am currently running:
ROM:
http://forum.xda-developers.com/showthread.php?t=1801942
LTE and CDMA FH05:
http://forum.xda-developers.com/showthread.php?t=1620036#2
TWRP 2.2:
http://teamw.in/project/twrp2/92
shadowspires said:
So, I figured I'd share since I couldn't find much information on the forums about this.
I recently, within last few weeks, started having issues with the modem on my GNex.
I had been running a ROM derived from AOSP Jelly Bean without issue, except the modem seemed to get poor signal quality.
I tried to upgrade the modem once the official Sprint JB release of FH05 started spreading.
At some point afterwards it seemed the modem would inexplicably start to die periodically... (By die I mean the status would change to searching and/or not connected and the status icon would change to no service icon). I could sometimes trigger life back in at times by toggling CDMA/LTE or CDMA Only options or the data enabled options or rebooting...
I went through a period of continually trying to reflash the various radios FD02, FC12, FH05... all in an attempt to get stability.
I had persistent issues even trying to flash the radios. The LTE radio would always flash fine, but the CDMA radio would often hang in flashboot forcing me to sever connection and restart.
This never seemed to fix the issue and I began to think I might either have bad flash memory on the radio partition or there was a problem with the radio hardware causing this issue.
I then remembered I had dropped the phone on concrete and it landed on the modem side of the phone... phone seemed fine besides a few new dings, but operated ok. I considered maybe this had something to do with the state of things.
Last night I took my phone back off using these instructions: http://www.ifixit.com/Teardown/Samsung-Galaxy-Nexus-Teardown/7182/1
I basically just jostled the internals a bit hoping to fix maybe a simple misalignment...
It has been a solid 12 hours and everything seems to be running strong.
This is purely speculation, but given that I haven't been able to consistently replicate any scenario other than it not working... I am hoping this is the fix.
I hope it might help someone else, or someone else with a similar problem can confirm or provide alternate conclusion.
I am currently running:
ROM:
http://forum.xda-developers.com/showthread.php?t=1801942
LTE and CDMA FH05:
http://forum.xda-developers.com/showthread.php?t=1620036#2
TWRP 2.2:
http://teamw.in/project/twrp2/92
Click to expand...
Click to collapse
So you just took apart and reassembled and that got it working?
Maybe
xvanwilderx said:
So you just took apart and reassembled and that got it working?
Click to expand...
Click to collapse
Tried to sell phone on ebay because the wifi adapter was showing issues with range... I bought another and it was clear that the range of the older phone was having issues...
Tried to sell on ebay and buyer couldn't activate... just sent back and I can't get it to accept a flash at all... maybe trying the taking apart trick again...
Crazy

[Q] Text messages and calls not being received

I've been having a problem with receiving texts sometimes and I recently noticed that it happens with call apparently. The issue is that I'm texting people back and forth and then all of a sudden I wont receive messages for a long time (couple hours). At some point, someone's text message will push through all of the other ones all at the same time. Sometimes when I assume i'm having this issue, I will send a text to myself and it will push the other ones through as well. Recently though I was made aware that during this "outage", I also was not able to receive phone calls at all. The signal is strong at all times (3-4 bars). Also happens when I'm home all day and not changing locations when it will suddenly stop getting texts and calls. Does anyone know how to fix this issue? I restarted the phone and changed cell towers with the Airplane mode many times and the issue continues to happen at random times. It is really inconvenient. Suggestions?
Technical details: I use the stock 4.1.1 Rom that comes with AT&T S3. I do have LTE in my area.
And now it has happened 3 days in a row but at different times of day. This is a huge problem for me as I use my phone a lot. Any help would be appreciated
You still have your IMEI number via settings -> about phone -> status?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
ARPLEMODE
TRy making sure yiur not in airplane mode. i was stuck in airplane for a week ._____________.:cyclops:
That's weird. Re-seat your SIM card, if that doesn't do anything then take a trip to your nearest AT&T store/dealer and have them swap out your SIM card and see if it still occurs after that.
I had a similar problem a while back and it happened to be a network problem with my carrier. Gave them a call and all is fine now.
Sent from my SGH-I747 using xda app-developers app
fafik90 said:
I've been having a problem with receiving texts sometimes and I recently noticed that it happens with call apparently. The issue is that I'm texting people back and forth and then all of a sudden I wont receive messages for a long time (couple hours). At some point, someone's text message will push through all of the other ones all at the same time. Sometimes when I assume i'm having this issue, I will send a text to myself and it will push the other ones through as well. Recently though I was made aware that during this "outage", I also was not able to receive phone calls at all. The signal is strong at all times (3-4 bars). Also happens when I'm home all day and not changing locations when it will suddenly stop getting texts and calls. Does anyone know how to fix this issue? I restarted the phone and changed cell towers with the Airplane mode many times and the issue continues to happen at random times. It is really inconvenient. Suggestions?
Technical details: I use the stock 4.1.1 Rom that comes with AT&T S3. I do have LTE in my area.
Click to expand...
Click to collapse
It happend to me too. I went to att store and get new sim. No problem for last 15-20 days. Looks like i got stronger signal too.
Just to give anyone interested in this an update:
I went to the AT&T store today and told them my issue so they told me to go to the nearest AT&T device support center (which was really far away). People over there told me they heard about this issue many times over the past couple of months. The guy working there had a S3 and said he has the same problem. They received an email from the higher-ups this morning specifically talking about this random outage thing I have and that they are currently working on it. They were told to not exchange phones or sim cards because of this since it wont help. The issue involves a combination of Network and Jelly Bean software problems and happens on all new LTE devices that have Jelly Bean from AT&T. They told me to check periodically if there is a solution.
I guess I just gotta wait. Unless someone recommends a ROM that is not based on the latest AT&T jelly bean?
Bumping it up, both me and my wife have had this happen. From what im read its a pretty widespread deal.
Anyone know of a work around at least until they fix it?
Keep us updated
Same problem here - switched from Verizon to AT&T last month and started noticing this problem a few weeks ago. Back then a Google search didn't find much on it, but this thread looks promising.
Just to add my two cents: I'm on a rooted S3 with task650's AOKP (4.2.1) build 12.23.2012 (link). Made sure to flash the modem for my phone (I747UCLI5 from here). Problem: phone randomly won't receive calls or texts. Sometimes calling someone will fix it.
I read somewhere that on AT&T, calls and texts are received over 3G and sometimes phones have difficulty switching from 4G. Anyone know if this is true?
Do a full wipe /system, /data, /cache, /dalvik cache. And your problems should be gone 9 times out of 10 that's usually everybodys problem
Sent from the scary door....
fafik90 said:
I've been having a problem with receiving texts sometimes and I recently noticed that it happens with call apparently. The issue is that I'm texting people back and forth and then all of a sudden I wont receive messages for a long time (couple hours). At some point, someone's text message will push through all of the other ones all at the same time. Sometimes when I assume i'm having this issue, I will send a text to myself and it will push the other ones through as well. Recently though I was made aware that during this "outage", I also was not able to receive phone calls at all. The signal is strong at all times (3-4 bars). Also happens when I'm home all day and not changing locations when it will suddenly stop getting texts and calls. Does anyone know how to fix this issue? I restarted the phone and changed cell towers with the Airplane mode many times and the issue continues to happen at random times. It is really inconvenient. Suggestions?
Technical details: I use the stock 4.1.1 Rom that comes with AT&T S3. I do have LTE in my area.
Click to expand...
Click to collapse
I had this same problem except it would only happen on WiFi.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
thatsupnow said:
Do a full wipe /system, /data, /cache, /dalvik cache. And your problems should be gone 9 times out of 10 that's usually everybodys problem
Sent from the scary door....
Click to expand...
Click to collapse
Tried that no go, plus its on 2 different phones.
Found some more info and ended up adding anothe APN and chaning some info in it seems good now.
mrmooney said:
Tried that no go, plus its on 2 different phones.
Found some more info and ended up adding anothe APN and chaning some info in it seems good now.
Click to expand...
Click to collapse
Care to share what you did that fixed it?
fafik90 said:
Care to share what you did that fixed it?
Click to expand...
Click to collapse
Yeah more info here.
http://forums.att.com/t5/Android-Di...ing-Calls-Phone-issue-or-Android/m-p/3404809#
Seems to still be working fine.
I started a thread on this also and just yesterday received some info from AT&T tech.
http://forum.xda-developers.com/showthread.php?t=2123974
guys,
it is an ATT issue,
here is a temp solution for a fix:
1) With phone on, take off back cover and press your SIM card so it releases from the spring. It won't come all the way out as it's blocked by the battery. This seems fine - I didn't bother trying to force it out as I didn't want to break anything...
2) Once you see the message that the SIM card is removed, go to the dialer and dial *#2263#
3) You should see a menu with band selections. The current setting is "Automatic". If you switch to "GSM All", you will be EDGE (2G). If you switch to "WCDMA All", you will be on HSPA+ (3G, though AT&T and others call it 4G).
4) Press the SIM card back into place until it clicks. For whatever reason the phone will not recognize it until you reboot. Upon reboot you should see your new setting in effect
please see, post, comment here:
http://forums.att.com/t5/Android-Di...ls-Phone-issue-or-Android/td-p/3270741/page/3

Toro Network Drops, 4.2.2 and 4.3

Hey guys - my VZW Gnex (it's a refurb to replace my old one with a bad screen) has been having excessive network dropouts lately. When I boot the phone, it doesn't acquire signal for over a minute, when I place a call I lose signal afterwards, and data drops out randomly. The device will say it's connected (blue bars), although I cannot use the internet. Also, it'll randomly loose cellular connectivity, although indicate that it has signal. I'll go to send a text and it'll immediately have send errors, and I am unable to make or receive calls, even though it shows I have signal. To fix, a reboot is always necessary. This has happened on 4.3 (crDroid) and 4.2.2 (CM 10.1.3 stable). It has happened across all the different radios, 4.0.4 and up, and across several different kernels. Does anyone have suggestions, the phone isn't really usable if people can't get in touch and I'm unaware that they can't.
EDIT: When I go into the phone info menu *#*#4636*#*# when the radio has no data, it says preferred network is "unknown." If I change it, the setting immediately goes back to unknown.
U might need to go through the insurance and get another one.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
eriscentro said:
Hey guys - my VZW Gnex (it's a refurb to replace my old one with a bad screen) has been having excessive network dropouts lately. When I boot the phone, it doesn't acquire signal for over a minute, when I place a call I lose signal afterwards, and data drops out randomly. The device will say it's connected (blue bars), although I cannot use the internet. Also, it'll randomly loose cellular connectivity, although indicate that it has signal. I'll go to send a text and it'll immediately have send errors, and I am unable to make or receive calls, even though it shows I have signal. To fix, a reboot is always necessary. This has happened on 4.3 (crDroid) and 4.2.2 (CM 10.1.3 stable). It has happened across all the different radios, 4.0.4 and up, and across several different kernels. Does anyone have suggestions, the phone isn't really usable if people can't get in touch and I'm unaware that they can't.
EDIT: When I go into the phone info menu *#*#4636*#*# when the radio has no data, it says preferred network is "unknown." If I change it, the setting immediately goes back to unknown.
Click to expand...
Click to collapse
This is a known issue with 4.3 ROMs. I'm not sure about 4.2.2. It looks like CM 10.2 may have a fix for it in the next nightly. One known fix is to edit build.prop to include
ro.telepohny.default_cdma_sub=0
Thank has worked for me.
dlabadie said:
This is a known issue with 4.3 ROMs. I'm not sure about 4.2.2. It looks like CM 10.2 may have a fix for it in the next nightly. One known fix is to edit build.prop to include
ro.telepohny.default_cdma_sub=0
Thank has worked for me.
Click to expand...
Click to collapse
I've added that line, doesn't help

Categories

Resources