Related
I updated the PRL on my Note 3 using the dialer code. Ever since my phone won't connect to 4G LTE. I'm running Eclipse, not sure if that matters. Is there a way to get 4G back?
hehe i knew this would come in handy. Had the same happened to me. service menu 27663368378 > UE SETTING & INFO > SETTING > PROTOCOL > CDMA > EFS PROFILE > eHRPD PROFILE > SET TO VZW DEFAULT. Then restart. Problem should be fixed.
6d00z said:
hehe i knew this would come in handy. Had the same happened to me. service menu 27663368378 > UE SETTING & INFO > SETTING > PROTOCOL > CDMA > EFS PROFILE > eHRPD PROFILE > SET TO VZW DEFAULT. Then restart. Problem should be fixed.
Click to expand...
Click to collapse
Thanks for the suggestion, but the service menu doesn't work with the Eclipse ROM. The longer version of my problem is that I went on Vacation, and was getting poor reception. The coverage map seemed to indicate I should be getting better reception, so I tried to update my PRL. That is when I lost 4G completely. Upon arriving back home, I updated my PRL again while in an area I knew I usually got full bars of LTE. Now I get LTE, but it drops back to 3G after a few minutes if I'm not actively downloading anything. To get LTE back, I have to cycle airplane mode.
I may try to flash a rom that the service menu works with and try what you suggested when I find the time.
have you tried [APP][1.6+] CSC Changer + Refurbishment Check + Phone INFO
MongarEric said:
Thanks for the suggestion, but the service menu doesn't work with the Eclipse ROM. The longer version of my problem is that I went on Vacation, and was getting poor reception. The coverage map seemed to indicate I should be getting better reception, so I tried to update my PRL. That is when I lost 4G completely. Upon arriving back home, I updated my PRL again while in an area I knew I usually got full bars of LTE. Now I get LTE, but it drops back to 3G after a few minutes if I'm not actively downloading anything. To get LTE back, I have to cycle airplane mode.
I may try to flash a rom that the service menu works with and try what you suggested when I find the time.
Click to expand...
Click to collapse
heres link. free from playstore should work around the google dialer. http://forum.xda-developers.com/showthread.php?t=2609045
also the "activity launcher" app from the play store may help as well
Hehe i use that app to get inside the service menu. Since dialing the code doesnt work on the stock verizon rom. Served me well.
LordOfTrance said:
heres link. free from playstore should work around the google dialer. http://forum.xda-developers.com/showthread.php?t=2609045
also the "activity launcher" app from the play store may help as well
Click to expand...
Click to collapse
Nice!
I tried going back to the MJE modem, problem seemed to get worse. Went back to the NC4 modem and updated PRL, and LTE seems to be sticking now.
What procedure did you use to update the prl. Honestly prl update on their own so I dont know why you decided to do this
drewcam888 said:
What procedure did you use to update the prl. Honestly prl update on their own so I dont know why you decided to do this
Click to expand...
Click to collapse
I was on vacation in LA and was getting terrible signal wherever I went (coverage maps indicated I should have had a good signal most places). I figured it would be a quick thing to try. I dialed *228 to do it. I thought it was a long shot that it would fix anything, but I figured it couldn't hurt.
MongarEric said:
I was on vacation in LA and was getting terrible signal wherever I went (coverage maps indicated I should have had a good signal most places). I figured it would be a quick thing to try. I dialed *228 to do it. I thought it was a long shot that it would fix anything, but I figured it couldn't hurt.
Click to expand...
Click to collapse
*228 Should never be uaed on a 4G phone it could easily mess up your phone like it seemed to do. PRL are automatically pushed to 4G devices. I don't undwrstand how but you can supposedly ruin your sim card by doing it.
Interesting. I'll try swapping sim cards with my tablet. I'm traveling again, and LTE isn't working now that I'm in Atlanta. It was working this morning in DC. That service menu setting didn't seem to help.
I swapped sim cards with my tablet, and both devices had LTE. Did a speed test, and they both got above 15 Mbps. When I swapped the cards back, my phone once again failed to connect to LTE. I don't have any idea what information sim cards hold, but it seems weird that my phone sim card works fine in my tablet but not in the phone. I guess I'll be getting a new sim card.
MongarEric said:
I swapped sim cards with my tablet, and both devices had LTE. Did a speed test, and they both got above 15 Mbps. When I swapped the cards back, my phone once again failed to connect to LTE. I don't have any idea what information sim cards hold, but it seems weird that my phone sim card works fine in my tablet but not in the phone. I guess I'll be getting a new sim card.
Click to expand...
Click to collapse
Don't do *228 anymore also that way you save your sim card.
I'm still confused why the "bad" sim card works fine in my tablet.
My wife and I live up in the foothills of Colorado where there are no Sprint cell towers. There is one cell tower which our Sprint S7 edges can barely pick up that comes and goes and indicates that we are roaming. For a few seconds our phones might see it but then it will go away for minutes, then it will come back only to go away again ... etc. In any event, it was necessary to use Wifi calling when we are at my home. Prior to the Nougat upgrade everything was fine. As soon as we walked into the house our S7 edges would connect, Wifi calling would activate and would be functional. After the Nougat update we have discovered that Wifi calling no longer works unless we can also see that one roaming cell tower. Then Wifi calling turns on, stays on and we can make/receive calls. I emphasize that this behavior occurs with both our phones.
This problem makes all the Sprint stores basically useless. Since they are located where there are towers, Wifi calling works as expected. As a result Sprint has been absolutely no help. I am wondering if anybody else has had problems with Sprint Wifi calling when unable to see a cell tower? If so could you work around the problem? I am open to suggestions. I consider this a bug in the Spring S7 edge firmware.
BTW, I know that when I can make a call, Wifi calling is used because the pop-up "Congratulations you just made a Wifi call" appears. I purposedly have not turned that off to be sure I am not using that one roaming tower. What is interesting is that I only need to be able to see the "R" by the triangle showing cell tower strength (don't need any bars) and then the Wifi calling icon will turn on. At that point I can make a phone call and even if I lose the connection to that one cell tower (i.e. the "R" disappears) the Wifi call will remain active. I can go anywhere in my house and not drop the call. But once I hang up, the Wifi calling icon will gray out with a slash through it, the phone will indicate that there is no network and the phone can only make emergency calls.
If I cannot get a fix to this problem then I might just have to go back to the last Marshmallow firmware and block the update if possible.
just for the hell of it to check, I turned on airplane mode and left it for 5 mins, leaving it on turned wifi on, and wifi calling connected within a few seconds of wifi connecting. I am on the nougat update. I have absolutely no cell signal as that is turned off. I am able to make calls without a problem.
Reboot your phone into recovery and clear cache and try again.
also, you may want to check and make sure "smart switch" is turned off. it's under the connections > wifi > advanced > smart network switch. I haven't tested it, but in theory it might demand you be connected to a cellular network to work and be causing your problem.
nosympathy said:
just for the hell of it to check, I turned on airplane mode and left it for 5 mins, leaving it on turned wifi on, and wifi calling connected within a few seconds of wifi connecting. I am on the nougat update. I have absolutely no cell signal as that is turned off. I am able to make calls without a problem.
Reboot your phone into recovery and clear cache and try again.
also, you may want to check and make sure "smart switch" is turned off. it's under the connections > wifi > advanced > smart network switch. I haven't tested it, but in theory it might demand you be connected to a cellular network to work and be causing your problem.
Click to expand...
Click to collapse
Thanks for the suggestions. I tried several things. First I verified that I already had "smart switch" turned off. So I went ahead and turned it back on... no love with that feature either turned on or off. Second, I rebooted as you suggested into recovery and cleared the cache. That also did not fix the problem. Third I tried the same experiment as you and turned on airplane mode. I waited a bit (maybe not the same 5 minutes) and then turned on the Wifi and Wifi calling. Again no love. I even tried to make a call and the phone told me I had to turn off airplane mode. For whatever reason Wifi calling will only activate when the phone can see that one tower and starts roaming. At least I can use your experiment to demonstrate the problem at a Sprint store. I might just try using Odin to flash nougat and start clean and see if I cannot get this to work that way. I really don't want to go back to using the Airave although that was pretty reliable for me.
Paul Ganci said:
Thanks for the suggestions. I tried several things. First I verified that I already had "smart switch" turned off. So I went ahead and turned it back on... no love with that feature either turned on or off. Second, I rebooted as you suggested into recovery and cleared the cache. That also did not fix the problem. Third I tried the same experiment as you and turned on airplane mode. I waited a bit (maybe not the same 5 minutes) and then turned on the Wifi and Wifi calling. Again no love. I even tried to make a call and the phone told me I had to turn off airplane mode. For whatever reason Wifi calling will only activate when the phone can see that one tower and starts roaming. At least I can use your experiment to demonstrate the problem at a Sprint store. I might just try using Odin to flash nougat and start clean and see if I cannot get this to work that way. I really don't want to go back to using the Airave although that was pretty reliable for me.
Click to expand...
Click to collapse
So question is, if you go somewhere with signal and wifi you can connect too, turn on airplane mode, leave it on and turn wifi on, does wifi calling work. If not then for sure a reset is in order.
If it does work, then that just tells me the phone isn't really turning everything off with airplane mode on (which is lame) and sprint just goofed up the nougat update and you are the extremely small % that falls victim.
I haven't been able to get WiFi calling to work on my Edge since new. UNTIL I upgraded to Nougat. Now it seems to be working fine. Go figure.
nosympathy said:
So question is, if you go somewhere with signal and wifi you can connect too, turn on airplane mode, leave it on and turn wifi on, does wifi calling work. If not then for sure a reset is in order.
If it does work, then that just tells me the phone isn't really turning everything off with airplane mode on (which is lame) and sprint just goofed up the nougat update and you are the extremely small % that falls victim.
Click to expand...
Click to collapse
Okay some interesting data. I did exactly this experiment this morning. I drove into my office, connected up to the office WiFi and placed my phone into airplane mode. I then turned on WiFi and WiFi calling. Voila I could make a WiFi call!
However I did not stop there. One of the keys to all this is that the one tower happens to cause "roaming" if my phone was lucky enough to connect to it. So for grins I changed the network mode from automatic to LTE/CDMA (Sprint & Verizon are CDMA). When I was back at the house guess what... WiFi calling now works. Interestingly the phone is in "searching for service" mode which implies that the one cell tower seen from my house is either AT&T or T-Mobile which use GSM. By turning off automatic mode everything worked.
It is kind of a bummer but what seems to fix the issue is to choose Connections->Mobile networks->Network mode->LTE/CDMA. Each time a switch is made from Connections->Mobile networks->Network mode->Automatic back to Connections->Mobile networks->Network mode->LTE/CDMA, etc. the phone has to be rebooted. Unfortunately while traveling in a car Automatic mode is desired and at the house LTE/CDMA is best. Switching back and forth will be a PITA because of the reboot but at least I don't have to go back to the Airave.
I tried to explain this to the Sprint rep. on the phone this evening but he did not understand. Over the weekend I might try a clean install via Odin and see if that improves things. I hate doing that because it takes a fair amount of time to put the phone apps back together. I also have my doubts it will fix anything. IMO something broke with the Nougat upgrade and nothing I do will fix it. And as you point out, I am in that very tiny percentage of people who might actually experience an issue.
Paul Ganci said:
Okay some interesting data. I did exactly this experiment this morning. I drove into my office, connected up to the office WiFi and placed my phone into airplane mode. I then turned on WiFi and WiFi calling. Voila I could make a WiFi call!
However I did not stop there. One of the keys to all this is that the one tower happens to cause "roaming" if my phone was lucky enough to connect to it. So for grins I changed the network mode from automatic to LTE/CDMA (Sprint & Verizon are CDMA). When I was back at the house guess what... WiFi calling now works. Interestingly the phone is in "searching for service" mode which implies that the one cell tower seen from my house is either AT&T or T-Mobile which use GSM. By turning off automatic mode everything worked.
It is kind of a bummer but what seems to fix the issue is to choose Connections->Mobile networks->Network mode->LTE/CDMA. Each time a switch is made from Connections->Mobile networks->Network mode->Automatic back to Connections->Mobile networks->Network mode->LTE/CDMA, etc. the phone has to be rebooted. Unfortunately while traveling in a car Automatic mode is desired and at the house LTE/CDMA is best. Switching back and forth will be a PITA because of the reboot but at least I don't have to go back to the Airave.
I tried to explain this to the Sprint rep. on the phone this evening but he did not understand. Over the weekend I might try a clean install via Odin and see if that improves things. I hate doing that because it takes a fair amount of time to put the phone apps back together. I also have my doubts it will fix anything. IMO something broke with the Nougat upgrade and nothing I do will fix it. And as you point out, I am in that very tiny percentage of people who might actually experience an issue.
Click to expand...
Click to collapse
Just out of curiosity have you tried turning your roaming off? Or adjust the settings to not connect?
Sent from Uranus, the only planet with a ring on the inside
izzibew26 said:
Just out of curiosity have you tried turning your roaming off? Or adjust the settings to not connect?
Sent from Uranus, the only planet with a ring on the inside
Click to expand...
Click to collapse
Thanks for the idea.
So while my wife and I were having lunch in town this afternoon, I took our phones and toggled LTE/CDMA and Automatic modes. When we arrived at the house with the phones in Automatic mode WiFi calling worked. I think as long as the phones do not roam and connect to that GSM cell tower, WiFi calling seems to work. So I put both our phones into Home only mode (Settings->Connections->Mobile networks->Data roaming->Roaming network->Home only). So far so good. Both our phones have had WiFi calling activated now for several hours so I think the strategy works. Turning roaming on and off is not as painful as changing the network mode. Still the Nougat behavior is very different, I dare say, broken from Marshmallow behavior.
Paul Ganci said:
Thanks for the idea.
So while my wife and I were having lunch in town this afternoon, I took our phones and toggled LTE/CDMA and Automatic modes. When we arrived at the house with the phones in Automatic mode WiFi calling worked. I think as long as the phones do not roam and connect to that GSM cell tower, WiFi calling seems to work. So I put both our phones into Home only mode (Settings->Connections->Mobile networks->Data roaming->Roaming network->Home only). So far so good. Both our phones have had WiFi calling activated now for several hours so I think the strategy works. Turning roaming on and off is not as painful as changing the network mode. Still the Nougat behavior is very different, I dare say, broken from Marshmallow behavior.
Click to expand...
Click to collapse
It's weird and I would bet money something they accidentally broke and such odd and perfect conditions have to be met to make it present itself, they probably had no idea. The sad thing is, this bug probably affects so few people, and most will probably not be tech people and will just get frustrated and switch carriers, and so the bug probably won't ever get fixed, except by accident possibly.
On a side note have you tried changing your location settings to GPS only. If you have it set for a method that looks for towers that might be the issue right there. GPS-LOCATING METHOD-DEVICE ONLY.
Sent from Uranus, the only planet with a ring on the inside
Greyed out apn settings
Need help I rooted my s7 edge sm-g935p sprint it is updated to the latest update and I have my msl code but can not access my apn settings they are greyed out even if I dial data and try to access it that way please help
..
izzibew26 said:
Wrong thread. Right section, wrong thread. There are 2 ways. I'm assuming you're attempting hotspot bypass
Sent from Uranus, the only planet with a ring on the inside
Click to expand...
Click to collapse
Sorry about that can you hook me up with the thread
YES I am trying to bypass have wifi sharing app but tends to make the rooted phone lag
...
I just tried the experiment. That did not work and in fact broke WiFi calling. So far the only solution is to toggle the LTE/CDMA and Automatic network modes where there is a Sprint tower preferably and then turn off roaming as I drive up to the house. Then WiFi calling works without issue. Nice thought though.
Sent from my SM-G935P using XDA-Developers Legacy app
Paul Ganci said:
I just tried the experiment. That did not work and in fact broke WiFi calling. So far the only solution is to toggle the LTE/CDMA and Automatic network modes where there is a Sprint tower preferably and then turn off roaming as I drive up to the house. Then WiFi calling works without issue. Nice thought though.
Sent from my SM-G935P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Okay so things get even worse. Today I drove up to the house with roaming turned off and network mode automatic. After parking the car and walking to the end of the driveway to retrieve my garabage can, not only did WiFi calling fail to activate but I could not turn roaming back on. The Settings->Connections->Mobile networks->Data roaming->Roaming network menu is greyed out. IMO, Sprint has hosed up their edition of Nougat. So I will be left with a brick as a phone while I am up here at 8400' at my house. I am quite pissed.
FWIW, what I think happened is I walked to the end of my driveway and lost my WiFi connection. That caused WiFi calling to shut off and now it will not turn back on. At least if I could get roaming turned back on I could try and connect up to that one lonely GSM tower to possibly fix this issue. But I cannot even do that because the Roaming network menu is greyed out. I am going to have to drive into town just to fix this problem. Ugh!
Paul Ganci said:
Okay so things get even worse. Today I drove up to the house with roaming turned off and network mode automatic. After parking the car and walking to the end of the driveway to retrieve my garabage can, not only did WiFi calling fail to activate but I could not turn roaming back on. The Settings->Connections->Mobile networks->Data roaming->Roaming network menu is greyed out. IMO, Sprint has hosed up their edition of Nougat. So I will be left with a brick as a phone while I am up here at 8400' at my house. I am quite pissed.
FWIW, what I think happened is I walked to the end of my driveway and lost my WiFi connection. That caused WiFi calling to shut off and now it will not turn back on. At least if I could get roaming turned back on I could try and connect up to that one lonely GSM tower to possibly fix this issue. But I cannot even do that because the Roaming network menu is greyed out. I am going to have to drive into town just to fix this problem. Ugh!
Click to expand...
Click to collapse
try ##72786# in your dialer
Paul Ganci said:
Okay so things get even worse. Today I drove up to the house with roaming turned off and network mode automatic. After parking the car and walking to the end of the driveway to retrieve my garabage can, not only did WiFi calling fail to activate but I could not turn roaming back on. The Settings->Connections->Mobile networks->Data roaming->Roaming network menu is greyed out. IMO, Sprint has hosed up their edition of Nougat. So I will be left with a brick as a phone while I am up here at 8400' at my house. I am quite pissed.
FWIW, what I think happened is I walked to the end of my driveway and lost my WiFi connection. That caused WiFi calling to shut off and now it will not turn back on. At least if I could get roaming turned back on I could try and connect up to that one lonely GSM tower to possibly fix this issue. But I cannot even do that because the Roaming network menu is greyed out. I am going to have to drive into town just to fix this problem. Ugh!
Click to expand...
Click to collapse
Found the fix... Updated the PRL & Profile. I guess the phone lost its mind and could not find it once the WiFi was dropped.
Many retail mobiles have "Wifi Calling" function but not any menu entry to enable , The APP can check the hidden function and enable it if can use.
https://play.google.com/store/apps/details?id=com.widget7.wifi.calling
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:
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.
On Sprint's Network, unlocked bootloader & critical partitions. Anytime I even receive a notification for a phone call coming in, my LTE is dropped instantly. Deny or hang up the call, it comes back. I've read that Sprint's 3G can't handle voice and data at the same time, but this is 4G. Wifi is also completely useless on this phone as it stays connected for about 60 seconds tops.
Tried doing a complete wipe and reset to both Pie stable and Q beta 6, same exact thing. Tried all the network options in settings and nothing.
Does anyone with Sprint have working LTE during a phone call? I'm trying to figure out if it's a **** copy I got from Amazon, or the network. Thanks.
xe500linux said:
On Sprint's Network, unlocked bootloader & critical partitions. Anytime I even receive a notification for a phone call coming in, my LTE is dropped instantly. Deny or hang up the call, it comes back. I've read that Sprint's 3G can't handle voice and data at the same time, but this is 4G. Wifi is also completely useless on this phone as it stays connected for about 60 seconds tops.
Tried doing a complete wipe and reset to both Pie stable and Q beta 6, same exact thing. Tried all the network options in settings and nothing.
Does anyone with Sprint have working LTE during a phone call? I'm trying to figure out if it's a **** copy I got from Amazon, or the network. Thanks.
Click to expand...
Click to collapse
I have the issue. I also can't get LTE+ to work either. I'm on Boost, but they use Sprint. All stock roms and I can't get 4G at all on custom roms. I bought mine directly from Essential.
Sent from my PH-1 using Tapatalk
Sheradrax said:
I have the issue. I also can't get LTE+ to work either. I'm on Boost, but they use Sprint. All stock roms and I can't get 4G at all on custom roms. I bought mine directly from Essential.
Click to expand...
Click to collapse
I can't say anything about Sprint, but VoLte on Verizon behaves the same way for me on Q beta 6. If the radio cycles for any reason I lose VoLte even if it shows selected. I have to toggle it in network settings for it to work.
Just curious, if you go into the phone info with *#*#4636#*#*, does it show that VoLte is provisioned?
garywojdan81 said:
I can't say anything about Sprint, but VoLte on Verizon behaves the same way for me on Q beta 6. If the radio cycles for any reason I lose VoLte even if it shows selected. I have to toggle it in network settings for it to work.
Just curious, if you go into the phone info with *#*#4636#*#*, does it show that VoLte is provisioned?
Click to expand...
Click to collapse
It's grayed out for me. I can't enable it. Maybe calling Boost customer service might result in fixing it.
Sent from my PH-1 using Tapatalk