Database Users

Have to reboot after disconnected to Mobilicty to reconnect

I'm located in Toronto, Canada and recently subscribed to Mobilicity.
I recently got a T-Mobile samsung vibrant and I'm having this problem where if I lose my mobilicity connection (ie in the subway) I have to reboot the phone to get the connection back.
If I don't reboot the phone will not reconnect to mobilicity network.
Is there a network setting I need to do to get it to connect automatically whenver I get disconnected? Or maybe there's a fix for this somewhere?
The vibrant is not rooted and has stock apps right now.

salvador3 said:
I'm located in Toronto, Canada and recently subscribed to Mobilicity.
I recently got a T-Mobile samsung vibrant and I'm having this problem where if I lose my mobilicity connection (ie in the subway) I have to reboot the phone to get the connection back.
If I don't reboot the phone will not reconnect to mobilicity network.
Is there a network setting I need to do to get it to connect automatically whenver I get disconnected? Or maybe there's a fix for this somewhere?
The vibrant is not rooted and has stock apps right now.
Click to expand...
Click to collapse
I would suggest turning the radio off ( airplane mode ) and then turning it back on, this should force your phone to reconnect to mobilicity. It would be considerabbly faster and more convienent than rebooting your phone entirely... The fastest way to turn off the radio is to press and hold the power button until the power options menu pops up and hit the airplane mode selection.
Let me know if this works for you.

Frizzmmm said:
I would suggest turning the radio off ( airplane mode ) and then turning it back on, this should force your phone to reconnect to mobilicity. It would be considerabbly faster and more convienent than rebooting your phone entirely... The fastest way to turn off the radio is to press and hold the power button until the power options menu pops up and hit the airplane mode selection.
Let me know if this works for you.
Click to expand...
Click to collapse
Thanks for your reply.
I've tried this with mixed results. Sometimes I would be able to connect to mobi's network sometimes it doesn't. If it does connect, it's only for voice and not 3G.
I've also tried manually selecting the network. It takes a minute or so to search networks and then sometimes mobi's network doesn't even appear.
Rebooting it works everytime though so there's something amiss going on here.

I tried a few things:
Coming out of subway (prolonged disconnect): The vibrant gets stuck in "Searching" mode. It does not lock into Mobi's network at even after turning on/off the airplane mode (turns off all wireless). The only way I get connected back is to power off the phone.
Coming out of basement or elevator (intermitent disconnect): I tend to lose my 3G connection when this happens. Power on/off restablishes the 3g connection. I get mixed results with the airplane mode being toggled on/off.
So right now my settings are:
- WCMDA Only in both the Mobile Network settings and the testing menu (*#*#4636#*#*)
- Manual network connection to Mobilicity
Still getting disconnects anybody with other suggestions?
thanks

Does anyone have a solution to this problem? It seems to be only happening with the mobilicty SIm card. SOMEONE HELP!!

I'm having the same problem. Is it a network problem or a phone problem? I'm using T-Mobile Galaxy S Vibrant and Mobilicity. Let me know if you guys have the solution. Thanks.

masterguapo said:
I'm having the same problem. Is it a network problem or a phone problem? I'm using T-Mobile Galaxy S Vibrant and Mobilicity. Let me know if you guys have the solution. Thanks.
Click to expand...
Click to collapse
Looking for input on this as well please.

I have vibrant on mobilicity as well, had this problem on stock JFD, flashed to any froyo roms and didn't have this problem again (currently using macnut R12 + EB stock kernel)

o NICE... its all in the radio... thanx so much... i'm going to install the JK6 custom rom.... hopefully that has the fix as well...

I am actually re locating to Toronto for work so that is good to know.
Out of curisosity, I actually just purcahsed my phone and I am unlocking it at this moment. Do you know if you have to have a sim card inside the phone while inlocking? Or just after to get the key? Thanks!! I see to be having problem running the script, so I was just wondering.

Not longer seeing telus

Hi All,
Not quite sure what happened here.. Upgraded to latest nscollab yesterday, everything was working fine. Decided to try the "Antennas" app to see if it'd show where the towers are near me, switched to 2g mode, played around with it a bit, switched off 2g mode and now my phone does not see telus at all. When I go into search networks, telus simply doesn't show up and my phone stays in emergency mode.
It sees rogers fine and is able to connect to rogers with a friend's rogers sim. I've tried my telus im in other phones and it works fine, other people's telus sims in my phone don't work either.
I've tried reverting to an earlier backup as well as going back to a stock backup. I've also tried reflashing both the kb1 and kb3 radios, no luck.
Anyone know what might be the issue here?

both Telus / Bell do not have 2G
they only have 3G, as in the VOICE only works via 3G
it was the same using the SGS i9000

Did the rogers SIM work on 2G (Edge) only? I am guessing Rogers and Fido will work, but only on 2G
Same happened to me, on Fido, my phone could no longer connect to 3G...Only 2G after playing with settings. I returned the phone
The reason why Telus-Bell SIM would not work at all at this point is that they only support 3G...

That makes sense, but i don't have it set to 2g mode anymore. It should be seeing 3g just fine.

5h4d0w said:
That makes sense, but i don't have it set to 2g mode anymore. It should be seeing 3g just fine.
Click to expand...
Click to collapse
maybe try to do a factory reset default?
in settings > privacy > format

AllGamer said:
maybe try to do a factory reset default?
in settings > privacy > format
Click to expand...
Click to collapse
Just tried that, nothing. I think that's the same as a wipe data in recovery?
I've tried:
- Reverting back to a stock backup
- Reverting to an earlier working backup
- Doing a factory reset on both of the above
- Reflashing the radio on both

5h4d0w said:
Hi All,
Not quite sure what happened here.. Upgraded to latest nscollab yesterday, everything was working fine. Decided to try the "Antennas" app to see if it'd show where the towers are near me, switched to 2g mode, played around with it a bit, switched off 2g mode and now my phone does not see telus at all. When I go into search networks, telus simply doesn't show up and my phone stays in emergency mode.
It sees rogers fine and is able to connect to rogers with a friend's rogers sim. I've tried my telus im in other phones and it works fine, other people's telus sims in my phone don't work either.
I've tried reverting to an earlier backup as well as going back to a stock backup. I've also tried reflashing both the kb1 and kb3 radios, no luck.
Anyone know what might be the issue here?
Click to expand...
Click to collapse
This just happened to me, I switched to 2G and got nothing but com.android.phone quit errors, now I can't get back on 3G. Flashed radios, data wipe, everything... wtf... it's back to stock now and still can't get on Telus... double wtf...

Christ... finally got it... my head hurts from all this reading
For some reason it was on the wrong band. Do this in dialer... *#*#4636#*#*, phone information, menu, select radio-band, USA, and should work make sure its on WCDMA preferred as well under phone information

KryPTiCk0d3 said:
Christ... finally got it... my head hurts from all this reading
For some reason it was on the wrong band. Do this in dialer... *#*#4636#*#*, phone information, menu, select radio-band, USA, and should work make sure its on WCDMA preferred as well under phone information
Click to expand...
Click to collapse
I had the same issue when in Canada, and forgot I had the band set to Europe (my region).
I set it to Automatic detect, i know catching signal will take longer. But then I dont forget
Sent from my Nexus S using XDA App

i had the same problem since may 14th (sat), thanks for the fix!!!!!!!

Same thing happened here, same solution. Glad you stumbled on it too!
As the title says, had the same problem on my Nexus S (running on Bell), I believe manually switching the 2g/3g toggle in cyanogenmod rom accidentally is what set it off.
Glad you found the solution!! Was maddening for me; knew there must be a way to fix through the UI, but until I fond it, phone was a wifi mp3 player :/

Roaming and EG22

Anyone having any luck with Roam Control on EG22? I'm running the EG22 w/ EG22 modem. Everything looks to be working fine except for one huge glaring problem...roaming. I have all the roam guard nonsense turned off. I hit Roaming Only, I get the little triangle and even see it in the debug connected to VZW but I never get any data connection. I've tried rebooting, etc.
I would love to hang out on EG22 but without roaming this thing is worthless to me. At work I have to force roam since Sprint data has been dead downtown for over a year.

Works fine for me
remember, data won't show if you're connected to 4g or wifi.

LunaticWolf said:
Works fine for me
remember, data won't show if you're connected to 4g or wifi.
Click to expand...
Click to collapse
Hmm... no 4G or WiFi here. It just shows the triangle with the signal meter, but of course there is no data connection.
I flashed the DEODEXED version by decadance. What version are you using? are you using the EG22 modem? I haven't tried to flash an older modem yet.

Make sure you have data enabled. hold the power button and then click data network mode.

Tried with rc 1.4 and it worked, the 3g data symbol doesn't show up till you request for internet. Both time I tried took 1 min to handshake.
I am using prl 11114 and my suppose to be 3g data roam speed is at cdma speed dl is caped around 120kbps on verizon full signal bar.
Sent from my SPH-D700 using XDA App

the newest RC works for me, but the modem crashes and reboots every time I go into roaming, but it reboots into roaming fine so I haven't really worried too much

I checked all that. It just doesn't handshake for some reason. I remember this same issue on the very first Froyo leak. Weird thing is I tried the roaming on the very first GB leak and it worked just fine.
I'll have to flash around some modems, try a different release of EG22 and see if I can get this working. This feature is a huge must for me.

Got it working... ODIN'd to this version of GB and it worked first shot. WOOHOO!! Loving it.
http://forum.xda-developers.com/showthread.php?t=1184134

Sprint WiFi Calling doesn't work after Nougat Upgrade

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

8.1 dumb questions

First I am on Verizon.
I have to PH-1's I did a factory reset and updated one to 8.1. I don't see LTE or LTE+ anywhere AND every time I turn it on, it says no SIM card. Then after I enter my pin. It shows Verizon.
Also Backup's all say "waiting to backup"
Ideas?
Thanks

Zargone said:
First I am on Verizon.
I have to PH-1's I did a factory reset and updated one to 8.1. I don't see LTE or LTE+ anywhere AND every time I turn it on, it says no SIM card. Then after I enter my pin. It shows Verizon.
Also Backup's all say "waiting to backup"
Ideas?
Thanks
Click to expand...
Click to collapse
Was your device on Sprint first?
The SIM stuff is not a surprise. I see the same behavior.
If you wait long enough, it will connect.

Never on Sprint. Just very bad reception now. Backups still waiting. Phone connectivity seems somehow related to wifi on/off poor or none existant. Very strange. Also will not connect at all to my Verizon range extender with any settings.

Zargone said:
Never on Sprint. Just very bad reception now. Backups still waiting. Phone connectivity seems somehow related to wifi on/off poor or none existant. Very strange. Also will not connect at all to my Verizon range extender with any settings.
Click to expand...
Click to collapse
Shows fine in the tray here

If I go into Phone Info and look at carrier provisioning Info, I see Provisioning failed trying to restart session.
Clicking on "Trigger carrier provisioning" seems to do nothing.
Volte tends to stay off.

Partial fix: new activated SIM install in VERY strong LTE location with WIFi OFF! But it will not fall back to 3G. Now I can turn WiFi back on. Wish 3G worked.