Drop calls on Nexus 5 ATT!

"..To be clear, IMS did not solve AT&T’s network coverage problems in NYC; building out a decent radio network solved that. But it does highlight that Telcos cannot simply offer ONLY the best effort experience of say Skype, where voice gets garbled or the line goes blank and then the voice comes back again but a couple of sentences have been lost. BUT for some customers and some conversations this is clearly acceptable, given the volume of traffic Skype represents internationally, over one third of voice traffic and near 100% of consumer video telephony traffic.

Also there are lots of scenarios where a call starts on 4G and then needs to drop to 3G. Unless a telco makes the simplifying assumption that 4G works everywhere, which as a Verizon customer is not yet the case on its network. This complex network scenario IMS solves so communications just work..."



IMS and IP Communications, Two Different World Views?
 
I think everyone is overlooking the newest upgrade to KitKat. Google just pushed out 4.4.4 and that's when I started getting disconnected after 2-3 seconds on a call.

Its possible that the update is not compatible with AT&T. This is yet another problem that Google /Android needs to address quickly.

I downgraded my Nexus 5 to 3G and I'm able to use the phone for in & out going.

I'm in Northern NJ

Posted via the Android Central App
 
I've had 4.4.4 for months now..(Stock version, not rooted or anything like that) Problem just came up a week or 2 ago from what I can tell.
 
Am I the only one whose nexus 5 has completely gone to "no service"??. Unable to make or receive calls and texts. I've been having the dropped calls, so I switched to 3g yesterday and it was working fine. Then this morning it was no service. Changed back to LTE, the 3g, then 2g, turning on and off multiple times and still nothing. I've called att and they're not help, making u do the same things you've done over and over again. Now they'll call me back. How does no one know what exactly is going on and what the fix is?
This sucks!!
 
Turn off LTE and reboot if you need to make more reliable phone calls.. (Set it to 3g).. Or connect to WiFi somewhere.. It seems to work fine for me when I do that as well.
 
so let me get this straight - i got a gimped Nexus 5 on AT&T, no OTA Lollipop, and no pre-order Nexus 6?

i'm pretty much just left holding nothing but my **** in my hands.
 
It's a diabolical plot by AT&T to force Nexus 5 users on their network to purchase the new AT&T branded Nexus 6

Posted via Android Central App
 
Any other fix or temp fix? Its so weird. I can go on the internet on the phone tho.

i would do a couple reboots and try again with 3G only. and as a last resort try a new SIM card and/or a factory reset. your problem sounds unrelated as we are able to make calls normally under 3G. good luck.
 
It's a diabolical plot by AT&T to force Nexus 5 users on their network to purchase the new AT&T branded Nexus 6

Posted via Android Central App


lmao....


could be..

you noticed how many of the carriers, suddenly *stop* carrying the nexus 5, even sprint?


what secret sauce does it contain that the carriers don't want revealed??!

will the next update unlease this secret sauce ( that the other phones don't have) minus the nexus 6?

& a lookback -

http://forums.androidcentral.com/google-nexus-5/323425-does-lack-volte-confirmation-nexus-5-deter-anyone-upgrading.html
 
Last edited:
Thanks but I did everything you already suggested. . I then rebooted in 2g and now its working. Lol unbelievable, this situation is.
 
Just called AT&T to check on my case.. They said that the problem is indeed with HD Voice.. The Nexus 5 wants to use it, and the network is not yet capable of it, or at least that is how they described it to me. They did confirm that LG is working on an update to prevent the Nexus 5 from trying to use HD Voice in the future. The workaround is to use 3G instead of LTE mode when making calls. I still think everyone needs to call them so they get on LG / Google's case about this.
 
Just called AT&T to check on my case.. They said that the problem is indeed with HD Voice.. The Nexus 5 wants to use it, and the network is not yet capable of it, or at least that is how they described it to me. They did confirm that LG is working on an update to prevent the Nexus 5 from trying to use HD Voice in the future. The workaround is to use 3G instead of LTE mode when making calls. I still think everyone needs to call them so they get on LG / Google's case about this.

what's strange is why only NYC/NJ/Philly? is that where AT&T is testing it?
 
As it was explained to me, the issue which any unbranded LTE capable handset is experiencing is almost 100% on at&t Mobility.

The issue as it was explained to me is as follows: During this testing, the Base Station Controllers in the NY Metro Area (the device which is responsible for controlling a few to multiple cell sites) are trying to upgrade a user's call from 3G (which is fairly crowded) to 4G VoLTE (which is relatively empty) and the Nexus 5 (at least as of today) is NOT capable of VoLTE and thus drops the call.

Eventually the testing will end and hopefully the Engineers will make the necessary configurations to prevent the network from trying to upgrade handsets from 3G calls to 4G calls which the handset is not capable of making.

It is possible that Google/LG are working on some sort of software work around to prevent the handset from handing the call over to 4G, but as it was explained to me, it would be far easier for the at&t Engineers to simply make the needed corrections on their end. It is also possible that the Google/LG are going to release either with Lollipop or another software patch down the rode, the ability for the Nexus 5 to make VoLTE (aka HD Voice) calls, but that is unknown at this time.

Dan
 
they over xda,

talking about flashing roms & whatnot, trying to fix the issue..


smh..



i wonder if it sunk in that it's not the phone, that's at fault.
 
they over xda,

talking about flashing roms & whatnot, trying to fix the issue..


smh..



i wonder if it sunk in that it's not the phone, that's at fault.

No offense to XDA, the work their users do is nothing short of amazing and deserves respect.

Having said that, in my experience Software folks see Software, just like Hardware folks see hardware and so forth and so on. I know from personal experience that it is really hard to see outside your wheelhouse and it sounds like XDA members are having trouble seeing outside their wheelhouse of Software and modifications of Software.

Again, it is not a criticism, it is just what happens, even to myself from time to time. That is not to say a software work around may not be a viable solution, but as it was explained to me, it would be easier if at&t just made the fixes on their end.

Dan

Posted via Android Central App
 

Trending Posts

Forum statistics

Threads
954,623
Messages
6,962,230
Members
3,163,095
Latest member
jams