Just this morning I noticed that I couldn't make outgoing calls and got a recorded message instructing me to make sure I am dialing the right number or something like that. Also, incoming calls were going straight to rapid beeps, in other words incoming was failing too.
I went in to Sprint and they noticed that my network setting was set to Global instead of LTE/CDMA, changing it got calling working again. They suspected an update overnight may have caused it as another user with an LG G3 came in earlier today.
I am running 5.0.1 build LRX21Y, LS990ZV8
PRL version is 55023
I don't think any of these indicate anything new. But just be aware, if your phone has suddenly stopped making/receiving calls, go into settings, More, Mobile networks, Network mode and verify you see LTE/CDMA.
Related
I've had the Galaxy S2 for about 2 months now without any problems.
As of last Friday, I can't receive incoming calls. People who try to call me hear one beep and then they get my voicemail.
Outgoing calls work just fine, as does SMS (incoming and outgoing).
I've put my T-Mobile SIM in another phone and then it is able to receive a call. Another SIM in my phone -> same problem: no incoming calls.
So I figured it must be the phone.
Customer support has started an investigation but that can take up to 1 week, so I thought let's ask XDA.
Can it be a simple setting that I've accidentally changed? Pretty often when I take my phone from my pocket, the screen is unlocked so that could be a cause.
If anyone has a clue or an identical situation, please let me know.
Zjoske said:
I've had the Galaxy S2 for about 2 months now without any problems.
As of last Friday, I can't receive incoming calls. People who try to call me hear one beep and then they get my voicemail.
Outgoing calls work just fine, as does SMS (incoming and outgoing).
I've put my T-Mobile SIM in another phone and then it is able to receive a call. Another SIM in my phone -> same problem: no incoming calls.
So I figured it must be the phone.
Customer support has started an investigation but that can take up to 1 week, so I thought let's ask XDA.
Can it be a simple setting that I've accidentally changed? Pretty often when I take my phone from my pocket, the screen is unlocked so that could be a cause.
If anyone has a clue or an identical situation, please let me know.
Click to expand...
Click to collapse
Does your phone ring when a call comes in and also does it go straight through to your voicemail?
daleski75 said:
Does your phone ring when a call comes in and also does it go straight through to your voicemail?
Click to expand...
Click to collapse
Straight to voicemail. But I've figured it out after 3 days
There's an option to automatically block all incoming calls in the settings. Must have accidentally been activated when the phone was in my pocket.
daleski75 said:
Does your phone ring when a call comes in and also does it go straight through to your voicemail?
Click to expand...
Click to collapse
In my case, the phone does not ring when I get a call at all. I have searched hi and low and I cant find a solution. I have rebooted, i have reflashed, I have changed my ringtone and nothing seems to work, please help!!
Hello my girlfriends SGS 2 has almost the same problem it cannot receive calls sometimes even though she can call everyone. The problem seems to fix by itself sometimes and it appears random.
I read that there was a problem with the samsung galaxy s when using 2G/EDGE connection with data activated and the problem was that the user could not receive calls randomly.
Can you confirm that you are using 2G/EDGE connection and Data activated? I am also trying to find the cause of this problem...
Hope my research helps good luck and waiting for your reply. (http://www.samsunggalaxysforum.com/...eive-incoming-calls-and-sms-while-using-edge/)
Later EDIT ---
She also has a vodafone provider but i have the same provider and never had this issue. Also no call filtering is done.
Make sure Call Forwarding is Disabled under Settings- Call- Call forwarding. And also try to delete the Voicemail number if you had set any.
Regards.
it's nothing Call Forwarding is Disabled related it is because of EDGE connection you can't have a sync or internet connection and while "dialing" data receive calls if you want to call anyone the network prioritizes and let's you dial whoever you want but it is not the same thing for incoming calls
^ Went over my head !
had the same problem in a bad 3g/data coverage area. solution was simply to turn data off and the calls started to come through.
turned data back on and now working ok.
After using QPST for my Dad's Inc4g it has 2 odd cellular problems.
#1
It can make outgoing calls for a few minutes.
But then it says that the “phone number is not active or invalid” (like it’s not activated).
Then the only call it can make is to 611 (data and wifi off), but it gives me his correct balance and minutes used (so it's still connected to his account).
Rebooting does not allow it to make outgoing calls either.
It's as if it's partially dropped off the verizon network somehow because turning the radio on and off again also doesn't work (airplane mode on/off).
And when another phone calls him it goes straight to his voicemail.
BUT….if another verizon phone calls he CAN receive that incoming call no problem.
*Then once he answers that incoming call, he can magically make an outgoing call again!
So can anyone tell me what I might need to change, to stop it from loosing the ability to make outgoing calls?
It’s brand new (NOT rooted or anything else).
The Preferred network is set to CDMA only.
Only changes have been through QPST, and switched to NV-Only mode so he doesn't have to use the sim card.
Also after QPST the roaming triangle popped up, but I have the 58012 PRL (isn’t this the latest for this phone)?
#2
If he starts to dial a number, but then immediately hangs up (accidental dial), his next call gets the "system busy" network error.
Then attempting to make a call after that gives the same error as above (requiring a verizon phone to call to get him back on the network).
Could someone try do this and see if they can repeat this error?
So to anyone who has used QPST with this phone, or flashed it to another carrier, do you have any change suggestions for either of these problems? Maybe changing something in EPST?
Thanks for your help.
My call forwarding on my AT&T Phone and AT&T Gear S won't connect. Anyone know of any threads or remedies?
Fixed My Own Problem
Ok I fixed my own problem and now it works better than before. I got on the chat with AT&T and they set up the call forwarding on their end. The Gear S still says there is no call forwarding connection though, so I disabled the option. Since it is enabled through AT&T, however, on a remote connection I can receive calls from both my phone number and my Gear S number. All the while call forwarding is disabled on the Gear S. I can receive texts through both numbers as well. The only downside is, to disable the call forwarding I would have to contact AT&T again. But I don't really know why I would ever want to disable that. I'm just going to leave my phone in a constant remote connection and get all the benefits of a regular bluetooth connection plus the ability to receive calls and texts on my Gear S number.
Customization
Ok wait. To customize my watch, such as adding new clocks and wallpapers, I would have to be on bluetooth. But that's no biggie i'll just reconnect.
Nevermind
This method does not work. Calls to my original number do not show up on my phone. Just my watch. I missed a call today because I had my watch turned off. Even though my phone was turned on, I didn't see the call. It went straight to my watch which wasn't on. AT&T said there is no way I could get the same call to appear on both my watch and my phone. So I'm still out of luck on getting the call forwarding option thru the Gear S working.
So phone is not working because of 3g gone on AT &T.
All incoming calls go directly to voicemail. Outgoing calls take two clicks to enable.
I am roaming in US from Canada. My provider Rogers told me to switch network to T-Mobile. That works but the problem is network selection has one choice Automatic. When you turn off and go to networks then chose T-Mobile it works but the phone shortly after turns back on automatic and AT&T then comes back.
Anyone have a solution to this?
I have a similar problem. All incoming calls go straight to voicemail. Outgoing calls and data service is fine.
I am using ATnT and Redpocket in USA.
Spoke with technical people at redpocket and they gave me new APNs. With one APN I started getting incoming calls but no data. They also suggested that my phone is not compatible as they are shutting down 3g service, but it doesn't make sense as I can still make outgoing calls plus with a different APN I can get incoming calls too.
I don't understand the reasons why this phone will not work. Maybe it uses volte to make outgoing calls. When I first dial a number it just closes but when dialed a second time it connected fine.
Back in Canada and no problem here. When roaming in the US it worked fine on T-Mobile but the phone kept defaulting back to AT&T which is Rogers Canada primary network affiliate for roaming in US.
Phone works fine on T-Mobile but that will end end of this year when they drop 3G.
Am trying to get an answer from Huawei support but so far nothing.
Will post any info I get from them.
Since the last OTA update I am facing issues while calling on WiFi.
While my phone is already on WiFi if I recieve a call, intermittently the voice breaks alot, after manually switching to Mobile network it works alright.
But Today I faced a weird issue, I received a call on mobile network when I was outside, as soon as I entered home and switched to WiFi, I got a message on my screen that the call has dropped and voice stopped, when I dialled back the call got connected automatically and I could hear my friend still talking like it never disconnected and at the same time I could also hear 2nd voice that the number you have called is busy. I tried to disconnect and call again but it was the same, to get out of this loop I had to switch back to Mobile network and disconnect.
This is the first time I faced such issue.