Hi
Dont know if anyone can assist but getting no where with T-mobile.
I am getting complaints that callers are getting no ringing tone when they try to connect just silence for c 10 seconds and then voicemail even though I have full strength bars showing on the hand set. I have alled T-M numerous times and they suggest I remove battery and sim card and replace and soft reset. This appears to temporarily fix the problem for a very short period and then the fault reappears. This is happening numerous times a day. I am not able to replace this hand set just yet but if anyone can suggest a remedy until can, it would be appreciated. I am missing so many important calls it is driving me to distraction. Mobile internet connection is working fine and calls out pose no problem.
Because I am showing full bars I have no idea that people can't get through until I get a delayed voicemail or check my emails and then remove battery etc.
I was on contract with T-mobile but this elapsed and the financial melt down has resulted in me moving over to a PAYG sim until things improve, so no upgrade available to me just yet.
Any help appreciated.
Any suggestions/fixes to the above that I could try, would be appreciated.
Robert1960 said:
Any suggestions/fixes to the above that I could try, would be appreciated.
Click to expand...
Click to collapse
If you aren't using a custom rom I would suggest a hard reset.
Hi I am using the ATT HTC VIVID from Nov 2011.
I bought this phone last Nov 11, and I stated noticing my phone was not receiving any calls if I stay at home(jersey city). If anyone calls to my number it will not connect at the same time it will not sent to voicemail also. It will say "call couldn't be completed".
After 2 months fight with ATT, they tried
1. they did a factory reset on my phone - it didn't help
2. changed the sim card - it didn't help
3. finally they replaced a another HTC vivid
even that didn't help
finally they said there was issue in near to my home and they fixed it.
now i a started receiving calls but now the new issue is, if I call to my number it will not connect first time it will go to voicemail, and second time if i try then it will ring. (First time also my phone is idle) This is happening randomly and ATT is not helping on this situation. As per them I am not able to replicate when they were testing on my phone.
Because of this issue I am missing calls which is making me really frustrated. After three week of research I found this is happening in not only near to my home its happening at my work place (NYC) and if I go around also its happening.
Can someone please give some advice to fix the issue that would be really great
Is there anyone else in or around your home with AT&T service? If so, do they experience the same problem as you? Can you receive calls everywhere else besides home and work? Do text messages get through? How about internet service? MMS?
Thanks for your response
The issue is not around my place
The issue is, if any one calls first time it will go to voice mail, if they call again it will connect to my phone. This behavior is happening randomly.
It is happening in my work place(NYC) and also if i go some where in new jersey also. I can't tell when its happening and how. In a day it may happen one or two time. I can't check constantly on a day when and where.
Sometime i feel I am not getting call, if i try from land line it may work or it may go to voice mail, after the second try then it will be fine for that day.
this issue look little weird. but because of that I am missing calls.
forgot to mention, that time my internet will work fine, how I am sure is one time i was browsing and trying to call my phone from land line it didn't connect. as usual second time if i try it did connected
Also the signal bar in my home and my work place its full
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?
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
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.