I've noticed that the profile for my home wifi network keeps getting disabled. Usually, I'll leave for a bit, then come back and about half the time it never reconnects. When I go into the wifi list, it's marked as disabled. I enable it and it works fine from that point unless I leave again. It's my understanding a profile will get disabled when it cannot connect to a network for some reason, but clearly it can. My G2 and SGS never have this problem. Is this a setting somewhere? Thanks...
I am having this same issue. I dont know how to fix it
This is more serious than I realized! I just got disconnected randomly even while staying in perfect coverage. Not only does it disconnect, but it DISABLES the connection and won't reconnect again unless I manually tell it to. I rely 100% on WiFi calling while home and now I'm missing all kinds of calls and texts because WiFi is disconnected...
I'm hoping this is just is a software issue that can be resolved pretty quickly, officially or unofficially...
This phone has like 10 legit problems already. Tmobile needs to hurry up with the updates or the refunds will kill them.
It might help if you talk about the router you're using. I have a Netgear N600 and haven't had any Wi-Fi issues either connecting, staying connected, or automatically reconnecting. Bluetooth on the other hand...
BarryH_GEG said:
It might help if you talk about the router you're using. I have a Netgear N600 and haven't had any Wi-Fi issues either connecting, staying connected, or automatically reconnecting. Bluetooth on the other hand...
Click to expand...
Click to collapse
It's a Linksys WRT610N. Very modern and very stable router. There's no reason this phone should have any problem with it. I literally have a G2 and SGS sitting side-by-side with the G2x and only the G2x has this problem. The SGS is Froyo and the G2 is Gingerbread. I also have a slew of other wireless (on both 2.4ghz and 5.8ghz bands) and wired clients connected that all have zero issues. I don't know why it would work on one router and not the next...
Are you using WPA2-AES encryption or something else?
zaventh said:
Are you using WPA2-AES encryption
Click to expand...
Click to collapse
Yes. And you're right, the phone is very temperamental across a number of areas.
Did you set up your wifi to never go to sleep? Cause if you havent - it disconnects every time you turn off the screen.
In order to do that, go to Settings=>Wireless & Networks=>Wi-Fi Settings=> click on the "menu" button on your phone=> Advanced=> Wi-Fi sleep policy=> and choose Never.
I did that, and my wifi calling is flawless ... and I rely on it pretty much all the time that I am at home (thanks for that stupid t-mobile signal)
I have the same issue and the setting I have by default to Never go to sleep... Also, has nothing to do with router as any of my other phones have this issue including Nexus One.
Did by any chance any of you with this issue restore some Titanium Back-ups? Because when I restored mine from a back-up of my 1st G2x (exchanged) I also restored the previous wi-fi settings and after that the wi-fi wouldn't work correctly. I did a factory reset and it fixed the problem.
Edit: If all else fails, then try a factory reset. I know it sucks, but it could fix everything.
Sent from my LG-P999 using XDA App
I'm having issues with this as well. Wifi set to never sleep, I haven't restored any apps. I constantly lose connection. I've tried the factory reset thing etc. and it doesn't help.
I can connect to my wireless g Linksys access point but not my airport extreme ... my Linksys is open my ape is not(I realize I wrote ape LOL)
Sent from my LG-P999 using Tapatalk
WiFi seems to be losing dns services
I have the same WiFi problems and while a factory reset clears the problem
temporarily and changing the WiFi sleep setting to never is an immense help
once it's gone off-line I can't get it to come back.
I have noticed that if it has a cached dns lookup to an ip address that that
ip address is still accessible. So if you can get OTA data live, look up google.
Switch to wifi, google is still accessible and you can do queries but you can't
click through on the links because the dns lookup fails.
I've fiddled with killing myaccount, suggested elsewhere, without success.
Unless there is some robust configuration change that pops up soon I suppose
I'll have to return it...
boylan said:
I have the same WiFi problems and while a factory reset clears the problem
temporarily and changing the WiFi sleep setting to never is an immense help
once it's gone off-line I can't get it to come back.
I have noticed that if it has a cached dns lookup to an ip address that that
ip address is still accessible. So if you can get OTA data live, look up google.
Switch to wifi, google is still accessible and you can do queries but you can't
click through on the links because the dns lookup fails.
I've fiddled with killing myaccount, suggested elsewhere, without success.
Unless there is some robust configuration change that pops up soon I suppose
I'll have to return it...
Click to expand...
Click to collapse
Did you also uninstall market updates and freeze the market updater?
It got mine working again without any problems. Sucks that this has to be done to get wifi to work properly.
I've frozen MyAccount and WiFi calling and it's working at the moment.
Truely I was a little tired and forgot about the market updates until I got
back here.
Insane that one has to do something like this for such a basic feature.
I mean who is going to use the OTA networking when wifi is available?
Let alone the cost issues. I went from 880kbps to 10100kbps going from
OTA to wifi.
This device must have rushed out the door.
Useless at any speed
So I've uninstalled the updates to and FROZEN:
My Account
Market Updater
WiFi Calling
AppPack
and the phone is still trippy. I've discovered also (via the engineering menu)
that the networking ping test fails - "network unreachable". The wifi
data looks good but it doesn't show the current gateway or dns configuration
information.
I'm at a loss for what to try next. Anyone got any suggestions?
Is there something like a netstat android app?
I am having the SAME issue as well as the OP..... =/
wifi recovery
Too soon to say that this is a consistent work-around but I'm
having some short term luck with
rebooting the phone (remove battery) in Airplane mode
enabling wifi
turning airplane mode off
Not sure if the battery pop is necessary. I suspect it's not.
I also suspect that freezing/deinstalling the various updates
is pointless.
Probably the whole work-around is to change the
Wi-Fi sleep policy to never:
settings->wireless & network settings->Wi-Fi settings->advanced
and use the airplane/wifi enable reboot sequence.
If someone has a permanent work-around based on precise setup
sequence and freezing applications I'd like to hear it - I think I've
followed the several posts on this topic and that path is unreliable but
it never hurts to be wrong.
dj75728 said:
Did by any chance any of you with this issue restore some Titanium Back-ups? Because when I restored mine from a back-up of my 1st G2x (exchanged) I also restored the previous wi-fi settings and after that the wi-fi wouldn't work correctly. I did a factory reset and it fixed the problem.
Edit: If all else fails, then try a factory reset. I know it sucks, but it could fix everything.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Mine does this and I never restored any system data. I only restored apps.
Strange.
I use WiFi calling at work with no problems. It is a Netgear router. I haven't had problems at home with my Linksys router either.
Hello all-
For the past couple days my wi-fi only xoom will not connect to wi-fi. I have tried multiples networks and nothing. When I hit connect and type in my network key( i have double checked and made sure I was typing in the right key) it constantly switches between scanning and connecting. I am not or ever have been rooted, and I have tried a factory reset still nothing. I am on 3.1 which was updated OTA not pushed to my xoom. Please help. I know if anyone can its the folks here at XDA. Thanks in advance for your help.
First thing I would do is disable all security on the network and see if it connects then, if it does then its not a hardware issue.
Remember to turn all the security on though when your done
I gave it a shot and still nothing. I tried connecting to my MyTouch hotspot and at Starbucks as well. Do you think the xoom is broken. I used to be able to connect no problem. This just started happening the last few days. Thanks!
OK so what's changed in the last few days then, any updates or app installs that might have screwed something up....?
Have you switched the Xoom off and on again?
If all else fails do a backup and reset the device..
Sent from my Xoom using XDA App
Not much has changed. I haven't installed any new apps in a month or so. As soon as the problem started happening I uninstalled all apps I had installed since i bought it. After that didn't work I did a factory reset. I really appreciate all your help on this.
I have a Samsung Focus v1.3 and it is dev unlocked. I decided to do the interop unlock/tethering hack and now I have problems with my wifi. The hack worked fine. I can connect to my network via wifi and get on the internet. It works for a few minutes but seems to just stop and not work after a few minutes or after my phone locks up. I can turn wifi off and on again and it works, but only temporarily. I have to use 3g now all the time and it is not an issue cause I have unlimited data but it's not as fast as my home network. I am wondering if anyone else has noticed this or if there is a setting that needs to be adjusted after I installed it. I also installed the advanced config tool but did not change any of the setting except to tell me when I have 3g+. I can change that back but the problem still exists. Any help would be appreciated, and thanks in advance. I can give more detailed information about my setup if needed.
i had a similiar issue on my hd7 after the last update that was released by htc. exact same issue with wifi. I ended up resetting to factory defaults and reload my apps/emails on and all is good . no more problems. you may wanna try doing that
Hey Guys,
I have been facing this issue ever since I started using mobile hotspot on 7.1.1.
It gets disconnected after some time (may be 15 minutes). When I check my phone , it shows as disabled. I have to then reenable it to use it.
Has anyone faced this issue ? I contact google support and they asked me to do Factory Reset. So, I wanted to see if anyone has some solution other than reset.
Hello,
I have a carrier unlocked Pixel 2 walleye that is rooted (magisk, no custom recovery) and on Verizon
android version 8.1.0
build #OPM1.171019.021
when I try to activate wifi calling, i get the spinning circle for a long time, and then it finally says "unable to activate wi-fi calling. please try again later"
I have HD voice activated on my verizon wireless account.
I tried the VoEnabler module in Magisk
Wifi calling is turned on in the phone info screen (*#*#4636#*#*)
The only thing i guess i haven't tried is installing a Verizon ROM instead of the stock Google ROM.
Before I went that route, I wanted to check here and see if anyone else was able to get it to work for them.
Thanks in advance.
ok so i had this issue twice on the same phone and i am rooted as well. i think the only way to get it to work is to disable root, activate wifi calling, then reactivate root.
I have enabled this feature while rooted on 2 different PIxel 2's.
This sounds silly but turn off wifi and try to activate it. I've been unable to input my address during the activation process multiple times unless I am on cellular.
thanks for the suggestions everyone. with wifi turned off, it still won't work. I'll try the unroot path next time there is a new system update. It's not a critical need at the moment, but it is rather annoying that i can't activate it.
Schedonnardus said:
thanks for the suggestions everyone. with wifi turned off, it still won't work. I'll try the unroot path next time there is a new system update. It's not a critical need at the moment, but it is rather annoying that i can't activate it.
Click to expand...
Click to collapse
I don't think your problem is related to root unless it's a Magisk module of some kind that's the problem. I'm on Verizon, rooted with Magisk. I haven't had wireless calling turned on but after seeing your post I thought I'd check and see if it works on mine. It connected without any problems for me.
Did you ever figure this out?
Schedonnardus said:
thanks for the suggestions everyone. with wifi turned off, it still won't work. I'll try the unroot path next time there is a new system update. It's not a critical need at the moment, but it is rather annoying that i can't activate it.
Click to expand...
Click to collapse
I'm having a similar issue, except that I can enable wifi calling but always get the "Turn off airplane mode or connect to a wireless network" message when attempting to place a wifi call. Everything with regard to wifi calling is set up correctly. I thought I had this narrowed down to Oreo version and patch level, but I honestly can't come up with a repeatable scenario that breaks it. About all I can say for sure is it seems like when I flash back to bone stock, OPM1.171019.021, wifi calling works as expected. However, it seems to break after a while, even without applying any updates. My gut says it's related to root, but I've also seen it work with root. I also have a suspicion it has something to do with the type of authentication on the wifi network, as the first time I ever saw wifi calling work was when I connected to an open SSID. The problem is, right after that, it worked fine on a WPA2 network on which it never worked before. This is on Verizon with a Pixel 2 from the Google Store. I have a hard time believing it's a Verizon issue, though. It's more like the phone does a check for wifi connectivity and returns "false" for some reason.
*** I should add all my testing has been done by turning on airplane mode (thus disabling LTE/3G) and then enabling wifi. My office at work has horrendous cell coverage, but I haven't gotten it down to zero bars without airplane mode to see if it works then.