Database Users

Newest 3.2 Update Ruined Wifi

Hey guys, the newest 3.2 update (not the first one but the second one that came out) messed up my Wifi and now I can't connect to it. I've turned off/one my roouter+modem, wifi on tablet, tablet itself, and re-added the network multiple times and nothing seems to work. What happens is that I add the network and it would try to connect and authenticate but then it just retries connecting again and then all the available wifi networks are gone. It's a mess. And it happened a few times where it would finally connect but then no webpage would open after a few minutes and the wifi bars on the bottom right turn from blue to grey. Wtf. How the hell can Samsumg mess up something like that? And no it's not my wifi since it works perfectly fine with alllll of my other devices.

I just had exactly the same problem. 3.2 was working fine for a couple of days for me but now has difficulty connecting and when it does connect doesn't seem to be able to reach the internet. No issues with other devices. Time for a custom ROM?

Had also issues with wifi and the latest stock 3.2. It went away with Task 6.1 and probably the other custom rom also.

And now it is all working again.
Strange but worrying.......

On the contrary the wifi is better now with me. I used to have wifi issues after the TW update. The first days with stock Android I dont remember a single day dropping my wifi connection, but after TW update I sometimes picked my Tab to see "no internet connection". After 3.2 update it is just always on. I am quite happy with this update. If I ever see a drop in connection it is %100 router related which sometimes confuses and tries to assign the same the IP address to 2 different devices.

Wiping wifi cash/memory

Well, today I had some wifi issues with my tab and was wondering if anyone can help me out.
I am currently running Task10 with pershoot 's kernel and while working on a secured wifi at a client's office my tab was unable to pull down an ip address. The weird part was my Epic 4G touch was working fine with the accesspoint but after about an hour of using the tab it just stopped all Internet access and would constantly fail to connect. I tried forgetting the network and even rebooting but to no avail.
My question is, aside from forgetting a network is there a wireless protocol /ssid cache that I could have wipe other than simply forgetting the network?
I almost wish there was a way to perform a release and renew.
Thanks in advance for everyone 's help!

I too have many problems with wifi on my phone and tab. I randomly can not obtain an IP from hotspots I use all the time. At home I just reboot the device and the AP and it usually fixes it. Now that I think of it I haven't had the problem since I installed ICS.

Help with fixing Wi-Fi

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!

Nexus 4 WiFi Problem

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!

[Q] VZW 4.1.2 latest build, won't connect to FIOS router

So, my wife got a Droid RAZR M. First thing we did was download the 2 updates from Verizon. Current version is 98.18.78.XT907.Verizon.en.US
I get home, and go to connect to my FIOS Actiontec MI424WR-GEN3i running the latest firmware available. (40.20.7)
Running WPA PSK, in b/g/n compatibility mode, with SSID on.
The phone refuses to connect. It will see the SSID, an even automatically identify that it's WPA PSK security. But when I go to connect, the signal drops to almost nothing, then doesn't connect. I make it forget the network and start fresh, same thing. Reboot the phone, same thing.
WPS is not active on the FIOS router firmware, so I can't try to connect via WPS.
I've got a Galaxy Nexus connected to the wifi and about 6 different wifi devices (laptops, xBox, HP Touchpad, etc). So, I know it's not the config of the router.
Anybody have any idea of what's going on with this thing? My wife doesn't want me to root it, but I'm getting close. However, please do not just suggest rooting it, because I would really like to resolve this wifi issue with the stock build.

dvsDave said:
So, my wife got a Droid RAZR M. First thing we did was download the 2 updates from Verizon. Current version is 98.18.78.XT907.Verizon.en.US
I get home, and go to connect to my FIOS Actiontec MI424WR-GEN3i running the latest firmware available. (40.20.7)
Running WPA PSK, in b/g/n compatibility mode, with SSID on.
The phone refuses to connect. It will see the SSID, an even automatically identify that it's WPA PSK security. But when I go to connect, the signal drops to almost nothing, then doesn't connect. I make it forget the network and start fresh, same thing. Reboot the phone, same thing.
WPS is not active on the FIOS router firmware, so I can't try to connect via WPS.
I've got a Galaxy Nexus connected to the wifi and about 6 different wifi devices (laptops, xBox, HP Touchpad, etc). So, I know it's not the config of the router.
Anybody have any idea of what's going on with this thing? My wife doesn't want me to root it, but I'm getting close. However, please do not just suggest rooting it, because I would really like to resolve this wifi issue with the stock build.
Click to expand...
Click to collapse
I don't think rooting it will solve the issue. have you tried changing the router to WEP?

jco23 said:
I don't think rooting it will solve the issue. have you tried changing the router to WEP?
Click to expand...
Click to collapse
The m works fine on WPA PSK(as I am connected to a WPA PSK network as I type this).
This sounds like some of the bugs that have been reported before.
If I were you, I'd try a factory reset, and if that doesn't work, go back to the store. Since you're not rooted, you've got a good warranty claim. Last option is to root and try WiFi connection fixer, which worked for me in the past.
Good luck...
Sent from my XT907 using Tapatalk 4

sloosecannon said:
The m works fine on WPA PSK(as I am connected to a WPA PSK network as I type this).
This sounds like some of the bugs that have been reported before.
If I were you, I'd try a factory reset, and if that doesn't work, go back to the store. Since you're not rooted, you've got a good warranty claim. Last option is to root and try WiFi connection fixer, which worked for me in the past.
Good luck...
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Turned it in under warranty today. Turns out the speaker you use when you hold the phone to your ear didn't work (my wife normally uses the speakerphone, so she didn't discover this till last night) We'll see what happens when we get it back next week. Worst part? They gave her this old LG Vortex running 2.2 as a loaner phone..... she is going nuts trying to deal with the low-res tiny screen and going back to 2.2 after being on 4.1 for so long really sucks.