Database Users

X10 & Netgear DG834v5 Wifi Connection Problems - Solution

Hello all,
I love my X10, but the frustration with getting it to connect to my Netgear DG834 router was getting to me, so I dedicated an afternoon to working out a solution and I've found one that works for me, so I hope it'll work for you too.
Summary of problem
--------------------
The phone will connect to the Router once, and once only. Any attempt to re-connect to the wifi will result in the phone disconnecting, scanning again, then discinnecting until the user gives up. Nothing will cause the phone to reconnect (telling it to forget the connection for example). The only surefire way to reconnect is to reboot the router each time - not ideal.
Manually adding a Static IP also doesn't work - which is weird as that is how I've solved it, see below.
Scale of problem
----------------
The problem seems to be with the router and not necessarily the phone as it appears to be on a wide range of phones (Hero, Droid, Touch HD etc.). Seeing at the DG834 is the most popular router in the world, and Android is growing all the time, there are a large number of people affected.
However Iphone and Symbian phones appear to be unaffected.
Reason for the problem
-----------------------
Currently unknown, but appears to be something to do with the handshaking procedure when a device asks the router for an address (DHCP) - though as to what I don't know.
Solution
--------
1) Download an app called WiFiStatic from the App Market. WiFiStatic takes each DHCP assigned IP address and stores it in a small database to be re-applied whenever you are back in range of the same Router again. It is not an ideal solution as you may have to re-scan and re-assign if you visit a busy hotspot, but this is a two press function, so it's not that onerous.
2) Turn off your Router. Make sure the WiFi on your phone is off too.
3) With the router off, clear your Remembered WiFi connections (or at the very least the Netgear connection). Once that's done, turn the Router on again and wait until it is full back up again.
4) When the Router is fully operational again, turn on your wifi on the phone and let is scan for and connect to the Netgear Router. You may need to tell it to connect from the Wireless Settings menu on the phone.
5) The phone should now connect to the Router successfully. If it doesn't, repeat the above procedure.
6) With the phone connected to the router, fire up WiFiStatic. Check Auto Switch and Show Visual Prompt if they are not already selected, then Tap Add configuration at the bottom of the screen.
7) The IP address and other settings assigned by your router should be displayed at the top of the screen, at the bottom should be the name of your router and its MAC address. If not then tap Menu > Generate to populate the form.
8)Tap Menu > Done when everything is ok.
That's it. Now when you move into range of your Netgear, you should get connected, though it does take a bit longer than normal (the Router still wants to assign an address first before accepting the static IP). You can speed this up by changing the Device table on the router to always keep the Phone's static IP open.
This shouldn't work as all my other attempts with Static IP failed, but I've had five days now of instant connection to WiFi at home, so something has been freed up.

i can not tell you how seeing this post was like finding bin ladin in the white house. Prob would have found him twice trying to solve this WIFI problem. And the strange thing is this is the 1st phone i have had that there are so few posts about it...is everyone on that icrack? scary. cheers to you...

Thank you for posting this.
I tried this with my and it seems it doesn't make a difference for me. I still can only connect once to the router and for me to connect again i have to restart the router again. Am i missing something?
Problem is when I connect for the first time at home it works then when i leave to the office i use the wifi there and never have any problems there but when i get back home it doesn't work. Do you guys switch the wifi off manually when you are not using it?

one thing that is almost always overlooked is updating the router's firmware. this usually solves a number of issues. I dont know about netgear but it's worth a try to update

bimmerboii said:
one thing that is almost always overlooked is updating the router's firmware. this usually solves a number of issues. I dont know about netgear but it's worth a try to update
Click to expand...
Click to collapse
That was one of the first thing i tried....it seems i have the latest firmware.

Is this an issue for a lot of people then? Ive one of these routers and never had an issue connecting any phones to it. Had 3 nokias and 3 different android phones, currently on the x10, and they all connected fine everytime.

i have some troubles in x10i wifi connection and holp someone helps me~
------------------------------
im chinese, my x10i have had the lastest firmware but the phone cant connect the AP which set the channel is "13". but i used it long before and suddy just one day i find it dosnt work~ it cant scan(and find) the AP anymore !
then i have tried and config the router in another wifi channel(just like 1,8,11..) and the phone can scan and refind the AP.
i have tried to reload the phone's default setting,but it dont work(in channel 13)ToT
---------------------------
someone tell me why? and someone give me some suggest?
in china , lots of router's wifi channel are using "13" by default(factory setting);so, if my x10i cant works in that channel means i couldnt find the "opend APs" which in the public place(like KFC~~)
THX to help~

StampedChipmunk said:
Hello all,
I love my X10, but the frustration with getting it to connect to my Netgear DG834 router was getting to me, so I dedicated an afternoon to working out a solution and I've found one that works for me, so I hope it'll work for you too.
<snip>.
Click to expand...
Click to collapse
Thank you! I have spent three days trying to get my phone to re-connect to a DG834v5.
Your solution has worked! I had gone as far as reserving an IP address on the router and linked it to the MAC of the phone... no dice. The phone would connect once and then never again until the router was reset. Really irritating because I have two PPPoe connections running through the router with a routing table that has to be re-loaded via telnet every time the router is reset. I was considering a new phone or a new router.

HI,
I have near the same problem.
But I found out that when I remove on the access point the hidden function ( SID ) then it works perfect.
so that is a bug in the ROM of the X10, I have the R2b026.
At the moment everone can see my Access Point but I can live with that solution.

Worked for me! Many many thanks this had been infuriating me...

Same problem here - never had an issue with any other router, so I blame Netgear...
Let's just hope this works - it's been driving me crazy for the past 5 days...

Neh, hasn't worked for me....
Stupid freakin' Netgear...

works on the HD2 aswell. Thanks alot!

Not just Netgear, maybe Android
k1sr said:
Same problem here - never had an issue with any other router, so I blame Netgear...
Let's just hope this works - it's been driving me crazy for the past 5 days...
Click to expand...
Click to collapse
I am having the same issue on my HD2 Android 2.3.4, connecting to a D-Link DIR-635. If I use Static IP, everything is fine...

WORKS! I can't believe it, finally i can disconnect and connect without having to reset my router everytime. BIG thanks man!

alright, it worked fine for the first 5-6 hours. then it went back to not connecting without rebooting the router. this problem happens only with my home router, at work i can connect fine, as well as in other places.
any thoughts or solutions? i mean it did work in the beginning, then why did it stop? shall i change my router?
P.S.: i noticed that every time i connect to my home router i get the same IP address and all the stats are the same.

Captivate & 802.1x

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.

Wifi obtaining ip address....

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Bump.

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

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

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

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

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

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

Nexus 4 Wifi Issues - connects to router but no internet

Just want to know who else on XDA has a similar problem to me on the Nexus 4.
Recently moved country and took my Nexus 4 with me, got a data plan, no problems there. I was also was given the stock router for my ISP (Movistar) when taking out my broadband contract and my Nexus 4 is the only device that won't connect to wifi.
So here's what happens:
1) Network can be seen on the Android 4.2.2 Wifi Settings
2) I can connect, either by WPS or by entering the password, and Nexus 4 shows connected with indicator
3) Indicator instead of being the standard blue is grey, which seems to be no internet connection. I can get some access but at very, very slow speeds (about 9kbps)
The Nexus 4 is the only device in my house with the issue, no problems on PCs, iPads, etc.
Google have acknowledged this is a bug and there is a fix which involves root, but I don't want to root at the moment. Google also say it'll be fixed in the next update, but they've said that and we've seen 4.2.1 and 4.2.2 come out in the meantime.
Google Support also sent me a rubbish response to my questions about when it'll be fixed, telling me what Wifi is and how to turn it on and off..
So just want to know, are you having the similar issues with certain routers on 4.2.2 (stock)? I know I'm not the only one but I couldn't find any other threads.
Thanks!

I started having this same issue man! care to show me whats the root needing fix?

Brokenme23 said:
I started having this same issue man! care to show me whats the root needing fix?
Click to expand...
Click to collapse
There are a lot of fixes in the Android Development Section.

Typically this can be a DNS problem if your router is not correctly set up to relay DNS requests (windows/OSX tends to be a lil smarter about it if it can't get the appropriate response from the router).
You could try to set a DNS yourself such as google's public ( 8.8.4.4 and 8.8.8.8 ) in the advanced properties when you long press the SSID you're connected to and see if that allows for internet access. If it does, then maybe you just need to log into your router and correct the DNS info.

Thanks for the responses guys
kbeezie said:
Typically this can be a DNS problem if your router is not correctly set up to relay DNS requests (windows/OSX tends to be a lil smarter about it if it can't get the appropriate response from the router).
You could try to set a DNS yourself such as google's public ( 8.8.4.4 and 8.8.8.8 ) in the advanced properties when you long press the SSID you're connected to and see if that allows for internet access. If it does, then maybe you just need to log into your router and correct the DNS info.
Click to expand...
Click to collapse
Tried that I'm afraid :/ No luck. According to Google it is the fact "they have no drivers for that router" considering they will probably have a generic driver for the average user to connect whatever the router.
Sadly I've had to practically try everything to get it to work. Thanks so much for your response though!
Brokenme23 said:
I started having this same issue man! care to show me whats the root needing fix?
Click to expand...
Click to collapse
Hi! It's an annoying issue, I'm currently tethering through Mac to get it to work. The root fix does work but drains battery life a lot more (instead of 0.5% per hour drain it's 5%). If you want to look I'll pass the link, but wouldn't recommend it.
Thanks!

carmichaelalonso said:
Thanks for the responses guys
Tried that I'm afraid :/ No luck. According to Google it is the fact "they have no drivers for that router" considering they will probably have a generic driver for the average user to connect whatever the router.
Sadly I've had to practically try everything to get it to work. Thanks so much for your response though!
Hi! It's an annoying issue, I'm currently tethering through Mac to get it to work. The root fix does work but drains battery life a lot more (instead of 0.5% per hour drain it's 5%). If you want to look I'll pass the link, but wouldn't recommend it.
Thanks!
Click to expand...
Click to collapse
See if you're able to do a traceroute from within android when connect to the router to see where it's failing.

Mine got fixed by changing the routers channel, weird cos' no other thing connected had a problem, not even my sister's nexus 4
Sent from my Nexus 4 using xda app-developers app

kbeezie said:
See if you're able to do a traceroute from within android when connect to the router to see where it's failing.
Click to expand...
Click to collapse
Hi, tried this and have no problems. The only issue is it takes too long to complete, which is the 9kbps download issue I was having. I'll attach a screenshot of the traceroute if needed. Thanks for the reply, much appreciated!
And about changing routers, not possible at the moment. I've just moved abroad and have my old router somewhere too hard to find. Google are no help with this which is the problem, but if it persists in the next update I'll get a new router whatever the case.
It's strange since my iPad and all my other devices work with no problems!
Good luck, hope yours works now!
Sent from my Nexus 4 using xda app-developers app

my friend's phone also has this problem....

policeman0077 said:
my friend's phone also has this problem....
Click to expand...
Click to collapse
Yep it's a common problem I'm afraid which is obsolete in the eyes of Google and not a device defect...
Just to get an idea, what router models are you using? I'm on Movistar's stock router - ASL-2665 - common issue with this router. I've also heard big brand routers having similar problems, anyone got any problems with a particular router?

kbeezie said:
Typically this can be a DNS problem if your router is not correctly set up to relay DNS requests (windows/OSX tends to be a lil smarter about it if it can't get the appropriate response from the router).
You could try to set a DNS yourself such as google's public ( 8.8.4.4 and 8.8.8.8 ) in the advanced properties when you long press the SSID you're connected to and see if that allows for internet access. If it does, then maybe you just need to log into your router and correct the DNS info.
Click to expand...
Click to collapse
Brokenme23 said:
I started having this same issue man! care to show me whats the root needing fix?
Click to expand...
Click to collapse
I've been looking a bit lately and I've found this flashable fix if you're rooted, take a look and let me know how it goes!
http://techmell.net/android-tips/fix-wifi-issue-40065-nexus-4-7-android/
I've bought a wifi extender to fix this today, I'll see how this goes and may have to be the non-root fix...

I am very close to buying the Nexus 4 for my wife. If this WiFi issue intermittent or consistent?
-T

T-BoneFL said:
I am very close to buying the Nexus 4 for my wife. If this WiFi issue intermittent or consistent?
-T
Click to expand...
Click to collapse
The Nexus is a great phone, just a few odd issues which hopefully will be fixed.
This issue is persistent but dependant on the router. For example, my extender works perfectly whilst the main router doesn't - let me know what your router model is and I'll check to see if this will be common for your router
Sent from my Nexus 4 using xda app-developers app

carmichaelalonso said:
The Nexus is a great phone, just a few odd issues which hopefully will be fixed.
This issue is persistent but dependant on the router. For example, my extender works perfectly whilst the main router doesn't - let me know what your router model is and I'll check to see if this will be common for your router
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks!
I have the "BUFFALO AirStation HighPower N600 Gigabit Dual Band Wireless Router WZR-600DHP"
-T

T-BoneFL said:
Thanks!
I have the "BUFFALO AirStation HighPower N600 Gigabit Dual Band Wireless Router WZR-600DHP"
-T
Click to expand...
Click to collapse
Hi!
Taken a quick look and doesn't seem to be any problems with your router. What you can do is to purchase the device and test to see it works on WiFi.
If it works, you're good to go!
If not, try some troubleshooting, so change channels, IP address, or even just a reset of the router could work.
Still not working? You can try what I did and buy an extender, but that'll set you back a bit of money.
You could wait until this is fixed, which we don't know when yet, or if you can't fix it you have a return period on which you should get a refund from Google.
Let me know what you decide to do, personally I'd try it out since it's likely to work, but I would return if not. But the Nexus 4 is a great overall device for the price.
Hope this helps!
Sent from my Nexus 4 using xda app-developers app

OP, have you checked to see if this is an issue with the wifi access point of your router, or actually a routing issue?
To do this, set up ftp services on your computer or phone and login from the other device and copy a file from one to the other. If the bandwidth is good, your problem isn't with wifi but rather a routing issue that can likely be addressed in its settings.

Solutions Etcetera said:
OP, have you checked to see if this is an issue with the wifi access point of your router, or actually a routing issue?
To do this, set up ftp services on your computer or phone and login from the other device and copy a file from one to the other. If the bandwidth is good, your problem isn't with wifi but rather a routing issue that can likely be addressed in its settings.
Click to expand...
Click to collapse
Thanks for your reply!
I'm about certain this is to do with the router itself and not a routing issue, this is a common nexus4-my router problem and various other models.
I've adjusted every setting possible in the router settings to no avail, and all of my other devices which include other android devices work perfectly.
Sadly it seems to lie with a Qualcomm driver from what I've seen, and hopefully Google can fix in the next update
Sent from my Nexus 4 using xda app-developers app

If you don't bother to check if you have good throughput over your LAN, you'll never know whether this is a wifi issue or a routing issue.
Drivers talk to hardware, i.e. Your wifi chip. That is all local, and has nothing to do with the routing (Internet) part of your router. Without knowing where the actual issue lies, you're just guessing if a new wifi driver will help.

Solutions Etcetera said:
If you don't bother to check if you have good throughput over your LAN, you'll never know whether this is a wifi issue or a routing issue.
Drivers talk to hardware, i.e. Your wifi chip. That is all local, and has nothing to do with the routing (Internet) part of your router. Without knowing where the actual issue lies, you're just guessing if a new wifi driver will help.
Click to expand...
Click to collapse
Sorry, you seem to have misunderstood me and you're obviously making the assumption that I haven't already checked for routing issues.
As I said, my Nexus 4 is the only device in my house with this problem, all others work perfectly. From what I've gathered from these issues, it lies within the drivers of the phone.
WiFi works perfectly on every other router I've used with my N4, it's only my home router with the problem. It's a Movistar default router and other users have the same problems with this router (the brand is fairly unknown).
And I'm definitely not guessing that it's a driver issue - I've had this problem for over a month, I've tried everything I can: changing router settings, resetting, etc. So I doubt this is a routing issue but more an issue with the device, and from what I've read on other forums, this could be down to a Qualcomm driver issue.
Thanks for your help anyway!
Sent from my Nexus 4 using xda app-developers app

I am not assuming anything. Simple troubleshooting 101. You're not getting a decent Internet connection. Could be wifi or router. I merely offered a simple method for determining which one.
Don't know who you spoke with at Google, but first couple of support levels don't have the stones to try and solve these things. And while I have no doubt other folks with the same setup are also experiencing this issue and that Google has recorded this info, that doesn't mean that a workaround is impossible.