I know you will drop 3g data on a call. That I completely understand. But this is the first device I've used that is dropping my lte data during a call. I'm not sure if this is a rom issue or a modem issue.
I am on sprint, and not sure if this is an isolated issue for sprint customers or across the board.
Another issue I would like to see resolved is patching native tethering. I'm currently stuck using WiFi tether app in ad-hoc mode. Which unfortunately my nexus 7 can't attach to.
In case you're wondering I'm running slim kat currently. I've tried cm and stock before rooting and all formats have dropped LTE on call.
Probably because there is no voice over LTE. Same happens on Rogers too.
Sent from my Nexus 5 using Tapatalk
Elisha said:
Probably because there is no voice over LTE. Same happens on Rogers too.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
But I've always had voice over LTE on Sprint. Just not with this phone. Galaxy nexus, and HTC one never had that issue.
If it's something I have to live with, that's fine. I just would like to see this feature implemented if possible.
maybe its the way the radio is designed for this phone?
thats my only guess.
joebags said:
But I've always had voice over LTE on Sprint. Just not with this phone. Galaxy nexus, and HTC one never had that issue.
If it's something I have to live with, that's fine. I just would like to see this feature implemented if possible.
Click to expand...
Click to collapse
Nope, not going to happen. It requires a very specific setup with the radios that results in poor battery life. Sprint does not run with voice over LTE, it's simply running calls as normal and keeping LTE active at the same time.
In addition, large portions of Sprint's network outright do not support this functionality anyway.
About 3 out of 5 times when I make a call when I am originally on LTE the phone call drops. I am on AT&T and when I make a call it switches from LTE to H+ then all of a sudden it just completely drops signal and thus the call and about 3 seconds later regains signal. Does anyone know what may be causing this issue or has had this issue? I am on 4.4.4 Stock with Root.
Well dropping calls isn't normal, but dropping from LTE to H+ is. VoLTE isn't really a thing yet. Calls don't work over LTE, so when you make a call it automatically drops to H+. That's normal behavior.
Did this just start happening out of the blue? Or always done that? Make sure you have the correct APN settings. If so try calling your provider and see if there's anything they can do for you.
RoyJ said:
Well dropping calls isn't normal, but dropping from LTE to H+ is. VoLTE isn't really a thing yet. Calls don't work over LTE, so when you make a call it automatically drops to H+. That's normal behavior.
Did this just start happening out of the blue? Or always done that? Make sure you have the correct APN settings. If so try calling your provider and see if there's anything they can do for you.
Click to expand...
Click to collapse
Sorry forget to mention I knew that was normal for the drop to H+, but yes the signal drop is not. Well it started out of the blue. IS there a thread on here with what should be the correct APN settings? Also my old nexus 5 started to do this before I returned it under warranty for refurbished, then I had a moto G lte for a month worked fine, got a refurbished (due to warranty) and started again.
Here is a graph of my network coverage to show that the signal just drops.
Sent from my Nexus 7 using XDA Free mobile app
same problem
jgr208 said:
About 3 out of 5 times when I make a call when I am originally on LTE the phone call drops. I am on AT&T and when I make a call it switches from LTE to H+ then all of a sudden it just completely drops signal and thus the call and about 3 seconds later regains signal. Does anyone know what may be causing this issue or has had this issue? I am on 4.4.4 Stock with Root.
Click to expand...
Click to collapse
Mine doesn't seem to have any particular count pattern, it happens very randomly, usually when attempting to call someone and once they pickup on their end, my phone would hang up. This happens maybe 40-50%of the time, can't estimate a guess, but i can say that it happens enough to piss me off. I've checked my AT&T APN, which matches to what the carrier has it set, i even went and got my SIM replaced, rebooted in safe mode, gps works, so it's not a third party app causing this. Last resort is factory reset, although I'm almost positive that won't do anything. I'm currently also running android 4.4.4 stock aosp on a 32Gb N5. Device was purchased new in early may 2014, and came with android 4.4.2 preinstalled. The random call drops issue started in early October, a few months well into 4.4.4 update. All I've found online is that i it has something to do with a missing cellular radio, but to be honest, i don't want to mess with those as that may cause further problems. Called Google, and they act like they're clueless about this issue, all they can offer is a replacement, which is nice, but to be honest, it's probably going to happen again even with the new device. My coworker has the same issue with his 16gb N5 black model. If anyone with this device trying out android 5.0 lollipop preview can chime in on if this problem still persists, would be very awesome. I'm going to wait and see when the official android 5.0 comes out, if that fixes the dropped calls problem, then N5 can be used, if not then I'm getting it replaced and reselling it, may go with the moto x+1. So either a good portion of nexus 5 devices are factory defects or this really is a cellular radio problem. Really hope that lollipop will fix this issue.
The APN only handles packet data and not voice so that shouldn't be the issue.
I would try setting your phone to 3G only for a while and see if the drops still occur when you are on 3G prior to the call.
Syndrome666 said:
Mine doesn't seem to have any particular count pattern, it happens very randomly, usually when attempting to call someone and once they pickup on their end, my phone would hang up. This happens maybe 40-50%of the time, can't estimate a guess, but i can say that it happens enough to piss me off. I've checked my AT&T APN, which matches to what the carrier has it set, i even went and got my SIM replaced, rebooted in safe mode, gps works, so it's not a third party app causing this. Last resort is factory reset, although I'm almost positive that won't do anything. I'm currently also running android 4.4.4 stock aosp on a 32Gb N5. Device was purchased new in early may 2014, and came with android 4.4.2 preinstalled. The random call drops issue started in early October, a few months well into 4.4.4 update. All I've found online is that i it has something to do with a missing cellular radio, but to be honest, i don't want to mess with those as that may cause further problems. Called Google, and they act like they're clueless about this issue, all they can offer is a replacement, which is nice, but to be honest, it's probably going to happen again even with the new device. My coworker has the same issue with his 16gb N5 black model. If anyone with this device trying out android 5.0 lollipop preview can chime in on if this problem still persists, would be very awesome. I'm going to wait and see when the official android 5.0 comes out, if that fixes the dropped calls problem, then N5 can be used, if not then I'm getting it replaced and reselling it, may go with the moto x+1. So either a good portion of nexus 5 devices are factory defects or this really is a cellular radio problem. Really hope that lollipop will fix this issue.
Click to expand...
Click to collapse
Yea it wasn't an exact count but like 3 out of 5 says, enough that is annoys me. Tried all those as well and like I said I have a moto g lte that the sim worked in so it isn't the sim. This is my refurb unit, but the other one I have since November started to do the same thing in August as well on 4.4.4 never had an issue before that. Where did you find that if you don't mind me asking? I am comfy enough to mess with that stuff, so i'll give it a shot.
raptir said:
The APN only handles packet data and not voice so that shouldn't be the issue.
I would try setting your phone to 3G only for a while and see if the drops still occur when you are on 3G prior to the call.
Click to expand...
Click to collapse
Already did and it doesn't but is an annoyance then since part of the price of the Nexus 5 is to have LTE and I am not getting the full product then which is not ideal.
cell radio fix
jgr208 said:
Yea it wasn't an exact count but like 3 out of 5 says, enough that is annoys me. Tried all those as well and like I said I have a moto g lte that the sim worked in so it isn't the sim. This is my refurb unit, but the other one I have since November started to do the same thing in August as well on 4.4.4 never had an issue before that. Where did you find that if you don't mind me asking? I am comfy enough to mess with that stuff, so i'll give it a shot.
Click to expand...
Click to collapse
I found it here (just take away the spaces after .com and after 02/): ianmarmour.com /2014/02/02/ google-nexus-5-fixing-modemcellular-issues-on-34g-networks
It's an older post from February, but seems to have the best details and fixes. If you simply search nexus 5 cellular radio issues or nexus 5 4.4.4 call drops, you should find a lot of these recalls from lots of N5 users. I'm tempted to try it, but don't really feel like sorting all my files in case i brick my device. I'm also not sure if ota update will work if i tinker with cell radios. Otherwise that's the page containing all the details you'd need including links and step by step guides. And hey if it works for you, let me know, maybe I'll try it out if it goes well for you.
jgr208 said:
Already did and it doesn't but is an annoyance then since part of the price of the Nexus 5 is to have LTE and I am not getting the full product then which is not ideal.
Click to expand...
Click to collapse
Exactly, i know that's totally possible, but i wouldn't want a smartphone that has no lte and/or hspa+ service at this point in time. This seems to happen wherever lte isn't as strong or available but hspa+ is. I think the modem responsible for switching between lte and hspa+ causes calls to drop. I took note of it a couple hours ago when i attempted to make a few phone calls resulting in instant call drops. Seems to do it while switching from lte to hspa+ network. I just wish Google would stop burying their heads from the outside world like an ostrich, and get in top of this. I mean this is their flagship device until N6 goes on sale. They should seriously fix this issue or at least stop denying that they've never heard of any complaints with their N4 and N5 customers. I love this device, but a simple fix like this not being addressed by Google is not very professional, especially because it's primary function is to call people. I'm really tempted to flash those radios, but really want to see if Google addresses this issue with an official ota lollipop update.
Syndrome666 said:
Mine doesn't seem to have any particular count pattern, it happens very randomly, usually when attempting to call someone and once they pickup on their end, my phone would hang up. This happens maybe 40-50%of the time, can't estimate a guess, but i can say that it happens enough to piss me off. I've checked my AT&T APN, which matches to what the carrier has it set, i even went and got my SIM replaced, rebooted in safe mode, gps works, so it's not a third party app causing this. Last resort is factory reset, although I'm almost positive that won't do anything. I'm currently also running android 4.4.4 stock aosp on a 32Gb N5. Device was purchased new in early may 2014, and came with android 4.4.2 preinstalled. The random call drops issue started in early October, a few months well into 4.4.4 update. All I've found online is that i it has something to do with a missing cellular radio, but to be honest, i don't want to mess with those as that may cause further problems. Called Google, and they act like they're clueless about this issue, all they can offer is a replacement, which is nice, but to be honest, it's probably going to happen again even with the new device. My coworker has the same issue with his 16gb N5 black model. If anyone with this device trying out android 5.0 lollipop preview can chime in on if this problem still persists, would be very awesome. I'm going to wait and see when the official android 5.0 comes out, if that fixes the dropped calls problem, then N5 can be used, if not then I'm getting it replaced and reselling it, may go with the moto x+1. So either a good portion of nexus 5 devices are factory defects or this really is a cellular radio problem. Really hope that lollipop will fix this issue.
Click to expand...
Click to collapse
Factor resetting it won't help, I've tried it already.
jgr208 said:
Already did and it doesn't but is an annoyance then since part of the price of the Nexus 5 is to have LTE and I am not getting the full product then which is not ideal.
Click to expand...
Click to collapse
part of the price? no. you dont see any phone more expensive because it can handle lte. your issue is with your network, and its signals around you. as we all know that the lte available can not handle voice calls. your isdue involvez lte handing off to H or 3G. thats where your network comes in.
simms22 said:
part of the price? no. you dont see any phone more expensive because it can handle lte. your issue is with your network, and its signals around you. as we all know that the lte available can not handle voice calls. your isdue involvez lte handing off to H or 3G. thats where your network comes in.
Click to expand...
Click to collapse
Then why does my moto g work fine in the same locations? And LTE isn't more expensive on a phone? Please explain then how a LTE phone is more expensive then the 3g variant. Go compare the moto g to moto g LTE. Defeats your argument.
Sent from my Nexus 7 using XDA Free mobile app
jgr208 said:
Then why does my moto g work fine in the same locations? And LTE isn't more expensive on a phone? Please explain then how a LTE phone is more expensive then the 3g variant. Go compare the moto g to moto g LTE. Defeats your argument.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
lol, ok. the moto g variants are an exception to the majority. their already cheap price point being the reason.
those are two different devices, with differing hardware. its possible that moto can catch the signal from a little further away than the n5 can. the n5 was made less expensive because they used less expensive hardware in places. a shorter antenna being one of those places.
---------- Post added at 09:48 PM ---------- Previous post was at 09:44 PM ----------
anyways, if you bought it from google, you can request an exchange.
I wouldn't try any hardware mod, etc as the issue is with the software. This kind of thing happens to me also, regardless of where I am or what network I'm on (tested this with a friends AT&T sim also). In the settings menu my signal strength just says "0" (kid you not ZERO) and sticks there until I manually set the phone to 3g when I go to a place with weak LTE (like a basement).
DISCLAIMER: I am only assuming this as I don't know that much about this topic, but I think stock 4.4.4 doesn't understand that LTE can still be received at worse than -115dbm and causes this fault. It doesn't matter which radio you flash (using the newest dev preview radio on 4.4.4 still has this issue, but on 5.0 it works flawlessly), what network you are on, where you are with strong LTE coverage... If you go to the wrong LTE dead spot you have this issue. It's as if the radio is saying "I'm still good on LTE" and the phone says "-115dbm isn't good we need to switch" and the radio says "I'm still connected to LTE though" and the conflict causes the signal to go to 0. I don't think it's got anything to do with the handoff from LTE to 3G either (but it might, as I said I'm no expert). -115dbm seems to be the doom number for me on LTE with 4.4.4.
Try flashing the new dev preview if you want LTE. No network = 0 bug. Hell I can even get LTE in my basement (at worse than -115dbm, of course). I had to flash back to 4.4.4 though, too many games/apps not updated yet.
Long story short, this is fixed in Lollipop. Less than two weeks...
simms22 said:
lol, ok. the moto g variants are an exception to the majority. their already cheap price point being the reason.
those are two different devices, with differing hardware. its possible that moto can catch the signal from a little further away than the n5 can. the n5 was made less expensive because they used less expensive hardware in places. a shorter antenna being one of those places.
---------- Post added at 09:48 PM ---------- Previous post was at 09:44 PM ----------
anyways, if you bought it from google, you can request an exchange.
Click to expand...
Click to collapse
It worked until august so your argument is void.
Sent from my Nexus 7 using XDA Free mobile app
anactoraaron said:
I wouldn't try any hardware mod, etc as the issue is with the software. This kind of thing happens to me also, regardless of where I am or what network I'm on (tested this with a friends AT&T sim also). In the settings menu my signal strength just says "0" (kid you not ZERO) and sticks there until I manually set the phone to 3g when I go to a place with weak LTE (like a basement).
DISCLAIMER: I am only assuming this as I don't know that much about this topic, but I think stock 4.4.4 doesn't understand that LTE can still be received at worse than -115dbm and causes this fault. It doesn't matter which radio you flash (using the newest dev preview radio on 4.4.4 still has this issue, but on 5.0 it works flawlessly), what network you are on, where you are with strong LTE coverage... If you go to the wrong LTE dead spot you have this issue. It's as if the radio is saying "I'm still good on LTE" and the phone says "-115dbm isn't good we need to switch" and the radio says "I'm still connected to LTE though" and the conflict causes the signal to go to 0. I don't think it's got anything to do with the handoff from LTE to 3G either (but it might, as I said I'm no expert). -115dbm seems to be the doom number for me on LTE with 4.4.4.
Try flashing the new dev preview if you want LTE. No network = 0 bug. Hell I can even get LTE in my basement (at worse than -115dbm, of course). I had to flash back to 4.4.4 though, too many games/apps not updated yet.
Long story short, this is fixed in Lollipop. Less than two weeks...
Click to expand...
Click to collapse
Def wasn't gonna try hardware and only software and great to hear! Did you try out lollipop yet?
Sent from my Nexus 7 using XDA Free mobile app
jgr208 said:
It worked until august so your argument is void.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
if it worked until august, then it supports my point of probably being an issue with your network, and not the phone itself.
simms22 said:
if it worked until august, then it supports my point of probably being an issue with your network, and not the phone itself.
Click to expand...
Click to collapse
But then why does my moto g work? Why is the issue also all the way from Philadelphia to new jersey to new York. That supports software if you ask me. Also it working it lollipop supports software. Also if it was network I think we would hear more about this issue from other phones as well
Sent from my Nexus 7 using XDA Free mobile app
jgr208 said:
But then why does my moto g work? Why is the issue also all the way from Philadelphia to new jersey to new York. That supports software if you ask me. Also it working it lollipop supports software. Also if it was network I think we would hear more about this issue from other phones as well
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
well, try the lollipop preview, it was working for the other guy, see if itll work for you. if it does, great.
Just seeing if this is possible. I'm on AT&T and had the Note 3 and 4 previously. There is no way I'm getting a Note 5 which can't be rooted, so I'm thinking of getting the Tmobile one. My only issue is that I need WiFi calling at home, where I get crappy reception. AT&T WiFi calling has been a lifesaver.
So, any possibility of getting AT&T WiFi calling on a tmobile Note 5? I don't mind rooting and changing rom, although I have a feeling the issue is with the lack of hardware bands.
spinedoc said:
Just seeing if this is possible. I'm on AT&T and had the Note 3 and 4 previously. There is no way I'm getting a Note 5 which can't be rooted, so I'm thinking of getting the Tmobile one. My only issue is that I need WiFi calling at home, where I get crappy reception. AT&T WiFi calling has been a lifesaver.
So, any possibility of getting AT&T WiFi calling on a tmobile Note 5? I don't mind rooting and changing rom, although I have a feeling the issue is with the lack of hardware bands.
Click to expand...
Click to collapse
Due to the hardware differences in the att and
the tmobile phones tmobile's wifi calling will not work on an att phone even if the att phone is unlocked and rooted.
Good luck,
Sent from my SM-G928T using Tapatalk
spinedoc said:
Just seeing if this is possible. I'm on AT&T and had the Note 3 and 4 previously. There is no way I'm getting a Note 5 which can't be rooted, so I'm thinking of getting the Tmobile one. My only issue is that I need WiFi calling at home, where I get crappy reception. AT&T WiFi calling has been a lifesaver.
So, any possibility of getting AT&T WiFi calling on a tmobile Note 5? I don't mind rooting and changing rom, although I have a feeling the issue is with the lack of hardware bands.
Click to expand...
Click to collapse
AT&T currently only supports WiFi Calling on the iPhone 6/6+/6S/6S+.
The software installed on our phones is configured to work with T-Mobile's implementation of WFC, and would most likely not work even when AT&T brings WFC to Android.
Anyone running the google pixel 2 on AT&T unlocked? If so thoughts, I've been reading that VoLTE does not work nor does WiFi calling. I have a Samsung S8 that I purchased from Best Buy and I flashed the AT&T firmware to get all this working. I know that this phone is not on AT&T so I doubt there will be a way to flash any firmware since this device is not sold by AT&T.
Anyway, just throwing it out there for feedback from Google Pixel 2 users on AT&T.
I signed up for Android beta, and had VoLTE and HD voice on AT&T, but not wifi calling. I switched back to the Nov security release to see if Bluetooth issues were fixed and those things went away. I have since re-signed up for the beta, but haven't gotten an OTA yet for the next beta, but I'd assume they will come back. So the answer to your question is yes and no....
53fireman said:
I signed up for Android beta, and had VoLTE and HD voice on AT&T, but not wifi calling. I switched back to the Nov security release to see if Bluetooth issues were fixed and those things went away. I have since re-signed up for the beta, but haven't gotten an OTA yet for the next beta, but I'd assume they will come back. So the answer to your question is yes and no....
Click to expand...
Click to collapse
Thank you for the feedback, this is the only thing that keeps me from buying this phone unlocked. At&T service sucks where I work, so I'm dependent on WiFi calling functionality. I think I may have to switch to Verizon if I really want this phone.
I went back and forth on keeping it vs going back to my HTC One M9 that seemed to work flawlessly.... The Pixel 2 is nice and the battery is sweet, but I feel like the technology goes backwards sometimes with the Bluetooth issues and lack of some casting support. I decided to keep it, in the hopes that the Bluetooth issues will get resolved, and the battery life. I have good AT&T service, so those things I never had, I didn't even know what I was missing.
53fireman said:
I went back and forth on keeping it vs going back to my HTC One M9 that seemed to work flawlessly.... The Pixel 2 is nice and the battery is sweet, but I feel like the technology goes backwards sometimes with the Bluetooth issues and lack of some casting support. I decided to keep it, in the hopes that the Bluetooth issues will get resolved, and the battery life. I have good AT&T service, so those things I never had, I didn't even know what I was missing.
Click to expand...
Click to collapse
I have an S8 that I purchased out right unlocked from Best Buy. The phone is good but I get irritated because it runs like a snail from time to time and it drives me insane. A quick reboot fixes it all but then after some use (days) it's starts doing it again. Maybe it's all the dumb Samsung bloatware that slows it down. Which is why I like the clean vanilla UI on the pixel 2.
bezerk19 said:
Anyone running the google pixel 2 on AT&T unlocked? If so thoughts, I've been reading that VoLTE does not work nor does WiFi calling. I have a Samsung S8 that I purchased from Best Buy and I flashed the AT&T firmware to get all this working. I know that this phone is not on AT&T so I doubt there will be a way to flash any firmware since this device is not sold by AT&T.
Anyway, just throwing it out there for feedback from Google Pixel 2 users on AT&T.
Click to expand...
Click to collapse
I can confirm that HD voice works fine on my unlocked Pixel 2 on AT&T. HD voice was added in Android 8.1.
lacibaci said:
I can confirm that HD voice works fine on my unlocked Pixel 2 on AT&T. HD voice was added in Android 8.1.
Click to expand...
Click to collapse
does VOLTE work if you're on AT&T prepay?
elijahblake said:
does VOLTE work if you're on AT&T prepay?
Click to expand...
Click to collapse
Not sure. You can test it yourself though. Find another phone (person) on AT&T with a handset that supports HD voice and make a phone call - making sure you're in well covered LTE area.
You will see "HD" displayed on you Pixel 2 screen under the name of the person you're calling.