Related
Is anyone else having issues with the WiFi stalling and having to reset it, even though signal strength shows as excellent?
It's not a channel interference issue as I know what channels are in use, plus its doing the same on 3 different networks where other devices work fine, I'm using WiFi fixer to reconnect but its still problematic.
What have others found to be the best solution?
Samme issue here. Wifi keeps on disconnecting/loosing the connection and is most of the time unable to reconnect. Have to either turn wifi off/on or choose "forget" and reconfigure the AP my Hero in order to get it to work again.
It´s a Linksys WRT54GX running WPA/WPA2 + TKIP.
Have used an iPhone 3G on the same router for a year now without ´any´ problems.
I'm using WiFi quite often but I don't have this problem with my Hero.
Are you absolutely sure that there isn't any interference? It might be that the Hero is just a bit more sensitive than your iphone.
Today I found G-mon at Market which scans around for WiFi-networks. Perhaps you'll find out that there is a network that's interfering constantly. I've had that a few years ago and then found out that the bus-company uses WiFi on their busses which uses the same channel as I did with my WiFi-network.
Thx for the tip. Checked and no interference.
Also having this problem with a Linksys WRT54G. No WPA though.
I don't trust this router at all; using WPA and connecting a Dell Axim X51v to it in the past used to knock out WLAN on router, needing a hard reset.
same problem here. Wifi is disconnecting randomly within a few meters from the Airport extreme. It also reconnects again...most of the time....without me doing anything.
i'm also having problems with wifi - using a linksys befw11s4 with wep. i've got everythign else turned off - have followed all the instructions i can find here in the forums, and not had any success :/
If you press the Menu button in the Wifi settings you can select Advanced. There's an option there that defines when Wifi is disconnected. If you set this to Never than the Wifi connection will be stable. (At least in my case it is).
Again, thx for the tip but this is not really considered a "solution" but rather a workaround.
I don't like the idea of having it on "allways on". A real battery drainer and it shouldn't be necessary.
I had similar issues with my wifi (Linksys WRT160NL) until I installed "Wifi Fixer" from the market on my hero. Since then wifi runs without problems!
I had similar problem, Linksys WRT54G v1.0 running fairly old (but latest available) Linksys firmware, with WPA/PSK.
Yesterday, re-flashed router to Tomato (based on HyperWRT), setup for WPA2/PSK(AES) and now all is working perfectly, no problems at all.
So looks like some incompatibility between the Hero and the Linksys firmware, for WPA.
Well, I'm running the latest firmware for my router but have now done some other configuration changes and it seem somewhat consistent with your findings.
Previously it was running in a "WPA, WPA2 + TKIP" mode but it has now been working flawlessly since I change it to "WPA2 + AES". Hence:
- WPA2
- AES
=
- WPA, WPA2
- TKIP
=
Info, update on the router: I'm having a WRT54GX, not WRT54G.
interesting; I had no choice but to upgrade, as the newest firmware for the v1.0 WRT54G doesn't - I believe - support WPA2.
Since I had many other wireless clients working fine with WPA (not WPA2), but not the Hero, one wonders if there are some WPA bugs on the Hero that get tickled by older routers, or just that the Hero is being less lenient than other clients.
glad yours is better too, anyway
I found that wifi performance and stability on the hero improved a lot when I changed my AP from dynamic 802.11 b/g/n operation to 802.11g only. I've seen other boxes with linux having similar issues with this AP (D-Link DIR-655), which points towards a driver issue. Wifi works better on Linux kernel 2.6.30 and later on notebooks so things should improve once HTC produce a build that include a more recent kernel. Wifi was quite a headache on notebooks too with the drivers in kernel 2.6.27.x that is included in the current hero firmware.
I have same problem - frequent line drops whne full strenght signal shows
I also have a Linksys WRT54G - never had any problems before.
tried wep and wpa -no difference.
Also tried some "always On" utility from the market place, it only helped reset it quicker.
As stated above, mine got more stable when fixing router to WPA2+AES but I now realize that I still do experience connectivity issues, although less frequently then before...
i don't think this has anyting to do with the router. I got a router from HUAWEI,forgot its brand, but not linksys for sure. I've tried the university wifi as well. they all have the same issue.
Mine is working great with a Belkin.
Looks like a problem with the Linksys firmware.
Anyone tried a firmware upgrade on the router?
Uqbar said:
Mine is working great with a Belkin.
Looks like a problem with the Linksys firmware.
Anyone tried a firmware upgrade on the router?
Click to expand...
Click to collapse
Indeed, if you read up just a few posts, you'll find that question answered
that said, although things seemed initially to get better, I'm still seeing regular drop-outs with the upgraded router, and now still with the Hero upgraded to the HTC 2.0 ROM.
I do note that it seems to drop most when I'm sitting quite close to a different strong wireless client, e.g. a laptop. Perhaps the Hero just isn't a strong enough signal, and gets swamped?
Anyone else notice a correlation between dropouts, and proximity to other clients?
I have always had an issue with the wifi on my N1 when trying to connect to my router at home. Getting a connection use to be hit or miss, I would often try connecting over and over again with no success. Even when I did connect it would drop out as soon as the phone when into standby.
Well to my surprised after downloading/installing GB I went to attempt to get on wifi and it connected right away. I was shocked to say the least. I turned it off and tried it again and it connected again. Then I put the phone in stand by and it still stayed connected. Then I had to run to the store and left wifi on, when I got back to my apartment it connected again, no issues. This is completely awesome!
Froyo 2.2.1 fixed my major wifi issue (wifi going dead while the phone was asleep), but not the smaller issue where my connections would randomly disable themselves occasionally. I haven't seen that happen since Gingerbread though, so that's a good sign so far.
My only remaining issue with wifi is that the DNS cache still doesn't get flushed when switching to/from wifi to/from 3G/EDGE. This causes me frustration with our Exchange server which has a different IP on our LAN than it does on the public internet...
Congrats. I used to have problems, but I got a new router and it has been fine since. I used to get the "disabled" once in a while, but then I started using Auto Wifi Toggle, and never had another problem.
I know how you feel, it's nice when things work.
I've found these wifi connection issues to be Mostly Harmless
phazerorg said:
Froyo 2.2.1 fixed my major wifi issue (wifi going dead while the phone was asleep), but not the smaller issue where my connections would randomly disable themselves occasionally. I haven't seen that happen since Gingerbread though, so that's a good sign so far.
My only remaining issue with wifi is that the DNS cache still doesn't get flushed when switching to/from wifi to/from 3G/EDGE. This causes me frustration with our Exchange server which has a different IP on our LAN than it does on the public internet...
Click to expand...
Click to collapse
Really?! How come the same issue wasn't solved for me until gingerbread?
Now wifi is working just perfect Connects fast, sleeps when it should and transfers are awesome and rock solid
I had an issue with my home router and N1 where the N1 would connect, but after a bit of idle time, lose connection. It would re-try connecting only when I turned the screen back on and waited a good 10sec.
I was on 2.2, then 2.2.1, then 2.2.2
Now with 2.3.3 ...... my WIFI stays connected at home and at work... no hiccups at all.
MitchRapp said:
I had an issue with my home router and N1 where the N1 would connect, but after a bit of idle time, lose connection. It would re-try connecting only when I turned the screen back on and waited a good 10sec.
I was on 2.2, then 2.2.1, then 2.2.2
Now with 2.3.3 ...... my WIFI stays connected at home and at work... no hiccups at all.
Click to expand...
Click to collapse
I had exactly the same issue with my N1. Oddly, it got worse when I upgraded to a newer router (New D-Link with -n, compared to a 6yo Netgear with -g only) No idea why, but it did.
I finally got the OTA last night for Gingerbread and only now does it automatically connect and stay connected to WiFi like it should have.
My N1 is plain vanilla - no mods. For the 6+ months I've had the phone, it would constantly lose connection. I'd hit the WiFi button on the Power widget to turn off and on just to force it to reconnect to WiFi. 5 minutes later, I'd check my phone... back on 3G. I knew it was the phone, because I have plenty of other portable WiFi gadgets that stay connected just fine.
Whatever it is, I'm glad they fixed it.
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.
I have reached my wit's end trying to resolve my problems, so I'm posting here for ideas on fixing this, any input is appreciated!
When this started I was on stock, rooted, ICS 4.0.3 and had been for months. My wife has a nexus s with the same config and hers works fine.
Last week, my daughters sidekick 4G stopped having wi-fi internet connectivity. I turned her wi-fi off, then back on and it was fine and has been ever since. Later that night, my nexus did the same thing, the same procedure resolved it. Ever since then, my wi-fi will only work for 1-5 minutes after turning the wi-fi on. This is the only thing I can think of that changed that could have caused this. This was the first night we connected her sidekick to wi-fi.
The wifi symbol is up there, it'll be blue for up to half an hour, but won't have internet connectivity for long. One thing I noticed pretty quickly was that even though the grey wi-fi symbol is there, I can't access the router settings at 192.168.1.1 from the phone. I thought the grey wifi symbol still indicated I was connected to the router still, but it's not working. Each time this happens, I can turn wi-fi off, back on immediately and it'll work for 1-5 minutes. It appears that the more I constantly use it after turning it back on, it seems to maintain connectivity longer.
Last weekend, just after these issues started, I visited my sister and my phone operated on her wi-fi all weekend just fine.
When I came back home, my problems started immediately.
Here's what I've tried in pretty much the order I tried them:
I started by uninstalling avast, facebook, and autostarts
selected "Forget network" in access points screen and reconnected
Factory reset
Wipe dalvik cache & fix permissions
see if it worked without sim card in (it didn't)
flash GB broadcom driver
Switched router channel from 6 to 1
flash stock 2.3.6 (wi-fi problems still present)
flash OTA ICS (still had problems)
flash stock 2.3.6
flash OTA ICS
re-root
Flash PixelROM 1.60 LiteTouch
factory reset router (No wifi problems on using open network and default SSID for 30 minutes!)
resetup WPA Personal security and rename SSID same as before
Worked for another 15 minutes or so after this
flashed stock 2.3.6
flashed OTA ICS
re-rooted
Restored nandroid backup - quit working after this step
Factory reset router - worked for about 15 minutes, I decided I was ok so I setup security and SSID as before, then it quit working again
flashed PixelRom 1.60 LiteTouch
flashed stock 2.3.6
Flashed OTA ICS - THIS time I did not restore my google backups from the cloud, fearing that this was somehow restoring something that was causing me problems. It did not help.
Changed SSID on my router and reconnected phone
I have spent countless hours trying to fix this. I don't believe it's the hardware because the router factory reset seems to help quite a bit, works fine on unencrypted default router settings, and it worked on my sister's wi-fi.
I have nmap and wireshark and have a basic working knowledge of them. I have adb setup and usable on my computer. I also have dd-wrt installed on my router and have for years. Is there any kind of IP or hardware logging I could perform with these tools to help figure out what's going on??? ANY help is GREATLY appreciated!!
Well i'm no expert with any of this, but it sounds more like a router issue.. If both your sidekick and nexus have the same characteristics of failing wifi, it cant be the devices..
If you've already reset your router and it does the same exact thing, maybe it is something wrong with the router itself. You said it connected fine at your sisters house, so it cant be any hardware within the phone.. The only thing I could think of is maybe try a different router in your house to see if it works? If that helps get rid of the connectivity issue, then you can just get a new router and be happy with the wifis
I don't think a *hardware* problem with the router would only affect 1 device connecting to it wirelessly. I would think that kind of issue would affect all devices on the network.
Which makes me wonder if there's a setting on the router that may be causing it somehow, or some combination of packets might somehow cause the router to block my phone.
But again, I'm open to ideas here and I appreciate your input. I think getting another router will be my next step if I don't hear anything better by the time I get my next paycheck.
nevarDeath said:
I don't think a *hardware* problem with the router would only affect 1 device connecting to it wirelessly. I would think that kind of issue would affect all devices on the network.
Which makes me wonder if there's a setting on the router that may be causing it somehow, or some combination of packets might somehow cause the router to block my phone.
But again, I'm open to ideas here and I appreciate your input. I think getting another router will be my next step if I don't hear anything better by the time I get my next paycheck.
Click to expand...
Click to collapse
Ohh, I thought you had said that both the sidekick and nexus were having problems connecting. My bad.
But yeah have you changed any settings on it lately? Or messed with anything related to the router? Some setting may be kicking your device off after 5 mins, maybe some frequency setting or something dumb like that, I have no clue.
I know how it feels to have funky wifi, so I was only trying to help. good luck
Have you removed DD-WRT from your Wireless Router and back to stock OS? I had a Linksys router with DD-WRT and after about 3 years it started working so weird it became useless with any device. Had to buy a new one.
BTW, are other devices connecting fine to this router?
As swamp goblin stated, I would try with a new router.
It sounds like an issue on your router (or AP) with mixed client settings. I have had this issue with an old Netgear AP.
Try forcing "WPA2 with AES only" if all clients support it, otherwise force "WPA with TKIP only". If you have mixed B/G/N devices, force the fastest mode that all devices support. I use "G only".
Then remove and re-add the router on all your devices.
Also check for router firmware updates, and if you use DD-WRT firmware, find the Wiki page for your model and revision and use the suggested build there. The DD-WRT database they have is a mess and should not be used!
swamp goblin said:
Ohh, I thought you had said that both the sidekick and nexus were having problems connecting. My bad.
But yeah have you changed any settings on it lately? Or messed with anything related to the router? Some setting may be kicking your device off after 5 mins, maybe some frequency setting or something dumb like that, I have no clue.
I know how it feels to have funky wifi, so I was only trying to help. good luck
Click to expand...
Click to collapse
I haven't changed any settings, until this problem began, which makes this even more maddening. I appreciate your input regardless
Oogway13 said:
Have you removed DD-WRT from your Wireless Router and back to stock OS? I had a Linksys router with DD-WRT and after about 3 years it started working so weird it became useless with any device. Had to buy a new one.
BTW, are other devices connecting fine to this router?
As swamp goblin stated, I would try with a new router.
Click to expand...
Click to collapse
I haven't removed it. I thought I had a model that couldn't go back to stock, but I WILL be looking into this. The other devices connecting fine are Sidekick 4G, Wife's Nexus S, Acer Aspire one, HP tx2000 laptop, and my wife's HP laptop. I also have my satellite receiver connected via ethernet.
SpookyTunes said:
It sounds like an issue on your router (or AP) with mixed client settings. I have had this issue with an old Netgear AP.
Try forcing "WPA2 with AES only" if all clients support it, otherwise force "WPA with TKIP only". If you have mixed B/G/N devices, force the fastest mode that all devices support. I use "G only".
Then remove and re-add the router on all your devices.
Also check for router firmware updates, and if you use DD-WRT firmware, find the Wiki page for your model and revision and use the suggested build there. The DD-WRT database they have is a mess and should not be used!
Click to expand...
Click to collapse
I will certainly try these settings. Thanks for the tip on the wiki page
I had this problem too, I solved only flash again my radio...
Try if solve...
Or if don't work try to make a reset.
Sent from my Nexus S using Tapatalk 2 Beta-4
SpookyTunes said:
...Try forcing "WPA2 with AES only" if all clients support i...
Click to expand...
Click to collapse
THIS FIXED IT! I tried it first since it was the simplest solution and I've been 4 days with no loss of connectivity since I changed it to AES only, which all my clients do support! Thanks so much!
My phone has problems staying connected to wifi. It's often disconnected and has to reconnect when I wake my phone up (even though it's set to not turn off during sleep) and it'll disconnect and reconnect sometimes even when the phone is awake. I've read about people having problems with D-Link routers, but none of my routers are D-Link. The problem seems to have improved a lot after I flashed my modem to the MDL modem, but it still comes up. Does anyone have any solutions or would anyone know what could be causing this? I'm currently running the Wicked rom but I had this problem even when my phone was completely stock. Has anyone had this problem go away after switching to an AOSP-based rom?
AZImmortal said:
My phone has problems staying connected to wifi. It's often disconnected and has to reconnect when I wake my phone up (even though it's set to not turn off during sleep) and it'll disconnect and reconnect sometimes even when the phone is awake. I've read about people having problems with D-Link routers, but none of my routers are D-Link. The problem seems to have improved a lot after I flashed my modem to the MDL modem, but it still comes up. Does anyone have any solutions or would anyone know what could be causing this? I'm currently running the Wicked rom but I had this problem even when my phone was completely stock. Has anyone had this problem go away after switching to an AOSP-based rom?
Click to expand...
Click to collapse
I still have this problem, it disconnects and reconnects minutes later. I am on stock, stock kernel and rooted. could it be a root problem?
It can't be a root problem because I had this problem even when the phone was completely stock. I'm wondering if it's a TW problem, which is why I asked if anyone still had this problem after switching to AOSP (the Wicked rom I'm running now is TW).
If it were me, I would try a different modem, but thats just me.
Is there a thread with the available modems?
AZImmortal said:
Is there a thread with the available modems?
Click to expand...
Click to collapse
What device are you on, could be another fix.
AZImmortal said:
My phone has problems staying connected to wifi. It's often disconnected and has to reconnect when I wake my phone up (even though it's set to not turn off during sleep) and it'll disconnect and reconnect sometimes even when the phone is awake. I've read about people having problems with D-Link routers, but none of my routers are D-Link. The problem seems to have improved a lot after I flashed my modem to the MDL modem, but it still comes up. Does anyone have any solutions or would anyone know what could be causing this? I'm currently running the Wicked rom but I had this problem even when my phone was completely stock. Has anyone had this problem go away after switching to an AOSP-based rom?
Click to expand...
Click to collapse
Just because it isn't a DLINK wireless ap doesn't mean you won't issues. All the consumer-grade wireless routers/ap's share a narrow range of chipsets made by broadcom, atheros, etc.. So, the brand has nothing to do with it.
I would suggest getting a logcat if you can or try another wireless ap somewhere else. I've got a TPLINK wireless router with OpenWRT flashed, runs flawless.
TheAxman said:
What device are you on, could be another fix.
Click to expand...
Click to collapse
SGH-I337 (AT&T)
chaosclarity said:
Just because it isn't a DLINK wireless ap doesn't mean you won't issues. All the consumer-grade wireless routers/ap's share a narrow range of chipsets made by broadcom, atheros, etc.. So, the brand has nothing to do with it.
I would suggest getting a logcat if you can or try another wireless ap somewhere else. I've got a TPLINK wireless router with OpenWRT flashed, runs flawless.
Click to expand...
Click to collapse
I never said that only D-Link routers have problems. There's a well-known issue with D-Link routers so I wanted to state up front that I don't have any D-Link routers in case anyone wanted to suggest that it could be the cause.
http://www.zdnet.com/samsung-acknowledges-galaxy-s4-wi-fi-connection-problem-7000015431/
Does anyone have any solutions/possible causes?
From another thread...
http://forum.xda-developers.com/showpost.php?p=43495950&postcount=60
and
http://forum.xda-developers.com/showpost.php?p=43501841&postcount=64
See if that helps your issue and if it does make sure to thank the original poster of the threads. Good luck.
scott14719 said:
From another thread...
http://forum.xda-developers.com/showpost.php?p=43495950&postcount=60
and
http://forum.xda-developers.com/showpost.php?p=43501841&postcount=64
See if that helps your issue and if it does make sure to thank the original poster of the threads. Good luck.
Click to expand...
Click to collapse
Thanks, I actually came across that solution already but I don't seem to have that option under the advanced options. I'm not sure if it's because I'm running the Wicked rom.
AZImmortal said:
Thanks, I actually came across that solution already but I don't seem to have that option under the advanced options. I'm not sure if it's because I'm running the Wicked rom.
Click to expand...
Click to collapse
He said the option was only available while originally connecting and setting up the connection for the first time. Maybe you can try to delete the wifi connection all together and then let it re-detect and go through the set up process again...if that is an option.
My phone was doing this on my friends router but not on my home router. He searched google & found something stating that the S4 dont like routers with AES encryption for the security. He changed his router security to TKIP+AES encryption & the next time I was there wi-fi stayed connected with no constant reconnect problems. Buuuut, my home router security is just AES & I have no issues connecting to it, yet at least. Dont know if this will help anybody else out but its worth a shot to play with your routers security settings.
I thought I had an issue with my I337 S4 do the same thing.turns out my phone was just bouncing around trying to connect to 6 other open WiFi signals I've used
So just to give an update, I tried installing another router in my house as an access point and the phone has no problems staying connected to it, so there's definitely something that the phone doesn't like about the other routers that I'm running. I'm reluctant to say that there's anything "wrong" with my old routers because no other device had a problem staying connected, but if anyone else experiences the same problem, changing routers/APs could work. Fwiw, my old routers had Broadcom chipsets while the new one has an Atheros chipset. I'm going to try updating the firmware for the old routers to see if it helps (I run DD-WRT and Tomato on all of my routers).
AZImmortal said:
Thanks, I actually came across that solution already but I don't seem to have that option under the advanced options. I'm not sure if it's because I'm running the Wicked rom.
Click to expand...
Click to collapse
I'm having the same constant-disconnect issue as well and searching for solution.
I'm rooted, on stock rom and cant find any "key management" option at initial connect. Issue was happening when unrooted as well.
No issues when connected to router at work, but have connected two other, albeit older android devices to home router without issues.
home router is dlink dir655
bo8 said:
I'm having the same constant-disconnect issue as well and searching for solution.
I'm rooted, on stock rom and cant find any "key management" option at initial connect. Issue was happening when unrooted as well.
No issues when connected to router at work, but have connected two other, albeit older android devices to home router without issues.
home router is dlink dir655
Click to expand...
Click to collapse
Try WPA2 Personal TKIP+AES
Craptain Krunch said:
Try WPA2 Personal TKIP+AES
Click to expand...
Click to collapse
Thanks, forgot to mention the router is already set to TKIP+AES.
However, upon confirming this morning, it is set to auto WAP/WAP2. Will try WAP2-only tonight, unless this won't make a diff?
bo8 said:
Thanks, forgot to mention the router is already set to TKIP+AES.
However, upon confirming this morning, it is set to auto WAP/WAP2. Will try WAP2-only tonight, unless this won't make a diff?
Click to expand...
Click to collapse
WPA/WPA2 decreases the bandwidth of the router. WPA2 will support a full 300Mbps link state. So yea, they are different, but it may not fix it.
I have a Cisco EA6500, so I'm connected to the AC 5Ghz band, and it works flawlessly. WPA2 Personal
My bad on typing WAP instead of WPA.
Doesn't sound like fully opening up the bandwidth will fix it.
Has something to do with how the phone manages the encryption keys?