Related
Alright, I'm kinda having a pretty annoying issue now.
My Wildfire is flashed with OpenFire.
Since I don't have a wireless router I use connectify.
I setup my connectify network, and I try to connect to it, but my Wildfire just shows ''Obtaining IP-Address'', then it disappears, and then it says ''Obtaining IP-Address'', and this is kinda an endless loop.
Anyone have any advice on how to fix this?
I have kind of same situation where it only says Obtaining adress and nothing happens. It used to happen to me only on one specific router and when that router was reseted it was all OK. But now it happens again but resetting doesn't help. Any help?
I just plugged out the power source of my router for an entire day, and now I can connect to it and everything is working fine.
If resets of anything aren't working for you i'd suggest flashing the stock modem. This has been the case for a couple users. I'm currently stuck in the same place as you and I reflashed my own stock modem (sgs2) if anyone has any tips for me I would be VERY grateful!
My WiFi was working fine on my Xoom, and now it gets stuck while "obtaining IP address." It says for a split second "remembered" as if it was connected and starts the ongoing circular process of "obtaining IP address" all over again. I saw that galaxy tab users had this same problem and found a resolution by connecting "static" instead of "DHCP." I didn't try that as I honestly don't know how. What I do know is that there are a few devices like my OG droid, my laptop, my mothers' laptop, my xbox 360 that are connected to the same WiFi network. This randomly happened, when I decided to disconnect from WiFi to run a speed test on 3G and I was unable to connect to WiFi ever since. I tried unplugging/plugging the routers, turning the Xoom off and on, and even went so far as to doing a factory reset on the Xoom and I still can't connect. 3G works fine, but I have a 1GB cap and I would rather only use that while I'm on the go, and obviously WiFi is definitely faster. If I can't resolve this, I still have enough time to return this thing. Call me a newb, but I need a little help!
I know you said you did a factory reset, but google stores wifi passwords in the cloud now. Try making the xoom forget the network you're trying to connect to.
My only other thought is that you need to go into your router's configuration and remove the xoom as a remembered device.
Bauxite said:
I know you said you did a factory reset, but google stores wifi passwords in the cloud now. Try making the xoom forget the network you're trying to connect to.
My only other thought is that you need to go into your router's configuration and remove the xoom as a remembered device.
Click to expand...
Click to collapse
How do I get the xoom to forget the network? How do I remove the xoom as a remembered device? Sorry but I really don't know how to do that..
EDIT: I went into settings>privacy>backup and restore> and unchecked "back up application data, Wi-Fi passwords, and other settings to googles servers and was still unable to connect.
I think if you long press on the wifi network it will give you the option to forget it.
As for the router, do you remember setting it up? The settings pages where you set the wifi name and password and such.. it should have a section where it tells you which devices are connected.
I have pressed "forget network" on the xoom several times when trying to connect. As for the router, do I remember setting it up? No, as a matter of fact I didn't set it up. Could I configure this thing from my laptop?
droiduser1988 said:
I have pressed "forget network" on the xoom several times when trying to connect. As for the router, do I remember setting it up? No, as a matter of fact I didn't set it up. Could I configure this thing from my laptop?
Click to expand...
Click to collapse
Of course, anything that's connected to the router should let you configure it. It's too complex to explain here, but you need to enter the router through it's IP address and find the configuration.
Find the manual for the router you have and go from there.
I'll try to look into that, any idea as to wtf happened? This is beyond an inconvenience..
I'm having much the same problem. After entering the passphrase it says 'obtaining ip address from....' and thats all. It never connects??? I have tried 'forget' several times and no luck.
I have been able to connect to unsecured wifi with no problems.
Use the free app "wifi static". Config to assign you a static IP on that network only and dhcp on others. Its something within android as I have the same issue in my phone with a few networks but not most.
Sent from my Xoom using XDA App
jcampbell037 said:
Use the free app "wifi static". Config to assign you a static IP on that network only and dhcp on others. Its something within android as I have the same issue in my phone with a few networks but not most.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
OK, tried it. NO GO! After entering the passphrase it STILL says 'obtaining ip address from....' I may be doing something wrong with the app since it comes with absolutely NO directions. If this is going to be an issue average folks will take it back!
Have any of you with this issue verified that the DHCP scope on the wireless network is not full or that DHCP is even allowed? The fact it works one place but not another tells me the issue may be with the network and not the device.
Dave
Sent from my Xoom using XDA App
I was having the same issues as you originally at first until I reset my router and my Xoom.
Sent from my Xoom using XDA App
je2345 said:
I was having the same issues as you originally at first until I reset my router and my Xoom.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
I also had this issue, I ended up fixing it by upgrading my router BIOS. the version that was on there was dated 2004 (yikes), and though the most current update was only 2006, it seems to have fixed the problem.
That or the reboot after the update as previous poster said and the update didn't really have anything to do with it, but either way it got fixed.
I am trying to connect to home wifi which I have done in the past but it is not connecting. I am getting:
"Obtaining IP Address..." "Disconnected" and that just loops
I am on my laptop connected to the same wifi network, I got on my wife's Vibrant and connected to the wifi, what is up w/ my phone?
What suggestions do you have, this is what I tried, I was even able to connect to neighbors open network:
restart phone, turn off, "forget network", toggle wifi on/off, plug in usb,
Your lease probably expired. Did you try restarting your router?
Never had to do that in the past, but I'll try it. Guess i'll go to sleep now, maybe it fixes itself tomorrow, if not, I'll restart the router and post back the results
what type of router have you got? I have the same problem with a Zyxel router. Can't find a solution to it. Google shows lots of problems with Zyxel and HTC.
If you find a solution to your problem can you post back so I can try it out. Cheers.
MAC address filtering enabled?
Yea I also had that issue but only on cyan base roms. Sense and MIUI never had that issue. Well anyways I fixed this by flashing a new rom
Sent from my HTC Vision using XDA Premium App
Yeah I had the same problem, I just rebooted my router and it worked perfectly after that.
Reboot your router.If also not working,change you router's sig channel(1~12).
Since the update, WiFi fails to connect to the Router after several starts (sleeps).
Upon entering the WiFi control panel, you notice it's stuck at "Obtaining IP Address" indefinitely.
The only way to resolve the problem seems to be to manually shutdown the WiFi and restart it again.
The problem reappears after several sleeps.
i have the same problem... whenever I wake my tf up I have to shut off then turn on the wifi. Annoying!
I always leave the wifi on as a result. Normally if I pull the power on my router, it'll fix it.
I had this initially at work when I first acquired the unit, but my Froyo phone couldn't get an IP either so I figured it was work related. Every day since then it has worked seamlessly everywhere.
Got the same issue, have to switch Wifi off and back on to fix it. Still running 3.0.1 though, hopefully this gets fixed. What versions are the previous posters using?
Not seeing an issue on mine. Running 3.1.
I had this issue too ever since flashing PRIME 1.4 and going from 3.0 to 3.1 but as time passed this happened less frequently and now it happens once in a long while. I believe (not sure though) that the update downgrades the wifi (drivers or whatever) version as some other things (gps too i think). maybe that causes the issue.
I've seen this also with my stock 3.1 16GB. Doesn't happen all the time, but enough to be annoying.
So I find it's best not to leave the tablet attached to the dock because of the dock battery draining issue, and now maybe it's best not to use the wifi power savings mode because of this problem.
I have been experiencing weird issues with the network I built at my own business. I have 4 pc's, a NAS and a printer connected to my router. Previously I had 2 pc's via direct connections into the router along with the NAS and printer and the other 2 pc's and my Galaxy S phone connected via wireless. The minute I introduced the Transformer to the network (after discovering the Transformer couldn't see channel 13 and having to change my router to a lower channel) I have had issues.
Everything would work fine until I used the Transformer on the network and then the wireless would go down within a matter of hours and be unresponsive until I rebooted. I eventually connected all pc's to the router via a powerline socket network and only had the phone and transformer via wireless as I needed the pc's connected reliably.
I have eventually found that the only way to have the wireless working fine is to either not use the Transformer at all with it or (the option I am using now) to have the router only use B & G ranges and to turn of N. I wonder if there is issues with the drivers for the wifi regarding the N standard (could be a stupid question but I know zero about network standards / drivers).
klau1 said:
Since the update, WiFi fails to connect to the Router after several starts (sleeps).
Upon entering the WiFi control panel, you notice it's stuck at "Obtaining IP Address" indefinitely.
The only way to resolve the problem seems to be to manually shutdown the WiFi and restart it again.
The problem reappears after several sleeps.
Click to expand...
Click to collapse
Same here......
Sent from my Transformer TF101 using XDA Premium App
Ive had this issue when I first got my TF with 3.0. It was still there after updating to 3.1. Someone here mention to set your wifi to static ip. I did and the problem is gone now.
I rooted and flashed my phone last night and everything was fine other than 1 thing. The Wi-Fi wouldn't connect on my home router. I tried several different roms and was left with the same problem where it was stuck on either obtaining ip address or authenticating. I then came into work this morning and the phone connected to my Wi-Fi network straight away.
Does anyone know how I can get around this problem, don't want to be using up all my data at home!
Thanks in advance
Dont get me wrong but did you try to restart the Router?
Sent from my HTC using XDA Windows Phone 7 App
Timzter said:
I rooted and flashed my phone last night and everything was fine other than 1 thing. The Wi-Fi wouldn't connect on my home router. I tried several different roms and was left with the same problem where it was stuck on either obtaining ip address or authenticating. I then came into work this morning and the phone connected to my Wi-Fi network straight away.
Does anyone know how I can get around this problem, don't want to be using up all my data at home!
Thanks in advance
Click to expand...
Click to collapse
I second the other suggestion. Those symptoms sound like your router needs a restart if it hangs at getting IP/authenticating.
I'm having the same problem on the network at my university.
I'm having problems with my wifi as well. We have a network here at my office secured with WEP. My galaxy nexus connects to it just fine but my Nexus 4 refuses. It sees the network, show strong signal but it doesn't seem to connect. I did manage to get it to connect once and I downloaded some updates but then the connection dropped and will not reconnect. I've tried various advanced settings (forcing the network to 2.4GHz, changing the power options, etc... No joy. This is particularly frustrating for me as my micro sim has not yet arrived so WiFi is all I have Hopefully it will work at home. At least there I have access to the router so I can make changes if needed. So far not a fan though.
I've got WiFi problems here, too. Roaming between different WiFi networks (home and university) often results in an non functional WiFi connection. Experienced this problem with stock Android 4.2 on Nexus 4 and Galaxy Nexus and latest CM 10.1 nightly on Nexus 4. Even reboot doesn't help every time.
As workaround: If WiFi connection is broken, turn on "flight mode", wait a few seconds and turn it off again. Works for me, maybe it works for your problems too.
I literally just received my nexus 4, and I haven't done anything with the SIM card yet, I just wanted to get things going on WiFi to start. It sees the network I want, let's me type in the password, and lets me click connect. After that it does literally nothing. No thinking, no obtaining IP address, nothing. Any ideas?
dyslexicpenguin said:
I literally just received my nexus 4, and I haven't done anything with the SIM card yet, I just wanted to get things going on WiFi to start. It sees the network I want, let's me type in the password, and lets me click connect. After that it does literally nothing. No thinking, no obtaining IP address, nothing. Any ideas?
Click to expand...
Click to collapse
I have exactly the same problem. Got the phone today and have tried several different access points - no luck. Restart the phone, no change.
Also, system updates screen said I could only download the update to 4.2 from a wifi connection till the 7th, so i set the date to the 7th and did the update successfully over the cell connection. Still no WiFi. Factory reset - no change.
---------- Post added at 09:18 PM ---------- Previous post was at 09:17 PM ----------
Oh, also tried the flight mode "trick" with no success.
Heartbreak said:
I'm having the same problem on the network at my university.
Click to expand...
Click to collapse
Your uni wifi probably is LEAP wifi or PEAP wifi, which is proven broken in Android 4.2
ecsk said:
Your uni wifi probably is LEAP wifi or PEAP wifi, which is proven broken in Android 4.2
Click to expand...
Click to collapse
It's also broken on my campus. Do you have any suggestions to bypass this?
ecsk said:
Your uni wifi probably is LEAP wifi or PEAP wifi, which is proven broken in Android 4.2
Click to expand...
Click to collapse
My university provides both LEAP and PEAP authentication. LEAP doesn't work for me either. But PEAP works. I'm able to connect via PEAP. (Stock 4.2 / 4.2.1 and CM 10.1)
Here is my log. It appears the authentication is timing out.
12-07 10:42:43.863: I/wpa_supplicant(19563): wlan0: Authentication with xx:xx:xx:xx:xx:xx timed out.
12-07 10:42:45.345: I/wpa_supplicant(19563): wlan0: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='XXXXX' freq=2447 MHz)
12-07 10:42:45.385: I/wpa_supplicant(19563): wlan0: CTRL-EVENT-ASSOC-REJECT bssid=xx:xx:xx:xx:xx:xx status_code=1
12-07 10:42:55.346: I/wpa_supplicant(19563): wlan0: Authentication with xx:xx:xx:xx:xx:xx timed out.
All other devices do connect fine and I even restarted the AP to make sure.
This is getting very frustrating. I couldn't connect to wifi at work (WEP, I know...) at all yesterday. I went home, and my WPA2 network at home worked perfectly. I come in this morning and boom, I'm connected just fine to the wifi here at work (the connection was remembered from my tries yesterday). I went to lunch, came back, no wifi. Reboots, reconnections, nothing seems to work. I also have a Galaxy Nexus with 4.2.1 and it connects to the wifi just fine. Grumble grumble....
-Matt
I did a few tests today and it seems to be only when using WPA2 with a pre-shared key. WPA works, as do open AP's.
jim.k.yee said:
It's also broken on my campus. Do you have any suggestions to bypass this?
Click to expand...
Click to collapse
No solution with stock google image AFAIK, because google does not provide 4.1.2 image for Nexus 4. You can try other custom ROM or ask if some one has successful LEAP wifi story about running custom ROM.
BTW I don't own Nexus 4, I am stilling using Galaxy Nexus, as soon as I upgraded to 4.2 LEAP wifi broke, I flash 4.1.2 back then it works fine.
I found that upgrading the access point (MikroTik) to the latest version allows me to connect.
Seems something in this device does not like some older WPA2 versions?
extremewing said:
I found that upgrading the access point (MikroTik) to the latest version allows me to connect.
Seems something in this device does not like some older WPA2 versions?
Click to expand...
Click to collapse
My N4 has been connecting fine to my home router over the past two days. Suddenly, today, it stopped recognizing the network (shown as "not in range" in wifi settings). No amount of router or phone reboots would get it to connect. I read in another forum about going to Displays in the settings menu, scroll to bottom - Wireless Displays. Turn on and search for wireless displays, then turn off. I thought, wtf? Anyway, I tried this and it connected to wifi immediately. Maybe there's a bug in the wireless display function that's interfering with wifi.
I am actually having a similar issue as others here, but I have found another weird work-around. Basically, although the Nexus 4 see's my campus's network, no packets get transfered back and forth, and I am not even sure what is going on (The IP address, tho, is usually "unknown".) However, upon going to the campus's IT help today, they turned off mobile data, and it then seemed to connect fine over Wifi. Any idea what is going on here?
There is no "signing in" to the network at my university, it just connects and verifies your device's MAC address, so I don't think they are doing any fancy authentication. I was thinking about maybe flashing a different ROM and seeing if I get different results.
i got mine yesterday and it connects then stops connecting after a couple seconds
Atrag said:
I am actually having a similar issue as others here, but I have found another weird work-around. Basically, although the Nexus 4 see's my campus's network, no packets get transfered back and forth, and I am not even sure what is going on (The IP address, tho, is usually "unknown".) However, upon going to the campus's IT help today, they turned off mobile data, and it then seemed to connect fine over Wifi. Any idea what is going on here?
There is no "signing in" to the network at my university, it just connects and verifies your device's MAC address, so I don't think they are doing any fancy authentication. I was thinking about maybe flashing a different ROM and seeing if I get different results.
Click to expand...
Click to collapse
I get exactly the same issue in my office. I can connect to school open network, but after a few minutes it lost connection (while still showing connected). I got to wifi setting, it shows that there is only one wifi hotspot and i am connected to it. But actually there should be more than five hotspot! If i switch wifi off and back on it can detect all the networks and get connected again, but then it goes to the weird cycle over and over.
Strangely, if i stayed in another office, it is connected all the time. Seems like the signal problem in my office. But i got no problem in my office when i was using galaxy nexus.
I am driven crazy by this!