Related
Ok I have a very iritating problem.
My captivate works amazing in all ways... except one. When I'm at home connected to Wifi, within a few mins of me putting the phone down, or even mid use, the wifi will just stop working. The icon still shows it to be connected however no apps are able to actually get internet. A quick pulldown of the quick access menu and tapping wifi off and back on again gets it going great... for another 5 mins. Then the same thing happens.
Its been like this ever since I got the phone, even after flashing different roms. Now i'm running a Linksys Wireless - N router - maybe they're not playing nice?
I dont think its a hardware fault because when I serve wifi, IE the captivate is an infrastructure mode access point for 3g, it stays on consistently and my laptop can tether for 2 hours or more.
Anyone know what might be causing this?
Thanks
When you have wifi on, go to menu settings and 'Wireless and network'. In Wi-Fi settings you can change the Wi-Fi timeout.
nickbarbs said:
Ok I have a very iritating problem.
My captivate works amazing in all ways... except one. When I'm at home connected to Wifi, within a few mins of me putting the phone down, or even mid use, the wifi will just stop working. The icon still shows it to be connected however no apps are able to actually get internet. A quick pulldown of the quick access menu and tapping wifi off and back on again gets it going great... for another 5 mins. Then the same thing happens.
Its been like this ever since I got the phone, even after flashing different roms. Now i'm running a Linksys Wireless - N router - maybe they're not playing nice?
I dont think its a hardware fault because when I serve wifi, IE the captivate is an infrastructure mode access point for 3g, it stays on consistently and my laptop can tether for 2 hours or more.
Anyone know what might be causing this?
Thanks
Click to expand...
Click to collapse
Try goin to settings->wireless and networks-> wifi settings (menu key)advanced and set the sleeping policy to never
I've done that...
i *Think* i've fixed it. I was using WPA2 IPK encryption or whatever.. Switched back to the 64 bit crappy WEP. Wifi was on all night and all morning with no cut out.
Might be just another linksys-is-crap situation.
HI, I figured I keep my wifi woes within a singe thread so.
I have an old D Link WBS 2310 router.
I recently got a message from AT&T that I'm near my data limit. This surprised me as my last cycle I barely got near 500mb. Since my bill isn't ready yet, I can't see exactly what it is I'm doing to use so much data.
TO be safe I figured I'd pull out my old router and set it up. After hours of hassle getting it to work on my new computer, I wasn't able to get my Captivate to hook up to it.
My laptop works fine. It gets a fast wifi signal, but my phone just says "Obtaining IP address" for a while and then gives up.
My phone gets wifi at work, at friends', at coffee shops - but not at home.
I've tried this with no encryption, WEP encryption and WPA2 encryption.
Each time my laptop would hook up to the wifi but my phone wouldn't.
I searched some other forums and found similar problems with HTC phones.
Some answers say that D Link sucks. But that answer applies to other brands as well.
Do I need "n" wifi, rather than "g"?
I don't want to buy another router only to find it still doesn't work.
Any help?
gluvox said:
HI, I figured I keep my wifi woes within a singe thread so.
I have an old D Link WBS 2310 router.
I recently got a message from AT&T that I'm near my data limit. This surprised me as my last cycle I barely got near 500mb. Since my bill isn't ready yet, I can't see exactly what it is I'm doing to use so much data.
TO be safe I figured I'd pull out my old router and set it up. After hours of hassle getting it to work on my new computer, I wasn't able to get my Captivate to hook up to it.
My laptop works fine. It gets a fast wifi signal, but my phone just says "Obtaining IP address" for a while and then gives up.
My phone gets wifi at work, at friends', at coffee shops - but not at home.
I've tried this with no encryption, WEP encryption and WPA2 encryption.
Each time my laptop would hook up to the wifi but my phone wouldn't.
I searched some other forums and found similar problems with HTC phones.
Some answers say that D Link sucks. But that answer applies to other brands as well.
Do I need "n" wifi, rather than "g"?
I don't want to buy another router only to find it still doesn't work.
Any help?
Click to expand...
Click to collapse
part of the IEEE 802.11n standard is backward compatibility with all previous 802.11 standards IIRC, so there should be no need to buy a new n device.
HOWEVER, i am also having issues with my wi-fi and my g capable router. i will meddle around with some phone and router settings to see if i can fix this, this is one area were i can actually be of some use on this forum
Hi. It turned out the wifi was broken on my captivate. I reset it to stock and it's all better. It had been working up to the previous day so I assumed that it was still working. The router goes down intermittently in general, so I've ordered a new one to see what's up.
Hi, I'm back! So after resetting the phone and getting wifi to actually connect (rather than being stuck searching for IP address), I'm now having the exact same problem is the OP. The OP seems to have solved this by switching to WEP. I tried this and it doesn't work. My timeout is set to never. Also, it's the same at home (I replaced my router) as well as at Starbucks and a friends house.
I'm connected, but can't download or sync. It works initially and then stops, and then comes back in briefly and then stops, all the while "connected." Sometimes I can fix it temporarily by turning off wifi and then turning it back on.
SO what's the deal? Is it a hardware problem? Is there some secret magic code?
edit: Just disabled encryption - same problem.
Hi all, newbie poster, but been on the forums for about 2 weeks. Thanks for all who have provided such great methods to unlock the full potential of the NC!
I flashed to Decad3nce's 1.1 ROM yesterday from my Autonootered 1.01 setup, and was able to get most issues worked out, but the one thing left that's bugging me is the WiFi. When I initially boot up, it seems the device recognizes my WiFi network, and connects. However, after I resume the NC from sleep, it doesn't reconnect to my access point. In fact, the only way I've been able to get the connection back it to use the stock browser, at which point I'm asked which network to connect to. It says my network is "remembered", but it won't connect automatically, I need to manually connect every time.
Any ideas on why this is happening, and how I can get the NC to automatically connect to my network after resuming from sleep?
Thank you!
Hi there. Wass havingg the same issue you had. Take a look at the instructions for enabling adhoc wifi on Nookdevs.com Wether you want to enable adhoc or not that's up to you. But i followed the directions for Settings Profile Pro from there. Now everytime i turn off my screen and turn it back in. My nook connects right away to my wifi network.
Edit: Mine connects fine. But with my wifes nook. If she is coming off a reboot. She would have to goto settings and connect initially. But after that. Everytime she turns off her screen and turns it back on it reconnects right away.
Good luck.
Sent from my "NookDroid" using XDA App
Been having a similar issue without the 1.1 rom. Can't connect to my own wifi unless i reboot router but it connects to other wifi fine.
Anyone hits a clue or is it my network (my laptops iphone and desktop all run fine on my wifi)
sent from my nootered nook color
phirephotog said:
Been having a similar issue without the 1.1 rom. Can't connect to my own wifi unless i reboot router but it connects to other wifi fine.
Anyone hits a clue or is it my network (my laptops iphone and desktop all run fine on my wifi)
sent from my nootered nook color
Click to expand...
Click to collapse
I had that problem with 1.01. It occured after I ran the script for swapping the adhoc and infrastructure supplicants without disabling wifi first. The only thing that fixed it for me was a full reset from 1.0.0. Router was a verizon fios router/modem.
I had this problem before and can't test if it still happens but for me it only happens with one wireless network and all the others are fine. Is that the way yours behaves? Since it worked fine with others I didn't really worry about it
You said you can only get it to work by opening the browser - does that mean it doesn't work if you toggle wifi off and on? That was usually how I got it to connect to that one network
Same issue. After sleeping it sees my AP but doesn't connect. Turning wifi off and on recovers it.
Ultimoose said:
Same issue. After sleeping it sees my AP but doesn't connect. Turning wifi off and on recovers it.
Click to expand...
Click to collapse
same here but only if it has been sleeping for a while
sidenine said:
Hi all, newbie poster, but been on the forums for about 2 weeks. Thanks for all who have provided such great methods to unlock the full potential of the NC!
I flashed to Decad3nce's 1.1 ROM yesterday from my Autonootered 1.01 setup, and was able to get most issues worked out, but the one thing left that's bugging me is the WiFi. When I initially boot up, it seems the device recognizes my WiFi network, and connects. However, after I resume the NC from sleep, it doesn't reconnect to my access point. In fact, the only way I've been able to get the connection back it to use the stock browser, at which point I'm asked which network to connect to. It says my network is "remembered", but it won't connect automatically, I need to manually connect every time.
Any ideas on why this is happening, and how I can get the NC to automatically connect to my network after resuming from sleep?
Thank you!
Click to expand...
Click to collapse
Well, it looks like no immediate solution to this other than starting from a factory reset. I restored my backup ROM from CWM that I saved prior to flashing to 1.1.0, and WiFi is working fine again, so I'll stay here on 1.0.1 until I hear of a solution. Plus, XDA app works as expected in 1.0.1 as well. Thanks for any additional help!
I'm having the same issue as others.
Decad3nce wanted some logs so I pasted them into PasteBin:
dmesg - pastebin.com/wsajYF77
logcat - pastebin.com/gPasCEtZ
racks11479 said:
Hi there. Wass havingg the same issue you had. Take a look at the instructions for enabling adhoc wifi on Nookdevs.com Wether you want to enable adhoc or not that's up to you. But i followed the directions for Settings Profile Pro from there. Now everytime i turn off my screen and turn it back in. My nook connects right away to my wifi network.
Edit: Mine connects fine. But with my wifes nook. If she is coming off a reboot. She would have to goto settings and connect initially. But after that. Everytime she turns off her screen and turns it back on it reconnects right away.
Good luck.
Sent from my "NookDroid" using XDA App
Click to expand...
Click to collapse
Thanks for this post. This seems to have solved the problem for me.
Edit: Actually this didn't work I just didn't let it sleep long enough. Once it sleeps for several minutes WiFi requires a reset to reconnect.
rodneyshupe said:
I'm having the same issue as others.
Decad3nce wanted some logs so I pasted them into PasteBin:
dmesg - pastebin.com/wsajYF77
logcat - pastebin.com/gPasCEtZ
Click to expand...
Click to collapse
Dmesg shows nothing wrong with tiwlan driver.
Logcat shows that the "nookwifimanager" just fails at reconnecting to preconfigured networks
Code:
D/NookWifiManager( 1188): Cannot connect to pre-configured networks
What kind of security do you have on your router? (might be wep bug)
Other than that, you can try using the patched wpa for ad-hoc
I was having an issue where it it would connect to Wi-Fi for a minute and then disconnect. I could turn off wi-fi and repeat the process. I restored to my last CW backup then I used the 1.1_r2 and everything worked perfectly. I'd rollback to the backup you did (if you followed Deced3nce's steps) then use the r2 update. It's made all the difference for me.
I flashed r2 and I'm having the same issue...I have to turn off/on wifi after it goes to sleep in order for it to connect
Xhorder said:
I flashed r2 and I'm having the same issue...I have to turn off/on wifi after it goes to sleep in order for it to connect
Click to expand...
Click to collapse
Did you flash it over top of r1? Or did you start with 1.0.1? And were you using any special kernels prior to the flash?
similar issue - wifi only works after a reboot. after sleep it can see but cannot connect to either adhoc or infrastructure networks. no fix other than to reboot. which is a huge PitA
one4thewings said:
Did you flash it over top of r1? Or did you start with 1.0.1? And were you using any special kernels prior to the flash?
Click to expand...
Click to collapse
I actually flashed it over rooted 1.0.0. And I was running the 900 mhz kernel
Hey guys I tried searching but came up empty handed here.
Whenever I put my nook in standby (push power button or it automatically does it with inactivity) the wifi connection turns off. I've got it set to do that in spare parts so that it only stays "awake" while charging and not while idle.
The problem is it doesn't do that. Regardless of if it's charging or not, whenever I wake it up, even though wifi is enabled in the settings, it doesn't search on connect to my network. I have to go into Setting -> Wireless and as soon as I go into that menu, it finally connects automatically. It won't do it unless I go to that menu.
I'm rooted with the 1.0.1 Autonoonter btw.
Mine was doing something similiar. For me, it kept hanging up on obtaining an IP. I used an app called Wifi Static (free in the market) to set up a static IP and haven't had any problems since. Wifi seems to shut itself off way less often and when it does, it only takes 1-2 seconds to auto reconnect. Don't know if it will help you or not, but it's worth a try.
Have you done any modification of the wifi settings at all? Like the ad-hoc supplicant mod?
Quilombo said:
Have you done any modification of the wifi settings at all? Like the ad-hoc supplicant mod?
Click to expand...
Click to collapse
I have not.
I have the problem but it only happens with certain routers others work just fine . . . weird!
I have exactly the same problem. It started with the upgrade to 1.1. Affects stock or adhoc supplicant.Very annoying. Yet to find a fix
I had this happen twice on rooted stock and now it's happened on cm7.
I believe what triggers it is a failed connect to an open network. Then I got home and couldn't connect to my remembered network and it simply says out of range. And scan won't find any networks.
On rooted nook, I had to remove all remembered networks and then it worked. Scans started working again. Cycling wifi on/off or reboots do not fix it.
I really don't want to remove my remembered networks again and re-add them. Is there a different workaround to this?
edit: hmm I guess it's not the exact same issue as the rooted nook. I let it charge for a bit and now it's finding the networks again. Still like to know what was wrong but it seems to have fixed itself.
I just received my gen 2 moto x last night and am having trouble connecting to Wifi at work. It connects to my home network and one of my work networks just fine, but when I try to connect to the work network I need it to connect to the signal strength drops to "poor" as soon as I press connect. My home network and work network both are password protected. I've verified the password and have the same connection settings as my friend's gen 1 moto x, which connects properly. The work network has excellent signal at all times when I am not trying to connect to it. It just keeps cycling from "connecting" to "saved."
Has anyone else experienced this or know a workaround? I found this but this is for a gen 1 (I'm not sure if that would help) but I'm not rooted so I don't have access to phase 2 authentication. http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-signal-drops-trying-to-connect-t2872241
Thanks,
Mike
mikekory87 said:
I just received my gen 2 moto x last night and am having trouble connecting to Wifi at work. It connects to my home network and one of my work networks just fine, but when I try to connect to the work network I need it to connect to the signal strength drops to "poor" as soon as I press connect. My home network and work network both are password protected. I've verified the password and have the same connection settings as my friend's gen 1 moto x, which connects properly. The work network has excellent signal at all times when I am not trying to connect to it. It just keeps cycling from "connecting" to "saved."
Has anyone else experienced this or know a workaround? I found this but this is for a gen 1 (I'm not sure if that would help) but I'm not rooted so I don't have access to phase 2 authentication. http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-signal-drops-trying-to-connect-t2872241
Thanks,
Mike
Click to expand...
Click to collapse
Exact same problem. Fine at home and everywhere else. Spent a couple hours this week on the phone with Moto. They keep saying it's the network, yet everyone else is on it. They say update firmware and open MAC. Both of which are done.
This is the message in the Access point every 3 seconds when my phone is trying to connect...
"Client Deauthenticated: MACAddress:9c:d9:17:a1:c8:51 Base Radio MAC:b8:62:1f:ad:5e:90 Slot: 0 User Name: unknown Ip Address: unknown Reason:Unspecified ReasonCode: 1"
My wife's phone drops WiFi in favor of 4G LTE at home. I have to turn off data to connect to WiFi but it eventually drops the WiFi. I'm still waiting on my pure edition so I'm not sure if its just her phone or if its a common problem.
bradley26 said:
My wife's phone drops WiFi in favor of 4G LTE at home. I have to turn off data to connect to WiFi but it eventually drops the WiFi. I'm still waiting on my pure edition so I'm not sure if its just her phone or if its a common problem.
Click to expand...
Click to collapse
This!
I have this problem all the time ON multiple networks, its very frustrating
Mines will disconnect from my 5ghz when the screen goes off and reconnects when turned on, works fine on 2.4ghz. I have a Nighthawk ac1900 so the phone is definitely the problem.
Sent from my Hammerhead
This is related to 802.1X, We have it implemented Radius and 802.1X at work and it doesnt connect. But the same AP has a guest SSID which has no protection and a separate vlan which has access only to internet and it works fine.
giovannirc said:
This is related to 802.1X, We have it implemented Radius and 802.1X at work and it doesnt connect. But the same AP has a guest SSID which has no protection and a separate vlan which has access only to internet and it works fine.
Click to expand...
Click to collapse
Sounds like this could be my problem. We have 4 networks we can login to, but they are all broadcast from the same access point. One says "secured with 802.1x" and is for laptops, two say "secured with WPA/WPA2" and are for cell phones/other, and the final is unsecured. I can only connect to the unsecured network.
So does it sound like it's the phone that's refusing the network, the network is refusing the phone for something the phone is sending back to it, or the network is refusing the phone for another reason?
I'm having this same issue. 1st Gen Moto X sitting right next to 2nd Gen, and the 1st Gen is connected while the 2nd Gen can't.
I'm having the exact same issue. It appears the problem is that older Cisco firmware doesnt support 802.11w, which is what the moto x 2014 uses by default. Here is a thread where a moto rep explains it to Cisco - https://supportforums.cisco.com/discussion/12331486/connectivity-issues-cisco-controllers-and-pmf-enabled-moto-x-gen-2
My girlfriend and I have this phone and we had a similar problem. It would connect/reconnect like a billion times before staying connected on our home network but connect fine on other networks. I tried several solutions but the one that worked was changing the channel on the router. I live in an apartment building and there are a lot of WiFi networks around me so I figured that might be causing some interference. I changed my channel from 6 to auto (it automatically jumped to 11) and now it connects instantly and is solid. What's weird is I tried channels recommended by WiFi analyzer and my other devices would connect just fine but the Moto X's couldn't even see the network in the list when it was on a lot of channels like 12, 13, and 14.
Seems like a weird WiFi radio firmware bug to me.
Is there a client side fix for this?
I just ran into the problem at my work. It is a major hospital. They are not going upgrade their cisco firmware so a couple of people's personal phones are able to connect to the network.
WiFi in general is bad on the X2014 and I am reading the same in the Droid Turbo forums.
Sent from my XT1095 using XDA Free mobile app
What!? Really?
I've not had a single issue with WiFi connectivity. I'm an IT professional so heavily reliant on WiFi.
will54880 said:
WiFi in general is bad on the X2014 and I am reading the same in the Droid Turbo forums.
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
Wutang200 said:
I've not had a single issue with WiFi connectivity. I'm an IT professional so heavily reliant on WiFi.
Click to expand...
Click to collapse
I never had a WiFi problem with the Moto X 2014 until today at work. It wouldn't connect to a few different clients Wireless APs. At the first client site I power cycled the phone and WiFi still wouldn't connect. I then went to another client site and once again it would no longer connect. I power cycled again and this time it connected just fine albeit Bluetooth was acting funny and not connecting to the Moto 360. After cycling Bluetooth off and on again the 360 finally connected. Not sure if this is an actual issue or just dumb luck. I wonder if anyone that was having WiFi issues with this phone also has a Moto 360 connected via Bluetooth?
I don't own a 360 and my bluetooth is normally switched off unless I'm streaming music at home.
I know none of what I am about to write will solve anyone's issue but sharing my experiences mught help understand you're not alone. I wander between as many as a dozen different wifi networks daily. I manager a 63 room hotel on 7.5 acres where we are currently running EnGenius EAP350 AP's broadcasting in 2.4mhz band ONLY using .11bgn. I set the entire network to use one SSID so roaming is, in theory, problem free. My XT1095 has not had any issues at all here on property.
I also have my personal network in the lobby and main building under 2.4/5/.11AC side by side with out guest network. No issues bouncing around. I honestly expected issues but have found none.
There is one issue I have found in Android in general which can happen randomly, or I have not been able to induce the behavior only recognize it. Occasionally when I move from one building to another Android (ICS forward for sure) will forget which actual AP it's after and just hang. My solution is to tell the device to forget that node then once forgotten the network, of course, shows up in the list. I then select it and boom we're back in business.
I do have issues when I visit a network at say, the grocery store which requires accepting an EULA...the device simply will hang Wifi wize, even when I delete and reconnect I won't get the note to open the authorization page. I end up just killing wifi and going with LTE.
I get the same behaviors from all my phones ICS though Kitkat, don't have Lollipop yet darn it!!
I have long been frustrated with this weirdism from Android but have reached a point of M.A.D. with my devices but never found a solution.
I have noted I have the most issues by far with Cisco/Linksys devices. It has been almost assured that if I have an issue it's one of those routers running an older firmware version (amazing how many AP/routers use default password settings...I mean, really???)
Not 100% sure it's a firmware only issue but I do think it's some common bit of hardware in an AP/Router which can go spastic for some reason preventing Android from figuring out how to remain or get connected. I even had one of the EnGenius AP's go nuts, a fast swap with a freshly configured AP resolves but, again, still does not identify or solve the problem
I also sense there is some oddness deep in the bowels of Android's wifi/networking subsystem which just was never written correctly and may never be fixed.
Last I run and app called Wifi Analyzer by Kevin Yuan, it helps me a GREAT deal because I can target a specific AP/node to connect with. Android versions often defeat this by not remaining connected to that desired target AP and switching to something else. Here is where I think some of the issues with wifi connectivity live...Google MUST spend some time refining their wifi subsystem.
No matter this is a Very frustrating issue when it happens. My best solution has always been to forget the current connection then reconnect with it again once it reappears. Better yet use Wifi Analyzer or similar app to target a specific AP/node and connect/forget from inside the app, that really does seem to help, mostly...sigh, I know, sorry...
This WiFi issue is really aggravating. I have tried so many things:
1. Rebooting Router
2. Powering Off/On Phone
3. Turning WiFi Radio Off/On
4. Resetting Phone Cache Partition
5. Using WiFi analyzer and setting my router to various channels manually
6. Changing Router SSID
7. Forgetting SSID on phone and re-adding it
8. Verifying MAC Filtering is not enabled
9. Enabling MAC filtering and specifically allowing phone MAC address
10. Disabling "Avoid Poor Connections" in WiFi settings
11. Manually setting WiFi frequency band to 2.4ghz in phone settings
12. Disabling "WiFi Optimization" in phone settings
23. Changing WiFi direct and BT phone names (yeah, a big stretch, but I read somewhere that this worked)
24. Installed updated firmware on my ASUS RT-N12D1 (3.0.0.d.376_3602)
25. Disabled WPS on router
26. Switched router between Auto, Legacy and N-Only
27. Disabled Authentication and Encryption on router, just an "Open" connection.
After all of this, the phone still has WiFi connectivity issues. Sometimes after a phone power cycle it will connect to WiFi, but never for very long. Every other device I have connects to the WiFi without issues. I just got the Moto X a few days ago (AT&T version) and this is the first time I have ever had a device with WiFi connectivity issues like this. Very aggravating. There is clearly something wrong with either the hardware, or software on the phone.
There are some other oddities. When it won't connect to WiFi, there is something strange with the phone. Its not like it just can't connect or stay connected to WiFi, but somehow it seems like the WiFi is in a stalled state. Sometimes it won't show any WiFi networks and just says "Searching for WiFi networks..." until I turn off wifi and turn back on again. Then as soon as it turns back on, it will show the nearby SSID's, and try to auto-connect to my router, but after a few seconds it shows "Disabled" under the SSID. Then after a few seconds the disabled goes away, and it just shows the SSID name. It also won't let me change the WiFi Direct phone name while the WiFi is in this state, it gives me an error saying "Failed to rename device", followed by "Group Creation Failed". However, when I am actually connected to WiFi, I can rename the WiFi direct name just fine. So its not just simply an issue with bad radio signal or something, but something more serious, like the WiFi state is hung or something. If I can't resolve this in another day or two, I am going to have to return the phone, and hopefully a replacement will work. If not, I might have to get something other than a MotoX because I can't not have WiFi while at home and work.
---------- Post added at 12:29 PM ---------- Previous post was at 12:10 PM ----------
I found a way that seems to work to connect to WiFi. To clear, this isn't a fix for the data-sync issue that some people are having, or poor signal, but the issue where you can't connect to an SSID, and there is no error or anything.
1. Hold Down Power Button
2. Turn Airplane Mode On
3. Turn Wi-Fi On
4. Connect to SSID
5. Press Power Button down again
6. Turn airplane mode "Off"
I have now tried this several times, and it works everytime. If I turn off Wi-Fi and back on again, it won't connect, until I do the airplane mode trick. I don't know who to give credit for this, I have spent days and hours searching, and I remembered reading that from somebody else, but not sure where, so this is not my fix, I am just posting it here as it seems to work.
This issue is strange, and must be some combination of Android, and Motorola software/hardware/firmware configuration. I hope they get this fixed, but it at least now, this temporary fix will work whenever WiFi is not connecting.
For those of you getting WiFi connectivity problems, it could be related to your router setup. Download an app called InSSIDer and run a scan, then choose a channel that's not being used but make sure it's 5 channels higher or lower. For example, if it detects 3 networks on channels 3, 5 & 6, then you want to choose channel 10 or 11. If it detects one network on channel 6, then you should choose channel 1 or channel 10 or 11.
I noticed issues like this when I bought my Nexus 4 after my iPhone 4. Android devices seem to ship with rubbish WiFi radios.
Like I've mentioned before, I've not experienced a single disconnection with my phone either at home, work, in laws, coffee shops or anywhere else ever. Same with my first gen Moto X.
Mine is slightly different. Now and then, after power cycling or rebooting, it forgets all the WiFi passwords. Not every time. Just now and then.
Also sometimes it's quite fast, some slow. My wife's firs gen is pretty constant.