I have a problem with my LG G2 D800 where it will not connect to wifi unless the screen is on.
Example: I arrive at home with phone, get on PC, log onto my router and monitor wireless clients. Phone screen still off. No phone on wifi. An hour later there is still no phone on wifi. I then turn on phone screen, I can see no wifi icon in top bar. After a second, wifi icon shows and connects and router shows the client.
I also have this same issue at work. As I walk around the building that is covered by different wireless APs, the phone will disconnect, then never reconnect to wifi until I turn the screen on.
During this time I am getting email notifications so it would still be using mobile data.
Tested with CM12.1 several different nightlies. Also with SlimSaber several versions and all perform the same.
I can very reliably cause this by connecting my phone to wifi, start ping to phone ip, then rebooting router. With these roms it will never connect to wifi without turning screen on. With CloudyG2 3.3 rom it will reconnect after a minute of router coming back up. Also my old Atrix HD and Asus TF201 connect quickly also.
I have taken it back to stock with Supersport's method http://forum.xda-developers.com/showthread.php?t=2663369. I then used Ioroot and AutoRec
I then tested with a full wipe of everything except internal storage and clean install of these roms. Kept all default settings and did NOT sign into Google, so no apps were restored/downloaded. Nothing running except what comes with the ROM and still have this issue.
I captured a logcat and below is the timeline.
Phone connected to wifi then screen turned off. Start ping
6:11 pm rebooted router - pings drop
6:12 pm router back online and other wireless devices connected
6:18 pm still no response from phone
6:23 pm turn screen on - see wifi connect - ping starts responding
Logcat
http://pasted.co/4fc50273
may be I could be wrong... but did you disable the "keep wi-fi on when screen is off" option in advance wi-fi settings ?
It is set to always stay enabled which is the default on all roms I have tested. The WIFI has no problems staying connected with the screen off, as long as I stay in range it will stay connected.
It is only when not connected and the screen off, it will never connect until screen is turned on. Like when I come home it will not connect to wifi until the screen is turned on. Even several hours after I got home.
Did you try any stock lollipop roms?
appsmarsterx said:
Did you try any stock lollipop roms?
Click to expand...
Click to collapse
Pure stock works as expected as does CloudyG2 3.3, which I believe is based on stock.
May be try dirty deeds rom?
http://forum.xda-developers.com/lg-g2/development/rom-dirty-unicorns-5-1-1-t3162408
Or blastagator's striped lp rom
http://forum.xda-developers.com/att-g2/development/rom-stock-lollipop-30b-stripped-t3144195
appsmarsterx said:
May be try dirty deeds rom?
http://forum.xda-developers.com/lg-g2/development/rom-dirty-unicorns-5-1-1-t3162408
Or blastagator's striped lp rom
http://forum.xda-developers.com/att-g2/development/rom-stock-lollipop-30b-stripped-t3144195
Click to expand...
Click to collapse
Forgot to add I also tried Blisspop and ResurrectionRemix and both have the same problem. All that I have problems with appear to be AOSP based so I would guess dirty deeds would also have the problem but the stripped stock LP would not.
I just don't know where to go from here to fix it. Like I said, I have taken it back to stock and went through entire process to get CM12.1 but have same issue.
Have you tried rebooting the wireless access point (i.e. Router/Modem)?
Look for interference near by on the same wireless channel, grab WiFi Analyzer from the play store and see if there's a stronger signal essentially jamming the wireless frequency.
I had a laptop that wouldn't stay connected to it's access point because a wireless printer was putting out a stronger signal on the same channel, the printer jammed the frequency causing the computer to disconnect.
If it's happening across multiple roms, then it seems like there are only two things in common; 1. the phone 2. the Router/Modem.
xNotta said:
Have you tried rebooting the wireless access point (i.e. Router/Modem)?
Look for interference near by on the same wireless channel, grab WiFi Analyzer from the play store and see if there's a stronger signal essentially jamming the wireless frequency.
I had a laptop that wouldn't stay connected to it's access point because a wireless printer was putting out a stronger signal on the same channel, the printer jammed the frequency causing the computer to disconnect.
If it's happening across multiple roms, then it seems like there are only two things in common; 1. the phone 2. the Router/Modem.
Click to expand...
Click to collapse
Rebooted router many times in testing.
I have to believe it is the phone/rom because it has the same issue at home, work, friends houses when running a rom like CM12.1. All with different router/AP combinations. I also have several other wireless devices at home that don't have issues. Specifically my Atrix HD and TF201 work fine on my home router.
I also don't believe it is a hardware issue with the phone because stock and stock based roms work as expected.
In asking around about these different roms, I seem to be the only one with this issue, but I don't know what I could be doing wrong.
I did find this in Nexus forum so it looks like it may be a global Google issue. http://forum.xda-developers.com/google-nexus-5/help/wifi-issue-t3059452
Related
My Epic will connect to my network and act as though everything's connected, and it can stay connected as long as I keep WiFi on, but it isn't loading anything over WiFi -- on the browser, it seems to attempt to load a page for about a minute before giving me a "Web page not available" error (on websites that I know are up), and any apps that use data simply give me a connection error. 3G works fine, and I can't comment on 4G as I'm not in a 4G area.
I haven't been able to test it on another WiFi network, though other WiFi devices connect to the network just fine; I'm typing this very post on another device connected to the laptop.
Has anyone else been experiencing this issue, and has a resolution been found? I've tried everything I can think of, from factory resetting, to completely reflashing the phone back to stock settings, and nothing has seemed to work. The WiFi did work at one point, but has stopped for whatever reason today.
Wifi
I actually have had the same issue here in Philadelphia and we have 4G coverage. This is what I have figured out so far. I have an app called "gas buddy" if I have 4G enabled it tells me there is no internet connection available. The minute I turn it off it works fine. I have seen similar issues with a couple of apps. Once i disable the 4G the apps in question work fine. I also noticed that I have to turn off the wifi radio button. I think the issue may be related to the app not having 4g settings yet. Make sure you disable the wifi and 4g settings and try that app again.
deleted post! Sorry wrong thread!
Well my first post was for a different thread but i may be able to help here. Sometimes the router or modem is to blame. The device is able to connect with the router but either the router is not allowing the device to actually get through to the internet, or the router is not. either way resetting the modem or router or both generally fixes this. sometimes when modems and routers (such as my current router) start to go bad it needs done quite a bit. Just unplug the power cord from the modem and router and wait about 5-10seconds to make sure the capacitors have drained. Then plug the modem in and wait for the lights to stabilize (stop flashing and stay lit) then plug the router back in and wait for you device (smartphone) to pick up the signal. If that is the problem, you should be back in business! hope this helps!
My wifi is spotty, at best. I've tried every ROM but every ROM has the same issues: wifi will work for awhile, then it won't, then I power the phone off, then it doesn't work after I power it back on, then I disable it and re-enable it, and it may/may not work. Basically, it's totally unreliable.
I AM running a 2.4 mouse/keyboard combo, but I've tried different channels on my router: 1,6,11 ... they all have issues. My router is a D-LINK 615 and supports 801.11b-n.
I have an iPhone and it is rock solid on the wifi; plays nicely with the keyboard and mouse and doesn't miss a beat. But I REALLY want my HD2 to work: it's more baddass!
Can anyone help me out?
by not working, could you be more detailed? coz if the problem is about wifi went to sleep state after you lock the phone, then there's a settings for that.
danxtian said:
by not working, could you be more detailed? coz if the problem is about wifi went to sleep state after you lock the phone, then there's a settings for that.
Click to expand...
Click to collapse
Where's the setting?... I must have missed it! I can restart the phone and get the wifi symbol, but the reception bars aren't fully lit... only the very lowest (I'm on a sense build now).
I go into wifi settings and it says 'connected' ... but I try to load the browser, or marketplace, or Amazon AppStore ... and I'm not connected. I disable wifi then I renable it and my wifi bar is full! And the wifi works for, maybe, 30-45 seconds before it doesn't work again.
Really, really odd. And this is how it behaves on all ROMs I've tried.
*EDIT* I just saw that my wifi sleep policy is set to 'never' go to sleep.
I just turned on "best wi-fi performance" but I have my doubts that it will work... and my battery is going to suffer, big time.
I suffer from similar symptoms.
Wifi will show as being connected (but sometimes the signal meter is obviously off), but things like the browser won't load. It'd be nice if wifi just dropped entirely (and then push notifications would work again), but it doesn't. It just doesn't work; it shows as being connected, but I can't load things.
If I disable/re-enable wifi, it works again.
I think most of the time (for me) the trouble is the result of going between different APs or coming back to an AP, but still sometimes problems occur even when I'm sitting still at a single place (I'm connected to a campus network, but I've had this problem happen on a 1-router network before too).
I've found that, overall, the g.lewarne kernel works really well after a few reboots (wifi sometimes still gets "stuck," but not as often...), at least better than Raf 1.9. But... problems still exist.
Hope you find a solution here! There have been several threads with this already...
Thanks! Help installing a new kernel...
linj said:
I suffer from similar symptoms.
Wifi will show as being connected (but sometimes the signal meter is obviously off), but things like the browser won't load. It'd be nice if wifi just dropped entirely (and then push notifications would work again), but it doesn't. It just doesn't work; it shows as being connected, but I can't load things.
If I disable/re-enable wifi, it works again.
I think most of the time (for me) the trouble is the result of going between different APs or coming back to an AP, but still sometimes problems occur even when I'm sitting still at a single place (I'm connected to a campus network, but I've had this problem happen on a 1-router network before too).
I've found that, overall, the g.lewarne kernel works really well after a few reboots (wifi sometimes still gets "stuck," but not as often...), at least better than Raf 1.9. But... problems still exist.
Hope you find a solution here! There have been several threads with this already...
Click to expand...
Click to collapse
Hrmm.... I've been searching high and low for a good kernel and was thinking it might be the issue. I found g.lewarne's kernel http://forum.xda-developers.com/showthread.php?t=917590 ... but I have no idea how to apply it to my current build: http://forum.xda-developers.com/showthread.php?t=1027768
Is it possible to apply the g.lewarne kernel to CME Desire HD2?
linj said:
I suffer from similar symptoms.
Wifi will show as being connected (but sometimes the signal meter is obviously off), but things like the browser won't load. It'd be nice if wifi just dropped entirely (and then push notifications would work again), but it doesn't. It just doesn't work; it shows as being connected, but I can't load things.
If I disable/re-enable wifi, it works again.
I think most of the time (for me) the trouble is the result of going between different APs or coming back to an AP, but still sometimes problems occur even when I'm sitting still at a single place (I'm connected to a campus network, but I've had this problem happen on a 1-router network before too).
I've found that, overall, the g.lewarne kernel works really well after a few reboots (wifi sometimes still gets "stuck," but not as often...), at least better than Raf 1.9. But... problems still exist.
Hope you find a solution here! There have been several threads with this already...
Click to expand...
Click to collapse
I just flashed g.lewarne's GL_CORE_V5 from here:
http://forum.xda-developers.com/showthread.php?t=917590&highlight=reboot
... I flashed the whole ROM and I'm getting zero wifi. Even with the other kernels I was able to get some wifi, but none with this one. I like the ROM look a lot, but nothing doing on the wifi front.
Anyone else have suggestions??
WPA vs WPA2
Make sure you set ONLY WPA and TKIP in your router settings... I have much more reliable wifi because of this.
Also, choose specific wifi channel ... channel 6 works for me, and I've seen channels 1 and 11 as recommended channels as well.
Mixed WPA/WPA2 and TKIP/AES modes were horrible for wifi
FYI!
My ROMs are working relatively well now... much better than mixed modes (no wifi working)
diznanl said:
Make sure you set ONLY WPA and TKIP in your router settings... I have much more reliable wifi because of this.
Also, choose specific wifi channel ... channel 6 works for me, and I've seen channels 1 and 11 as recommended channels as well.
Mixed WPA/WPA2 and TKIP/AES modes were horrible for wifi
FYI!
My ROMs are working relatively well now... much better than mixed modes (no wifi working)
Click to expand...
Click to collapse
Ah. Unfortunately I have little control over the wifi infrastructure on campus (I'm in a college environment). That said, I'm not connected to the WPA2 Enterprise ssid but the unencrypted one.
Good to hear you found a resolution!
I have found that WiFi works just as good as my laptop when I'm running Windows Phone 7. Much faster at connecting and can connect further to the edges of signal then Android. I wonder why this is.
Since the update, WiFi fails to connect to the Router after several starts (sleeps).
Upon entering the WiFi control panel, you notice it's stuck at "Obtaining IP Address" indefinitely.
The only way to resolve the problem seems to be to manually shutdown the WiFi and restart it again.
The problem reappears after several sleeps.
i have the same problem... whenever I wake my tf up I have to shut off then turn on the wifi. Annoying!
I always leave the wifi on as a result. Normally if I pull the power on my router, it'll fix it.
I had this initially at work when I first acquired the unit, but my Froyo phone couldn't get an IP either so I figured it was work related. Every day since then it has worked seamlessly everywhere.
Got the same issue, have to switch Wifi off and back on to fix it. Still running 3.0.1 though, hopefully this gets fixed. What versions are the previous posters using?
Not seeing an issue on mine. Running 3.1.
I had this issue too ever since flashing PRIME 1.4 and going from 3.0 to 3.1 but as time passed this happened less frequently and now it happens once in a long while. I believe (not sure though) that the update downgrades the wifi (drivers or whatever) version as some other things (gps too i think). maybe that causes the issue.
I've seen this also with my stock 3.1 16GB. Doesn't happen all the time, but enough to be annoying.
So I find it's best not to leave the tablet attached to the dock because of the dock battery draining issue, and now maybe it's best not to use the wifi power savings mode because of this problem.
I have been experiencing weird issues with the network I built at my own business. I have 4 pc's, a NAS and a printer connected to my router. Previously I had 2 pc's via direct connections into the router along with the NAS and printer and the other 2 pc's and my Galaxy S phone connected via wireless. The minute I introduced the Transformer to the network (after discovering the Transformer couldn't see channel 13 and having to change my router to a lower channel) I have had issues.
Everything would work fine until I used the Transformer on the network and then the wireless would go down within a matter of hours and be unresponsive until I rebooted. I eventually connected all pc's to the router via a powerline socket network and only had the phone and transformer via wireless as I needed the pc's connected reliably.
I have eventually found that the only way to have the wireless working fine is to either not use the Transformer at all with it or (the option I am using now) to have the router only use B & G ranges and to turn of N. I wonder if there is issues with the drivers for the wifi regarding the N standard (could be a stupid question but I know zero about network standards / drivers).
klau1 said:
Since the update, WiFi fails to connect to the Router after several starts (sleeps).
Upon entering the WiFi control panel, you notice it's stuck at "Obtaining IP Address" indefinitely.
The only way to resolve the problem seems to be to manually shutdown the WiFi and restart it again.
The problem reappears after several sleeps.
Click to expand...
Click to collapse
Same here......
Sent from my Transformer TF101 using XDA Premium App
Ive had this issue when I first got my TF with 3.0. It was still there after updating to 3.1. Someone here mention to set your wifi to static ip. I did and the problem is gone now.
Hey guys, the newest 3.2 update (not the first one but the second one that came out) messed up my Wifi and now I can't connect to it. I've turned off/one my roouter+modem, wifi on tablet, tablet itself, and re-added the network multiple times and nothing seems to work. What happens is that I add the network and it would try to connect and authenticate but then it just retries connecting again and then all the available wifi networks are gone. It's a mess. And it happened a few times where it would finally connect but then no webpage would open after a few minutes and the wifi bars on the bottom right turn from blue to grey. Wtf. How the hell can Samsumg mess up something like that? And no it's not my wifi since it works perfectly fine with alllll of my other devices.
I just had exactly the same problem. 3.2 was working fine for a couple of days for me but now has difficulty connecting and when it does connect doesn't seem to be able to reach the internet. No issues with other devices. Time for a custom ROM?
Had also issues with wifi and the latest stock 3.2. It went away with Task 6.1 and probably the other custom rom also.
And now it is all working again.
Strange but worrying.......
On the contrary the wifi is better now with me. I used to have wifi issues after the TW update. The first days with stock Android I dont remember a single day dropping my wifi connection, but after TW update I sometimes picked my Tab to see "no internet connection". After 3.2 update it is just always on. I am quite happy with this update. If I ever see a drop in connection it is %100 router related which sometimes confuses and tries to assign the same the IP address to 2 different devices.
First my setup:
XT1572
TruPureXMM 2.6.3
frankenclark kernel 0.8
Is there anyway to connect to my homewifi faster? I've selected to only show 5ghz wifi networks and I'm only seeing two when I enable wifi yet it dosen't connect to my wifi for maybe 5-10 seconds. Is this a problem with the rom/kernel? I don't remember connecting being this slow when I was on stock 5.1.
If I can change connect speed through the rom/kernel that would be best. Otherwise is there an app that can do it?
Heaby said:
First my setup:
XT1572
TruPureXMM 2.6.3
frankenclark kernel 0.8
Is there anyway to connect to my homewifi faster? I've selected to only show 5ghz wifi networks and I'm only seeing two when I enable wifi yet it dosen't connect to my wifi for maybe 5-10 seconds. Is this a problem with the rom/kernel? I don't remember connecting being this slow when I was on stock 5.1.
If I can change connect speed through the rom/kernel that would be best. Otherwise is there an app that can do it?
Click to expand...
Click to collapse
i cant see why you would choose 5ghz over 2.4ghz maybe thats the reason for your problem
5Ghz allows for faster throughput (more bandwidth available) - uses 80 mhz channels vs 20 mhz on the 2.4ghz.
I noticed the slow connection too. Seems if you open wifi settings, it connects immediately.
Heaby said:
First my setup:
XT1572
TruPureXMM 2.6.3
frankenclark kernel 0.8
Is there anyway to connect to my homewifi faster? I've selected to only show 5ghz wifi networks and I'm only seeing two when I enable wifi yet it dosen't connect to my wifi for maybe 5-10 seconds. Is this a problem with the rom/kernel? I don't remember connecting being this slow when I was on stock 5.1.
If I can change connect speed through the rom/kernel that would be best. Otherwise is there an app that can do it?
Click to expand...
Click to collapse
Did you try changing the channel in your router?
Haven't tried changing the channel. Will report back after I get home after work.
Heaby said:
First my setup:
XT1572
TruPureXMM 2.6.3
frankenclark kernel 0.8
Is there anyway to connect to my homewifi faster? I've selected to only show 5ghz wifi networks and I'm only seeing two when I enable wifi yet it dosen't connect to my wifi for maybe 5-10 seconds. Is this a problem with the rom/kernel? I don't remember connecting being this slow when I was on stock 5.1.
If I can change connect speed through the rom/kernel that would be best. Otherwise is there an app that can do it?
Click to expand...
Click to collapse
I can say that problem is with ROM.
It has very slow auto connection time.
To connect faster I am using:
- drop down notification menu - tap wifi menu where its possible to choose wifi's from that setting - just wait, as soon as it turns on wifi and actually starts to scan area it will auto connect faster than when you just turn on wifi and wait.
I confirm this behavior on XT1575 as well. It takes quite a long time to connect when i enable WiFi.
But if I enter the WiFi settings, it connects instantly.
And i think it's like this since Android 6. I don't recall having this issue on Android 5.
I can't say I've noticed any problems connecting to WiFi networks at home.
I'm running 6.0 stock (Feb 2016 security update) rooted to hell and back.
I have access to five different WiFi networks at home, and am registered to all five for convenience.
I use an app called Best WiFi to auto-connect to the strongest signal whenever my current signal drops below a user-configurable strength threshold.
Perhaps that's the reason I'm not feeling this issue?
https://play.google.com/store/apps/details?id=com.pintacdesign.bestwifi&hl=en
I've been using this app for years, since Android 4.0, and across four or five different devices now.
Edit - Before the inevitable questions. I live in a basement and have my own personal WiFi network down there. Upstairs, we have two network piping out of the office (2.4 GHz and an associated 5 GHz link). For the far side of the home, we have a WiFi extender that mirrors and extends those two signals coming from the office (2.4 GHz-Ext and 5 GHz-Ext).
My report:
Whether connecting to 2.4 Ghz (20/40 Mhz) or 5 Ghz (20/40/80 Mhz) the connectspeed is between 5-15 seconds if singlepressing on the wifitoggle. If longpressed it takes about 2-3 seconds. Either this is a problem with the rom or this is the intended behaviour in Marshmallow. But this was not the behaviour in Lollipop as far as I remember. Of course you could argue this a nonissue since longpressing the wifitoggle is the solution. However I would like singlepressing to behave the same since I use Gravitybox to hide the statusbar when pressing 2-state tiles.
Yeah this is a huge pain in the ass. I set up a WiFi shortcut on my home screen so I would start using WiFI more to save battery, but it takes so long for it to finally connect. I also have Tasker turn WiFi on in the morning when my alarm goes off, and it takes so long. It took a few seconds in Lollipop, and now it takes 10+ seconds in Marshmallow. It's ridiculous. Anyway there is no real fix except going into the settings or tapping the drop-down toggle multiple times, as others stated.
I notice the same thing too. Wifi takes long to connect on boot. When I go to connect wifi off, it always shows the routers in the previous area before showing what's in the current area. I turn wifi off when leaving home. I'll connect to a public router, but will still show my home router before showing any around me. I had a Galaxy S5 before and wifi connected right away.
Heaby said:
First my setup:
XT1572
TruPureXMM 2.6.3
frankenclark kernel 0.8
Is there anyway to connect to my homewifi faster? I've selected to only show 5ghz wifi networks and I'm only seeing two when I enable wifi yet it dosen't connect to my wifi for maybe 5-10 seconds. Is this a problem with the rom/kernel? I don't remember connecting being this slow when I was on stock 5.1.
If I can change connect speed through the rom/kernel that would be best. Otherwise is there an app that can do it?
Click to expand...
Click to collapse
First off, I am not sure if the OP is turning wifi on first when arriving at home and then seeing the delay, or if Wifi is already ON when you arrive home (EDIT: just reread OP and it appears you are turning it ON - see below), but I leave Wifi ON all the time and do not see any delay when I get home (I pull into my garage and my apps are already updating via my home wifi before I park my car).
There are various steps involved in "getting onto wifi" that don't just involve the client device (authentication to the access point; getting an available IP address from your AP or a separate router, and the stability/software quality of those devices, for example). but you may want to consider a few things to speed up the process at home regardless if Wifi is on, or you turn it on first:
1) go into "Saved Networks" in your wireless settings and "forget" any networks you don't need
2) make sure the device on your network issuing IP addresses (DHCP server software built into your router or AP, whichever you use - also make sure only ONE of the them is acting as DHCP server) has enough available IP's in its pool - better yet, assign the same IP to your MotoX's MAC address (set up a static IP in your routers LAN/DHCP settings if it has them so your MotoX gets the same IP every time)
3) while I agree with another poster about avoiding the 2.4 GHz for Wifi (congestion and more interference), even many 802.11n client radios today don't support 5GHz so keep that in mind if you shut down 2.4GHz in your home completely
4) Use WPA2 with PSK for authentication AND make sure your home SSID is being broadcast (not hidden, which they really aren't anyway with the right tools - A strong WPA2 PSK password is better security even if the world can see your SSID.
4) If you do turn Wifi On and Off, consider leaving it ON and see if that helps your connection time (I suspect it will If you are concerned about battery drain, you can disable wifi during sleep in wireless settings, but I don't have a battery issue with Wifi on 24/7. The Wifi radio beaconing for SSID's or even staying connected to an SSID in the background, when you're not using Wifi, is a very minimal power drain compared to having your screen brightness higher than you need (you can however turn off the annoying wifi network notification setting).
Hope this helps.
For those with this delay, are you running xposed with gravitybox? Tried disabling gravitybox? It maybe GB that's introducing the delay. Need feedback from those running stock.
If stock exhibits similar behavior then it's probably characteristic of the quick toggles in the moto x. The delay appears to be in the actual wifi connection phase, not acquiring ip. As once it actually connects, IP acquisition is almost instant. Toggling wifi off then on directly through settings is very fast, maybe 3-4 seconds.
I have a moto g lte (xt1045) on cm13 which takes about 5 seconds to connect after toggling wifi off then back on. The moto x takes a good 15 seconds.
ech1253 said:
First off, I am not sure if the OP is turning wifi on first when arriving at home and then seeing the delay, or if Wifi is already ON when you arrive home (EDIT: just reread OP and it appears you are turning it ON - see below), but I leave Wifi ON all the time and do not see any delay when I get home (I pull into my garage and my apps are already updating via my home wifi before I park my car).
There are various steps involved in "getting onto wifi" that don't just involve the client device (authentication to the access point; getting an available IP address from your AP or a separate router, and the stability/software quality of those devices, for example). but you may want to consider a few things to speed up the process at home regardless if Wifi is on, or you turn it on first:
1) go into "Saved Networks" in your wireless settings and "forget" any networks you don't need
2) make sure the device on your network issuing IP addresses (DHCP server software built into your router or AP, whichever you use - also make sure only ONE of the them is acting as DHCP server) has enough available IP's in its pool - better yet, assign the same IP to your MotoX's MAC address (set up a static IP in your routers LAN/DHCP settings if it has them so your MotoX gets the same IP every time)
3) while I agree with another poster about avoiding the 2.4 GHz for Wifi (congestion and more interference), even many 802.11n client radios today don't support 5GHz so keep that in mind if you shut down 2.4GHz in your home completely
4) Use WPA2 with PSK for authentication AND make sure your home SSID is being broadcast (not hidden, which they really aren't anyway with the right tools - A strong WPA2 PSK password is better security even if the world can see your SSID.
4) If you do turn Wifi On and Off, consider leaving it ON and see if that helps your connection time (I suspect it will If you are concerned about battery drain, you can disable wifi during sleep in wireless settings, but I don't have a battery issue with Wifi on 24/7. The Wifi radio beaconing for SSID's or even staying connected to an SSID in the background, when you're not using Wifi, is a very minimal power drain compared to having your screen brightness higher than you need (you can however turn off the annoying wifi network notification setting).
Hope this helps.
Click to expand...
Click to collapse
gpz1100 said:
For those with this delay, are you running xposed with gravitybox? Tried disabling gravitybox? It maybe GB that's introducing the delay. Need feedback from those running stock.
If stock exhibits similar behavior then it's probably characteristic of the quick toggles in the moto x. The delay appears to be in the actual wifi connection phase, not acquiring ip. As once it actually connects, IP acquisition is almost instant. Toggling wifi off then on directly through settings is very fast, maybe 3-4 seconds.
I have a moto g lte (xt1045) on cm13 which takes about 5 seconds to connect after toggling wifi off then back on. The moto x takes a good 15 seconds.
Click to expand...
Click to collapse
@ech1253: I've checked everything you suggested and you are right, having wifi on will make it connect almost instantly.
@gpz1100: I'm running xposed with gravitybox. Disabling gravitybox didn't change anything. I'd rather not uninstall xposed and/or go back to stock so if someone on stock without xposed could chime in that would be helpful.
It does it on stock android 6 for me and on a custom rom as well. Since day 1 with the moto x but at least wifi works just a long delay that no other android flagship from suffers from. :S
hexxor93 said:
It does it on stock android 6 for me and on a custom rom as well. Since day 1 with the moto x but at least wifi works just a long delay that no other android flagship from suffers from. :S
Click to expand...
Click to collapse
That's...not encouraging
Hopefully it's a softwarebug.