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.
I've been running 6.1 ROM (Official) now for a month or so and am using a program on my Tilt that uses a lot of data...so while I'm at home I thought I would allow it to use my WiFi router instead of my 3G connection.
I turned on the WiFi and it can "see" my router's SSID. I enter the WPA-TKIP passcode and tell it to connect. It just sits there saying "connecting to network" but never completes the connection to acquire it's IP.
I have even gone as far as setting the IP configuration manually (Static IP) and the TILT keeps trying to connect to the network.
I have a DLink DI-624 that I have had no problems connecting the WiFi when I was running ROM 6.0.
I have done the following in trying to troubleshoot:
- Turned OFF Turbo on the Router
- Configured router for AutoChannel
- Configured TILT for Best Performance
- Rebooted Router AND TILT.
Still no go...Ideas?
I sometimes get this after flashing a new rom. It seems to affect the way it connects to WPA networks but not WEP or unsecured.
You can try changing your security to WEP and see if that works.
But when I need to solve this I usually have to do a Hard Reset and then connect the WIFI first. When it does this the phone seems to be able to auto-detect the network type (i.e without me needing to select it as WPA) and after entering the passcode it can connect.
Yep, go to WEP, this should be enough for most people and has never given me a problem.
martythebrit said:
Yep, go to WEP, this should be enough for most people and has never given me a problem.
Click to expand...
Click to collapse
Unfortunately I can't change my network to WEP. My network is not only my home network but also used for my wife's business...so for security reasons I have to keep the security up.
Drop the security just for a test and see what happens.
I am using the official ATT 6.1 ROM and it works just fine on my wifi, first with WPA-PSK then with WPA2-PSK. You could set your WAP to WEP (say that fast 3 times!) for a 5 minute test and see if it connects. Does your phone connect to other Wifi hot spots? What does ministumbler say about wifi in your area? You may have some interference with a neighbors wifi.
Well...I know that my issue is not limited to my router at home (DLink DI-624). I'm experiencing the SAME issues at work as well.
At work I'm using a NetGear WGT624 v3.
- The security is WPA-PSK (TKIP)...just like at home.
- Broadcasting SSID on Channel 11 (Fixed). There are no routers in nearby offices (I've checked using a wifi scanner on my laptop).
- I've configured a static IP in my Tilt and it just sits there at Connecting...again same as what happens at my house.
- I have also tried using DHCP with no joy.
I'll try the WEP at home to see if it's a WEP/WPA issue.
Unfortunately if it IS an issue...I don't think I'm going to get much joy from HTC on releasing a fix. Maybe there will be some way around it though...I hope!
Make sure you use the correct authentication: Use Smart Card or Certificate. That fixed mine
brynwall said:
Make sure you use the correct authentication: Use Smart Card or Certificate. That fixed mine
Click to expand...
Click to collapse
Here is what I have set in my TILT...
Connects to: The Internet
Hidden network: NOT checked
Ad-Hoc: Unselectable (Grey)
Auth: WPA-PSK
Encry: TKIP
Use IEEE: Grey (Non-Selectable)
EAP: Grey (Non-Selectable...but Smartcard or Certificate IS in the box)
(Still at work...will test WEP when I get home)
(I'm home)
Ok...Now I know for SURE that this is a WPA issue with the TILT running the AT&T ROM 6.1 (Official).
I changed my home router from WPA-PSK (TKIP) to WEP.
Made the needed changes in my TILT to change it from WPA to WEP and entered the correct key.
* IT CONNECTED TO THE ROUTER! Whoo Hoo.
I change nothing in the router except from WEP back to WPA and again I'm stuck at "connecting" on the TILT.
Ideas?
At least you know
And Knowing Is Half The Battle
clstan said:
(I'm home)
Ok...Now I know for SURE that this is a WPA issue with the TILT running the AT&T ROM 6.1 (Official).
I changed my home router from WPA-PSK (TKIP) to WEP.
Made the needed changes in my TILT to change it from WPA to WEP and entered the correct key.
* IT CONNECTED TO THE ROUTER! Whoo Hoo.
I change nothing in the router except from WEP back to WPA and again I'm stuck at "connecting" on the TILT.
Ideas?
Click to expand...
Click to collapse
Is a backing up everything and doing a hard reset too much hassle? Make sure you connect to a WPA Wifi first before installing any other programs. Its the only way I could fix it... =/ As recommended I always do another hard reset straight after flashing a new rom now.
Hey...someone...somewhere has mentioned that there might be a WPA issue in relation to removing the AT&T Bloat. Is there anything to this? I HAVE removed my bloat on my Tilt.
I don't want to have to re-Hard my Tilt...but will if I have to...but only as last resort.
What fixed with my DI-624
I found that I had to upgrade to the newest ROM from D-Link. (I had original ROM from 5 years ago.) I found that the PSK password (using WPA2) could NOT contains shift-numbers such as $, %, #. I converted the symbols to numbers (and letters)and it works fine now. I have had no problems since.
segaza said:
I found that I had to upgrade to the newest ROM from D-Link. (I had original ROM from 5 years ago.) I found that the PSK password (using WPA2) could NOT contains shift-numbers such as $, %, #. I converted the symbols to numbers (and letters)and it works fine now. I have had no problems since.
Click to expand...
Click to collapse
My home router is a DI-624 Rev E. The ONLY Firmware for the E Rev is 5.00 and I'm running it.
Even though not completely secure...my WPA password is a 20 character, lower case entry...no strange characters or whatever.
*Well folks...I had just installed the 6.1 Rom onto my Tilt about a month ago...so I don't have that much installed...and I can always reload it. So I HardReset and followed by removing bloat. WPA WORKS NOW! (Insert "Twilight Zone" theme music here.)
All in all...it just seems strange to have to HARD Reset my phone to get something like this to work again.
So I just got my Captivate a few days ago and I love this thing. I rooted it briefly with OneClickRoot and removed some AT&T bloatware and the unrooted so that I wouldn't have any issues with the upcoming Froyo update.
I don't know if it's related, but now my phone refuses to connect to my home Wifi. It repeatedly says 'obtaining IP address' but then says 'connection unsuccessful' over and over again. It was connecting fine last night after I rooted/unrooted.
I have 'forgotten' the network and tried to reconnect without success. I have cycled the router and gotten it to connect very briefly but sure enough I'm not connected anymore. I'm currently on the wireless on my laptop and it's infuriating.
I've already been growing steadily unhappier with the GPS situation and now this is really putting a damper on my excitement over this phone.
Does anybody know what to do about this wireless?
And if all else fails, how do I get my phone to a point where I can return it for a new one that actually works?
Thanks for all your help.
Christine
Yes the phone can be returned to the stock state by using odin . Its very easy. You should first try to use a staic ip. Sometimes the problem is that the captivate chooses to use the same ip as some other electronic that's using that router.
Just go to wireless networks -> wifi -> (menu key) advanced and then plug in the static ip
I am somewhat familiar with static IP's but have never set one up before, certainly not on a phone. Do I need to specify a DNS, too, or just go in and specify a different one from my laptop?
I had that problem before. I just used Odin and flashed the stock firmware (jf6) back on again and it was fine.
Going back to jf6 makes me think there is something wrong with the wireless drivers. Anyone have more information?
Sine I started to flash new firmware I have seen my wifi refuse to connect until the 4th attempt.
clarient said:
I am somewhat familiar with static IP's but have never set one up before, certainly not on a phone. Do I need to specify a DNS, too, or just go in and specify a different one from my laptop?
Click to expand...
Click to collapse
On the laptop click start and click run. Type cmd then press enter. Type ipconfig and copy those numbers to your phone but make IP ADDRESS a different number.
Its probably your router
I had the same problem with my captivate. Everything else in the house would connect to the router but my phone wouldn't (even though we have 3 captivates in the house). Then the router started acting up badly so I replaced it with a nice cisco router and BEHOLD!!!! My captivate connects quickly now. no problems.
Cisco Linksys E1000 is the model router i got. Highly recommended.
Good point, power cycle the router and see if the phone can connect after that.
I had this problem with my Linksys router. I had to log into the admin settings and I increased the number of connections available and it connected immediately.
The app, FXR fixed my gf's phone with this problem.
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
I have had my Tab for 2 weeks now.
At home I had no problem to connect to my WiFi network for 1 week: then suddenly the Tab would not connect and would remain stuck on “getting IP address…”.
I changed from WPA to WEP to WPA2 PSK with no luck
But if I go to a static IP, then I have no problem to connect.
On my office “public” WiFi network, exactly the same problem: it worked for a week and then bingo stuck on “getting IP address…”. Again going to static IP solved the connection problem.
My question is: how do you delete a network from the list? It seems to me that the Tab keeps an IP address in memory and if ever that address is taken by another device, it gets stuck!
Any advice would be appreciated.
I had this exact same issue on the same day I bought my Sprint Galaxy Tab (11/14). I did a hard reset that afternoon, and I haven't experienced the issue since. I'd already had all of my apps downloaded, and settings tweaked, so hard resetting was kind of annoying. I hope this doesn't come up again.
Yep sounds familiar, my Thomson Speedtouch 780i runs on a old firmware which gives me same issue with the Tab, had to run with no security. If you decide to run with no security turn off broadcasting..or update firmware/router..
My router is quite recent and has the latest firmware.
All my toys (iPad, Dell Streak, HD2 together with 3 PCs) connect without any problem.
The Tab had no problem either for a week.
Then for unknown reason no way to connect unless using a static IP.
And as I have not found a way to delete the network in memory (short of doing a hard reset)I am stuck.
And now same problem arises with office netxork:-(
Yeah just do a factory reset in privacy settings i think
susu42 said:
My router is quite recent and has the latest firmware.
All my toys (iPad, Dell Streak, HD2 together with 3 PCs) connect without any problem.
The Tab had no problem either for a week.
Then for unknown reason no way to connect unless using a static IP.
And as I have not found a way to delete the network in memory (short of doing a hard reset)I am stuck.
And now same problem arises with office netxork:-(
Click to expand...
Click to collapse
My Tab is doing the same thing now. I can't do a hard reset....is there another solution?
Ugh, I have the same issue! Had it for 2 days and all of the sudden it's stuck on Getting IP address from... Resetting to factory defaults was depressing. I wish there was another way!
It also happened to me when I was on vacation at my relatives home. The tab would work for a day or two and then be stuck at that message. I had no issues with doing a factory reset as it was still new. But then I started using the static IP trick and that worked. Now I'm back at home and I don't have this issue at all. Been using it for a week with my wifi and all is well.
Nothing was actually working: restarting the router, forgetting the network, creating the network manually, changing the authentication method, etc.
I'm sure its was an issue with the router at my relatives home, but still why was my Nexus one and Laptop connecting with no problem???
For those who are having the problem, use a static IP for the time being, you don't have to reset.
-Gus
I ended up switching to Channel 1 on the router at home, and haven't had any problems since. Chose Channel 1 after running WiFi Analyzer.
having this same problem. I've messed with WEP vis WPA and tried static IP. Using a verizon fios router. any help?
Bah, it happened again! Now I really dont want to reset
Same issue here ...
I can get WIFI at Starbucks but not at home ( Open-WRT on linksys )
I wonder if it depends on SIM card being inserted?
Mine is a Verizon FioS router as well, at work. Can get on fine at home or anywhere else. My iPad had a problem here forgetting the network but I could at least reconnect. This is doing exactly like you guys.
I wouldn't even care that much except when I'm inside the office I can only pull in Edge data. Ugh.
I had to change wireless settings on my Linksys - most changes were to disable some fanny things like "afterburner" - and setup wap2 for security to have a stable wifi.
I've had the same problem with my TMobile Galaxy Tab. All I do is to turn off Wifi in the Settings app, then turn it on again. I am usually able to snarf an IP address straight away after that.
It also helps to just turn the device on and then off again. it boots so fast that it isn't too annoying.
I had similar problem at home. My DHCP server had wrong time set. After setting the time on DHCP server correctly everything is back to normal.
i hav a tab on tmobile love it not sure if i had the same issuse as u guys tho the issuse i had was it would work without any problems im talkin about wifi then the next day the wifi doesnt want to lock onto the wifi it would search then drop to start serchin again , now wat i learned is sum apps require wifi to work because high data at the same time it changes sumthing in ur wifi settings after using the app the first time which would require u to master reset the device to resolve the issue the program that was doin it for me was frostwire
same here
my version of the same problem appeared when i changed the static IP of my home router (AVM Fritz!Box 7170). before that i always got a dynamic IP through DHCP on my galaxy tab.
After changing the router IP i only could connect with a static IP.
if i use a different WIFI network instead, DHCP is working as expected.
in my opinion the problem is with the firmware storing the network settings and with no possibility of deleting it completely. a hard reset cannot be the solution...
does anybody of you know if this problem occurs on other froyo-based devices also? is there a way of deleting network settings in a working way?
Had the same problem, EU TAB white Stock 2.2 rooted spot connecting to my main Wifi but connects to 3 or 4 other dhcp APs.
Have a htc Desire whit stock 2.2 + rooted and never had that problem.
In the end i hardreset Tab and no problems 1week and counting.
EDIT
FUuuuuuuuuuuuuuuuuuuuuuuuuuuuuuu
Happen again... im not going to hardreset again, im looking for a more permanent solution
Had the same problem. I have the Verizon FIOS router. The solution is actually easy. Just drain the battery of the Tab. Charge it to full and turn the Tab on. I think the Tab really "forgets" the old network after this kind of restart. No need to reset your Tab to the factory settings.