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.
Related
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 added the EI03 ROM for the verizon LTE tab. Everything was great, only problem was it was a little slow. Had it for two days. Today, I get home form work and the damn thing wont connect to Wifi. It sees my home network but gets stuck and says "obtaining IP adress". The crazy thing is I can connect to 3g or LTE with no problem...My Driod Bionic and this laptop are currently on the same network.
Heres what I have done...
1) I unplugged my router and modem for ten minutes twice.....no luck
2) I tried the Allshare work around that peopl posted about...nothing
3) downloaded the galaxy tab DHCP fix app ....nothing
4) reset the tab at least 7 times....nada
I am guessing this is the 3.2 Build? I got nothing else. I am guessing I have to reload 3.1 and go back to liquidspeed....
Am I missing someting? is there ANY suggesitons?
Thanks in advance
You've probably done it but haven't listed it; delete wifi network settings for your network and set that up again . . . then if that doesn't work delete ALL wifi network settings for ALL networks you've connected to and set up your network again . .
If after all that you still get nothing, see what happens when you strip all network security temporarily from your network, just to see if wifi is truly hosed on the tab.
Just brainstorming things I'd try before going back to Liquidspeed.
So far my wifi has been rock solid for the past two days. At home I'm running WPA2 Personal and at work I'm running standard WEP. I toggle my wifi on/off when I leave either location and haven't had any connection issues thus far.
I did that as well. Literally everything connected to the router without encryption on except the tab. It just was suck on "obtaining IP address"
after some research this seems very similar to the wifi cutoff issue the wifi only owners had with the 3.2 official OTA update that Samsung had to fix.
I'm hoping this isn't the case. Any body else got any other suggestions
Sent from my DROID BIONIC using Tapatalk
UPDATE
I see what went wrong. In an effort to re root the tab, I applied Kernel.zip that should only be used for 3.1 LTE devices.
I reloaded TW 3.2 on the LTE and could connect to wifi immediately. When I tried to root again, I applied kernel and this happened again.
Apparently I dont get this. Oh well. I a, gonna go back to EG01 where I am comfortable rooting and Overclocking.
The instructions said to apply Recovery (the new one), but ti continued to fail, so I assumed I needed to apply kernel first. This is just not working for me.
I tried and failed about 4 times. back to the original rom it is
reloading 3.2
How did you reinstall 3.2? I'm having the same wifi issues on my GTab LTE.
Here's my problem, and I've seen many problems with wifi here and on other forums but nothing exactly like this.
When I'm at work, my phone connects to the network over there without any problem but, every time I come home, it simply shows my network as "Not in range", even at 2 feet away from the router (WPA PSK security). I've tried turning wifi off and on, resetting my router, "forgetting" my network on the phone. Nothing does the trick unless, I restart my phone and then it connects automatically and stays connected until I leave.
Something strange I noticed tonight; I went to my son's hockey game and, at the arena, I noticed it still showed as connected to my home network!?!?!!?
I started noticing this issue a few days ago, after flashing the 4.2.2 image from Google. My phone is rooted and is running the latest clockworkmod recovery but otherwise, still stock.
Something else I just noticed; my Nexus 7 doesn't have the same issue...
Anybody else having the same issue? Any hints on what's going on?
I also have this issue. But I had the problem before 4.2.2
Sent from my Nexus 4 using xda premium
Got to work this morning... wouldn't connect to the network here because... It was still connected at home, 40km away. That's a powerful router!
Any clues as to what might be the cause?
What brand/type of wireless router are you using? What type of security?
We gotta be more than 2 with this problem... I've seen so many issues with wifi with this phone on other threads... Weird
Last night I went to my parents and again, my phone wouldn't connect to their home network so, its definitely not my router. So I made a backup of all my apps and returned to 4.2.1 and voila, wifi problems are fixed, for now...
I have the newest fw for my S5 and I have a lot of problems with WiFi. Sometimes I just get the err_name_not_resolved
In chrome and then I have to disable and enable WiFi and everything is OK again for perhaps an hour or a day... My phone also keeps getting warm and I suspect it has something to do with WiFi?!
I have tried reinstall my phone and my router is a Asus new one.
Please help. I had problems with WiFi since galaxy s3... (On different routers)