Hey all,
I recently picked up a LG G2 (second hand)
and I believe I have some issues with the phone not picking up LTE so easily.
Before this, I had Iphone 5, nexus 4, G Pro, Gnote2, etc... and they all picked up LTE just fine at my home
However, G2 rarely picks up LTE signal and it is mostly on HSPA+ (4G Icon) I believe.
I took it into AT&T store to see if I could get a new sim card but when I got there, the phone picked up LTE no problem.........
Looks like many Sprint users are experiencing same issue.. is there a fix for this??
*The phone is currently on stock / non-rooted 4.4.2
Thank you in advance!
I'm in the same boat as you, my data will work for a good 30+ min and then all of sudden no network for 30 seconds or so. I've also been unable to connect to a lte signal I've only been able to use hspa, searching the threads on here have been hit and miss with a lot of vague answers but nothing clear cut if anyone's dealt with this and has a clear fix it would be appreciated.
Sent from my LG-D800 using Tapatalk
A little update to this, yesterday I went to AT&T to see if I could maybe clear this up with a new SIM card and while waiting I checked out the two G2s they had there, these two display phones were literally 10 ft apart and one had lte while the other one was stuck on 4g only. I think this is looking more like a hardware issue now after checking out both store phones on display, I'm going in today to swap out my handset to see if this will solve it.
Sent from my LG-D800 using Tapatalk
Here's another update for those with lte or signal loss issues, after trying everything I could find on these forums the only answer was a warranty swap out, as soon as I put my SIM card into the warranty phone let showed up and after half a day I haven't experienced no random signal loss at all.
Sent from my LG-D800 using Tapatalk
Interesting...
This is interesting. Currently running CM11 latest nightly and I thought it was due to CM codebase. It looks like non-CM related?
Please keep the details coming. When I have time, I will flash a stock ROM to see what happens. But at this point, it looks scary that maybe hardware problems might be there.
For comparison, 2 iPhones literally next to G2 had 3 bars with LTE while my G2 had no network.
ainstushar said:
This is interesting. Currently running CM11 latest nightly and I thought it was due to CM codebase. It looks like non-CM related?
Please keep the details coming. When I have time, I will flash a stock ROM to see what happens. But at this point, it looks scary that maybe hardware problems might be there.
For comparison, 2 iPhones literally next to G2 had 3 bars with LTE while my G2 had no network.
Click to expand...
Click to collapse
After a full day and a half use now im fulling supporting the theory of a hardware fault. Before returning my phone for a replacement i was fully rooted on gardys kit kat rom with recovery, i had read that supposedly rooting or flashing was apparently breaking lte so i went back to the stock jellybean rom only to discover the issue still there, i then fully updated to the over the air kit kat update which also did not solve the issue. It really does look like theres a issue with the phone itself.
Sent from my LG-D800 using Tapatalk
Oh wow. Thanks for your reply.
So i have tried working on this and so far no good.
LTE picks up good when i walk into an att store and that is causing difficulty with store workers..
I get stable, steady connection with hspa+ but rarely pick up LTE..
What is the process of getting a replacement? Its way over 15,30 day period for me..
Sent from my LG-D800 using Tapatalk
For me lte did not work at all even in store, I can see where you might have a issue if they can't reproduce the issue but just be persistent and they should take care of it for you. As for warranty you have a year from your purchase date for a warranty claim through At&t, I went through a device support center which you might have depending on where you live otherwise you can send it in. You must revert back to a complete stock state or you will be more than likely denied.
Sent from my LG-D800 using Tapatalk
Got it fixed after several attempts with new sim cards! Picks up Lte fine! Wootwoot
My fix
call att tech support make sure that the lg g2 imei matches your line/sim card
So I went through a bunch of phones in the past couple weeks, I have at&t service but my last phone was verizon droid maxx. Next I went to the AT&T store and he put my phone number under the new sim card for my AT&T LG G2 but the rep didn't ask me for the IMEI or look at the phone at all, he just got my line on the new sim and I left. I noticed the phone was going back and fourth to LTE but it was 4g (non LTE) about 70% of the time. I changed APN settings, I updated, nothing worked. Then I remembered a long time ago that if you go from android, blackberry, or iphone to another type of phone you would have to call att and make sure something was changed so I called att tech support and asked if they would put my IMEI under the new sim, the tech said yeah I should do that because currently my line doesn't show I have the g2 (make sure to call tech support because online it'll show you have a g2 and if you call costumer service usually they will see the g2 too) and after that i reset my phone and got LTE 100% of the time since then.
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.