01-30-2013 11:29 PM
01-31-2013 8:48 AM
Got my GS3 in early December and upgraded to JB 4.1 shortly after. Started having the same issue described by everyone here immediately. Last week had my SIM changed and that has not helped. The phone and text issues are both happening with me. Incoming calls may not even hit voicemail, I have been told that it sometimes sounds like a busy signal which is not good when one is expecting potentially important phone calls. I went to a newly opened Device Support Center here in Columbus, OH today and they told me immediately that there is an issue with ALL phones running 4G/LTE on the ATT network that run JB 4.1.
She told me that there is a patch being worked on and apparently they have also found that JB 4.2 works with 4G/LTE just fine. She could not tell me when there is an expected fix.
My question to Jamileh (apparently the ATT Community Manager) is, if ATT knows that JB 4.2 would fix this issue, why has that not been rolled out to us yet? I do not anger easily but if I am waiting on someone to contact me about a job interview or if a family member is in trouble for some reason I do not want to have to wonder whether or not my phone is going to work as I have paid for it (and am paying monthly) to. If JB 4.2 works please roll that out.
I'm sorry you're having an issue with receiving calls on your phone. Unfortunately, I can't speculate on the release times of updates to Android or any other operating system.
01-31-2013 10:31 AM
01-31-2013 12:20 PM - edited 01-31-2013 12:20 PM
I don't think this is stricly an Android or 4.1 issue. We have an iPhone 5 in our house and it had these issues too. Also, I'm running a custom 4.2 CyanogenMod Nightly on my S3 and I still had these issues. If anything, it would be the modem version, not strictly the android version. And like I said, we have an iPhone 5 that does the same thing. The solution for us was getting AT&T to give us a MicroCell which keeps the phone in 3G anyway. I don't mind this since I have WiFi in my house and I work from home. For people who are having this issue at their work place they'll have to keep the 3G only APN until AT&T fixes this problem which I don't think they can with the current infostructure of LTE.
02-01-2013 1:11 PM
I have had this issue for well over a month. Been through too many steps to list, new sim card, two phones and many calls to AT&T, all failed. Yesterday after yet another failure, I called AT&T and spoke to a guy that got my hopes up. He said he knew exactly what the issue was and can fix it today. I don't know what all the terms he threw at me meant but he said my account was wrong. Said my routing numbers and "LRN" were mismatched. Also said I was on the wrong network and he moved me to cingular wireless. Another statement he made was that my "SOA updated with LRN to proper SPID". I hung up thinking I have finally got a fix only to have the phone fail again today!
A few minutes ago, I used the work-around mentioned in this thread and followed the video to create a new APN and use 4G vs LTE. I sure hope this at least allows me to receive phone calls. I have elderly, ill parents and I need my phone AT&T!
02-01-2013 3:14 PM
This is directed to the Community Manger Jamileh. Is ATT aware that there is a problem with calls not getting through? Are the engineers at ATT working on a solution? Are all support people at ATT now aware of this problem? Thank you in advance of your reply.
02-01-2013 3:57 PM
I was able to finally speak to a tier 3 technical support rep who acknowledged to me that att was aware of this problem and was working on it. First rep on the phone who understood was I was saying although it sounded like they were in the first stages of calling people who are reporting it to collect information. Said that it had to do with a circuit switch fallback failure on the lte network . . just as a few assumed on this forum. No idea on an timeframe for a fix. The only temporary solution they had was creating a wap.cingular apn to disable lte. Said it was nationwide and it seemed to be getting worse in the past few weeks and would personally call me back in a week to follow up... Hopefully this brings some hope to some of you...
02-02-2013 6:38 AM
02-04-2013 10:36 AM
My husband and I upgraded (or should I say downgraded lol) to the Samsung Galaxy S3 from the iPhone 4 in November 2012. Since the first day we got these phonewere have had issues with:
not receiving calls, either goes to voicemail or busysignal,
trying to make calls and it says call ended,
not receiving text messages and voicemails for hours
horrible signal. And battery life
I have been fighting with att since I stupidly let the 14 day window pass and we had already gotten rid of our iphones. They kept saying wait for the JB update it will fix everything. That was a joke!! They actually made me feel stupid like I was doing something wrong with the phone and couldn't get it to work properly!! They haven't even given me the curtosey of swapping my phones out, they go thru the tech support steps and just cuz the phone takes a couple calls they say its fixed and they pat themselves on the back. Meanwhile we are still left with a piece of crap phone and myself like others use my phone for my business. Not to mention if something happens and my kids need to get ahold of me and they can't that is a big issue. Att should give the customers the option to upgrade to another phone if we can't wait til the so called fix. One person from case management actually told me to buy some go phones from Walmart until the issue was fixed!!! I'm so tired of these phones and the lack of consideration from att I am ready to just cancel and move on!!
02-04-2013 8:33 PM
talked to at least 3 techs, no one knows whats going (chated with online tech support even linked this thread), all i got is useless advice saying i need to change the sim card, restart my phone, ect ect ect... and the issue is getting worse, half of my calls are getting through, i get texts in internvals, cant use the phone for work when it doesnt work hafl the time, i even missed a family emergency due to this issue.
02-04-2013 8:42 PM
02-05-2013 6:07 AM
02-05-2013 9:06 AM
I fully agree, please remove the "solved" tag, no where near resolved and no answers.I had to put my phone back on LTE vs 4G because the phone went to constant SOS status all the time!
02-05-2013 9:32 AM - edited 02-05-2013 9:36 AM
I understand and agree that this is not a true solution to the issue but since it contains steps that several people found helpful, it will remain an Accepted Solution for visibility's sake. Marking that post as an Accepted Solution does not mean that we are no longer working with Samsung on this issue.
If you'll take a look at my post earlier in the thread, I stated that this is NOT an AT&T solution but since it has worked for some people, I wanted to make it visible. I will update jan_raghavan's post with an edit that more clearly convey's the message so we do not continue to have confusion.
When there is more information available, I will update the thread and Accepted Solution accordingly.
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.