Tmobile, just picked it up yesterday and I was excited! I got some calls yesterday and everything was fine. Now today many of my calls are going straight to VM. I called tmobile support, they did their thing, not fixed. I did a factory reset on my phone, not fixed.
Is anyone else experiencing this issue? Do I have a defective phone?
edit:
it was the new sim that I was given when I bought the phone.
something about the cell tower not recognizing the new sim. it's been fixed now!
Related
Hi, can anyone help me please?
I'm losing my company voda phone (sim card) as I'm being made redundant, and swapped it out for an Orange payg sim last week. All seemed to be working fine. However, I tried to call my phone today, and it just goes straight to answerphone. I contacted Orange CS, and they sent me some sim updates. Rebooted, and Orange CS managed to place a call to my phone. Sorted. Or so I thought. Just tried again, and it's still going to answerphone. Have I messed my phone up somehow? I know my 2 year old daughter was palying with it at the weekend, and managed to call one of my friends for 2 mins!! Could she have changed something else?
Check call forwarding in the phone settings.
You can adjust how long it takes to divert to voicemail here. Perhaps this is your culprit?
Make sure that the top checkbox (forward all incoming phone calls) is unchecked also.
Thanks for the suggestion, but seems to have sorted itself out now
I have been swapping the sim cards around, and trying different phones. I guess one of the reboots must have done something? Anyway, all working again
Check This Out
All folks who have this issue may want to check out this thread.
The calls going straight to voicemail may be a symptom of NSI as defined in the thread linked above. As of right now, there is no cure except a soft reset or perhaps going back to a 6.0 ROM.
Hello
On Wednesday, I was sending and receiving multiple texts all day just fine.
Now starting Thursday morning, i sent out some texts to 15 different people, all said they received it and texted back.
My phone has not received a single text since wednesday. It can do everything else, send texts, phone calls, etc.
I'm on cognition 4 ROM, i've tried hard resetting it multiple times, called ATT and they said I should be getting them but I am not. I have full service. They also said i'm not the first person to call about this problem. I've also put my SIM in another phone and still no texts received.
Any ways to fix this?
Smitty50 said:
Hello
On Wednesday, I was sending and receiving multiple texts all day just fine.
Now starting Thursday morning, i sent out some texts to 15 different people, all said they received it and texted back.
My phone has not received a single text since wednesday. It can do everything else, send texts, phone calls, etc.
I'm on cognition 4 ROM, i've tried hard resetting it multiple times, called ATT and they said I should be getting them but I am not. I have full service. They also said i'm not the first person to call about this problem. I've also put my SIM in another phone and still no texts received.
Any ways to fix this?
Click to expand...
Click to collapse
If you put the similar in another phone and you are still not getting them then it is a network issue. Are you using a 3rd party text app?
zelendel said:
If you put the similar in another phone and you are still not getting them then it is a network issue. Are you using a 3rd party text app?
Click to expand...
Click to collapse
Nope. Stock texting.
That's what ATT is apparently telling me and it's pretty frustrating.
ATT needs to "re-activate" your phone.
I've had this problem 3 times. Sometimes it will take a few hours for all the old texts you missed to show up.
I had the same issue. Went to the ATT store told them I called customer service and that customer service said i needed a new SIM card. Got a new SIM card - problem solved. Then almost immediately all my texts started showing up.
vdubguy said:
I had the same issue. Went to the ATT store told them I called customer service and that customer service said i needed a new SIM card. Got a new SIM card - problem solved. Then almost immediately all my texts started showing up.
Click to expand...
Click to collapse
I agree. Sounds like a bad sim card, especially considering you didn't receive texts in the other phone you put your sim in.
First of all, I want to say that I found people with the same issue using Android everywhere and with a lot of different phones, so it's probably an Android bug rather then Moto X itself, but I wanted to leave my report.
I came from an S3, which suffered from the same problem when using Cyanogenmod. When using official Samsung ROM everything worked as it should. Now, I'm getting the same issue on my brand new Moto X.
When I try to call someone, sometimes it just doesn't call, after I press the dial button, it just hangs (without ringing) and finished the call with a "Cal ended" message. It happens randomly, and sometimes I can't call anybody for like 2/3 hours.
The simcard has been changed from the S3 (micro) to the Moto X (nano), so it's probably not it. Also, with the Samsung ROM it didn't happen.
I can still receive calls and messages, and the signal strength is fine most of the time. I just can't call.
Today I faced this problem and then I tried calling from my girlfriend smartphone (samsung ace IIx) at the same time, which is from the same carrier, calling to the same number, and it just worked fine. Mine still didn't work though.
Here is a thread on people on xda facing the same problem, but with a different phone: http://forum.xda-developers.com/showthread.php?t=2351227
Don't know what to do.
i've had the call not go through as you've described, but have never had a phone not let me place "any call" afterwards. i always chalked it up to poor performance (limited RAM, too many processes, etc). My DROID3 would do it and often times when it finally did make a call, there was zero sound and I would have to reboot the phone.
640k said:
i've had the call not go through as you've described, but have never had a phone not let me place "any call" afterwards. i always chalked it up to poor performance (limited RAM, too many processes, etc). My DROID3 would do it and often times when it finally did make a call, there was zero sound and I would have to reboot the phone.
Click to expand...
Click to collapse
Hmm, it doesn't seems like poor performance. I ended up every task and it still happened.
However, I noticed that when I check the "2G ONLY" option it comes back to work. Maybe it's something with the HSPA/HSPA+ connection.
it could be completely carrier dependent then. my experience has been with vzw.
Moto X "Call Ended"
I have experienced this same problem in Houston on the T-Mobile network after switching over to Android. My T-Mobile rep told me they have had towers vandalized for copper which has impacted service for them, I believe he said it was about 15 towers and 10K a pop to get things corrected. What gets me is I was on a Bold 9900 and while I had signal problems in the affected areas of town I didn't not experience the "call ended" issue. I can also call other T-Mobile phones from those same areas but not land lines so to me this seems like a possible network routing issue which I have seen before between specific carriers.
If the problem does continue I may have to switch carriers. T-Mobiles service was previously outstanding in Houston but recently had not been great after the 4G LTE upgrades. I support multiple hospitals and need service to work correctly and will work with the T-Mobile Engineers to see if I can make headway on that front. I noticed another MotoX user reporting he only had the issue when flying in to Houston for work and that everything worked for him outside of Houston. His solution was to operate in 2G mode which for me is really not an option. I have to handle a lot of tasks over the network while on calls.
Anyways I would appreciate it if others could post if they are experiencing these issues and give as many details as possible so we can try to isolate the root cause of this problem and if found to be a carrier issue we can escalate with them. Thanks
dicarli said:
First of all, I want to say that I found people with the same issue using Android everywhere and with a lot of different phones, so it's probably an Android bug rather then Moto X itself, but I wanted to leave my report.
I came from an S3, which suffered from the same problem when using Cyanogenmod. When using official Samsung ROM everything worked as it should. Now, I'm getting the same issue on my brand new Moto X.
When I try to call someone, sometimes it just doesn't call, after I press the dial button, it just hangs (without ringing) and finished the call with a "Cal ended" message. It happens randomly, and sometimes I can't call anybody for like 2/3 hours.
The simcard has been changed from the S3 (micro) to the Moto X (nano), so it's probably not it. Also, with the Samsung ROM it didn't happen.
I can still receive calls and messages, and the signal strength is fine most of the time. I just can't call.
Today I faced this problem and then I tried calling from my girlfriend smartphone (samsung ace IIx) at the same time, which is from the same carrier, calling to the same number, and it just worked fine. Mine still didn't work though.
Here is a thread on people on xda facing the same problem, but with a different phone: http://forum.xda-developers.com/showthread.php?t=2351227
Don't know what to do.
Click to expand...
Click to collapse
Call Ended Issue Resolved
Hi All,
I see this Call Ended Issue in many brands. So I assume the error is a combination of the Network along with the SimSlot.
I tried various combinations for my Moto-E mobile.
Before i post the solution i found, Let me provide a brief about the problem.
I use Vodafone network on sim1 slot and Uninor network on Sim2 slot. I started facing the call ended issue on my sim 1 vodafone network.
I inter changed the sim's and found the network working absolutely fine. This makes me to understand that the sim1 slot with the vodafone carrier has some network issue where that IMEI code has some problem.
i tried to place the vodafone sim again on the sim 1 slot and found the problem persists. So i came to that conclusion.
Hope this might help you and provide a instantaneous and temporary resolution.
Thanks,
Praveen.
Call Ended problem still going...
Hey,
I just rooted my Moto X (XT 1053), like 5 min ago, in the hope to fix this same problem. I`m no programer/developer and have nothing against rooting, I just don`t think I`m that kind of user. Anyway, about a week ago my phone started to drop my calls right after dialing. I restored factory settings, updated it and nothing worked. I took it for service and they offered to charge me 150 bucks to restore factory settings and update the software. So I was kinda forced to root and try to fix it this way. The problem is that I probably don`t understand half of what you guys say, so if there are any kind souls out there, please help me out.
To sum it up:
- No Sim Card error
- I get carrier services and can use mobile internet (3G because 4G is still too explensive here in Brazil)
- Directly drops my calls
- Won't receive calls
- Won't send or receive text messages via carrier (just over 3G or wifi)
I`ve tried another carrier's Sim Card, no go.
I`ve tried my Sim Card on another phone and it worked just dandy, so I really don`t think it`s carrier related.
I`m running Android 4.4.3, as the other updates weren`t available for my phone via Motorola. I thought maybe updating to a newer version of Android might do the trick. I just have no clue on how to do that on a rooted phone... or on a non rooted phone for that matter.
Can anyone give me any tips/pointers/etc... ?
Thanks!
I have the same issue with my moto x on Verizon. Have you been able to figure it out?
I've had an issue twice now where I can't make or answer voice calls. When I answer I get nothing but silence, and the other person says it keeps ringing, and when I call I get nothing but silence (no ring or anything on my end, but it does ring for the person I'm calling.). I updated to the OTA after getting it yesterday, and things seemed to be fixed, but today it is doing it again. I have great signal (both LTE and the older network), IMS registered, and not roaming. Has anyone else had this problem? It is extremely frustrating.
Edit: Texts work, mobile data works, everything except calls.
I've noticed the call quality on 1X has been pretty poor. Also, I've had call roaming pop up a couple of times where I've never had any problems in the past. I haven't experienced exactly what you describe tough. We need VoLTE, and we need it quick.
It's still going today. I'm going to take the phone back to Verizon. Completely unacceptable.
Update: Verizon swapped out two SIMs and still couldn't figure it out. Sending me a brand new one.
Sent from my XT1254
Got today's update BQJA AT&T Note 8. Update completed and my phone came back fine.
After an entire day, I realized that I'm not able to make or receive calls... I'm so frustrated.
Anyone else having this issue?
Please help.
It may not be the update. My family down south has been having problems all day on AT&T. Family and friends up here in the Ohio valley area have had same problems. I think AT&T is having large-scale network problems. Didn't they have some across California last week?
why wouldnt you just call ATT and ask them to fix it for you???
AT&T just released a press update an hour ago telling everyone to restart their phones to make calls now.
I didn't get an update but I was not able to make calls so I rebooted. But now I don't have VOLTE.
Issues with towers. I work for att and have had customers coming in all day with calling problems still not sure what exactly the problem was or is.
Thanks all... As that night progressed, I did find out that it was indeed AT&T network problems nationwide. I attempted several restarts. One finally took and my phone is acting normally now.
Thanks again.