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

Help Captivate WiFi Issues - Again

C

camosoul

Lurker
I have looked at several other threads on the matter, but none seem to be 100% identical, not have any of the fixes worked for me.

My Captivate USED to work fine on WiFi. I put the Unofficial Froyo on it as soon as I got it from AT&T. It has worked fine for a long time. Until now. WiFi will not connect to anything, ever. As this did not occur when I installed the Unofficial Froyo, and it worked for a very long time afterwards, I doubt his is related. I just wanted to mention it for the sake of being thorough.

Says "Obtaining IP address from..." then "Disabled"

I have 4 other computers that connect to the WiFi without issue. In spite of this, I have tried the following:

I have hard reset my router to defaults. All other computers connected with no trouble. Captivate would not.

I disabled all security on WiFi. All other computers connected with no trouble. Captivate would not.

I had changed all WEP/WPA/WPA2/No Security and SSID in random combinations. I have changed channels as well. Every time, all computers connected with no issue. Captivate would not.

Captivate will "see" any WiFi network, it will identify Open or security type(s). It will display signal strength. I can tel it to "forget" but this has no effect.

When told to connect, it will say "Obtaining IP address from..." and then after about 30 seconds, "Disabled."

I have Rebooted many, many times. I have removed SIM/SD, etc. I've done everything I can do to it. It will not connect to any WiFi anywhere, ever.

WiFi Router works flawlessly with any other device regardless of Security/SSID/Channel.

If I had a way to wipe the Network Data via Console/Command Prompt, would that matter? I'm not a noob. I've been running Gentoo Linux for nigh on a decade. Clearly, there is something wrong here. I need a way to get at the problem.
 
I'm a bit of a noob (not completely), and what worked for me (I had this EXACT problem) was this:

Samsung Galaxy S WiFi Issue Fix | BK Integration does IT easy

It took me about an hour to find a way to root that satisfied me, but in the end it worked out kinda well. Today, my phone is dead, and I'm not sure if that's because of the root, the wifi fix, or just because of random stuff I've done to the phone.

If you aren't a noob, I think you should look at that link and see what's going on. It seemed simple enough to me, although the effects of deleting that config file are pretty unknown I'm guessing (other than fixing wifi).
 
Apparently, those rooting methods do not work on the Unofficial Froyo.

The first method acts like it works, but once in Terminal Emulator, no root functions are available. su doesn't work. /data/wifi is off limits, ls command is off limits....

"rm /data/wifi/bcm_*"
Permission Denied.

su and sudo are 'not found.' Apparently, they don't even exist.

I then tried the second method:

"E:signature verification failed
Installation aborted"

So, both of those methods of rooting do not work.

Gotta kill this file...
 
Hi, Just bought a dell streak with Android froyo 2.2 in it. I am having issues with Wifi. Each time after wakeup, I have to manually go and connect to my default wifi connection. This is very much annoying. The system shows that it is scanning and shows a list of wifi connections. But against my default connection it displays a message disabled. Dont know why. But, my iphone is quickly finding the network and connecting. Please help. Screen Shot is here: : Android wifi settings menu | Flickr - Photo Sharing!
THanks in advance for your help... If i cant find a solution to this problem, only option is to sell streak and go for iphone 4 - the no problem phone.
 
vvmenon said:
only option is to sell streak and go for iphone 4 - the no problem phone.
Click to expand...

There are plenty of other options. The Streak blows, and everyone knows that.

I cannot imagine you did any research before buying it.... You wouldn't have if you did.

iPhone is a Child's Toy.
 
i have a similar issue - sometimes it connects to wifi when i pull into the driveway, other times i have to manually reset the router (dlink). secured with wpa2/psk if i'm not mistaken.

anyone know of a work around where i DONT have to root my phone? that seems to be the answer to a lot of problems but the cause of just as many, it's an issue i'd like to steer clear of. plus i dont want to brick a very expensive phone, there's too much to consider.

also, i was wondering what unofficial froyo was. it was my understanding 2.2 was 2.2.

thanks a bunch
 
Ravenspine said:
also, i was wondering what unofficial froyo was. it was my understanding 2.2 was 2.2.
Click to expand...

No. Each 2.2 is customized and tweaked for the specific device hardware it's targeted at. Sometimes the source code is available allowing for full hacking, other times just the binary files are available forcing people to experiment mixing and matching pieces with other parts to see what works best.

Most of the unofficial 2.2 ROMs for the Captivate use foundations from non-Captivate Galaxy S phones as they have source available and newer files. However, this often leads to quirks since the hardware isn't exactly the same.
 
After the official Froyo update my captivate wouldn't connect to the wifi even though my computer would connect. It would stay in "obtaining IP address" for a while and then turn to disabled. Tried messing with the router without success. Finally I downloaded "FX Wifi Fix" from the market. It seems this deletes all previous wifi network information in your Captivate and searches for them again. This worked perfectly!
 
Mine won't connect now either when the security WEP security is turned on. When I turn the security off, it connects just fine.
 
I have the same problem. When trying to connect to wifi I get an 'obtaining IP address' message for 30 seconds then 'disabled' then 'connecting' then it loops again to the obtaining IP address message...


I have connectedto this router before and never had a problem until I updated to froyo. Also couldn't find fX wifi fix in the android market.

OK seems like I fixed it. For those having trouble try opening your allshare app. Then try connecting to your desired network. Mine connected after about 10 seconds
 
camosoul said:
I have looked at several other threads on the matter, but none seem to be 100% identical, not have any of the fixes worked for me.

My Captivate USED to work fine on WiFi. I put the Unofficial Froyo on it as soon as I got it from AT&T. It has worked fine for a long time. Until now. WiFi will not connect to anything, ever. As this did not occur when I installed the Unofficial Froyo, and it worked for a very long time afterwards, I doubt his is related. I just wanted to mention it for the sake of being thorough.

Says "Obtaining IP address from..." then "Disabled"

I have 4 other computers that connect to the WiFi without issue. In spite of this, I have tried the following:

I have hard reset my router to defaults. All other computers connected with no trouble. Captivate would not.

I disabled all security on WiFi. All other computers connected with no trouble. Captivate would not.

I had changed all WEP/WPA/WPA2/No Security and SSID in random combinations. I have changed channels as well. Every time, all computers connected with no issue. Captivate would not.

Captivate will "see" any WiFi network, it will identify Open or security type(s). It will display signal strength. I can tel it to "forget" but this has no effect.

When told to connect, it will say "Obtaining IP address from..." and then after about 30 seconds, "Disabled."

I have Rebooted many, many times. I have removed SIM/SD, etc. I've done everything I can do to it. It will not connect to any WiFi anywhere, ever.

WiFi Router works flawlessly with any other device regardless of Security/SSID/Channel.

If I had a way to wipe the Network Data via Console/Command Prompt, would that matter? I'm not a noob. I've been running Gentoo Linux for nigh on a decade. Clearly, there is something wrong here. I need a way to get at the problem.
Click to expand...



I had the same problem. Samsung issued 2.2 through kies mini so. Both my wife and I have the captivate. I started on mines first. The upgrade went flawless until i tried connecting to my home wifi. For some odd reason the I have 2 laptops and 2 destops including these phones that conected through this connection with no problem and now nothing connects. I tried all of the suggestions below and nothing worked including resetting the belkin router. I remembered I had another wireless router so I switched them out. but before I did that I turned all wifi's off. Once I connected the new router and power on all wifi's, and everthing connected just fine. That took me close to 2 hours to figure this out. I then did my wifes phone. But this time once the download completed and restarted the phone I unplugged the router. Once the phone fully booted to idle, I turned on wifi and let t search for a few minutes then I plugged in the router. This time there no issues. By the way the upgrade has some cool features added and gps works now.
 
My Captivate USED to work fine on WiFi when stayed 2.1 but after updated to 2.2, unable to connect my home WEP. Says "Obtaining IP address from..." then "Disabled" I could connect WPA at office but no WEP at home.

After all kind of twiking on router and different sec settings but no luck, I downloaded "FXR WiFi fix and rescue" and fixed all problems in few minuets.
 
Just wanted to confirm that the app "FXR WiFi Fix" in Android Market works !! ;)

I own a rooted Captivate running un-official Froyo 2.2 with OneClick LagFix and had this issue for several weeks. Tried numerous fixes posted here and on XDA forums with NO luck ... didn't want to resort to total reset & wipe ...until I found this fix in the market.

Don't thank me ... thank owner. The app works with some other Android phones ... see app description for listing.
 
I had the same issue on my fascinate running OS 2.2. djsmvp's fix worked for me. I opened AllShare, then wifi connected. Thanks djsmvp
 
djsmvp said:
For those having trouble try opening your allshare app. Then try connecting to your desired network. Mine connected after about 10 seconds
Click to expand...

Red is because djsmvp is my love!
desire.gif


before trying all these other fixes i tried turning allshare on and exactly 10 seconds later i was in business.

this fix needs to be google bombed!!
explode.gif
explode.gif
explode.gif
explode.gif
 
You must log in or register to reply here.
Back
Top Bottom