> > However, if you just turn off and turn back the wifi on, it doesn't > automatically associate with the AP. > > You need to have more debugging enabled in the framework (WifiService & WifiStateTracker) to understand what is happening in the framework. Log the sequence of driver commands issued to the wpa_supplicant to further figure out if there is something wrong.
> state=SCANNING > D/NetworkStateTracker( 969): setDetailed state, old =DISCONNECTED and > new state=SCANNING > D/wpa_supplicant( 1352): AWEXT: wpa_driver_priv_driver_cmd RXFILTER- > ADD 0 > D/wpa_supplicant( 1352): AWEXT: wpa_driver_priv_driver_cmd BTCOEXSCAN- > STOP > D/ConnectivityService( 969): Dropping ConnectivityChange for WIFI: > DISCONNECTED/SCANNING > I//system/bin/wpa_supplicant( 1351): ioctl[SIOCGIWRATE]: Network is > down > INFO::Network is down! > D/wpa_supplicant( 1352): Scan timeout - try to get results > D/wpa_supplicant( 1352): Failed to get scan results > D/wpa_supplicant( 1352): Failed to get scan results - try scanning > again > Look at why these failures are happening. why are scans failing ? These failures seem to repeat in the rest of the log. How is it showing up in the UI. Is the network getting disabled ? Do you see scan results ? can you select and associate instead of entering the AP details ? -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
