So after obtaining S-off finally w/ Moonshine I installed WiFi tether Trev E mod app and tried many configurations and still get this message error: Tethering started with errors. Errors are: Error with configuring AP. And: error starting AP...someone know a fix? I get this w/ all 4.2.2 based ROMs and now using Dirty Unicorn...any help is appreciated.
poor-soul! said:
So after obtaining S-off finally w/ Moonshine I installed WiFi tether Trev E mod app and tried many configurations and still get this message error...
Click to expand...
Click to collapse
I just achieved S-Off a week ago and had the same problems, so I still feel your pain!
Have patience, relax, and do it by the numbers.
You're a little light on specifics so I suggest that you:
Make sure you're on the latest radios & PRL.
I suggest twrp 2.5 recovery
Do a Nandroid backup b/4 you do anything else.
Uninstall the WiFi Tether app that you just installed.
Dump cache & Dalvik cache & then reboot
Test the device's internet connection via your browser to make sure it is functioning.
You will need to enter the device's phone number in the little box in Sprint Zone b/4 you proceed.
Get out of the Sprint page and go to one you're familiar with to make sure you have internet, 4G LTE would be best.
Once you're happy that the phone's internet works, update your profile and reboot.
Install the WiFi Tethering app again.
Follow the instruction below.
http://forum.xda-developers.com/showthread.php?t=2269917
The other variable is the device which you are trying to tether. You may have your handset and app configured correctly and not know it because the WiFi utility in your tethered device is configured incorrectly.
A tool that I use every day to jump or kick start the connection between my Evo(s) and my laptop is a simple batch file that I keep pinned to my desktop. Copy, paste to your notepad, save as "Anything.bat" You'll wonder what you did without it.
ipconfig /release
ipconfig /flushdns
ipconfig /renew
tmwilsoniv said:
I just achieved S-Off a week ago and had the same problems, so I still feel your pain!
Have patience, relax, and do it by the numbers.
You're a little light on specifics so I suggest that you:
Make sure you're on the latest radios & PRL.
I suggest twrp 2.5 recovery
Do a Nandroid backup b/4 you do anything else.
Uninstall the WiFi Tether app that you just installed.
Dump cache & Dalvik cache & then reboot
Test the device's internet connection via your browser to make sure it is functioning.
You will need to enter the device's phone number in the little box in Sprint Zone b/4 you proceed.
Get out of the Sprint page and go to one you're familiar with to make sure you have internet, 4G LTE would be best.
Once you're happy that the phone's internet works, update your profile and reboot.
Install the WiFi Tethering app again.
Follow the instruction below.
http://forum.xda-developers.com/showthread.php?t=2269917
The other variable is the device which you are trying to tether. You may have your handset and app configured correctly and not know it because the WiFi utility in your tethered device is configured incorrectly.
A tool that I use every day to jump or kick start the connection between my Evo(s) and my laptop is a simple batch file that I keep pinned to my desktop. Copy, paste to your notepad, save as "Anything.bat" You'll wonder what you did without it.
ipconfig /release
ipconfig /flushdns
ipconfig /renew
Click to expand...
Click to collapse
Awesome. Thank you I will give your advice a try. I'll let you know how it goes.
poor-soul! said:
Awesome. Thank you I will give your advice a try. I'll let you know how it goes.
Click to expand...
Click to collapse
Did you ever figure it out? I am having the same problem with the AP error in the log and I have been trying for hours to get it to work...Any help is appreciated!
thepennster said:
Did you ever figure it out? I am having the same problem with the AP error in the log and I have been trying for hours to get it to work...Any help is appreciated!
Click to expand...
Click to collapse
I wish I remember exactly what I did to get mine working, but I do remember throwing in at least one Fix Permissions along the way.
Failed doing these steps...never had this problem on sense ROMs
thepennster said:
Did you ever figure it out? I am having the same problem with the AP error in the log and I have been trying for hours to get it to work...Any help is appreciated!
Click to expand...
Click to collapse
Error configuring AP persists...not sure what to do but go back to sense ROM..
No didn't work for me...the error w/ configuring AP persists....
Related
So I've had root (stock Froyo) on my TB for a month or 2 now and really like being able to take off the bloatware and maintain consistent backups with TI and pull back a recovery with ROM Manager.
Over the past 2 weeks or so the damn OTA has been forcing its way into my phone, literally!!!
Every so often I would open my phone and it would be in process of DL a Firmware update. I'd pull the battery and restart and give me a server failure error and I was able to continue wihtout error.
All other times it would give indication that Verizon was trying to do something and I would reject it. It would disappear for a few days and reappear with the same 3 selections. I would always reject.
Then one day, as mentioned previously, I noticed my phone was in process of DLing a firmware update.
I thought I caught it in time, but then it kept happening.
I guess yesterday was the last straw VZW had with me rejecting their update and it was forced on. I was then stuck in a boot loop. It would start up and run some processes, get past the SD connection and then hang for a minute then return to a shutdown.
After this I decided to run the Deodexed 1.70 update and the Radio update.
Sat down last night and started messing with it.
Ran the Deodexed through HBOOT and nothing really happened. Did not process as I would expect or had seen when I set up ROOT originally.
So I then ran the radio through HBOOT and this one ran as expecxted asking me for the next step to run the install.
Seemed to work fine and the phone rebooted without a problem, that is until I saw my phone had 'No Service' on the lock screen and the little [x] next to the reception bars.
I tried running both files again through ROM Manager and received the same result.
What I noticed is the following;
Yeah I switched my Tom's and I had no data connection. This is what I did.
Step 1. ##778
step 2. Password 000000 ( six 0's)
Step 3. Tap on edit mode
Step 4. Go to modem settings and scroll to Rev.A (I was on eHRPD so I switched to Enable or whatever the first option is. If your oh enable switch it to eHRPD I did this setting when I didn't have connection a looong time ago)
Sounds like you successfully flashed an MR2 radio but you are still on MR1 (1.13.605.7 indicated by your screencaps) thus no service.
Assuming your recovery still works, flash the 1.70.605.0 rom via recovery.
bloated: http://forum.xda-developers.com/showthread.php?t=1160374
debloated: http://forum.xda-developers.com/showthread.php?t=1161251
If your recovery doesn't work, reflash it then flash the rom.
As you see in the screencaps, you should see 1.70.605.0 under build and software.
The OP's issue is a common one. Rejecting updates is a sorry way to retain root.
First, the 1.13 RUU that was flashed after rooting via ADB was NOT intended to be retained as the long-term solution. Please take a look at this radio link. As you'll see, RUU 1.13 is OLD. I believe many are under the impression this is the firmware that was on their device pre-root, and it likely wasn't. Most started with RUU 1.66 or 1.68. By running that post-root RUU, you're running firmware that is significantly older and less efficient than just about anything out there. And it WILL continue to attempt an auto-update until you fix that situation.
If you like your stock ROM, flash the RUU 1.68 rooted ROM but keep your radios. An even better idea would be to flash the RUU 1.70 ROM and radios since they are the most stable and efficient Froyo releases out. Of course, flashing a real custom ROM would be the best solution, but I know some people like bone stock or have some irrational paranoia about custom ROMs.
Check the Access Point name
Someone else had a similar problem. He realized he had no Access Point Name assigned. (Menu/Settings/Wireless & networks/Mobile networks/Access Point Name)
He wasn't able to reset it from the menu/reset option on the APN page, but was able to add a new APN with VZWINTERNET as the Internet name with the same settings as the non-working APN. Once he had the new APN enabled, he had data access.
brenick said:
Someone else had a similar problem. He realized he had no Access Point Name assigned. (Menu/Settings/Wireless & networks/Mobile networks/Access Point Name)
He wasn't able to reset it from the menu/reset option on the APN page, but was able to add a new APN with VZWINTERNET as the Internet name with the same settings as the non-working APN. Once he had the new APN enabled, he had data access.
Click to expand...
Click to collapse
Not this case since from the pics, the OP never actually flashed a rom that would work with his radio anyway as I mentioned above.
my wifi worked for awhile then stopped connecting. tried wiping cache/davlik 3 times. tried re-installing the rom. i nandroided back to an older version which wifi worked before and now it doesn't. tried flashing a different rom no success. tried flashing a different kernal anthrax b-02 via recovery no success so i tried flash gui image app in the market. all with no luck. im on h-boot 1.40.
my 4g connects just not my wifi. if anybody can help it would greatly be appreciated.
ro2themax said:
my wifi worked for awhile then stopped connecting. tried wiping cache/davlik 3 times. tried re-installing the rom. i nandroided back to an older version which wifi worked before and now it doesn't. tried flashing a different rom no success. tried flashing a different kernal anthrax b-02 via recovery no success so i tried flash gui image app in the market. all with no luck. im on h-boot 1.40.
my 4g connects just not my wifi. if anybody can help it would greatly be appreciated.
Click to expand...
Click to collapse
The 4G and WiFi drivers are stored in the same directory. Generally, if one is not working due to a mismatch with the kernel, the other one will not work either.
Since you're taken some initial steps to gaurantee the WiFi module definitely matches the kernel version, I would move on two more detailed troubleshooting.
There are two approaches I would suggest to get at the root of the issue quickly without wasting more time/effort.
1) When you toggle WiFi on/off from the Settings screen, what message does it display there? It should also be displaying detailed error out put in at least the logcat if not also in dmesg/kmsg. If you are able to post up these logs, it should help narrow down the issue.
2) Nandroid your current setup, you can revert back later and then flash a completely 100% stock ROM and kernel. Use a modified version of the RUU if needed.
Personally, I would glance at the logs from Step 1, but to make sure the hardware on the device is in deed working 100% and there are no hardware issues, I would revert to 100% stock ROM and kernel. If the WiFi doesn't work with 100% ROM and kernel, this would appear to be a potential hardware issue and I would look into getting the device repaired/exchanged.
If the WiFi works on the 100% stock ROM and kernel, then the issue now lies with either the previous ROMs/Kernels or the methods used to load them.
Hope that helps and appreciate the support!
hey, thanks for the reply and help.
when i try ti connect in the settings, it attempts to connect and obtain the ip address but it doesnt connect and just times out. i dont know how to look at or even find the the logcat or dmesg/kmsg. if you could tell me how to find it, i would post it.
im going to try to flash a stock rom with stock kernal, hope fully its not a hardware issue. i will post my results on the stock rom flash.
i just flashed Shooter_S_Sprint_W...8.651.3_deodex.zip and still no wifi.
am i just screwed or is there another way to fix this problem?
joeykrim said:
The 4G and WiFi drivers are stored in the same directory. Generally, if one is not working due to a mismatch with the kernel, the other one will not work either.
Since you're taken some initial steps to gaurantee the WiFi module definitely matches the kernel version, I would move on two more detailed troubleshooting.
There are two approaches I would suggest to get at the root of the issue quickly without wasting more time/effort.
1) When you toggle WiFi on/off from the Settings screen, what message does it display there? It should also be displaying detailed error out put in at least the logcat if not also in dmesg/kmsg. If you are able to post up these logs, it should help narrow down the issue.
2) Nandroid your current setup, you can revert back later and then flash a completely 100% stock ROM and kernel. Use a modified version of the RUU if needed.
Personally, I would glance at the logs from Step 1, but to make sure the hardware on the device is in deed working 100% and there are no hardware issues, I would revert to 100% stock ROM and kernel. If the WiFi doesn't work with 100% ROM and kernel, this would appear to be a potential hardware issue and I would look into getting the device repaired/exchanged.
If the WiFi works on the 100% stock ROM and kernel, then the issue now lies with either the previous ROMs/Kernels or the methods used to load them.
Hope that helps and appreciate the support!
Click to expand...
Click to collapse
joeykrim, thanks bud for your help. I got it to work. i really do appreciate the quick reply and assistance.
I've been ripping my hair out the last couple days trying to figure this out.
In the process of flashing a ROM and kernel I did a number of things:
-Carrier unlock (I feel like this is the culprit)
-Unlocked the bootloader
-Flashed Wet Dream (2.3.6 build)
-Installed webtop
-Attempted to root, unsuccessfully (let me know when the 2.3.6 root is available, haha)
After all this, everything was working fine--including wifi. But somewhere along the lines, maybe 15 minutes after I complete all these steps, out of the blue my wifi won't connect. It just says "obtaining IP address" and never connects.
So I got pissed and went on a wiping/reflashing spree. Got everything reset. The wifi was working great again. Then randomly, it just stopped working again.
Question:
Does anyone know why this is happening and what I can do to fix it?!
I'm dying here. Just as a side note in case you need this information, I think I'm going to flash to the 2.3.4 Wet Dream so I can root my device. Also, I don't mind going back to stock. If that's what fixes, it then I'll be more than happy to go stock. I plan on running webtop2sd as well.
Thanks in advance.
Mankey Magic said:
I've been ripping my hair out the last couple days trying to figure this out.
In the process of flashing a ROM and kernel I did a number of things:
-Carrier unlock (I feel like this is the culprit)
-Unlocked the bootloader
-Flashed Wet Dream (2.3.6 build)
-Installed webtop
-Attempted to root, unsuccessfully (let me know when the 2.3.6 root is available, haha) <-- i think this one no need to do
After all this, everything was working fine--including wifi. But somewhere along the lines, maybe 15 minutes after I complete all these steps, out of the blue my wifi won't connect. It just says "obtaining IP address" and never connects.
So I got pissed and went on a wiping/reflashing spree. Got everything reset. The wifi was working great again. Then randomly, it just stopped working again.
Question:
Does anyone know why this is happening and what I can do to fix it?!
I'm dying here. Just as a side note in case you need this information, I think I'm going to flash to the 2.3.4 Wet Dream so I can root my device. Also, I don't mind going back to stock. If that's what fixes, it then I'll be more than happy to go stock. I plan on running webtop2sd as well.
Thanks in advance.
Click to expand...
Click to collapse
try check in: settings-- battery & data manager--battery mode ( see what presets u use).
then try check: settings--wireless & network settings--wifi settings--advanced (press menu key(the left touch key in bottom)--wifi sleep policy-- set to never.
btw, wetdream should be already rooted. correct me if im wrong.
hope this help.
benjat said:
hope this help.
Click to expand...
Click to collapse
Benjat, thanks for the reply.
My battery settings were set to "Nighttime saver". I set it to "Performance mode".
I set my wifi sleep policy to Never.
Still have the same problem.
My understanding was that WD was already rooted, but Busybox wasn't installing so I ran Root Check Basic from the Market and it said my device did not have root access
Mankey Magic said:
Benjat, thanks for the reply.
My battery settings were set to "Nighttime saver". I set it to "Performance mode".
I set my wifi sleep policy to Never.
Still have the same problem.
My understanding was that WD was already rooted, but Busybox wasn't installing so I ran Root Check Basic from the Market and it said my device did not have root access
Click to expand...
Click to collapse
maybe try reboot the phone after change the setting?
im not sure about busybox. what apps u running that require busybox? i want to try install it.
*i just try download root check basic. got message "your device isn't compatible with this item" hehe
Reboot and still no dice.
Ahhhh! So frustrating!
I was mid webtop2sd install and busybox is required for one of the steps to work. I'm actually not sure what it does.
Mankey Magic said:
Reboot and still no dice.
Ahhhh! So frustrating!
I was mid webtop2sd install and busybox is required for one of the steps to work. I'm actually not sure what it does.
Click to expand...
Click to collapse
last try.. remove all wifi network added.. double check all the things i post before.. switch off wifi.. power off ur phone.. 10 sec then switch it on back, then on wifi. if still cant, i dont have anymore idea..
Thanks for all the help benjat. Unfortunately, it didn't work. Hopefully, someone else who has gone through this can help me out.
Mankey Magic said:
Thanks for all the help benjat. Unfortunately, it didn't work. Hopefully, someone else who has gone through this can help me out.
Click to expand...
Click to collapse
nvm.. maybe do full wipe again..
what ver of WD u using? with what addon? im using WD 1.4.3 full
I've already done a cache/date wipes to no avail.
I'm using 1.4.4 lite. I'm thinking of flashing the 2.3.4 based WD though (is that 1.4.3?).
I could flash something else too, I guess. I really need webtop (with xfce mod) and I heard Wet Dream works well with it.
If this really is a software problem and it is the ROM's fault, then does anyone have a webtop compatible ROM recommendation?
Mankey Magic said:
I've already done a cache/date wipes to no avail.
I'm using 1.4.4 lite. I'm thinking of flashing the 2.3.4 based WD though (is that 1.4.3?).
I could flash something else too, I guess. I really need webtop (with xfce mod) and I heard Wet Dream works well with it.
If this really is a software problem and it is the ROM's fault, then does anyone have a webtop compatible ROM recommendation?
Click to expand...
Click to collapse
i cant tell if its problem with rom or what.. 1.4.3 is 2.3.6 base. and yes webtop work well with it.
here's normaly what i do..
Boot CWM Recovery
Wipe data/factory
wipe cache
wipe dalvik
flash rom
reboot to fastboot and do fastboot-w & then fastboot reboot.
let it boot for 1st time (until stable/full load) i left it around 10 mins
then reboot back to CMW to flash addon. usually i flash 1 then boot.. continues untill flash all.. maybe a bit fussy step.. but i prefer all loaded before flashing another
*i never tried webtop2sd yet.. still dont buy bigger mem card coz funding for lapdock
** maybe can try this one to make it clean wipe.. http://forum.xda-developers.com/showthread.php?t=1421522&highlight=fastboot+-w
Yeah I realized too late that everything cost me way more than I had originally intended to spend. SD cards have come down in price but still pretty pricey for a 32 GB card.
And thank you for the link. I'll try it out tomorrow and report back. It's 1:00 AM here in Seattle!
Hey Mankey,
Have you tested different Wifi networks to ensure that the issue is not with the phone or the ROM at all?
Also, check if someone else on Wet Dream thread had WiFi issues, if this happened with someone else, then they should have fix for sure!
Usually I do what bejnat mentioned and usually works.
Also, about the root, try to follow a root process again. It happened with me before, then I had to install a .zip file through Recovery mode to have root access again.
Hope this helps!
wouldn't just flashing the radio or a newer radio maybe fix his issue??
Yeah it doesn't work with other networks either. And as for root I don't think there's a direct way to root 2.3.6 yet.
Sk8trix, I think I'll try that after I flash back to stock 2.3.4. I've tried just about everything but the radio. Kernels don't fix it.
I'll post an update in a couple days. I really want to get this fixed.
I had the same problem with my dark side when I 1st got it and to fix it I flashed another ROM ,loaded it then flashed back ,cleaned delvik cache and flashed gapps then rebooted and 1st boot fixed my problem was using 2.3.6 with webtop2sd+nebtop app hope this helps you
Sent from my ics+darkside multiboot mb860 using xda premium
Searched and found nothing.
CleanRom supplies a visual voice mail download. http://forum.xda-developers.com/showthread.php?t=2055170&highlight=vvm
However, when I download the zip and open the pdk, I keep getting an error that says fail to install.
I'm a newb as far as rooting the phone etc...
So any help is appreciated. Thank.
deputydog95 said:
Searched and found nothing.
CleanRom supplies a visual voice mail download. http://forum.xda-developers.com/showthread.php?t=2055170&highlight=vvm
However, when I download the zip and open the pdk, I keep getting an error that says fail to install.
I'm a newb as far as rooting the phone etc...
So any help is appreciated. Thank.
Click to expand...
Click to collapse
Are you flashing this in TWRP or CWM? Sounds like you're unzipping and trying to install via the apk, but I'm pretty sure this is a flashable zip. Just install the zip file to the root directory on your sdcard (internal storage) and flash via TWRP or CWM, whatever recovery you installed to flash CleanRom.
johnnyvol said:
Are you flashing this in TWRP or CWM? Sounds like you're unzipping and trying to install via the apk, but I'm pretty sure this is a flashable zip. Just install the zip file to the root directory on your sdcard (internal storage) and flash via TWRP or CWM, whatever recovery you installed to flash CleanRom.
Click to expand...
Click to collapse
Ahhh... That makes more sense.
I went and put google voice on there in the meantime to see how that works. Might be able to save $3 a month as a result
As long as I'm asking questions... I have a verizon network extender in my office. After I installled cleanrom, every time I go into my office and get on the extender it goes into roaming mode. At which mode texting etc... is shut down.
Any clue as to what's going on there? I spend a lot of time in my office so that's not going to work for me.
deputydog95 said:
Ahhh... That makes more sense.
I went and put google voice on there in the meantime to see how that works. Might be able to save $3 a month as a result
As long as I'm asking questions... I have a verizon network extender in my office. After I installled cleanrom, every time I go into my office and get on the extender it goes into roaming mode. At which mode texting etc... is shut down.
Any clue as to what's going on there? I spend a lot of time in my office so that's not going to work for me.
Click to expand...
Click to collapse
Same happened to me. Not yet sure if it's a CleanRom issue or a 4.1.2 issue. Some people have reported the roaming issue on other devices recently.
You can set roaming data to always in settings, and as long as you don't travel into a real roaming area you should be fine.
johnnyvol said:
Same happened to me. Not yet sure if it's a CleanRom issue or a 4.1.2 issue. Some people have reported the roaming issue on other devices recently.
You can set roaming data to always in settings, and as long as you don't travel into a real roaming area you should be fine.
Click to expand...
Click to collapse
I ended up trying beatown's "Jelly Beans" ROM. So far so good. A couple weird things but it seems to be more friendly than CleanRom.
True test will be at the office.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
after a lot of trial and error trying to determine why WiFi calling kept giving me the "Error: REG99 Unable to Connect" message, I was able to narrow it down to busybox pro found here. after I install this app WiFi calling breaks and I'm left with that REG99 message. if I remove busybox and reboot, WiFi calling is working properly again. I've scoured the Internet and there have been a few references to this, but no real solution other than to remove busybox. I'm posting here hoping someone may have a solution!
dimm0k said:
after a lot of trial and error trying to determine why WiFi calling kept giving me the "Error: REG99 Unable to Connect" message, I was able to narrow it down to busybox pro found here. after I install this app WiFi calling breaks and I'm left with that REG99 message. if I remove busybox and reboot, WiFi calling is working properly again. I've scoured the Internet and there have been a few references to this, but no real solution other than to remove busybox. I'm posting here hoping someone may have a solution!
Click to expand...
Click to collapse
Did you use the smart install option?
Swizzle82 said:
Did you use the smart install option?
Click to expand...
Click to collapse
yes! and it ended up choosing /su/bin... should I do something different?
dimm0k said:
yes! and it ended up choosing /su/bin... should I do something different?
Click to expand...
Click to collapse
I don't know if it was related to busybox, but I had been getting the same error until I reflashed a new system and factory reset. The first tine I had trouble getting the same busybox to load. After the second try it loaded in seconds and used smart install. Uninstall the busybox files through the app but not the app and then choose smart install>clean mode.. Not saying it will work but those are the options I choose everytime.
Swizzle82 said:
I don't know if it was related to busybox, but I had been getting the same error until I reflashed a new system and factory reset. The first tine I had trouble getting the same busybox to load. After the second try it loaded in seconds and used smart install. Uninstall the busybox files through the app but not the app and then choose smart install>clean mode.. Not saying it will work but those are the options I choose everytime.
Click to expand...
Click to collapse
whoa!! out of all the times I've opened up busybox in the past, I may have opened that "smart install" section once or twice and that was after busybox had already been installed so I never bothered to go back to it. so to confirm you were getting the same WiFi calling issue previously and it didn't install with smart install, but the second try it did use smart install? does this mean you currently have busybox installed and WiFi calling is working?
dimm0k said:
whoa!! out of all the times I've opened up busybox in the past, I may have opened that "smart install" section once or twice and that was after busybox had already been installed so I never bothered to go back to it. so to confirm you were getting the same WiFi calling issue previously and it didn't install with smart install, but the second try it did use smart install? does this mean you currently have busybox installed and WiFi calling is working?
Click to expand...
Click to collapse
Like I said, I'm not sure if my problem was your problem, I did have trouble installing it the first time I had rooted (I always install busybox right after rooting) and also had wifi calling issues(again, not sure if related). After I re-rooted and did a factory reset I installed busybox again, no issues getting it to install properly that time, wifi calling was also working again. You say you traced your problem to busybox and so I would suggest trying the smart install and see if that works.. If not try a factory reset. I'm pretty sure my issue was on the data rather than system side of things because a factory reset took care of it.
Swizzle82 said:
Like I said, I'm not sure if my problem was your problem, I did have trouble installing it the first time I had rooted (I always install busybox right after rooting) and also had wifi calling issues(again, not sure if related). After I re-rooted and did a factory reset I installed busybox again, no issues getting it to install properly that time, wifi calling was also working again. You say you traced your problem to busybox and so I would suggest trying the smart install and see if that works.. If not try a factory reset. I'm pretty sure my issue was on the data rather than system side of things because a factory reset took care of it.
Click to expand...
Click to collapse
!! looks like this solved it for me! ran a TWRP backup just to be sure and then proceeded with an install using the options you've used and WiFi calling is still fully operational! thanks!
dimm0k said:
!! looks like this solved it for me! ran a TWRP backup just to be sure and then proceeded with an install using the options you've used and WiFi calling is still fully operational! thanks!
Click to expand...
Click to collapse
Good to hear!