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).
Related
I have a ZyXEL P-2602HW-D1A Wireless router. I have tried all combinations of security, even NO SECURITY WHATSOEVER, and still the device won't transfer data.
Not working;
Firmware: 1.5, Build: CR817
Wifi Router: ZyXEL P-2602HW-D1A
Security: Tried All; WPA2, WPA, WEP & None.
Problem: Connect under all conditions but no data is sent
Please help.
Have you tried another WiFi access point to check the devices WiFi module actually functions?
No, I haven't tried that yet, but don't really see the point... I've connected effortlessly to the same WiFi network with my HTC Touch Diamond.
jbelman said:
Have you tried another WiFi access point to check the devices WiFi module actually functions?
Click to expand...
Click to collapse
For some reason my N800 wouldn't connect to MY ZyXEL P-2602HW-D1A unless I set the device (N800) to disable any kind of wifi powersaving features it had.
On another note, how did you get your hands on the device so early? I'm guessing you are using a Cybercity internet connection? (I'm in copenhagen myself)
edit: I actually came to that solution when i noticed I could connect to OTHER accespoints, but not the Zyxel ones.
Same problem here in France with a Freebox as router
I've noticed under the router's WLAN client list that the device does not have a "Host Name". Would that present a problem?
It is assigned an IP address by the router without any problems, though.
Also the device seems to lose connection and reconnect constantly (every 5-10 seconds).
I done some digging around in the router settings and found an "AnyIP" feature. Would that possibly help?
There are a number of issues floating around. Support for WPA2 seems iffy and some people can just change to WPA or WEP and all work fine.
There are however a number of people (such as me) who can get a connection perfectly, it shows connection OK, they get an IP from the DHCP server etc, they can even browse a page for a few seconds... but after that no data is sent and everything times out. This is happening on any security from none through to WPA2.
I have seen no solution to this anywhere and believe me I have looked. Some people have given up and got a new router, but this is not a solution.
Can someone confirm that this has been recognised as a fault with the magic and is being investigated, rather then assuming it's a user or router error. There are far too many instances of this across many brands of router for it not to be an issue with the HTC Magic.
zyborg said:
No, I haven't tried that yet, but don't really see the point... I've connected effortlessly to the same WiFi network with my HTC Touch Diamond.
Click to expand...
Click to collapse
What I mean is have you tested the device on ANY other AP except the ZyXEL?
No, but since I'm by far the only one having this issue (try searching the web; see my last post), I didn't feel it was necessary. Just want some input from xda-dev that might solve the problem, if any.
jbelman said:
What I mean is have you tested the device on ANY other AP except the ZyXEL?
Click to expand...
Click to collapse
I've had exactly the same problem earlier with the N800 on the zyxel. Exactly how you describe it.
Did you find out if you could turn off any powersaving features on the HTC?
same problem here
in france with a freebox
I don't exaclty know what router is in the box
but I have excalty the same
I set on never the wifi sleep(powersaving) mode.
i found it in setting wifi menu button then advanced and "never"
but the problem is still here
zyborg said:
There are however a number of people (such as me) who can get a connection perfectly, it shows connection OK, they get an IP from the DHCP server etc, they can even browse a page for a few seconds... but after that no data is sent and everything times out. This is happening on any security from none through to WPA2.
Click to expand...
Click to collapse
I have the exact same problem on mine. I just hope it is not a hardware issue...
Could be DHCP lease time problem. Did anyone of you tried to set up Magic with Static IP?
Yes, I tried that also - didn't help one bit.
TheRookie said:
Could be DHCP lease time problem. Did anyone of you tried to set up Magic with Static IP?
Click to expand...
Click to collapse
I also have this problem. Im in Denmark with a Zyxel P660HW-p1.
Another user of Cybercity in Denmark with the same problem.
ZyXEL P-660HW-D1
The android is the only device that doesn't work. I have tried with Iphone and laptops.
I've tried to change the settings on the router to no avail.
Enable 802.11g+ mode [on/off]
RTS/CTS Threshold [2432/4096]
RTS/CTS Threshold [2432/4096]
Max. Frame Burst [600/1800]
The device shows up in the device list with no hostname, the HTC Magic gets the right ip address (using the program WhatIsMyIp to view it)
I had the same problem before, when I set my TP-LINK draft N router with WEP security my HD can see it, connect to it (but speed was slow tho), and my HTC Magic just keep saying its not in range. However, when I set it to open security it works, so I recognise its probably the security setting... so I changed that to WPA2 and then it works.
In my case, I see different device have different tolerance to some settings (in my case, draft N + WEP is OK with laptop, HTC HD, but not Magic), so its still worthwhile to try a few different settings, and try a public wireless access point also to double confirm?
Power save?
I have Zyxel (P-2602R-D1A) router.
I had exactly the same problem with my HTC Vox (winmo)... but that was solved by boosting the WiFi in the phone.
WiFi -> Best performance
So Im guessing magic is in some WiFi "power save" mode...
I dont know how this works, but I thought maybe you could change some WiFi settings behind the hood - that is if the hardware is capable of it.
Zyxel (P-2602R-D1A) router
I am having the same issue with this router as the other posters. The phone connects perfectly and reports an excellent signal, but barely sends or receives any data. I have used a terminal emulator to ping the router and it reports an 82% packet loss. This must be a big problem for many Danish users as it is the standard wifi router provided by two of the major ISP's.
same issue here with my vodafone uk magic.
wifi connects and i can browse for a few seconds then get a connection error and can't browse until i re-start wifi on the magic...
i've actually given up using wifi at home now due to this.
router is a talktalk supplied Huawei Echolife HG520b using 128 bit WEP
i can connect fine via wifi at the office so i don't think it's an issue with the handset, just with certain routers or router configs...
this issue has been reported on the vodafone uk forums but as yet no solution.
http://forum.vodafone.co.uk/index.php?showtopic=31937
I've had the captivate about 24 hours now and dig it. I've rooted it and remove the att bloatware (per titanium backup), I've also performed a backup using Rom Manager.
I'm having trouble getting it up and running on an enterprise wireless what uses 802.1x PEAP authentication. I can get through all the auth. steps, and the device is assigned an IP, but I am unable to do anything that requires an internet connection; browser, market, etc.
Has anyone else ran into this issue?
*****EDIT*****
sigh i just realized that this is in the wrong area, it should have been over in development...i'm an idiot
I had a similar problem on a WEP-encrypted network, which I fixed by setting a static IP on the phone and then setting it back to DHCP (the correct setting). However, your problem could be entirely different than mine (not that I even am sure what my problem was, just that I fixed it!)
Best of luck!
Having the same problem on enterprise access points regardless of encryption. Home wifi netwroks work great (open and WPA2). Enterprise APs (open and WEP) connect and give me an IP, but will not transfer data. Think its a driver issue with the Wifi, it happens on every captivate ive tested, and seems to be more widespread than the GPS issue.
I have had the same issue with my work at work. I can get it to connect and get a ip but can not pass any data.
Sent from my SAMSUNG-SGH-I897 using XDA App
Had the same problem at work. Luckily I'm an admin and figured mine out. Our monowall portal was the issue. I can give a detailed answer for my problem tomorrow when I get to work.
I actually had the cap wiped to go back, then I literally figured out the problem. Thanks go out to my team mate for helping me talk through this.
Sent from my SAMSUNG-SGH-I897 using XDA App
can't wait to hear what your fix was!
Sent from my SAMSUNG-SGH-I897 using XDA App
This sounds more like your network not being allowing your device rather then the device having an issue.
it's been frustrating as I know two other guys with android devices that didn't have an issue. one is a droid eris running 2.1 and the other is a nexus one running 2.2.
Sent from my SAMSUNG-SGH-I897 using XDA App
designgears said:
This sounds more like your network not being allowing your device rather then the device having an issue.
Click to expand...
Click to collapse
Worked closely with my highly experienced network admin in my dept. for an afternoon (we had some time to kill). He checked the firewall and dhcp servers, ran packet traces, etc.
With what I'm experiencing, its the device. These wifi networks we use with Cisco APs are completely wide-open. All other phones and mobile devices have always worked great for years. We rely on this network for many custom applications and mobile tools.
Once the dhcp server leases an address, it seems like the radio stack hangs, and the device ceases communication. Here's an older thread on the exact issue over at androidfouroms: http://androidforums.com/samsung-captivate/130403-wifi-terrible.html
I have tested multiple new unmodified captivates and the issue is identical accross the board.
Now that I am at work, and have coffee in me and not beer, I will go through the problem I had with miCap and works wireless. Due to my skeptical ways, I will be semi vague for security purposes. On with it.
When I originally got miCap (pet name for it) I was able to access our public wifi. It allowed me into the public portal to agree to terms. I played a little bit on it, but wanted to see if I could access our private wifi. I got in the private no problem. But after that I never was able to get back on to our public. It did the same thing as I've read. It got an ip no problem (via dhcp) and acted like all was well. No browser, or ap could get a connection. The phone would not switch over to 3g to get info.
Armed with ip and mac address, my co-worker and I started to did through our monowall. ( He also has a cap that had no issues on public or private). We try tried reserving the ip for miCap, didn't work. We tried static ip, didn't work. I spent the morning completely wiping miCap to get it back to return worthy.
This was when I decided on last ditch effort.
Our ap's are cisco's that connect into monowall. I got into monowall and dug around. I found that with in the captive portal (how fitting) that the ip/mac associated with my phone hadn't checked in for 8 days. Even though I tried everyday. I deleted the entry to the phone there and suddenly my phone was getting access again.
Now I understand that this may not help everyone, because setups vary from place to place. But digging deeper into configurations at the access points may be what is needed. Do I think the phone had nothing to do with it? No, I think it helped aggravate the problem.
We have had problems with the Intel 3945abg chipsets with the same exact setup. That problem was fixed with driver updates on the laptops.
sorry for the long winded reply.
So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.
Pmac25 said:
So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.
Click to expand...
Click to collapse
Essentially yes. But it is not listed like that in the portal. Hmmm. I wonder about the combo of dhcp/dns being the culprit.
I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network
I sent a help ticket into samsung; maybe if enough folks do we can get it on their radar.
jhannaman82 said:
I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network
Click to expand...
Click to collapse
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.
phlunkie said:
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.
Click to expand...
Click to collapse
Thanks for that, i figured the menu was built in somewhere just never found it.
:thumbsup:
UPDATE
So I flashed the i9000 Eclair rom last night, and when I got into work today I can connect and use the wifi here. So looks like something AT&T buggered up, big surprise there, when they "customized" the captivate.
As much as I normally love blaming AT&T for problems, that can't be done here. My Captivate (running Stock Firmware) connects just fine to my work network. We use 802.1x with PEAP/MSCHAPv2 for authentication.
Anyone been able to connect at over 802.11b speeds while connected to an 802.1x network? I show connections at G and N speeds on my WPA2 network but nothing over 11Mbps on 802.1x.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hi,
I am also having problems with my work wifi network.
It is 802.1x, on TTLS/PAP it also requires a thawte premium server ca certificate insalled.
Is there any way to connect this kind of networks?
With my previous iphone 3g it was taking only 4-5 seconds.
I've tried several builds:
Darkstone Froyo
DarkStone FroyoStone
mattc Froyo with Sense
mattc Froyo without Sense
shubcraft
Xcelsior
mccm v1.7
WiFi just does not work at home. It'll connect, but I can't actually browse anything. It comes back immediately as a "page not found" error. Today I took my phone around town specifically to test WiFi on other networks. It worked perfectly on two open networks. There were no issues at all. It works at my office as well.
My network at home is wired as:
Internet --> DLink Gamer Lounge (wired router with special features) --> Linksys WRT54G wireless router
The DLink has DNS and DHCP services. The Linksys has none and is assigned a static IP.
My network at work is wired as:
Internet --> DLink Gamer Lounge --> everything else including a Linksys WRT54G setup just like at home
There is a Windows Server setup to take care of DNS and DHCP. The Linksys has same setup as at home.
At home, I disconnected the DLink, enabled DHCP on the Linksys, then my Android phone worked on wifi just fine.
I reconnected wired router and reset all settings. Android wifi doesn't work anymore.
I don't think my wired router is incompatible. I'm wondering if the wireless router not being the DHCP agent has anything to do it. Other wireless devices connect fine like this. My phone in WinMo connects fine. My friends' iPhones connect fine. My friends' native Android phones connect fine. Every wireless device (except HD2 Android) connects to the network and works just fine.
Anyone have any suggestions?
Is there a route tracing program for Android? Or something that will show me all the IP information (including DNS)?
Update:
DarkStone1337 said:
Because you have no DHCP on your wireless router, your IP address and DNS server and default gateway settings aren't being set by Android. No idea why. You'll need to do this manually in Android by pressing the windows button in the wifi network settings and setting the right values from there.
Click to expand...
Click to collapse
I just used an app to check IP settings. IP address, subnet mask, gateway, DNS, and everything are being set properly (there is a DHCP server on network, just not on WiFi router). I tried to setup a static IP address and other settings. Whenever I try to connect that way, it gets to "Obtaining IP address" and then fails, cycling through the whole process. Is it possible the code for IP stack (or IP Tables) in these builds of Android are not complete?
Update 2:
DarkStone1337 said:
Not an app, but using ADB logcat is sufficient enough.
If you have adb set up then follow this: https://sites.google.com/site/androidhowto/how-to-1/save-logcat-to-a-text-file
Click to expand...
Click to collapse
Just read about ADB (Android Debug Bridge) briefly. I think this will be a bit out of my league. I'm not that familiar with Android / linux. I'll post in the other thread asking if someone else more skilled can grab one. If not, I'll see about trying to figure it all out this weekend.
Same issue
FreakyFerret said:
I've tried several builds:
Darkstone Froyo
DarkStone FroyoStone
mattc Froyo with Sense
mattc Froyo without Sense
shubcraft
Xcelsior
On all of them, WiFi just does not work. It'll connect, but I can't actually browse anything. It comes back immediately as a "page not found" error. Today I took Matt's Froyo with Sense around town specifically to test WiFi on other networks. It worked perfectly on two open networks (Quizno's and McDonald's). There were no issues at all.
My network was wired as
Internet -- Wired router (with special features) -- wireless router
The WiFi router was basically treated like a switch with its DHCP turned off. I disconnected the wired, enabled DHCP on the wireless, then my Android phone worked on wifi just fine.
I reconnected wired router and reset all settings. Android wifi doesn't work anymore.
I don't think my wired router is incompatible. I'm wondering if the wireless router not being the DHCP agent has anything to do it. Other wireless devices connect fine like this. My phone in WinMo connects fine.
Anyone have any suggestions?
Is there a route tracing program for Android? Or something that will show me all the IP information (including DNS)?
Edit: It should be noted other Android phones (that came with Android) do work fine. Just these HD2 builds is the problem.
Click to expand...
Click to collapse
I just want you to know I'm in the same situation as you. My router is a Belkin Wireless N router (WPA2 encryption). I get a valid IP address and I can ping the router but no DNS or access past the router. There was an earlier version of an Android build (I think a MattcFroyo) that worked with my wifi set-up. But I need BT headset support and the Darkstone build seems to be the only one that reliably works with my BT devices. (BlueAnt T1 & Motorola EQ7)
Please let me know if you find a solution that works!
Thanks.
Sept 4 Update. The only version that I have found that provides both Wi-fi connectivity and BT head set is the Shubcraft version 1.4 for my router configuration. Version 1.5 doesn't and neither do the latest Mattc and Darkstone builds.
Hell, I can't even get my Wifi working at all. Darkstones V1... Wifi just says "Error". Have the latest zImage, and everything. :/
Shushunmire said:
Hell, I can't even get my Wifi working at all. Darkstones V1... Wifi just says "Error". Have the latest zImage, and everything. :/
Click to expand...
Click to collapse
jinhenry, I'll let you know.
Shushunmire, are you using HD2Froyo or FroyoStone (clean or Sense)? Also be sure to post in Darkstone's thread that relates to the build. I know HD2Froyo v2 was giving error for wifi, but his latest update fixes that.
I tried various market apps to do network diags on the phone. All they offered was basic ping. When trying to ping anything on the wifi, it just fails right away. It's like it's not even seeing the network and just saying no network around. I even tried to ping the phone's own local IP and it failed. I tried looking for a traceroute type app, but there was none.
I installed Cirtex app. On cell connection, it pulls up the IP info of the wifi (but cell data works):
Device IP Address:{cell IP}
Interface name:/usb0(usb0)InetAddress:/{Ip of wired router, DHCP server, DNS server}
Interface name:rmnet0(rmnet0)Inetaddress:/25.1.238.x (don't know)
Interface name:lo(lo)InetAddress:/127.0.0.1
On wifi connection, it gives error:
Can not get te IP Address for the device. (errors their's)
Interface name:eth0(eth0)InetAddress:/{correct wifi ip}
Interface name:usb0(usb0)InetAddress:/{correct wifi ip}
Interface name:lo(lo)InetAddress:/127.0.0.1
If I use a static IP, and set the gateway to the actual network gateway (wired router, DHCP server, DNS server), phone tries to connect until it gets to the "Obtaining IP" stage, then it fails and cycles over. If I set the gateway to the wifi router (which is no more than a wifi access point) it will connect.
To repeat cause I know you have a lot going on: other wifi devices work on this network fine (using static or dynamic ips) including windows laptops, mac laptops, xbox, Wii, iphones, winmo phones (this one even), and even other android phones.
If I set the wifi router as the gateway (plug internet directly into it and turn on DHCP on wifi router), everything works fine. I don't even change its static IP.
Hopefully some of this will help. :/ The more I play around with it, I get the feeling the IP stack is the cause.
I AM HAVING THE SAME PROBLEM!!!! my lil bro got an htc hd2 as well n we got them the same day n when i flashed android on his and mine... his wifi was working while mine was not and i have tryed so many different builds but nothing solves the problem...it searches but at the end it says unable to scan networks....anyone plz help i really need wifi
p.s we both are on....
rom: core cell series
build: hd2 froyo v2.1
his hd2 works perfect while my wifi is not
jinharry said:
I just want you to know I'm in the same situation as you. My router is a Belkin Wireless N router (WPA2 encryption). I get a valid IP address and I can ping the router but no DNS or access past the router. There was an earlier version of an Android build (I think a MattcFroyo) that worked with my wifi set-up. But I need BT headset support and the Darkstone build seems to be the only one that reliably works with my BT devices. (BlueAnt T1 & Motorola EQ7)
Please let me know if you find a solution that works!
Thanks.
Click to expand...
Click to collapse
have you tried setting the router to use G only? i had an issue with the newer builds on a d-link 635 that was the same, it woudl work then suddenly woudnt work at all, rebooting the phone didnt help, changing the router to use G only instead of mixed seemed to fix the issue
Here's my issue. On my phone I could connect to wireless fine, my two sons liked Android on the hd2 so much that we picked up 2 more hd2's, that's where the problem started. Any one of the phones can work on wireless just fine... but try and connect any of the others and while they do connect, they don't work. Any of them.
It's almost as if they are seen as the same device or something. Some kind of unique id is missing or something.
Ducter said:
Here's my issue. On my phone I could connect to wireless fine, my two sons liked Android on the hd2 so much that we picked up 2 more hd2's, that's where the problem started. Any one of the phones can work on wireless just fine... but try and connect any of the others and while they do connect, they don't work. Any of them.
It's almost as if they are seen as the same device or something. Some kind of unique id is missing or something.
Click to expand...
Click to collapse
are they using the same builds? its possible that the mac address being used is the same and the router sees it as the same device
Richy99 said:
have you tried setting the router to use G only? i had an issue with the newer builds on a d-link 635 that was the same, it woudl work then suddenly woudnt work at all, rebooting the phone didnt help, changing the router to use G only instead of mixed seemed to fix the issue
Click to expand...
Click to collapse
Didn't help Thanks for suggestion though.
unless it has changed recently, all HD2-android builds are using the same MAC-address. So this could very well be your problem.
Ducter said:
Here's my issue. On my phone I could connect to wireless fine, my two sons liked Android on the hd2 so much that we picked up 2 more hd2's, that's where the problem started. Any one of the phones can work on wireless just fine... but try and connect any of the others and while they do connect, they don't work. Any of them.
It's almost as if they are seen as the same device or something. Some kind of unique id is missing or something.
Click to expand...
Click to collapse
FreakyFerret said:
jinhenry, I'll let you know.
Shushunmire, are you using HD2Froyo or FroyoStone (clean or Sense)? Also be sure to post in Darkstone's thread that relates to the build. I know HD2Froyo v2 was giving error for wifi, but his latest update fixes that.
Click to expand...
Click to collapse
I'm using FroyoStone (w/Sense).
And yeah, will do that. I just figured it wasn't working at all until I saw your post.
I use currently mattc 1.5b w/sense and had (have) the same problem with
DHCP is on. I allways got the status "Obtaining IP address" and nothing happen.
I played a little bit with the static IP settings...I set DNS 1 equal the the gateway entry and then wifi works....but only static.
I think this is a router issue...I use Speedport W 502V.
I doubt it's a router problem since all other devices work perfectly.
same issue, please give your attention, developers, thanks.
I've had the exact same problem with my Wi-Fi using several Android builds. Tried static IP and every possible setting I could find and solved it by add the Mac-adress in my router setting. (192.168.1.1) and now it works perfectly. I'm now using shubCRAFTv1.3
Hope you can fix your problem this way. Cheers.
Sent from my HTC HD2 using XDA App
I'm having issues with Wifi too. I'm also currently using mattc Leo + Froyo w/Sense 1.5b. My problem isn't that the phone doesn't connect via wifi... it does. The problem is that after it connects the connection seems to go dead/times out after about a minute or two.
For example, after installing the build and running through the setup, i connect to wifi, then sign in with my gmail account. This all works as it should. Then by the time I want to sign in to my facebook/twitter accounts during that same setup sequence, it no longer can connect to the internet. My suspicions of the connection having a "timing out"-like occurrence was then confirmed when I turned off wifi, and switched it back on. Everything would work and sync for about a minute, then it would cut out again (but it would still show a full strength connection via wifi). It's a bit of a strange one.
I used Energy's build before trying this one, and WiFi worked flawlessly. So I'm assuming its not my router, but something up with my device and/or its settings.
Thanks in advance for any tips/help.
snozze said:
I've had the exact same problem with my Wi-Fi using several Android builds. Tried static IP and every possible setting I could find and solved it by add the Mac-adress in my router setting. (192.168.1.1) and now it works perfectly. I'm now using shubCRAFTv1.3
Hope you can fix your problem this way. Cheers.
Click to expand...
Click to collapse
What do you mean by you added your phone's MAC address to the router? Where exactly in the router? Guessing you mean you set your phone to use a static IP, then set your router's DHCP client to always assign that IP to the phone?
wibblewobbles said:
I'm having issues with Wifi too. I'm also currently using mattc Leo + Froyo w/Sense 1.5b. My problem isn't that the phone doesn't connect via wifi... it does. The problem is that after it connects the connection seems to go dead/times out after about a minute or two.
For example, after installing the build and running through the setup, i connect to wifi, then sign in with my gmail account. This all works as it should. Then by the time I want to sign in to my facebook/twitter accounts during that same setup sequence, it no longer can connect to the internet. My suspicions of the connection having a "timing out"-like occurrence was then confirmed when I turned off wifi, and switched it back on. Everything would work and sync for about a minute, then it would cut out again (but it would still show a full strength connection via wifi). It's a bit of a strange one.
I used Energy's build before trying this one, and WiFi worked flawlessly. So I'm assuming its not my router, but something up with my device and/or its settings.
Thanks in advance for any tips/help.
Click to expand...
Click to collapse
sounds like the same issue i had, i had to set my router to use G only rather then mixed g/n to fix the issue
FreakyFerret said:
I've tried several builds:
I don't think my wired router is incompatible. I'm wondering if the wireless router not being the DHCP agent has anything to do it. Other wireless devices connect fine like this. My phone in WinMo connects fine.
Anyone have any suggestions?
Edit: It should be noted other Android phones (that came with Android) do work fine. Just these HD2 builds is the problem.
Update:
I just used an app to check IP settings. IP address, subnet mask, gateway, DNS, and everything are being set properly (there is a DHCP server on network, just not on WiFi router). I tried to setup a static IP address and other settings. Whenever I try to connect that way, it gets to "Obtaining IP address" and then fails, cycling through the whole process. Is it possible the code for IP in these builds of Android are not complete?
Click to expand...
Click to collapse
I had problems before with a similar setup, and I can tell you that NOT having the DHCP on the router (gateway out) is the issue. You have to remember that "these HD builds" are still in development with WIFI issues still being ironed out.
My advice, try using fixed IP assigning (on wireless router) using the phone's wifi adapter mac address.
Right now your phone is going to the wifi router who will be sending packets to the DHCP server and back to wifi router so that it goes out. Also usually, there tends to be a conflicts because some DHCP clients just assume that the server for DHCP is the gateway too.
or... Check that your DHCP server (if another machine) is doing internet sharing, in case devices try to use its address as a gateway, which will then go out anyway through the wifi router.
The fact you report may be in my oppinion, useful for the devs (eventually), but dont get high hopes for this to be on the immediate to-do list
My Wifi connected to my home router perfectly until I flashed the custom rom.
Now it wont work. the phone recognizes my network, then tries to connect but it pauses at the obtaining ip address bit and doesn't connect?
I tried to restart the router. It doesn't work.
I tried to reflash the rom or offical rom (KE7). It doesn't work.
I also tried to delete the file /data/misc/dhcp/dhcp_list, but there are no "dhcp_list" file inside 'dhcp'
Do anyone have another way to solve this problem?
Thanks
Could be a problem with the router, are other devices able to acquire IP addresses from it correctly?
Perhaps you should assign a static IP to see if that makes a difference.
I am on KE7 stock rom with root and had this problem too. It just started yesterday and got stuck at obtaining ip adress. So I switched WIFI off and flight mode on and after some seconds wifi on and flight mode off and it connected. I also noticed that now sometimes when it is in standby it disconnects from the wifi network (but wifi is still ON) and when I wake it up it connects to my network.
Me too, same problem.
If wifi is ruled on "sleep when screen turn off", it don't wake when screen turn on.
It stay on " searching for IP adress...".
For the moment, I'm forced to leave wifi on "never" and I use Juice defender for disabling wifi on screen off.
I really think it's a common pb with SGS 2. May be it will be fixed with 2.3.4.
Same problem. I 'fix' it by turning off wifi then turning it back on and it gets an IP address immediately.
same problem here with a dlink dir-615 router. from time to time the phone can't get an ip, and it only works if i reboot the router. didn't try with another router yet ( well, i connected to a few more but not frequent so i can see if there are problems), but i ordered a new one anyways since the dlink also crushes my battery too.
try posting the brand/model of the router you have problems with, maybe there's some specific ones that are troublesome.
d-link dir-615 here / ke7 stock - rooted
I also have a dlink router. But I get the same problem with a Belkin.
With my first SGS, no problem. I really think it's a specific issue on SGS2.
I'd read in some place that 2.3.4 will fix some wifi problem known for the moment on 2.3.3...
Let's see...
I'm seeing this with both my home router (Netgear WNDR3700) and my office router. Disabling & re-enabling WiFi on the SGS2 solves it -- fortunately, it's easily accessible on the notifications panel.
Same thing with Dlink dir 815.
Sent from my GT-I9100 using XDA Premium App
Same thing here with Draytek 2820 router, all other devices (PC's Phones, PDA's etc) have no problem. SGS2 however needs WiFi turning off when waking from sleep to get it to obtain an IP address again. However my HD2 also running Gingerbread 2.3.3 works faultlessly.
KF2 seems, for me and some others, fix the problem...
hi
lucky me, i thought im the only 1 having problem with wifi
my problem, same as the others
the wifi try to connect (obtaining IP) and then disconnected
it will scan again, same thing will happened
try with all type of protocols, wifi b,g,n wep, wpa, no passwd
results still same
try to connect wifi at my office, results also the same
im on KF1 using dlink 615
hopefully someone can help us
tq
Just got my Galaxy S2 today. Cannot connect to wifi network on G or mixed mode, with or without security - just tries to obtain an IP address. Ridiculous.
Any help ? Quick search on Google doesn't bring up too much. There does seem to be an app called "FXR Wifi" but I don't expect to use that on a brand new phone.
Update: Upgraded my router's firmware (WRT54GS) and it works !
I have the same problem with my SGS 2. I can't connect to an AP - NETGEAR DG834G.
I found a partial solution to use my phone with my AP until I solve the problem. In the Wi-Fi settings menu enter Advanced mod and set the IP address, Gateway, Netmask, DNS1 manualy (by touching <Use static IP>). If you don't know what IPs you have to set for IP address, Gateway, etc. just connect with you laptop or desktop and use the settings from your computer. Just make sure you type a different IP address in your mobile (not the one from your computer - for example in you computer you'll find something like this: 192.168.0.3, you'll have to type in your mobile something like this: 192.168.0.10). The rest of the settings have to be identical.
Good luck!
To solve this "obtaining ip address problem". Set the following manually in the advanced configuration and save it.
1. ip address(your choice).
2. subnet mask(255.255.255.0).
3. default gateway(192.168.1.1).
4. dns servers(8.8.8.8,8.8.4.4)
Note: The above given values are the most commonly used, you change it if you want so.
After entering these values manually(and correctly), it will connect to the networ in 1 or 2 seconds.
like mine SG s2, wifi connects works perfectly at home and friends place,
but stucks at obtaining ipaddress for wifi, at the mall and college, ( where it needs first login page for authentication) ( or to agree user terms and regulation),
any idea, how to fix this issue.
Thanks
mine also does this where it doesn't get an ip. Reboot your router or just disable and re-enable the access point feature on the router and it should work without having to reboot it
Sent from my GT-I9100 using Tapatalk
but at university?college or mall, we dont have access to router.
any other idea to fix this
Thanks
Hey guys! Did you find a fix for this problem? I have the same thing happening right now. I tried at different places, home and country house with Zyxel P660HN and Cisco E4200 respectively. Stuck at obtaining IP address...
XSCounter said:
Hey guys! Did you find a fix for this problem? I have the same thing happening right now. I tried at different places, home and country house with Zyxel P660HN and Cisco E4200 respectively. Stuck at obtaining IP address...
Click to expand...
Click to collapse
Search xda with 'wifi rare' and 's2 wifi not working'.. U can find few threads dealing with wifi problem..
Sent from my GT-I9100 using XDA Premium App
There appears to be a problem with new versions of Android and old routers. Many people have reported the "obtaining IP address" loop problem.
Let me explain. I use the leisure facilities in a local hotel. It has a public (open) wifi network. I believe it uses an old router. My Galaxy S2 (Gingerbread) and AsusTransformer (ICS) both connected to this network without problems. I recently replaced the S2 with an S3 (ICS) and my Transformer with a Nexus 7 (Jellybean). Neither of my new devices connect to this network. I have had the same problem in a local cafe.
I have researched this problem. It is not uncommon. It appears to be caused by an odd mix of hardware (router and wifi chipset) and software (later versions of Android). If you are unlucky (like me and some others) you will be unable to connect to some networks.
The solution is to use static IP addressing (since your device is unable to obtain a dynamic IP address). This will allow your device to connect to the network -- but you need to know the correct settings (for static IP addressing) before you can actually use the network.
This problem has been reported by many people. Does anyone know if there is a fix or a workaround?
The only one I can think of it to get hold of a device that does connect to this network and copy the (static IP) settings. But this would only solve it for one location meaning that I will run into it again the next time I try to connect to a network with old hardware.
Sometimes when I get that problem it's due to IP address conflicts on the Windows 7 computers.
I go to the computer and:
http://helpdeskgeek.com/networking/release-and-renew-an-ip-address/
Otherwise I just pull the router out and refresh it, should work for another few weeks or so.
Asovse1 said:
Sometimes when I get that problem it's due to IP address conflicts on the Windows 7 computers.
I go to the computer and:
http://helpdeskgeek.com/networking/release-and-renew-an-ip-address/
Otherwise I just pull the router out and refresh it, should work for another few weeks or so.
Click to expand...
Click to collapse
I don't have access to the PC. It is owned by the hotel. I need a solution that I can apply client (Nexus) side.
Solution
I found a solution. I asked the guy to reset the router and both my Nexus and S3 immediately connected. Someone advised me to do this. I have no idea why it worked. Not really a solution since i cant go round cafes asking people to reset their routers for me.
Is there a way to find out IP, DNS, gateway etc values on Nexus when they are dynamically assigned?
I sometimes have this Problem when starting my accesspoint after enabeling wifi on my N7.
I have to reboot my N7 in that case to get an IP.
Happened to me quite a few times when I went out with it to a restaurant or something. It just loops and loops.
My Nexus (and S3) now connect to the hotel network every time now. So it looks like you only need to ask the owned to reset his router once.
Embraced with this problem
bobbyelliott said:
My Nexus (and S3) now connect to the hotel network every time now. So it looks like you only need to ask the owned to reset his router once.
Click to expand...
Click to collapse
Resetting the modem solves the problem if you don't make any change to the router settings. I don't understand why the hell google is not solving the problem yet...
many users are found to face the same problem..
eve I can connect with my Nokia E72 but not with my N7...
I can get the IP from my cell phone. But come on, what's the point of doing so?? Are you gonna assign the IP for each and every WiFi you connect?? Or if the IP changes everyday??
Static ip won't help, yes you can connect to wifi, but cannot get connection to internet. This is a bug of android, and ITs in Princeton univ. had some investigation. 412 should have fixed it
Sent from my HTC Z710e using xda premium
gcd0318 said:
Static ip won't help, yes you can connect to wifi, but cannot get connection to internet. This is a bug of android, and ITs in Princeton univ. had some investigation. 412 should have fixed it
Sent from my HTC Z710e using xda premium
Click to expand...
Click to collapse
no. The same problem with 4.2.1 on my N7. God,this is really pissing me off !
EDIT: Finally found a solution . Thank god!!
TheDarkDefender said:
no. The same problem with 4.2.1 on my N7. God,this is really pissing me off !
EDIT: Finally found a solution . Thank god!!
Click to expand...
Click to collapse
What was the solution?
bobbyelliott said:
Is there a way to find out IP, DNS, gateway etc values on Nexus when they are dynamically assigned?
Click to expand...
Click to collapse
For a simple display of the values look at something like Network Signal Info of Wifi Analyser (both free)
jet1000 said:
What was the solution?
Click to expand...
Click to collapse
Use a static IP .
Sent from my Nexus 7 using xda app-developers app
You can only get internet access when you'll be using the correct IP, DNS etc. So try to find out what is the working IP setting...
Sent from my Nexus 7 using xda app-developers app
Deleted
I just started having a similar problem. I have a samsung galaxy tab with Sprint. I've had it for a year and this is the first time I've had this trouble.
The only difference is, I cannot connect to any wifi network at all. It keeps hanging on "obtaining IP address" and then disconnects. It doesn't matter if it's my home wifi or school or free wifi in a restaurant.
The only possible connection I can make is that I downloaded Lookout to check it out as a possible security app, I have since uninstalled it but that did not fix my problem.
Continuing to research this but any ideas on how to fix this would be fantastic.
I'm having this problem on my HTC One S. It happened yesterday without warning and it's really annoying. I went to a nearby cafe and the wifi worked perfectly, so it's something wrong here.
Static IP solution connects to me to the network but I can't actually use the internet, so I'm stumped.
i'm getting the same error with AOKP 4.2.2, and also know people with stock 4.2.2 with it.
the only way i found to fix it is to reboot the phone..... and wait for it to happen again and reboot it again
i cannot use static IP since in my university (and some other public places) it is not possible to connect it like that :S
TheDarkDefender said:
no. The same problem with 4.2.1 on my N7. God,this is really pissing me off !
EDIT: Finally found a solution . Thank god!!
Click to expand...
Click to collapse
How did you solve this? I Need help with my tf 300
bobbyelliott said:
There appears to be a problem with new versions of Android and old routers. Many people have reported the "obtaining IP address" loop problem.
Let me explain. I use the leisure facilities in a local hotel. It has a public (open) wifi network. I believe it uses an old router. My Galaxy S2 (Gingerbread) and AsusTransformer (ICS) both connected to this network without problems. I recently replaced the S2 with an S3 (ICS) and my Transformer with a Nexus 7 (Jellybean). Neither of my new devices connect to this network. I have had the same problem in a local cafe.
I have researched this problem. It is not uncommon. It appears to be caused by an odd mix of hardware (router and wifi chipset) and software (later versions of Android). If you are unlucky (like me and some others) you will be unable to connect to some networks.
The solution is to use static IP addressing (since your device is unable to obtain a dynamic IP address). This will allow your device to connect to the network -- but you need to know the correct settings (for static IP addressing) before you can actually use the network.
This problem has been reported by many people. Does anyone know if there is a fix or a workaround?
The only one I can think of it to get hold of a device that does connect to this network and copy the (static IP) settings. But this would only solve it for one location meaning that I will run into it again the next time I try to connect to a network with old hardware.
Click to expand...
Click to collapse
Note: You Must have root.
Go to
/data/misc/dhcp/
and delete all 3 / 4 files there.
And voila it should work.