Overview: Using stock Nexus 7 to connect to wireless network; not acting like pre-ICS devices.
Can connect using my EVO4G (CM7.2) and my TF101 (Revolver 3.7), using the "WiFi Advanced Configuration Editor" tool on the market.
For the above devices, the WiFi SSID shows as "Work" (Secured with WEP), with WiFiAdvanced on the device, i would:
1) In Settings/Wireless & Networks: select the network: "Work" (Secured with WEP)
2) enter some garbage text as the key, click connect
3) turn off/on the WiFi
4) open WiFiAdvanced and select the "Work" connection and change the settings (as listed below)
5) then within 5-20 seconds the device would connect (and stay connected) to the network without issue
This procedure is SOP for every non-ICS Android device at the company and works flawlessly.
Additionally, I've used other procedures for attempting to configure the network using the "Add network" button in the Wi-Fi settings area with the same SSID name "Work"; however these settings do not appear to stay in place, as the wireless network "Work" still shows as "Secured with WEP" and will not connect using the 802.1x EAP settings.
However after asking around the office (I work in the Infrastructure team with the Network Admins - one of which has a HTC One X that appears to be having similar connectivity issues to this specific network) turns out that most other ICS devices, and specifically for my new Nexus 7 (Stock 4.1.1, not rooted), the "Work" (Secured with WEP) network is never replaced with the 802.1x EAP version; And after adding the new network or setting up via WiFiAdvanced there is a duplicate "Work" network that shows as "out of range".
On the duplicate network listing, when clicking on the "out of range" "Work" network, it shows Security 802.1x EAP in the details (but no option to Connect). I have more than 2 bars on over 6 WAP's in the distributed wireless network (Cisco wireless devices configured to use rotating keys and assign via DHCP) and have full signal on all my devices.
My Nexus 7 does work very well at my home, running WPA2 (TKIP + AES) at 150MBPS (138mbps reported), and at the coffee shop next to work; leading me to believe it is not a functionality issue with the wireless adapter.
WiFiAdvanced settings for the "Work" network:
SSID:
SSID: Work
BSSID: [no change]
Hidden SSID: [unchecked]
Configuration:
Key Management: [None, IEEE8021X]
Auth Protocols: [Open, Shared]
Group Ciphers: [WEP40, WEP104, TKIP, CCMP]
Pairwise Cipher: [None, TKIP, CCMP]
Security Protocols: [WPA, RSN]
Enterprise Configuration:
EAP: [PEAP]
Phase2: [auth=MSCHAPV2]
Identity: [my domain/username]
AnonymousIdentity: [empty/no-change]
Password: [my domain password]
Client Certificate: [empty]
CA Certificate: [empty]
Private Key: [empty]
Yes, i know there are other threads out there, I've spent the majority of my day researching and testing - to no avail.
Can anyone suggest steps that may assist in getting the Nexus7 able to connect to this network?
UPDATE:
Asof Oct 15, 2012: This issue has been fixed in the 4.1.2 OTA.
jonnyg000 said:
Overview: Using stock Nexus 7 to connect to wireless network; not acting like pre-ICS devices.
Can connect using my EVO4G (CM7.2) and my TF101 (Revolver 3.7), using the "WiFi Advanced Configuration Editor" tool on the market.
For the above devices, the WiFi SSID shows as "Work" (Secured with WEP), with WiFiAdvanced on the device, i would:
1) In Settings/Wireless & Networks: select the network: "Work" (Secured with WEP)
2) enter some garbage text as the key, click connect
3) turn off/on the WiFi
4) open WiFiAdvanced and select the "Work" connection and change the settings (as listed below)
5) then within 5-20 seconds the device would connect (and stay connected) to the network without issue
This procedure is SOP for every non-ICS Android device at the company and works flawlessly.
Additionally, I've used other procedures for attempting to configure the network using the "Add network" button in the Wi-Fi settings area with the same SSID name "Work"; however these settings do not appear to stay in place, as the wireless network "Work" still shows as "Secured with WEP" and will not connect using the 802.1x EAP settings.
However after asking around the office (I work in the Infrastructure team with the Network Admins - one of which has a HTC One X that appears to be having similar connectivity issues to this specific network) turns out that most other ICS devices, and specifically for my new Nexus 7 (Stock 4.1.1, not rooted), the "Work" (Secured with WEP) network is never replaced with the 802.1x EAP version; And after adding the new network or setting up via WiFiAdvanced there is a duplicate "Work" network that shows as "out of range".
On the duplicate network listing, when clicking on the "out of range" "Work" network, it shows Security 802.1x EAP in the details (but no option to Connect). I have more than 2 bars on over 6 WAP's in the distributed wireless network (Cisco wireless devices configured to use rotating keys and assign via DHCP) and have full signal on all my devices.
My Nexus 7 does work very well at my home, running WPA2 (TKIP + AES) at 150MBPS (138mbps reported), and at the coffee shop next to work; leading me to believe it is not a functionality issue with the wireless adapter.
WiFiAdvanced settings for the "Work" network:
SSID:
SSID: Work
BSSID: [no change]
Hidden SSID: [unchecked]
Configuration:
Key Management: [None, IEEE8021X]
Auth Protocols: [Open, Shared]
Group Ciphers: [WEP40, WEP104, TKIP, CCMP]
Pairwise Cipher: [None, TKIP, CCMP]
Security Protocols: [WPA, RSN]
Enterprise Configuration:
EAP: [PEAP]
Phase2: [auth=MSCHAPV2]
Identity: [my domain/username]
AnonymousIdentity: [empty/no-change]
Password: [my domain password]
Client Certificate: [empty]
CA Certificate: [empty]
Private Key: [empty]
Yes, i know there are other threads out there, I've spent the majority of my day researching and testing - to no avail.
Can anyone suggest steps that may assist in getting the Nexus7 able to connect to this network?
Click to expand...
Click to collapse
I'm afraid this is a Jelly Bean bug and not an issue with your particular device. You can see one of the many bug reports here: h t t p://code.google.com/p/android/issues/detail?id=34212 (forum wont let me post links yet ). The link provided has a flashable fix that I can confirm works for the Verizon Galaxy Nexus, but does not seem to work on the Nexus 7 based on the posts.
We basically have to wait for Google to fix this or for another dev to write a Nexus 7 compatible fix. Lastly, this bug fix is not included in custom ROMs, so you have to run it yourself either way. Very annoying on Google's part to break this.
crobles81 said:
I'm afraid this is a Jelly Bean bug and not an issue with your particular device. You can see one of the many bug reports here: h t t p://code.google.com/p/android/issues/detail?id=34212 (forum wont let me post links yet ). The link provided has a flashable fix that I can confirm works for the Verizon Galaxy Nexus, but does not seem to work on the Nexus 7 based on the posts.
We basically have to wait for Google to fix this or for another dev to write a Nexus 7 compatible fix. Lastly, this bug fix is not included in custom ROMs, so you have to run it yourself either way. Very annoying on Google's part to break this.
Click to expand...
Click to collapse
Thanks for the response. That bug looks exactly like the problem.
Apparently this bug has been open for 2 weeks without a fix, not boding well for JellyBean as an iOS competitor.
i uses wifi tether for root and worked with infuse hspa+
jonnyg000 said:
Thanks for the response. That bug looks exactly like the problem.
Apparently this bug has been open for 2 weeks without a fix, not boding well for JellyBean as an iOS competitor.
Click to expand...
Click to collapse
The bug report has been updated with some permissions info that will make it work for the Nexus 7.
crobles81 said:
The bug report has been updated with some permissions info that will make it work for the Nexus 7.
Click to expand...
Click to collapse
So should we flash it or copy it to the system/bin like the one post at the bottom says using root explorer? Do we need to rename that file at all or download as is?
Thanks,
Same problem here. Works fine on ICS device, but no go with 4.1.1 Nexus 7.
Verified permission....still doesn't work
I verified that the wpa_supplicant in /system/bin has the rwxr-xr-x permission.
Still doesn't work the EAP-TLS
Nexus 7 Network Configuration problems
From a less technical standpoint, similar issues:
Clear Wireless Internet Service at office and home.
New Nexus 7 16GB tablet.
No problem with initial network configuration at office. I entered the PW in the identified network and was instantly online.
Network at home, also Clear Wireless, with different name and PW, gave me long delay and repeatedly "Authentication Problem" failure. Two other devices (Android phone and Windows laptop) continued to function normally on the home network.
Call center wasted about an hour and wanted me to call the device manufacturer (ASUS) help call center, which I declined to do. Supervisor was better at English but not at network configuration. A trip to the Clear Wireless brick & mortal location and a temp tech rep there resulted in his ordering a new (replacement) modem for home use.
I could not delete or 'forget' the home network on my Nexus 7 to rescan for a new network configuration for the home network.
Took the Nexus 7 to the office and it again signed me on without a problem, but the home network disappeared while many other nearby business networks showed up.
My next step is to take the device back home and hope that a re-scan of the available networks will re-create a home network that will not result in the "Authentication Problem" failure from what I believe to be its faulty configuration that I was previously unable to modify, delete or 'forget'. I assume that "forget" means to delete or remove.
From the process of elimination, it appears to me that the home network configuration that was automatically created by the device is flawed and unless I can remove or re-configure it am at an impasse. Reconfiguration or removal for a re-scan were not available options when first attempted, unless and until, I get it home and am permitted to do so this time, I may have to return the device to Google under warranty.
Any related or similar problems or suggestions from others would be appreciated.
Thanks
crobles81 said:
The bug report has been updated with some permissions info that will make it work for the Nexus 7.
Click to expand...
Click to collapse
In order to apply the "working" patch from the thread, you need an unlocked bootloader with CWR or to manually install the file in the filesystem with "root" (Superuser) access; either way, you're breaking the stock-ness of the device (not a cool thing to do in a corporate environment that prohibits such actions).
In order for most corporate users (which this bug almost exclusively affects) to use any Android 4.1+ device on the WiFi at their offices, Google will need to fix this with an OTA, and FAST.
I can't believe that google still hasn't patched this. They acknowledged the problem over a month ago and have a fix ready, but nothing has been done. I don't want to unlock my bootloader and root my N7 just to fix a stupid wifi bug that google already knows about. Between this and the random touch sensitivity issues all I can say is that google is lucky I'm already past the full refund period, or they would be getting this tablet back.
ravage485 said:
I can't believe that google still hasn't patched this. They acknowledged the problem over a month ago and have a fix ready, but nothing has been done. I don't want to unlock my bootloader and root my N7 just to fix a stupid wifi bug that google already knows about. Between this and the random touch sensitivity issues all I can say is that google is lucky I'm already past the full refund period, or they would be getting this tablet back.
Click to expand...
Click to collapse
I am not sure about fix for EAP-TLS. I tried all of the workarounds and it does not work. Perhaps that is why patch is still not issued.
6opuc said:
I am not sure about fix for EAP-TLS. I tried all of the workarounds and it does not work. Perhaps that is why patch is still not issued.
Click to expand...
Click to collapse
Same problem in my work wifi network with the Nexus 7, my Nexus One and other iphone or android devices working fine.
I do not want to root yet my one day old device to avoid problems with the warranty.
So bad that google does not pay attention to these problems that are really annoying for the new users :/
Managed to get it working
jonnyg000 said:
Overview: Using stock Nexus 7 to connect to wireless network; not acting like pre-ICS devices.
Can connect using my EVO4G (CM7.2) and my TF101 (Revolver 3.7), using the "WiFi Advanced Configuration Editor" tool on the market.
For the above devices, the WiFi SSID shows as "Work" (Secured with WEP), with WiFiAdvanced on the device, i would:
1) In Settings/Wireless & Networks: select the network: "Work" (Secured with WEP)
2) enter some garbage text as the key, click connect
3) turn off/on the WiFi
4) open WiFiAdvanced and select the "Work" connection and change the settings (as listed below)
5) then within 5-20 seconds the device would connect (and stay connected) to the network without issue
This procedure is SOP for every non-ICS Android device at the company and works flawlessly.
Additionally, I've used other procedures for attempting to configure the network using the "Add network" button in the Wi-Fi settings area with the same SSID name "Work"; however these settings do not appear to stay in place, as the wireless network "Work" still shows as "Secured with WEP" and will not connect using the 802.1x EAP settings.
However after asking around the office (I work in the Infrastructure team with the Network Admins - one of which has a HTC One X that appears to be having similar connectivity issues to this specific network) turns out that most other ICS devices, and specifically for my new Nexus 7 (Stock 4.1.1, not rooted), the "Work" (Secured with WEP) network is never replaced with the 802.1x EAP version; And after adding the new network or setting up via WiFiAdvanced there is a duplicate "Work" network that shows as "out of range".
On the duplicate network listing, when clicking on the "out of range" "Work" network, it shows Security 802.1x EAP in the details (but no option to Connect). I have more than 2 bars on over 6 WAP's in the distributed wireless network (Cisco wireless devices configured to use rotating keys and assign via DHCP) and have full signal on all my devices.
My Nexus 7 does work very well at my home, running WPA2 (TKIP + AES) at 150MBPS (138mbps reported), and at the coffee shop next to work; leading me to believe it is not a functionality issue with the wireless adapter.
WiFiAdvanced settings for the "Work" network:
SSID:
SSID: Work
BSSID: [no change]
Hidden SSID: [unchecked]
Configuration:
Key Management: [None, IEEE8021X]
Auth Protocols: [Open, Shared]
Group Ciphers: [WEP40, WEP104, TKIP, CCMP]
Pairwise Cipher: [None, TKIP, CCMP]
Security Protocols: [WPA, RSN]
Enterprise Configuration:
EAP: [PEAP]
Phase2: [auth=MSCHAPV2]
Identity: [my domain/username]
AnonymousIdentity: [empty/no-change]
Password: [my domain password]
Client Certificate: [empty]
CA Certificate: [empty]
Private Key: [empty]
Yes, i know there are other threads out there, I've spent the majority of my day researching and testing - to no avail.
Can anyone suggest steps that may assist in getting the Nexus7 able to connect to this network?
Click to expand...
Click to collapse
Hope this helps ...
Managed to get nexus 7 connected to 802.11 wifi. So now Nexus 7 automatically switch between home wifi and corporate wifi. To have corporate wifi connectivity I needed to add the CA certificate (Ask your network administrator for it) in the tablet directory structure. No need to root the device for that. just follow instructions at the following instructions:
To install a certificate from your tablet's internal storage:
Copy the certificate or key store from your computer to the root of your device's internal storage (that is, not in a folder).
Go to Settings > Personal > Security > Credential storage > Install from storage.
Touch the filename of the certificate or keystore to install. Only certificates that you haven't already installed are displayed.
If prompted, enter the key store password and touch OK.
Enter a name for the certificate and touch OK.
Typically, a CA certificate included with a client certificate is installed at the same time. You can also install separate CA certificates using the same steps.
If you have not already set a pattern, PIN, or password for your device, you’re prompted to set one up. The type of lock that's acceptable may be predetermined by your system administrator.
You can now use the certificate that you installed when connecting to a secure network or for client authentication with Email, Chrome, and third-party apps. After a certificate is installed successfully, the copy in storage is deleted. (source: support.google.com)
All items as quoted above were entered except for phase 2 item.
Security type: WPA2-enterprise
Network authentication method: PEAP
fast Roaming enabled with PMK caching
Encryption type AES
EAP may work, but not TLS
xPBA said:
Hope this helps ...
Managed to get nexus 7 connected to 802.11 wifi. So now Nexus 7 automatically switch between home wifi and corporate wifi. To have corporate wifi connectivity I needed to add the CA certificate (Ask your network administrator for it) in the tablet directory structure. No need to root the device for that. just follow instructions at the following instructions:
To install a certificate from your tablet's internal storage:
Copy the certificate or key store from your computer to the root of your device's internal storage (that is, not in a folder).
Go to Settings > Personal > Security > Credential storage > Install from storage.
Touch the filename of the certificate or keystore to install. Only certificates that you haven't already installed are displayed.
If prompted, enter the key store password and touch OK.
Enter a name for the certificate and touch OK.
Typically, a CA certificate included with a client certificate is installed at the same time. You can also install separate CA certificates using the same steps.
If you have not already set a pattern, PIN, or password for your device, you’re prompted to set one up. The type of lock that's acceptable may be predetermined by your system administrator.
You can now use the certificate that you installed when connecting to a secure network or for client authentication with Email, Chrome, and third-party apps. After a certificate is installed successfully, the copy in storage is deleted. (source: support.google.com)
All items as quoted above were entered except for phase 2 item.
Security type: WPA2-enterprise
Network authentication method: PEAP
fast Roaming enabled with PMK caching
Encryption type AES
Click to expand...
Click to collapse
I see that your authentication works, but for example, my school uses CA certs for their 801.11x network that work with TLS as a phase 1.
Successfully installing the CA cert and properly identifying the signal do absolutely nothing for my tablet other than give it an authentication loop.
Have tried multiple times at re-installing the certificate to see if it was just not done right the first time to no avail.
It's the TLS authentication library on the device (at least that's what the code.google bug report page says).
I'm not sure if this will really help those of you at work, but I was having authentication issues on my home network as well. I discovered that I was able to get around the authentication bug by connecting via WPS (Wifi protected setup). Just go to wifi settings and hit the symbol that looks like two arrows in a circle. If your router supports WPS it should have a button with the same symbol. Just press and hold until a light comes on and you should be able to connect just fine.
Not sure if it's related but after updating to 4.1.2 I can connect to my work wifi now that uses 802.1x with PEAP=MXCHAPv2. FINALLY!
biggiestuff said:
Not sure if it's related but after updating to 4.1.2 I can connect to my work wifi now that uses 802.1x with PEAP=MXCHAPv2. FINALLY!
Click to expand...
Click to collapse
I can confirm that updating to 4.1.2 did solve my problem with connecting to the Wi-Fi at my company. We use 802.x PEAP MVSCHAPv2 :good:
biggiestuff said:
Not sure if it's related but after updating to 4.1.2 I can connect to my work wifi now that uses 802.1x with PEAP=MXCHAPv2. FINALLY!
Click to expand...
Click to collapse
Yup, the 4.1.2 OTA fixed it :highfive: .. only took the Android team 3+ months to release a patch after root cause was identified.. how agile of them..
'Tis a shame corporate has since banned the use of N7's for business use because of the WiFi issue in Stock 4.1.1. :silly:
I just had to submit a re-eval request on 4.1.2+ in order to stop blocking the N7 MAC's from the network.. ( that should only take about 1-4 MORE months to get the device re-reviewed, approved, and enabled.. yay ).
I am confused on how you got your Nexus 7 fixed. My work's wifi network also uses Dynamic WEP 802.1x, but even after updating to V4.1.2 I still can't connect. (Although I could with my old Galaxy Tab running V2.2)
Encryption: WEP
Security: 802.1X EAP
EAP Method: PEAP
Phase 2: MCHAPv2
The network shows up as "Secured with WEP", but if I try to create an identically named network with 802.1x settings (or start with a bogus password for WEP and try to use the WifiACE app to add the 802.1x settings), I still just end up with an identically named network that is always "Not in range".
What did you do after the V4.1.2 update to get it to work?
Related
Hi everyone,
I just got a router today and set it up with a hidden SSID.
I have no problem connecting to broadcasted SSID, but it won't let me connect to this hidden SSID router.
Steps taken:
1. Remembered the SSID
2. Entered the WPA password
What happens next is the Aria just keeps scanning for available wifi. It doesn't connect automatically to the hidden SSID (home). Neither did it allow me to manually connect by clicking on 'home'. Instead, it gave me an option to Forget the network if I click on it.
I noticed there are several threads that belongs in other forums in XDA but none of them answers this question.
Any advice/suggestions? Greatly appreciate it!
Thanks everyone!
Update:
By the way I read a thread that we have to add the device MAC address to the routers' filter. Did that but still won't connect automatically. Neither does it allow me to connect manually.
Clicking on 'home' just gave me the same options:
1. Forget network
2. Change password
If only it would give me a third option:
3. Connect
That would be great!
emigre said:
Update:
By the way I read a thread that we have to add the device MAC address to the routers' filter. Did that but still won't connect automatically. Neither does it allow me to connect manually.
Clicking on 'home' just gave me the same options:
1. Forget network
2. Change password
If only it would give me a third option:
3. Connect
That would be great!
Click to expand...
Click to collapse
You did not mention which Aria ROM you are using.
Did you type it exactly the same? Its case sensitive.
I've turned off MAC filtering because some routers have a max that can be in the list, preventing the later ones from connecting. I've had no problems connecting to both my Westell (home) and Netgear (work) routers with hidden SSID's after turning off MAC filtering using stock ROMs (2 & 12)
Sent from my HTC Liberty using XDA App
bunky213 said:
I've turned off MAC filtering because some routers have a max that can be in the list, preventing the later ones from connecting. I've had no problems connecting to both my Westell (home) and Netgear (work) routers with hidden SSID's after turning off MAC filtering using stock ROMs (2 & 12)
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
I've used mac filtering before with a hidden ssid and never had any problems connecting. I'm guessing maybe he typed the ssid wrong. The devices don't care if it's hidden or not. What matters is it it's typed correctly and that it's in range to see it.
Thanks for the enthusiastic response everyone!
Sorry I forgot to mention my ROM. I'm using Liberated R12 here.
I've undertaken all these steps:
1. Case sensitive SSID is correct (all lowercase which is correct)
2. password is 100% correct
3. wifi is in range (sat right next to it) - I'm using D-link router
These happened:
1. Range not found
2. Can't connect manually
So anyway, I've decided to broadcast SSID and password protect it instead. Also removed MAC filtering. No problem now.
However just for future reference, let's get to the bottom of this!
By the way, I noticed that the Aria is receiving weaker signals than the iPod and Blackberry that is also within the same range distance. Any thoughts on this?
Thanks again guys!
Greetings all,
I just purchased the aria and am having a
variation on this problem. I have successfully
gotten my aria to connect to my hidden SSID
network. However, if I leave the range of the
and then return, it will not connect automatically.
If I try to add a network of the correct name, it
will suddenly find my network. I have version
2.1-update1 on my phone and I suspect this to
on the phone end since my wife's phone does not
have this problem and they were purchased at the
same time. Thank you for your time.
Keith
Very well could be your phone. On stock rom and even cm6 I had no problem connecting to a hidden network. It was with the cm7 nightlies that I had to turn SSID broadcasts back on.
Sent from my Liberty using XDA App
I have done about everything. I can connect to my Android phone (using tether), my house, other open networks PERFECTLY, but unfortunately my gym uses a WEP network and I cannot get my tablet to connect to their network.
I have rebooted, forgot the network and set it up again (a million times) I have done EVERYTHING. My Android phone can connect to the gym network perfectly. Any suggestions?
Anyone have any suggestions? Does anyone connect to a WEP secured network and know that this works?
I had the same problem and found out the solution changing some values in the set up router.
Sent from my X10i using XDA App
I'm connected to our home browser which uses WEP. I think it's a matter of settings/wireless and networks/Wi-Fi settings/add wi-fi network. Once you are in the 'add' page, it asks about security, you should be able to input the data.
Jim
I have had same problems, honeycomb handles WPA and WPA2 enterprise networks weird compared to gingerbread. I have had problems with connections too. Try to use the "wifi advanced config editor" and make sure settings are correct for that network (after you attempt to connect to it in settings app). I hope google fixed this problem in ICS or i will be furious. Most of these kind of bugs are laziness on coders or just people who missed lines of code and then don't want to release an update (or wait till next update release rather than a hotfix).
1337GameDev said:
I have had same problems, honeycomb handles WPA and WPA2 enterprise networks weird compared to gingerbread. I have had problems with connections too. Try to use the "wifi advanced config editor" and make sure settings are correct for that network (after you attempt to connect to it in settings app). I hope google fixed this problem in ICS or i will be furious. Most of these kind of bugs are laziness on coders or just people who missed lines of code and then don't want to release an update (or wait till next update release rather than a hotfix).
Click to expand...
Click to collapse
So just to make sure I understand...
Basically the way I originally connected was that I let the tablet scan for networks, and it found the gym network. Once it found the gym network, I selected it and entered the password. I left the proxy and DHCP settings alone and pressed connect, and cannot get it to connect.
What you are suggesting that I do is delete the network, and add the network MANUALLY (where I input securtiy, SSID, passcode, etc.).. Is that right?
So I installed the Advanced Wifi tool, to no avail.
Here is the funny thing. I have a Samsung Epic 4G phone which uses Gingerbread, and it connects to the WEP just fine. I installed the Advanced Wifi on there as well, and went through the settings that were autoconfigured for the gym. Each setting matched my tablet perfectly, yet my tablet cannot pull an IP address, but my phone can.
I'm having the same issue. Thought it was the tab, just received replacement and still a No Go! Every other device in my house connects to this network. And the Gtab also connected perfectly until recently... no clue what to do now.
I can't connect to my corporate wifi. The following process worked on my Kindle Fire, and dozens of phones of others in the office:
Add a new connection with hidden SSID
EAP = PEAP
Phase 2 = MSCHAP (not MSCHAPv2)
CA Certificate (got it, installed it, not expired)
domain\usr
pwd
Run WiFi Advanced Configuration Editor
Key Mgmt, uncheck WPA-EAP (IEEE8021X checked)
Enterprise Configuration, re-enter pwd.
Turn WiFi off, back on.
Ignore the SSID secured with WEP.
Done.
This process does not work on my 8GB Nexus 7. I've done the process enough times on my KF and other people's phones to know I'm not doing it differently on the N7. Yet, it doesn't connect. Ever. I sit right across from the AP. Also, I had someone else who's done this a dozen times before also try. No dice there either.
Any idea why I can't get connected?
<noob_shield>I found no (meaningful) results searching this forum for "wifi certificate" and a few other searches.</noob_shield>
Are you in a domain and running through a proxy server? If so try just joining the network normally using your domain\uname letting the cert install automatically then long holding the wifi connection modify connection check advanced then add the proxy settings, worked for me...
Sent from my Nexus 7 using xda app-developers app
_DrG_ said:
Are you in a domain
Click to expand...
Click to collapse
Yes, there's a domain. I'm using my domain acct as the identity/password
and running through a proxy server?
Click to expand...
Click to collapse
No proxy server.
If so try just joining the network normally using your domain\uname letting the cert install automatically
Click to expand...
Click to collapse
The SSID is hidden. I have to start by manually adding the network. Considering that I can't get to connect to that network at all, I'm not sure how to go about "joining the network normally." I'll try it without specifying/bringing my own certificate, and see if one is installed automagically. IIRC, iPad users don't have to manually copy the cert onto their tablet.
I'm having the same issue connecting a Nexus 7" on Jelly Bean to our wifi using a cert. I'm using the exact same settings I use on my Droid Razr Maxx (running ICS) and it connects no problem. If I figure it out I'll post up, but I have a feeling it's a Jelly Bean issue. On ICS when I install a cert it no longer shows in storage, however on Jelly Bean after installing it leaves the cert in storage. Not sure if maybe its not installing it completely, or if that's just how Jelly Bean will do it on all devices. Another thing I noticed is it strips the name of cert, whereas in ICS it leaves the cert name assigned. I'm going to mess around with it now.
This has been discussed and determined to be most likely a jelly bean issue.
Sent from my Nexus 7 using xda app-developers app
Lame answers from Google and ASUS
I tried to get the corporate network connectivity issue resolved through support at Google and ASUS. Google's response was to ask my IT guys to, "use mac filtering on the router". ASUS's response was to reset the tablet, when that did not work, Russell on their support line said that, "the Android OS does NOT support 802.1x EAP on the Nexus 7". This seems like a deal-breaker for the Nexus 7, buyer beware.
I've been having problems trying to connect my friend's Nexus 7 (32Gb) to my home wifi. I tried 4 (yes 4) wireless routers, and it refused to connect to any of them. It would prompt for my (WPA2) login credentials, then spend a few minutes trying to connect, then give up and try another access point. It would mark the AP just tried as "avoided poor internet connection".
The routers I tried were:
- Belkin Play Max N600 HD
- Buffalo WHR-G54S
- Draytek Vigor 2920n
- O2 Broadband wireless box 5
The signal strength from all of them was shown as excellent. I tried the O2 wireless box with WEP encryption instead of WPA2 and that didn't help.
I was able to connect both a Samsung Q330 laptop and a Galaxy S3 to all of these routers, so they all appear to be working fine.
As I'm shortly planning to buy a Nexus 7 I'm keen to understand what sort of problem might stop it connecting to my routers!
Any ideas?
avoided poor internet connection
Hi,
I have the same issue and i foud that it is due to the inferior frequency of my router wich is 2.4ghz.
so i you did found a solution please share it,thanks in advance.
nabs2048 said:
Hi,
I have the same issue and i foud that it is due to the inferior frequency of my router wich is 2.4ghz.
so i you did found a solution please share it,thanks in advance.
Click to expand...
Click to collapse
All routers use 2.4 GHz unless they are branded/advertised as being 5 GHz. The Nexus doesn't even support 5 GHz. The warning is more about the actual internet connection anyway. As for removing this warning, you can easily disable it under advanced WiFi settings.
Sent from my SGH-I777 using xda premium
I subsequently acquired my own Nexus 7 and had no problem connecting it all of the routers that my friend's Nexus 7 wouldn't connect to. I'm guessing that I was running a newer ROM. I still have no idea why my friend's unit wouldn't connect
Your friend should return his faulty N7 for a replacement.
If you can access the router, do a reset or reboot, sometimes a refresh would get the "hand shaking" working again, switch to an alternate wireless channel as it could be interference from other nearby routers.
after some research i found this .
and for the "avoid poor internet connection" in the advanced menu ,in 4.1.1 the is no such option in the menu .
and i found this .
http://productforums.google.com/forum/#!msg/mobile/Y33mbUPrbsU/tjjHaIRbPAQJ
and this
http://code.google.com/p/android/issues/detail?id=40065
nabs2048 said:
after some research i found this .
and for the "avoid poor internet connection" in the advanced menu ,in 4.1.1 the is no such option in the menu .
and i found this .
http://productforums.google.com/forum/#!msg/mobile/Y33mbUPrbsU/tjjHaIRbPAQJ
and this
http://code.google.com/p/android/issues/detail?id=40065
Click to expand...
Click to collapse
You don't see it right below the wifi sleep options?
Sent from my Nexus 7 using Tapatalk HD
korockinout13 said:
You don't see it right below the wifi sleep options?
Click to expand...
Click to collapse
Your custom rom is not the same as the OP. There is no option you suggest on a stock rom.
I had the same problem with my PC...
usually the problem is with the router, restart the router,
Avoid poor connections FIX without ROOT
itm said:
I've been having problems trying to connect my friend's Nexus 7 (32Gb) to my home wifi. I tried 4 (yes 4) wireless routers, and it refused to connect to any of them. It would prompt for my (WPA2) login credentials, then spend a few minutes trying to connect, then give up and try another access point. It would mark the AP just tried as "avoided poor internet connection".
The routers I tried were:
- Belkin Play Max N600 HD
- Buffalo WHR-G54S
- Draytek Vigor 2920n
- O2 Broadband wireless box 5
The signal strength from all of them was shown as excellent. I tried the O2 wireless box with WEP encryption instead of WPA2 and that didn't help.
I was able to connect both a Samsung Q330 laptop and a Galaxy S3 to all of these routers, so they all appear to be working fine.
As I'm shortly planning to buy a Nexus 7 I'm keen to understand what sort of problem might stop it connecting to my routers!
Any ideas?
Click to expand...
Click to collapse
SOLUTION
Figured it out...go to the WiFi settings, hit the menu key and choose "Advanced", and uncheck "Avoid poor connections".
There are lots of android phones without the above mentioned option(The place where you can uncheck your "Avoid poor connections" )
If you're in that case I've got an alternate for you
1. run command prompt and type ipconfig
2. note down your ip address
3. now what you do is change the last digits after the last point and give the command
ping 192.168.1.xx(changing the last digit or last two digits)
it'll say pinging and BLAH BLAH BLAH
It'll give details about the sent and received packets of data
And also LOST packets
NOTE: If the lost =0( 0 % lost)
4. Then note down the ip address which you've given after the command ping **192.168.1.xx**
if the lost= (100 % lost) or may be some other percentage of lost... it means there is some loss of data packets
so never note down that..... repeat the process 3. changing the last digits of your ip address
5. Now once the lost percentage is 0 %
6. go to settings->Wi-Fi-> And long press the network to which you wanna connect your device
7. Choose modify network
8. Enter the password(If there is any and do not press save)
9. Enable show Advanced options
10. Change the ip settings to static
11. Enter the ip address which you've noted down in steps 3 & 4
12. Enter the noted ip address in the ip address
13. Also Enter the gateway address in the column below which you find from your cmd prompt giving the command ipconfig
14. The network prefix length ,DNS 1 And DNS 2 Will be automatically assigned
15. Now click Save
Thats it .......You're Done
incase if the Avoided poor connection occurs again repeat the steps from 6 till the end giving the same ip address which you've noted down
ENJOY ! ! ! ! !
I've fixed it
Hello.
I fixed this bug, it isn't poor conection... it is an error about dhcp server in the android 4.x
First you need to download and install ipconfig app from aptoide
So you need to try to conect to your network, while it is showing obtaining ip adress, you should go to ipconfig app (be as fast as posssible)
Finally you should find your ip number and your gateway, if you don't, click in refresh.
Now go to settings and long click into your network, so click in advenced settings and change dhcp to static IP, here are the recommended settings:
IP- get in ipconfig
Gateway- it will automatically set, the most used is 192.168.1.1
Prefix- 22 or 24
Subnet mask- 255.255.255.0
Dns1- 8.8.4.4
Dns2- 4.4.4.4 (no need to set)
I wanna develop an app to do it automacally, but I need help... I'm pretty noob, I've got only 14 years old
Edited: Oops, I didn't saw your solution, anyway it doesn't work on all routers cause some routers are set to another ip
I'm glad to help you
Antonio Harres
Somebody please delete my previous thread (wrong forum), thank you: http://forum.xda-developers.com/showthread.php?t=2707468
------------------------------------
WiFi connects to my router and stays connected at excellent signal strength without any trouble. Internet connection however, always disappears after a minute or so. Then my Dolphin Browser either keeps loading a website forever or gives me some error like "Webpage not available". Same story with stock or any other browser. I'm not sure since how long I have had this issue. It surely existed already when my phone came back from warranty service (and I had sent it there because of very short range of WiFi commonly known problem which they fixed by giving the phone new hardware). I think that upgrade to Android 4.2.2 might have caused my problem, but it was such a long time ago that I don't remember now (I don't use/need WiFi that much, mobile data internet is enough for me).
What I've tried so far:
-rebooting phone and router obviously
-factory formatting the phone
-WiFi analyzer app
-changing all the network parameters and re-setting it up
-WPS connecting
-playing with all the WiFi settings on my phone (proxy settings, ip settings, wifi optimization and other)
-finally, today I unlocked bootloader, rooted and installed custom ROM hoping it'd help (but it didn't and now I lost my warranty lol)
What I have:
HTC One X Endeavor
Android 4.2.2 HTC Sense 5.0
Android Revolution HD 33.1
3.1.10-g7f360be Kernel version
TP-LINK
N750 Wireless Dual Band Gigabit Router
Model No. TL-WDR4300
I'm thinking about installing other ROM, some that works on Android 4.0 or KitKat, could it help?
Oh, and I should add that two different notebooks, Galaxy S4, S3 mini, Xperia X10 and a tablet all work fine with this network :>
I can provide any screenshots, photos, names of devices etc., just tell me what is needed.
HELP!
I have a similar problem with my device, but I just reset my router and it's fine. Maybe your problem is that your phone doesn't receive an ip address. You can check out if you have received an address via settings->wi-fi-> advanced, and check the 'ip address'. If it says ' not available, reset your router and your phone's wi-fi until you get one.
|>/\nte said:
I have a similar problem with my device, but I just reset my router and it's fine. Maybe your problem is that your phone doesn't receive an ip address. You can check out if you have received an address via settings->wi-fi-> advanced, and check the 'ip address'. If it says ' not available, reset your router and your phone's wi-fi until you get one.
Click to expand...
Click to collapse
Nopes, IP reception is fine. Here are all my settings:
Status: Connected
Signal strength: Excellent
Link speed: 26Mbps
Security: WPA/WPA2 PSK
IP address: 192.168.0.101
Proxy settings: None
IP settings: DHCP
As I said earlier, I have been playing with all the network settings above as well as with the phone WiFi advanced settings and it didn't change anything.
Hm…it may be a hardware problem.