Database Users

3G Data Not Working

Problem has been resolved. See my final post in this thread.
Long time lurker. First time poster.
I am having problems getting 3G data on my new phone.
Last week I activated a new Moto X Pure Edition on the Sprint network via MVNO Ting. The phone appeared to activate just fine. Voice, text, LTE, Wi-Fi, and 1x data are all working without any obvious issues. Phone is pure stock.
3G data is not working. If I set Preferred Network Type to "LTE (recommended)", mobile data works on LTE but if I travel to an area that has not yet been upgraded to LTE, it will not drop back to 3G. Further, if I choose 3G as the Preferred Network Type regardless of whether the phone is connected to an LTE tower or a non-LTE tower, I get no data connection. Same for Global - no 3G connection.
If I choose "1x" as the Preferred Network Type (whether in an LTE area or not) then the phone will establish a data connection. The phone reports this connection as 3G in the status bar but the speed is so unusable that I doubt it can be a 3G connection.
I've done a carrier wipe, updated the device config (profile) and updated the PRL, all several times. Nothing changed. I've also done a factory reset which also did not help. I did not have any issues with my Nexus 5 which the MXPE replaced. I have since reactivated the Nexus 5 with a new number while troubleshooting this problem and it reactivated just fine. No issues at all.
Questions:
1) SignalCheck Pro reports that mobile data is "unregistered" when trying to get 3G data. Is registration of 3G data tied to the SIM card or to the MEID of the phone? Trying to determine if the registration problem lies with the SIM, the phone, or the network.
2) Why would I be able to get a 1x data connection but not 3G?
3) Ting is suggesting network problems may be playing a part but I'm not sure as the problem has persisted through several cities around west Texas and eastern New Mexico and throughout Lubbock TX which has many cell towers. Is there any way this could be a network issue?
4) Is the SIM for the MXPE compatible with my old Nexus 5? I'm wondering if swapping the SIM into my N5 will help to diagnose the problem.
5) Is anyone else with a MXPE having issues with 3G data?
This one is puzzling and I need some help from the gurus. Thanks much.
DC

Bump.

Swapped SIMS with one sent by Ting to verify the problem wasn't with the SIM. Still no 3G.
DC

DC73 said:
Long time lurker. First time poster.
I am having problems getting 3G data on my new phone.
Last week I activated a new Moto X Pure Edition on the Sprint network via MVNO Ting. The phone appeared to activate just fine. Voice, text, LTE, Wi-Fi, and 1x data are all working without any obvious issues. Phone is pure stock.
3G data is not working. If I set Preferred Network Type to "LTE (recommended)", mobile data works on LTE but if I travel to an area that has not yet been upgraded to LTE, it will not drop back to 3G. Further, if I choose 3G as the Preferred Network Type regardless of whether the phone is connected to an LTE tower or a non-LTE tower, I get no data connection. Same for Global - no 3G connection.
If I choose "1x" as the Preferred Network Type (whether in an LTE area or not) then the phone will establish a data connection. The phone reports this connection as 3G in the status bar but the speed is so unusable that I doubt it can be a 3G connection.
I've done a carrier wipe, updated the device config (profile) and updated the PRL, all several times. Nothing changed. I've also done a factory reset which also did not help. I did not have any issues with my Nexus 5 which the MXPE replaced. I have since reactivated the Nexus 5 with a new number while troubleshooting this problem and it reactivated just fine. No issues at all.
Questions:
1) SignalCheck Pro reports that mobile data is "unregistered" when trying to get 3G data. Is registration of 3G data tied to the SIM card or to the MEID of the phone? Trying to determine if the registration problem lies with the SIM, the phone, or the network.
2) Why would I be able to get a 1x data connection but not 3G?
3) Ting is suggesting network problems may be playing a part but I'm not sure as the problem has persisted through several cities around west Texas and eastern New Mexico and throughout Lubbock TX which has many cell towers. Is there any way this could be a network issue?
4) Is the SIM for the MXPE compatible with my old Nexus 5? I'm wondering if swapping the SIM into my N5 will help to diagnose the problem.
5) Is anyone else with a MXPE having issues with 3G data?
This one is puzzling and I need some help from the gurus. Thanks much.
DC
Click to expand...
Click to collapse
Yes..i am having the same issue..with vodafone in india

Update. After two Moto X PE phones, numerous factory resets, much research and testing, there is now a work around to this problem. The problem does not appear to impact any phones on the big 4 networks. It only impacts phones on a Sprint MVNO.
There are now known eHRPD issues with Sprint and their MVNOs. The work around solution is to disable eHRPD. Sprint is working on changes to eHRPD that may resolve the issue permanently. Thanks to Ting for their persistence in helping get to the bottom of this problem.
DC

Final update. Earlier this month Sprint released some changes to the way eHRPD handoffs are handled and that resolved my issue. My Moto X PE now works as it should with no workarounds necessary to get 3G data.
DC

DC73 said:
Final update. Earlier this month Sprint released some changes to the way eHRPD handoffs are handled and that resolved my issue. My Moto X PE now works as it should with no workarounds necessary to get 3G data.
DC
Click to expand...
Click to collapse
How to get this update?

Sekasniy said:
How to get this update?
Click to expand...
Click to collapse
There was no update pushed to the phone and no changes to the phone. The fix was on the network side.
DC

DC73 said:
There was no update pushed to the phone and no changes to the phone. The fix was on the network side.
DC
Click to expand...
Click to collapse
So why not work 3g? Is the problem in cell operator?

^^Sprint had some issues with 3g (ehrpd) on mvno's. It would work if forced to evdo, but not ehrpd. Sprint made some changes to their network so this now works correctly. It was a network side issue.

Roaming on VZW after CM13

When I first started using CM13 my signal went to roaming when I know I should have service. I have data roaming off and I've checked to make sure I'm not getting charged for roaming and I'm not. My phone works as it should and I can do everything I need still so I was hoping it would be fixed in one of the new updates. I am on the newest nightly build as of this morning and the R above my signal is still there, just wondering if anyone else is having this problem or know the cause?

I have the same issue on my Nexus 6

Same issue here. Nexus 6 Verizon, just switched to CM13 and I'm stuck on roaming - so far I've tried airplane mode for a minute or two, turning the data off and on, turning the phone off and on, and chatting with Verizon support in case they could do anything remotely. The one thing I haven't done though is try putting another sim card into my phone to see if I could divine any information that way.
Any help would be appreciated.

So after trying just about everything I decided to cave in and jump back to CM12. It was there that I noticed a key difference:
CM12's settings -> mobile network settings, has the following sub-options:
Data Roaming on/off
Preferred Network Type
Enhanced 4G LTE Mode on/off
System select
Access Point Names
CM13 (nightly #2) only has:
Data Roaming
Preferred Network Type
System Select
...while in all honesty I don't know what it all means except to say that it appears to be missing some features of the CM12 nightly I'm using on my Nexus 6 on Verizon. I guess I'll try back in a week or three to see if everything is working fine.

For whatever reason I had LTE pop up for like 2 seconds but went back to R and has stayed since..

Cell service won't connect when roaming with Lineage OS on Sprint, works with stock

This is a Galaxy S5 on the Sprint Network with Lineage OS version from a few weeks ago.
Last week this was working fine and then since Sunday cell service stopped working completely. The only change I did was updating TWRP, I did not update LineageOS, but I can't imagine TWRP would have affected it. I ended up reverting back to the stock ROM thinking I would have to call Srpint customer service, but then it started working under the stock ROM. Reflashed TWRP and Lineage OS and no service. Tried older and newest versions of TWRP and Lineage OS but nothing works except stock ROM (yuck).
The cellular connection says "no service" with completely empty bars. About every 5 seconds it will flash like it is connected, with most bars and the little R for roaming, then immediately goes back to "no service". I've tried changing preferred networks and looked at settings but can't find anything to fix it.
Any ideas? It's almost like the network is rejecting it but I don't see why it would matter if it is a custom ROM.
EDIT: oh yeah and on start up it says "Activating cellular service... This may take up to 5 minutes" or and then after a while says "Couldn't Activate" and that it may be fixed by restarting the phone (which of course doesn't fix it). Also I'm not entirely sure if it is related to roaming or not.
EDIT2: I'm wondering/betting this has something to do with the ICCID number. I noticed with Lineage OS installed it says "DUMMY_NV_ICC_SERIAL" but with the stock ROM it is a long string of digits. Now maybe I can change the ICCID on Lineage OS? Or maybe Lineage OS isn't reading my sim card properly (from googling what ICCID is)?

Did you ever figure this out? I have the same issue. Until the most recent build, I was forcing the phone down to 3G because of the SMS bug, but now that I have it set to use LTE, it won't connect (even to fallback, I don't care about getting LTE, I would just like not to miss calls/texts because I do have voice roaming).

Firstly, check the baseband, if it's the newest. Sometimes this causes the problem. If this doesn't help, then only the ROM is the actual problem.

bussemac said:
Did you ever figure this out? I have the same issue. Until the most recent build, I was forcing the phone down to 3G because of the SMS bug, but now that I have it set to use LTE, it won't connect (even to fallback, I don't care about getting LTE, I would just like not to miss calls/texts because I do have voice roaming).
Click to expand...
Click to collapse
I did not figure it out. I went back to my home area, re-installed LineageOS and then it activated on the Sprint network fine. But I suspect if I was in roaming again it would still not work if I did a factory reset or an update while in roaming. So I guess the only "solution" I've found is to be on a home network, let the phone activate, and then you can go back to roaming area. Not much of a solution if you are not near a home area.

I use https://forum.xda-developers.com/xposed/modules/app-roaming-control-v1-0-t3267154 to re-enable national roaming.
Also had some problems getting the modul work. I had to enable modul by toggle flight mod. Also i still have to enable roaming befor i switch from wifi to data connection then i can turn roaming (international) in system off and national roaming still works.
Maybe you have to do so :fingers-crossed:

No Lte connection

Hi everyone
So I've had the mi a1 for a couple of days and so far have not been able to connect to lte network. 3g is working. Apn is set and configured correctly. This is in areas where my Redmi 4x, previous note 4x and all other devices connect to lte networks (same sim card obviously). I have the global version and have immediately installed the September update after setting up the device. I suppose no-one else has issues with lte, otherwise I would have found a thread about it? Are there any suggestions what I can do to find out what the problem is? I tried an app to force lte only but it doesn't connect to a network when set to lte only.

Nevermind. Restarting and cycling through 2g/3g/4g options in mobile network menu resulted in 4g connecting. Still a bit odd though as I'd cycled 3g/4g before and only connecting to 3g signal. Restarted once after the update as well.

Emergency calls only/LTE data, or voice and limited to 3G data? Sprint

I had my phone running PureNexus(7.1.2?) on Cricket with no issues, a couple days ago at the same time as switching to Sprint, I decided to update my ROM, went with a 8.1 ROM. When I did this, I had issues getting any sort of signal to work right, so I figured it was something with the custom ROM, grabbed the latest stock and reflashed. I then went through the same thing many others have here, but when I go back to the custom 8.1 ROM, I do not get LTE to connect, just 3G. Even erasing modemst1 and 2, it does not connect to LTE. So, ignoring that, I still backed up the EFS and restored it over the stock ROM. Doing this, I'm able to get 3G and voice to connect, but when I go into the phone menu(*#*#4636*#*#) and turn the radio off then back on, eventually it will connect to LTE. But in doing so, it puts the phone in 'emergency calls only' for voice. Currently it shows
Voice Service: In Service
Data Service: Connected
Voice Network Type: 1xRTT
Data Network Type: eHRPD
And if I go into the menu and toggle the Mobile Radio Power, it will change to:
Voice Service: Emergency Calls Only
Data Service: Connected
Voice Network Type: Unknown
Data Network Type: LTE
Once it goes to LTE, it does not go back to voice/3G even on reboot unless I erase the modem or restore an EFS backup. I've been able to replicate this 3 times now in 3 different 7.1.2 ROMs, anything 8.1 I've only been able to get 3G working. In 7.1.2 I am able to run the update device configuration, and update PRL. Both work successfully, but it still does the same thing. At this point, I know that the hardware works, as both do work fine, just not at the same time. LTE and voice does still work fine on Cricket, I put in another active SIM and both work as expected. Anyone know what else I could try?
Sorry if this is rambling, I actually had a much more detailed post then somehow refreshed my screen and lost it all

I'm essentially having the same issue with my Moto g5 plus on Verizon. Read my post!

I am having a similar issue on Sprint as well. For a little while I couldn't get 8.1 ROMs to connect to data at all, after serial flashing a bunch of them I ended up with data again accross all ROMs but now I only have LTE, it does not switch to 3 g ever, only 1x when making phone calls. I wish I knew which ROMs I flashed to get to this point but I can't remember anymore. Good luck.

emraith said:
I had my phone running PureNexus(7.1.2?) on Cricket with no issues, a couple days ago at the same time as switching to Sprint, I decided to update my ROM, went with a 8.1 ROM. When I did this, I had issues getting any sort of signal to work right, so I figured it was something with the custom ROM, grabbed the latest stock and reflashed. I then went through the same thing many others have here, but when I go back to the custom 8.1 ROM, I do not get LTE to connect, just 3G. Even erasing modemst1 and 2, it does not connect to LTE. So, ignoring that, I still backed up the EFS and restored it over the stock ROM. Doing this, I'm able to get 3G and voice to connect, but when I go into the phone menu(*#*#4636*#*#) and turn the radio off then back on, eventually it will connect to LTE. But in doing so, it puts the phone in 'emergency calls only' for voice. Currently it shows
Voice Service: In Service
Data Service: Connected
Voice Network Type: 1xRTT
Data Network Type: eHRPD
And if I go into the menu and toggle the Mobile Radio Power, it will change to:
Voice Service: Emergency Calls Only
Data Service: Connected
Voice Network Type: Unknown
Data Network Type: LTE
Once it goes to LTE, it does not go back to voice/3G even on reboot unless I erase the modem or restore an EFS backup. I've been able to replicate this 3 times now in 3 different 7.1.2 ROMs, anything 8.1 I've only been able to get 3G working. In 7.1.2 I am able to run the update device configuration, and update PRL. Both work successfully, but it still does the same thing. At this point, I know that the hardware works, as both do work fine, just not at the same time. LTE and voice does still work fine on Cricket, I put in another active SIM and both work as expected. Anyone know what else I could try?
Sorry if this is rambling, I actually had a much more detailed post then somehow refreshed my screen and lost it all
Click to expand...
Click to collapse
Your problem is really simular to mine, but I have an axon 7 and the service is Total wireless (verizon). I can get data and calls are emergency only. Its very odd, the other odd thing is I have 2 axon 7 (got a replacement). The one with the problem has everything working and the kicker is I restored this replacement to match the working one. So why It cant connect is really odd.

madhits45 said:
Your problem is really simular to mine, but I have an axon 7 and the service is Total wireless (verizon). I can get data and calls are emergency only. Its very odd, the other odd thing is I have 2 axon 7 (got a replacement). The one with the problem has everything working and the kicker is I restored this replacement to match the working one. So why It cant connect is really odd.
Click to expand...
Click to collapse
How is this similar? You are trying to use an Axon 7 on Verizon's network... How do you expect that to work? The Axon 7 doesn't have a CDMA radio.

acejavelin said:
How is this similar? You are trying to use an Axon 7 on Verizon's network... How do you expect that to work? The Axon 7 doesn't have a CDMA radio.
Click to expand...
Click to collapse
Yes it does have CDMA. Its just not officially supported by verizon. I found out that my modem partition I believe EFS was messed up and that contributed to the emergency calls only issue. I never got it fixed even through multiple re-flashes so I simply sent it back to ZTE.

madhits45 said:
Yes it does have CDMA. Its just not officially supported by verizon. I found out that my modem partition I believe EFS was messed up and that contributed to the emergency calls only issue. I never got it fixed even through multiple re-flashes so I simply sent it back to ZTE.
Click to expand...
Click to collapse
I stand corrected... I assume you have seen this, especially post #3?

acejavelin said:
I stand corrected... I assume you have seen this, especially post #3?
Click to expand...
Click to collapse
I have read that thanks for pointing it out. I actually could offer a correction to what he says because you can get VoLTE on the axon7 with verizon but its tricky. I had to activate the phone on an HD voice 1.0 phone iphone 6 or newer and prob other models. I have total wireless (verizon Mvno) once I do that I can swap the sim and get VoLTE on the axon7 through turning it on in test mode. Ive had volte working for a while now. I believe verizon just thinks Im on the iphone6. and I dont know what would happen if I took the iphone 6 and tried to use it on another verizon account as my service is prob tied to its IMEI.