Related
I own a Mi Max Helium and from the first day I use it with open bootloader and Custom Roms.
After 4 Weeks of using the strange things began:
- I lost network sometimes, but most of the times it was back in seconds. (once or twice a day)
- then randomly the MiMax said there is no sim card installed. Ok reboot phone and everything was okay. (once or twice a day)
- then it happened every hour
- and then sometimes after some hours or some minutes - not replicatable
- as a last step rebooting the phone doesn´t help. I have to kick out the Sim, wait some seconds and put it in again
Ok I thought it was a fault with the custom roms.
Made a real big factory reset with mi flash tool and cleaned the whole phone like a new device after the delivery.
After the first reboot it wasn´t able to find any simcard (IMEI und EFS was okay), so I thought phone or SimCard has a defect.
Took a simcard from my girlfriend - everything was working fine. Took my simcard in the MiMax and curiously everything was working fine
Flashed Xenon HD Custom Rom and everything worked well the last 4 Weeks and now the whole Sh*t begins again in the same way like described above.
Wtf is that behaviour? Can anybody report similar things?
Using SIM-Slot 1 or SIM-Slot 2 makes no difference. Its not logical or reproducible for me
T-Mobile? There has been reports not only fo Mi Max but One Plus X and some other Chinese brands killing particular tipes of T-Mobile sim cards by constantly trying to write on them. Sounds exactly what you are describing.
Solution is call T-Mobile, they know the issue and should replace sim card with the right tipe.
nijel8 said:
T-Mobile?...
Click to expand...
Click to collapse
Interesting. No I´m using a german multiple provider called 1&1 and they use Vodafone D2 Network here.
They also use Telefonica (ePlus & O2), but the reason for that behaviour could be the same. I will call my provider and hope the know similar cases.
Thanks for the advice so far :good:
Well I share you problem I am.from Chile and this started to happen after updating to official ROM 8.2.3.0
I tried for months to find a fix but in the end I've noticed in my country all operators started using 4g band 28 (700mhz aggregation) band is not compatible with my Max prime (helium)
This doesn't explain why the card is lost until rebooting the Phone though.
A good thing is to set auto turn off in security app at 7:00am then enable auto turn on at 7:10 am this way your phone will work in the morning and not lose any important phone calls.
Check out this thread
Do you have any similar symptoms? Can you search for networks manually? I can't
https://forum.xda-developers.com/showthread.php?t=3604428
Sent from my MI MAX using Tapatalk
DJ_Tomato said:
Well I share you problem I am.from Chile and this started to happen after updating to official ROM 8.2.3.0
I tried for months to find a fix but in the end I've noticed in my country all operators started using 4g band 28 (700mhz aggregation) band is not compatible with my Max prime (helium)
This doesn't explain why the card is lost until rebooting the Phone though.
A good thing is to set auto turn off in security app at 7:00am then enable auto turn on at 7:10 am this way your phone will work in the morning and not lose any important phone calls.
Check out this thread
Do you have any similar symptoms? Can you search for networks manually? I can't
https://forum.xda-developers.com/showthread.php?t=3604428
Click to expand...
Click to collapse
Try cleaning the sim card with acetone.
nijel8 said:
T-Mobile? There has been reports not only fo Mi Max but One Plus X and some other Chinese brands killing particular tipes of T-Mobile sim cards by constantly trying to write on them. Sounds exactly what you are describing.
Solution is call T-Mobile, they know the issue and should replace sim card with the right tipe.
Click to expand...
Click to collapse
can you please explain smart cpu efficiency feature in new miui nougat update it will be very helpful I tied to create a port regarding this but can't
Even i had than issue on xenon and aosp extended rom could not able to find workaround so jumped to miui
Hello all,
I was warned of an impending "update" a few nights ago. Since it hit, my mobile hotspot no longer works.
Does anyone else have an S7 Active on Red Pocket who has a working hotspot? If so, could you share the APN settings you are using, and the Android version you are on?
I think they rolled me back to January 2018. G891AUCU2BRB5
Would rather not factory reset or root, but getting very close to doing so. Neither RP or AT&T are helpful here.
Thank you,
Bob
Red Pocket Mobile Hotspot problem solved - stock Oreo 8.0 fixed it
Well, for anyone who might encounter this, I finally resolved it.
Pulled the SIM card and did a factory reset. Then it recognized the Oreo update over Wifi. Had to load an intermediate update first.
I put it Red Pocket's AP settings.
First time I tried Mobile Hotspot, it still didn't work.
Restarted the phone.
Still didn't work.
Then I remembered one rep saying to switch MVNO type to "IMSI".
3rd times a charm. Hotspot and USB tether now both working.
After ten hours of wading through poor advice, I'm back to where I was four days ago.
With one exception: I learned how to turn on Developer Mode (tap Build Number 7 times in Software Info)
AND SHUT OFF THE AUTOMATIC UPDATES UNDER DEVELOPER MODE SO IT WON'T HAPPEN AGAIN!!!
I have a stock S7 Active/G891A that I bought unlocked on eBay in March of 2018. It's currently running Oreo 8.0.0, build G891AUCS4CSA3. I just now disabled OTA updates thanks to you.
I've been trying to get Mobile Hotspot to work on this phone ever since I switched Consumer Cellular several months ago. Whenever I tried to enable hotspotting the phone screen would display a popup:
Please wait while verifying
Which was a normal message on the AT&T network, but now (using AT&T's network through Consumer Cellular), after 5-10 seconds a different window would appear:
Tethering/Mobile AP is unavailable.
A network issue may be preventing use of your Mobile Hotspot. Please call Customer Care at 611.
[excessive hard-coded line breaks omitted]
Over the course of several weeks in January I literally spent hours on the phone with several Consumer Cellular 1st and 2nd tier support techs trying to get past that error. Tier 2 support gave me new APN settings, had me do a network reset, and suggested that I do a factory reset. Which I did later, but that didn't work, either. Then CC tier 2 support gave up and bumped my ticket to tier 3. Tier 3 support then transmitted their version of an APN definition to my phone, but still no love. At the end of the 2nd week of phone tag, a Tier 2 tech told me that "it <Mobile Hotspot> just doesn't work with some phones not sold by us".
Maybe hotspotting won't work with my old Motorola Razor, but I was pretty sure that I'd eventually strike gold with my trusty G891A.
Because my S7 Active has version 4 of the boot loader (thank you, latest and final OTA), I haven't been able to find anything that resembles a working root. I even paid OneClickRoot to do it via remote desktop session, hoping that they had some good mojo that I hadn't yet discovered. But their support tech hit a wall, too, and ended up flashing my phone back to stock Oreo 8.0.0. They also refunded my purchase almost immediately which made me sort of happy but still sad that I had no Hotspot abilities.
While searching for possible workarounds (ROMS, root, mystical incantations) tonight I came across your posts:
bobcpdx said:
[snip]
Then I remembered one rep saying to switch MVNO type to "IMSI".
[snip]
Click to expand...
Click to collapse
So I followed your tip. I created a new APN definition and copied in all of the values from the CC Tier 3 definition . I then set Mobile virtual network operator type to imsi . This value was set to None in all in all of the other APN definitions on my phone.
I didn't even need to reboot the phone. I selected my new APN definition and enabled Mobile Hotspot. The first message about verifying came up. But then the phone didn't direct me to dial 611. Mobile Hotspot simply started working.
Thanks every so much for sharing this insight.
bobcpdx said:
Well, for anyone who might encounter this, I finally resolved it.
…..
Then I remembered one rep saying to switch MVNO type to "IMSI".
3rd times a charm. Hotspot and USB tether now both working.
….
Click to expand...
Click to collapse
WOW! Thanks so much for posting this. I've been struggling for a couple of months to find a way to hotspot my two unlocked LG's (G6 and a G7) on Cricket and Consumer Cellular. This trick enabled hotspot/tether quickly and easily.
My apologies to Cricket and CC, for my unflattering thoughts about them. I assumed it was their issue! Not sure why these unlocked LG's are fidgety like this. We got a Moto X4 (Android One flavor) in the family, and it can hotspot with no tweaking.
BTW - I have a similar issue with call forwarding on the LG's. Can't enable it, get an error. But the Moto X4 has no problem on either of these AT&T MVNO's. Anyone have an easy answer for that? Thanks.
This doesn't answer the call forwarding question. I'm not sure who pushes OTA updates, but soon after my last post I got a notification that an my phone needed to be rebooted for an update to finish. This was after I (at least thought that I had) disabled automatic updates. After the update the hotspot feature no longer worked. I checked APN settings and found that the update had reset the APN MVNO type to NONE . I manually changed it back to imsi and it's been working ever since. I also made sure (twice with reboot in between) that automatic OTA Updates are disabled.
Although enabling/disabling these features seems to be problematic with AT&T MVNOs, what I find more curious is that techs at Consumer Cellular claim not to know how to fix them. Maybe that's true, or maybe that's what they are told to say.
Was it coincidence that I received an OTA update within days of making this change, or is the Big Brother with the Blue Death Star logo watching us so closely?
Im having some trouble with a xiaomi mi 11 and a poco f3.. I can recieve but not send any messages.??
I've got the global rom installed on both and no updates availeble..
What to do?? I do not have VOLTE enabled, cause i've read that it could be the problem.. How to fix this?? Is xiaomi just a piece of crap?? Or does anyone know how this could be fixed??
Regards
mattti1990 said:
Im having some trouble with a xiaomi mi 11 and a poco f3.. I can recieve but not send any messages.??
I've got the global rom installed on both and no updates availeble..
What to do?? I do not have VOLTE enabled, cause i've read that it could be the problem.. How to fix this?? Is xiaomi just a piece of crap?? Or does anyone know how this could be fixed??
Regards
Click to expand...
Click to collapse
First of all, please don't take this as offensive or insulting.
1) Do you have balance on your mobile plan?
2) Are you 100% sure that it's not caused by your provider?
3) Is your SIM card damaged in any way?
I could understand if one phone could and the other couldn't, however, in your case, I'm 99% sure it's not caused by the phone itself, rather by your provider, therefore I cannot recommend that you factory reset your phone.
Hello thank you for reply??
yes my mobile plan has 4g.5g volte, sms and normal call so i should be covered there
And my SIM is working in other phones, my SIM is i the 1 place..
thanks
mattti1990 said:
Hello thank you for reply??
yes my mobile plan has 4g.5g volte, sms and normal call so i should be covered there
And my SIM is working in other phones, my SIM is i the 1 place..
thanks
Click to expand...
Click to collapse
If you can call people normally using the dialer app (not using WhatsApp, Telegram, etc.) then you should contact the customer support of your provider.
Just getting this out there, I think Xiaomi makes sub-par and super bloated software.
However, calling, messaging, and other core components of mobile phones have never lacked in terms of quality for me.
Check your APN those are probably incorrect
Hello again
My APN is completely correct..
If you're positive your APN is correct then try turning off and on chat features in messenger settings
Has anyone else experienced the same problem? Is there any way to get them to reactivate it?
I had an an XT1955-5 that was fully functional on the AT&T network, including voice over LTE. I bought this phone because XT1955-5 was on their list of approved phones. I even checked the sim status to verify that it didn't kick down to 3g/H+ when I made a call, and it had the HD symbol on the call screen.
Despite this, AT&T disabled it because they were shutting down the 3g network. I got them to reactivate it and it worked again for several months. Then, when they sent me the cheap replacement phone and sim card, they deactivated my old phone and I couldn't get it to work again. I tried calling them and talking to their technical support to explain the situation that VoLTE was fully functional on it. They didn't seem to know much other than "the computer says this phone isn't compatible." They said they would try changing my provisions, but they ended up making it much worse so mobile data wouldn't even work anymore.
Do they just go by an IMEI whitelist that can't be overridden? My best guess is that they seem to be shutting down all phones that weren't AT&T branded, so this one gets the axe because it was unlocked from another carrier. This is very disappointing because I really liked this phone for a combination of several factors that I can't seem to find in any others.
Unless I'm misreading the list, this is a whitelisted device on the AT&T network.
Correct, the model number is on their whitelist. That's why I chose this phone and why it's so frustrating that it was deactivated. I guess there's a subset of whitelisted IMEIs within that list, but isn't published. This particular one must not have been on their whitelisted IMEI list because it was unlocked from a nother carrier. Do you know if there's any way to get ATT to add it of am I SOL?
They say nothing about IMEI number limitations.
As long as it's not blacklisted there shouldn't be an issue. This list was just revised so your phone may not have been previously whitelisted.
There's quit a bit of confusion is what I gathered.
Some of the AT&T features like vid calling won't work without the AT&T software maybe firmware. Guess we'll both find out on the 22nd.
Call AT&T advance tech support as this is the game that moves as you play it.
I have a development:
I flashed back to stock/RetUS ROM from LineageOS 18.1 to try to fix wifi calling on T-Mobile since I was trying to switch to them due to this hassle. While I was at it, I read a post on a forum for another phone, where the person said they reflashed stock to reprovision the sim. I figured it's worth a try, so I popped in my AT&T sim card while on stock ROM and to my surprise, it fixed it. The LTE network is fully functional, at least for now. I didn't think Lineage did anything to change the radio firmware or whatever it is that controls how it interacts with the cell carrier. I guess I was wrong.
Now, I wonder if I'm stuck with the stock ROM because AT&T will detect a change and shut it down, or if I can get away with switching back to Lineage. I'll try it soon.
MotoMan1955-5 said:
Now, I wonder if I'm stuck with the stock ROM because AT&T will detect a change and shut it down, or if I can get away with switching back to Lineage. I'll try it soon.
Click to expand...
Click to collapse
AT&T isn't witch hunting. As long as it's firmware is compatible with their protocols it will work.
I have no clue what those protocols are though.
(deleted, mistook carrier)
I've pretty much lost hope at this point but I might as well share some more of this madness I'm experiencing. Maybe you'll even get some amusement out of my struggles.
VoLTE continued to work with the stock ROM. I flashed LineageOS again last night and was pleased to see VoLTE still worked. It went fine all day until someone in person mentioned to me that they texted me yesterday but I didn't respond. I never received the text, and I tried sending them one and they had not received that either. Since I was on the stock ROM when that text had been sent, I figure it was something still incorrectly configured with the carrier. I tried messages to several other people. They would all say "sent" but only a couple actually made it to the recipient, and likewise I could not receive messages from most people.
When I got home, I switched the sims around in a couple of phones to narrow down whether it was my phone or my sim that was causing the issue. It turned out to be the sim, as evidenced by successful messaging with a different sim in my phone but not my sim in a different phone. I happened to have the SIM in the AT&T Callypso when I called ATT customer support to see if they could fix the problem. Ultimately they did. VoLTE worked. Messaging worked.
I switched the SIM back to the G7 (currently running LineageOS 18.1). I made a quick call to confirm VoLTE still worked. It did. Great success! Then right after that I got the dreaded message saying they're updating the network and the phone I was trying to activate will not work. Now, it drops from LTE to H+ any time I have an incoming/outgoing call again, and mobile data doesn't even work now. At least messaging works now.
To make things worse, now it isn't even automatically reprovisioning when I put the sim in a new phone so I can't automatically get those privileges back like I did before. To make it double-worse, the sim for my spare line got the same screwed up status from being inserted into the G7 that it now has the same troubles.
Blackhawk, I agree that they probably aren't witch hunting or intentionally making this difficult, but obviously its network is changing my privileges when I put the SIM card in this phone. It seems to be that switching a sim to a new phone sends that phone info to the carrier, and if they have it on their list they automatically adjust the types of services available to that line to fit the phone. I suspect that info it sends also includes some software info, considering how it worked as intended when I had the stock software but not with Lineage which it probably did not recognize. My best guess is that I got away with flashing Lineage yesterday because my line was already configured correctly from when I had the stock rom, and since the SIM didn't change with the Lineage flash, it kept that same configuration. Moving it to another phone and back made it see the G7 as a new phone again, and it sent the info but the software wasn't recognized so I didn't get the good privileges.
ffdm, unfortunately you seem to be correct about just getting the runaround if your issue isn't common. The tech support people don't seem interested in anything other than their pre-scripted instructions, and it doesn't help that the support has clearly been outsourced to another country so they are hard to understand.
I have one last hope which is to put the SIM into the G7 totally stock, call customer support and have them reset the provisions for this line, then flash Lineage again and hope it never triggers the automatic provisioning ever again.
I just want a phone with a long battery life and AOSP not bloated with spyware that sends all my information to third parties that profile me. It shouldn't be this hard.
MotoMan1955-5 said:
I've pretty much lost hope at this point but I might as well share some more of this madness I'm experiencing. Maybe you'll even get some amusement out of my struggles.
VoLTE continued to work with the stock ROM. I flashed LineageOS again last night and was pleased to see VoLTE still worked. It went fine all day until someone in person mentioned to me that they texted me yesterday but I didn't respond. I never received the text, and I tried sending them one and they had not received that either. Since I was on the stock ROM when that text had been sent, I figure it was something still incorrectly configured with the carrier. I tried messages to several other people. They would all say "sent" but only a couple actually made it to the recipient, and likewise I could not receive messages from most people.
When I got home, I switched the sims around in a couple of phones to narrow down whether it was my phone or my sim that was causing the issue. It turned out to be the sim, as evidenced by successful messaging with a different sim in my phone but not my sim in a different phone. I happened to have the SIM in the AT&T Callypso when I called ATT customer support to see if they could fix the problem. Ultimately they did. VoLTE worked. Messaging worked.
I switched the SIM back to the G7 (currently running LineageOS 18.1). I made a quick call to confirm VoLTE still worked. It did. Great success! Then right after that I got the dreaded message saying they're updating the network and the phone I was trying to activate will not work. Now, it drops from LTE to H+ any time I have an incoming/outgoing call again, and mobile data doesn't even work now. At least messaging works now.
To make things worse, now it isn't even automatically reprovisioning when I put the sim in a new phone so I can't automatically get those privileges back like I did before. To make it double-worse, the sim for my spare line got the same screwed up status from being inserted into the G7 that it now has the same troubles.
Blackhawk, I agree that they probably aren't witch hunting or intentionally making this difficult, but obviously its network is changing my privileges when I put the SIM card in this phone. It seems to be that switching a sim to a new phone sends that phone info to the carrier, and if they have it on their list they automatically adjust the types of services available to that line to fit the phone. I suspect that info it sends also includes some software info, considering how it worked as intended when I had the stock software but not with Lineage which it probably did not recognize. My best guess is that I got away with flashing Lineage yesterday because my line was already configured correctly from when I had the stock rom, and since the SIM didn't change with the Lineage flash, it kept that same configuration. Moving it to another phone and back made it see the G7 as a new phone again, and it sent the info but the software wasn't recognized so I didn't get the good privileges.
ffdm, unfortunately you seem to be correct about just getting the runaround if your issue isn't common. The tech support people don't seem interested in anything other than their pre-scripted instructions, and it doesn't help that the support has clearly been outsourced to another country so they are hard to understand.
I have one last hope which is to put the SIM into the G7 totally stock, call customer support and have them reset the provisions for this line, then flash Lineage again and hope it never triggers the automatic provisioning ever again.
I just want a phone with a long battery life and AOSP not bloated with spyware that sends all my information to third parties that profile me. It shouldn't be this hard.
Click to expand...
Click to collapse
If these apply to you try:
Clear system cache
Clear Sim Toolkit data
Reset network setting
Get a new sim card from AT&T, handle like a stick of ram as they can be damaged by ESD.
From what is described, it does sound like a provisioning issue, and calling to get it fixed would probably be the correct solution. But why is it flagged as incompatible? Why would that status be persistent for that line? It's weird.
FWIW, AT&T kicked me off for switching from a OnePlus 6 (not a 5g phone) to a OnePlus N10 (5G phone). They were nice enough to disable my account on a Friday night when I switched sims, and was without cell service all weekend since they apparently don't want to do customer service outside banker's hours. Couldn't use the old one either (on 4G), I was completely blacklisted.
T-Mobile happily accepted my porting on Monday .
I'll save my unkind thoughts past "maybe consider firing them" as I don't want to sound like a loonie.
Man, I wish I could switch. I actually tried switching to a T-Mobile MVNO. They provisioned my SIM correctly, but unfortunately their coverage was insufficient in my rural area. I considered sticking with them and using wifi calling at home if that would work, but that feature was broken on lineage and I thought I got this to work correctly with AT&T.
I did get it working by flashing stock again, calling ATT to have them correctly provision it, then flashing LineageOS again. It has been working properly for about a week so with any luck I'll get to continue using the phone.
The 22nd came and went. I'm noticing some vids pause occasionally. May be just a random glitch otherwise no change. I may eventually try a network reset and have AT&T do it on their end.
Long live 4G LTE
Hi guys, so I've been testing and enjoying this Korean LG G8 here in Europe and I've been trying to enable LTE-A. I've tried literally everything but I just can not get anything to work when it comes to enabling it. I know for a fact that the x24 modem can support it but the SADEST PART is that LG took out the field test option and also the hidden menu is incomplete ( *#546368#820# is the ONLY option sadly, I think it's because LG is you know... shutting down..., there is no incentive for devs to code for it.)
Anybody, any help would be amazing as in my area 4G+ is really SO much better than the laggy and bad LTE.
So yeah... btw, how do I get rid of the roaming clock on the homescreen, I've tried everything but it still shows the time in Korea.
Oh yeah also, I enabled wi-fi calling in the hidden menu which honestly, it was hard af to find that even as no one seems to care, BUT the sad part is that the ''wi-fi calling'' option in the engineering menu (or what's left from it, I'm on Android 12 and it seems like from 11 to 12 LG has decided to be lazy and destroy any kind of debugging etc. so yeahhhhhhh.)
So in the ''official'' menu it's greyed out but I just enabled it, I am 100% sure you can do this with CA/ LTE-1/4G+ as well, also the way they classify bands is just UGH on android, why are they using classes and not bands.
I am pretty upset rn as I've spent soooooooo many hours now on something that should take 1 minute or less, wtf!
Okay so has anyone actually gotten Carrier Aggregation/4G+/4.5G to work on this phone?
I am really curious, it is becoming more and more important as companies are putting more emphasis on 5G and this phone sadly not being 5G enabled, sometimes my DL speeds are so trash and reception as well. When I pop my sim in my iPad mini 6, it just flies, 200 mbit DL all day, sometimes not even 5mbit DL or no reception at all, all due to CA being blocked by the carrier, yeah the phone is unlocked but basially eliminating the CA option toggle in the engineering menu really is a clear signal this phone was not really intended to be used on the network other than the network you signed up for. Talking about the Korean variant here, which to my knowledge has the most bands active aside from the ATT model I think but that's another story.
So yeah guys, anyone gotten CA to work on their phone? If so please post a screen so I can see a unicorn lol.
Were you able to find a solution to this problem yet? Doesn't seem like anyone else is having this problem because they would have posted it here. I live in the USA and I'm still waiting for the Android 12 update from US Mobile (T-Mobile).
Shawn R said:
Were you able to find a solution to this problem yet? Doesn't seem like anyone else is having this problem because they would have posted it here. I live in the USA and I'm still waiting for the Android 12 update from US Mobile (T-Mobile).
Click to expand...
Click to collapse
I gave up, it is actually VERY hard to make this work, I would update to Android 12 if you don't need any VoLTE, (VoWifi seems to be fine tho for some reaon) no CA / 4G+, none of that...
Hello,
I know you gave up, but I own the LG U+ G820N (thanks its the less bloated one) and I also face bad reception sicne switching carrier/updating t A12, I don't know which one is the cause.
I also can NOT access the *#*#4636#*#* engineering menu. Do you have any clue ?
Xdekker said:
Hi guys, so I've been testing and enjoying this Korean LG G8 here in Europe and I've been trying to enable LTE-A. I've tried literally everything but I just can not get anything to work when it comes to enabling it. I know for a fact that the x24 modem can support it but the SADEST PART is that LG took out the field test option and also the hidden menu is incomplete ( *#546368#820# is the ONLY option sadly, I think it's because LG is you know... shutting down..., there is no incentive for devs to code for it.)
Anybody, any help would be amazing as in my area 4G+ is really SO much better than the laggy and bad LTE.
So yeah... btw, how do I get rid of the roaming clock on the homescreen, I've tried everything but it still shows the time in Korea.
Oh yeah also, I enabled wi-fi calling in the hidden menu which honestly, it was hard af to find that even as no one seems to care, BUT the sad part is that the ''wi-fi calling'' option in the engineering menu (or what's left from it, I'm on Android 12 and it seems like from 11 to 12 LG has decided to be lazy and destroy any kind of debugging etc. so yeahhhhhhh.)
So in the ''official'' menu it's greyed out but I just enabled it, I am 100% sure you can do this with CA/ LTE-1/4G+ as well, also the way they classify bands is just UGH on android, why are they using classes and not bands.
I am pretty upset rn as I've spent soooooooo many hours now on something that should take 1 minute or less, wtf!
Click to expand...
Click to collapse
After weeks of research I actually tried the voWifi toogle + an app enabling the LG Wi-FI calling menu.
With voWIFI set to 0, the LG menu accessed via the app directly switches back to off when toggled.
But, with voWIFI on1 in the *#546368#820# menu, the other menu accessed via the app stays toggled.
I just tried at work with the phone in ariaplane mode and connected to a mobile sharing wifi form my professional phone but it was isntant voicemail....
Did you managed to get voWIFI without changinf the software ? Was the Field test menu available in A11 ?