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?
Related
Guys,
When I got my P3600 some weeks ago I didn't experience any problems with problems with calls dropping. But ever since I've upgraded to WM6 I am experiencing this problem... the calls drop at random, sometimes I can talk for hours without any disconnect, and sometimes the call drops and I cannot even call the person back... And even after downgrading to the shipped rom, I still have this problem... That made me wonder if maybe I have had problem when I got the device but at that point I was just lucky not to have calls dropping.
Yesterday was the last time a call dropped on me. I couldn't call the person back, the phone didn't establish a new connection. When I finally got the person back on the phone (2 minutes later) he/she said that the whole time she thought I was driving through a tunnel and that I would reconnect because... I stayed connected at the other phone... After 2 minutes, she said, the connection was finally broken and that's when I was able to call again.
So sounds to me that windows mobile disconnects me and that the operators network still keeps my number connected.
Well, needless to say, I want to fix this issue. I have a 3G Vodafone NL subscription but I read that 3G could be the cause of my issue. so I've just disabled 3G. Now I'm just running on GPRS... Which isn't how I want it to stay. Any ideas, same experience/ pointers how to solve this?
Thnx. Arend
Reply from HTC
This is the reply I got from HTC:
Try to remove it off 3G go to settings / phone / band - then select GSM from the top drop down menu.
Should now reset.
If it comes up with an error, turn on flight mode then do the above again.
Click to expand...
Click to collapse
So based on this reply it seems that 3G might be causing my issue.
I replied to HTC:
I have followed your instructions but now I can only use gprs... but I have a 3G subscription with my provider. So even if this workaround works, it's not to my satisfaction.
Pls advice.
Click to expand...
Click to collapse
I'll post their reply.
Further, if someone has more info on the subject please let me know.
Same problem here...
No issues before upgrading to WM6. Sometimes the call drops out after a few minutes, sometimes a few seconds, and sometimes already after a few rings. The other day I had to make a call 5 or 6 times to finish the conversation - very annoying...
I'm running the first official Australian WM6 release for Dopod/HTC, i.e. the one that got pulled off the web for a while. Possibly going to the newer release of the ROM update solves the problem? Even though I think both versions run on the same radio ROM.
I've used the same rom as you to upgrade to WM6. But in my case, even when downgrading to the shipped rom, I still had calls dropping. And like you, sometimes after minutes, seconds etc.
Still having no drops since I have turned 3G off. But I just wanted to look something up on the internet... took minutes to get the info on my screen with GRPS, so it's not much like a solution.
This is the reply of HTC:
Dear sir,
Regarding your situation with the device , I would suggest you, to? resolve your issue with the network coverage ,to practice a hard reset on your mobile with the following step:
START -> Setting->System->CLEAR STORAGE and follow the procedure, if you have already done this manipulation , I would direct you? to this service and check the right number on this area with your network ush the green button to call->then go to menu-> option ->Services->select the on the following list ->Voice mail etc-> and then get setting -> and check that the number is right with your network provider.
Click to expand...
Click to collapse
Needless to say, but I'll say it anyway, I have performed hard resets... indeed, multiple
The second action they adviced, sounded a bit strange to me. But when I retrieved the settings I saw that there was no number filled in for voicemail. So I've entered 1233 (Vodafone NL voicemailnumber).
So maybe the last action has nothing to do with my issue, but who knows.
So now I am running again on 3G. I'll keep y'all posted.
Just checked it on my device and there is already an entry under voice mail. So I severly doubt that it has anything to do with the voice mail settings, too.
No, I guess you are right.
Further, since I am running 3G my signal I noticed my signal is weaker then running GPRS-only. My calls have not dropped since but I do get complaints that people sometimes cannot hear what I say because my line goes dead, and a moment later it's back again.
I've got another reply from HTC:
---
If a hard reset didn't solve the problem and the problem only occurs when switching to 3G, than this can be caused by the following;
1. Problem with the device.
2. Problem with the network, ???
I would suggest to test your SIM in another HTC device with 3G and see what happens. If it happens again than it is a? problem with the network. If it works with that 3G device than it could be a faulty device. The experience is that it is related to the 3G network himself. If it is a network issue, than you can ask them to deactivate the 3G/HSDPA.
We can't find this out for you in the UK, you need to see if you could determine the problem yourself.
---
Thus the support of HTC.
So now I have written an email to vodafone. I'll keep you posted.
Same problem !
Try to flash your device with ROM_Radio 1.41.00.11,
Friendly
Barichon said:
Same problem !
Try to flash your device with ROM_Radio 1.41.00.11,
Friendly
Click to expand...
Click to collapse
Ok... but I'm somewhat confused... are you experiencing the same problem with 1.41.00.11? Or did you solve the problem by flashing to 1.41.00.11?
2----> solve by reflashing with 1.41.00.11
Ok, I've upgraded to 1.41.00.11.
So far, I've experienced no calls dropping on me.
Nevertheless, I've also made a phonecall to Vodafone explaining the issue. They acknowlegde the issue... SAY WHAT?!! Yes... they acknowledge the issue and recommend turning the device to GRPS only. WHAT?!!.. Chill, they can at least try that, who knows, maybe I would have said yes.
So, I explained GPRS only is not an option since it is a tiny bit slower then what I am paying for.
They've put the call through to their 2nd line and keep me informed. So as soon as I hear something I will get back to you.
ps. What I found very great is that they did not cut it off with "Ow, you are using the HTC P3600... I'm sorry, we do not support that device." Vodafone NL, keep up this great level of support!
Ok, so far I've heard nothing from Vodafone. And so far I have had one call that dropped. So although that is a huge improvement, it still sucks.
So... now what? The way I see it:
1. I want to have fast internet on my PDA (3G), so only GPRS is not an option
2. There are problems with the 3G network which make calls drop every now and then
3. Vodafone isn't going to fix this in a short period of time.
So the question is: what is more import to me: 3G or a reliable phone connections?
The answer is: reliable phone connection.
So I will switch my network to GSM instead of auto and when
I really need fast internet I will switch to 3G.
Case closed... well, not really... but still, case closed.
Hi
I think is not the operator problem and could be the phone problem, I am using the D810 in Singapore with Starhub and have the same problem with drop calls once I use 3G network. If I switch to GSM only than is perfect no drop calls and calls quality improve also.
So sad having a 3.5G phone and can't use 3.5G service
Could be, but HTC and Vodafone confirmed me that it has to do with the 3G network. And I do not want to know the technical details about all that so I'll leave it at that.
I have brought two phones to the UK. Both of them are Samsung Captivates, one of which has Eclair, and the other has Froyo. I recently purchased a SIM card from the 3 (Three) Network and except for a small APN problem. Everything seemed to be working fine. Recently, I've been periodically unable to make calls from either of the phones. Text messaging and internet over the 3G network work fine, but when I try to call, it looks as though it connects, but I can't hear anyone and they can't hear me. If a friend calls me, I do see an incoming call on my phone, but when I pick up, we can't hear each other. I've noticed that when I reboot my phone after having the SIM card removed for a while, it connects for the first call made, and both people can hear each other, but after that first call, it goes back to not working. Has anyone here had a similar issue, or have any idea what could be causing this?
By the way, I was on the phone with 3 (Three) customer support, and they had me completely reset one of the phones, and the problem still happened. Also, I put in a SIM card that I knew was working, so it seems to me that it must be some weird compatibility issue with the Captivate, although I can't imagine why, because it's a phone almost exactly like the i9000 in Europe and the UK, and should be able to work fine with any network.
sorry if this has been answered but I have searched all over and cant find it.
So I took the spint OTA the other day and now every one in awhile i recieve Assisted dialing error / Invalid Mobile country code. I have turned off assisted dialing but I'm still getting this error. It takes me off 4g and says its on 3g but yet no connection seems to be there at all. anyone else have this problem?
david.herh said:
sorry if this has been answered but I have searched all over and cant find it.
So I took the spint OTA the other day and now every one in awhile i recieve Assisted dialing error / Invalid Mobile country code. I have turned off assisted dialing but I'm still getting this error. It takes me off 4g and says its on 3g but yet no connection seems to be there at all. anyone else have this problem?
Click to expand...
Click to collapse
Did you do a factory reset, I know you lose everything but in my past experience, factory reset after taking an ota is a must.
Sent on my Moto X
I've been intermittently getting this error for the past couple of days too. And yes, I did a factory reset after the KitKat OTA.
I am also getting this notification a few times a day. Both my "current country" and "reference country" are correctly set to USA, and it doesn't matter if I have assisted dialing turned on or off. Fortunately, it doesn't seem to affect the cell signal.
Just got my Sprint Moto X two days ago and did the KitKat update immediately on receiving.
Doing a search on it, it seems to have been infrequently reported going back several years, and always on Motorola devices. And sometimes has been reported as causing loss of the cell signal until you reboot.
fwald said:
I am also getting this notification a few times a day. Both my "current country" and "reference country" are correctly set to USA, and it doesn't matter if I have assisted dialing turned on or off. Fortunately, it doesn't seem to affect the cell signal.
Just got my Sprint Moto X two days ago and did the KitKat update immediately on receiving.
Doing a search on it, it seems to have been infrequently reported going back several years, and always on Motorola devices. And sometimes has been reported as causing loss of the cell signal until you reboot.
Click to expand...
Click to collapse
It's not a huge deal but kind of annoying. And it only started happening to me a few days ago.
clankfu said:
It's not a huge deal but kind of annoying. And it only started happening to me a few days ago.
Click to expand...
Click to collapse
Agreed. If it ever starts resulting in loss of cell signal, however, it will be a huge pain.
I have this happening as well. It seems to happen often when the phone registers to a new tower while I am driving. To make it go away I "change" my country to USA. I changed it last night while driving and it went away. I haven't had it back since. I don't know if this is a random issue with sprint's network or if it is problem with the phones. Perhaps we can try to figure this out?
I have my # connected to Google Voice.
My phone is a replacement phone from Motorola.
My phone would not self-activate, I had to call and get it manually programmed by Sprint support.
Do we have anything in common?
My phone would not self activate either but that's the only thing in common on those grounds.
dshiznit00 said:
I have this happening as well. It seems to happen often when the phone registers to a new tower while I am driving. To make it go away I "change" my country to USA. I changed it last night while driving and it went away. I haven't had it back since. I don't know if this is a random issue with sprint's network or if it is problem with the phones. Perhaps we can try to figure this out?
I have my # connected to Google Voice.
My phone is a replacement phone from Motorola.
My phone would not self-activate, I had to call and get it manually programmed by Sprint support.
Do we have anything in common?
Click to expand...
Click to collapse
Wasn't it already on USA?
I also have my number integrated with Google Voice via Sprint.
I seem to get this error whenever it switches from wifi to mobile data.
[
dshiznit00 said:
I have this happening as well. It seems to happen often when the phone registers to a new tower while I am driving. To make it go away I "change" my country to USA. I changed it last night while driving and it went away. I haven't had it back since. I don't know if this is a random issue with sprint's network or if it is problem with the phones. Perhaps we can try to figure this out?
I have my # connected to Google Voice.
My phone is a replacement phone from Motorola.
My phone would not self-activate, I had to call and get it manually programmed by Sprint support.
Do we have anything in common?
Click to expand...
Click to collapse
I'm integrated with Sprint/Google Voice, but was getting it right off the bat before I even set up GV.
Mine is a new phone.
My phone also would not self-activate, I went to the Sprint web site and entered the MEID and UCC but still had to call them.
However, I only experienced the problem 1-2 more times since my post. I only had the phone in my house, which I suppose doesn't eliminate tower switching but makes it less likely.
I've since unlocked the bootloader and rooted and haven't had it once after that.
It does seem to be a Sprint-only issue with the Moto X this time, but if you do a Google search it was a rare issue with other Moto phones.
Here is the gist. We have 2 G4's that right when they cross into Canada, all hell breaks loose!
End Button (dialer) Loses functionality. The only way to end a call is either the other person, or remove battery.
Phones cannot call each other but can call other phones (data does not work either, but texting does)
No incomming calls work at all, however it seems to be trying (not going straight to voicemail, but rather ring 20 times and then busy signal.
Sprint says everything should be good, and unlocked on their end. They even state that the sim cards have "registered" with rodgers. I am at a complete loss. Hours and hours with tech support, reset / factory wipe, etc... Even tried putting in a Rodgers SIM, and still a big fat ZERO. The troubling thing is that once the phones come back to the states, everything works fine. We have had them switch the plan to the canada plus, to the international plan and back, to no avail. Has anyone experienced this problem? Really frustrating to say the least! I could see one being a "bad" phone, but two??? No way. Coincidences like that just don't happen! Oh- yes, latest software update IS installed (the ls991zv5). Build LMY47D Android 5.1 Kernel 3.10.49
Thanks in advance!
Im having the same problem too
I try a hard reset and still nothing
Issue with me, and how to make Data works
This issue is random Sprint LG G4 LS991 to me. 50% phones work perfectly, 50% have issue.
If you want Data works. Download APN zip file, extract, replace, change permission like original file (0644). Go to Dialer, type ##3282#, APN Settings, touch Menu, Reset default. Turn On Mobile Data.
chlywily said:
Here is the gist. We have 2 G4's that right when they cross into Canada, all hell breaks loose!
End Button (dialer) Loses functionality. The only way to end a call is either the other person, or remove battery.
Phones cannot call each other but can call other phones (data does not work either, but texting does)
No incomming calls work at all, however it seems to be trying (not going straight to voicemail, but rather ring 20 times and then busy signal.
Sprint says everything should be good, and unlocked on their end. They even state that the sim cards have "registered" with rodgers. I am at a complete loss. Hours and hours with tech support, reset / factory wipe, etc... Even tried putting in a Rodgers SIM, and still a big fat ZERO. The troubling thing is that once the phones come back to the states, everything works fine. We have had them switch the plan to the canada plus, to the international plan and back, to no avail. Has anyone experienced this problem? Really frustrating to say the least! I could see one being a "bad" phone, but two??? No way. Coincidences like that just don't happen! Oh- yes, latest software update IS installed (the ls991zv5). Build LMY47D Android 5.1 Kernel 3.10.49
Thanks in advance!
Click to expand...
Click to collapse
problem solved
Ok everyone figured I'd come here to where the experts live. Haven't been here in awhile.
Recently my S8, wifes S8, and our sons S8+ all have the same issues.
The first issue is texts get stuck "sending". This happens with WiFi on or off, with wifi calling on or off, and I even tried changing off LTE to just 4G/3G/2G and even 2g in settings to see if that would help. I'm on the latest firmware from TMO ending in QEF, well we all are.
The other one is apps like FB and others aren't alerting but they will show the number of alerts even after they've been checked. I've reinstalled these apps and the problem persists, and then I can reboot my phone or wifes phone and all the alerts start working again for awhile and then die eventually.
The texting issue though persists and is random when it will hang and when it doesn't.
According to TMO rep at the store it's a bug in the firmware with bixpy that was pushed out, but I frankly don't buy it and figured I'd hit the guru's up here and see if you guys have any thoughts.
Thanks in advance guys and gals....
I too have had the random "texts get stuck sending" issue. I haven't had it in a while though (now that I've said that I'm sure I will).
I unfortunately don't have any suggestions.
I ended up using googles version of messages due to this. Only on stock text app do i have any problems anymore. I also noticed on the stock app that my phone would say "sending" when the other side would actually get it, but it was at random.
You don't have a cellspot repeater or router do you? Last time I had it, my device was hung and needed reboots. Just a thought.
Thanks for the feedback, yes I have a cell spot, but I also have the issue other areas of town too with no real specific place thatbit always happens.
I'm going to reverse back from the qef firmware and see if that resolves things. This has been so annoying, and it just started about two weeks ago.
Thanks again everyone.
I have had the same issue with sending texts too. I have been using the stock messenger app. I may just switch to textra.
Same issue here. A temporary fix, try turning on airplane mode and off. Works for me a times
Also happening to me on the XAA firmware (have unlocked NA variant) with the stock messaging and Google messages.
So I'll ask the question begging to be asked (at least by me): How does one disable this messaging app and use "stock messaging" app?
Thanks in advance....
rabilancia said:
So I'll ask the question begging to be asked (at least by me): How does one disable this messaging app and use "stock messaging" app?
Thanks in advance....
Click to expand...
Click to collapse
Just get a app disabler for Samsung from play store like BK Disabler.
If I were you, just download Android Messages. It's simple and fast.
However, I do not recommend disabling stock messaging, unless you don't like getting EAS (Amber/Weather/Presidential Alert)
Having the exact same issues and it's driving me crazy because I really like this phone. I don't get notifications for any of my apps but when I open them I can see the new messages. A reset seems to fix the problem but it only lasts about an hour before it starts doing the same thing. I've tried using different messaging apps but the same thing. And the fact that I don't get notifications for other apps it can't just be a text messaging issue right?
Happened to me for almost 2 months but haven't had an issue in about a week. Called t mobile, they created a ticket and said they'll be working on it. Few days after speaking to them, problem went away.
This has been happening intermitantly for me as well. It's been bad the past three days. I'm currently in coversations with T-mo's engineering team and they seem to be coming up with a bunch of dead ends. It's not a location based thing as it's been happening over a 20 mile radius in the past few days for me. Other people on T-mo network that I'm freinds with or I work with aren't having any problems. I'm wondering if just a fresh SIM card could solve it?
I have data connection although it seems a little sluggish compared to when I originally got the phone. Similar to OP I've tried all the "G's" modes, with wifi calling on, with it off, with cellular network preffered with wifi calling on and off. With Textra, with stock messaging app. I've factory reset to no avail. I've pulled and re-inserted the SIM card to no avail. This is incredibly frustrating for a flagship phone on a network where I've had no previous issues.
UPDATE: T-Mobile sent me a new SIM card and that seems to have cleared up the issues. Not sure if it just hapened to coincide with T-Mo tower fixes or anything else like that in my area but I'm back to normal operation. Anybody else experiencing this I recommend you push customer service to send you a new sim.
my husband and i are having a strange issue where we can message pictures and video clips to other people that don't have the s8, or aren't on tmobile and they'll send and receive just fine, but when we try to send to each other, the first attempt to send fails, but the second attempt goes through?
balthuszar said:
my husband and i are having a strange issue where we can message pictures and video clips to other people that don't have the s8, or aren't on tmobile and they'll send and receive just fine, but when we try to send to each other, the first attempt to send fails, but the second attempt goes through?
Click to expand...
Click to collapse
i had same problem one of you is not using stock message app, if you check it ull find pictures all there i think its new messages plus thing