Database Info

[Q] Losing data/voice connections....

So, my wife bought this phone a couple of months ago, and for the most part she likes it. However, she does have problems with the phone loosing voice and/or data connections. She uses the Sprint Zone to check, and often times one or the other has failed. After the first time this happened, I spent a lot of time with sprint getting the phone refreshed. Eventually we returned it for another one, but are still having the same intermittent problem.
We have found out that putting the phone into airplane mode will reset the radios and it works again, but eventually we loose one or the other.
So, do others have this issue, and if so, what did you do to fix it? I looked around (albeit not as hard as I could have) but I haven't seen much on this....
thanks!

yep, i have this happen sometimes, but haven't found any solution other than what you said: toggling airplane mode. and the issue seems to have persisted thru software updates.... although the latest official asa14 release seemed to be decent, the main problem i had was when switching from cdma/lte to cdma or vice versa, i would have to toggle airplane mode to get it to reconnect.
on the JB soak update, i've seen data seem to be connected, but no data will load at times.

I believe that its been stated that until official lte launch that the different signals will not handshake properly when switching towers, but that may not be your situation.
Sent from my XT897 using xda app-developers app

ok yeah, i believe the launch became official a week or so ago in my area, and the transition does seem to be seamless now.
another thing i see is the 3G icon and signal bars randomly turning white(instead of blue), and no data loading. but to be fair, that is on the JB beta test build..

Thanks for the input! I'm not sure if it's switching towers or not, I think there was at least one time that it was. Denver doesn't have LTE yet (supposedly, the Sprint Call Center in Centennial does, haven't confirmed or denied yet) so I can't test that. We'll be in KC next month, they do and I'm planning on checking it.
I'll keep an eye on it, and report back. Hopefully she gets JB soon... there's a lot of cool things with it I'm showing her she can't do.

I live in the chicago area and we got LTE a few months ago and I did have this issue for a while but as the rollout of the new equipment went along and more towers were updated i had it less and less. Dont seem to have it at all anymore.

Cool, thanks! No clue when Denver is getting it, if ever. Could be tomorrow, could be two weeks before 5G is rolled out....

toolegit said:
Cool, thanks! No clue when Denver is getting it, if ever. Could be tomorrow, could be two weeks before 5G is rolled out....
Click to expand...
Click to collapse
I use s4gru.com to keep track of when rollouts are hitting.
Colorado appears to be Q4 2013 - but I don't think that is going to be accurate, that is just the original plan...
http://s4gru.com/index.php?/topic/212-network-visionlte-deployment-running-list/

Yeah, I've been watching that site. They have a colorado thread there that I have bookmarked....
I'm just a cynic.

[Q] Signal drop/No service

Just wondering if any one else gets this, sometimes my signal just drops out and I get no service.
Then it comes back it does not happen all the time, I live in a big city Leeds infact so signal is quite strong.
Just wondering if it could be a fault with the phone?
Thanks

I've noticed it happens to me too.

Tony_YYZ said:
I've noticed it happens to me too.
Click to expand...
Click to collapse
I was wondering if its my device because I live in the city and the signal is excellent around here, my other phone HTC sensation never had this problem. Was concerned it could be software/hardware problem possibly.
Sent from my Nexus 5 using Tapatalk

bassist9 said:
I was wondering if its my device because I live in the city and the signal is excellent around here, my other phone HTC sensation never had this problem. Was concerned it could be software/hardware problem possibly.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It's likely the radio software.

Tony_YYZ said:
It's likely the radio software.
Click to expand...
Click to collapse
Right I see could this possibly be fixed in next update you think?
Sent from my Nexus 5 using Tapatalk

bassist9 said:
Right I see could this possibly be fixed in next update you think?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It is definitely possible.

I'm on AT&T and have the correct APN settings and have called AT&T with my IMEI. I have significantly worse signal than with my HTC One X. I am not comparing bars to bars, but rather where the signal drops completely. In places where I had low signal but still connected I now have nothing.

Straight talk using at&t Sim and notice radio drops..
Sent from my Nexus 5 using xda app-developers app

T-Mobile on stock ROM i had my first signal drops.
I was fine (or at least never noticed them) from the time i got my phone (day one) without any drops here in orlando.
Drove over to Tampa/Venice Beach area this past weekend and noticed some drops. Had about 6 drops according to my battery stats in 2 days. i had good to excellent coverage the entire time except when it would drop comlpetely (outline of signal bars)
would connect in a couple seconds, but i noticed over night, it would drop for a pretty large amount of time (like 10-15 minutes at a time.)

Mmm defo seems like were all having the same issues, wonder what it could be
Sent from my Nexus 5 using Tapatalk

I had this issue too, and here's how I fixed it:
By default LTE is enabled, meaning the phone will periodically scan for a LTE network. If you're in a big city, you're likely to find one. Your phone will attempt to connect. However, it fails, meaning it will have to rescan the HSPA bands to connect back. That results in a few seconds of no service. Why can't it connect to LTE? Because by default, the APN is not the LTE APN, for Rogers at least. I'd assume AT&T would be the same. You can test this by dialing *#*#4636#*#*, selecting phone info, and selecting LTE only. You'll see that there is no service. I tested this in an area I knew had great LTE coverage, and that led me to the conclusion that it's LTE causing the signal drops.
So how to fix? Simple, just change your APN to the LTE APN for your carried. To do that go to Settings -> More -> Mobile Networks -> Access Point Names. If you're experiencing this issue on Rogers, change the APN field to ltemobile.apn. If you're on another carrier, you'll have to search for their LTE APN configuration.
After doing this your phone should start connecting to LTE again, and you won't get those annoying signal drops.

PaulGoogle Employee
Nov 20
A few days ago I let you know that we'd be reaching out on email to some of you for some additional bug report data. I'd like to thank everyone who responded to our email -- the bug data you sent in has been helpful to us in tracking this down.
This is looking like a software issue on our side, and we're investigating a fix.
Click to expand...
Click to collapse
So yeah the next update will probably fix the issue. It's not so bad in the meantime, Lightflow sill notify you that your nexus has lost signal, and you still get the internet and incoming calls.

We're not alone. Supposedly Google is "aware" of the issue.

i've hcanged my setting from '4g' to '3g' to see if i notice a difference (hopefully will) then when 4g is released or i get a 4g sim, can move it back up

Yes, I'm having issues too. The real problem is the fact that I have a Wilson cell booster in my home (supposed to have up to 5000 square foot range) and my n4 had full bars most everywhere inside. With my n5 It shows 1 to 2 bars if I'm lucky and quite often drops to none! The only way to get full bars Is to stand right under the indoor antenna. Not impressed, and I sure hope this is fixable!
sent from my next gen N7

I hate to revive a dead thread, but I was wondering if people were still having problems. Once or twice during the day that I can see I will lose signal for a few seconds only to have it reconnect. Running 4.4.2 so the latest update did nothing to help the problem as far as I can see and I have messed with my APN settings. On AT&T. The Google thread seems to have a lot of different problems on the same thread, and it is a bit unclear if people are still having this problem. This is very annoying for such an otherwise spectacular phone. Thanks and sorry again for reviving the thread... :fingers-crossed:

gidgiddonihah said:
I hate to revive a dead thread, but I was wondering if people were still having problems. Once or twice during the day that I can see I will lose signal for a few seconds only to have it reconnect. Running 4.4.2 so the latest update did nothing to help the problem as far as I can see and I have messed with my APN settings. On AT&T. The Google thread seems to have a lot of different problems on the same thread, and it is a bit unclear if people are still having this problem. This is very annoying for such an otherwise spectacular phone. Thanks and sorry again for reviving the thread... :fingers-crossed:
Click to expand...
Click to collapse
Actually, there have been several threads on the issues associated with this (emergency calls only, missed calls, no signal,etc.). Ongoing and unresolved for some.

wideasleep1 said:
Actually, there have been several threads on the issues associated with this (emergency calls only, missed calls, no signal,etc.). Ongoing and unresolved for some.
Click to expand...
Click to collapse
Appreciate the speedy reply. Hope Google gets on this fast. I also have LTE connection issues which has plagued both this and my original device so I am pretty sure its a radio issue. The phone loves to stay on HSPA+ even when there is a decent LTE connection: it's last in the pack to connect to LTE and first to disconnect when compared to others on AT&T.

gidgiddonihah said:
Appreciate the speedy reply. Hope Google gets on this fast. I also have LTE connection issues which has plagued both this and my original device so I am pretty sure its a radio issue. The phone loves to stay on HSPA+ even when there is a decent LTE connection: it's last in the pack to connect to LTE and first to disconnect when compared to others on AT&T.
Click to expand...
Click to collapse
My N4 with a combo radio sticks to LTE a tad better than my N5 with stock radio. Sadly, morrislee hasn't fiddled and combo'd N5 radios, and I'm not sure they've been tested and sussed out like the N4 radios. Citing the fact some with issues have flashed all the radios so far with minimal success means we wait for Qualcomm, after Google kicks them in the you know where.

wideasleep1 said:
My N4 with a combo radio sticks to LTE a tad better than my N5 with stock radio. Sadly, morrislee hasn't fiddled and combo'd N5 radios, and I'm not sure they've been tested and sussed out like the N4 radios. Citing the fact some with issues have flashed all the radios so far with minimal success means we wait for Qualcomm, after Google kicks them in the you know where.
Click to expand...
Click to collapse
Hopefully Google kicks hard and fast . Multiple times if needed. Thanks again for the speedy and enlightening replies. Much obliged.
Sent from my Nexus 5 using Tapatalk

Calls made when on LTE keep getting dropped

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.

Unable to establish a wireless data connection

I have two Sprint Galaxy S8s that I purchased from Sam's Club. I have the same issue with both of them. Please respond if you are having this issue, or not and if you have found a fix. Apparently it is an issue on multiple Samsung devices with Sprint.
I continuously get a pop-up error that states:
Unable to establish a wireless data connection
LTE: ESM - 38 EMM - x
In the notification panel it shows:
RilNotifier
Mobile data connection error
I have spent hours on the phone with Sprint and they have not been able to permanently fix it. The last person talked to told me to take it to a store and they could fix it. Well, we all know how that goes....
There is 1 temporary fix. If I put in the Dialer code: ##72786# and let it do its thing, it will have no issues until the next time the phone is restarted.
I have update the PRL and profile numerous times. I have installed the latest system updates, factory reset. Nothing permanently fixes it thus far.

mikeregister said:
I have two Sprint Galaxy S8s that I purchased from Sam's Club. I have the same issue with both of them. Please respond if you are having this issue, or not and if you have found a fix. Apparently it is an issue on multiple Samsung devices with Sprint.
I continuously get a pop-up error that states:
Unable to establish a wireless data connection
LTE: ESM - 38 EMM - x
In the notification panel it shows:
RilNotifier
Mobile data connection error
I have spent hours on the phone with Sprint and they have not been able to permanently fix it. The last person talked to told me to take it to a store and they could fix it. Well, we all know how that goes....
There is 1 temporary fix. If I put in the Dialer code: ##72786# and let it do its thing, it will have no issues until the next time the phone is restarted.
I have update the PRL and profile numerous times. I have installed the latest system updates, factory reset. Nothing permanently fixes it thus far.
Click to expand...
Click to collapse
I was having/have this issue as well, but seems to only happen when I have been on Wifi Calling and loose Wifi connection.

ait1071 said:
I was having/have this issue as well, but seems to only happen when I have been on Wifi Calling and loose Wifi connection.
Click to expand...
Click to collapse
It happens to me regardless of the Wi-Fi/Wi-Fi calling situation.
Sent from my SM-G950U using Tapatalk

I have this issue and it only happens when I have location toggled on.
I've redone profile etc, but as soon as location is turned on it re-appears.

this happens to me occasionally as well. Not sure what is causing it. I normally toggle the "Mobile Data" on and off to get rid of it. It is at random times and not that often but it is annoying for sure

I noticed this today also. I toggled airplane mode but it keeps coming back...

I also have an S8 from Sam's with this same issue, as well as 2 G6's that i purchased from Sprint's web site that constantly drop data connection. Tried all kinds of settings changes, including changing bands, carrier aggregation, reset network, sim pull, etc and currently have a ticket open with the "network team". I have an S6 on the account also that has been upgraded to Android 7. It has no issues at all. Also, the issues seem to only happen in LTE only areas, I have been to an LTE-Plus area twice and the phone maintained a constant connection. That makes me think this is related to HPUE. BTW, the G6 will stay connected for 10 seconds on lte, then lose all data connection for 15 seconds, then repeat. I have watched and timed this behavior with a stop watch for close to 30 minutes, while moving and standing still.

mikeregister said:
I have two Sprint Galaxy S8s that I purchased from Sam's Club. I have the same issue with both of them. Please respond if you are having this issue, or not and if you have found a fix. Apparently it is an issue on multiple Samsung devices with Sprint.
I continuously get a pop-up error that states:
Unable to establish a wireless data connection
LTE: ESM - 38 EMM - x
In the notification panel it shows:
RilNotifier
Mobile data connection error
I have spent hours on the phone with Sprint and they have not been able to permanently fix it. The last person talked to told me to take it to a store and they could fix it. Well, we all know how that goes....
There is 1 temporary fix. If I put in the Dialer code: ##72786# and let it do its thing, it will have no issues until the next time the phone is restarted.
I have update the PRL and profile numerous times. I have installed the latest system updates, factory reset. Nothing permanently fixes it thus far.
Click to expand...
Click to collapse
Are you in an LTE-Plus area?

rockywall said:
I also have an S8 from Sam's with this same issue, as well as 2 G6's that i purchased from Sprint's web site that constantly drop data connection. Tried all kinds of settings changes, including changing bands, carrier aggregation, reset network, sim pull, etc and currently have a ticket open with the "network team". I have an S6 on the account also that has been upgraded to Android 7. It has no issues at all. Also, the issues seem to only happen inLTE only areas, I have been to an LTE-Plus area twice and the phone maintained a constant connection. That makes me think this is related to HPUE. BTW, the G6 will stay connected for 10 seconds on lte, then lose all data connection for 15 seconds, then repeat. I have watched and timed this behavior with a stop watch for close to 30 minutes, while moving and standing still.
Click to expand...
Click to collapse
Dial ##scrtn# I'm on my second s8 plus both have same issue

The only way I've found that keeps the error from happening for me is to turn off location. Since then I haven't seen the error pop up.

njdan30 said:
Dial ##scrtn# I'm on my second s8 plus both have same issue
Click to expand...
Click to collapse
Already have, twice.

rockywall said:
Already have, twice.
Click to expand...
Click to collapse
Sucks it's just a temp fix I noticed after I use WiFi at home then goto service area I med to dial it every time on this over priced p.o.s. my s7 edge iPhone 6 plus and 5 other phones have zero issue just my s8 plus. They thought it was a defected antenna which I figured it wasn't, I tried dialing ##omadm# and changing to sprint development mode which phone wouldn't activate only in production mode would it work, also seems to only be the phone I got thru mail without a set msl this one is 000000 my other galaxies have sprint set msl

rockywall said:
Are you in an LTE-Plus area?
Click to expand...
Click to collapse
I am not sure how to tell if an area has LTE Plus, but I live in SW Virginia and went 3 hours away for a couple days to Richmond and had no issues. So, it's definitely the network in certain areas.
Sent from my SM-G950U using Tapatalk

mikeregister said:
I am not sure how to tell if an area has LTE Plus, but I live in SW Virginia and went 3 hours away for a couple days to Richmond and had no issues. So, it's definitely the network in certain areas.
Sent from my SM-G950U using Tapatalk
Click to expand...
Click to collapse
I am also in SW VA, and after speaking to a few stores, one mentioned that it has something to do with the nTelos merger. I have to use 3G from Roanoke to Danville on a daily basis. even though it is fairly solid LTE coverage.
If you look at Sprint's coverage map, LTE Plus is a darker color. Richmond and Norfolk/Hampton Roads area are Plus.

rockywall said:
I am also in SW VA, and after speaking to a few stores, one mentioned that it has something to do with the nTelos merger. I have to use 3G from Roanoke to Danville on a daily basis. even though it is fairly solid LTE coverage.
If you look at Sprint's coverage map, LTE Plus is a darker color. Richmond and Norfolk/Hampton Roads area are Plus.
Click to expand...
Click to collapse
I have assumed it was something to do with nTelos. I live in Roanoke and work in Christiansburg. The issue is in both places. Follow my instructions in my OP with the dialer code and your LTE will work fine, just have to do it anytime you restart your phone. No need to suffer on 3G.
Sent from my SM-G950U using Tapatalk

I doubt it has anything to do with nTelos. I live in Michigan and I get the same issue with my s8 plus and whatever nTelos is, we don't have it.

TheFugg said:
I doubt it has anything to do with nTelos. I live in Michigan and I get the same issue with my s8 plus and whatever nTelos is, we don't have it.
Click to expand...
Click to collapse
nTelos was a regional carrier in VA, WV, NC, OH, MD. They were purchased by another local company, Shentel, that operates under Sprint. They are not an MVNO though, they sell Sprint branded phones and service. And all the stores changed to Sprint branding. It could be a different regional carrier from your area, This merger happened a over a year ago and that is when we started getting LTE service. I think the merged network is not capable of dealing with HPUE. That is the common denominator with the G6 and S8.

Galaxy S8 plus and S8 same error
So if I understand all these comments correctly, there is still no resolution to this? I live in Huntington Wv and yes we did have nTelos. I have 2 S8+ and 1 S8 all get this error. I have a ticket in for the network team but I'm not holding my breath.

I am also having this issue. I've done ##72786# that seemed to fix it, but it's back. I change to CDME/LTE from automatic, and it still happens. I was about to do a factory reset. It's my only complaint with this device, otherwise I love it. I am in southwest PA. It seems to happen during cell tower hand offs like if I'm out driving. I just toggled data and the error went away.
Edit: I'm on the S8 Plus but I don't think that makes a difference.

Outatime67 said:
I am also having this issue. I've done ##72786# that seemed to fix it, but it's back. I change to CDME/LTE from automatic, and it still happens. I was about to do a factory reset. It's my only complaint with this device, otherwise I love it. I am in southwest PA. It seems to happen during cell tower hand offs like if I'm out driving. I just toggled data and the error went away.
Click to expand...
Click to collapse
On my phone it starts doing it again after doing the dialer code only once I restart the phone. Is this your problem?
Sent from my SM-G950U using Tapatalk

Question GSM issues, sudden disconnection?

Hey guys,
So I've received my P7P a couple days ago. Ordered in Romania from the official Amazon Store. 5G, VoLTE, and VoWiFi don't work, as you all know.
But the biggest problem I have is that the network just completely disconnects if I leave the phone on the desk for a couple minutes. I have people messaging me and asking why they can't call me. When I look at the phone, there's no GSM signal of any kind. This is in a location where I have full 5G coverage otherwise.
I had to go into airplane mode 2 times before I was able to receive a call. The first time it connected to LTE for a couple seconds and then it completely dropped again.
Not to mention it takes forever to connect again after going in an area with weak signal.
I've updated to the Beta and the issue persists.
Great software, great camera, whatever, all useless when you can't fulfill your main purpose of being A PHONE.
Anyone else with issues like this? This is all I've found: https://piunikaweb.com/2022/10/20/pixel-7-7-pro-no-network-or-no-service-connectivity-issue/

Does the phone have the LTE bands it needs to even work where you live? If not, then I doubt there will be anything you can do but return it and look to another OEM.

jaseman said:
Does the phone have the LTE bands it needs to even work where you live? If not, then I doubt there will be anything you can do but return it and look to another OEM.
Click to expand...
Click to collapse
oh LTE works well. 5G doesn't work.
It just gets disconnected from any kind of cellular network and gets no signal after a while.

Have you taken the day one OTA? That fixed the problem for most of us. I haven't seen any X or ! since the first day. Before that update I was having my connection drop every 10 minutes or so.
If you already have taken this update, you may have a defective model.

Try force stopping Carrier Services and Google Play Services and deleting the storage for both. That help me tremendously with connectivity issues with Pixel 6 Pro.
Might want to try Carrier Services beta as well.
Another thing to check is your APN settings. Make sure they're what your service provider recommends

I immediately updated before unlocking the bootloader and rooting, I don't have network outage or anything. 5G seems to be working as well, at least available in settings, I'm yet to test it in 5G area but where I live, there's no 5G actually so it would not bother me much anyways. I'm so far very happy with it