Database Develop

"Call ended" right after dialing

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?

Having problems reciving calls.

I have a problem with incoming calls, sometimes when try to call me it say's my phone is turned off, when it's not (I can call out without any problems)
Signal is fine and i can call out but people have problems calling me.
I don't get it.

sencricer said:
I have a problem with incoming calls, sometimes when try to call me it say's my phone is turned off, when it's not (I can call out without any problems)
Signal is fine and i can call out but people have problems calling me.
I don't get it.
Click to expand...
Click to collapse
It may not related to the hardware nor software of your phone. I've been facing this problem since I was on my old Sony Ericsson K770i. People can't reach as if my phone was turned off. However it happens occasionally. Yes, until today, same things happen but only occasionally. The only thing I can blame is my service provider.
But odds do happen. It might have something to do with your device. Does it happen everywhere you go?

Major problems with voice calls.

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

VoLTE/WiFi Calling Issues?

I picked up the Note 4 last Thursday. This is my first phone with WiFi Calling and VoLTE and so far the experience has been less than ideal. I've found that I get more dropped calls and the person on the other end can often not hear me when we first connect (and I need to call them back) when using WiFi calling or VoLTE.
Is it common to have more frequent call issues with these two features enabled, or could there be an issue with the handset?

I called TMo support last night for similar issues. I would try to clear the cache and data from the phone app. That's what they suggested for me and it's been working much better for me!
Sent from my Note 4 using the XDA app. Damn this thing's sweet!

Trust me, clearing the cache and data has nothing to do with it. It's a network issue. I've been having similar issues sporadically with WiFi calling ever since they switch to a different format of WiFi calling a few years back. Also couple that with the upgrades they're doing, at times service may be affected.

princeasi said:
Trust me, clearing the cache and data has nothing to do with it. It's a network issue. I've been having similar issues sporadically with WiFi calling ever since they switch to a different format of WiFi calling a few years back. Also couple that with the upgrades they're doing, at times service may be affected.
Click to expand...
Click to collapse
Yeah I didn't think it would. However, when my calls drop, I get kicked immediately back to the home screen. There was not a FC error or even a call drop tone (which I've NEVER heard on T-Mobile after a call drops). When I had a Note 3 with Verizon, my dialer would say 'No Signal' and it would at least tell me that the call was dropped. I'm not getting that here. After 2 weeks, I can't say I'm particularly impressed with the QoS of T-Mobile as I have several dropped calls daily -- sometimes 4 or 5 per day. It's getting rather old, honestly. If it wasn't for the dev phones, I would have ended up back at Verizon. I just had to start somewhere with the cache and data clear....

Well that's not quite what's happening to me. My calls either drop just like a normal dropped call (sound and all) or stay connected and just have audio issues.
Anyway, I was playing around with it a bit more and it seems to only occur on HD calls. My wife and my dad both have Nexus 5's, and I see the issues frequently with them. But VoLTE calls to non-T-Mobile customers seem to be fine.

Anyone else note 4 take 5 to 10 seconds to connect the call? Happened with my note 3 as well.

nano303 said:
Anyone else note 4 take 5 to 10 seconds to connect the call? Happened with my note 3 as well.
Click to expand...
Click to collapse
Not up to 10, but usually 3-5 seconds. This was true of my Nexus 5 as well though. It tends to be longer when it is not a VoLTE call, I imagine because it needs to drop from LTE to HSPA to connect.

[Q] HELP - Phone hangs up immediately after answering call

Ok, I've got a problem that just started happening the last week or two. When certain people call me, I can answer. However my phone always hangs up on them 1 second after the call. The behavior is the same, based on the number calling me.
For instance, if my wife calls me from her cell phone (Sprint iPhone 5S), it will always hang up immediately after answering.
If my wife calls me from our house phone, it always works like normal.
This so far as I can tell, only affects inbound calls. I have no issues calling out.
Running latest OTA. I've updated PRL and profile, and it made no difference. I've never rooted the phone or messed with S-on/off. Pure stock. I have rebooted the phone into safe mode, and the same behavior is present.

Interestingly enough, I'm also on Sprint, I have a Nexus 6 and my wife a Note 4, and we've had the same issue over the past week or two. She can call me and immediately after answering the call will end. This has happened with her calling from her cell phone and her office phone, both of which are attached to her contact. I can call out with no problem, and I've tested calling my phone from different numbers and had no problem. No clue whats going on.

Are one (or both) of you using Sprint's Google Voice integration?

shawndoc said:
Are one (or both) of you using Sprint's Google Voice integration?
Click to expand...
Click to collapse
I am having the same issues when my mom (S4) whose on the same contract as me, calls me (S6 edge) it always hang up immediately after I pick it up. I have no issues calling her though. I am using Sprint's Google voice integration but I do not believe my mom is.

It is the Google Voice integration that is causing the disconnects.
See here:
https://productforums.google.com/forum/?utm_medium=email&utm_source=first_post_notification#!topicsearchin/voice/sprint$20integration|sort:relevance/voice/NxkMd3YpzSw

I'm having the same problem with a Metro PCS phone. I've seen it elsewhere on line - it's some Android issue.