Captivate, Froyo and WiFi

[JonDeutsch]

WiFi problems after Froyo Upgrade

Ever since upgrading to Froyo, my WiFi functionality has started acting flaky.

Sometimes, when I get home and turn on WiFi, it just "hangs." And requires a reboot. Sometimes, when I get home and turn on WiFi, I get an "error" and I have to toggle WiFi on again manually and then it 'takes.'

A few searches have shown me that this is not a common problem. This never happened to me before the Froyo upgrade.

Any ideas?
Thanks!
Jon

 

[Raven71]

Look at the last page of the offical froyo update 2.2 features that I put in yesterday. It is a common problem and I put some things in that I tried. So far using the all share seemed to get my wifi working, but I don't know if using the terminal enumerator helped by deleting the code and then letting it boot up. If that needed to be done before the all share program was used. So far my wifi is working again without any problems. Now if my battery would last more then 4hrs, or 40 minutes of solitaire before I no need to recharge.

 

[Raven71]

Well seems like if I try to hook up to another wifi spot and then come home and try to get back onto my ssid. I have to go through using the terminal app and then use all share to get it to work.
Also it wasn't able to hook up to the ones I usually do when away from home. It also drains my battery trying too communicate with the one I'm trying to get connected with. I'm bringing the phone to att store to see if they know wtf is wrong.
I wouldn't care if this was a outside build, but this is the offical froyo from att. The amount of time we waited to get it from them to make sure it worked right, you think that these problems would not be here. If it was only a couple of phones I would say it is a fluke. Seems like there are to many people having this problem along with battery drain complaints.

Should I un root my phone and remove titanium back up and rom manage before I bring it back for them to look at?

 

[valentine14]

Has anyone found a fix or anything yet? Or called ATT or Samsung?
The same this is happening to me too on 2.2 official froyo
I had to send it in to Samsung since it was powering itself off and got it back a couple weeks ago. Been my perfect little phone until today! It is also switching from "obtaining IP address from.." to "disabled" and once it said "remembering" for a few seconds before going back to the first message.
I tried the FXR and it didn't do anything for me. I forgot the network, rebooted, anything I could. All other devices are working on my wifi without issue.

 

[SlappyMcgee]

I have posted this before in android forums and XDA.

I had a friend who was having issues with her phone not even attempting to scan for wireless, seems there is an issue on android phones that the networking cache file or whatever it is gets cluttered and needs to be renamed. (Android recreates it)

The process is rather simple, I walked my friend through the steps over the phone w/o issues.

I had her use oneclick root/unroot to root her phone.
[PROGRAM] Updated:One Click Root/UnRoot (Mac and PC) - xda-developers

Then Had her go through these steps to rename the file.
http://androidforums.com/samsung-mom...-networks.html

The steps are for a samsung moment but still work. Also noted that the steps w/o rooting do not work. After you finish renaming the file you can use the application in the first link to unroot the phone and go back to stock

 

[Bmoe320]

I am having the same issues, beginning about 2 days after a hard reset of Froyo. I will try FXR, but have talked to Samsung and they say WiFi is a AT&T issue. Waiting for a response beyond a hard reset from AT&T.

 

[Bmoe320]

I fouind another thread and it directed me to the all share app. I turning it on and I suddenly got connected. Wondering if this is making some sort of coflict? It has gotten me back on wifi at a Starbucks that was performing the same as at hoime. Hopefully it will work at home too.

 

[valentine14]

My internet has been acting weird the last week or so, they came out to fix it yesterday. Since I was online on my computer and iPod connected I thought why wouldn't my phone work? This morning the internet cut out again but when I reset my router it came back with no problem and my phone connected to it. Maybe it wasn't a froyo problem for me or the FXR worked.
If it happens again I'll know what I can do to fix it! Thanks!

 

[Raven71]

Once you have rooted your phone restart the device and then go to the Android market place and download the App “terminal Emulator” open the terminal emulator app and then enter the fallowing commands.

su
cd /
cd data
cd wifi
ls
After this command you should see a file “bcm_supp.conf” If you do not then you have done something wrong. Log out of the terminal emulator and log back in and start over.

rm bcm_supp.conf
After this file has been deleted log out of the terminal emulator and reset your device, after the full reboot has happened restart WiFi and begin your quest for data.

I had to do this again but I also had to refresh my router. I have VERIZON FIOS with a actiontec M1424WR. I refreshed only the IP address that my phone connects to. This was on the advice of Verizon. So far it has connect almost instantly, without the use of all share. Now this might not last because it seems after a couple of days it starts acting up again.

 

[SlappyMcgee]

Yep thats the instructions in the links on my post Of course I would recommend just renaming the file instead of removing it just in case.

 

[Raven71]

Yep thats the instructions in the links on my post Of course I would recommend just renaming the file instead of removing it just in case.

Yep I figured I just post it instead of having to switch back and forth. What I can't understand is that if it is a corrupt file like being posted. Why when you remove or rename it does it not become corrupt when it installs again. After all it is on the phone already that was downloaded from the site.
something is not right and both att and samsung keep passing the problem too each other. There are to many people having this problem and they should address the dam problem already. Also the battery life sucks. I'm going back to Eclair with the voodoo lag fix, or try a custom Froyo first.

 

[SlappyMcgee]

When you delete or rename it. Then go into the Wifi and recreate a connection Android recreates the Wifi Cache file.

Think of it like deleting temp internet files. Once the cache starts getting cluttered, in your browser, it is no longer performing its purpose, i.e. storing caches settings so web pages load faster. and pages start taking longer to load or plug-ins do not load properly. So you delete temp internet files, when you visit websites again, it downloads and stores new cache files and the pages load properly and sometimes faster.

 

[Raven71]

Thanks I was under the impression that it was a file written for the wifi itself. Not just a folder like you explained. I guess the rom is what controls the way the wifi works or kennel. So is there a way to increase the size of temp data the folder can hold. So far with what I have done it is connecting instantly, without the use of all share. Still if this is only going to last until the file gets full, that's not going to be good. I guess for some reason the file is not realizing it is full and needs to make room.

 

[summersrl]

Download the FXR wifi fix app from the market, select "fix my wifi" and reboot. Worked perfectly for me.

I just experienced this issue for the first time. I upgraded to 2.2 when it first came out a few weeks ago. After reading the posts in this thread (and... thanks to all who have resolved this before me and have posted their results!) I tried the FXR fix. I'm happy to report that it worked. I certainly hope this does not become a recurring issue.....

 

[SlappyMcgee]

Thanks I was under the impression that it was a file written for the wifi itself. Not just a folder like you explained. I guess the rom is what controls the way the wifi works or kennel. So is there a way to increase the size of temp data the folder can hold. So far with what I have done it is connecting instantly, without the use of all share. Still if this is only going to last until the file gets full, that's not going to be good. I guess for some reason the file is not realizing it is full and needs to make room.

MY terminology didn't explain it well. Its a cache file that gets corrupted, its not that it is full its just corrupted (cluttered) but by deleting it and allowing the OS to recreate it, it removes the corrupt information. Think format reinstall of Windows Gives you a nice fresh start

 

[madskeelz]

After upgrading to Froyo 2.2 I experienced issues similar to the ones described in this thread on my Samsung Captivate. When trying to connect to the wifi at my home the device would continuously go through the following loop:

1. A message about connecting to wifi
2. A message that it was connected, and obtaining an IP address
3. A message that the wifi was disconnected, then back to #1

The wifi worked perfectly before the upgrade to Froyo 2.2.

A chat with ATT support yielded no help. My favorite part of the chat was at the end when the support rep asked if all my questions had been answered today with a straight face. Well, I assume it was with a straight face anyway.

Fortunately the FXR app took care of everything. Installed it, ran it, clicked the "Fix My WIFI" button, rebooted and everything was back to working.

 

[JonDeutsch]

Sadly for me, FXR did NOT work! I still get an "error" status about 1/2 the time I turn WiFi on. Sometimes, cycling through again will remove the error. Sometimes, I need to reboot.

Any other ideas?

 

[SlappyMcgee]

Jon - did you try the instructions that Raven and I posted?

 

[JonDeutsch]

Jon - did you try the instructions that Raven and I posted?

Hey Slappy,

I would, but it requires a rooting of the device. Believe it or not, I've been trying so hard not to root my phone because I come from WinMo6.5 and I "rooted" myself to death. I changed OSs in part so I could get out of the rooting business and get into enjoying a more effort-free lifestyle!

Is there a way to "root" for this procedure and then immediately unroot?

I'll be honest, I hate the AT&T lock-down on sideloading, and I am not a huge fan of the AT&T HotSpots app always running in my task manager.

And, lastly, I wish there were a way to have Android chill out on how many apps it pre-loads preemptively,which slows down my phone. So, maybe if rooting could solve all of these issues, I'd do it.

But right now, I just want my WiFi to work...but I would also like to have my phone "supportable" by AT&T in case something goes wrong.

Any insights appreciated.
Thanks,
Jon

 

[SlappyMcgee]

Jon, yes after you rename the file you can use the oneclick root/unroot to unroot the phone. Then you are back to normal