Related
My hd2 is running TyphooN CyanogenMod 7. I attend the University of Arizona and can't connect to their network. What happens is it scans, connects, authenticates, then disconnects? I have spent the last 2 weeks looking for a solution such as editing my wpa_supplicant and either my wifi gets an error or it still does not connect.
Also, I went down to my university's tech center and they told me I SHOULD be able to if the EAP is PEAP and the phase 2 is MSCHAPV2 but everytime i change it, it goes back to "none".
I have even tried switching to other roms in hope that it will work and still no luck.
please help me!
i had the same problem. i believe most ROMS have had this issue until recently. There are a few kernels that have been released that i believe address this issue. I'm using HyperDroid and it has this fix. if you insists on sticking with the ROM you have then just find a kernel with the fix.
grimmjaw said:
i had the same problem. i believe most ROMS have had this issue until recently. There are a few kernels that have been released that i believe address this issue. I'm using HyperDroid and it has this fix. if you insists on sticking with the ROM you have then just find a kernel with the fix.
Click to expand...
Click to collapse
Thanks grimmja! I will flash it over right now! is there anything else you did besides just set up the entering identification and password for the wifi?
hi everyone,
I have a similar problen, I am able to connect to my university wifi but I can't open any page other than the university pages. I fixed the proxy settings but it did not work. can anyone help me?
I should mention that I am using winmo not android.
Thank you so much grimmjaw! I updated the kernel to tytung r6 kernel and it connected in seconds!
Hi ppl, I'm having some serious problem with my wify connection getting lost every time since the 3.2 update the wify icon! Goes gray and blue each moment, it's like it lost the inernet from the router. Because of this gtalk doesn't keep connected. Hope y can help me here
Xoom wifi us stock 3.2
Hope ur xoom is not configured to get static IP from the router if yes remove the static IP or u can configure the static IP on the xoom itself hope it helps
Sent from my Xoom using Tapatalk
Yep, same issue here. I think there is a bug with the update...
Its no bug
Sent from my Xoom using Tapatalk
I had the same issue it use to dissconnect and get stuck at obtaining IP address when I removed the static IP I configured from the router i for xoom a day earlier when I got the update
Sent from my Xoom using Tapatalk
I have no problem getting an ip, and it's not static. And how do you know for sure this is not a bug? Are you and Android developer?
2 of us have the same issue afte updating. I bet there will be more as it rolls out.
I won't say anything here was just trying to help I faced a similar problem so I thought it might help you as we'll have fun figuring it out
Sent from my Xoom using Tapatalk
The router its configured to assign an static ip to my xoom. Until the update was perfect now doesn't keep the connection. Have to add that the xoom get its ip with no problem, but had I say keep disconnecting
ahmed007 said:
Hope ur xoom is not configured to get static IP from the router if yes remove the static IP or u can configure the static IP on the xoom itself hope it helps
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Wow this actually worked like a charm, it's weird that this be a problem with the xoom now, it should be totally transparent to it. Well I guess that later will come out some sort of explanation to this. Thx!.
Ur welcome
Sent from my Xoom using Tapatalk
I don't have such problems, but i want to point out that gray wifi icon doesn't mean there is no internet connectivity. If you disable sync the icon will turn gray, but you still have internet.
i have the exact same problem with losing connection to the Google server and the wifi icon switching from blue to grey constantly. When this happens my internet cennections also times out for a split second causing downloads in progress to end. I do also believe that it is a bug associated with 3.2. I've tried everything that I can think of to resolve it with no luck too. First I went through all of my router settings and did a wipe of the xoom. It didn't work so I went through the hassel of unrooting, relocking, and starting from scratch on 3.0, and I still have the same problem now that I'm back to 3.2. The xoom did not experience this issue on 3.0 or 3.1 and my Asus transformer is not having any problems running on the same connection, so the only thing left to blame my issues on is the 3.2 update itself.
droidx1978z4 said:
i have the exact same problem with losing connection to the Google server and the wifi icon switching from blue to grey constantly. When this happens my internet cennections also times out for a split second causing downloads in progress to end. I do also believe that it is a bug associated with 3.2. I've tried everything that I can think of to resolve it with no luck too. First I went through all of my router settings and did a wipe of the xoom. It didn't work so I went through the hassel of unrooting, relocking, and starting from scratch on 3.0, and I still have the same problem now that I'm back to 3.2. The xoom did not experience this issue on 3.0 or 3.1 and my Asus transformer is not having any problems running on the same connection, so the only thing left to blame my issues on is the 3.2 update itself.
Click to expand...
Click to collapse
I agree, my wifi turns off when the screen is off even though I have it set to always on!
I am also seeing some strange WiFi connectivity issues that I did not have on 3.1. The indication goes from blue to grey constantly and does cause a interuption of any downloads. Nothing has changed on my router or Xoom settings and both are set to dynamically assign the IP address. While I can still surf when it is grey, something is just not right. I have tried resetting both the router and my Xoom, nothing seems to solve this issue. This definately seems like a bug to me.
Can anyone confirm this is not an issue with the latest Tiamat kernel? I am currently 100% stock and this would give be one more reason to root.
HuckFinn said:
Can anyone confirm this is not an issue with the latest Tiamat kernel? I am currently 100% stock and this would give be one more reason to root.
Click to expand...
Click to collapse
I just finished reunlocking the bootloader, rerooting, and reinstalling cwm. I am in the process of downloading the deodexed 3.2/tiamat 2.0.0 rom to see if this has any effect on the wifi problems that I have been experiencing on 3.2. If this does not work then I am going back to 3.1 until another update comes out. I'll report back to tell you whether I still have these wifi issues tomorrow.
Unfortunately the deodexed 3.2/tiamat 2.0.0 rom did not help with my wifi issues. I flashed the tiamat 1.1 rom, which is based on 3.1 and now everything is working great. I don't know what my problem was with 3.2 or why so few people seem to be suffering with the same problem, but I'm sticking with this rom for awhile.
Was having similar wifi issues... connection retry messages in Market, failed to load web pages, etc. Additionally, network indicator remained primarily "gray". Removed DCHP reservation from router as recommended in earlier post and problem seems to have disappeared. Network indicator remains "blue" and retry messages have completely vanished. Thanks for suggestion
I think I have solved my issues. On the networks I manage (home and portable hotspot) I set the profile on the Xoom to use a static IP. What is strange is that on networks that I do not have control over (work and public hotspots) I left it as DHCP and I am not having any issues. I was having issues before I changed the OTHER profiles to static. Very strange.
I have opened issue 18648 at google code for this:
http://code.google.com/p/android/is...CP&colspec=ID Type Status Owner Summary Stars
DHCP seems to renew my IP address every 2-3 mins according to the adb debug log. Please star the issue if you are still getting it.
Just chiming in...I have a (new to me) XOOM with 3.2, 100% stock, no root, no funny business -- and I have the exact same problem.
There is a constant shift from blue to grey WiFi connection status icon, and issues with playing games online (server disconnections) and downloading apps.
I watched the log and do not see DHCP re-attempts as a new comment suggested, however.
I will attempt to set a static IP when I am home tonight and see if that fixes my issues there...
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!
I rooted and flashed my phone last night and everything was fine other than 1 thing. The Wi-Fi wouldn't connect on my home router. I tried several different roms and was left with the same problem where it was stuck on either obtaining ip address or authenticating. I then came into work this morning and the phone connected to my Wi-Fi network straight away.
Does anyone know how I can get around this problem, don't want to be using up all my data at home!
Thanks in advance
Dont get me wrong but did you try to restart the Router?
Sent from my HTC using XDA Windows Phone 7 App
Timzter said:
I rooted and flashed my phone last night and everything was fine other than 1 thing. The Wi-Fi wouldn't connect on my home router. I tried several different roms and was left with the same problem where it was stuck on either obtaining ip address or authenticating. I then came into work this morning and the phone connected to my Wi-Fi network straight away.
Does anyone know how I can get around this problem, don't want to be using up all my data at home!
Thanks in advance
Click to expand...
Click to collapse
I second the other suggestion. Those symptoms sound like your router needs a restart if it hangs at getting IP/authenticating.
I'm having the same problem on the network at my university.
I'm having problems with my wifi as well. We have a network here at my office secured with WEP. My galaxy nexus connects to it just fine but my Nexus 4 refuses. It sees the network, show strong signal but it doesn't seem to connect. I did manage to get it to connect once and I downloaded some updates but then the connection dropped and will not reconnect. I've tried various advanced settings (forcing the network to 2.4GHz, changing the power options, etc... No joy. This is particularly frustrating for me as my micro sim has not yet arrived so WiFi is all I have Hopefully it will work at home. At least there I have access to the router so I can make changes if needed. So far not a fan though.
I've got WiFi problems here, too. Roaming between different WiFi networks (home and university) often results in an non functional WiFi connection. Experienced this problem with stock Android 4.2 on Nexus 4 and Galaxy Nexus and latest CM 10.1 nightly on Nexus 4. Even reboot doesn't help every time.
As workaround: If WiFi connection is broken, turn on "flight mode", wait a few seconds and turn it off again. Works for me, maybe it works for your problems too.
I literally just received my nexus 4, and I haven't done anything with the SIM card yet, I just wanted to get things going on WiFi to start. It sees the network I want, let's me type in the password, and lets me click connect. After that it does literally nothing. No thinking, no obtaining IP address, nothing. Any ideas?
dyslexicpenguin said:
I literally just received my nexus 4, and I haven't done anything with the SIM card yet, I just wanted to get things going on WiFi to start. It sees the network I want, let's me type in the password, and lets me click connect. After that it does literally nothing. No thinking, no obtaining IP address, nothing. Any ideas?
Click to expand...
Click to collapse
I have exactly the same problem. Got the phone today and have tried several different access points - no luck. Restart the phone, no change.
Also, system updates screen said I could only download the update to 4.2 from a wifi connection till the 7th, so i set the date to the 7th and did the update successfully over the cell connection. Still no WiFi. Factory reset - no change.
---------- Post added at 09:18 PM ---------- Previous post was at 09:17 PM ----------
Oh, also tried the flight mode "trick" with no success.
Heartbreak said:
I'm having the same problem on the network at my university.
Click to expand...
Click to collapse
Your uni wifi probably is LEAP wifi or PEAP wifi, which is proven broken in Android 4.2
ecsk said:
Your uni wifi probably is LEAP wifi or PEAP wifi, which is proven broken in Android 4.2
Click to expand...
Click to collapse
It's also broken on my campus. Do you have any suggestions to bypass this?
ecsk said:
Your uni wifi probably is LEAP wifi or PEAP wifi, which is proven broken in Android 4.2
Click to expand...
Click to collapse
My university provides both LEAP and PEAP authentication. LEAP doesn't work for me either. But PEAP works. I'm able to connect via PEAP. (Stock 4.2 / 4.2.1 and CM 10.1)
Here is my log. It appears the authentication is timing out.
12-07 10:42:43.863: I/wpa_supplicant(19563): wlan0: Authentication with xx:xx:xx:xx:xx:xx timed out.
12-07 10:42:45.345: I/wpa_supplicant(19563): wlan0: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='XXXXX' freq=2447 MHz)
12-07 10:42:45.385: I/wpa_supplicant(19563): wlan0: CTRL-EVENT-ASSOC-REJECT bssid=xx:xx:xx:xx:xx:xx status_code=1
12-07 10:42:55.346: I/wpa_supplicant(19563): wlan0: Authentication with xx:xx:xx:xx:xx:xx timed out.
All other devices do connect fine and I even restarted the AP to make sure.
This is getting very frustrating. I couldn't connect to wifi at work (WEP, I know...) at all yesterday. I went home, and my WPA2 network at home worked perfectly. I come in this morning and boom, I'm connected just fine to the wifi here at work (the connection was remembered from my tries yesterday). I went to lunch, came back, no wifi. Reboots, reconnections, nothing seems to work. I also have a Galaxy Nexus with 4.2.1 and it connects to the wifi just fine. Grumble grumble....
-Matt
I did a few tests today and it seems to be only when using WPA2 with a pre-shared key. WPA works, as do open AP's.
jim.k.yee said:
It's also broken on my campus. Do you have any suggestions to bypass this?
Click to expand...
Click to collapse
No solution with stock google image AFAIK, because google does not provide 4.1.2 image for Nexus 4. You can try other custom ROM or ask if some one has successful LEAP wifi story about running custom ROM.
BTW I don't own Nexus 4, I am stilling using Galaxy Nexus, as soon as I upgraded to 4.2 LEAP wifi broke, I flash 4.1.2 back then it works fine.
I found that upgrading the access point (MikroTik) to the latest version allows me to connect.
Seems something in this device does not like some older WPA2 versions?
extremewing said:
I found that upgrading the access point (MikroTik) to the latest version allows me to connect.
Seems something in this device does not like some older WPA2 versions?
Click to expand...
Click to collapse
My N4 has been connecting fine to my home router over the past two days. Suddenly, today, it stopped recognizing the network (shown as "not in range" in wifi settings). No amount of router or phone reboots would get it to connect. I read in another forum about going to Displays in the settings menu, scroll to bottom - Wireless Displays. Turn on and search for wireless displays, then turn off. I thought, wtf? Anyway, I tried this and it connected to wifi immediately. Maybe there's a bug in the wireless display function that's interfering with wifi.
I am actually having a similar issue as others here, but I have found another weird work-around. Basically, although the Nexus 4 see's my campus's network, no packets get transfered back and forth, and I am not even sure what is going on (The IP address, tho, is usually "unknown".) However, upon going to the campus's IT help today, they turned off mobile data, and it then seemed to connect fine over Wifi. Any idea what is going on here?
There is no "signing in" to the network at my university, it just connects and verifies your device's MAC address, so I don't think they are doing any fancy authentication. I was thinking about maybe flashing a different ROM and seeing if I get different results.
i got mine yesterday and it connects then stops connecting after a couple seconds
Atrag said:
I am actually having a similar issue as others here, but I have found another weird work-around. Basically, although the Nexus 4 see's my campus's network, no packets get transfered back and forth, and I am not even sure what is going on (The IP address, tho, is usually "unknown".) However, upon going to the campus's IT help today, they turned off mobile data, and it then seemed to connect fine over Wifi. Any idea what is going on here?
There is no "signing in" to the network at my university, it just connects and verifies your device's MAC address, so I don't think they are doing any fancy authentication. I was thinking about maybe flashing a different ROM and seeing if I get different results.
Click to expand...
Click to collapse
I get exactly the same issue in my office. I can connect to school open network, but after a few minutes it lost connection (while still showing connected). I got to wifi setting, it shows that there is only one wifi hotspot and i am connected to it. But actually there should be more than five hotspot! If i switch wifi off and back on it can detect all the networks and get connected again, but then it goes to the weird cycle over and over.
Strangely, if i stayed in another office, it is connected all the time. Seems like the signal problem in my office. But i got no problem in my office when i was using galaxy nexus.
I am driven crazy by this!
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?