Samsung Galaxy S3 Not Receiving Calls - Phone issue or Android issue?

I just gave in and finally got an iPhone 5 today. Everyone says I even sound clearer on the iPhone then I did on the S3. Right when I got the phone it was weird because everyone started calling me on it lol. I wonder how many calls I actually missed cause of the S3. It was just too frustrating. I also like the way the iPhone 5 feels in my hands. I still might consider getting another Galaxy phone later on down the road but for now, I'm stuck with the 5 for 2 years but, I Think it's worth it, I hope.

I upgraded from iphone 4s to galaxy s4 last month 05/07/2013, and I lives in Pullman WA where we have LTE network here. My GS4 missed phone calls 4 times after I got it and they are all random, there is no missed call in the log at all.

Just put my problem here and see if anyone has the same problem with GS4, maybe we should open a new theared for this problem for the GS4.

---

@MN-Android wrote:

---

@theskyisnotalwaysblue wrote:

Hi,

 

I am having this same issue on S3 with AT&T and I live in Tennessee. I do not even see the calls coming in and then after the calls come in they get put on block some how right after and then I have a hard time with calling them back. I can receive text messages fine and check my emails fine. I am stressed out about the fact I cannot receive calls. My doctor had to call the home phone due to the fact he could not reach me on my cell phone. I was relieved he had my home phone but that is not the only important call I've missed.

 

What should I do? My friend in Florida is having the same problem with her S3.

 

Thanks

---

As far as having a phone that can receive calls, you can do the work around outlined by M A S E in earlier pages of this thread. When I did this and dropped down to HSPA vs LTE, the phone never failed but that is hardly a suitable fix over AT&T addressing and fixing it. As far as what you an do with AT&T, I wish you good luck. They will have you look at and verify every setting on the phone, send you to your nearest AT&T store for a new sim card and then finally exchange your phone for a refurbished one. None of this will cure ths issue and you will have to start completely over with explaining the issue with each new call to AT&T. The front line techs know nothing of this ongoing LTE issue but deeper levels of tech support do but they too can offer no remedy. 

---

Good God did you sum it up perfectly in short paragraph. It’s quite a charade they want you to endure just to end up with the same problem. I have three of the S3’s and all had the same problem no matter where I was in the country. I had one of them back to Samsung three times because I didn’t want a refurbished S3 through at&t, but to no avail. I dropped down to HSPA as outlined by M A S E in earlier pages of this thread, and no more dropped calls. I eventually managed to have at&t agree to a $900 credit to my account for the trouble. I was just happy that after about 30 hours on the phone with them, someone from the deeper level of support finally admitted there was a problem. The front line support was insulting and infuriating to get through… all while listing to their chip cheery at&t commercials while waiting on hold.

I am late to this thread, having just upgraded to the Galaxy S3 this month. However, I have been reporting this exact issue for a long time, since my previous phone, a Motorola Atrix 2, had the same problem. I was always told (besides replacing the SIM card and powering off/on) that it was because my house was between two cell towers and it was fighting over which to connect to. AT&T even gave me a MicroCell to fix this, but I eventually disconnected it because it did not help.

I opened a ticket yesterday, and was told it would be resolved Friday (6/28). I assume that there is no resolution yet, from the postings in this thread.

I tried the trick to create another APN for wap.cingular, but this is only a short-term workaround as now my data speeds drop to almost "dial-up" levels. I have not tried the *#2263# workaround as it also will drop my speed to almost nothing.

I did try the *#197328640# trick to unlock the phone, but that generates an error and does not unlock.

I am about to call the number mentioned in a thread at forums.androidcentral.com (also mentioned in this thread, but later redacted, presumably by AT&T) to talk to the engineers there, but I don't have much hope.

I have a couple of questions...

1) Is there a new AT&T employee to monitor these forums (community manager?) since Jami quit May 1?

2) Does this occur if you root your phone and install Android 4.2.2? Previous postings claimed it did and did not fix the issue. Gizmodo just had an article saying S3 would be getting 4.2.2 Real Soon Now.

3) Does this occur with Galaxy S4?

If the S4 works fine, then I will attempt to get the "retention specialist" mentioned earlier to replace my S3's with S4's. The previous posting mentioned getting a $900 credit due to this issue. Since I have been reporting it a long time (check the support records for my number), I may be able to get them to do a deal for a pair of S4's.

In the meantime, I assume there is still no fix.

---

@LogicSmith wrote:

I am late to this thread, having just upgraded to the Galaxy S3 this month. However, I have been reporting this exact issue for a long time, since my previous phone, a Motorola Atrix 2, had the same problem. I was always told (besides replacing the SIM card and powering off/on) that it was because my house was between two cell towers and it was fighting over which to connect to. AT&T even gave me a MicroCell to fix this, but I eventually disconnected it because it did not help.

 

I opened a ticket yesterday, and was told it would be resolved Friday (6/28). I assume that there is no resolution yet, from the postings in this thread.

 

I tried the trick to create another APN for wap.cingular, but this is only a short-term workaround as now my data speeds drop to almost "dial-up" levels. I have not tried the *#2263# workaround as it also will drop my speed to almost nothing.

 

I did try the *#197328640# trick to unlock the phone, but that generates an error and does not unlock.

 

I am about to call the number mentioned in a thread at forums.androidcentral.com (also mentioned in this thread, but later redacted, presumably by AT&T) to talk to the engineers there, but I don't have much hope.

 

I have a couple of questions...

 

1) Is there a new AT&T employee to monitor these forums (community manager?) since Jami quit May 1?

2) Does this occur if you root your phone and install Android 4.2.2? Previous postings claimed it did and did not fix the issue. Gizmodo just had an article saying S3 would be getting 4.2.2 Real Soon Now.

3) Does this occur with Galaxy S4?

 

If the S4 works fine, then I will attempt to get the "retention specialist" mentioned earlier to replace my S3's with S4's. The previous posting mentioned getting a $900 credit due to this issue. Since I have been reporting it a long time (check the support records for my number), I may be able to get them to do a deal for a pair of S4's.

 

In the meantime, I assume there is still no fix.

---

Like you, the APN fix didn't work for me either, only the *#2263# worked for me but like you mention, you will not be on LTE. It will however allow you to not miss calls and sms messages. I demanded AT&T remedy this for me in a two hour call with them. Talk about torture! The final resolution was a new S4 and I have not had any problems with this phone. My wife also has a new S4 from AT&T with no issues. I also hear that 4.2.2 is coming for the S3 but can't guaranty if it cures this issue or noton this phone. The member (M A S E) who posted the work-around has told me that he went to a 4.2.2 rom and it completely cured the problem for him. 

So to sum up, your options appear to be to use the work around until July when 4.2.2 comes out for your S3 and see if the new OS cures the problem or deal with AT&T and get an S4 or HTC One, etc.  I know how you feel, either way it will be a work for you and I put it off for months living under the downgraded speeds until I decided to switch my S3 back to LTE hoping that AT&T might have fixed htis. When it yet again failed, I had had enough and made the long, very heated call to them. 

Best of luck to you!

Was going on previous info and another search shows that it has been delayed. Looks like this narrows the options even more. 

Forum chatter

Apparently 4.2.2 has been "leaked", but Cyanogen Mod has it now (dated 6/24, I think). I wonder if it's worth rooting and installing this version, or should I try to convince AT&T to give me free upgrades to S4?

The official word on many sites says July or August for the official release.

Guys, 

i am flat out telling you. 

ya'll just waisting your time. ATT will NEVER EVER fix this as this issue resolved in 4.2.2

they will not push new specific update for your current version nor they will ever agree to say they have an issue. 

this site is managed by a 3rd party company that have zero tech knowledge or any power at ATT to change anything. 

so either root your phone and get rid of that ATT bloatware to your ROM (which is step number one with ANY phone i get from ATT) and put 4.2.2 from xda-developers site. 

or go with Cyanogen (PS - CM 10.1 works flawlessly on this device). 

just check xda site. 

get rid of that awefull really immature of an attempt to customize an OS made by ATT. 

or just get the S4 (like me and the genterlman before). 

stop waisting your time openning tickets with AA, they clearly do not value our time. why should we value theirs...

just move on and do ur own thing. 

good luck.

The Wife says rooting the phone voids the warranty. True? Maybe getting them to upgrade us to S4 is best idea.