• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

WiFi is TERRIBLE

Did you folks having issues try setting a static IP (and related values, i.e., subnet, DNS, gateway)?
 
[DT];1223850 said:
Did you folks having issues try setting a static IP (and related values, i.e., subnet, DNS, gateway)?

That works (kinda) for the home access point issues, but not for the enterprise AP stuff. But cmon we both know you can't go around trying to figure out what the static IP should be at every starbucks. :)
 
My wifi works just fine. I'm using it now to post this from my Captivate. The signal strength is 2/3. I'm connecting via a Verizon FIOS router/modem.
 
Everyone whose WiFi is working could you maybe stop browsing, hit the home button, play with a few things, and then go back to browsing. Maybe try this multiple times or in an area where you only have 1/3 bars?

Thanks guys.
 
Everyone whose WiFi is working could you maybe stop browsing, hit the home button, play with a few things, and then go back to browsing. Maybe try this multiple times or in an area where you only have 1/3 bars?

Thanks guys.
I have 2/3 bars right now but I did try this and it's working fine for me. I have run into this problem right after I wake the phone though. But once the connection is made it seems solid.
 
Somebody's going to have to start taking these things apart and looking at build numbers and lot numbers and so forth. Might be bad batches of kit.
 
That works (kinda) for the home access point issues, but not for the enterprise AP stuff. But cmon we both know you can't go around trying to figure out what the static IP should be at every starbucks. :)

True, but I was thinking it was probably hardware specific, so depending on what's in place at the 'Bucks, it might be OK :)

I had an old[er] notebook that would not work on the new router here at the World HQ, but was fine on the older one.

The PS3 here will work fine with the router open or WEP, but won't configure using WPA/2 (but works fine with a static setup).

I think there's just lots of flakiness with all these devices and the security protocols (especially in mixed mode operation). Agree it's sort of a drag, but I'm willing to wait (and hope) future updates clear this up a bit.
 
Well most likely you are correct and the radios are fine, and just need a software or firmware update. But we have had in the past a certain well respected brand of enterprise wireless equipment that had a somewhat similar problem that turned out to be actual chip defect (which they have still not fixed, btw).
 
I have been doing some testing and may have determined part of the problem. I have 2 access points at my house that share the same SSID and channel. A working WiFi device is able to automatically switch to the AP with the strongest signal without losing connectivity. This is where my Captivate runs into problems. If I have just 1 AP running, I have no connectivity problems. When the second one is enabled, my Captivate starts to choke. The status bar shows that I am connected to WiFi, but I am unable to access the internet.

It seems that when the phone is trying to switch access points something gets locked up and it gets stuck. The only way to fix the problem is disabled WiFi reconnect.

I believe this is the same issue that others are having with their Cisco APs. It's not the access points, it's something in the phone as it's trying to switch between APs.

I talked with a Samsung Representative for 30 minutes today and explained the problem. He said that have no fixes for this issue and that they were unable to test the problem because they only have one AP. He made a detailed note of my description of the problem and said he would forward it on to the right people.
 
Geez if only they could fix this all up with an update.

I exchanged my phone today for a new one and so far so good. I will be rooting and sideloading soon and will report back to say if it could be a problem.
 
You didn't by any chance record your ROM/OS/etc version number from the old phone did you? I'm just curious if there's any differences in phones currently in the channel.
 
[DT];1236952 said:
You didn't by any chance record your ROM/OS/etc version number from the old phone did you? I'm just curious if there's any differences in phones currently in the channel.

Any place to find that info?
 
Yeah, that's the place.

My firmware is 2.1-update1 and my kernel is 2.6.29 (Eclair)
 
There is definitely a problem with galaxy s wifi software. It randomly makes wi-fi sleep without notifying the user, hence the frequent disconnection.

The solution is the plug your device, when connected to wi-fi. While charging, it doesn't need to sleep at all, hence no disconnection.
(Cross-posting to some other thread)
 
There is definitely a problem with galaxy s wifi software. It randomly makes wi-fi sleep without notifying the user, hence the frequent disconnection.

The solution is the plug your device, when connected to wi-fi. While charging, it doesn't need to sleep at all, hence no disconnection.
(Cross-posting to some other thread)

The only thing to stop sleep is to go to Connections > Manage Wifi? > Advanced Settings, and change the sleep settings during screen sleep.
 
Been experiencing the WiFi issues too. I have wifi set to always on. Left home and came to work >>> It shows connected and the WiFi bars, but it wouldn't actively work on the network. I had to disable and reenable it.
Also last night at home after the phone was sitting unused for a couple hours, I pick it up and the WiFi is not working again despite showing connected. Turning off and on connected it again.

I'm also wondering if the Task Killer is killing some radio connection in the background. Mine is set to kill every two hours. Although when I manually kill tasks it doesn't kill the WiFi, so ??????
 
Does anyone that is having problems, have root access? If so, see if you can download wifi analyzer. With that, I was able to see multiple routers with the same name, and I think my Captivate is having problems deciding which one to connect to. That's the only thing I can think of, cause when I'm at home, it works. But when I'm at work, it can't connect at this one spot (but can in other locations).
 
Mine shows connected with the WiFi signal, but it won't pull up the page. I need to disable and reenable the wifi.
 
My phone works just fine connecting to my WPA2 wifi network at home. At my work it says it connected but I can't actually see any pages in the browser. This is the same for behavior WPA2-enterrpise and a WPA2-personal networks. I think its a bug in how it handles DHCP. I changed to using a static IP and everything works great now. So my workaround is to get an IP address first through DHCP and then set that as my static IP address. It works, but its really, really lame.
 
I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.

Installing WiFi Buddy from the market allowed me to access these connection settings.

I just used an address from our static IP pool.

Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network :)
 
I have a D-Link g/n at home running WPA, I haven't come across any issues yet. I'll mess around with some settings when I get home and post again if I happen to find anything out of the ordinary.
 
I'm also having horrible wifi issues similar to those stated above.

Anyone have a fix besides setting wifi to never sleep? (didn't help) Any word on a software update that may fix this?

I really love this phone and don't want to take it back but I bet the iphone4 will work just fine on my wifi.

A smart phone with no internet is basically useless.

.02
Russell
 
I'm also having the issue of wifi showing connected, but the phone not loading anything requiring data. turning wifi off then on doesn't always work.

I've emailed samsung about it, waiting on a reply of some sort.
 
Back
Top Bottom