Database Develop

[Q] Vivid Issue Receiving the Calls

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

"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?

Help, I can't receive any calls but no problems to make them.

Hello, everyone.
I need help with an issue I'm facing. My phone is not receiving any calls whatsoever and I don't know why. I can make calls without any problems, the issue is that I can't receive them.
I don't know when this started happening since I don't receive many calls, I don't know if it's a result of rooting the phone, because it's rooted, or what else can it be. I don't remember if the phone received calls before or immediately after being rooted.
I've tried flashing different modems but I haven't been successful. Also, I have gone through the settings and disabled everything that could be causing the calls to be blocked. I have also called T-Mobile and they disconnected and reconnected my phone to the network and I have gone to one store to have the sim card replaced and that didn't help either. I have wiped the cache and the Dalvik cache and nothing. The only option left that I know is to factory reset the phone wich I'm trying to avoid because I have a ton of apps and my home screens are already setup and folders created and I don't want to do all this setup again.
Here is the weird part. Under just this specific scenario I can make my phone receive calls.
Make a call to any phone
Hangup a couple of seconds after the other phone starts ringing.
IMMEDIATELY BEFORE the call is terminated (lost) dial from the other phone (the one that was called in step 1). This should be within one second and no more after the call is lost.
If I follow this procedure then the call goes through and my note 4 receives it, but the call shall be made immediately after I hang up, otherwise it doesn't go through.
Does anybody have an idea of what could be happening?
Thanks!!

try this, go to settings all the down to calls and click on call rejection which says auto rejection turn that to off, ive had the Same problem and thats what help me out

Texts stuck "sending" and other issues

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

I'm having trouble getting calls and texts

I hope someone can help me with this issue.
I have a Moto X4 XT1900-1 which I have flashed the latest Lineage OS 16 on which is running on the Mint Mobile (T-Mobile MVNO).
Simply put the phone seems to sleep right through texts and calls. It doesn't consistently wake up and ring or give me texts in a timely fashion.
I've tested it many ways including putting the phone on a table next to me and sending texts to it and it doesn't seem to wake up. In case you're wondering it does not seem to be a network issue because another phone with the same SIM card on the same table 5 minutes later works properly.
One of the more peculiar things is when texts do finally trigger a notification they will be dated as "8 minutes ago", for instance.
The same issue appears to be happening with incoming calls when I test them. It's difficult to tell how often I miss calls because many people just hang up if they get voicemail.
One more thing that I doubt has anything to do with the problem, but under mobile network, in settings, it has "preferred network type" and it is set to "global". Is this the correct setting for me to use?
Could it be just a setting I need to change? Any help would be most appreciated.