Database Develop

WiFi DoA on my Tilt/Kaiser?

Hello Everyone,
I'm looking for either a confirmation that my my WLAN is bad, or suggestions on other things I should try before taking it back in for replacement.
Searching and browsing through the forums I didn't see anyone mention any of the problems I'm having so I'm assuming I'm the only one (or one of very few) that bought a Kaiser with a defective Wifi radio.
Here's the symptoms:
I tried connecting to my wireless connection at home maybe a day or two after I bought my Tilt (last Friday). My home connection is draft 802.11n with WPA2-PSK security.
So I enable the WLAN and it detects my Wifi network and it asks for the key. I input it and then it tries to connect, but... it never does. I tried it a few times consecutively and it still didn't work (I get the animating arrows and the 'halo' around the beacon, but then it goes away, and it just keeps doing that). Now, I've seen this before with on my XV6700 with a beta ROM of WM6, but I know well HTC and AT&T wouldn't release something with broken WPA/2 support. At least HTC, I thought...
So I unlocked my Tilt and loaded the factory Kaiser ROM I downloaded from here, and well, WPA2 didn't work on it either. Weird, I thought, so I searched forums and no one mentioned any of this. So I changed my security settings on my network to WPA-PSK (from WPA2) and that made no difference at all... I don't want to bore y'all with everything else I tried, but to sum it up, I then tried a WPA fix I found on PPCGeeks, but that just ended up making my WLAN staying disabled, so I unintalled that and I decided I would try it with a WEP or Open wireless network.
Well, this morning I did just that and even when I try to connect to a wireless connection with WEP, I get the same behavior when I tried this at home with WPA. I've triple checked the WEP key, and I know it's right.
I haven't tried it on an Open network yet, but I'm assuming I'm going to get the same results. I'll have to find a wireless router no one's connected to so that I can try this out, but it might take me a while. Should I even waste anymore time on this? Anyone else here having (or had) the same problem?
I might start loading the AT&T ROM on this soon so I can take it back, but if any of you have any suggestions, I'm all ears.

Wow. Am I the only one on here who's having this problem?? Lucky me, I guess... :S
Anyway, I just tried connecting to a public and open wifi network here in SF, but my Kaiser still wouldn't connect. Guess that confirms it: my WiFi adapter is defective.
Anyone know if I can get it replaced in a different store from where I purchased it, and what I need to take (hope it's just the phone)?

d0ubl3_d1zzl3 said:
Wow. Am I the only one on here who's having this problem?? Lucky me, I guess... :S
Anyway, I just tried connecting to a public and open wifi network here in SF, but my Kaiser still wouldn't connect. Guess that confirms it: my WiFi adapter is defective.
Anyone know if I can get it replaced in a different store from where I purchased it, and what I need to take (hope it's just the phone)?
Click to expand...
Click to collapse
just tried my wifi on the tilt ... works fine out of the box (to my home secured wireless network)

d0ubl3_d1zzl3 said:
Hello Everyone,
I'm looking for either a confirmation that my my WLAN is bad, or suggestions on other things I should try before taking it back in for replacement.
Searching and browsing through the forums I didn't see anyone mention any of the problems I'm having so I'm assuming I'm the only one (or one of very few) that bought a Kaiser with a defective Wifi radio.
Here's the symptoms:
I tried connecting to my wireless connection at home maybe a day or two after I bought my Tilt (last Friday). My home connection is draft 802.11n with WPA2-PSK security.
So I enable the WLAN and it detects my Wifi network and it asks for the key. I input it and then it tries to connect, but... it never does. I tried it a few times consecutively and it still didn't work (I get the animating arrows and the 'halo' around the beacon, but then it goes away, and it just keeps doing that). Now, I've seen this before with on my XV6700 with a beta ROM of WM6, but I know well HTC and AT&T wouldn't release something with broken WPA/2 support. At least HTC, I thought...
So I unlocked my Tilt and loaded the factory Kaiser ROM I downloaded from here, and well, WPA2 didn't work on it either. Weird, I thought, so I searched forums and no one mentioned any of this. So I changed my security settings on my network to WPA-PSK (from WPA2) and that made no difference at all... I don't want to bore y'all with everything else I tried, but to sum it up, I then tried a WPA fix I found on PPCGeeks, but that just ended up making my WLAN staying disabled, so I unintalled that and I decided I would try it with a WEP or Open wireless network.
Well, this morning I did just that and even when I try to connect to a wireless connection with WEP, I get the same behavior when I tried this at home with WPA. I've triple checked the WEP key, and I know it's right.
I haven't tried it on an Open network yet, but I'm assuming I'm going to get the same results. I'll have to find a wireless router no one's connected to so that I can try this out, but it might take me a while. Should I even waste anymore time on this? Anyone else here having (or had) the same problem?
I might start loading the AT&T ROM on this soon so I can take it back, but if any of you have any suggestions, I'm all ears.
Click to expand...
Click to collapse
This is what I did. Start->settings->connections tab->WiFI. Now you should see your routers name there with the signal bar next to it. Tap AND Hold the name, then go to settings or edit(I forget), then click NEXT, uncheck the box that says "the key is automatically provided"(thats for open access routers/networks that dont require codes). Then type in your code & make sure you specify what key # it is. click next and youre done. You should be able to connect.

silly question here. is your router broadcasting 802.11b or g? the wifi won't connect to anything else.

You might also check your AP to see if it's not broadcasting its SSID to the world (a common security setting). I couldn't connect until I enabled broadcast on my AP, set the network up, and then went back and disabled SSID broadcast.
Why in the hell this is a problem in the first place is beyond me, but this is the third smartphone/PDA with wireless that I've had to do that for. And every time, once the device found the network once, it never had a problem finding it again.

Believe me. I tried everything in the WiFi settings page. I edited the settings, removed them and added them again, and like I said before I even went and changed my security settings on my router (which to answer your question, zeta, it broadcasts in: n, g, and b. Same router worked with my Apache/XV6700).
Anyway, I stopped by the store where I bought it today and they told me that as far as he can tell, that does qualify for a replacement. The problem is they don't have any in stock to replace it with, and he has no idea when they'll be getting more in. They only received 2 on launch day, and I bought one of those. He did mention that I can get it replaced at any store, however, but they all might be in the same boat.
Guess I'll try another store tomorrow, but if not I guess I'll have to go through AT&T's tech support (don't like the sound of that) and get it replaced through them. So I guess this means I might have a few days to mess around with the phone and even try some risky thangs.
So if any of you developers and hackers, er, I mean tweakers need some1 to test something, I can be that guinea pig (for a while at least)... Just give me a shout.

To troubleshoot your wireless connection always try ruling out as many other factors as possible. So put your router to NO security (temporarily ofcourse) and have it broadcast 802.11g. Also make sure you add the mac address of your device to the list in your router, if it uses mac address filtering. Try connecting to it with a laptop and see if that goes fine. Work systematically...

PerfAlbion said:
You might also check your AP to see if it's not broadcasting its SSID to the world (a common security setting). I couldn't connect until I enabled broadcast on my AP, set the network up, and then went back and disabled SSID broadcast.
Why in the hell this is a problem in the first place is beyond me, but this is the third smartphone/PDA with wireless that I've had to do that for. And every time, once the device found the network once, it never had a problem finding it again.
Click to expand...
Click to collapse
I have a similar Problem, your solution works partly for me:
As soon as I enable the AP to broadcast it's ID, Kaiser connects.
But as soon as the ID is hidden, it does not connect.
Weird.
Is it a security problem if the ID is broadcasted, provided I use WPA2-PSK/AES?
Thanks
V

No. Hiding the SSID really only protects you from folks that are wandering around without any tools. Open up a more fully featured scanner, and it'll pull the SSID out of the air. The encryption is much, much more important.
And I also wouldn't bother with MAC filtering. Changing the MAC address is usually a software setting, so it's not all that much additional security. WPA/WPA2 are much better solutions.

Yeah, the hidden SSID is not an issue with me, since I don't mind broadcasting it at home. Not too paranoid about it. If someone *really* wanted to sniff and break into my network, they could. Don't do much important and highly confidential stuff at home anyway.
Plus, like Perf mentioned, there's software out there, even for PocketPCs, that will find so-called "hidden" SSIDs. Thanks for your suggestions, anyway.

d0ubl3_d1zzl3 said:
Yeah, the hidden SSID is not an issue with me, since I don't mind broadcasting it at home. Not too paranoid about it. If someone *really* wanted to sniff and break into my network, they could. Don't do much important and highly confidential stuff at home anyway.
Plus, like Perf mentioned, there's software out there, even for PocketPCs, that will find so-called "hidden" SSIDs. Thanks for your suggestions, anyway.
Click to expand...
Click to collapse
i had no issue connecting to my wrt54g running DD-WRT v23 SP2 with my SSID hidden with WEP enabled. when setting up a new connection, i just entered the name of the connection and then the WEP hex, and it connected flawlessly. Have fun hacking your phone until you can swap?

Mine is not working either. I exchanged the phone and found out that I was the 3rd person with the same problem.

BiPolarXpress said:
Mine is not working either. I exchanged the phone and found out that I was the 3rd person with the same problem.
Click to expand...
Click to collapse
Glad to hear, I'm not the only one.
I exchanged my phone this morning, and I just tried connecting to my wireless network and guess what??
I'm getting the SAME RESULTS.
Now, before anyone goes and tells me that my router is the problem or that it's user error, then tell me: why does my laptop, PS3 and my Wii connect just fine?? I even changed the SSID and WPA key last night and they all connected w/o a problem as well. All except my freaking Tilt.
Can be it a coincidence that I got 2 bad phones? I don't know if I should call the store and tell them to hold up on sending the other phone to HTC.
Which reminds me, I probably should try calling HTC today, but I doubt they'll be much help...

I don't think you're nuts, and I doubt you got two bad phones. But if you want to double-check, take the phone to your local Starbucks or other shop with WiFi and see if it can detect that AP.
But at this point, I'd be inclined to look for a firmware upgrade for your AP. I could be that it's not supporting long or short preambles right (a problem for some devices in the past), doesn't like seeing more than XXX different devices, or just doesn't like your phone much.
Either way, I'm smelling an issue with your AP. I had a US Robotics AP/Router that drove me nuts because it would spontaneously reboot after a random period any time an IPSec VPN was present.

try setting the power mode on best performance. when i do that i stay connected to wifi.

I took both my old I730 and my tilt to the coffee shop before I returned my first tilt. I was able to connect my I730 at the coffee shop and home, but couldn't connect the tilt at either place. I also tried some open AP's in my neighborhood that I have been able to connect to in the past with the same results. Picky phone or bad wifi radios maybe.

Jesus... like the bloke said:
1) Turn off wpa and see if it will connect (it will unless you have set your N router to only use "n") If it won't then send it back.
2) If it does... then turn on WEP 128bit on your router... and use that instead.
WM devices have always had problems with WPA...

Hi all.
I have tried my HTC TyTN II with one Wifi LinkSys WAG54GS Router using WPA and not hidding the SSID and works fine, no problem at all.
Test with one AP from DLink at the office, using hidden SSID and WEP 64 and 128 Bits and no problem at all, works as fine as my LinkSys.
I'm going to try hidde the SSID at home with WPA and WPA2 and post the results later to know if there is a common issue with Kaiser or some freaky coincidence.
Regards.

d0ubl3_d1zzl3 said:
Hello Everyone,
I'm looking for either a confirmation that my my WLAN is bad, or suggestions on other things I should try before taking it back in for replacement.
Searching and browsing through the forums I didn't see anyone mention any of the problems I'm having so I'm assuming I'm the only one (or one of very few) that bought a Kaiser with a defective Wifi radio.
Here's the symptoms:
I tried connecting to my wireless connection at home maybe a day or two after I bought my Tilt (last Friday). My home connection is draft 802.11n with WPA2-PSK security.
So I enable the WLAN and it detects my Wifi network and it asks for the key. I input it and then it tries to connect, but... it never does. I tried it a few times consecutively and it still didn't work (I get the animating arrows and the 'halo' around the beacon, but then it goes away, and it just keeps doing that). Now, I've seen this before with on my XV6700 with a beta ROM of WM6, but I know well HTC and AT&T wouldn't release something with broken WPA/2 support. At least HTC, I thought...
So I unlocked my Tilt and loaded the factory Kaiser ROM I downloaded from here, and well, WPA2 didn't work on it either. Weird, I thought, so I searched forums and no one mentioned any of this. So I changed my security settings on my network to WPA-PSK (from WPA2) and that made no difference at all... I don't want to bore y'all with everything else I tried, but to sum it up, I then tried a WPA fix I found on PPCGeeks, but that just ended up making my WLAN staying disabled, so I unintalled that and I decided I would try it with a WEP or Open wireless network.
Well, this morning I did just that and even when I try to connect to a wireless connection with WEP, I get the same behavior when I tried this at home with WPA. I've triple checked the WEP key, and I know it's right.
I haven't tried it on an Open network yet, but I'm assuming I'm going to get the same results. I'll have to find a wireless router no one's connected to so that I can try this out, but it might take me a while. Should I even waste anymore time on this? Anyone else here having (or had) the same problem?
I might start loading the AT&T ROM on this soon so I can take it back, but if any of you have any suggestions, I'm all ears.
Click to expand...
Click to collapse
I found that I couldn't get my Kaiser to connect to my WPA encrypted LAN - open access and WEP (64 and 128 bit) work fine.
Not sure what the problem is - maybe some incompatibility between the Kaiser and my Netgear router. I've downgraded the security to 128bit WEP for the time being but I'm hoping that there's a fix soon.

Verizon FiOS and Wi-Fi

Hey all. I saw a thread where an issue was briefly mentioned before but saw not resolution. I just had FiOS installed at my house last week and ever since then I cannot get to the internet when connected to Wi-Fi.
Just so there is not any confusion, I am able to connect to wi-fi and get an IP address. I am also able to access the verizon router's web page from my phone but cannot get out to the internet. It works fine on 3G and Edge.
The problem is seen on both my G1 (running Super D 1.5) and my wife's phone (Running CM 4.2.4).
Anyone else seen this problem and know a solution?

Sounds like a router problem. Get a different one, or turn all the security off on the Verizon and restore to default settings.

evilkorn said:
Sounds like a router problem. Get a different one, or turn all the security off on the Verizon and restore to default settings.
Click to expand...
Click to collapse
I already turned off all the wi-fi security and tried, still a no go. Verizon FiOS uses a modem/router combo and you have to use it. Prior to last week I had a Comcast using a Motorola Surfboard Cable Modem and a D-Link Wireless router with no issue.
I have no doubts this is a router issue I just don't know what it could be as all 3 of my wireless computers are able to access the internet without any issues. The only devices that are having problems are the wife and my G1's.
I will try to do a factory reset today but am afraid this may affect the FiOS home media server and other Set Top Box I have.
I was just hoping someone had a solution to this as someone else mentioned the issue on this thread: http://forum.xda-developers.com/archive/index.php/t-444245.html

Best bet is to take it up with verizon, I'm sure there are other people that have the problem.
It's good to know they force you into using their hardware, I wouldn't want to go without a proper router, so it could be a deal breaker for some.

evilkorn said:
Best bet is to take it up with verizon, I'm sure there are other people that have the problem.
It's good to know they force you into using their hardware, I wouldn't want to go without a proper router, so it could be a deal breaker for some.
Click to expand...
Click to collapse
yeah, basically what I had done was turned off the wi-fi on the verizon router and hooked my D-link wireless N router up so the Verizon was basically just acting as a modem. I took my d-link out of the equation to troubleshoot and determined that it is definitely something with the Verizon router, I just don't know what. The interface on the Verizon router is crap too.
I'm going to reset the router today and see if that resolves the problem. Other than this issue I have been totally happy with their service. The FiOS Cable is nice and the broadband is way faster than what I was getting with Comcast.

This is solved. It turned out to be a port forwarding issue.

3G mobile hotspot

alright i know i got this somewhere on another forum and found it to be a great way to wifi tether out of the box with out root
on the phone do ##778 goto edit mode enter 000000 then into the security settings change the S.IP DUN User name to [email protected] and back out of there to the M.IP Default Profile and change your DUN NAI to [email protected] hit menu and hit Commit Modifications.
I have tested and verified this works 100% with no problems.
Granted to have the 3g mobile hot spot option you need to have loaded the leaked OTA but i see this would also work when 2.2 is released!
Also sorry if this is in the wrong area and please feel free to move it where it belongs.

I am just using the wifi tether app from the market place.. I am scared if I am using the VZW app I will get hit with charges.

make no mistake im using the wifi tether app too but this is an alternative as this also gives you a widget option for turning on and off.

Sweet has anyone confirmed no charges or crazy letters from VZW??

One thing I did notice is that this method uses infrastructure as opposed to the ad-hoc mode of wireless tether.

well thats some good news then

the method which you described is on xda some place, the thread was started right near the time the phone came out in late april. it also doesnt not require root, but it is a usb tether not wifi tether. i dont believe you can do wifi tether without root

I believe this will work without root. You just need to apply the leaked OTA and make the appropriate changes in the first post. I'm not able to verify that since I'm rooted.

i cant get my laptop to get the ip address. i was able to connect to the mobile hot spot but cannot get the ip address. i tried, wep, wpa and no key. Any ideas???
thanks

dkhait said:
i cant get my laptop to get the ip address. i was able to connect to the mobile hot spot but cannot get the ip address. i tried, wep, wpa and no key. Any ideas???
thanks
Click to expand...
Click to collapse
have you tried repairing on your computer and also verifiying your TCP/IP settings on your laptop that its set to accept DHCP and not be static

thatdudebutch said:
I am just using the wifi tether app from the market place.. I am scared if I am using the VZW app I will get hit with charges.
Click to expand...
Click to collapse
[email protected] is the username that your phone uses to connect to the internet, and [email protected] is what Mobile Broadband Connect and the 3G Mobile Hot Spot uses to connect.
Unless you're using obscene amounts of data you shouldn't be caught. This is doing exactly the same thing that the Wifi Tethering app and PDANet does, though I can certainly understand why you'd be scared.

outsid0r said:
have you tried repairing on your computer and also verifiying your TCP/IP settings on your laptop that its set to accept DHCP and not be static
Click to expand...
Click to collapse
it works fine with wireless tether. same laptop same settings

Does anyone know if this works (with the appropriate @xxx.com) for sprint phones like the hero or the evo 4g? Couldn't find anything in their forums.
Thanks and sorry for the wrong phone section post.

BlueWyvern said:
Does anyone know if this works (with the appropriate @xxx.com) for sprint phones like the hero or the evo 4g? Couldn't find anything in their forums.
Thanks and sorry for the wrong phone section post.
Click to expand...
Click to collapse
I would imagine if u looked at their settings that it should work, but thats a SHOULD only way to know is to give it a shot and if it doesnt then you need to remember what the settings were prior.

Guys, be careful with this - I used to do this with my VX8300 back in the day and although it worked great, I eventually did get a letter from VZW saying to stop or they would terminate my contract, and I didnt even use it that much.
Just a heads up...

mattwood2000 said:
Guys, be careful with this - I used to do this with my VX8300 back in the day and although it worked great, I eventually did get a letter from VZW saying to stop or they would terminate my contract, and I didnt even use it that much.
Just a heads up...
Click to expand...
Click to collapse
O'RLY?
I've used this for long time from the Vogue to Imagio and now DINC, nothing happened...
Did you tether to P2P? Downloading bunch of stuff? If so, you're sticking out like a sore thumb...

Yeah wonder how they would find out. It's the same exact internet connection that your phone uses. You're just "sharing" it with other devices. How would Verizon be able to tell if you're using that same internet but on a different device? Assuming of course that you aren't using it for online gaming or torrents or other bandwidth intensive applications.

The VX8300 didn't have much of a browser. I imagine if you ever did much of anything on there and didn't have a tethering plan then it would look suspicious.

Wifi Problems

Well I've had my Captivate for 3 months, and up until now it's been smooth sailing. Two days ago I came home and my power was off, and when it came back on I tried connecting to my router like usual, but now it won't connect. On the "wifi settings" menu it just says "obtaining ip address from..." for a few seconds then it says "disconnected" and goes back into "scanning..." mode. Also, under the "wifi networks" section it shows my network as "Disabled, secured with WPA/WPA2 PSK". (I am using a Linksys WRT54G with WPA2 security f.y.i.)
I've tried "forgetting" the network, I've deleted the whole file that remembers your networks, I've tried connecting via WPS button, I've double checked my password, I've power cycled my router, I've reset my router back to default and re-configured it...still nothing. It connects to the wifi on campus with no problems (in 4 different buildings), so obviously there is something wrong with my router setup.
If anyone has any advice on how to resolve this problem, it would be much appreciated!
**Also, I forgot to mention I am running Cognition v2.2 Beta 6

Bump for hope

Does anything else connect to your router
Sent from my SAMSUNG-SGH-I897 using XDA App

M3MPH1S said:
Well I've had my Captivate for 3 months, and up until now it's been smooth sailing. Two days ago I came home and my power was off, and when it came back on I tried connecting to my router like usual, but now it won't connect. On the "wifi settings" menu it just says "obtaining ip address from..." for a few seconds then it says "disconnected" and goes back into "scanning..." mode. Also, under the "wifi networks" section it shows my network as "Disabled, secured with WPA/WPA2 PSK". (I am using a Linksys WRT54G with WPA2 security f.y.i.)
I've tried "forgetting" the network, I've deleted the whole file that remembers your networks, I've tried connecting via WPS button, I've double checked my password, I've power cycled my router, I've reset my router back to default and re-configured it...still nothing. It connects to the wifi on campus with no problems (in 4 different buildings), so obviously there is something wrong with my router setup.
If anyone has any advice on how to resolve this problem, it would be much appreciated!
**Also, I forgot to mention I am running Cognition v2.2 Beta 6
Click to expand...
Click to collapse
Happened to me a few times. Only way I could get out of this was to restore to a previous backup, or install fresh again. By the way, I experienced this problem only on 2.2. Never happened on 2.1.

fatttire said:
Does anything else connect to your router
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Unfortunately I don't have anything else with wireless to test.

Elaborating on the issue
I've encounter exactly the same problem described here.
Samsung Galaxy S I9000. Froyo (official version). Not rooted.
Now it is the first time it has happened, and still I have not found a solution (restarted the router, restarted the phone and made more tests).
Before the upgrade to Froyo it has never happened. After the upgrade it worked ok for several days untill now.
Several other deviced at home are well connected to the router.

Its just s stupid suggestion maybe... but have you tried to change channels with your router?
Sometimes is just a stupid channel issue....

I found out the answer to this problem. I had to connect using static addressing. It seems at some point, the captivate 2.2 roms get confused for some of us and it starts trying to assign an IP address already used.
In my case, I tried everything... rebooting phone, router, ect.
Laptop connects fine, Wii connects fine...
But, I decided to connect via static addressing... BAM connected perfectly and instantly.
Connecting to other DHCP networks seems to be hit and miss as well.
So, I'd suggest reflashing might be the overall fix. But if you're like me and cannot reflash right away, try static addressing till you can get around to it.

yukinok25 said:
Its just s stupid suggestion maybe... but have you tried to change channels with your router?
Sometimes is just a stupid channel issue....
Click to expand...
Click to collapse
Not stupid at all, but unfortunately yes, I tried a couple different channels and still nothing.

DigitalEagle said:
I found out the answer to this problem. I had to connect using static addressing. It seems at some point, the captivate 2.2 roms get confused for some of us and it starts trying to assign an IP address already used.
In my case, I tried everything... rebooting phone, router, ect.
Laptop connects fine, Wii connects fine...
But, I decided to connect via static addressing... BAM connected perfectly and instantly.
Connecting to other DHCP networks seems to be hit and miss as well.
So, I'd suggest reflashing might be the overall fix. But if you're like me and cannot reflash right away, try static addressing till you can get around to it.
Click to expand...
Click to collapse
Awesome! This sounds like a promising solution, thanks. Yeah I need to reflash soon anyway seeing as how Cognition is up to 2.4.x already...
Probably won't be tonight, but I will do this soon and let you know my results.

Alright, I have typed just about every keyword into google relating to setting up my router/phone to use a static IP and for some amazing reason there are ZERO results that have any information whatsoever about setting up a static ip on a phone. This is really frustrating, so if anyone would be kind enough to explain how to do this or link me somewhere that does, that would be awesome

go to your wi-fi settings and click the menu button.
it should pop with a "scan" and "advance"
click on advance and scroll down to "use static ip address"
then i guess you have to put in your network details, not sure on the details there cause i have done it but experiencing same problem with my galaxy s
power went out and now can't connect to my network
Edit : Possible fix
I just managed to connect to my network.
I put the device in flight mode and restarted my modem at the same time
put it out flight mode and pluged in the modem again and now works.
Hopefully that works for you to guys.

Yea, works perfectly. I have my laptop connected to it right now. I usually have to reset the phone to get wifi again.
edit: I set it to static ip, but then i got the same problem. Except now google search engine works No webpage opens, youtube app didnt work either.. only the search engine worked.

Well my phone must be in a good mood today because it just decided to start working again all on its own! I don't know what caused it...I have actually had both my phone and computer constantly on since this started happening. So for now I'm keeping my fingers crossed and hoping it doesn't mess up again.

This is probably just for me, but this isn't a viable solution.
The ONLY router I seem to have this issue with is the one that Verizon gives all it's FiOs customers. It's the Actiontec M1424WR Router/Modem. I know my WEP key is correct because it works just fine on all the laptops and other phones (a Palm Pre and another Captivate on 2.1). It tries to obtain an IP address for about 5 minutes and then just sits and says disabled. Does anyone know if there's a way to dump the DNS cache or whatever like you can on Windows?

Add me to the list of ones having this problem...guess I'll try to reflash everything in a bit to see if that fixes the problem.

Just an update I backed up everything using Tibu and then just restored it and my WiFi problem went away.

Mine is stock and just started having this problem....will connect to other wireless routers except mine, really pissing me off!
I've tried many times having the the phone "forget" me, then put in my password(which is correct)...same thing over and over.

Same problem here
I have a galaxy s and the recent update to froyo brought me the same problem already described here.
And the "funny" thing is that my router doesn't have an Static IP option, it's a simpler router from the cable provider.
So i'm trying also to find a solution to this. Two days ago i changed the wifi channel and it worked. But today i have again the same problem and changing the channel don't work anymore.
Each time i find a possible solution, it only works one time.
This is really annoying me. This must be a froyo bug, 2.1 never gave me this problem

pedroc2009 said:
I have a galaxy s and the recent update to froyo brought me the same problem already described here.
And the "funny" thing is that my router doesn't have an Static IP option, it's a simpler router from the cable provider.
So i'm trying also to find a solution to this. Two days ago i changed the wifi channel and it worked. But today i have again the same problem and changing the channel don't work anymore.
Each time i find a possible solution, it only works one time.
This is really annoying me. This must be a froyo bug, 2.1 never gave me this problem
Click to expand...
Click to collapse
It must be a froyo beta bug. Remember we don't have a final version of this firmware for the Galaxy S family.
Sent from my Captivate

No connection over WiFi

Hello,
I got the 2.2.1 SuperBled Rom installed on my G1.
Since a few days i cannot use the connection over WiFi.
after turning it on it finds all the access points around and also builds up a connection to my router. i get an ip from my router and everything seems fine.
but i cant use that connection, nothing is working, no market, nothing through the browser, no mails etc. the connection is displayed as connected all the time.
i have not changed any settings on the phone nor on the router.
it worked fine before. it also doesnt work with any other access points like at my uni or friends place.
i can still use the internet through mobile networks.
any suggestions what the problem might be ?
thanks in advance
cheers

I am having the exact same issue but a Rooted Nexus S with CyberGR v10.