Comment 3 for bug 1039941

It's not clear from this what the problem actually is.

tilt-3.4 is working OK in barebones Ubuntu for acquiring WPA encrypted AP and IP address

root@(none):/# iwconfig
lo no wireless extensions.

sit0 no wireless extensions.

wlan0 IEEE 802.11abgn ESSID:off/any
          Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Encryption key:off
          Power Management:on

eth0 no wireless extensions.

nt.conf &e):/# wpa_supplicant -Dwext -iwlan0 -c /etc/wpa_supplicant/wpa_supplican
[2] 977
root@(none):/# [ 297.949096] wl12xx: firmware booted (Rev 6.3.5.0.98)
[ 297.969573] ADDRCONF(NETDEV_UP): wlan0: link is not ready
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
Trying to associate with f8:d1:11:39:0b:44 (SSID='foamy' freq=2417 MHz)
[ 299.954284] wl12xx: Association completed.
[ 299.979064] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Associated with f8:d1:11:39:0b:44
WPA: Key negotiation completed with f8:d1:11:39:0b:44 [PTK=CCMP GTK=CCMP]
CTRL-EVENT-CONNECTED - Connection to f8:d1:11:39:0b:44 completed (auth) [id=0 id_str=]

root@(none):/# dhclient wlan0 &
[3] 987
root@(none):/#

root@(none):/# ifconfig
wlan0 Link encap:Ethernet HWaddr de:ad:be:ef:00:00
          inet addr:192.168.1.108 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::dcad:beff:feef:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:5 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:998 (998.0 B) TX bytes:1600 (1.6 KB)

root@(none):/#

I marked it invalid for us, if there's some sign that it's a kernel issue please let us know and we'll look again.

Some suggestions for checking on rootfs side:

 - try association with unencrypted AP see if that is any different
 - if there is a wpa_supplicant app in android try running it by hand, with -dd to get debugging info
 - look in the android system logs to see if anything was told there