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?
For an unknown reason, my previous moto X and the 2nd moto X share one annoying problem: I have to tap phone dialer twice to open the phone dialer pad. That is, tapping the phone dialer icon once is not enough. This is very annoying. Has anyone encountered the same problem and found the solution? Thank you in advance!
Same thing happening to me. Is the stock dialer replaceable with a different one?
Just thinking out loud here... What happens if you remove your sim card abd try to open the phone dialer?
Also, have you used the moto migrate to transfernyour data?
Moto XT1097 for the win
I've had my Verizon Moto X 2014 for about 3 weeks now and for some reason sometimes a person would try to call or text me and it doesn't go through. or even if I send out a text or a call and that doesn't go through. I went to Verizon the other day and they said *73 should stop the fowarding. The guy said it could possibly was trying to go another phone number?I didn't have any of these problems with my 13 Moto X. Any suggestions on how to fix this?
ry_t said:
I've had my Verizon Moto X 2014 for about 3 weeks now and for some reason sometimes a person would try to call or text me and it doesn't go through. or even if I send out a text or a call and that doesn't go through. I went to Verizon the other day and they said *73 should stop the fowarding. The guy said it could possibly was trying to go another phone number?I didn't have any of these problems with my 13 Moto X. Any suggestions on how to fix this?
Click to expand...
Click to collapse
my dad had this problem, get a new sim card from verizon
I had an issue where I could not receive texts on my 2013 X. I was on the phone with both Verizon and Moto. We tried for a whole weekend to get it working. In the end I was able to fix it...factory reset. Pain the in the a$$ but at least it fixed the issue. Still not sure what caused it.
Recently I've noticed that my Moto Voice isn't working like it should.
For example, it'll only allow me to ask it one question, then any following questions and it'll ignore them with a sound as if it has rejected my voice.
I've already reset my phone to factory settings before anyone asks but it's not made a difference.
Even if I ask if what the weathers like, it'll say half of the first word then go silent but still display the right info on the screen.
Anyone else getting this?
I'm not rooted and am running on Marshmallow if it helps.
I've tried retraining my voice and cleared the cache of the Moto app but no luck.
Sent from my XT1092 using Tapatalk
How did you get Moto Voice to work, I can't get it to work with Moto App
Hi,
I have a Moto G2 phone. With Docomo as my cellular I cannot answer incoming calls by swiping. If I change the simcard to any other vendor(say Airtel or Vodafone) I can answer calls normally.
Does anyone faced a similar issue in answering incoming calls with swipe, please suggest to resolve the issue. I have searched the internet and tried the options but in vain.
Thanks in advance.
no such problem mayb try a factory reset or put your sim in other slot and try again
Sent from my Moto G 2014 using Tapatalk
techlover93 said:
no such problem mayb try a factory reset or put your sim in other slot and try again
Sent from my Moto G 2014 using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply. I have checked that already and it works but not always. However, I will look for any settings in the Moto Assist as well and post my update here.
Cheers.