Hello Nail, Sorry for the late response. I took some vacation .... I am not sure exactly in which order you are trying to port the Wifi to your device.
In general I would recommend to make sure that your needed functionality is running on native before you do any integration on Java level. You might want to check in the Wifi native code in which cases (if not done yet) the error " Unable to open connection to supplicant on" is reported. Please, keep me updated about your progress. Thx, Roman -- Roman Baumgaertner Sr. SW Engineer-OSDC ·T· · ·Mobile· stick together The views, opinions and statements in this email are those of the author solely in their individual capacity, and do not necessarily represent those of T-Mobile USA, Inc. On 4/14/09 2:47 AM, "nail" <s894...@gmail.com> wrote: > > dear Roman, > > i found the wlan interface which wpa_supplicant create is locate at > root dir, i.e. /wlan0, > > so, i try to use "wpa_cli -p /wlan0", it can connect to > wpa_supplicant :-) > > next step i need to let android wifi UI has the same behavior as > wpa_cli command, > > i modify some code of "Framework/base/services/java/com/android/server/ > Wifiservice.java > " and "hardware/libhardware_legacy/wifi/wifi.c", > > after execute, i got following error: > > "D/WifiHW ( 2127): Unable to open connection to supplicant on "/ > wlan0": Connection refused", > > i think this is some kind of "permission deny", and the user:group of / > waln0 is root:wifi, > > do you have any idea about this issue :-( > > On 4月14日, 上午8時42分, Roman <roman.baumgaert...@t-mobile.com> wrote: >> Hi Nail, >> >> Here is an article which might help >> >> http://w1.fi/wpa_supplicant//devel/driver_wrapper.html >> >> Of course you still have to find out how to hook up your code exactly >> to the Androidwifisupport. >> >> Have you tried already to install a common LinuxWifisupplicant on >> your board? >> >> --Roman >> >> On Apr 12, 9:26 pm, nail <s894...@gmail.com> wrote: >> >> >> >>> dear Roman, >> >>> sorry for i have not explain my question enough, and i will be glade >>> to explain it again: >> >>> my goal is to enable the "intel 3945 abg"wificomponent on our x86 >>> target platform >> >>> so my first step is to enable corresponding kernel config and built-in >>> corresponding firmware >> >>> my next step is trying to build wpa_xxx utility into android to >>> supportwifisetting, >>> these utility include wpa_cli, wpa_supplicant, ... , etc. >> >>> after that, i try to config wpa_supplicant.conf, and all the contents >>> are shown below: >> >>> ===================================================================== >>> wpa_supplicant.conf >> >>> update_config=1 >>> ctrl_interface=wlan0 >>> eapol_version=1 >> >>> # ap_scan=1: wpa_supplicant initiates scanning and AP select >>> ap_scan=1 >>> fast_reauth=1 >> >>> network={ >>> ssid="simple" >>> psk="very secret passphrase" >>> priority=5 >> >>> } >> >>> # Wildcard match for SSID (plaintext APs only). >>> #This example selects any >>> # open AP regardless of its SSID. >>> network={ >>> key_mgmt=NONE} >> >>> =========================================================================== >> >>> and I enablewifiusing the following command written in >>> init.rc: >>> ======================================================= >>> "mkdir /data/misc/wifi0770wifiwifi >>> mkdir /data/misc/wifi/sockets 0770wifiwifi >>> mkdir /data/system/wpa_supplicant 0770wifiwifi >>> mkdir /data/misc/dhcp 0770 dhcp dhcp >>> chown dhcp dhcp /data/misc/dhcp >> >>> ifup wlan0 >> >>> service wpa_supplicant /system/bin/logwrapper /system/bin/ >>> wpa_supplicant -iwlan0 -c/system/etc/wifi/wpa_supplicant.conf -dd >>> groupwifi >> >>> service wlan_dhcpcd /system/bin/dhcpcd wlan0 " >> >>> =================================================================== >> >>> after all steps, i can connect to the newwork , and get IP >> >>> but i don't know which AP thewifihas connected, it is >> >>> configured automatically. >> >>> althoughwifihas connected, but the "settingwifi" section in the >>> android UI >> >>> does not know this inform, i.e. i can not enablewifiselection on >>> android UI >> >>> so, my next step is to let android UI knows that thewifi >> >>> has enabled, i.e. i need to connect upper and below together >> >>> BTW, when i type iwconfig, it shows: not found >> >>> thank you for your help >> >>> On 4月11日, 上午7時33分, Roman Baumgaertner <roman.baumgaert...@t-mobile.com> >>> wrote: >>>> Nail, >> >>>> I don't understand your question. If you are connected you should see with >>>> the command iwconfig to which SSID you are attached to. >> >>>> It might make sense to send the detail configuration of your supplicant to >>>> find out what is going on. Make sure that you have nowhere a typo in your >>>> configuration files. >> >>>> Roman Baumgaertner >> >>>> Sr. SW Engineer-OSDC >>>> ・T・ ・ ・Mobile・ stick together >>>> The views, opinions and statements in this email are those of the >>>> author solely in their individual capacity, and do not necessarily >>>> represent those of T-Mobile USA, Inc. >> >>>> On 4/9/09 10:49 PM, "nail" <s894...@gmail.com> wrote: >> >>>>> Dear Roman >> >>>>> yes, i got IP and can connect to network, >> >>>>> it is because i have configred the wpa_supplicant.conf, and the >>>>> contents is shown below: >> >>>>> wpa_supplicant.conf: >>>>> =============================================================== >>>>> update_config=1 >>>>> eapol_version=1 >>>>> ap_scan=1 # ap_scan=1: wpa_supplicant initiates scanning and AP >>>>> selection >>>>> fast_reauth=1 >> >>>>> network={ >>>>> ssid="simple" >>>>> psk="very secret passphrase" >>>>> priority=5 >>>>> } >> >>>>> # Wildcard match for SSID (plaintext APs only). This example selects >>>>> any >>>>> # open AP regardless of its SSID. >>>>> network={ >>>>> key_mgmt=NONE >>>>> } >> >>>>> =============================================================== >> >>>>> so, it will do all things needed automatically, >> >>>>> could you please help me to find out where to get the SSID ? >> >>>>> On 4月10日, 上午11時23分, Roman Baumgaertner <roman.baumgaert...@t- >>>>> mobile.com> wrote: >>>>>> Hi Nail, >> >>>>>> You mentioned that you are connected. What does it mean you are >>>>>> connected? >>>>>> Did you get an IP address or are you attached to the AP (you should be >>>>>> able >>>>>> to see the SSID)? >> >>>>>> Try first to find out on the AP whether it can see you. >> >>>>>> Roman Baumgaertner >> >>>>>> Sr. SW Engineer-OSDC >>>>>> ・T・ ・ ・Mobile・ stick together >>>>>> The views, opinions and statements in this email are those of the >>>>>> author solely in their individual capacity, and do not necessarily >>>>>> represent those of T-Mobile USA, Inc. >> >>>>>> On 4/9/09 7:19 PM, "nail" <s894...@gmail.com> wrote: >> >>>>>>> Hi, I have enabledwifiusing the following command written in >>>>>>> init.rc: >> >>>>>>> "mkdir /data/misc/wifi0770wifiwifi >>>>>>> mkdir /data/misc/wifi/sockets 0770wifiwifi >>>>>>> mkdir /data/system/wpa_supplicant 0770wifiwifi >>>>>>> mkdir /data/misc/dhcp 0770 dhcp dhcp >>>>>>> chown dhcp dhcp /data/misc/dhcp >> >>>>>>> ifup wlan0 >> >>>>>>> service wpa_supplicant /system/bin/logwrapper /system/bin/ >>>>>>> wpa_supplicant -iwlan0 -c/system/etc/wifi/wpa_supplicant.conf -dd >>>>>>> groupwifi >> >>>>>>> service wlan_dhcpcd /system/bin/dhcpcd wlan0 " >> >>>>>>> and it can connetc to the network, but when i type "wpa_cli -p/data/ >>>>>>> system/wpa_supplicant/ scan" >> >>>>>>> it shows "Failed to connect to wpa_supplicant - wpa_ctrl_open: Unknown >>>>>>> error: 0" >> >>>>>>> do you have any idea about this ? thank you >> >>>>>>> On 3月27日, 下午7時49分, Androidphan <niels.kee...@tass.nl> wrote: >>>>>>>> # wpa_cli -p/data/system/wpa_supplicant/ scan >>>>>>>> Selected interface 'wlan0' >>>>>>>> Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or >>>>>>>> directory >> >>>>>>>> On 27 mrt, 12:15, Michael Trimarchi <trimar...@gandalf.sssup.it> >>>>>>>> wrote: >> >>>>>>>>> Hi, >> >>>>>>>>> Androidphan wrote: >>>>>>>>>> This is the output when starting wpa_supplicant: >> >>>>>>>>>> Initializing interface 'wlan0' conf '/system/etc/wifi/ >>>>>>>>>> wpa_supplicant.conf' >>>>>>>>>> drive >>>>>>>>>> r 'wext' ctrl_interface 'N/A' bridge 'N/A' >>>>>>>>>> Configuration file '/system/etc/wifi/wpa_supplicant.conf' -> >>>>>>>>>> '/system/ >>>>>>>>>> etc/wifi/ >>>>>>>>>> w >>>>>>>>>> pa_supplicant.conf' >>>>>>>>>> Reading configuration file '/system/etc/wifi/wpa_supplicant.conf' >>>>>>>>>> update_config=1 >>>>>>>>>> ctrl_interface='DIR=/data/system/wpa_supplicant/ GROUP=system' >>>>>>>>>> eapol_version=1 >>>>>>>>>> ap_scan=1 >>>>>>>>>> fast_reauth=1 >>>>>>>>>> Initializing interface (2) 'wlan0' >>>>>>>>>> EAPOL: SUPP_PAE entering state DISCONNECTED >>>>>>>>>> EAPOL: KEY_RX entering state NO_KEY_RECEIVE >>>>>>>>>> EAPOL: SUPP_BE entering state INITIALIZE >>>>>>>>>> EAP: EAP entering state DISABLED >>>>>>>>>> EAPOL: External notification - portEnabled=0 >>>>>>>>>> EAPOL: External notification - portValid=0 >>>>>>>>>> SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf >>>>>>>>>> capabilities: key_mgmt 0xf enc 0xf >>>>>>>>>> WEXT: Operstate: linkmode=1, operstate=5 >>>>>>>>>> Own MAC address: 00:22:43:2c:fa:a6 >>>>>>>>>> wpa_driver_wext_set_wpa >>>>>>>>>> wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0 >>>>>>>>>> wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0 >>>>>>>>>> wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0 >>>>>>>>>> wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0 >>>>>>>>>> wpa_driver_wext_set_countermeasures >>>>>>>>>> ioctl[SIOCSIWAUTH]: Operation not supported on transport endpoint >>>>>>>>>> WEXT auth param 4 value 0x0 - wpa_driver_wext_set_drop_unencrypted >>>>>>>>>> Setting scan request: 0 sec 100000 usec >>>>>>>>>> ctrl_interface_group=1000 (from group name 'system') >>>>>>>>>> Added interface wlan0 >>>>>>>>>> RTM_NEWLINK: operstate=0 ifi_flags=0x1002 () >>>>>>>>>> RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added >>>>>>>>>> Wireless event: cmd=0x8b06 len=8 >>>>>>>>>> Ignore event for foreign ifindex 4 >>>>>>>>>> RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP]) >>>>>>>>>> RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added >>>>>>>>>> State: DISCONNECTED -> SCANNING >>>>>>>>>> CTRL-EVENT-STATE-CHANGE id=-1 state=2 >>>>>>>>>> Starting AP scan (broadcast SSID) >>>>>>>>>> Trying to get current scan results first without requesting a new >>>>>>>>>> scan >>>>>>>>>> to >>>>>>>>>> speed >>>>>>>>>> up initial association >>>>>>>>>> Received 0 bytes of scan results (0 BSSes) >>>>>>>>>> Scan results: 0 >>>>>>>>>> CTRL-EVENT-SCAN-RESULTS Ready >> >>>>>>>>> Hi, test youwificonnection using the wpa_cli program. The parse >>>>>>>>> function of the >>>>>>>>> scan result expect a - to the signal stregh (if I remember) to parse >>>>>>>>> the >>>>>>>>> result, otherwise >>>>>>>>> fail. >> >>>>>>>>> wpa_cli has an interractive mode to operate, and you can send command >>>>>>>>> like: >>>>>>>>> scan and scan-results. >> >>>>>>>>>> No suitable AP found. >>>>>>>>>> Setting scan request: 0 sec 0 usec >>>>>>>>>> No enabled networks - do not scan >>>>>>>>>> State: SCANNING -> INACTIVE >>>>>>>>>> CTRL-EVENT-STATE-CHANGE id=-1 state=1 >> >>>>>>>>>> On 27 mrt, 11:39, Androidphan <niels.kee...@tass.nl> wrote: >> >>>>>>>>>>> I'm getting the following- 隱藏被引用文字 - >> >> - 顯示被引用文字 -... >> >> 閱讀更多 » > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
