Related
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
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).
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.
I just bought a nexus 7, came home and spent 3 hours trying to connect this to wifi and it doesn't work... meanwhile i have 9 devices connected wireless that never had problems... -_-
when i first start my NEW nexus 7 and get to select wifi page.. i select my wifi (which shows 3 bars) i enter my correct password and it just loops from "connecting.." to "obtaining ip address" over and over after hour of that i got fed up and tried connecting manually .. i tried using ip/dns from ipconfig in cmd didn't work.. i went to my iphone and copied the wifi adress settings to my nexus 7 and it said connected
but when i went to next i logged into my gmail account and i get this
"Couldn't sign in
Can't establish reliable connection to the server.
This could be a temporary problem. Try again or connect to another Wi-Fi network."
i have no idea what to do ARGGGG HELP PLZ!
MxZeal said:
I just bought a nexus 7, came home and spent 3 hours trying to connect this to wifi and it doesn't work... meanwhile i have 9 devices connected wireless that never had problems... -_-
when i first start my NEW nexus 7 and get to select wifi page.. i select my wifi (which shows 3 bars) i enter my correct password and it just loops from "connecting.." to "obtaining ip address" over and over after hour of that i got fed up and tried connecting manually .. i tried using ip/dns from ipconfig in cmd didn't work.. i went to my iphone and copied the wifi adress settings to my nexus 7 and it said connected
but when i went to next i logged into my gmail account and i get this
"Couldn't sign in
Can't establish reliable connection to the server.
This could be a temporary problem. Try again or connect to another Wi-Fi network."
i have no idea what to do ARGGGG HELP PLZ!
Click to expand...
Click to collapse
Expected it is not any Hardware issue, it seems your pb is related to your PW. try desabling it from your router (just a short time for test) or go to a free wifi place to check.
Also keyboard issue, do you use the standard one?
good luck
lolo9393 said:
Expected it is not any Hardware issue, it seems your pb is related to your PW. try desabling it from your router (just a short time for test) or go to a free wifi place to check.
Also keyboard issue, do you use the standard one?
good luck
Click to expand...
Click to collapse
Had this issue before with a bunch of Samsung phones turns out I had so many devices trying to use the same IP address set up by my router. I had to reset my router and assign each device its own IP address.
Sent from my Nexus 7 using xda premium
May also need to check the routers settings for maximum allowed wireless devices, or maximum dhcp users.
Sent from my Nexus 7 using xda premium
The obvious thing in your router configuration is that connections are being restricted to a list of hardware mac addresses.
peterk-1 said:
The obvious thing in your router configuration is that connections are being restricted to a list of hardware mac addresses.
Click to expand...
Click to collapse
The obvious is that jour Nexus 7 is not working properly, I had exactly the same behaviour tested many changes on my wifi settings, teathering from my phone...=> went back to the shop for an exchange and the new one was working perfectly
Guys, recently bought a Nexus 4 and it normally connects via wifi but can not connect.
I was using the Android 4.2.2 OTA updated to Android 4.3 and the problem persists.
The Nexus 4 connects normally, but the icons of wifi connection and carrier signal are gray instead of blue and even trying to install applications via Google Play or simply access a site via browser do not work and accuse the connection fails.
I was tested and the router's signal is good and other equipment that I usually work (other Android smartphones and notebook).
My router is standard G and I use WPA2.
viamais.net said:
Guys, recently bought a Nexus 4 and it normally connects via wifi but can not connect.
I was using the Android 4.2.2 OTA updated to Android 4.3 and the problem persists.
The Nexus 4 connects normally, but the icons of wifi connection and carrier signal are gray instead of blue and even trying to install applications via Google Play or simply access a site via browser do not work and accuse the connection fails.
I was tested and the router's signal is good and other equipment that I usually work (other Android smartphones and notebook).
My router is standard G and I use WPA2.
Click to expand...
Click to collapse
all routers?
i got the same issue but only on a particular router at home but worked perfectly elsewhere
i ended up changing the router
csara said:
all routers?
i got the same issue but only on a particular router at home but worked perfectly elsewhere
i ended up changing the router
Click to expand...
Click to collapse
Oddly enough, I have the Nexus just 3 days and only had access to the router so far from home, but today I'll look for a router to test the public.
But either way it's frustrating the Nexus 4 have these compatibility issues when connecting to a wifi router.
Before making the switch router, is it not possible to find out which configuration of WLAN could cause this? Does Google do not have this documented?
i feel your pain, been there
it could be your router, from the way it assigns ip addresses to your type of encryption. by any chance is it a linksys G router? that was my problem before until i just decided to get an N router.
did you try switching to WEP or open to see if the problem persists? or changing your gateway ip address? or changing which ch your wifi is on?
never hurts to try
Should factory reset your router and upgrade firmware first, then immediately connect to it without encryption and see if it work.