I'm on Verizon, and I have a Nexus 6 I bought through Verizon. My service was constantly dropping out, and sometimes just showed as no SIM in the last few days. But today, I found I was unable to recieve data at one point, even though I had a few bars of service. Then, I was unable to make calls. I also can't hang up after starting a call, I just get stuck in Hanging up. I don't know if I can receive calls at the moment, but is anyone having this issue? Better yet, has anyone had and solved this issue?
I was on AOSiP with Hellz Kernel, and thoght that my ROM may be the issue. I've since reflashed ROMs and kernels with loads of full wipes, all to no avail.
This might be the reason,
http://forum.xda-developers.com/nexus-6/help/data-voice-icon-t3102504
your not alone
This just started happening to me a few hours ago on Verizon as well. It happened out of no where and I haven't found any solutions after searching for a few hours.
Related
My first full day using the phone. Hadnt had an issue until this evening. For some reason i can not make a call. Im in an area that only gets edge, but it shows i have three bars. When i try to make a call it never rings or says connected, it simply ended after about 7 seconds or so. I can however browse the internet or watch my slingbox on the phone so it seems my connection is good. I tried a hard reset, but issue remains. If i try to make a call it will go through maybe once out of every 20 attempts.
I saw a few similar threads, but nothing like this. Anyone have any thoughts?
apparently there is a huge outage in the NYC metro area with cingular. So, thankfully its not the phone. way to go cingular!
im having a similar problem on fido in Vancouver, tho i dont think its as bad as yours. intermittent phone use at best.
I am having the same problem as well. It just says dialing but no tone. I remove the battery and it works again. But a day later and then it starts to act up again.
I was advised to update my sim card since its 3 years old now.
I am with Fido in Montreal Quebec Canada.
I have the Bell i9000M unlocked and used with Rogers SIM. Nothing else has been done to the phone besides installing apps (got the sd corruption on my first i9000m after using Odin and didn't want to go through that again).
Haven't had any problems for over two months but in the past week, I have dropped calls and could no longer make calls again until I restarted the phone. I have dropped calls before (there's always a couple of areas on my drive home where I drop calls using any phone) and have always recovered. But just this past week, I can no longer make or receive calls after a dropped call.
Sometimes the status bar shows the blue circle with a slash, but that changes to white bars. But even with bars I can't make or receive calls. When I check *#0011# it doesn't show that I'm attached to a network.
I can go to an area with strong signal and leave the phone for hours but still cannot make calls. The only solution for me is to restart the phone.
Anybody have this problem and know how to fix it? I've been searching for days but haven't seen a solution.
Thanks,
yvrRome
Sent from my GT-I9000M using XDA App
I had the exact same problem on my first 2 I9000M's. The only thing I ever found was to replace them. It was annoying as hell and made the phone impossible to use sending or receiving calls. the second one was JH2 with the 3BR fix. Texting was perfect as was the internet (3g).
I searched and searched as well. But I was talking with a bell guy about it and he said it may have to do with an IMEI issue they have a master ticket open 3449667. I know you are on rogers now, but hope that helps in some way.
Thanks, it is very frustrating and dangerous since I'm usually driving when this happens. Unfortunately my 60 days are up and I can't get a replacement. There must be a way to fix it since it was working before. Maybe a SIM issue? I'll keep searching and hoping and if nothing, then I'll do a reset before sending for repair.
Sent from my GT-I9000M using XDA App
Just to update, I got a new SIM card and I don't have the problem anymore.
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?
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.
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