Drop calls on Nexus 5 ATT!
- Thread starter Aj Irawan
- Start date
with BYODs, ATT (nor tmobile) **can't** fully control the QoS via the IMS core, which implements their IP telephony (wifi calling / volte) -
it would wreck havoc on the party crashers like the nexus 5, & other unlocked devices, maybe even native carrier devices, when they make upgrades to retrofit IP telephony via IMS..
& it's not so much an IMS issue (that expounded the lte issue), but it's how lte was retrofitted on legacy networks to begin with, & with the changing of QUALCOMM's chipsets - the combination threw skates underneath how both the devices & networks inter-acted..
I already linked this thread over at xda, it's only fair that you all get a birds eye of what they're talking about over there too -
Calls made when on LTE keep getting dropped | Google Nexus 5 | XDA Forums
I went there long ago there -
[Q] a nexus 5 e.csfb issue - Pg. 2 | Google Nexus 5 | XDA Forums
& asked for help troubleshooting for this lte IP handover issue, ( it wasn't just a sprint issue I found).. I guess I was wearing the wrong shirt or shoes in that thread.. no1 participated..
but oddly, it came full circle in the **Calls made when on LTE keep getting dropped** thread.. go figure..
Last edited:
At the risk of jinxing myself, my Nexus 5 with AT&T is excellent.
But to explain away your trouble with AT&T's priority list and unbranded phones? Unacceptable. It doesn't matter if you bring your own device, especially now that AT&T no longer subsidizes devices (AT&T Next has you paying full price for the phone in 2 years worth of monthly installments; the "discounted" price with a two year contract eliminates an otherwise standard $15 or $25 monthly discount on your data plan, to be sure you pay them the full price for the phone over two years).
If you have an authentic AT&T SIM card in your phone and you are paying AT&T for monthly cell phone and data service, it should work. If it doesn't, it means they are taking your money but not providing such service. Get a lawyer.
But to explain away your trouble with AT&T's priority list and unbranded phones? Unacceptable. It doesn't matter if you bring your own device, especially now that AT&T no longer subsidizes devices (AT&T Next has you paying full price for the phone in 2 years worth of monthly installments; the "discounted" price with a two year contract eliminates an otherwise standard $15 or $25 monthly discount on your data plan, to be sure you pay them the full price for the phone over two years).
If you have an authentic AT&T SIM card in your phone and you are paying AT&T for monthly cell phone and data service, it should work. If it doesn't, it means they are taking your money but not providing such service. Get a lawyer.
i'm continuing to have the issue so i just set preferred network to 3G and will leave it like that until Lollipop.
brosko
Well-known member
- Nov 30, 2013
- 1,466
- 1
- 38
reception is same - but that's not really a fair question because if LTE is not available the phone reverts to 3G anyway.
the only thing you are losing from 4G LTE to 3G as far as i can tell is some download speed and IMO it's not that noticeable with most daily regular use on a phone. sometimes you're on 3G anyway even when LTE is set as preferred. however - i'm not happy that we need to use this kludge fix.
I live in SNJ / Philly area and the same problem over here....
LTE>H>zero signal unless I'm on wifi then it works fine.......
started happening last week..... no one at AT&T or Google had ever heard of this problem apparently...
I'm hoping Andriod 5.0 fixes it, but by the way everyone is talking, it's AT&T and their network and not prioritizing BYOD phones...
LTE>H>zero signal unless I'm on wifi then it works fine.......
started happening last week..... no one at AT&T or Google had ever heard of this problem apparently...
I'm hoping Andriod 5.0 fixes it, but by the way everyone is talking, it's AT&T and their network and not prioritizing BYOD phones...
Same problem here... Delaware County and Philadelphia area... past few weeks. GPS has also been garbage for months now.. not sure if that's related, but I always have issues with the GPS on my N5. I called support yesterday and they noted it down.. They told me to go to a store and get an updated SIM today, and if that doesn't fix it, they push the report to their engineering side. Probably is something to do with VOLTE as was mentioned here.. Everyone should make a phone call to them.. The more of us that do, the more likely we are to get a timely resolution.
i feel better that it seems to be an isolated problem geographically - which tells me it's not a phone hardware fault/defect.
Update: Had the sim changed out.. It didn't fix anything. Problem remains.
I just called AT&T support again, and this time they opened a case and they are going to call me back..(On or before Nov 6.. ugh)
I suggest that everyone with the problem do the same.
I just called AT&T support again, and this time they opened a case and they are going to call me back..(On or before Nov 6.. ugh)
I suggest that everyone with the problem do the same.
Last edited:
I have been having the same problem with my OnePlus One. Likewise I am also in NYC and this problem has been occurring since last week (well that's when I noticed it). Since this seems like an isolated issue with the Northeast, seems like the Mid West and West haven't face this problem? Haven't read anything about it working/not working out there. Has anyone heard anything about it?
Problem remains even in safe mode.. or with google voice turned off.. but it seemed less often nonetheless (coincidence probably)..
Anyway I also contacted google nexus support.. They want to send me a refurb replacement, but I don't think that will fix it. I know others with the same device and same problem.. Not to mention the OnePlus One users are having the issue also. Either way, spread the word as much as you can and hopefully we can get a fix. Make the call to AT&T above all.
Anyway I also contacted google nexus support.. They want to send me a refurb replacement, but I don't think that will fix it. I know others with the same device and same problem.. Not to mention the OnePlus One users are having the issue also. Either way, spread the word as much as you can and hopefully we can get a fix. Make the call to AT&T above all.
I was talking with my friend again who said that the Engineer he spoke with said that the Engineers in the area should see an elevated drop call rate and investigate the cause, but did temper that by saying, "should" and the NY Metro area is a big market and lots of moving parts could make it more difficult to notice, especially since it is only affecting "Grey" IMEIs.
I did call front line customer service and while the representative was very nice, she admitted that all she could do was suggest getting a new SIM as at&t Mobility official policy is not to support unbranded handsets. She did say she would file a trouble ticket with Engineering, but did temper that by saying in her experience that doesn't really do all that much.
So, I am not sure where exactly that leaves the problem, eventually it will be fixed, that I am entirely sure of, it is just going to be a matter of when, sadly.
Dan
I did call front line customer service and while the representative was very nice, she admitted that all she could do was suggest getting a new SIM as at&t Mobility official policy is not to support unbranded handsets. She did say she would file a trouble ticket with Engineering, but did temper that by saying in her experience that doesn't really do all that much.
So, I am not sure where exactly that leaves the problem, eventually it will be fixed, that I am entirely sure of, it is just going to be a matter of when, sadly.
Dan
I have been going crazy with this same problem for the past week. Same issue, N5 on AT&T in NYC area. I was preparing to do a factory reset tonight until I saw this thread. Looks like I'll be calling AT&T instead.
Will try 3G in the mean time.
Posted via Android Central App
Will try 3G in the mean time.
Posted via Android Central App
Yea don't bother.. It's not your device. I hope Lollipop fixes it.. or at least the AT&T engineers.. that's why everyone needs to call to log a case.
you know, I wanted to make a correlation to *this* to se if anyone WASN'T having problems while using google voice / mobile number integration like myself (I'm not having the same issues of cut off calls like the thread)
& from google searching, seems the pure mobile number / google voice integration is limited to sprint's cdma network, so there's no way to compare..
Similar threads
Facebook
Twitter
Instagram