Hey everyone.
My LG G2X is running Cyogenmod 7.2.
Just last week my phone apparently started to not be able to receive phone calls. I called T-mobile and told them about the issue, however they tried calling me and it went through without an issue.
I am lost for words, i've had people from AT&T and Verizon try to call me and no calls go through.
Any ideas?
Kind Regards,
Jordan
What baseband are you on? If you're on a baseband that is not supported by the ROM then you may need to flash one of these zip files to make your phone capable of making calls. See this thread: http://forum.xda-developers.com/showthread.php?t=1776843
chowdan said:
Hey everyone.
My LG G2X is running Cyogenmod 7.2.
Just last week my phone apparently started to not be able to receive phone calls. I called T-mobile and told them about the issue, however they tried calling me and it went through without an issue.
I am lost for words, i've had people from AT&T and Verizon try to call me and no calls go through.
Any ideas?
Kind Regards,
Jordan
Click to expand...
Click to collapse
If test calls come through, and calls from other t-mobile phones come through, then it is clearly a t-mobile problem, NOT a phone problem. There is nothing ON your phone that rejects only calls from specific carriers.
You will need to call them back with specific examples of people (phone # and carrier) who cannot call you. Perferably you will also have some examples (landlines, other carriers) who CAN call you.
You also need to make sure to have more than one example, otherwise it could be on the other person's side.
Armed with that information you can prove a pattern and that it is not your phone.
On the other hand, if it is random as far as whether a call comes through or not, then it could be either your phone or t-mobile. A pattern is what you're looking for.
Source of information: I was once a T-Mobile Tier 2 PDA Tech.
Related
Hi I am using the ATT HTC VIVID
I bought this phone last Nov 11, and I stated noticing my phone was not receiving any calls if I stay at home(jersey city). If anyone calls to my number it will not connect at the same time it will not sent to voicemail also. It will say "call couldn't be completed".
After 2 months fight with ATT, they tried
1. they did a factory reset on my phone - it didn't help
2. changed the sim card - it didn't help
3. finally they replaced a another HTC vivid
even that didn't help
finally they said there was issue in near to my home and they fixed it.
now i a started receiving calls but now the issue i am having is, if I call to my number it will not connect first time it will go to voicemail, and second time if i try then it will ring. (First time also my phone is idle) This is happening randomly and ATT is not helping on this situation. As per them I am not able to replicate when they were testing on my phone.
Because of this issue I am missing calls which is making me really frustrated. After three week of research I found this is happening in not only near to my home its happening at my work place (NYC) and if I go around also its happening.
Can someone please give some advice to fix the issue that would be really great
Sounds like an issue that IMEI is conflicting :'(
Low end cheap bro.....
First of all, thanks for the response
But I am not getting the answer clearly
Can you please explain more and what should I do
Do I need to contact ATT or something
Long story short, my VM Victory was soft-bricked and came back to life after (mostly accidentally) flashing a Sprint rom on to it. It has worked splendidly for a month and a half.
The VM phone thinks it is on the Sprint network. All my data and phone usage is tracked minute-for-minute on my VM account, so I know that the phone just thinks it's on Sprint, but the phone is clearly on VM.
The only issue I have with this (since it works in all other matters) is that I can't get MMS. My BF, also on VM, wasn't getting MMS either, so I figured it was a VM problem.
He was able to get his MMS fixed by realigning MSID/MDN by using the ##VIRGIN# command in the phone dialer.
When I try ##VIRGIN# it says the command is invalid, and I'm guessing it's because my phone thinks it's Sprint, and Sprint doesn't know that command.
So my question is, what part of the flash makes it think it's Sprint, and is there anything I can do, or should I just get used to Sprint and no MMS?
Note: I have been unsuccessful flashing the one and only VM Victory Rom on the phone, so that doesn't seem to be an option.
I am having a similar problem. I tried to update my Virgin Mobile Galaxy S2 from ICS to Jelly Bean via Kies, and now my device thinks it is a Sprint phone. Can't receive MMS and my receiving/sending of texts and calls is spotty. I chatted with someone from Samsung and they were unable to help me, said to take the phone in to Best Buy and have a Samsung representative look at it. I'll be doing that today.
Have you made any progress with it?
Well, I went in to Best Buy and talked with the Samsung rep and he attempted to fix my phone to no avail. He did make it so that it would run correctly so I could receive texts and calls. But it seems the software is permanent. I went ahead and signed up for Sprint's free student plan and got the S4 Mini since I needed a new phone anyway and am going to attempt to sell my Galaxy 2. But yeah. Best of luck to you.
Not sure if this is a carrier thing or the device? I switched from AT&T to Verizon when this device came out. When on a call and a call comes in I place original call on hold and answer incoming call. If I then hang up on that call it hangs up on both people. Is there no call waiting?
Never had to tell someone they need to hang up so I can switch back to the other person on hold. Seems like either a bad carrier issue or bug? Never had CDMA carrier before so hopefully not an issue I'm stuck with?
deeznuts said:
Not sure if this is a carrier thing or the device? I switched from AT&T to Verizon when this device came out. When on a call and a call comes in I place original call on hold and answer incoming call. If I then hang up on that call it hangs up on both people. Is there no call waiting?
Never had to tell someone they need to hang up so I can switch back to the other person on hold. Seems like either a bad carrier issue or bug? Never had CDMA carrier before so hopefully not an issue I'm stuck with?
Click to expand...
Click to collapse
This is a CDMA bug since it happens with Sprint as well. I was like you, I switched over from AT&T about 4 years ago. It absolutely drove me crazy for about a year until I just finally gave up and accepted it. I'm hoping that things will chnage when VoLTE becomes the standard:fingers-crossed::fingers-crossed::fingers-crossed:
UPDATE:
http://forums.androidcentral.com/sp...nd-just-one-call-while-another-call-hold.html
There is a solution on wikipedia
mademan420 said:
This is a CDMA bug since it happens with Sprint as well. I was like you, I switched over from AT&T about 4 years ago. It absolutely drove me crazy for about a year until I just finally gave up and accepted it. I'm hoping that things will chnage when VoLTE becomes the standard:fingers-crossed::fingers-crossed::fingers-crossed:
UPDATE:
http://forums.androidcentral.com/sp...nd-just-one-call-while-another-call-hold.html
Click to expand...
Click to collapse
This just worked for me
https://en.wikipedia.org/wiki/Call_forwarding#Keypad_codes
easilybigger2 said:
This just worked for me
https://en.wikipedia.org/wiki/Call_forwarding#Keypad_codes
Click to expand...
Click to collapse
What worked? Must have not seen the solution reading the link.
Keypad Code
deeznuts said:
What worked? Must have not seen the solution reading the link.
Click to expand...
Click to collapse
If you have Sprint dial *38 and/or *720 to restore your call waiting. And for other mobile companies ##21#. But you can read through and find the correct deactivation. The problem happens because somehow call forwarding was active. I think it happened for me when I used my sprint number as my Google Voice number.
Before I get on hold with AT&T tech support, I wanted to ask the experts if anyone else has had this issue.
I bought my new A32 about a month ago. It was branded for T-Mobile, but was unlocked already.
In the past, I just put my AT&T sim card in the new phone and it was ready to go (I don't mind the T-Mobile start screen).
It worked fine for a couple of weeks, then T-Mobile sent out an update and it stopped receiving texts. AT&T put in a new sim card, and that fixed the text problem, but now it won't make or accept phone calls. Calls go right to voice mail. When I try to dial a number, it just disconnects immediately.
Anyone have any idea of what could be wrong?
Thanks.
You bought an unlocked phone for a different carrier, unlocked by a third party, and updated it.
the phone can have some issues if...
1. the software version running is different (each carriers may have different versions they approved and pushed to update for their customers, hence not supporting some versions)
2. If you have unlocked and the carrier is some minor name carrier and not the main ATT then the phone may not be supported by them.
You should backup all your data to either Google or Samsung account or whatever option is shown... then ask to have the device flashed with the latest market software version from ATT. Hope this helps.
TheImpalaKid said:
Before I get on hold with AT&T tech support, I wanted to ask the experts if anyone else has had this issue.
I bought my new A32 about a month ago. It was branded for T-Mobile, but was unlocked already.
In the past, I just put my AT&T sim card in the new phone and it was ready to go (I don't mind the T-Mobile start screen).
It worked fine for a couple of weeks, then T-Mobile sent out an update and it stopped receiving texts. AT&T put in a new sim card, and that fixed the text problem, but now it won't make or accept phone calls. Calls go right to voice mail. When I try to dial a number, it just disconnects immediately.
Anyone have any idea of what could be wrong?
Thanks.
Click to expand...
Click to collapse
I have the same problem. Acquired a NIB T-mobile Samsung A32 that is confirmed unlocked but doesn't work on PuretalkUSA when it came to calling or receiving calls. Texting and websurfing works but call get immediately terminated and calls made to the phone go automatically to VM. I spent three hours on the phone with Puretalk tech to make sure the settings were correct. The tech had me attempt to update the carrier configuration version to no avail. It refused to update and remained at version 0.0.0. I then stuck an T-mobile sim in the phone and noticed that the carrier config version change to some series that I currently do not recall. However, I still could not make or receive calls. I then purchased a prepaid ATT sim and stuck it in the phone. The carrier config version changed back to 0.0.0 but I was able to make and receive calls. I'm putting one more call in to puretalk to make sure I've tried everything before giving up on the phone.
I recommend that you check this guy's video on youtube. He seems to be on to something:
Very frustrated with Unlocked (USA) S22 Ultra. Somewhat frequently but intermittently my phone is unable to make a call. When I try to make the call it just ends immediately - and of note this is in full cellular service (4g or 5G) and also even if WiFi is on and the call is being attempted on WiFi calling. So it's not just a cellular network problem. The problem is reminiscent of back in the day when I would flash a custom ROM and the call features or CSC was messed up.
I believe a similar issue is that often I will get a text from my daughter (who the heck knows how many business calls I missed) - she says that she has tried to call all day and the call just ends immediately and won't ring through to me.
Looks like there are many complaints out there on the internet -- I am looking for a fix hopefully form someone int his community. I wonder if flashing ATT firmware on my unlocked phone would help??
Another problem is that sometimes (definitely intermittently) I am unable to activate the Speakerphone. Pushing the button highlights the Speakerphone indicator BUT the sound is still through the headset - not the speakerphone. Thoughts?
are you on June update? The latest june update seems to have fixed some of the GSM issue so maybe that would resolve your problem.
jcrompton said:
Very frustrated with Unlocked (USA) S22 Ultra. Somewhat frequently but intermittently my phone is unable to make a call. When I try to make the call it just ends immediately - and of note this is in full cellular service (4g or 5G) and also even if WiFi is on and the call is being attempted on WiFi calling. So it's not just a cellular network problem. The problem is reminiscent of back in the day when I would flash a custom ROM and the call features or CSC was messed up.
I believe a similar issue is that often I will get a text from my daughter (who the heck knows how many business calls I missed) - she says that she has tried to call all day and the call just ends immediately and won't ring through to me.
Looks like there are many complaints out there on the internet -- I am looking for a fix hopefully form someone int his community. I wonder if flashing ATT firmware on my unlocked phone would help??
Another problem is that sometimes (definitely intermittently) I am unable to activate the Speakerphone. Pushing the button highlights the Speakerphone indicator BUT the sound is still through the headset - not the speakerphone. Thoughts?
Click to expand...
Click to collapse
Never ever had this problem (ATT - locked, 12/512 SD). if nothing else you may want to try to take to ATT for re-provisioning (I assume ATT may be who you are trying to use)
jcrompton said:
Very frustrated with Unlocked (USA) S22 Ultra. Somewhat frequently but intermittently my phone is unable to make a call. When I try to make the call it just ends immediately - and of note this is in full cellular service (4g or 5G) and also even if WiFi is on and the call is being attempted on WiFi calling. So it's not just a cellular network problem. The problem is reminiscent of back in the day when I would flash a custom ROM and the call features or CSC was messed up.
I believe a similar issue is that often I will get a text from my daughter (who the heck knows how many business calls I missed) - she says that she has tried to call all day and the call just ends immediately and won't ring through to me.
Looks like there are many complaints out there on the internet -- I am looking for a fix hopefully form someone int his community. I wonder if flashing ATT firmware on my unlocked phone would help??
Another problem is that sometimes (definitely intermittently) I am unable to activate the Speakerphone. Pushing the button highlights the Speakerphone indicator BUT the sound is still through the headset - not the speakerphone. Thoughts?
Click to expand...
Click to collapse
I had simmilar problems with exynos variant. After last june updates i think that cellular problems is gone.
But i am not certain this phone (wait for next updates) and now i use stable fold 2.
jcrompton said:
Very frustrated with Unlocked (USA) S22 Ultra. Somewhat frequently but intermittently my phone is unable to make a call. When I try to make the call it just ends immediately - and of note this is in full cellular service (4g or 5G) and also even if WiFi is on and the call is being attempted on WiFi calling. So it's not just a cellular network problem. The problem is reminiscent of back in the day when I would flash a custom ROM and the call features or CSC was messed up.
I believe a similar issue is that often I will get a text from my daughter (who the heck knows how many business calls I missed) - she says that she has tried to call all day and the call just ends immediately and won't ring through to me.
Looks like there are many complaints out there on the internet -- I am looking for a fix hopefully form someone int his community. I wonder if flashing ATT firmware on my unlocked phone would help??
Another problem is that sometimes (definitely intermittently) I am unable to activate the Speakerphone. Pushing the button highlights the Speakerphone indicator BUT the sound is still through the headset - not the speakerphone. Thoughts?
Click to expand...
Click to collapse
I got the U.S. Unlocked 512/12 Snap Dragon also. No problems on prepaid plan on TMobile. Maybe it time to ditch that Crappy AT&T sucketh Network.
Paul_Deemer said:
I got the U.S. Unlocked 512/12 Snap Dragon also. No problems on prepaid plan on TMobile. Maybe it time to ditch that Crappy AT&T sucketh Network.
Click to expand...
Click to collapse
Point well taken - but for my area TMobile just can't compare to ATT with reception -..... and that brings up another point , maybe time to move from WV, lol .... oh yeah actually not funny but serious
jcrompton said:
Point well taken - but for my area TMobile just can't compare to ATT with reception -..... and that brings up another point , maybe time to move from WV, lol .... oh yeah actually not funny but serious
Click to expand...
Click to collapse
West Virginia explains a lot! I am in South Carolina now but grew up in Pittsburgh so I drive thru West Virginia alot on 79 and not surprised about cell reception.
I've had this happen a few times with an Unlocked version on ATT. I'll try to make a call and it will just immediately end. A reboot fixes it, but if someone was trying to call me I would have no idea.
Have you tried clearing the dialers cache and data?
What about a third party app like googles dialer?
I had the same issue on my s21 ultra and went thru various fixed ( reprovision, changed sim, manufacture reset ..etc). I bought unlocked S22 ultra direct from Samsung and same issue. I have my work # on using physical sim and personal # esim. "when I try to make the call it just ends immediately - and of note this is in full cellular service (4g or 5G).." same issue around 10 times in the last 6 months. It happened on both physical sim and esim. The person who called either number went to voicemail and texting was fine. When I tried to call used either number and it will end right away. when it happened I would reboot and wipe cache partition. I haven't received June update yet and hopefully, that fixes it. I am also unable to send MMS on secondary # but SMS is fine.