I have a us spec snapdragon version and haven't really had connection issues till recently. Anytime I try and make a call it automatically says "call ended" and thus never connects. I tried Oreo ROMs, Pie ROMs and MIUI ROMs. All have the same "call ended" issue.
I tried the us 21s modem and bootloader. Same thing. Heck I even tried the 19s that I think was for India and that didn't work.
I slapped my sim into my old One Plus One and lo and behold I could call out.
Any ideas on what is going on and how to fix it?
*Edit* thanks to the user that told me to switch off volte. I don't have volte now but at least I can make calls now
Related
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?
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
I have the International Note 5 (SM-N920C) with the Carrier T-Mobile in the U.S, I have had this Device for Over a year now and it always worked flawless, ever since T-Mobile started implementing changes to there System my Calls go straight to voicemail when anyone try calling me, also, when i try making out going calls it takes close to a Minute before i even here the phone start ringing on my end, its weird cause this never happened, and it not my device either, i called T-Mobile and they couldn't help me, Hence, I went on Vacation to Myrtle Beach and toke my Note 5 with me to see if it worked out there (I live in Brooklyn NY) and yes, of Course it started working Flawless again, Im writing this Post in HOPES someone can help me, I have Tried Many Custom Roms and CSC zips to No Avail, Im hoping someone out there went through what Im going through and Found a FIX, thanks in advance, Bless to everyone.. One Love, All we Have is One Life.
I'm having the same issues you're having. I recently switched over to TMobile with a SM-N920C. It takes a while to dial out and some calls are going to voicemail without even ringing. I'm in Jersey City so maybe it's something they're trying out in more congested areas.
I haven't tried any custom ROMs or kernels but I was wondering if it had something to do with Voice over LTE not being supported by the phone out of the box. Have you tried any VoLTE capable ROMs/kernels?
Hey S.G, first off, i got a Kick out your User Name, on another Note, i tried Various Custom Roms and Custom Kernels that allow me to turn on and Off VOLTE, nothing Worked, Like i mentioned in my post, i went on Vaction to South Carolina and my device worked Flawless like it should be working now, I Called T-Mobile and they couldn't help me, all i could ask is for you to also call tmobile to let them now its an issue on there end with the international devices, Now if they get enough calls from different ppl they will have no choice but to fix the issue, Ill do the same... Thanks for reaching out though. This really sucks cause i love this device.
Hi. I have exactly the same issue in NYC... Did you ever find the solution for your Note5?
I have the international version of the note 8 and it periodically doesn't receive calls, or texts seem to come sometimes super late and I sometimes have to resend texts because it fails to send the first time. I've tried resetting it, factory reset, rooting and custom rom (2 different ones) and still the same issue. The calls don't show up in my missed calls but the voicemails do show up.
I have had all of the Notes from 1 up to this one, all rooted with custom roms but I can't seem to figure this out. The so not disturb is off, the caller isn't blocked, airplane mod is off, I have no idea! I'm running a T-Mobile sim and using the recommended APN and have also tried the others available. Still having the same issues, if someone can please point me in the right direction I would be so very grateful. Thanks in advance.
https://forum.xda-developers.com/galaxy-note-8/help/phone-doesnt-receive-calls-texts-t3763813
Does the same thing happen when you use the same SIM with other devices? If it does then there is an issue with the SIM. If it doesn't I would take your device to a Samsung Service Center and let them take a look at it.
Hey!
I am using Havoc OS since I've bought this phone. But it does not matter what OS I am using, problem is still there.
When I am using LTE, every incomming call is shown as Unknown Caller. I've tried different SIM cards, I went to my service provider, they don't know anything, and never seen issue like this. Once I switch back to HSDPA or even EDGE, I can see incomming calls fine.
I've tried clean flash. I went back to stock and nothing has changed. I flashed stock with MiFlash, still same issue.
I am running out of ideas. Please help me, any advice will be usefull!