Database Develop

[Q] Can Anyone Reliably Make and Receive Calls?

I recently switched from an iPhone 5 to the One Dev Edition. After having some signal issues, I went to AT&T, got a microSIM, they switched me an Android data plan, etc. But I'm still having an issue where I can't reliably send and receive calls, especially from my desk at work. I can dial the number and hit Call but that's it. No ringing, nothing. Just dead air, then the "call" ends. If the call does go through, I can hear the other person but they can't hear me. Same thing when receiving a call. I'll hear them but they can't hear me. Sometimes my phone won't ring and it just rolls to voice mail. I can see the signal switching from LTE to H, etc, and I have practically full bar strength. I just don't understand why the calls aren't going through.
Is this an issue with the phone itself? Something with AT&T? Is there a newer radio firmware I can try flashing? I didn't have any issues with the iPhone 5, and I even had my coworker put his iPhone into field test mode so we could compare the numeric signal and they're about even, though the iPhone usually does have a slightly better db signal. I really like the One but not being able to send or receive calls while at my desk is a deal breaker.
Thanks!

From the sounds of it, you are running the stock firmware still? Any root or other possible modifications? If you answered Yes then no to those questions, I would head back to the AT&T store and have them try it out, if anything they should be able to take your SIM card and put it into another Android device and see what happens.
What about text/data, do those work?
You said mainly at your desk you notice this issue, so does that mean it happens at other places as well, same symptoms (full bars, allows to send call then nothing?) You may just be the lucky contestant with a defunct unit, HTC should be able to help you out.
I would suggest first going to AT&T store, try out their suggestions, then if anything give HTC a call/email to see if they can be of any help. At this point I would stay away from flashing custom radios as they may void your warranty then you will really be up $hit creek.

Sounds like att.
I had this problem with tmobile once. The signal wasn't strong enough and it wouldn't call.
Some please are spotty.

Something is wrong with your phone. That should be obvious. Of course the vast majority of people who got this phone can reliably make and receive calls or it would be the biggest mobile phone bust in history.
Sorry to be blunt but you already know it's not the signal so it has to be a defect in the phone.

Thanks for the suggestions. This is the stock Dev Edition ROM. I haven't made any changes other other than just installing apps.
I haven't made a lot of calls but I don't seem to have an issue any where else.
No issues with LTE. Data has been fine.
I wasn't sure if AT&T would assist since this is the Dev Edition but that's worth a shot to have them run some tests on it. Otherwise I'll try to get a replacement (or refund) from HTC.
Thanks!
Sent from my HTC One using xda premium

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

[Q] Silence when answering phone call

I have VoLTE and Wi-Fi Calling turned off. Sometimes when I answer an incoming call quickly (actually that doesn't matter), I just get silence and I can't hear the caller and they can't hear me. I have to hang up and try again; Anyone else encounter this?
Update: I think I narrowed it down. Apparently the first call I receive after rebooting my phone always fails (unless I've made an outgoing call first). Subsequent calls work fine until my phone is powered down or rebooted, then the 1st incoming call fails again. I can reproduce this 100% of the time.

I've had this happen a couple times, funny thing is I've had it happen on my S4 and S5 as well.. Im starting to think its Tmo's network.

It might be a glitch with T-Mobile's network, but I haven't encountered it on previous devices. For example, I just switched from the Nexus 5 and never had a problem with voice calls.

I've had this happen a few times also with my S6. Never happened before, and I've been with T-Mobile for over 2 years.

This only happens for me occasionally if one of the callers is on Wifi calling, but it's happened with every phone (not just the S6) so it's definitely a network issue

I found this related to the S4, http://thedroidguy.com/2013/06/gala...ting-incoming-calls-66029#jMqaFVvIYCDRQHse.97. I've disabled the mute function in motions and gestures. We'll see if that works.

ledvedder said:
I've had this happen a few times also with my S6. Never happened before, and I've been with T-Mobile for over 2 years.
Click to expand...
Click to collapse
Been with Tmo for 5 years now and I have had this happen on previous devices.. could be the area I am... lol, I also notice a delay when making a call out which I believe is the network

Never had this problem on S4, but since getting the S6 this problem has been bugging me. Very frustrating.

[Q] HELP - Phone hangs up immediately after answering call

Ok, I've got a problem that just started happening the last week or two. When certain people call me, I can answer. However my phone always hangs up on them 1 second after the call. The behavior is the same, based on the number calling me.
For instance, if my wife calls me from her cell phone (Sprint iPhone 5S), it will always hang up immediately after answering.
If my wife calls me from our house phone, it always works like normal.
This so far as I can tell, only affects inbound calls. I have no issues calling out.
Running latest OTA. I've updated PRL and profile, and it made no difference. I've never rooted the phone or messed with S-on/off. Pure stock. I have rebooted the phone into safe mode, and the same behavior is present.

Interestingly enough, I'm also on Sprint, I have a Nexus 6 and my wife a Note 4, and we've had the same issue over the past week or two. She can call me and immediately after answering the call will end. This has happened with her calling from her cell phone and her office phone, both of which are attached to her contact. I can call out with no problem, and I've tested calling my phone from different numbers and had no problem. No clue whats going on.

Are one (or both) of you using Sprint's Google Voice integration?

shawndoc said:
Are one (or both) of you using Sprint's Google Voice integration?
Click to expand...
Click to collapse
I am having the same issues when my mom (S4) whose on the same contract as me, calls me (S6 edge) it always hang up immediately after I pick it up. I have no issues calling her though. I am using Sprint's Google voice integration but I do not believe my mom is.

It is the Google Voice integration that is causing the disconnects.
See here:
https://productforums.google.com/forum/?utm_medium=email&utm_source=first_post_notification#!topicsearchin/voice/sprint$20integration|sort:relevance/voice/NxkMd3YpzSw

I'm having the same problem with a Metro PCS phone. I've seen it elsewhere on line - it's some Android issue.

[Q] Dropped Calls

In the last few days I've had at least one dropped call per day on my S6. It doesn't make any difference if my recipient is on a cellphone or landline nor does it matter if I'm in the car on bluetooth or using the handset elsewhere. I did some searches and found others having the same problem, not so much with AT&T (mine) as opposed to Verizon and T-Mobile. Some say a factory reset cured the problem, but I hate to do it unless I have to. Just curious how others on AT&T are faring. My previous S4 never dropped any calls nor did my HTC M7 so I'm thinking it's not a network issue, but something in the phone itself.

I've never had a dropped call in the month I've had the device. I had my chubby cheek hang up on my mom once last week, but that's as close as it gets. My area gets pretty good coverage for att and tmobile though. I've yet to drop a call since joining at&t

My Black Galaxy S6 Edge 64gb module was dropping calls like crazy, and was still within my exchange period so I switched it out. Haven't had any dropped calls since.

Call and connection quality have been stellar for me. Only dropped calls I've had are when going through known dead spots.

Looks like the factory reset fixed it for me so all is good now.

rmc69 said:
Looks like the factory reset fixed it for me so all is good now.
Click to expand...
Click to collapse
Have you had any dropped calls since your last post here? I'm having dropped calls often. I don't think a factory reset will help me because I wiped all data before flashing the rom I'm running. I may try a factory reset from within the settings menu if you haven't had any dropped calls since the 15th.

I've only had a couple dropped calls since then, but my problem now is that sometimes the other caller can't hear me, specially when I'm driving and on bluetooth through the car audio. It can't be the other caller because they were on a stationary, land-line phone. I checked out my mic by making a voice recording so the mic is fine. I just tried unchecking "Enable HD LTE Services" and I'll see what that does and report back. If it were not for the very nice camera, the annoyance of the dropped and muted calls plus the bad battery life would be enough to make me switch this phone. It's got to be a device-specific bug. My HTC M9 is running Android 5.0.2 and is rock solid and never dropped a call. Same with my LG G3. I would send in my S6 for repair, but I'm not sure what they would do. Not only would I get a refurb back, but it might do the same thing. If you've been following the threads, you might have seen that Sprint had to push a special update for it's S6 customers to fix dropped calls. Verizon customers are also having it bad (I'm on AT&T). It can't be all network issues though as like I said, my other devices including an LG G3 have never dropped a call.

Thanks for the response rmc69. I did uncheck the HD lte and it did not help me at all. Let me know if you have a different result. Thank you

The Sprint S6 and S6 Edge have the same problem. I have to turn off the LTE radio all together to have a usable phone. I couldn't send/receive text, I had dropped calls and a very poor signal. Once I turned the LTE radio off, all those problems went away. I realize this is not a fix but it's a workable bandaid for those that are having problems. Good luck to you guys.

Turning off lte did not work for me.

Robert, how did you turn off LTE? By going into the testing mode and changing it from there? Or were you simply referring to unchecking Enhanced LTE Services?

I think I figured it out from this thread, at least for AT&T
http://forums.androidcentral.com/samsung-galaxy-s6/518691-any-way-turn-off-lte-data-galaxy-s6-t-version.html

rmc69 said:
I think I figured it out from this thread, at least for AT&T
http://forums.androidcentral.com/sa...ay-turn-off-lte-data-galaxy-s6-t-version.html
Click to expand...
Click to collapse
I tried that, it did not work for me.

Sorry turning off LTE still didn't help. I guess the only alternatives now would be to wait for 5.1.1 and see what it fixes, or you may just consider asking for a replacement.
Sent from my SAMSUNG-SM-G920A using Tapatalk

rmc69 said:
Sorry turning off LTE still didn't help. I guess the only alternatives now would be to wait for 5.1.1 and see what it fixes, or you may just consider asking for a replacement.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
Yeah that is what I'm afraid of. Every time I go to the at&t store it's a big hassle. Hopefully an update will fix our problems.

@rmc69, is your phone rooted and running a custom rom?

No; pure stock. It's also a 64 GB model. I'm wondering if there is a difference that could affect reception, i.e., is the antenna placement exactly the same. I changed my band to GSM Auto last night removing LTE and so far, I haven't had any dropped calls, but it's too early to tell. The biggest problem I'm having is that sometimes callers cannot hear me, especially in the car using bluetooth.

I am rooted running DennisRom. Yesterday I did a factory reset via the stock recovery and made 4 calls and did not have 1 drop. I'll see how it goes for a few days and report back.

Great! That's encouraging.

Bad news, I just called my wife and the call dropped before she could answer her phone. I think I may give up and get a different phone. I'm loosing hope.