This is going to be embarrassing if I'm missing something easy and obvious, but I've done as much as I can think of. I can't seem to get wifi calling to work. I just flashed the LYZ28E factory image and used wugfresh's modified boot to disable encryption, I'm also rooted with supersu. I don't see T-Mobile Wifi Calling in the status bar on the lock screen, and when I put it on airplane mode with wifi on I can't make calls or send texts. I've read that sim status should change to IWLAN, but mine still shows LTE.
I've rebooted after turning on all settings. Turned wifi calling off and back on.
I've turned wifi calling on and set to wifi preferred.
I've updated my e911 address.
I've seen one other person with similar issues. Wouldn't be because I'm unencrypted/rooted/etc. Does airplane mode have to be off in order to work? Is there a better way to test this or know its working?
Are you on your home WiFi?
I'm not a nexus user but a Galaxy S5 user, I experienced this on certain WiFi networks like at work.
I also flashed a fresh image of the latest software and could not get it to work. This was at my home network. My wife's WiFi calling works perfect on her S6 so I know its not my router.
Even if WiFi is set preferred, mine seems to only switch if it drops off of LTE or the LTE signal is weak. At home, 70% of the time I've been on WiFi calling, with the rest of the time on good ol' cellular.
The calls are still negotiated over the cellular control channel, so if Airplane mode is on, you won't be able to make or receive calls.
edit: the above sentence is incorrect. I don't know why it didn't work for me at first, but it's working now. Calls can be placed on WiFi solely.
Same here with this build.... I'm where I would prefer having it.
ignitionnight said:
This is going to be embarrassing if I'm missing something easy and obvious, but I've done as much as I can think of. I can't seem to get wifi calling to work. I just flashed the LYZ28E factory image and used wugfresh's modified boot to disable encryption, I'm also rooted with supersu. I don't see T-Mobile Wifi Calling in the status bar on the lock screen, and when I put it on airplane mode with wifi on I can't make calls or send texts. I've read that sim status should change to IWLAN, but mine still shows LTE.
I've rebooted after turning on all settings. Turned wifi calling off and back on.
I've turned wifi calling on and set to wifi preferred.
I've updated my e911 address.
I've seen one other person with similar issues. Wouldn't be because I'm unencrypted/rooted/etc. Does airplane mode have to be off in order to work? Is there a better way to test this or know its working?
Click to expand...
Click to collapse
I have read in numerous forums that disabling encryption is breaking the WiFi calling. Try it again without flashing wug's boot image.
TheAmazingDave said:
The calls are still negotiated over the cellular control channel, so if Airplane mode is on, you won't be able to make or receive calls.
Click to expand...
Click to collapse
I don't think this is true. The whole point of Wifi calling is to be able to call when you have no cell signal.
xxfwmxx said:
I have read in numerous forums that disabling encryption is breaking the WiFi calling. Try it again without flashing wug's boot image.
Click to expand...
Click to collapse
I have encryption enabled and having the same issue.
andy o said:
I don't think this is true. The whole point of Wifi calling is to be able to call when you have no cell signal.
Click to expand...
Click to collapse
Sir, you are correct. I based that statement on my experience of not being able to place a call on WiFi alone originally after the update. I just tried it again though, and it worked. Strange it didn't work before, but no matter. I'll append my post above.
Do any of you have a prepaid plan? I got the 5GB 100 minute $30 plan, maybe that's it?
Edit: although wifi calling with prepaid plans works fine on other phones.
esjames said:
Are you on your home WiFi?
I'm not a nexus user but a Galaxy S5 user, I experienced this on certain WiFi networks like at work.
Click to expand...
Click to collapse
Yup home wifi.
xxfwmxx said:
I have read in numerous forums that disabling encryption is breaking the WiFi calling. Try it again without flashing wug's boot image.
Click to expand...
Click to collapse
I've talked to two people who are having the same issue while unencrypted. I wasn't looking forward to reflashing again but gave it a shot. It does work now, guess I'll have to get over my placebo effect of thinking I can notice a difference between encrypted/unencrypted.
Wonder if there will be a way to get around this in the future, don't particularly care to be encrypted and I will definitely want to use custom kernels.
ignitionnight said:
I've talked to two people who are having the same issue while unencrypted. I wasn't looking forward to reflashing again but gave it a shot. It does work now, guess I'll have to get over my placebo effect of thinking I can notice a difference between encrypted/unencrypted.
Wonder if there will be a way to get around this in the future, don't particularly care to be encrypted and I will definitely want to use custom kernels.
Click to expand...
Click to collapse
I don't think it's the encryption. Are you sure wugfresh's tool have the latest T-mo unencrypted kernel? In my case, I flashed the new boot.img and it started encrypting my phone, I had assumed that it had also flashed the kernel, but it had not. After reading your post I checked and my kernel still was dated in January, so I just flashed the boot.img again, and now it's the new one (3.10.40-g8887dbc dated Mar 20 15:56:38 UTC). Maybe you just need to wait until the kernel is modified for not forcing encryption.
andy o said:
I don't think it's the encryption. Are you sure wugfresh's tool have the latest T-mo unencrypted kernel? In my case, I flashed the new boot.img and it started encrypting my phone, I had assumed that it had also flashed the kernel, but it had not. After reading your post I checked and my kernel still was dated in January, so I just flashed the boot.img again, and now it's the new one (3.10.40-g8887dbc dated Mar 20 15:56:38 UTC). Maybe you just need to wait until the kernel is modified for not forcing encryption.
Click to expand...
Click to collapse
Maybe I'm misunderstanding the difference between the kernel and the boot.img. I was under the impression that the kernel was in the system.img, I was using the stock kernel. The only thing that was modified was the boot.img that I was using to turn off encryption, I didn't think the kernel mattered. I'm not too much of a noob, but I'm far from an expert so let me know if I'm wrong All I know is I was definitely unencrypted and wifi calling wasn't working.
Here's the modified boot.img that was downloaded via the wugfresh toolkit, I flashed everything manually with fastboot/adb though (I only keep the toolkit as backup just in case).
https://drive.google.com/file/d/0BxkNfETYeJqSZkFvX2t6cmFNNWs/view?usp=sharing
ignitionnight said:
Maybe I'm misunderstanding the difference between the kernel and the boot.img. I was under the impression that the kernel was in the system.img, I was using the stock kernel. The only thing that was modified was the boot.img that I was using to turn off encryption, I didn't think the kernel mattered. I'm not too much of a noob, but I'm far from an expert so let me know if I'm wrong All I know is I was definitely unencrypted and wifi calling wasn't working.
Here's the modified boot.img that was downloaded via the wugfresh toolkit, I flashed everything manually with fastboot/adb though (I only keep the toolkit as backup just in case).
https://drive.google.com/file/d/0BxkNfETYeJqSZkFvX2t6cmFNNWs/view?usp=sharing
Click to expand...
Click to collapse
The kernel and the ramdisk are in the boot.img. Wifi calling ability is in all likelihood in the kernel. According to the file name it's the correct build version though, but the sizes vary significantly at 8,338KB for the modified img and 7,442 for the original boot.img, but this could be because of repacking. Someone who knows better might chime in. I followed this to check the version, and it matches (Linux version 3.10.40-g8887dbc). It's weird that they would disable wifi calling for unencrypted devices though.
I don't know if this will help with the issue of the LYZ28E update not switching to T-Mobile WiFi calling for others, but let me share what is happening with my Nexus 6.
I'm running LYZ28E and no encryption (kernel dated Mar 20 15:56:38), and sure enough my phone isn't giving any indication in the status bar that it has switched to WiFi calling. I noticed this morning that the quick setting menu (which I never use - I pulled it down by accident) shows "T-Mobile WiFi Calling" below the signal strength indicator. I just received a call (at home), and my T-Mobile routers LED's began flashing very rapidly while I was on the call, and went back to a slow flash immediately as I ended the call. So it looks like my phone is indeed using WiFi calling. If it will help you gentlemen, it's not encrypted and obviously rooted, everything is stock, and it gives absolutely no other indication that I'm using WiFi other than in the quick setting menu. I have very little cell signal (if any) at home, and there is no way I could have made a cellular call if the phone wasn't on WiFi. I hope this might be the case for others, and perhaps it may just not be indicating WiFi calling is really working.
For others folks that WiFi calling is working for, do you see the "T-Mobile WiFi Calling" in the status bar, or how does it let you know it switched over to WiFi?
bob110011 said:
I don't know if this will help with the issue of the LYZ28E update not switching to T-Mobile WiFi calling for others, but let me share what is happening with my Nexus 6.
I'm running LYZ28E and no encryption (kernel dated Mar 20 15:56:38), and sure enough my phone isn't giving any indication in the status bar that it has switched to WiFi calling. I noticed this morning that the quick setting menu (which I never use - I pulled it down by accident) shows "T-Mobile WiFi Calling" below the signal strength indicator. I just received a call (at home), and my T-Mobile routers LED's began flashing very rapidly while I was on the call, and went back to a slow flash immediately as I ended the call. So it looks like my phone is indeed using WiFi calling. If it will help you gentlemen, it's not encrypted and obviously rooted, everything is stock, and it gives absolutely no other indication that I'm using WiFi other than in the quick setting menu. I have very little cell signal (if any) at home, and there is no way I could have made a cellular call if the phone wasn't on WiFi. I hope this might be the case for others, and perhaps it may just not be indicating WiFi calling is really working.
For others folks that WiFi calling is working for, do you see the "T-Mobile WiFi Calling" in the status bar, or how does it let you know it switched over to WiFi?
Click to expand...
Click to collapse
Rooted, but otherwise stock. Mine shows WiFi Calling on the lockscreen next to T-Mobile, in the quick settings shade as you've mentioned, and on the dialer when in a call.
Oops, I totally forgot about the lock screen, I don't use it, I just turn off the screen. Mine does in fact have the "T-Mobile WiFi Calling" indicator there (text). Thanks Dave.
bob110011 said:
Oops, I totally forgot about the lock screen, I don't use it, I just turn off the screen. Mine does in fact have the "T-Mobile WiFi Calling" indicator there (text). Thanks Dave.
Click to expand...
Click to collapse
Yes, and also during the call there's an indicator on the screen. Where did you get your boot.img?
I noticed that when I'm on stock kernel (or boot.img maybe) WiFi calling works but on a custom kernel even those made for 5.1.1 it never switches to WiFi mode.
@ignitionnight I installed the no encrypt boot.img here http://forum.xda-developers.com/nex...ed-encryption-gain-root-t2946715/post61015828 and wifi calling is working. You'll also notice the size is very close to the original. I think something was wrong with the NRT file. FWIW, I tried the NRT yesterday and it detected the wrong TWRP and wanted to install its own boot.img when I already had those two installed.
Hey guys, so I might have a solution to the issue with WiFi calling not showing in the notification bar or during a phone call. I recently side loaded the new update and then rooted. After rooting I tried out WiFi calling and it worked flawlessly, notifications and all. Immediately after I modified the build.prop file to allow a miracast connection to my Xbox One. After realizing my WiFi calling wasn't showing up anymore I thought the miracast line may have messed with WiFi calling, so I deleted it from my prop file. I rebooted and you guessed it!! WiFi calling shows up in the pull down menu and during a phone call. So give it a shot and see if it works like it did for me. Best of luck
Mike
Related
There have been a few discussions about this, but I have yet to find a solution that works for me...
I flashed CM6 today and now I'm finding that when I enable wifi, my 3g data connection is lost. Not sure this is really a CM problem, I just want to find a fix.
My setup:
Nexus One - CM6.RC1 - FRF91
williec30 said:
There have been a few discussions about this, but I have yet to find a solution that works for me...
I flashed CM6 today and now I'm finding that when I enable wifi, my 3g data connection is lost. Not sure this is really a CM problem, I just want to find a fix.
My setup:
Nexus One - CM6.RC1 - FRF91
Click to expand...
Click to collapse
what do you mean it's lost.. when you're turning Wifi on, that's the whole point (that you want to use your Wifi connection for data, and not your mobile 3G data.) Maybe I'm not understanding you?
pakraider said:
what do you mean it's lost.. when you're turning Wifi on, that's the whole point (that you want to use your Wifi connection for data, and not your mobile 3G data.) Maybe I'm not understanding you?
Click to expand...
Click to collapse
Even with wifi on you still need 3g data to send and receive MMS. I can't replicate this problem, though, so I'm afraid I'm not much help. All I can suggest is trying a full wipe of everything but battery and rotate stats and try to flash it again. See if that helps.
It works fine for me. Are you sure you are confussing not having both icons in the notification bar with 3g being off?
I answered this question a few months ago too.
Your 3g is not lost, it just hides the icon. Go into settings and look what network you are still connected to for yourself, it will still say 3g. If you were to send or receive an mms the 3g icon would briefly pop up, send the message, then disappear. Your phone is working just fine
thanks for the help... @roger, you are correct, i didn't realize that the icon was hidden vs. actually turned off, nor did i think to go check the actual service rather than rely on the icon
I just did the 4.3 OTA update and my WiFi keeps turning on and off on the phone. It loses connection and reconnects once a minute. Any ideas?
Oxrod said:
I just did the 4.3 OTA update and my WiFi keeps turning on and off on the phone. It loses connection and reconnects once a minute. Any ideas?
Click to expand...
Click to collapse
Took the OTA yesterday and I am not having that happen to me at all.
No issues here.
UPDATE:
Its not just my Wifi. Its the 3G too. All data drops out and connects again about once a minute. Spent an hour on the phone with Sprint. They tried everything including a wipe and hard software reset and still the issue is there. Only thing I can think of is that they snuck in some optimizing software or something. Either way, I now will need to go to a corporate sprint store. Really do not want to replace this phone that I have had for 27 days with a refurb, so any ideas will be welcomed.
Oxrod said:
UPDATE:
Its not just my Wifi. Its the 3G too. All data drops out and connects again about once a minute. Spent an hour on the phone with Sprint. They tried everything including a wipe and hard software reset and still the issue is there. Only thing I can think of is that they snuck in some optimizing software or something. Either way, I now will need to go to a corporate sprint store. Really do not want to replace this phone that I have had for 27 days with a refurb, so any ideas will be welcomed.
Click to expand...
Click to collapse
I was having the same issue, do you live in an area with 4G? I don't and I think it was the cause. I think my phone was 'programmed' to think there was 4G around, but there wasn't. I kept seeing eHRPD under network info. I think it might be a 4.3 bug, bc I went back to Viper and it worked fine. Not really sure, but Amazon replaced my phone and now I'm scared to go back to 4.3 and get plagued with the bug again. I also think the new radio gave me issues, so I downgraded to the original radio also
This happened to me, it was a mixture of a damaged N antenna and bad sprint lte performance. Reverting to a g router fixed the problem for me. You should try a different router. Now fixing your regular signal, that's something you'll have a tough time with. I recommend you go to a sprint store and get a replacement asap though, my suggestion is not a fix, just a temporary measure. Curious, did you try the GPE rom by team nocturne? This issue started once I reverted from the TN GPE rom to stock. I think that rom may have damaged my radio/antenna. It's just a far fetched theory but plausible nonetheless. And a risk I took willingly, but still, I'm just curious to clarify if it was tinkering or sh*tty htc components.
I personally think it is just 4.3. I didn't have any issues with 4.1.2 with my WiFi or connectivity. I've even tested it and my WiFi drops like crazy only on 4.3 but is fine on 4.1.2, so I reverted back and haven't had any issues.
Mouahmong said:
I personally think it is just 4.3. I didn't have any issues with 4.1.2 with my WiFi or connectivity. I've even tested it and my WiFi drops like crazy only on 4.3 but is fine on 4.1.2, so I reverted back and haven't had any issues.
Click to expand...
Click to collapse
I found this just now.. towards the bottom there's a dialer code *#*#4636#*#* if you do that and change to gsm/wcdma/lte (something like that) it resolved my problem with 3G not working. Wifi might be my router
I have looked in the settings and sometimes the power saver will automatically shut 3G of it will not reconnect with a disconnected I switch to LTE / CDMA only have had no issues and also the wifi is meant to do that to conserve battery you should be able to disable the wifi in advance I'm not short just my thoughts
Sent from my HTCONE using xda app-developers app
Idk. In 4.3 all my settings were correct (*#*#4636#*#*) and I turned all battery conservation off and my data (3g and WiFi) would cut out intermittently while I was using it. I've tried that on stock and all other 4.3 ROMs, I think it might just be my phone not liking 4.3, but YMMV. Stuck on 4.1.2 until I get the Note 3.
It's a power save feature if you have enabled Power Saver. Basically if you haven't used the connection in a while it turns it off until the next scheduled update check or your screen turns back on.
I have been having the same exact issue and it is driving me nuts. I have problems at home, work and anywhere else I use Wifi so it is not just one router. I have tried numerous 4.3 roms and was about to roll back to 4.1.2 to see if that fixes it.
Was starting to think that I was crazy, glad I saw this post!
I'd hate to be (just kidding, I love being) the smart alec here, but your post title says "Wii turning on and off." I clicked on this thread wondering how your phone update was turning your Wii on and off.
I'm having the same problem after the update. Wifi turns on n off, so will my 3g/4g while I'm using it. Didn't have this problem before the update so I doubt it's hardware related.
Sent from my HTCONE using XDA Premium 4 mobile app
Same here. I assumed it had something to do with the fact that they're working on lte in my area.
UPDATE:
At work (50 minutes from home) the 3G and Wifi spots I try are working fine. No strobe connection. But at home both Wifi and 3G blink. I know they are working on the antenna near home, so it must be the issue. Have tried shutting off mobile data while on wifi, tried both wifi antennas at home, can't seem to get the strobe effect to go away.
SlimWadey said:
I'd hate to be (just kidding, I love being) the smart alec here, but your post title says "Wii turning on and off." I clicked on this thread wondering how your phone update was turning your Wii on and off.
Click to expand...
Click to collapse
Yes, I messed up typing Wifi. At least with Wii up there get grabs people's attention.
Is anyone having signal issues with the axon pro? My phone keeps going in and out of signal, and while my status bar says that I have "no service" I will have full bars, but only when connected to WiFi. When not connected to WiFi, all the bars are lost.
Is anyone else experiencing these signal issues or bug of this sort? Just trying to determine the root of the problem.
Sent from my A1P using Tapatalk
When did you start having problems? After the latest update?
I think it is a problem with the Wifi calling feature. After trying wifi calling and having problems (the other person couldn't hear me), I decided to turn it off.
After turning it off I started having crazy issues - the wifi calling would turn on even though I had turned it off. After turning off wifi completely, data wouldn't work so I rebooted the phone. After rebooting the phone, I couldn't get a signal at all. I tried rebooting the phone multiple times but the signal wouldn't come back. I switched SIMs and it still wouldn't work. At this point I was thinking there was a hardware problem with the phone so I was considering calling ZTE to get a new one. But I tried one last thing - I turned wifi back on and made a wifi call - the signal came back! So it is a software problem.
So I turned on wifi calling again but configured for "cellular preferred". It seemed to work well for a while, but then a few days later went crazy notifying me every few seconds that wifi calling was turning on/turning off.
To keep the phone stable I have now unfortunately had to setup the phone with "Wifi Calling Preferred". Thankfully soon after I did this I started getting error "REG09: Missing 911 address" so it doesn't try to use wifi calling anymore.
No point calling ZTE support because their phone support is appallingly bad. They won't understand the issue, they won't give me a ticket number. All they will say is either "reset the phone" or try to send me a new phone which will just make me lose time and lose data. They had a website where you could raise tickets for a little while...but it looks like it has been blocked now as it could have been too useful .
gflash2015 said:
When did you start having problems? After the latest update?
I think it is a problem with the Wifi calling feature. After trying wifi calling and having problems (the other person couldn't hear me), I decided to turn it off.
After turning it off I started having crazy issues - the wifi calling would turn on even though I had turned it off. After turning off wifi completely, data wouldn't work so I rebooted the phone. After rebooting the phone, I couldn't get a signal at all. I tried rebooting the phone multiple times but the signal wouldn't come back. I switched SIMs and it still wouldn't work. At this point I was thinking there was a hardware problem with the phone so I was considering calling ZTE to get a new one. But I tried one last thing - I turned wifi back on and made a wifi call - the signal came back! So it is a software problem.
So I turned on wifi calling again but configured for "cellular preferred". It seemed to work well for a while, but then a few days later went crazy notifying me every few seconds that wifi calling was turning on/turning off.
To keep the phone stable I have now unfortunately had to setup the phone with "Wifi Calling Preferred". Thankfully soon after I did this I started getting error "REG09: Missing 911 address" so it doesn't try to use wifi calling anymore.
No point calling ZTE support because their phone support is appallingly bad. They won't understand the issue, they won't give me a ticket number. All they will say is either "reset the phone" or try to send me a new phone which will just make me lose time and lose data. They had a website where you could raise tickets for a little while...but it looks like it has been blocked now as it could have been too useful .
Click to expand...
Click to collapse
Trying posting to their Twitter account and report the issue, that is how i got their attention. Also when you call them (here in the USA) tell them that you have already done a reset on your phone and that did not resolve the issue!!!
gflash2015 said:
When did you start having problems? After the latest update?
I think it is a problem with the Wifi calling feature. After trying wifi calling and having problems (the other person couldn't hear me), I decided to turn it off.
After turning it off I started having crazy issues - the wifi calling would turn on even though I had turned it off. After turning off wifi completely, data wouldn't work so I rebooted the phone. After rebooting the phone, I couldn't get a signal at all. I tried rebooting the phone multiple times but the signal wouldn't come back. I switched SIMs and it still wouldn't work. At this point I was thinking there was a hardware problem with the phone so I was considering calling ZTE to get a new one. But I tried one last thing - I turned wifi back on and made a wifi call - the signal came back! So it is a software problem.
So I turned on wifi calling again but configured for "cellular preferred". It seemed to work well for a while, but then a few days later went crazy notifying me every few seconds that wifi calling was turning on/turning off.
To keep the phone stable I have now unfortunately had to setup the phone with "Wifi Calling Preferred". Thankfully soon after I did this I started getting error "REG09: Missing 911 address" so it doesn't try to use wifi calling anymore.
No point calling ZTE support because their phone support is appallingly bad. They won't understand the issue, they won't give me a ticket number. All they will say is either "reset the phone" or try to send me a new phone which will just make me lose time and lose data. They had a website where you could raise tickets for a little while...but it looks like it has been blocked now as it could have been too useful .
Click to expand...
Click to collapse
Those are precisely the issues I am having as well
Sent from my A1P using Tapatalk
I got some signal issues too I only get 2 to 3 tower usually but at time its completely dead and until I reboot my phone signal doesn't Pop up ...and at times even though I have like 2 signal tower it shows emergency calls oly...I don't use WiFi calling as am on straight talk.but the WiFi calling feature suddenly pops up in the notification bar giving an error message u can't swipe that off the notification bar too u gotta go to MORE in settings and switch on and switch off the WiFi calling feature to remove the error msg from the notification bar .
Signal keeps fluctuating call clarity is a lil bit poor comparing it to my old lg g2 . macro focus doesn't work at all u can't focus a thing that's really close in auto. I dono what to do with this phone.it just doesn't satisfy the basic need of a phone voice calls and message(messages take a long time to send ).
vickytarunl said:
....but the WiFi calling feature suddenly pops up in the notification bar giving an error message u can't swipe that off the notification bar too u gotta go to MORE in settings and switch on and switch off the WiFi calling feature to remove the error msg from the notification bar .....
Click to expand...
Click to collapse
I see the same issue. I have created a thread for it. Not sure how widespread the issue is
http://forum.xda-developers.com/zte-axon/general/wifi-calling-notification-issues-b25-t3290959
Coldheat1906 said:
Trying posting to their Twitter account and report the issue, that is how i got their attention. Also when you call them (here in the USA) tell them that you have already done a reset on your phone and that did not resolve the issue!!!
Click to expand...
Click to collapse
Again, not worth my breath. If you check the new thread someone called up ZTE about the issue and they blamed it on T-Mobile (which is complete and utter BS). When I called about the camera issues they tried to blame it on Google. Why waste my time to be told lies? The support is completely s***.
gflash2015 said:
Again, not worth my breath. If you check the new thread someone called up ZTE about the issue and they blamed it on T-Mobile (which is complete and utter BS). When I called about the camera issues they tried to blame it on Google. Why waste my time to be told lies? The support is completely s***.
Click to expand...
Click to collapse
Well hopefully ZTE will come out with a fix really soon, I don't think that they want to lose the users they have.......
Loss of at&t signal
In one location that I frequent I always sit there without a cellular signal while people around me are using their cell phones
LTE signal strength sporadic
My Pro shows a few bars for a couple seconds,then NO SIGNAL for a few seconds. ZTE is not fixing this problem? It has been going on since January. Now is September.
For those with this issue, does a factory reset change this behavior, or at least the frequency of it?
Not exactly certain where to post this (as I am not altogether certain the cause) so if mods have a suggestion to move it let me know.
I have a rooted Tmobile S6 (not rhe edge) running Sick as Hell custom Rom version X w/ Unikernel v9.
Periodically my WiFi signal will display the ER041 - DNS (or less frequently the ER081) error which I believe is related specifically to WiFi calling.
My GF has the exact same phone and the same setup (I think she has WiFi calling enabled as well).
I have run some tests previously where I turned WiFi calling off and still had hiccups with the WiFi (both home and at work).
It seems that when I clear the cache and reboot the issue resolves itself but only short term before I have to do it again.
No one else in the house is having WiFi issues such as me and I cannot seem to figure out if there is a setting that is throwing things off or what.
Any help is greatly appreciated.
Mine does this too but it usually clears itself up within a minute or two.
OP, check your IP address to see if your phone is getting an IPv4 address. I don't know why, but my phone was having major issues with this. I still haven't figured out exactly what the issue was; I was on Sow Nice, flashing back to stock solved the problem. The phone was getting an ipv6 lease, just not ipv4, for no apparent reason.
If that doesn't help, I would advise setting network configuration manually. However if ipv4 isn't working, this may not solve the issue.
WiFi Issues
Alright gang I need some brainstorming...and curious if any other T-mobile Galaxy S6 users are experiencing this issue. I don't believe it is ROM related but thought I'd post the inquiry in here anyhow.
Specs:
T-Mobile Galaxy S6 (SM-G920T) rooted with Sick as Hell X and Unikernel v9.1.
Baseband: G920TUVS3DOJC
Issue:
WiFi is intermittent (both work and at home). WiFi will be running fine on this device and also on my Kindle Fire and at some point WiFi on my S6 will stop working. The WiFi icon will still appear and the up/down arrows will flash but I can't pull up Google search results, YouTube videos, etc.
I get a ER041 - DNS error which is related to wifi calling but I think this issue is in fact DNS related (I've googled and googled and am just not entirely certain, if it is DNS related, exactly how to change settings to thwart this issue going forward).
If I run a speedtest I will get a "Network Communication Issues" message. If I turn off WiFi and then turn it back on the connection is still broken.
HOWEVER, if I clear the cache and reboot the phone, it will connect to WiFi for a period of time until the connection gets broken once again.
My phone seems to be the only device experiencing this issue. I have booted into Safe Mode and the issue still occurs so it doesn't appear to be app related. The Smart Network switch has always been off as well so I know that isn't the culprit.
At work I'm not going to be able to check the router settings but obviously I can at home (at home 4 other users connect to WiFi no problem).
There has got to be some sort of tweak/button/setting that I'm just not catching that is causing this. It is irksome.
I recently did a factory reset but the issue is still persistent. Scanning the interwebs this seems to be a pretty common issue with the S6 and Lollipop.
Any ideas??
socal87 said:
OP, check your IP address to see if your phone is getting an IPv4 address. I don't know why, but my phone was having major issues with this. I still haven't figured out exactly what the issue was; I was on Sow Nice, flashing back to stock solved the problem. The phone was getting an ipv6 lease, just not ipv4, for no apparent reason.
If that doesn't help, I would advise setting network configuration manually. However if ipv4 isn't working, this may not solve the issue.
Click to expand...
Click to collapse
Ya lost me on the IPv4 ipv6 lease jargon.
WiFi issued are 99% kernel related
The Sickness said:
WiFi issued are 99% kernel related
Click to expand...
Click to collapse
Hmmm...well then, Twisted v7.1 has yet to settle in so I guess I can let it ride for a couple days and see how things go.
Thanks bud
cwhiatt said:
Hmmm...well then, Twisted v7.1 has yet to settle in so I guess I can let it ride for a couple days and see how things go.
Thanks bud
Click to expand...
Click to collapse
Keep in mind, the other kernels are international
source.
EDIT.... also uni kernel adds a default.prop in system that has ro.securestorage=false when it needs to be set to true for USA devices
I'd say at this time I can rule out the kernel (it's a been a few days now running Twisted v7.1). I honestly think it is a Samsung bug. Not just S6 users but Galaxy S7 users are now reporting the issue as well (there is a thread over at AndroidCentral).
Just like myself, those users are reporting that Smart Network switch and Blutetooth and the like are turned off/disabled and yet the problem persists.
I've had WiFi issues on an s6 edge. But I figured it out that if I'm near my microwave and it's on WiFi dies on the phone. Soon as the microwave goes off it works fine ?
ShinySide said:
I've had WiFi issues on an s6 edge. But I figured it out that if I'm near my microwave and it's on WiFi dies on the phone. Soon as the microwave goes off it works fine
Click to expand...
Click to collapse
Huh. Not the case in my situation. I've got a microwave but it's in the basement and rarely used.
I ended up going back to stock and taking the updates. The lack of development for the Verizon S6E basically did me in. :crying: I activated the advanced calling and the wifi calling option and I took a call and noticed the icon in the top left of the phone screen. After that call, when I am connected to wifi and making a call the icon has disappeared. I have performed a cache wipe and did a factory reset to no avail. I also tried to toggle the wifi calling feature on and off and I still do not see the icon. Anyone with a similar issue or that can help? Thanks!
If I remember right, the WiFi calling will only work as needed. So I don't think it will always be on.
I may be wrong though.
Thanks, I was wondering whether it determines which route will result in better connectivity. If anyone else has an idea about this I'd be happy to hear!
Yeah it only uses wifi if you have very low signal and strong wifi, or no signal and wifi.
Thanks, I figured it is operational by just going to airplane mode and switching on wifi. Icon came back and calls successful over wifi. Much thanks.