Related
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.
hey all..just bought my diamond..have the same issue with wifi connection at home..it just wont work..its connected..says its connection..have all the ip settings etc but just wont connect to internet..
saw the thread before about this but see there was no outcome..thread just stopped do'h
so can anyone help me ? ive never had problem like this with all my other wm phones lol
i dont have any problem connect using WIFI @ home.. did u set the network correction? (if use wireless , each set got it own network point & password) did u set correctly
I'm experiencing some problem like this also.
With my Hermes, I was able to get a working WiFi connection @ home. With my Diamond I simply can not. My Diamond can see the WiFi network and than wants to log in to the network, but it gets rejected for what reason. I tried every possibility in my router (WPA1, WPA2, even unsecured, Turbo off etc --> not random, I know enough bout networking to know what I'm doing). It's really strange, by a friend of my I can connect to his WiFi network. Let's me conclude that it is my router.....
hmm not sure about router being problem
Caspertje19 said:
I'm experiencing some problem like this also.
With my Hermes, I was able to get a working WiFi connection @ home. With my Diamond I simply can not. My Diamond can see the WiFi network and than wants to log in to the network, but it gets rejected for what reason. I tried every possibility in my router (WPA1, WPA2, even unsecured, Turbo off etc --> not random, I know enough bout networking to know what I'm doing). It's really strange, by a friend of my I can connect to his WiFi network. Let's me conclude that it is my router.....
Click to expand...
Click to collapse
hey..i understand what you saying..ive been owning wifi phones since they first came out all different models and makes..never a problem with them except this darn diamond..since i also know little about pc's my first laptop was actually black and white..windows didnt exist..250 hard drive and 8 mb ram..surely like you and zillion other people can handle connecting a phone to wifi..guess the problem is with the phone..i must admit my router is old now..maybe the have changed something in the connection that its know becoming out of date
Caspertje19 said:
I'm experiencing some problem like this also.
With my Hermes, I was able to get a working WiFi connection @ home. With my Diamond I simply can not. My Diamond can see the WiFi network and than wants to log in to the network, but it gets rejected for what reason. I tried every possibility in my router (WPA1, WPA2, even unsecured, Turbo off etc --> not random, I know enough bout networking to know what I'm doing). It's really strange, by a friend of my I can connect to his WiFi network. Let's me conclude that it is my router.....
Click to expand...
Click to collapse
UPDATE:
after flashing Elite 1.0 the problem is solved. I can now login to my router by WiFi....Don't know what the problem was with the orginal rom 1.35.404.4 NLD
i have a linksys WRT54GX4. When I try to connect to it using the xperia, it tries to connect for a few seconds and then the status shows unavailalbe then a couple seconds later the status of the router goes back to available but i can never connect to it. The router is running a DHCP server and the wireless security is WEP 128bit and the authentication is open. I don't know why it doesn't want to connect. I really need to sort this out. Anyone else experience this problem? The phone connects to other routers in my neighborhood though, so it might be the router, but i have other devices connected to the router and they are just fine.
Haven't used that router before but maybe you could try updating the routers firmware to the lastest available.
These should be available from the manufacturers website.
already tried its the latest.th erouter isn't giving me any problems on my othe computers/ laptops. Is it possible that the x1 just isn't compatible with it?
Do you have any other security, i.e. MAC filtering, turned on?
no i never mess with the more advanced settings. BTW I even tried disabling all encryption basically unprotected, and it still gave the same problems! Thanks for the quick replies also.
Hmmmm......
Ok, I know its a pain but try changing your security from WEP to WPA.
Everyone with wireless should really use WPA or above, WEP is quite crackable with various free tools floating around the net.
yea but shouldn't it have connected with NO encryption whatsoever?
Hpoefully a hard reset will fix your problem?
I had the same problem but i thougt it was becuse ny router but i tried to connect to other networks aswell an got the same problem, well later on my phone stopped accepting files thrue the usb cable. and didt want to install some cab files that i had istalled before and knew was working.
I had enough and decided to hard reset it and it really fixed all my problems.
so hopyfully it will for you too..
Good luck.
yea i'm gonna try now, hopefull that will work, did u hard reset thorugh the iption in settings, or did you do it physiclaly through buttons>?
Havent had that problems ... what i do is allow only my devices mac address to connect ...
my psp as well as gf psp
2 desktop + laptop
htc touch cruise
xperia
and home media player
Everything else gets denied, cant really beat mac address filtering.
ok just tried a hard reset and still didn't work. The signal strength is full but the phone never even gives me that automatic message that there is a network available, but it does this for other routers in my neighborhood.
BuddyLee said:
Havent had that problems ... what i do is allow only my devices mac address to connect ...
my psp as well as gf psp
2 desktop + laptop
htc touch cruise
xperia
and home media player
Everything else gets denied, cant really beat mac address filtering.
Click to expand...
Click to collapse
Actually, you can, but that's for another forum
OK PROBLEM SOLVED. Did a factory reset on my router, then the phone connected. But when I went to change the channel from auto to 10, the wifi stopped connecting. After that, any susequent changes to the channel; whether I tried a different channel or set it back to auto, did not work and the only way to get it back was factory reset the router. So basically I have resseted my router, and have not touched the channel settings and it is working fine. BTW the dedicated Xperia tech support line is AWESOME, even though they weren't the ones who figured out why i had the problem (and they wouldn't have because it was the routers problem) they knew what they were talking about and are actually from the US!
n4v1n, did WiFi work for you in other networks (with other routers)?
I have the same problem with my phone: only reset of my house router allows the phone to reconnect.
I am not so convinced that it's a problem of the router, because two of Samsung phones (Omnia HD on Symbian and Wave on Bada) connect always without any problem.
does your router have a physical easy connect button? try to use that before connecting even you already have the proper setup on both devices. sometimes somehow that happend to laptop, phone, wifi card. and with a single push solved most of the quirks.
if i remembered correctly, older wifi support only up to 7-1 devices. and my phone seems never connect to anything higher than channel 6.
Well, I just moved to a new house and reinstalled my wifi router. And since then my N1 does not see my home network, while it detects all the neighborhood ones!! In fact it did detect it once and then stopped. I tried to install it manually, it didn't work either. I also tried to install wifi manager from the market after doing lots of research on the subject, and it worked once and then disappeared again...And that is very frustrating.
Note: all other pda and pc at home detect the network.
elio said:
Well, I just moved to a new house and reinstalled my wifi router. And since then my N1 does not see my home network, while it detects all the neighborhood ones!! In fact it did detect it once and then stopped. I tried to install it manually, it didn't work either. I also tried to install wifi manager from the market after doing lots of research on the subject, and it worked once and then disappeared again...And that is very frustrating.
Note: all other pda and pc at home detect the network.
Click to expand...
Click to collapse
Your router is named? On channel 1-11? Is of a supported encryption type?
Yes named, no space in the name. WEP encrypted.
Strange thing is that it saw it once or twice and then never again... And it still detects fine other networks :S
elio said:
Yes named, no space in the name. WEP encrypted.
Strange thing is that it saw it once or twice and then never again... And it still detects fine other networks :S
Click to expand...
Click to collapse
For S&G try turning off WEP temporarily.
Not like WEP is any kind of security anyway.
Will try...
Solved
After weeks of researching: Nexus can only connect to routers set on channels 1 to 10. So anything above 10 won't be detected.
elio said:
After weeks of researching: Nexus can only connect to routers set on channels 1 to 10. So anything above 10 won't be detected.
Click to expand...
Click to collapse
Not true, my Wifi is always on channel 11 and always connects...make sure you aren't on N wifi at 5Ghz ONLY because the N1 only works for 2.4Ghz
gravufo said:
Not true, my Wifi is always on channel 11 and always connects...make sure you aren't on N wifi at 5Ghz ONLY because the N1 only works for 2.4Ghz
Click to expand...
Click to collapse
Then it must be 1 to 11
Just for "academic" purposes, can you set your router on a channel > 12 and tell us if it works?
Thanks
Just tried mine, channels 12 & 13 are fine, 14 is not.
Sometime ago faced same problem. After moving to custom rom my nexus have lost my AP
Try to set-up available channels on nexus by moving to "wifi/advanced/domain-blablabla"
My one works on #13
Dont forget yo do same thing with yours ap/router
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