I continue to see scan failures in the wpa_supplicant log, investigate that. Look at how the interaction with the supplicant directly from the wpa_cli works.
What happens when you load the driver, start the supplicant and initiate connection with a configured network from adb shell interface: # stop # insmod driver # setprop ctl.start wpa_supplicant # wpa_cli reconnect Does it connect right away ? If not, the problem is not in the framework. how does your wpa_cli scan_results and wpa_cli list_networks look like ? Is your AP hidden ? The settings list of networks is just a merge of configured networks and scanned results. Duplicate networks indicate there are duplicate configured networks (probably came when you added more networks with existing out of range networks). An out of range network indicates scan results are probably failing. I also see failures where the WifiMonitor seems to be failing to establish a connection to the wpa_supplicant, but this could be a temporary failure before it re-establishing connection. I/WifiHW ( 969): Interface name = /data/system/wpa_supplicant/wlan0 E/WifiHW ( 969): Unable to open connection to supplicant on "/data/system/wpa_supplicant/wlan0": No such file or directory Find out the exact sequence of supplicant commands from the framework with the first attempt as compared to the second attempt. Try that on the wpa_cli to see if its a framework issue or one with driver/supplicant interaction. Irfan On Wed, Nov 24, 2010 at 6:23 PM, Elvis Dowson <[email protected]>wrote: > Hi, > In summary, what I can observe is as follows: > > a. First AP association attempt works fine, and I'm able to browse the > internet. However, an extra AP with the same SSID gets displayed in > the list of scanned APs. > > b. After turning off and turning back the wifi on from the settings > control panel, the system tries to scan but does not display any AP > SSIDs. It also doesn't automatically associate with the previously > associated SSID. > > If you manually enter the AP SSID, it immediately connects, however, > it displays additional duplicate AP SSIDs shown in image "10 - Attempt > 02 - Duplicate AP SSIDs during second association after wifi > restart.jpg". If you wait and give it some more time, it keeps > scanning, and if you keep scrolling the scanned AP list, it keeps > adding and removing AP SSIDs, some actual ones around (neighbours > SSIDs which are very weak, and disappear quickly), and a lot of > duplicate AP SSIDs (i.e. mutilple AP SSIDs with name Olympus2), as > shown in image 11, 12 & 14. > > How can I troubleshoot this issue and get android wifi to connect > automatically to the AP after turning off and turning the wifi back > on? > > Elvis Dowson > > -- > unsubscribe: > [email protected]<android-porting%[email protected]> > website: http://groups.google.com/group/android-porting > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
