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.
Related
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.
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.
First - Hi all, long time reader but this is the first time I've needed to start a thread - so sorry about my first post being a problem/Q!
I've not had my Nexus 4 long, but have got some pretty annoying Wi-Fi issues. I've searched for answers but it seems that people have different Wi-Fi problems and I just wanted to see whether my issue was a common one and, if so, is there a fix on the horizon?
My issue is that I can connect to some routers but not to others (work, home, most open networks)... when I connect it simply says "saved, secured with WPA/WPA2" but wont then connect.
Phones running stock 4.2.1 with franco kernel r28 and the things I have tried are:
Resetting routers
Assigning static IP address
Wi-Fi direct from my Nexus 7
Cleared cache from recovery
changed the Wi-Fi band from 'Auto' to 2.4Ghz and 5Ghz
Flashed new kernel
Very frustrating and because of my signal the lack of Wi-Fi has made me go back to my old phone while I wait for a fix... which connects perfectly to the networks (S3 running CM 10.1)
Is this a 4.2.1 issue - as seems to be the consensus with other Wi-Fi issues or possibly a hardware issue?
Thanks for any info!
There's one fix you've not tried which might work for you (it didn't for me). You would have to be rooted though, which is going to system/etc/dhcpcd and changing the permission on dhcpcd-run-hooks to read and execute from "others". This help some people out but turns out for me that my router isn't compatible with my phone. (DSL-2780).
I've noticed that some of the mobile devices(eg iPhone 3gs, SGS2) are quite sensitive to wireless channel which your router/ap broadcast on.
Try manually switch to channel 6 or 8 that solved my issue - I don't believe in incompatible routers usually problems are related to config.
It is more complicated with an access to the public WiFi as you can not modify the setup.
Sent from my Nexus 4 using xda app-developers app
paulrawr said:
There's one fix you've not tried which might work for you (it didn't for me). You would have to be rooted though, which is going to system/etc/dhcpcd and changing the permission on dhcpcd-run-hooks to read and execute from "others". This help some people out but turns out for me that my router isn't compatible with my phone. (DSL-2780).
Click to expand...
Click to collapse
Ok, thanks for this I will give it a go and let you know.
sirbagin said:
I've noticed that some of the mobile devices(eg iPhone 3gs, SGS2) are quite sensitive to wireless channel which your router/ap broadcast on.
Try manually switch to channel 6 or 8 that solved my issue - I don't believe in incompatible routers usually problems are related to config.
It is more complicated with an access to the public WiFi as you can not modify the setup.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have tried this on the routers which I am able to change the channel of and it didn't change anything.
paulrawr said:
There's one fix you've not tried which might work for you (it didn't for me). You would have to be rooted though, which is going to system/etc/dhcpcd and changing the permission on dhcpcd-run-hooks to read and execute from "others". This help some people out but turns out for me that my router isn't compatible with my phone. (DSL-2780).
Click to expand...
Click to collapse
Just to update.
I've now tried this and still can't connect to the affected Wi-Fi networks, probably going to have to wait for 4.2.2 to see if that fixes it...
I had troubles connecting to my wifi network here in my house, which worked pretty good with my galaxy nexus, what i did and worked was deactivating the option "avoid poor connections" in wifi advanced settings, you should give this a try
Fixed it for me
Chad_Petree said:
I had troubles connecting to my wifi network here in my house, which worked pretty good with my galaxy nexus, what i did and worked was deactivating the option "avoid poor connections" in wifi advanced settings, you should give this a try
Click to expand...
Click to collapse
Thanks Chad, it was driving me crazy the constant data drops I had when trying to listen to streamed audio in XiiaLive Pro. Which worked flawlessly with my old HTC Desire.
Did as you said, and perfect now.
sandozer said:
Thanks Chad, it was driving me crazy the constant data drops I had when trying to listen to streamed audio in XiiaLive Pro. Which worked flawlessly with my old HTC Desire.
Did as you said, and perfect now.
Click to expand...
Click to collapse
Glad I could help
Sent from my Nexus 4 using Tapatalk 2
I too have wifi issues with my N4. We have several phones at home - an HTC Aria and believe it or not the SGS1, SGS2 and SGS3!
All of them connect with no problems. My brand new N4 will see the router but refuses to connect until I toggle wifi on/of serveral times in succession, sometimes 6-8 times!
I have avoid poor wifi disabled but it does not help
I really hope El Goog fixes this asap as it is very frustrating.
I've had this issue forever. Android phones hate low or overcrowded signal. Though my nexus 7 always works fine. Makes me think it is the lack of WiFi antenna strength
Sent from my Nexus 4 using xda premium
Its a 4.2.1 issue
http://androidheadlines.com/2013/02/nexus-users-reporting-wifi-problems-on-android-4-2.html
NeXus⁴ using XDA Premium
Nope, i have a 4.2.2 and its same think
i have a problem in my nexus 4 wifi ... it don't connect automatically to wifi network ,, i have to turn wifi off and turn it on to connect !!! any solution ??
This issue has been posted several times. I have searched most threads but didnt get right answer. I have a Samsung Galaxy S2 and Google nexus 7. I could connect both at home and at work to wifi and then to network. But for the last 1 week I am unable to connect to internet at home. There isnt such problem with laptop and Ipad at home. I had this problem with my galaxy s2 in the past, when it was only android device at home. I didnt give much attention at that time as it used to sort itself on its own. I mean to say though the network connectivity behaviour is erratic it didnt bother me much as I have other devices to use to connect to internet. I am posting this now to highlight this problem with android and some great soul will sort this out forever. I dont think it is a problem with router as this happened to several people with different brands of routers. As suggested by somebody, I have tried the Wifi fixer app, with no success. My galaxy S2 is not modified, but nexus 7 is rooted.
I had the same problem. I fixed it by setting my router to only do B/G instead of B/G/N. This means I can only get max 54kps, but so what. I was only getting a bit better than that before.
Hope this helps!
Sent from my HTC One S using xda app-developers app
sripos said:
I dont think it is a problem with router as this happened to several people with different brands of routers.
Click to expand...
Click to collapse
It takes two to Tango.
I had the symptom you describe on a 3 year old Android phone, while with the same router, no problem with Macs, Windows PCs, and iPod Touch devices. The Android phone could associate and authenticate ("connect") to the router, but it would never get an IP address via DHCP.
What was the solution? I updated (flashed) new firmware to the router.
Interop problems happen all the time with WiFi gear; it's unfortunate but true. I mention the above example because the symptoms seemed to point to the Android device as being the "trouble", and yet the fix involved changing software on the router side of things. And that's entirely the point - when bugs occur, they occur between TWO software stacks. Router firmware can have "latent" bugs that require client devices to deviate just a little bit before they occur, and the same thing is also true with the software stack on the Android device.
In general, you have more knobs to fiddle with on the router than you will have on the Android phone/tablet, and the more variable the behavior of the router is, the more likely bug expression between the two software/hardware stacks becomes. So - as with the suggestion of the above respondent - if you want to experiment, try turning off non-essential features on the router such as multiband, proprietary channel bonding or "turbo" modes, beacon suppression, etc. Simplify things and see if the problem disappears.
good luck
thank you
steve1326 said:
I had the same problem. I fixed it by setting my router to only do B/G instead of B/G/N. This means I can only get max 54kps, but so what. I was only getting a bit better than that before.
Hope this helps!
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Thank you, I will try this.
Hello all,
I just recently upgraded from a GS6 Edge + using JoD, and admit I'm loving this phone. However, I'm experiencing a weird issue that (I believe) relates to my home network.
Here is what happens: I successfully connect to my network and all seems well. I have Internet with full bars. I can browse and watch videos with no issues. But when I go to the Play store, I cannot download any apps. They just say “downloading” and never actually initiate the download.
My temporary workaround that I've found to work is to disconnect and reconnect to my network, and I'm able to get 1 or 2 downloads before I experience the issue again.
If anyone has any ideas on a permanent solution, please let me know. Or if you need more information to help.
Thanks in advance!
Sent from my SM-G935T using Tapatalk
I've experienced the same issue you're having on my office Wifi. The strange thing is when I connect to the office guest network, all is well. I'm also not able to download any photos from Google Photos so not sure if it's a google DNS thing or what. No issues on my home Wifi either.
wpbcubsfan said:
I've experienced the same issue you're having on my office Wifi. The strange thing is when I connect to the office guest network, all is well. I'm also not able to download any photos from Google Photos so not sure if it's a google DNS thing or what. No issues on my home Wifi either.
Click to expand...
Click to collapse
Ok, I'm glad to hear I'm not alone (despite issue being bad). I think it might be a Google thing, because I've also found that I can't setup Google accounts on the WiFi because it just hangs on the log in and never actually logs in. I can switch to data and all is well.
I've also been on a different network that worked with no issues, similar to your case with the guest network. Seems to be something with a very specific type of network...
Sent from my SM-G935T using Tapatalk
There's definitely some WiFi issues with the phone. I use WiFi Calling at the office and if I get out of range from the router in my office, it will not reconnect until I turn the screen on and unlock the phone.
Same here wifi is fine except with downloading from play store
I've had some WiFi issues as well. Sometimes, I'll have a full WiFi signal yet I lose all connection on my phone. I know my WiFi still works because I can access it from the computer or a Tablet. The only way to get the WiFi on the GS7 working again is by turning it off and back on.
I've noticed this too, but it seems to kill all internet and i have to cycle it..also I've noticed WiFi off several times
Sent from my SM-G935T using Tapatalk
Ok guys, I'm hoping it's just a software issue with Samsung's Marshmallow that will be fixed soon. It's a shame considering the phone is so great in other aspects.
Sent from my SM-G935T using Tapatalk
I think I fixed the issue by using google dns, but I actually did more than that. I reconfigured my home network to use on asus router instead of the old motorola from att which cannot set dns and handle heavy traffic
Sent from my SM-G935T using Tapatalk
cruel91 said:
I think I fixed the issue by using google dns, but I actually did more than that. I reconfigured my home network to use on asus router instead of the old motorola from att which cannot set dns and handle heavy traffic
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
I'm glad that worked for you. On my end, setting the DNS to standard Google 8.8.8.8 and 8.8.8.4 don't fix the issue. I don't think my router is to blame as it's a fairly new Linksys and all the settings seem to be set up properly as I've never had the issue before this phone. I might need to tinker more though.
Sent from my SM-G935T using Tapatalk
TheShoxter said:
I'm glad that worked for you. On my end, setting the DNS to standard Google 8.8.8.8 and 8.8.8.4 don't fix the issue. I don't think my router is to blame as it's a fairly new Linksys and all the settings seem to be set up properly as I've never had the issue before this phone. I might need to tinker more though.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
I've got an older Linksys N dual band at the office, upgraded to run DDWRT, and a Netgear AC router at home. I can reproduce the issue both places, so I'm confident it's an issue with software that T-Mobile/Samsung need to address.
NotATreoFan said:
I've got an older Linksys N dual band at the office, upgraded to run DDWRT, and a Netgear AC router at home. I can reproduce the issue both places, so I'm confident it's an issue with software that T-Mobile/Samsung need to address.
Click to expand...
Click to collapse
Ok, well then I guess we should all try contacting T-mobile and letting them know about WiFi issues. I don't want to have this phone ruined by poor net code or whatever it is.
Sent from my SM-G935T using Tapatalk
TheShoxter said:
I'm glad that worked for you. On my end, setting the DNS to standard Google 8.8.8.8 and 8.8.8.4 don't fix the issue. I don't think my router is to blame as it's a fairly new Linksys and all the settings seem to be set up properly as I've never had the issue before this phone. I might need to tinker more though.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
Though it was fixed, I still think it's something wrong with the software because I have several android devices (including both 5 and 6 android), but only two S7 edge have this issue.
I finally fixed the issue for me by setting the DNS of my router itself to Googles Public DNS addresses. Previously I thought changing it on the phone in network settings would do that, but apparently not! Now my phone is working great on my network.
Still an issue that needs to be addressed because some networks we don't have access to change anything.
Sent from my SM-G935T using Tapatalk
I've been going back and forth with T-Mobile and Samsung on Twitter regarding my issues. Samsung wanted me to take my phone to Best Buy, where there is a Samsung Experience kiosk, and have it reloaded with factory firmware. I told them I already downloaded it from SamMobile and would just flash it myself in ODIN. Did that last night after backing my stuff up to the computer, and not a single difference has been made.
My WiFi is rock solid, as long as I don't walk out of range from the router. If I do, it will not reconnect until I turn the screen on. No need to unlock it, just need to turn it on.
Also have a ticket in with T-Mobile for the poor radio performance compared to the Note5. We'll see where that goes.
NotATreoFan said:
I've been going back and forth with T-Mobile and Samsung on Twitter regarding my issues. Samsung wanted me to take my phone to Best Buy, where there is a Samsung Experience kiosk, and have it reloaded with factory firmware. I told them I already downloaded it from SamMobile and would just flash it myself in ODIN. Did that last night after backing my stuff up to the computer, and not a single difference has been made.
My WiFi is rock solid, as long as I don't walk out of range from the router. If I do, it will not reconnect until I turn the screen on. No need to unlock it, just need to turn it on.
Also have a ticket in with T-Mobile for the poor radio performance compared to the Note5. We'll see where that goes.
Click to expand...
Click to collapse
Does it still connect to mobile data when the wifi turns off?
jrwingate6 said:
Does it still connect to mobile data when the wifi turns off?
Click to expand...
Click to collapse
Yes it does. However my office is not in a Band 12 area and the signal is fluctuates between Edge and very weak H+. As soon as I get away from my section of the building however, full LTE and no need for WiFi.
I think this is the same problem I was having. Here's a link to my solution.
http://forum.xda-developers.com/tmo...e-via-wifi-t3335579/post65904586#post65904586
cfmarque said:
I think this is the same problem I was having. Here's a link to my solution.
http://forum.xda-developers.com/tmo...e-via-wifi-t3335579/post65904586#post65904586
Click to expand...
Click to collapse
Although that may very well make it work, this is still something that Samsung and/or Google need to address as not every router's settings are accessible to everyone especially at work or public hotspots.
wpbcubsfan said:
Although that may very well make it work, this is still something that Samsung and/or Google need to address as not every router's settings are accessible to everyone especially at work or public hotspots.
Click to expand...
Click to collapse
I know this won't help many (or anyone 'cuz lock bootloader ), but I think I might've disabled IPv6 on my previous phones, but you need root for that.