I realized that my University's wifi somehow does not support 4.2.1
I've asked them about it, and they said 4.2's kernel might be different and it might not recognize the wifi.
What can i do about that without downgrading? (My device is rooted.)
Thanks.
Perhaps you should say a few words about your University WiFi. Same goes for what you have done to your N7 (as you stated that it is rooted). Maybe you could mention whether or not you personally had it working with a 4.1.x-derived ROM on the phone - reading between the lines it sounds like that might be the case, but it isn't clearly stated.
"Does not support" is not very descriptive.
First - does the WiFi scan on the N7 display the network? (e.g. the N7 does not support Ad-Hoc networks, so they won't even show up in the first place)
What details can you provide about the WiFi network?
- Ad-hoc or Infrastructure mode?
- is WEP/WPA/WPA2 in use?
- if Y to above question, how is key distribution performed?
Are there any other relevant symptoms, such as the N7 connecting, but then fails to get an IP address - or gets an IP, but still acts as if not connected?
If you are convinced that it is in fact a 4.1.x vs. 4.2.x issue, could you not just install a 4.1.x-derived ROM?
Note also that the n7 does not support WiFi N band. Make sure the university provides G support.
Sent from my Nexus 7 using xda app-developers app
The N7 absolutely supports 802.11 b/g/n. Take a look at the tech specs in Play store.
bftb0 said:
Perhaps you should say a few words about your University WiFi. Same goes for what you have done to your N7 (as you stated that it is rooted). Maybe you could mention whether or not you personally had it working with a 4.1.x-derived ROM on the phone - reading between the lines it sounds like that might be the case, but it isn't clearly stated.
"Does not support" is not very descriptive.
First - does the WiFi scan on the N7 display the network? (e.g. the N7 does not support Ad-Hoc networks, so they won't even show up in the first place)
What details can you provide about the WiFi network?
- Ad-hoc or Infrastructure mode?
- is WEP/WPA/WPA2 in use?
- if Y to above question, how is key distribution performed?
Are there any other relevant symptoms, such as the N7 connecting, but then fails to get an IP address - or gets an IP, but still acts as if not connected?
If you are convinced that it is in fact a 4.1.x vs. 4.2.x issue, could you not just install a 4.1.x-derived ROM?
Click to expand...
Click to collapse
I know that, Wi-Fi works with Galaxy S 3 having 4.1.1
And the setting used to access Wi-Fi are as follows:
Security: 802.1x EAP
EAP Method: PEAP
Phase 2 Authentication: MSCHAPV2
... And I put-in my username and password in the followings.
I tried to connect, it shows the signal much weaker then it actually is, then it tried to connect, but just fails...
Zhoene said:
I know that, Wi-Fi works with Galaxy S 3 having 4.1.1
Click to expand...
Click to collapse
That's all well and good, but it doesn't necessarily mean that 4.1.x vs. 4.2.x is the cause of things. Different hardware, different OS, and presumably different WiFi radio hardware and firmware. Could be any of those things, the OS being one of them.
Zhoene said:
And the setting used to access Wi-Fi are as follows:
Security: 802.1x EAP
EAP Method: PEAP
Phase 2 Authentication: MSCHAPV2
... And I put-in my username and password in the followings.
I tried to connect, it shows the signal much weaker then it actually is, then it tried to connect, but just fails...
Click to expand...
Click to collapse
Association and Authentication to a WiFi AP have lots of moving parts. It is possible that the problem is with either of them. (My WAG would be the authentication process) Without a super-geek that can help you with wireless sniffing (to see if the fault location can be inferred), or your campus IT help desk being able to look at authentication logs, you don't really have much recourse but to:
- do something drastic (e.g. install new ROMs)
- experiment with the settings in the WiFi "Add network" page, and look to see if you get any meaningful or diagnostic messages in the system logs. I tried it just now, but I don't have an 802.1x AP available to test (a failed PW, for instance) with to see if anything diagnostic shows up in logcat. Is it possible that it is just a bad password entry? (I have had problems when I cut and paste in android with various apps inserting a leading space ahead of the paste).
The 4.1.2 factory image for the WiFi N7 (grouper) is still available from Google - I think the form in which they provide it to you needs to be flashed using fastboot though, and managing that seems to cause newbs trouble. You might want to just find an older ROM which is based on 4.1.x and try it to see if it fits your hypothesis. (If you fool with a factory ROM install, make sure you have backups of EVERYTHING first).
Good luck
I have taken my nexus 7 to IT they looked into it and they said its possibly that it not compatible with 4.2.1
I guess downgrading to 4.1.2 might do trick, but I also don't want to leave the awesome features of 4.2.1
I guess I will firstly try different kernels and see if they change anything.
This thread contains reports of problems with both 4.1.x and 4.2.x N7's
I suspect that just reflects a diversity of different wireless networks; but anyway - see the logcat entries with "I/wpa_supplicant" in them? Your tablet (on 4.2.1 or whatever) might have similar things in it that gives clues as to where the errors occur.
You can get logcats with adb - or failing that, there are free market apps you can get which will dump the logcat to a file of your chosing.
Good luck
Thanks I will take a look at those.
Miss-statement on my part earlier. Nexus 7 does support 802.1n operation - but only in the 2.4ghz band. 5ghz is not supported. My router supports both - and the faster ssids are not even visible on the Nexus 7.
Sent from my Nexus 7 using xda app-developers app
Is that all about hardware, or is there a software wise solution to it?
Zhoene said:
Is that all about hardware, or is there a software wise solution to it?
Click to expand...
Click to collapse
802.11n specifies channel bonding techniques as well as optional use of the 5 Ghz radio band.
So, marketers can safely say "Wifi N" or some such - as long as the hardware/software can do channel bonding (but possibly not operate in the 5 Ghz band).
Here's Asus N7 Spec Page, as you see they do not mention 5Ghz Wifi.
My thinking is that if the hardware had it, it would also show up proudly in the specs.
A to the Q: hardware.
It now occurs to me that Zhoene earlier had said
Zhoene said:
I tried to connect, it shows the signal much weaker then it actually is, then it tried to connect, but just fails...
Click to expand...
Click to collapse
A university setting probably would be a WDS (Wireless Distribution System) with many AP's. Possibly Zhoene was sitting close to a 5Ghz-only AP, and "seeing" a multi-band AP at a good distance away? Sure would be consistent with rmm200's observations on his/her router.
Also, I see reports of 5 Ghz service achieved on Galaxy S3 (Zhoene prev mentioned)
Perhaps this is exactly a 5Ghz AP vs. Nexus 7 issue.
And, oh crap after all this writing I did a search
http://forum.xda-developers.com/showthread.php?t=1777431&highlight=5ghz+802+11n&page=3
Zhoene you could ask your campus IT if there are any A/B/G- or B/G-only APs in their network & see if you can connect at those locations. If it was something weird like Beacons only in 5Ghz-band channels (I think that would violate the IEEE specs), then you could have been trying to connect to very remote APs - all the while getting clobbered by other devices sitting nearby doing 802.11n in the 2.4Ghz band, but also the nearby AP as well if it was operating in multi-band mode.
Thanks a lot for all the information, I'll try to find out what the problem really is using those informations.
Some of this talk of networking is over my head, but what I would try is flashing a 4.1.2 ROM/image and seeing if that fixes it. 4.1.1 had a bug that prevented the Nexus 7 from connecting to WPA-Enterprise networks, which is what my university uses (I know because my Kindle can't connect to it). 4.1.2 fixed this, and my Nexus 7 (on 4.1.2) can connect to my university's network. I have been rejecting the update to 4.2.1 after hearing about issues, so I don't know if it works with 4.2.1.
Related
I use CM7.1 and generally my ZTE Blade works really well. But I do have a problem connecting to the WiFi network at my workplace. It uses WPA2 with EAP (every user has a user name and a password), and no matter what I try to set it up, it just does not connect.
There is a tool called XpressConnect, which configures the WiFi for you. And that works.
I think that leaves only two plausible explanations: either the configuration data I am given is wrong (and that is unlikely, because it works on my computer), or the settings menu for WiFi networks is broken when it comes to EAP. Does that make sense? And is there a way to check the configuration files that are written by the settings tool, and compare them to what XpressConnect does?
I am not in a big rush to solve this issue, but given that WiFi problems seem to rank pretty high with CM, it may be worth tracking down.
MrPuddington said:
I use CM7.1 and generally my ZTE Blade works really well. But I do have a problem connecting to the WiFi network at my workplace. It uses WAP2 with EAP (every user has a user name and a password), and no matter what I try to set it up, it just does not connect.
There is a tool called XpressConnect, which configures the WiFi for you. And that works.
I think that leaves only two plausible explanations: either the configuration data I am given is wrong (and that is unlikely, because it works on my computer), or the settings menu for WiFi networks is broken when it comes to EAP. Does that make sense? And is there a way to check the configuration files that are written by the settings tool, and compare them to what XpressConnect does?
I am not in a big rush to solve this issue, but given that WiFi problems seem to rank pretty high with CM, it may be worth tracking down.
Click to expand...
Click to collapse
I'm not sure about cm7 but in cm 9 there is a option for it
saaransh9 said:
I'm not sure about cm7 but in cm 9 there is a option for it
Click to expand...
Click to collapse
Well there is an option to configure it all right, but it does not connect. Instead it sits around "connecting" for ages, and then disconnects.
If I use XpressConnect to configure it instead, it works as it should. I think that should help to narrow down the problem, but I do not have a lot of experience with how WiFi encryption works internally.
I've been reading through the forums trying to find a solution to my WiFi-N issues.
Here is what I've done and what is happening
1. Got a Nook Simple Touch (stock unrooted) and updated from 1.0 to 1.1.2 via the directions found at Barnes and Noble
2. Rooted using TouchNooter 2.1.31
3. The screen never turned black/off. The instructions remained on the whole time. So I left it over night to be sure it would work. Took out TouchNooter SD card and rebooted, and the NST was rooted and worked.
4. WiFi connection issues start.
I can connect to my home WiFi, but do not get any internet access.
NST says connected but No internet, router shows the NST as a connected device.
My router is a NetGear WNR2000v1 with the latest North American firmware (1.2.3.7).
I've got the security set to WPA2 PSK (but since I can connect I guess it is a moot point).
Attempted but failed solutions
1. Reboot NST (multiple times)
2. Forget my wifi network and then enter credentials again
3. Reboot router and cable modem (and repeat 1 and 2)
4. Change my wifi SSID to something more simple (and repeat 1 and 2)
5. Use an open network temporarily (and repeat 1 and 2)
6. Used MAC address filtering on the router to force a specific LAN IP address instead of leaving it up to DHCP
7. Ensured the NST (and my laptop) was only device on the network
Non-NST Based Solution (hopefully temporary)
My router was set to the 300Mbs setting, but that was not working, so I tried the 145Mbs setting without any luck, then switched it to 54Mbs setting and it works!
Per the manual for the router:
– Up To 54 Mbps. Legacy mode, for compatibility with the slower 802.11b and 802.11g
wireless devices.
– Up To 145 Mbps. Neighbor Friendly mode, for reduced interference with neighboring
wireless networks. Provides two transmission streams with different data on the same
channel at the same time, but also allows 802.11b and 802.11g wireless devices. This is
the default mode.
– Up To 300 Mbps. Performance mode, using channel expansion to achieve the 300 Mbps
data rate. The WNR2000 router will use the channel you selected as the primary channel
and expand to the secondary channel (primary channel +4 or –4) to achieve a 40 MHz
frame-by-frame bandwidth. The WNR2000 router will detect channel usage and will
disable frame-by-frame expansion if the expansion would result in interference with the
data transmission of other access points or clients.
Click to expand...
Click to collapse
I would assume the 145Mbs option should work with the NST since the NST is a 802.11b/g/n device.
I will probably try this solution when I get home [N2E][1.1][solved] wifi/dhcp lease issues
I did not try the WiFi Static app yet, because I have not gotten the market to work yet (i'm working under the assumption that it is the wait-a-day-or-so-for-the-market-to-work issue).
Do you have any other possible solutions or advice?
I'd really prefer to be able to use the 802.11n speeds on my router so that other devices play and stream nicely (Apple TV & PS3)
weird compatibility issues with specific router/firmware combos are, unfortunately, relatively common in nook devices and by no means unheard of for android devices as a group.
you may find that only the b/g mode works with your router - but once your device is connected to your router when it's running at 145, its worth looking to see if you can ping the mac address of the NST from your router, if your router supports a diagnostic ping that will take a MAC as an input.
Some folks over on the BN forums found that once they could ping the MAC, the connectivity issue was resolved. (I don't know how long-lasting the fix was.)
My guess is that some android devices are doing something odd in reply to ARP requests.
Another option would be to pick up the cheapest b/g or b-only access point you can find and just use that for the NST, leave the real access point set up for the things that can really use it. Fry's sells workable low-end access points from Trendnet for 25 bucks or so, or used to.
Here it is:
http://www.amazon.com/TRENDnet-Wireless-Broadband-Router-TEW-432BRP/dp/B000BI1XNE/ref=pd_sim_e_1
I used this for a year or so at one point; for me it worked fine. Many people do hate it (20% of the reviews are one-star.)
For a little more,
http://www.amazon.com/TRENDnet-54Mb...430APB/dp/B000799LPE/ref=cm_cr_pr_product_top
you get two antennas and only 10% 1-star reviews
Out of curiosity, before you got it rooted – were you able to connecet @ 300 Mbps. Performance mode?
You need internet connection to register nook, unless you bypass registeration…
I honestly am not sure if it was the performance mode, but it did connect automatically and my router was set to performance mode. I'm working under the assumption it did connect with the 1.0.1 software that came with it... I registered and updated the software then rooted, but didn't pay attention to whether the 1.0.1 vs 1.1.2 connected before rooting.
The second router is a pretty good idea, I probably have one sitting around somewhere too.
_Boondock_ said:
The second router is a pretty good idea, I probably have one sitting around somewhere too.
Click to expand...
Click to collapse
Pocket/travel size router coming up regularly on slickdeals.net for $10-20 shipped. Some even support DD-WRT.
I got a "refurbished" D-Link DIR-615 (that takes DD-WRT) for $20 locally.
"Refurbished" in this case means that somebody bought it once, it was too complicated for them,
they threw it back in the box and D-Link repackaged it in a plain box.
The Nook has a spare connector inside for a second antenna.
It's one of those teeny-tiny connectors.
Renate NST said:
The Nook has a spare connector inside for a second antenna.
It's one of those teeny-tiny connectors.
Click to expand...
Click to collapse
Interesting!
Did you take a picture?
Have you connected it already? :good:
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.
Hello all.
I can connect my Nexus 10 to my home wifi (password protected), my girlfriend's home wifi (password protected), and the wifi at public places (I've only tried ones without passwords so far). My only problem is when using my University's Wifi. They have one that you use with an account and password, and one that is free (though you need to sign in using an email via a website. Kinda like hotels).
This is surprising to me because I have a Galaxy Nexus running the same OS (4.2.1) and it can connect just fine. When my N10 tries to connect, it says "connecting" for a second or two, and then it just says "Saved" but never "connected" and it never shows a wifi connected symbol at the top right.
I have read multiple posts about wifi problems from 4.2 but couldn't find any specifically buggy wifi problems like this. Have any of you heard of this or a solution to it? Any help would be appreciated!
Have you tried a reboot? Also check to see if your frequency band is set to auto under advanced wifi settings.
Gotta love university security and logins... they can't leave stuff simple
Oh yes. I have rebooted many times and tried using auto, as well as both frequency bands separately.
Hmmm...are you on stock?
Yes I am. Stock on both my Gnex and N10.
I wonder if using a third party wireless manager would help. Search the PlayStore and try one or two. Before you do that, go into your normal WiFi settings and click "forget this network" on the university one.
Hi there,
I work at a University in the midlands and had the same/similar problem. It's to do with certificate revocation in Jellybean (and also the latest ios my colleague tells me). For example on my Nexus 10 I was able to see the network and obtain an ip address but the webpage where you login wouldn't redirect or load. I don't know what Uni you go to but we are advising people to give the IT dept a call and give them your mac address and they can create a fixed profile.
Hope this helps
I'll definitely try the third party app. As for telling the n10 to forget the WiFi, I tried that many times too
Well that's why I mentioned my gnexus because they're the same android versions so if it works on one it should on the N10. I actually work for tech support at my university and my boss couldn't figure it out or suggest a process like you described. Thanks, though!
yodasoja said:
I'll definitely try the third party app. As for telling the n10 to forget the WiFi, I tried that many times too
Well that's why I mentioned my gnexus because they're the same android versions so if it works on one it should on the N10. I actually work for tech support at my university and my boss couldn't figure it out or suggest a process like you described. Thanks, though!
Click to expand...
Click to collapse
Oh yeah you did mention your Galaxy Nexus, my bad! let us know how you get on with the third party app. You could try giving your N10 a static or reserved IP if you have access, as a workaround!
Hey guys,
I'm from France and had such trouble with my Motorola Milestone and my HTC HD2 (and friends too with Samsung Galaxy S2 and Sony Ericsson Xperia Active) with my school's network. If it's an Eduroam network, try Eduroam Fixer from PlayStore, it helped all of us except one Samsung Galaxy S2. Give it a try
https://play.google.com/store/apps/details?id=nl.luqq.eduroamfixer&hl=fr
I wish I could use that app, but it says I can't use it in my country (USA)
yodasoja said:
I wish I could use that app, but it says I can't use it in my country (USA)
Click to expand...
Click to collapse
Make sure you have the EAP set correctly and check if you need a phase 2 authentication. For example, here at UofM we use PEAP for eap and mchapv2 for the phase 2. If you don't have details like these, your tablet won't connect even if you have the proper login.
You will find them at the top of the page you use to login to a secure network.
Hope this helps!
Yes, that is exactly how the secure WiFi is set up at my University, too! What should I do in this case?
Edit: Nvm, Just noticed this was already tried
I had a similar issue with my One XL. It was a frequency issue. I switched it from 5ghz to auto and all was good.
Settings/WiFi/advanced/WiFi frequency band/auto.
Sent from my Nexus 10 using xda app-developers app
Okay so I found out that my N10 is able to connect to the exact same WiFi network when in another building. I believe there is just an issue connecting to the specific router used at a computer lab. Will update when/if a resolution arises for that lab.
Hi folks,
I have two Nexus players at home. When I first got the initial one, I had it setup on my 2.4G network (network connectivity was very strong so it did not matter). Recently, I upgraded my router that supports 802.11AC (2400mbps). Since the router was further out and since AC provides a better streaming experience, I added the 5G network as well. It turned out that it was still connecting to my 2.4G network (based purely on signal strength, I assume, which is absurd). So I had it "forget" the 2.4G connection. The next day, I had my replacement for the Nexus player (had a issue with the remote but they sent me the whole thing anyway) and bought a second Nexus player. I logged in with the same account that I had used and surprisingly both of them were logging onto my 2.4G network without even asking. It left me puzzled. I tried "forgetting" the network and it did not work. I tried intentionally giving a "bad" password and that did not work either (i.e. the second option at least kind of worked for one full day where it did not connect to the 2.4G connection). I have since done a factory reset with two options. A) re-login with the same account and B) login with a different account. Not too surprisingly, option (A) allows me to "connect" to the 2.4G connection whereas (B) does not.
I have since tried to figure out where this password is saved and I cannot seem to find it. The only logical way for me to NOT connect is to turn off the 2.4G connection (which is not possible because some of my devices still do not support 5G) or rename the connection (logistical issue but can be done). My concern is "WHERE IS MY PASSWORD SAVED AND WHY AM I NOT ABLE TO DELETE IT AS I WOULD ON ANOTHER DEVICE"
I called Nexus support (they are practically useless unless you are requesting a replacement) and I got the following (no I am not kidding, these were literally the things that they told me):
1. "The Nexus player has no GUI". I refuted this claim and explained that the device was fully self-sustained in that it did not require a phone to be its alibi and that a network can be "forgotten"
2. "The Nexus player has no firmware". I again respectfully refuted this claim as well but it was getting a little hilarious because I really thought she said "no GUI" to imply something else. To this, the rep said (and in a very authoritative tone), GIVE ME THE ADDRESS OF THE FIRMWARE. I explained that all firmware does not have to have an IP address (I work at a company that makes hardware and specifically work on the DSP which has no direct access or IP address except via a host processor). I then asked "Can you do a software update on the device" and she responded "I don't know" and then went on to say the following
3. "THE NEXUS PLAYER HAS NO OS!". SHE LITERALLY SAID THAT.
At no point in time was she did even accept that the password was saved "somewhere" in the cloud and was attached to my google account that I had no access to which I believe is very creepy (because now I do not know what other information is "stored"). Then she said "let me send you to speak to the manufacturer because we have nothing to do with this device" or something to that effect!
I am curious if anyone of you can try this out and tell me if the player continues to connect to a network that you ask to be forgotten. I am curious also what you think about the issue.
Saving WiFi passwords to your Google account is a standard feature of Google's Backup & Restore, if you have this enabled. The option to disable this doesn't seem to be exposed by the Android TV UI, though.
And that support conversation was hilarious
ghtop said:
Saving WiFi passwords to your Google account is a standard feature of Google's Backup & Restore, if you have this enabled. The option to disable this doesn't seem to be exposed by the Android TV UI, though.
And that support conversation was hilarious
Click to expand...
Click to collapse
That is precisely my point as well. When information that pertains to me is stored, I need to have the option (within reason) of being able to delete it. When such an option is being provided on their Android devices, they only have 2 options on the Nexus player. Save it on the device and a factory reset removes it OR allow the option to delete such info. Not doing either seems like a violation IMO.
I've been looking for a way to solve this exact problem.
I have a 5ghz SSID and a 2.4ghz SSID and I want my nexus player to ALWAYS use the 5ghz, but because I have the same Google account synced to all my Android devices I can never "forget" the 2.4ghz SSID on my nexus player, it always gets restored. To make matters worse, the nexus player prefers the 2.4ghz connection because the signal tends to be stronger.
The only solution I've seen is to dump and disable android backup on every android device I own (2x Nexus Player, 2x Tablets, 3 Phones) to prevent it from syncing both network connections, but it doesn't appear to be possible to JUST remove wifi networks from being synced.
Intersting to read that. Do you at least have a reliable connection when using the 5GHz? (meaning a stable connection over a full week, without connection drops?)
By the way: If *anybody* could shed some light on whether the Marshmallow preview finally enables us to use DFS channels on the Nexus Player, then this would be great. I cannot really flash the preview as it would wipe the player and I'd need hours to set up all my apps again from scratch... and since I know that some people have been testing this, I prefer to ask. Apparently got new neighbors last week who are now polluting the lower 5GHz band which used to be perfectly free... so I wanna switch to the DFS channel frequencies, however the Nexus Player can only connect to the lowest four 5GHz currently, which are the non-DFS ones (all my laptops and even a friend's Samsung tablet from 2013 support the 5GHz DFS channels though)
The Marshmallow changelog contains the following commit: https://android.googlesource.com/platform/frameworks/opt/net/wifi/+/dfc7d48
Has anyone been able to check if this has any effect on the Nexus Player with the latest firmware?
Edit: besides this there's also: https://android.googlesource.com/platform/frameworks/opt/net/wifi/+/6f59b02
For the two people caring: The Nexus Player supports DFS channels and can successfully connect to those after the Marshmallow update.
Mine got the update without me noticing it at all and when I realized it had received the update, I wanted to check the wi-fi and saw it was already connected to my 5GHz wi-fi (which is on one of the upper DFS channels).