Related
Hello
My N1 can connect easily to all kind of wifi routers and modems without problem but not with my fitness club's one, they have a Linksys N160.
My N1 can detect the signal,enter the password but then it's stucked with the message ''getting ip...''
Where is the problem? is it a know hardware or software compatibility stuff?
Sometimes rebooting the wifi router helps. Also make sure that when the guy over at your fitness club reboots the router you don't have the wifi of the club saved. delete the saved wifi profile, reboot the wifi router and then try. Cheers.
Already tried it several times. I saw that OS4 of iphone/ipod have the same problem with router enabling Wireless-N, I will ask him to limit the router to B/G
I also had similar problem with Linksys WAG54G2 (at latest firmware). Then I changed to much cheaper adsl router, TP-LINK WD-W8960N and no more connection problem.
Sent from my Nexus One using XDA App
I had problems using my Nexus One on my SMC Barricade 802.11b/g/n router when 802.11n was enabled. Turned it off; problems were gone. I don't think that works well yet, though some people have said otherwise. Could be a router-specific issue.
Ok so it's a WAG160N to be specific.
He tried to use mixed B/G instead of mixed (which would imply N too) but it still stuck at getting ip...
I told him to throw this router in the garbage because anyway SE and HP mobiles can't connect too,but he said he would do it but his boss will never accept to pay a penny more
My parents had a router that did exactly the same, my phone got stuck on Obtaining IP, whilst the missus 5800 connected and broswed just fine.
It was a crappy old thing and they replaced it the other week, now I can connect and browse just fine.
I also use a linksys WAG160N.
bought a nexus one, could not for the life of me get an internet connection.
turns out dns on router is poofed, so i just set DNS from my isp manually on the nexus one together with a static ip and booya interent at full 802.11n speeds.
sometimes its the simple things.
This sounds similar to when I set my router to channel 13 or whatever the max was on it. My N1 would only sometimes get a connection, but would eventually drop it and stay off. Solved it by selecting a lower channel (WifiAnalyzer suggesten channel 1 as the best alternative to channel max) on the AP.
I can see that in CM6 nightly that I have since started using I can choose regulatory domain, and thereby open up channels previously blocked. If you can't change anything on the AP this might help you solve the problem on your end.
So suggestions if none of the posts above me provide a solution is to run WifiAnalyzer and see how the channel-graph looks.
I can connect to my home wifi fine, good signal and everything, but the thing is when I go to say, load a webpage, it just won't load. No matter how long you leave it.
But when I connect to a mobile hotspot Wifi from my other phone it works fine.
Could it be something to do with my router?
Thanks to anyone that try to help
What router is it?
Sent from my XT862 using XDA
If you have a terminal emulator on your phone, you can try to "ping" the router (most likely 192.168.something.1..)
"ping 192.168.1.1" or whatever address the router has...
This is the same address that you'd type in a browser on your PC to configure access the router's config..
And try to ping something on the Internet such as one of Google's DNS server (ping 8.8.8.8)
A few more details might help us help you:
Router brand and model?
Encryption type used (None, WEP, WPA, WPA2..)? ..WPA2 is sometimes downright broken on some router models..
Does your wireless Internet router work for another wireless device?
Does your Internet work from a wired computer on the same router?
Is the router configured for wireless g,n, or mixed? You might need to play with the router configs.
Sent from my XT862 using XDA
MrObvious said:
What router is it?
Sent from my XT862 using XDA
Click to expand...
Click to collapse
It's a NETGEAR Wireless N Router - WNR2000.
Security: WPA-PSK [TKIP] + WPA2-PSK [AES]
Channel: Auto
All my other devices that I have used the wifi with have worked fine.
This is really annoying, I just can't think of what the problem is..
How many devices are connected to the router at any given time? Try disconnecting another device from wifi and see if that works.
Sent from my XT862 using XDA
Yeah when I disconnected my laptop and then connected my DROID3 it worked fine.
What is the solution to allow it for the DROID3 to work?
Your router only allows for a certain amount of connections. You will either have to turn wifi off of one of the devices or get another router.... simple solution would be to turn off wifi one of the devices when you are not using it.
Sent from my XT862 using XDA
vit3l said:
It's a NETGEAR Wireless N Router - WNR2000.
Security: WPA-PSK [TKIP] + WPA2-PSK [AES]
Channel: Auto
All my other devices that I have used the wifi with have worked fine.
This is really annoying, I just can't think of what the problem is..
Click to expand...
Click to collapse
Try changing the security to WPA2 with AES only - I've seen problems with Android phones in the past when both TKIP with WPA and AES with WPA2 are enabled. If you have any old devices that don't use WPA2 (unlikely), then try WPA with TKIP only. See if that fixes it.
If not, and it's a device limit issue, check the DHCP settings on the router to see what the address range is. If it is set to something like 192.168.0.2 to 192.168.0.xx (whatever number xx is), try extending the range to something larger (though no larger than 254, obviously) and see if that helps.
I tried it a second time and a only got connections every minute or something and it wouldn't last for very long :\
It's not a device limit issue because I have had 2+ devices connected to the wireless before.
I second switching to AES. It is more secure anyway.
Sent from my XT862 using XDA
^ tried that aswell and it didn't work
Maybe try setting a static IP?
Sent from my XT862 using XDA
vit3l said:
^ tried that aswell and it didn't work
Click to expand...
Click to collapse
Turn off all security on the router and try again as a test.also you might need to reset your wifi connections on your phone. Try wifi fixer
Sent from my XT862 using Tapatalk
Have you tried resetting the router? Power it down and then re apply the power. I know that it makes no sense that this should work, but it has fixed the problem twice on my D3.
Hi everyone,
I have a Beklin Share N300 router and trying to set up my chromecast on this network.
Everything works fine, i mean the set up process; chromecast can see the network, can connect the network without any problem but get this message on the screen:
ChromecastXXX connected to yournetwork, but cant access the internet.
Has anyone faced this problem before?
I appreciate for your comments
legendnexus said:
Hi everyone,
I have a Beklin Share N300 router and trying to set up my chromecast on this network.
Everything works fine, i mean the set up process; chromecast can see the network, can connect the network without any problem but get this message on the screen:
ChromecastXXX connected to yournetwork, but cant access the internet.
Has anyone faced this problem before?
I appreciate for your comments
Click to expand...
Click to collapse
Im been having the same problem since yesterday morning. Ive been in contact with Google and they escalted my case but i havent heard back from them about it.
I had the same problem with my E4200v2 router. I just kept trying and trying from the chromecast app on my Samsung Galaxy S4 and after an hour it finally setup. Have patience and keep trying everything. Reference your router's manual for additional information you might need. Good luck!
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
---------- Post added at 08:34 PM ---------- Previous post was at 08:33 PM ----------
Try rebooting the router.
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
did you try putting the CC in the DMZ?
I don't have the CC yet, so I don't know if it needs any ports open in your firewall. Is there any way to manually enter a private IP or DNS info?
From what you're describing, the Chromecast isn't getting the DNS information.
lovekeiiy said:
did you try putting the CC in the DMZ?
I don't have the CC yet, so I don't know if it needs any ports open in your firewall. Is there any way to manually enter a private IP or DNS info?
From what you're describing, the Chromecast isn't getting the DNS information.
Click to expand...
Click to collapse
DMZ could be the solution. Try disabling AP isolation under your router's setup UI.
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
The AP (access point) he probably doesn't have setup anyway since that's more for bridging.
I just don't know if CC needs any ports forwarded. He may want to see what IP is being assigned to his CC and then check the firewall logs to see if any traffic is being blocked by it. The DMZ on his router should place the CC in front of the router and thus let all traffic to and from it, which should, in theory, fix the DNS problem.
It maybe to worth a shot to port foward port 53, which is usually used for DNS. I don't remember if it was UDP or TCP or both. And sometimes you still need to port forward even when using the DMZ. It's lame, but router's just act funny sometimes.
====================
it just dawned on me, it might be that CC is getting it's internet access from the device that's getting the content. So, you may need to enable internet sharing on your PC. Although, I don't think this is the case.
I also was getting the "connected to wireless, but can't access the internet" What I determined is that the ChromeCast is NOT using the DNS servers provided by my DHCP server, it was trying to communicate to a different DNS (likely Google's own).
In my case, I had a firewall in place that prevented access to any DNS other than what I was providing in DHCP. Once I opened the restriction and allowed all DNS traffic, chromecast immediately connected.
Hope this helps someone else.
FLJ74 said:
I also was getting the "connected to wireless, but can't access the internet" What I determined is that the ChromeCast is NOT using the DNS servers provided by my DHCP server, it was trying to communicate to a different DNS (likely Google's own).
In my case, I had a firewall in place that prevented access to any DNS other than what I was providing in DHCP. Once I opened the restriction and allowed all DNS traffic, chromecast immediately connected.
Hope this helps someone else.
Click to expand...
Click to collapse
Interesting. In my case, it was the opposite. I had my laptop configured to use Google's DNS servers and I kept on getting the same "connected to wireless, but can't access the internet" message. I reset the DNS servers on my laptop and Chromecast immediately connected to the Internet.
anyone know which port/s does chromecast use
DMZ worked for me but i dont like putting devices on DMZ. Sounds like this is just a port forwarding issue and putting it on DMZ is an overkill.
Anyone knows which port/s does chromecast use???
I also have the Belkin N300 and was having the same trouble. What i did was a factory reset on my router and a firmware update in the router settings and now everything seems to be working fine as of now.
AP Isolation
Switching off AP Isolation fixed the issue for me. I had the same issue before I did this.
Soldier 2.0 said:
DMZ could be the solution. Try disabling AP isolation under your router's setup UI.
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
I tried DMZ, but it didnt work. Also I tried disabling firewall, it didnt work too.
lovekeiiy said:
The AP (access point) he probably doesn't have setup anyway since that's more for bridging.
I just don't know if CC needs any ports forwarded. He may want to see what IP is being assigned to his CC and then check the firewall logs to see if any traffic is being blocked by it. The DMZ on his router should place the CC in front of the router and thus let all traffic to and from it, which should, in theory, fix the DNS problem.
It maybe to worth a shot to port foward port 53, which is usually used for DNS. I don't remember if it was UDP or TCP or both. And sometimes you still need to port forward even when using the DMZ. It's lame, but router's just act funny sometimes.
====================
it just dawned on me, it might be that CC is getting it's internet access from the device that's getting the content. So, you may need to enable internet sharing on your PC. Although, I don't think this is the case.
Click to expand...
Click to collapse
I tried this too, even porting, but no luck..
tried every single suggestion but cant figure out what is wrong.
What i understand from the replies; it needs some specific DNS. But when i change my DNS on my routers setting page different than provided my ISP, router itself doesnt connect to internet.
DMZ, MAC filtering, disabling Firewall, disabling AP, none of them work so far; with numerous combination of those...
I believe it shouldnt be that hard.. ?
Update: Placing it in DMZ took a couple of retries but have fixed the issue now.
Similar problem. Worked on the first setup. Then after two day a get "can't connect to internet" message. Tried factory resetting and putting in the DMZ. Nothing helps. Anyone?
legendnexus said:
... What i understand from the replies; it needs some specific DNS. ...
Click to expand...
Click to collapse
NeedAPhone said:
Update: Placing it in DMZ took a couple of retries but have fixed the issue now.
Similar problem. Worked on the first setup. Then after two day a get "can't connect to internet" message. Tried factory resetting and putting in the DMZ. Nothing helps. Anyone?
Click to expand...
Click to collapse
I don't really have more suggestions. From what I know, the CC doesn't need any special DNS information because really all the CC is just a media player (although not exactly correct). When you cast something to it, the device (mobile device or PC) you're sending it a URL, which it then opens and can play. This is why it needs an internet connection. Tab casting is a little different. Thus, if it'll play on your mobile device or PC, you can play it on the CC (assuming the content is CC compatible). If there is not internet to the CC, then the DNS and ISP information is not being forwarded to the CC or it's not connecting to them; this assumes it's getting an private IP from the router and not being denied because of MAC filtering or something.
Over here I've got another problem. My current ISP forces me to use their DNS. Since the Chromecast has its own fixed Google DNS (8.8.8.8 & 8.8.4.4), the Chromecast is not allowed to connect to the internet.
Rvanlaak said:
Over here I've got another problem. My current ISP forces me to use their DNS. Since the Chromecast has its own fixed Google DNS (8.8.8.8 & 8.8.4.4), the Chromecast is not allowed to connect to the internet.
Click to expand...
Click to collapse
Same here, I'm on a studentnet that uses a PPTP connection with their own DNS, so if I change the DNS I won''t have an internet connection, permanent. Not sure how to fix that.
ninepoint said:
Same here, I'm on a studentnet that uses a PPTP connection with their own DNS, so if I change the DNS I won''t have an internet connection, permanent. Not sure how to fix that.
Click to expand...
Click to collapse
Try a VPN ?
Sent from my XT897 using XDA Premium 4 mobile app
I had the same issue with the original firmware (12072).
After leaving it connected a few days it eventually stayed connected long enough to download an update.
After restarting it, it applied the update.
On firmware 13300 it complains when it initially boots, then after about a minute or two it connects successfully.
So...
If you're rooted, use FlashCast to update to PwnedCast 1.0 (based on 13300)
If you're not root-capable or have no plans to root, set it up and leave it at the "but can't connect to the Internet" for a few days (just leave it powered by the power adapter), then power-cycle it, hopefully you will see it updating.
I used to use the netflix on daily basis until about three weeks ago I started to get the following message after a long time displaying the netflix splash screen on my TV: "Humm... It seems we're unable to connect". And then the netflix closes after 10 seconds. Every other chromecast official app works good, but Netflix. I also noted that if I restore the chromecast and launch netflix, everything will work. But if I cast other app, as YouTube for instance, and then return to netflix, I'll get the problem again, requiring another restore.
My chromecast software version is 16664.
Is anyone experiencing the something like that?
Sent from my HTC One_M8 using XDA Free mobile app
luizm.jr said:
I used to use the netflix on daily basis until about three weeks ago I started to get the following message after a long time displaying the netflix splash screen on my TV: "Humm... It seems we're unable to connect". And then the netflix closes after 10 seconds. Every other chromecast official app works good, but Netflix. I also noted that if I restore the chromecast and launch netflix, everything will work. But if I cast other app, as YouTube for instance, and then return to netflix, I'll get the problem again, requiring another restore.
My chromecast software version is 16664.
Is anyone experiencing the something like that?
Click to expand...
Click to collapse
Just to confirm, you're not using any DNS relocation/redirection (Unlocator, Unotelly, etc), right?
I just used Netflix the other day, and I'm still on 16664.
It's weird that everything else works except for Netflix, and also weird that factory reset makes it work. Could be a bug or perhaps something with WiFi connectivity. You don't have a WiFi repeater or multiple APs using the same SSID do you?
bhiga said:
Just to confirm, you're not using any DNS relocation/redirection (Unlocator, Unotelly, etc), right?
I just used Netflix the other day, and I'm still on 16664.
It's weird that everything else works except for Netflix, and also weird that factory reset makes it work. Could be a bug or perhaps something with WiFi connectivity. You don't have a WiFi repeater or multiple APs using the same SSID do you?
Click to expand...
Click to collapse
I use regular DNS. I also tried different WiFi routers and I always got this issue. Rarely Netflix works without need factory reset.
I was wondering if it could be a problem with the chromecast cache. Do you know a way to clear the cache without factory reseting?
luizm.jr said:
I use regular DNS. I also tried different WiFi routers and I always got this issue. Rarely Netflix works without need factory reset.
I was wondering if it could be a problem with the chromecast cache. Do you know a way to clear the cache without factory reseting?
Click to expand...
Click to collapse
Not that I know of... however, since the Netflix app is stored on Chromecast, there's a small possibility that it's a RAM or NAND issue on your Chromecast itself. If it's not rooted or special in any way, you might want to consider getting it replaced.
Or see if you can borrow another Chromecast to see if the problem is localized to your specific device.
bhiga said:
Not that I know of... however, since the Netflix app is stored on Chromecast, there's a small possibility that it's a RAM or NAND issue on your Chromecast itself. If it's not rooted or special in any way, you might want to consider getting it replaced.
Or see if you can borrow another Chromecast to see if the problem is localized to your specific device.
Click to expand...
Click to collapse
This is new for me. I thought Netflix was loaded online. I'll ask a friend that has chromecast to test mine in his home and and borrow his chromecast.
I'll let you know the results tomorrow.
Thanks
I borrowed a chromecast and first time it worked. After casting YouTube videos and then return to netflix, same thing happened. My friend got everything working great using my chromecast.
The only thing that never changed is my cable modem, but I never change anything on it. Moreover, why this is happening only with netflix and why it works if I factory reset are still a mystery.
Sent from my HTC One_M8 using XDA Free mobile app
luizm.jr said:
I borrowed a chromecast and first time it worked. After casting YouTube videos and then return to netflix, same thing happened. My friend got everything working great using my chromecast.
The only thing that never changed is my cable modem, but I never change anything on it. Moreover, why this is happening only with netflix and why it works if I factory reset are still a mystery.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Perhaps you are seeing the first case of Net Neutrality biting you in the ISP?
See if you can reach Netflix via the browser...
I don't think so. I can access netflix anywhere else: tablet, phone, ps3 and computer. Besides, my friend use the same isp.
The only other place I having trouble in access netflix is my old Asus cube that I had retired since I got the chromecast last year.
Sent from my HTC One_M8 using XDA Free mobile app
luizm.jr said:
I don't think so. I can access netflix anywhere else: tablet, phone, ps3 and computer. Besides, my friend use the same isp.
The only other place I having trouble in access netflix is my old Asus cube that I had retired since I got the chromecast last year.
Click to expand...
Click to collapse
Quite the puzzle...
Since your Chromecast works on your friend's network, and your friend's Chromecast shows the same behavior as yours on your network, the breakage factor definitely seems to be something about your network.
I really can't think of your cable modem being an issue unless isn't going bad (if it has an interface, look for excessive errors and/or poor signal quality - for example, Motorola SurfBoards usually have an interface at http://192.168.100.1/).
As your friend is using the same ISP, I would compare your router settings with his - ISP login type, routing and DNS in particular.
Of course if you have different routers then the router itself is still a variable.
I'll try to share my mobile Internet connection as soon I get back home to see if it will do the same.
Also I'll try to look the router log to see something.
Sent from my HTC One_M8 using XDA Free mobile app
I tested chromecast connecting to my phone in tethering mode. Netflix worked everytime. But when I got back to my regular connection, the problem appeared again.
So the problem seems to be located in my cable modem that also is a router.
Sent from my HTC One_M8 using XDA Free mobile app
Ok first question...do you have another router connected to the Modem Router? Are you using the Modem's built in WiFi or this other router's?
If you have another router then chances are likely you have a double NAT situation which is messing you up.
Check your other router and see what IP address is has listed under Internet connection...If it is a 192.168.xxx.xxx then it's a double Nat and you need to call your Cable company and have them put the Modem into Bridge mode.
If you do not have another router and use only the Modem router then you need to call the cable company and have them change the settings on the router to allow multicast and UPnP...Maybe a few other settings as well. Tell them what you are trying to do they have probably gotten lots of calls from others with the same issue.
Me personally I prefer to use my own router and have them put the Modem into Bridge mode so I have full control over the network and don't need to call them whenever I have a problem or want to change settings.
Asphyx said:
Ok first question...do you have another router connected to the Modem Router? Are you using the Modem's built in WiFi or this other router's?
If you have another router then chances are likely you have a double NAT situation which is messing you up.
Check your other router and see what IP address is has listed under Internet connection...If it is a 192.168.xxx.xxx then it's a double Nat and you need to call your Cable company and have them put the Modem into Bridge mode.
If you do not have another router and use only the Modem router then you need to call the cable company and have them change the settings on the router to allow multicast and UPnP...Maybe a few other settings as well. Tell them what you are trying to do they have probably gotten lots of calls from others with the same issue.
Me personally I prefer to use my own router and have them put the Modem into Bridge mode so I have full control over the network and don't need to call them whenever I have a problem or want to change settings.
Click to expand...
Click to collapse
My cable modem a public IP provided by my ISP, and a private IP that is 192.168.0.1. My router has a WAN IP provided by my cable modem (192.168.0.xxx) and a LAN IP 192.168.1.1. My chromecast used to be connected in my router LAN, but I changed it to connect directly to the cable modem router. I'll try to put the cable modem in bridge mode to see what happens as I have full access to its configuration.
Thanks again
luizm.jr said:
My cable modem a public IP provided by my ISP, and a private IP that is 192.168.0.1. My router has a WAN IP provided by my cable modem (192.168.0.xxx) and a LAN IP 192.168.1.1. My chromecast used to be connected in my router LAN, but I changed it to connect directly to the cable modem router. I'll try to put the cable modem in bridge mode to see what happens as I have full access to its configuration.
Thanks again
Click to expand...
Click to collapse
Yep that setup causes a double Nat situation Which doesn't work well for most networking applications....
Especially since you are also dealing with Two different Wireless networks.
Best setup is to have the modem just be a modem and send public IPs to whatever connects to it.
Then you won't have any Nat translation issues PLUS you get the ability (if your Modem has multiple ports like most Modem/Router Hybrids do, You can get a public IP for any device directly connected to the Modem which is good for running servers and for testing router issues.
Problem solved!
I turned off the wifi on the cable modem and put it on bridge mode, letting my router deal with my network. Netflix is now working good on both chromecast and Google tv.
However I believe the problem was related to a still unknown setting in the cable modem as I left it operating alone and netflix was still not able to load.
Thank you very much for the help. I really appreciate it.
Sent from my HTC One_M8 using XDA Free mobile app
luizm.jr said:
Problem solved!
I turned off the wifi on the cable modem and put it on bridge mode, letting my router deal with my network. Netflix is now working good on both chromecast and Google tv.
However I believe the problem was related to a still unknown setting in the cable modem as I left it operating alone and netflix was still not able to load.
Thank you very much for the help. I really appreciate it.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
it may very well have been a Router issue with the Modem...But now that it is only a Bridge the other router's settings will handle all the communication needed for the CCast and it should work...
As long as the settings on the second router were not the issue in the first place.
I just updated my Nexus 6 from T-Mobile and now the WiFi won't turn on. Any one else with this issue?
It will just show this
Sits on this screen also. WiFi is broken
Bump
jprovan1 said:
Bump
Click to expand...
Click to collapse
Might be defective, might be a bug you should try a factory reset. I suspect I have a WIFI problem as well (not the same) as mine will absolutely not connect to my work network even though it should and I've tried everything.
youareme7 said:
Might be defective, might be a bug you should try a factory reset. I suspect I have a WIFI problem as well (not the same) as mine will absolutely not connect to my work network even though it should and I've tried everything.
Click to expand...
Click to collapse
Same here. I had the problem on the Nexus 5 and hoped the Nexus 6 would solve this but I cannot connect to my work wifi either.
I am having the same problem at work too. Never had it on any other devices (m8, nexus 5, note 4, etc.) Wondering of they did something new with WiFi or if its the router settings or outdated routers.
Android devices have had a history of issues with some older Wireless Access points. The problem isn't that they won't connect, but that they won't get an IP address. You may be able to work around the issue, by finding an unused IP address, and manually setting it for that wifi connection. Contact your IT person if you don't know what all this means, and ask him/her for the following:
IP Address
Subnet Mask
Default Gateway
DNS Server
You'll need those to set things up manually. If you can connect after setting it up manually, then the issue is incompatibility with the WiFi access point (or the DHCP server, which gives out IP Addresses), not with your phone.
jt3 said:
Android devices have had a history of issues with some older Wireless Access points. The problem isn't that they won't connect, but that they won't get an IP address. You may be able to work around the issue, by finding an unused IP address, and manually setting it for that wifi connection. Contact your IT person if you don't know what all this means, and ask him/her for the following:
IP Address
Subnet Mask
Default Gateway
DNS Server
You'll need those to set things up manually. If you can connect after setting it up manually, then the issue is incompatibility with the WiFi access point (or the DHCP server, which gives out IP Addresses), not with your phone.
Click to expand...
Click to collapse
I will give that a try. I just confirmed that it's ONLY my nexus 6, I brought in my nexus 7 2013 with lollipop to work (which I have never done) and it was able to connect with no problem so now I'm sure it's a problem with the nexus 6.
EDIT: I tried manually connecting to the router and that didn't do it as well. I wish there was a way to submit the bug because it's a pain in the ass to not have wifi on my phone at work, poor signal in the building means it kinda chews on the battery.
If anyone else tries manual and succeeds please let us know!
https://code.google.com/p/android/i...fi&colspec=ID Type Status Owner Summary Stars
Add feedback to escalate the issue. I get no cellular signal inside my office at work so WiFi is A MUST for me.
HCdroid said:
https://code.google.com/p/android/i...fi&colspec=ID Type Status Owner Summary Stars
Add feedback to escalate the issue. I get no cellular signal inside my office at work so WiFi is A MUST for me.
Click to expand...
Click to collapse
Yep exactly, it's not just a nexus 6 issue, it also affects the nexus 5 on LXR210. Sounds like it's actually cisco's fault for incorrectly using the wrong EAPOL-Key descriptor version (3 instead of 2). Hopefully google fixes the issue quickly.
I had a defective unit. Took it back to T-Mobile and they had one Nexus left and swapped it out now everything is great. Now the damn X Where it says NEXUS on the back of the phone fell off . Oh well
I have the AT&T Nexus 6 and now I'm having WiFi issues. Keeps dropping connection or says poor than disconnects. No issue on any other device and it will not even show my 5ghz band.
Sent from my Nexus 6