Has the wireless network bug been fixed?

[masterz13]

With my home network, I have to use the Allshare app to access my wireless settings to connect to my network. I try using the normal way (settings > wireless), but it always ends up disabling the connection. I am currently using Froyo. Any help would be appreciated.

 

[Buddha64]

My phone connects to my Linksys (E2000) 801.11x wireless router without so much as a burp. I've never had to do what you describe.

What "bug?"

Edit: You need to provide more info other than, "It ain't working, please help." Like how about the type of router are you using? What are you connecting to via AllShare?

If your phone cannot connect to the router, but it can connect to another Samsung device via the wireless, it doesn't sound like you have a phone/wireless issue. Could it be your router set-up that is the issue and not your phone? Is there a limit on the number of connections your router can have?

 

[George0211]

Never heard of this problem either.
Also, does the phone turn off the wireless modem by itself or it just doesn't connect to your router?

 

[james27007]

I have a FiOS router and 50% could not get a solid conntection, kept saying "Aquiring network connection..." until I found this thread: [WiFi] DHCPCD Issues and How To Avoid Them (ROM maintainers please read) - xda-developers has worked 99% of the time since.

 

[masterz13]

Yes, that's the error. My home network is the only one to do this to me, and it never did it when I had 2.1. When I try connecting from settings, it'll say acquiring network address for a long period of time, and then it will say disabled. If I open the Allshare app and then connect through it, it connects easily. I tried doing what the above poster said, but I can't find my /system/ folder on my phone, even though it's rooted.

 

[masterz13]

Update: I downloaded an app called fxr wifi from the market and apparently it fixed it. I can now connect to my home network within a couple seconds and everything works fine. I'll let you know if it reverts back to the error though.

 

[Squiner]

Update: I downloaded an app called fxr wifi from the market and apparently it fixed it. I can now connect to my home network within a couple seconds and everything works fine. I'll let you know if it reverts back to the error though.

Worked for me too, thanks for the tip!

 

[gorf]

Over time, I developed issues with a number of Linksys routers and access points. I tried all of the suggestions made by other frustrate people: android apps, forcing G, etc. The only thing I didn't try was DD-WRT, as others had already gone that route with no success.Nothing solved the problem. I was about ready to chunk the phone.

I switched to a D-Link WAP-1522 (in forced N-mode) and never had any issues. I then switched to an Apple Airport Extreme (also using N) and the connection is still rock-solid. I have been mirroring the port on my ProCurve 1810-24g switch that is connected to the WAP and logging the syslog traffic via Splunk for analysis. I can definitely tell you one thing, the Airport Extreme does a far superior job to either the Linksys or the D-Link in maintaining sync with my NTP server (HP DL-380 with Scientific Linux 6.0).

So, in my case, I ditched the Linksys range and have had no problems since.

 

[jeanbean5]

how do i stop allshare from running on my skyrocket