01-16-2013 11:27 AM
That's what I do with my galaxy s3 right now. I have to disable Wifi for my phone to start acting like a phone and receive calls. I don't have unlimited data so this temporary fix has bad consequence.
How did you ended up with solution of turing off wi-fi?
Who said it's due to wi-fi?
01-16-2013 1:14 PM
I have been having this issue since last 2 months. I have done everything as per AT&T's guidelines but nothing worked. (changed SIM, changed phones, factory resets) Even after all this AT&T is not ready to admit its fault. And they are treating this issue as "User Issue"
I have posted on AT&T's facebook page and I seem to be getting responce from AT&T. I also received a call from AT&T public relations this morning. If you all can comment about your frustration on the link provided below and describe that you are having the same issue, we can get good visibility and hopefully solve the issue. If not, we can include media like Engadet, The Verge and others to get media coverage. Please comment your issue on the link below. Thanks a lot in advance.
01-16-2013 1:27 PM
I have posted on the facebook link above. I also urge everybody else to do the same. It's time that people are made aware of AT&T's LTE networks inability to receive calls.
01-16-2013 1:50 PM
Update on the options I tried to get my phone to work correclty
1) Factory Data Reset
2) Take out SIM and Battery and put them back
3) Change to a new SIM card
4) Trade in Phone at the warranty center for a new phone
5) Put phone in and out of airplane mode
6) Turn off Wifi
7) Have Att device support install JB from thier machines
8) Called ATT support and they "re broadcast" my phone number.
Well..all of the above FAILED. I will also update the facebook link with this issue.
01-16-2013 1:53 PM
Sorry I am posting so much, but, I am livid that AT&T is ignoring us. Every option they have offered me will cost me money (such as adding another line to my family plan and trying a different phone AT MY EXPENSE). "Too bad, you're past the 14 day warranty period." I want this to receive as much publicity as it can. I have submitted an email to consumerist, and hopefully, they will run with it.
01-16-2013 2:01 PM
Eventually, after a few device exchanges, I asked to speak with customer retention and told them I want to cancel my service because of the issues. After speaking with a supervisor they offered me any other $200 device for free if I re-signed a 2 year. Unfortunately the only other devices worth looking at are the LG Optimus and Note 2. The Note 2 suffers from the same issues as the GS3 and the reviews on the LG are not that good.
01-16-2013 6:59 PM
I actually ended up with that solution accidentally. How? I usually notice the issue happening when I am at home (which I am always connected to Wifi) or any place where my phone is hooked to a Wifi. I CAN sometimes receive calls even if the Wifi is ON but if the Wifi has been on for a while, I seem to have trouble receiving calls. But when I am NOT on Wifi, I do not seem to have any problem. This is just based on MY own observation and AT&T does not have any single clue why this is happening . They only said that Wifi shouldn't interfere with phone calls, and that's what I thought too.
01-16-2013 7:01 PM
I just got off the phone with another case manager. She said she has seen a few cases talking about the issues we are having. She is going to escalate the case and speak with their engineers and get back to me. Unfortuately with ATT's track record for software updates are really bad, so who knows how long it will take to fix
01-17-2013 7:34 AM
I didn't expect to have to post to this forum again this soon. It took me a lot of time to sort out the battery drain issue and now I am having the lost signal issue. I am experiencing the same issue whereby my phone wouldn't ring and the call goes straight to the voicemail. This appears to be happening daily for the last few weeks. I have been using the phone since July and didn't experience this issue even after upgrading to Jelly Bean. I now think it has something to do with AT&T network, possibly their recent changes to the network? This is frustrating and quite disappointing as the phone becomes useless when this happens. I hope AT&T addresses this issue soon. This again reminds us how important the service reliability is and AT&T continues to prove that there's room for improvement after all these years.
01-17-2013 11:22 AM
Apparently the HTC One X also has this problem ...here is the thread : http://forums.att.com/t5/Android-Discussion-and-Support/HTC-one-X-plus-stops-receiving-calls/td-p/33...
Looks like ATT's LTE may be the cause for dropped calls after all....
01-17-2013 11:31 AM
I've seen issues like this in the past with multiple carriers. I've noticed that no one (that I can remember) posted his/her location. Sometimes these issues are concentrated in one geographic area, so it may be helpful to post your location with your comment.
01-17-2013 5:51 PM - last edited on 02-05-2013 9:33 AM by jamileh
I got this issue fixed. You dont have to remove the battery or even restart your phone for that matter. This problem occurs mainly because of 4G LTE. I dont know if its the phone or the service. So, I have found an alternative.
What you need to do is add a new APN and run your device on 3G so that you can still get calls and browse until att or samsung fixes this issue. You can either use 4G toggle which you can download from google play to toggle between 3g and 4g. Or you can add as I have said above the new APN. Please go to Settings -> More settings -> Mobile Networks ->Access point names-> (+ new APN) . Give the Name of your choice but the APN should be defined as wap.cingular and finally save it. Change the existing apn to your newly created apn. Go to you home menu and you will see the 4G is used insted 4G LTE. You can even check your speed by using speed test.
Actually now I even have fewer dropped calls and I get the calls as soon as they call it.
Please watch the below url: http://www.youtube.com/watch?feature=player_embedded&v=TqXFd5aJcuY or read this link : http://forums.androidcentral.com/t-galaxy-s-iii/243505-jelly-bean-4-1-1-phone-calls-bug.html
We are researching this but I have marked jan_raghavan's suggestion as an Accepted Solution for the time being because it's worked for a couple people.
I have to note that this is NOT an AT&T solution and it will limit your capabilities on the device because you won't be on 4G but since it's helped a few of you, I want to make sure it's visible.>
01-17-2013 8:05 PM
Jan is correct. I was in a corporate store (st.louis) today and there was an engineer in the store. He said they are very aware of the issue with any 4.1+ device experiencing the call and data issues. Something about how a 4.1+ device sends more than 130 bit signal to their LTE tower which is causing major issues. He said that he has bumped his GS3 down to 3G and is no longer experiencing any more issues. Unfortunately we have to loose LTE until they fix the issue or deal with horrible service.
01-18-2013 12:09 PM
FYI, I tried "contactparag's" solution on the 15th, have not noticed any missed calls and today is the 18th. Now my phone says I'm on 4G not 4G LTE, when they get this issue fixed how do I get back on 4G LTE? Thanks I was desparate!