Database Users

[Q] Xoom WiFi inoperative

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.

[Solved] Wifi doesn't reconnect after resuming from standby

My TF (Stock 3.1) has an annoying problem that I've just stumbled upon.
If I set the wifi to disconnect on sleep and reconnect when powered back on, the Wifi will not connect. Just gets stuck on aquiring network address.
If I set it to always on, it never has any trouble. Connects in an instant.
I tried leaving wifi On and rebooted the router and it connected as soon as the router was ready. I also switched it to wifi off and then on and it connected straightaway. Take it out of wifi zone and back again and connects perfectly.
Never lost/dropped a connection before. Though I'd enable the sleep feature to save some battery while I'm at work or at night.
I'm not sure if this is unique to me.

Had the same issues. I had to set my ip to static on the TF. This will resolve the issue you're having.

Had the issue only once. Had to turn off/on the wifi. I think is an android problem because my Motorola atrix has the same issue.

dazz87 said:
Had the same issues. I had to set my ip to static on the TF. This will resolve the issue you're having.
Click to expand...
Click to collapse
Fixed it. Thanks heaps..
Did not have this problem on the Desire, stock or with any of the ROMS i've tried

dazz87 said:
Had the same issues. I had to set my ip to static on the TF. This will resolve the issue you're having.
Click to expand...
Click to collapse
How do I do this on the TF? I can't find it anywhere for this option

I too have this problem, how do I create a static IP address on the TF please ????
Or is this done on my wireless router ?

rsmccleary said:
How do I do this on the TF? I can't find it anywhere for this option
Click to expand...
Click to collapse
go into you wifi setting. locate your ssid and click on it till you see modify. scroll.down to change from dhcp to.static

i don`t find that menue in the TF

yeah i dont have that option

It confused me at first as well.. locate your SSID and select the option to forget all the information. Then when you attempt to connect again you should see it there.
HTH.

oztraze said:
It confused me at first as well.. locate your SSID and select the option to forget all the information. Then when you attempt to connect again you should see it there.
HTH.
Click to expand...
Click to collapse
see i dont even have the option. in the wireless& networks > wi-fi settings, there is no option for ssid. the only option is an icon at the top right of the screen that says "scan" or "advanced". in the advanced section, it gives me IP and MAC addresses. nothing gives me an option to obtain ssid information. i wonder if the american version of the tab is different.

rsmccleary said:
see i dont even have the option. in the wireless& networks > wi-fi settings, there is no option for ssid. the only option is an icon at the top right of the screen that says "scan" or "advanced". in the advanced section, it gives me IP and MAC addresses. nothing gives me an option to obtain ssid information. i wonder if the american version of the tab is different.
Click to expand...
Click to collapse
Okay Go into Wi-FI setting, Under WiFi network setting find your wifi network (name of your network) which should be the first one at the very top. Hold down on your wifi network and you should see a "modify network" option. Select that. Then you want to scroll up. You should then see "IP setting", change DHCP to Static. SSID is the name of your wifi network.

Wi-Fi issues out of the box

My Tab is brand new from Staples bought yesterday. After unpacking and charging,
wi-fi won't connect to my Verizon DSL wireless router. The Tab has v3.0.1 software.
I've read about plenty of wi-fi issues with the 3.1 upgrade, but, are there know issues with v 3.0.1 software.
I am looking for suggestions and help. Thanks

jostarr said:
My Tab is brand new from Staples bought yesterday. After unpacking and charging,
wi-fi won't connect to my Verizon DSL wireless router. The Tab has v3.0.1 software.
I've read about plenty of wi-fi issues with the 3.1 upgrade, but, are there know issues with v 3.0.1 software.
I am looking for suggestions and help. Thanks
Click to expand...
Click to collapse
a little more info might help, like what the wifi does, does it just join, but just says remember, or does it not find at all, or does wifi say error completely??

jakomo73 said:
a little more info might help, like what the wifi does, does it just join, but just says remember, or does it not find at all, or does wifi say error completely??
Click to expand...
Click to collapse
Thanks for your reply.
I never got connected. It says trying to obtain an IP address, or something like that. I also tried several resets using the paper clip procedure to no avail.

And is your router secured with a key? If so, were you prompted to add it before trying to connect? Did you add it correctly?

gammaRascal said:
And is your router secured with a key? If so, were you prompted to add it before trying to connect? Did you add it correctly?
Click to expand...
Click to collapse
It never asked for the password because it never got an IP address assigned to it.

jostarr said:
It never asked for the password because it never got an IP address assigned to it.
Click to expand...
Click to collapse
It can't get an IP address unless it has the WEP key to connect to it.
I take it your router isn't secured then.
Or maybe it's different for DSL *shrug* I don't know.

gammaRascal said:
It can't get an IP address unless it has the WEP key to connect to it.
I take it your router isn't secured then.
Or maybe it's different for DSL *shrug* I don't know.
Click to expand...
Click to collapse
I may be wrong, but I think it must first have an IP address assigned to it by the router. Then, you must give the password to get connected.
That's how it works for my laptops and iPod Touches.

jostarr said:
I may be wrong, but I think it must first have an IP address assigned to it by the router. Then, you must give the password to get connected.
That's how it works for my laptops and iPod Touches.
Click to expand...
Click to collapse
Take it back and exchange it.....
my first one had wifi issues as well... hardware issue.

jostarr said:
I may be wrong, but I think it must first have an IP address assigned to it by the router. Then, you must give the password to get connected.
That's how it works for my laptops and iPod Touches.
Click to expand...
Click to collapse
I don't know. That might very well be a "DSL" thing. But in order to connect to a wireless router (which has been secured with a WEP key) one must first add the WEP key to the device then, and only then, will the device be able to connect - not the other way around.
Don't confuse 'password' with 'WEP key'. While their job is similar (preventing unauthorized users from connecting) the lack of a WEP key prevents connection, period, while a password requires a connection first.
But like I said, for DSL routers, maybe it's different - the only thing I can think of would be for you to log into your router from your laptop/desktop and check the wireless settings to see if it is indeed secured with a key - if so, write it down and try again from the tab, making sure that you input the key before it tries to connect.
Of course it *could* be a hardware issue. but it sounds to me like you're missing something.

gammaRascal said:
I don't know. That might very well be a "DSL" thing. But in order to connect to a wireless router (which has been secured with a WEP key) one must first add the WEP key to the device then, and only then, will the device be able to connect - not the other way around.
Don't confuse 'password' with 'WEP key'. While their job is similar (preventing unauthorized users from connecting) the lack of a WEP key prevents connection, period, while a password requires a connection first.
But like I said, for DSL routers, maybe it's different - the only thing I can think of would be for you to log into your router from your laptop/desktop and check the wireless settings to see if it is indeed secured with a key - if so, write it down and try again from the tab, making sure that you input the key before it tries to connect.
Of course it *could* be a hardware issue. but it sounds to me like you're missing something.
Click to expand...
Click to collapse
If it says it is still waiting for an IP address, I can't type anything in....WEP key or password. I may have not been clear with the problem. It "sees" my router, but is constantly trying to obtain an IP address. Sorry for the confusion.

There's no confusion. Of course it will see your router if the router is broadcasting its SSID. That still doesn't mean you *can* connect to it.
Log into your router and check if your wireless is secured with a key. If it is, then you need to add it to your tab *before* it can get an IP address. I can't be any clearer about that.

gammaRascal said:
There's no confusion. Of course it will see your router if the router is broadcasting its SSID. That still doesn't mean you *can* connect to it.
Log into your router and check if your wireless is secured with a key. If it is, then you need to add it to your tab *before* it can get an IP address. I can't be any clearer about that.
Click to expand...
Click to collapse
Ok, thanks. I know the WEP key. But I don't low how\where to enter it into the Tab. I would appreciate it if you could post step by step instructions. Up till now, I have been trying to follow what the Acer manual pdf says:
"If you did not connect to a Wi-Fi network when you first started your tablet, or want to connect to a new network, tap Apps > Settings > Wireless & networks to manage your connection settings. Alternatively, tap the Wi-Fi status icon in the bottom-right corner of the screen.
If Wi-Fi is not on, tap Turn on Wi-Fi, and wait for your tablet to detect nearby networks. Tap the name of your network and enter a security password, if needed."

Right. Click on the network, add the WEP key where it says 'password'.

I'll try it later when I get home from work and will post my results. Thanks for you help.

What you're doing sounds strange. I too have a DSL router, but it works no different than any other router I've ever had. I've had several Android devices including tablets, and they all work the same. When you try to connect to a protected network, it will prompt you for a password. It cannot obtain an IP without the password, this step occurs after the password verification.
I have had issues where my remembered networks just sometimes sit at "Obtaining an IP address...", and never connect. Usually a reboot solves this problem. I tend to have more issues with WPA networks than WEP, but almost nobody uses WEP anymore.
But, there really shouldn't be a trick to it. Click on the network and it will prompt you for a password (WEP or WPA, works the same). If you've already done this, try rebooting.
I've never had the experience that jostarr has, where I needed to enter a key before a password.
Otherwise, like one of the other posters stated, it could be a hardware issue.

Problem solved.
I tried the Factory Reset from the settings menu. It took a few minutes to reset and reboot. A s soon as I went to the Wi-Fi settings, it found my router, got great signal strength, and was asked for my password. It then connected immediately.
I then went to settings, and looked for any updates. It found the latest update, so I downloaded and installed OS v3.1. It took about 1 hour to complete the download and installation. My tab works great now. I could not be more pleased with it.
Many thanks to all on this forum and elsewhere who contributed their suggestions and advice.

congrats on solving your issue Jostarr. I'm happy you got it worked out.

Does anyone have a proper workaround for the obtaining IP address?

Honestly I have no idea why this is happening on my android 4.0+ devices. I will get stuck on obtaining IP address connecting to certain networks and the only thing that worked for my home network is static IP. But for instances when I don't have access to the router to know what the static IP should be, is there a way to get this working? This happened on my phone as well. I was at a local cafe which had wifi and before I upgraded my samsung galaxy s2 to ICS, I could connect to their wifi no problem, now it has the same issue, and so does my Nexus 7. I don't know what to enter for static IP, I entered some random IP, it connected but internet still didn't work. Why is this problem plaguing ICS onward, and does anyone have a workaround when static IP is not an option?

This is definitely not a universal problem (I've never heard of it before). Are you running stock roms? If not, then do you have these problems with stock roms?

C2Q
Why are you posting this to multiple threads?
There is no "proper way" to use a static IP for a router that is setup for DHCP only. For routers that use both, many times the static IP's are reserved for specific devices.
Sent from my Nexus 7

Because I didn't notice the other thread before I posted this one. Anyway then why is this obtaining IP address loop a problem on ICS? As I said, my phone on GB would manage to connect/obtain an IP address just fine before I upgraded to ICS. This happened with my home router and other areas as well. The solution that worked for me at home was to assign a random static IP within my routers IP range. But if I don't know the gateway IP this won't work. So what gives? I'm kind of confused what you mean by routers set up for DCHP only. If I use static or DCHP options on the android device to connect, they will both work (this was before ICS).

I ran into similar issues with my nexus 7 and my work open wifi. It needs you to connect to a web login page where you accept a use policy before you can surf. My nexus would connect but never redirect to that login page.
The issue was resolved by using static IP instead of DHCP and also by changing the DNS values to DNS1 8.8.8.8 and DNS2 4.4.8.8
Changing those settings lets me finally use my work wifi. My phone also has the same issue (its an ICS phone, whilst the nexus is jelly bean) but is not resolved with this change.

Sunburn74 said:
the issue was resolved by using static IP instead of DHCP and also by changing the DNS values to DNS1 8.8.8.8 and DNS2 4.4.8.8
Click to expand...
Click to collapse
Sure that is not 8.8.4.4 ?

Thanks for posting this question. I have exactly the same problem with my Samsung S3 (ICS) and Nexus 7 (Jellybean). My old Samsung S2 (Gingerbread) worked fine.
I am trying to connect to a hotel open network. When I try I get the looping "Obtaining IP..." message. I have a strong network signal.
What gives? How come earlier versions of Android worked but later ones don't?
As the OP stated, the static option works insofar as I can then connect to the network but the made up static IP numbers do not actually let me download (or upload) data. As the OP wrote, you need to know some valid values for the static IP setting.
Does anyone have a solution for this (apart from downgrading to Gingerbread)?

Ive always had this issue but my home router has dhcp off. A majority of routers start with 192.168.1.1 or 192.168.1.2 so its not hard to work it out.
BT routers always start with 192.168.1.254 so there's another option dunno why my devices do it but im used to it. My Wifes Xoom 2 and wildfire S are stock and do not have the issues my rooted ones do but i have just put it down to coincidence

First off. Is your modem in service? Do other devices connect? Have your restarted your tab? Does it connect to other networks? Meaning going to another WiFi hotspot If you can answer yes to all of these questions we move on....
What modem/router are you connecting to?
What type of WiFi encryption are you using? Wep-open, WPA, wpa2-psk
On the tab does it fail to obtain the IP address? Meaning it says "remembered"?
Not going to lie more the 3/4ths of the time you have the wrong WIFI PASSWORD. CHECK IT AGAIN usually its on the modem/router or if you have no clue here is a hint: on windows vista and windows 7 under control panel>network and sharing center>manage WiFi networks if your right click on the network name such as "Ilovepancakes"and go to properties it will have a security tab that you can click on and show password.
Sent from my Nexus 7 using XDA Premium HD app

bonesy said:
Ive always had this issue but my home router has dhcp off. A majority of routers start with 192.168.1.1 or 192.168.1.2 so its not hard to work it out.
Click to expand...
Click to collapse
I don't know what you mean. Do you mean that I should try these numbers to see if they work? You need a number of values to set up static IP addressing to work.

Did you dirty-flash your Nexus? A while back my Gnex wifi connections would take longer to complete the handshake. I did a factory reset/fresh install & it has been much faster.

strongergravity said:
Did you dirty-flash your Nexus?
Click to expand...
Click to collapse
My Nexus (and GS3) is completely stock (I have only added a launcher).
This problem seems to be caused by older routers, which don't seem to like something about newer versions of Android.
I'm not sure if it's something Google can fix, but the combination of old router and new Android seems to make logging onto wi-fi networks a problem.

Bump.

Ive been struggling with this problem for a week now since getting a transformer infinity. My s3 gets stuck when I try to connect to it. The tab cycles through connecting, obtain a valid address and saved.

I bought a new 32gb nexus yday and had this issue. I entered advanced settings, changed dhcp to static. Changed IP addy to 192.168.1.1 and it worked fine. Only had to do it once. After that it connected to every network fine without changing settings again.
Sent from my Nexus 7 using xda app-developers app

Warrior1975 said:
I bought a new 32gb nexus yday and had this issue. I entered advanced settings, changed dhcp to static. Changed IP addy to 192.168.1.1 and it worked fine. Only had to do it once. After that it connected to every network fine without changing settings again.
Click to expand...
Click to collapse
This worked for me also (Infuse 4G on JB), but it seems like this is only a problem on WiFi AP's that have marginal signal strength, even though they appear to have full bars. I personally have never have seen this issue on a network that was performing properly.

Same here!
Same thing is happening to me! Im using he htc desire c running ics.. my phone detects the wifi network, shows that it has excellent strength, but it gets stuck at "Obtaining IP Address"! My friend and I both bought the same model a couple of weeks earlier and till now neither of us have been able to connect to a wifi network! Please Help!!!

its a DHCP bug
This is probably not a problem with your network configuration unless it works everywhere else; im having the same problem as well as other people i know and its definitely a bug with DHCP, so the only way to work around this is by using a static ip as far as i know

bobbyelliott said:
I don't know what you mean. Do you mean that I should try these numbers to see if they work? You need a number of values to set up static IP addressing to work.
Click to expand...
Click to collapse
What he's saying is that most routers will begin assigning addresses starting with 192.168.1.1 or 192.168.2.1 for itself (you can access the router configuration page by typing in this address into a web browser), and then increment upwards afterwards. If you knew that the router started its DHCP addressing with 192.168.1.1, for example, you could try 192.168.1.2, and so on and soforth.
If you did a "dirty" upgrade, I'd recommend doing a factory wipe (after an appropriate backup-- there are some good apps out there that can handle this). In-place OS upgrades have a bad habit of being finicky. Android is also generally less tolerant of network "misconfigurations" than, say, Windows, OS X, or iOS. Many networks that use captive portals (your standard coffeeshop Wi-Fi) deliberately use an altered network setup to support their access policies, such as a captive portal.
However, with the exception of corporate/enterprise networks (which may require fine-tuning because of increased security), you really shouldn't be messing around with this if you don't have at least a rudimentary understanding of how networking works. That's not meant to be insulting, but when people plug in random values and find it doesn't work, it tends to lead to more frustration than utility.
(fyi: The reason you can "connect" by tossing in a random set of octets your your IP and DNS is because you've properly authenticated against your router, but you'll never be able to receive data unless your router's DHCP lease lines up with your self-assigned IP, because the router never handed that address out to you. It's the digital equivalent of building a mailbox in front of your house without registering with the post office, and wondering why you never get mail).

Unable to connect to portable hot-spot.

My 7th generation fire HD can't connect to my Nexus 6P's portable wifi hot-spot. It connects, but fails to acquire an IP address. Other devices have no problem. I've tried 2.4 and 5ghz. Security is WPA2 PSK.

go into wifi options and edit the connection to use a static ip and see if that works. You'll have to know the ip range the nexus 6p assigns.
I've used mine on my AT&T hotspot, mobley, and my pixel xl (on verizon OG GUDP) with no problems.

madsquabbles said:
go into wifi options and edit the connection to use a static ip and see if that works. You'll have to know the ip range the nexus 6p assigns.
I've used mine on my AT&T hotspot, mobley, and my pixel xl (on verizon OG GUDP) with no problems.
Click to expand...
Click to collapse
How do I discover what IP range it uses?
Nevermind. It seems to be android default: 192.168.43.0/24
192.168.43.1 as the gateway and 192.168.43.43 as the IP seems to have worked just fine. Unfortunately it doesn't remember those settings and I must enter them each time. I wonder why DHCP isn't working? >_<
At least it works. I'm going to have to do that frequently though. Thank you! ^_^

Dr3x1 said:
How do I discover what IP range it uses?
Nevermind. It seems to be android default: 192.168.43.0/24
192.168.43.1 as the gateway and 192.168.43.43 as the IP seems to have worked just fine. Unfortunately it doesn't remember those settings and I must enter them each time. I wonder why DHCP isn't working? >_<
At least it works. I'm going to have to do that frequently though. Thank you! ^_^
Click to expand...
Click to collapse
The reason is because Amazon has 'blocked' the use of that function so anytime your reboot, the settings to it are reset.