Hi Irfan,
On Fri, Nov 26, 2010 at 9:07 AM, Irfan Sheriff <[email protected]> wrote:
> 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.
>
I found out a specific difference that might narrow down the cause.
In my init.rc, I have defined a service called ifcfg_ralink to run ifconfig
to bring up the wlan0 interface:
service ifcfg_ralink /system/bin/ifconfig wlan0 up
group system wifi
disabled
oneshot
For testing this, I switched off wifi, and rebooted the device. This causes
the device to start without automatically attempting to reconnect wifi and
connecting to the AP.
I noticed service ifcfg_ralink executing, after which it started executing
service wpa_supplicant:
init: process 'wlan_loader', pid 1219 exited
init: starting 'ifcfg_ralink'
init: waitpid returned pid 1226, status = 00000000
init: process 'ifcfg_ralink', pid 1226 exited
SYNC - End of SCAN, restore to channel 1, Total BSS[01]
SCAN done, resume MSDU transmission ...
init: starting 'wpa_supplicant'
Driver auto reconnect to last OID_802_11_SSID setting - , len - 0
I think when I gave the wpa_cli reconnect command in the previous attempt,
it gave the following error probably because I didn't run service
ifcfg_ralink for bringing the wlan0 interface up:
Using interface 'wlan0'
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or
directory
So, during reconnect, I probably need an extra command to be issued to bring
up the wlan0 interface:
# insmod rt3070sta.ko
# setprop ctl.start ifcfg_ralink
# setprop ctl.start wpa_supplicant
# wpa_cli reconnect
I'll try that out and see if it works.
Elvis Dowson
--
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
