Very useful information, James. The most interesting quote from the second link is this:
=== The partial fix for getting Android 2.2 to connect to 802.1x secured network on Aruba Aps was to disable 'Wireless Multimedia U-APSD (WMM-UAPSD) Powersave' in the advanced properties of the SSID profile. This is enabled by default. In the 802.1x Authentication Profile Changing the 'WEP Key Message Retry Count' value to 3, the 'Interval between WPA/WPA2 Key messages' to 3000msec, the WPA/WPA2 Key Message Retry Count' to 3, and disabling 'Opportunistic Key Caching' seems to make things more reliable. These are the new defaults in ArubaOS 5.x, but were set lower by default in earlier versions. We have also found that not using an anonymous identity makes authentication more reliable, so it seems there could be an issue both in the WLAN driver and in the 802.1x supplicant. We do still have to tell Android to forget the network then re-enter my credentials if WLAN is turned off though... === It is difficult following the "alphabet soup" of acronyms. If the above posting is correct, part of the problem appears to be an issue with WMM-PS and, more specifically, WMM-UAPSD. These are features I would expect on any multimedia mobile device to save battery life. Disabling WMM would disable the power saving features, but also disable QoS. Disabling WMM-UAPSD could reduce battery life on any device on that WLAN that properly supports WMM-UAPSD. As I understand it, a WMM-UAPSD supported AP buffers data for devices and releases the data in response to a trigger packet from the client. This enables the client to periodically enter a low power state, preserving battery life. === Glossary: WMM: Wi-Fi Multimedia certification used for QoS on a Wi-Fi network WMM-PS: Wi-Fi Multimedia Power Save certification WMM-UAPSD: Wi-Fi Multimedia Unscheduled Automatic Power Save Delivery QoS: Quality of Service tagging on a network used to prioritize voice & video traffic. === Bruce Osborne Network Engineer - Wireless & NAC Liberty University -----Original Message----- From: James J J Hooper [mailto:[email protected]] Sent: Wednesday, September 29, 2010 3:42 PM Subject: Re: Android 2.2 disappointing on the secure WLAN- is it just us? On 29/09/2010 18:55, Lee H Badman wrote: > We have three cases of Droid smartphones that worked wonderfully on our > 802.1x/WPA2 WLAN on Android 2.1 operating system. Since going to 2.2 with > the devices, getting them to connect to the secure wireless network is > almost impossible. Open networks are OK. > There are known issues: http://code.google.com/p/android/issues/detail?id=8804 http://www.google.co.uk/support/forum/p/android/thread?tid=7f71ff06702e39e1 We have found that Android 2.2 "works" on our WPA2/AES eduroam, but roaming and re-auth are not reliable. HTC build 2.10.405.2 appears to improve things, but it's still not brilliant... Regards, James -- James J J Hooper Network Specialist Information Services University of Bristol http://www.wireless.bristol.ac.uk -- ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
