Database Info

[UPDATED 11/14/09] Wifi now working in Blur via CLI

Ok I'm setting up this thread as a place to collect my thoughts as I'm trying to get wifi working in Blur. I'm also hoping others will chime in and offer their help.
Currently I have wifi working from the commandline now
Here is what I have so far.
Wifi module (wlan.ko) loads into the kernel
Code:
insmod /system/lib/modules/wlan.ko
Produces the following output from lsmod
wlan 555768 1 - Live 0xbf11a000
Click to expand...
Click to collapse
I am able to now load the wifi driver
Code:
start wlan_loader
Produces the following output from dmesg
TIWLAN: Driver loading
wifi_probe
trout_wifi_power: 1
trout_wifi_reset: 0
trout_wifi_set_carddetect: 1
TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
tiwlan0 (): not using net_device_ops yet
TIWLAN: Driver initialized (rc 0)
TIWLAN: 1251 PG 1.2
TIWLAN: Driver loaded
Click to expand...
Click to collapse
I can now get wpa_supplicant loading after some mods to wpa_supplicant.conf
Code:
wpa_supplicant -Dwext -itiwlan0 -c /etc/wifi/wpa_supplicant.conf -dd
Produces the following shortened output. It's long so I cropped it
wpa_supplicant -Dwext -itiwlan0 -c /etc/wifi/wpa_supplicant.conf -dd
Initializing interface 'tiwlan0' conf '/etc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wifi/wpa_supplicant.conf' -> '/etc/wifi/wpa_supplicant.conf'
Reading configuration file '/etc/wifi/wpa_supplicant.conf'
update_config=1
ctrl_interface='/data/system/wpa_supplicant'
eapol_version=1
ap_scan=1
fast_reauth=1
Initializing interface (2) 'tiwlan0'
.....shortened output......
WEXT: Operstate: linkmode=0, operstate=6
Click to expand...
Click to collapse
Next is a verification we have the device
Code:
ls -l /dev/socket/wpa*
srw-rw---- 1 1010 1010 0 Nov 14 16:48 wpa_tiwlan0
Next let's verify we can scan open wireless networks
Code:
[B]wpa_cli[/B]
> [B]scan[/B]
OK
<2>CTRL-EVENT-STATE-CHANGE id=-1 state=2
>
<2>CTRL-EVENT-SCAN-RESULTS Ready
> [B]scan results[/B]
bssid / frequency / signal level / flags / ssid
00:14:6c:18:2f:0e 2462 -53 [WPA-PSK-TKIP] Quantum
00:24:01:7a:72:9d 2422 -75 [WPA-PSK-TKIP+CCMP][WPA2-PSK-TKIP+CCMP] frankiejparker
00:24:56:19:68:61 2412 -78 [WEP] 2WIRE466
00:1f:b3:d5:da:59 2427 -82 [WPA-PSK-TKIP] 2WIRE699
00:1e:c7:21:48:b9 2442 -83 [WPA-PSK-TKIP] 2WIRE604
00:21:29:9e:26:da 2412 -85 [WPA-PSK-TKIP+CCMP][WPA2-PSK-TKIP+CCMP] Leightons Network
02:18:41:e0:7f:f3 2437 -86 [WEP] 2WIRE817
00:1b:5b:1d:37:49 2417 -91 [WPA-PSK-TKIP] 2WIRE523
00:25:3c:d0:c3:d1 2427 -92 [WPA-PSK-TKIP] 2WIRE297
00:1f:33:b5:c9:e2 2452 -94 [WEP] Martinez
>
<2>CTRL-EVENT-STATE-CHANGE id=-1 state=1
Here I'll add a network, enable it, configure variables, save config, connect to a network, then start dhcp
Code:
> [B]add_network[/B]
0
> [B]list_network[/B]
network id / ssid / bssid / flags
0 any [DISABLED]
> [B]enable_network 0[/B]
OK
> [B]set_network 0 ssid "yourSSID"[/B]
OK
> [B]list_network[/B]
network id / ssid / bssid / flags
0 yourSSID any
> [B]set_network 0 psk "your wpa passkey"[/B]
OK
> [B]save_config[/B]
OK
<2>CTRL-EVENT-SCAN-RESULTS Ready
<2>Trying to associate with 00:14:6c:18:2f:0e (SSID='yourSSID' freq=2462 MHz)
<2>CTRL-EVENT-STATE-CHANGE id=-1 state=3
<2>CTRL-EVENT-STATE-CHANGE id=0 state=4
<2>Associated with 00:14:6c:18:2f:0e
<2>CTRL-EVENT-STATE-CHANGE id=0 state=5
<2>CTRL-EVENT-STATE-CHANGE id=0 state=5
<2>CTRL-EVENT-STATE-CHANGE id=0 state=6
<2>CTRL-EVENT-STATE-CHANGE id=0 state=6
<2>WPA: Key negotiation completed with 00:14:6c:18:2f:0e [PTK=TKIP GTK=TKIP]
<2>CTRL-EVENT-STATE-CHANGE id=0 state=7
<2>CTRL-EVENT-CONNECTED - Connection to 00:14:6c:18:2f:0e completed (auth) [id=0 id_str=]
> quit
Now let's start up dhcp so we can get an IP
Code:
[B]start dhcpcd[/B]
[B]/system/xbin/bb/ifconfig tiwlan0[/B]
tiwlan0 Link encap:Ethernet HWaddr 00:18:41:A9:48:5F
inet addr:192.168.1.9 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1901 (1.8 KiB) TX bytes:894 (894.0 B)
And there ya go, wireless is now functional from the commandline but since we're not actually activating it from the Android UI then you are not able to simply go into Settings->Wireless and connect to a network. So far it will have to be done from the commandline using the binary wpa_cli.
If an android developer would like to make a frontend be my guest
I've now provided you with what you need to make it work. I'll be releasing a Blur rom today that will have all the proper files and environment so these commands will work.

good job, hopefully this can be implemented into a blur rom for others use.

Added the code to actually connect to a wireless network and get an IP via dhcp

I guess no one else is excited but I'm freakin pumped!
I only get 10MB of data a month on my wireless plan so blur roms are a no go without WiFi.
Thank you so much for your hard work shafty on this and the hero roms also!

abteer said:
I guess no one else is excited but I'm freakin pumped!
I only get 10MB of data a month on my wireless plan so blur roms are a no go without WiFi.
Thank you so much for your hard work shafty on this and the hero roms also!
Click to expand...
Click to collapse
No problem, just took a good 2 hrs to figure out and get working. If you use the app that redirects all internet traffic through wifi then that would pretty much simulate what happens when you connect to wifi through the android UI.
One thing to note, once you add a network say like at your house and save the config you won't have to do any of that again.
To turn off wifi you'd just do
Code:
wpa_cli terminate
To re-enable
Code:
start wpa_supplicant
start dhcpcd

im def excited about this...thank you shafty for your hard work man...you getting closer and closer everyday to perfecting this rom...

Shafty, you are the man. Thank you again for all your efforts for the community.

Thank you much for posting this! I can't wait until it drops so I can finally run this ROM. I live in a GPRS/EDGE area and can't do ANYTHING w/o it. Are you going to add the working BT to the ROM also? I saw it working on 1 of them...can't remember which 1 though. ::Hoping:: It's another must for me.
Again...THANKS FOR YOUR TIME/EFFORTS!!!

Seriously? This is great news! I might be able to try out a blur finally! Happy dance! Happy dance! Happy dance! Happy dance!

shagge68 said:
Thank you much for posting this! I can't wait until it drops so I can finally run this ROM. I live in a GPRS/EDGE area and can't do ANYTHING w/o it. Are you going to add the working BT to the ROM also? I saw it working on 1 of them...can't remember which 1 though. ::Hoping:: It's another must for me.
Again...THANKS FOR YOUR TIME/EFFORTS!!!
Click to expand...
Click to collapse
BT is working in 1.071

shafty023 said:
Ok I'm setting up this thread as a place to collect my thoughts as I'm trying to get wifi working in Blur. I'm also hoping others will chime in and offer their help.
Currently I have wifi working from the commandline now
Here is what I have so far.
Wifi module (wlan.ko) loads into the kernel
Code:
insmod /system/lib/modules/wlan.ko
Produces the following output from lsmod
I am able to now load the wifi driver
Code:
start wlan_loader
Produces the following output from dmesg
I can now get wpa_supplicant loading after some mods to wpa_supplicant.conf
Code:
wpa_supplicant -Dwext -itiwlan0 -c /etc/wifi/wpa_supplicant.conf -dd
Produces the following shortened output. It's long so I cropped it
Next is a verification we have the device
Code:
ls -l /dev/socket/wpa*
srw-rw---- 1 1010 1010 0 Nov 14 16:48 wpa_tiwlan0
Next let's verify we can scan open wireless networks
Code:
[B]wpa_cli[/B]
> [B]scan[/B]
OK
<2>CTRL-EVENT-STATE-CHANGE id=-1 state=2
>
<2>CTRL-EVENT-SCAN-RESULTS Ready
> [B]scan results[/B]
bssid / frequency / signal level / flags / ssid
00:14:6c:18:2f:0e 2462 -53 [WPA-PSK-TKIP] Quantum
00:24:01:7a:72:9d 2422 -75 [WPA-PSK-TKIP+CCMP][WPA2-PSK-TKIP+CCMP] frankiejparker
00:24:56:19:68:61 2412 -78 [WEP] 2WIRE466
00:1f:b3:d5:da:59 2427 -82 [WPA-PSK-TKIP] 2WIRE699
00:1e:c7:21:48:b9 2442 -83 [WPA-PSK-TKIP] 2WIRE604
00:21:29:9e:26:da 2412 -85 [WPA-PSK-TKIP+CCMP][WPA2-PSK-TKIP+CCMP] Leightons Network
02:18:41:e0:7f:f3 2437 -86 [WEP] 2WIRE817
00:1b:5b:1d:37:49 2417 -91 [WPA-PSK-TKIP] 2WIRE523
00:25:3c:d0:c3:d1 2427 -92 [WPA-PSK-TKIP] 2WIRE297
00:1f:33:b5:c9:e2 2452 -94 [WEP] Martinez
>
<2>CTRL-EVENT-STATE-CHANGE id=-1 state=1
Here I'll add a network, enable it, configure variables, save config, connect to a network, then start dhcp
Code:
> [B]add_network[/B]
0
> [B]list_network[/B]
network id / ssid / bssid / flags
0 any [DISABLED]
> [B]enable_network 0[/B]
OK
> [B]set_network 0 ssid "yourSSID"[/B]
OK
> [B]list_network[/B]
network id / ssid / bssid / flags
0 yourSSID any
> [B]set_network 0 psk "your wpa passkey"[/B]
OK
> [B]save_config[/B]
OK
<2>CTRL-EVENT-SCAN-RESULTS Ready
<2>Trying to associate with 00:14:6c:18:2f:0e (SSID='yourSSID' freq=2462 MHz)
<2>CTRL-EVENT-STATE-CHANGE id=-1 state=3
<2>CTRL-EVENT-STATE-CHANGE id=0 state=4
<2>Associated with 00:14:6c:18:2f:0e
<2>CTRL-EVENT-STATE-CHANGE id=0 state=5
<2>CTRL-EVENT-STATE-CHANGE id=0 state=5
<2>CTRL-EVENT-STATE-CHANGE id=0 state=6
<2>CTRL-EVENT-STATE-CHANGE id=0 state=6
<2>WPA: Key negotiation completed with 00:14:6c:18:2f:0e [PTK=TKIP GTK=TKIP]
<2>CTRL-EVENT-STATE-CHANGE id=0 state=7
<2>CTRL-EVENT-CONNECTED - Connection to 00:14:6c:18:2f:0e completed (auth) [id=0 id_str=]
> quit
Now let's start up dhcp so we can get an IP
Code:
[B]start dhcpcd[/B]
[B]/system/xbin/bb/ifconfig tiwlan0[/B]
tiwlan0 Link encap:Ethernet HWaddr 00:18:41:A9:48:5F
inet addr:192.168.1.9 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1901 (1.8 KiB) TX bytes:894 (894.0 B)
And there ya go, wireless is now functional from the commandline but since we're not actually activating it from the Android UI then you are not able to simply go into Settings->Wireless and connect to a network. So far it will have to be done from the commandline using the binary wpa_cli.
If an android developer would like to make a frontend be my guest
I've now provided you with what you need to make it work. I'll be releasing a Blur rom today that will have all the proper files and environment so these commands will work.
Click to expand...
Click to collapse
Dude, I could almost Kiss you Right now. That's the only thing that was holding me back from Blur!!!!!!!!!!!!!!!
You Rock Dude. Think that will work on Pulse?

damn this is great news.. guess i wont have to buy the motocliq after all.. lol.. ready for a working blur rom with wifi

just wondering i heard motoblur was open sourced could you just edit the source to automate this process for the g1?

eugene373 said:
Dude, I could almost Kiss you Right now. That's the only thing that was holding me back from Blur!!!!!!!!!!!!!!!
You Rock Dude. Think that will work on Pulse?
Click to expand...
Click to collapse
Yup it should

jokersax11 said:
just wondering i heard motoblur was open sourced could you just edit the source to automate this process for the g1?
Click to expand...
Click to collapse
No this part was not released. They only released gpl code

omg this is great i can finally try out a blur rom on my g1 thanks shafty

hey shafty, your expertise has been a huge asset to the android community once again! you're the bomb.
Just curious, I can completely follow your instructions until the code box where you're adding the network(when you're actually dealing with wpa_cli)
How does wpa_cli work? which things that appear there did you type and which did it print out?

jcarrz1 said:
hey shafty, your expertise has been a huge asset to the android community once again! you're the bomb.
Just curious, I can completely follow your instructions until the code box where you're adding the network(when you're actually dealing with wpa_cli)
How does wpa_cli work? which things that appear there did you type and which did it print out?
Click to expand...
Click to collapse
If you launch "wpa_cli" by itself it will launch a "> " prompt waiting for u to type a command. The commands I typed are in bold. Try typing "help" at the prompt after launching wpa_cli.
Keep in mind it's very unlikely you'll get it working b/c u don't have the right kernel/wifi module/wifi driver/scripts/binaries. It took a while for me to get the right ones.
I'll release a copy when I have a script in place to automate it all. Have a busy weekend so won't be able to do it anytime soon. But feel free to try, at least if u find the right files you can be proud to know u made it work on ur own. Why else do u think I'd post all my work? So others can learn and try on their own good luck!

On 1.071 i type insmod /system/lib/modules/wlan.ko and it gives me an error:
# insmod /system/lib/modules/wlan.ko
insmod: init_module '/system/lib/modules/wlan.ko' failed (Exec format error)

crater said:
On 1.071 i type insmod /system/lib/modules/wlan.ko and it gives me an error:
# insmod /system/lib/modules/wlan.ko
insmod: init_module '/system/lib/modules/wlan.ko' failed (Exec format error)
Click to expand...
Click to collapse
I haven't released a build w/ the files to make this work yet. When I do it'll be v1.08. Hang tight and in a few days/this week I will. Very busy weekend for me

[Q] Networking (netmask) issues on a Captivate

I've got a shiny new Samsung Captivate (Galaxy S) on AT&T.. working fairly well so far, besides the annoyances with the phone being locked down and the crappy bundled mail client (I've got loooots of email in my imap box, grin.) Phone is still stock; haven't had a chance to root it yet.
In any case, the issue I'm having is that the phone is setting an invalid netmask (255.0.0.0) on the wifi interface, instead of the proper one as served by dhcp (255.255.255.0).. this is preventing the phone from talking to other devices in 10/8.
Here's the DHCP response sent to the phone by my DHCP server:
Code:
Client-IP 10.20.0.120
Your-IP 10.20.0.120
Client-Ethernet-Address 00:26:37:xx:xx:xx
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: ACK
Server-ID Option 54, length 4: 10.20.0.254
Lease-Time Option 51, length 4: 86400
Subnet-Mask Option 1, length 4: 255.255.255.0
Default-Gateway Option 3, length 4: 10.20.0.254
Domain-Name-Server Option 6, length 8: 10.20.0.254,10.20.0.1
BR Option 28, length 4: 10.20.0.255
RN Option 58, length 4: 43200
RB Option 59, length 4: 75600
END Option 255, length 0
PAD Option 0, length 0, occurs 4
As you can see from the above, the phone was assigned 10.20.0.120 with a netmask of 255.255.255.0. I finally set up the android sdk, and fired up a shell with adb.. here's what it thinks its ip is:
Code:
$ ifconfig eth0
eth0: ip 10.20.0.120 mask 255.0.0.0 flags [up broadcast running multicast]
even odder, the properties on the phone has the correct netmask; output from 'getprop':
Code:
[dhcp.eth0.pid]: [3350]
[dhcp.eth0.reason]: [BOUND]
[dhcp.eth0.dns1]: [10.20.0.254]
[dhcp.eth0.dns2]: [10.20.0.1]
[dhcp.eth0.dns3]: []
[dhcp.eth0.dns4]: []
[dhcp.eth0.ipaddress]: [10.20.0.120]
[dhcp.eth0.gateway]: [10.20.0.254]
[dhcp.eth0.mask]: [255.255.255.0]
[dhcp.eth0.leasetime]: [86400]
[dhcp.eth0.server]: [10.20.0.254]
I suspect a firmware bug, but don't know for sure - anyone run into this before?
Appreciate any thoughts!

Same issue here. I posted about it here and on the ATT forums and sadly nobody has any suggestions other than reporting the bug to samsung. I did a bit of poking around in the console grepping 255.0.0.0 but didnt find any files. Im just gonna weather the storm and wait for the next firmware to be released. I have a shortcut to wifi settings and I just toggle the "static ip" option as needed.

FYI, there's also a post on ATT's forums about this.. I'm not allowed to link to it, but a Google search for "Samsung Captivate WiFi DHCP netmask issue" will get you to it..

Generally I dislike reviving old threads, but this appears unresolved and I've been encountering it on my Samsung Vibrant.
Can anyone confirm whether this happens with Froyo, or other Eclair-based handsets, or is it specific to Android 2.1 on Samsung GalaxyS?
When the Wifi DHCP assigns an IP in the 10.x.x.x block, (which is actually assigned with a /24 netmask) android puts the IP on the interface TWICE, with both /24 and an incorrect /8 subnet mask. ("ifconfig" is essentially a legacy command from linux kernel 2.2 era, when multiple IPs required aliased interfaces - with two IPs on one interface today "ifconfig" will only show the first one. Since kernel 2.4 days "ip" is the preferred tool)
$ busybox ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: usb0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 5e:38:e9:7b:aa:6d brd ff:ff:ff:ff:ff:ff
3: tunl0: <NOARP> mtu 1480 qdisc noop state DOWN
link/ipip 0.0.0.0 brd 0.0.0.0
4: gre0: <NOARP> mtu 1476 qdisc noop state DOWN
link/gre 0.0.0.0 brd 0.0.0.0
30: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 5c:da:d4:09:fb:f3 brd ff:ff:ff:ff:ff:ff
inet 10.200.10.28/8 brd 10.255.255.255 scope global eth0
inet 10.200.10.28/24 brd 10.200.10.255 scope global eth0
inet6 2001:470:e130:98:5eda:d4ff:fe09:fbf3/64 scope global dynamic
valid_lft 2591705sec preferred_lft 604505sec
inet6 fe80::5eda:d4ff:fe09:fbf3/64 scope link
valid_lft forever preferred_lft forever
$
This causes me significant problems, as 10.200.10.0/24 is the wifi subnet, but 50 other 10.x.x.x subnets exist on the local network, and because it erroneously applies a /8 mask on the local interface I'm unable to reach anything on the 10.x.x.x networks outside of 10.200.10.x. (I have to manually go in and remove the first IP with the /8 subnet)
(Aside, as you might notice it correctly autoconfigured an ipv6 address, with 2001:470:e130::1/64 gateway running radvd - now if only apps like web browser understood ipv6...)
j

[Q] WiFi gets jammed in "turning off" state

Hi I am developing an application for controlling the WiFi interface and I have found a problem: WiFi interface gets jammed on the Xperia X10 Mini (I tested on three devices of the same model). Looking at the log with "logcat" I found the following error:
Code:
E/wpa_supplicant( 1775): ERROR - wpa_driver_tista_private_send -
(ioctl_cmd = 8021501, res = 1, errno = 99)
E/wpa_supplicant( 1775): ERROR - Failed to do tista scan!
W/wpa_supplicant( 1775): Failed to initiate AP scan.
The only way to fix the problem is rebooting the device (and it did not even work all the times). Has anyone got a solution? Any help is welcome?
P.S: I know there is a bug reported here: code.google.com/p/android/issues/detail?id=9677. However, it is for Motorola Droid, not for Xperia X10 Mini.

[Q] Wireless-N not work

Have faced a problem that my HTC One S don't connect to wi-fi N access point. It stucks at authentication. If I disable N-mode at AP - the phone connects normally. Does anybody have such problem? In both cases WPA2 is used.

bump.... so no one have such problems? or no one is using wifi-n?

have you try the advanced option of wi-fi?
option ---> wi-fi ----> advanced ----> better wi-fi performance?

igooor87 said:
have you try the advanced option of wi-fi?
option ---> wi-fi ----> advanced ----> better wi-fi performance?
Click to expand...
Click to collapse
Yes, I have tried but no luck. Here is logcat:
I/wpa_supplicant( 4356): wlan0: Trying to associate with yy:yy:yy:yy:yy:yy (SSID='MY-WLAN' freq=2472 MHz)
I/wpa_supplicant( 4356): Cancelling scan request -
I/wpa_supplicant( 4356): wpa_supplicant_set_state -
I/wpa_supplicant( 4356): WEXT: Custom wireless event: 'BEACONIEs='
I/wpa_supplicant( 4356): wpa_supplicant_set_state -
I/wpa_supplicant( 4356): wlan0: Associated with yy:yy:yy:yy:yy:yy
I/wpa_supplicant( 4356): Cancelling scan request -
I/wpa_supplicant( 4356): wpa_supplicant_set_state -
I/wpa_supplicant( 4356): [SeamLess] We are roaming state is drv->flag_roam_state is 0drv->flag_roaming is 0
I/wpa_supplicant( 4356): [SeamLess] We are roaming state is drv->flag_roam_state is 0drv->flag_disconnect_state is 0
I/wpa_supplicant( 4356): [SeamLess] Flag roam state is mlme_event_disconnect:1514
I/wpa_supplicant( 4356): [SeamLess] We are in roaming_scan_handler to register to timeout handlers
I/wpa_supplicant( 4356): [SeamLess] We requested scan to connect
I/wpa_supplicant( 4356): Setting scan request: 0 sec 0 usec
I/wpa_supplicant( 4356): wpa_supplicant_trigger_scan +
W/wpa_supplicant( 4356): [EAP-MSG] EAP [email protected]: eap_methods not available
I/wpa_supplicant( 4356): [SeamLess] This is already connected so rejected to yy:yy:yy:yy:yy:yy
I/wpa_supplicant( 4356): [SeamLess] flag_disconnect is set i.e., Seamless is give it up
I/wpa_supplicant( 4356): [SeamLess] Event DISASSOC is Generated seamless_roaming_disconnect:438
I/wpa_supplicant( 4356): wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
I/wpa_supplicant( 4356): WPA: Auto connect enabled: try to reconnect (wps=0)
I/wpa_supplicant( 4356): Setting scan request: 0 sec 500000 usec
I/wpa_supplicant( 4356): Setting scan request: 0 sec 100000 usec
I/wpa_supplicant( 4356): wlan0: CTRL-EVENT-DISCONNECTED bssid=yy:yy:yy:yy:yy:yy reason=0
I/wpa_supplicant( 4356): wpa_supplicant_set_state -
BUT, the passphase is correct. If I just turn off N-mode in access point it connects normally.

Does your router have the option for WPA+WPA2 not just one or the other? If so try enabling the setting to use both.
Sent from my HTC One S using xda premium

doktortaru said:
Does your router have the option for WPA+WPA2 not just one or the other? If so try enabling the setting to use both.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Currently I configure it to use only WPA2 (CCMP/AES cipher) but also tryed with WPA (TKIP cipher) and already tryed to use both WPA+WPA2 - no luck.
P.S.
I'm also have HTC Incredible S and it connects to AP normally in all possible modes while One S won't.

WLAN
Working fine on my Phone.. Problems with your Rom?

Andy2502 said:
Working fine on my Phone.. Problems with your Rom?
Click to expand...
Click to collapse
Have checked with 3 different roms including official. What AP do you have and which speed it suppors (150/300mbps)?

i had a similar issue but my phone would reboot after failed attempts to connect.
what is your baseband? i was on 0.15 and the phone finally connected when i used the TMOUS RUU to update to 0.16.

suhailtheboss said:
i had a similar issue but my phone would reboot after failed attempts to connect.
what is your baseband? i was on 0.15 and the phone finally connected when i used the TMOUS RUU to update to 0.16.
Click to expand...
Click to collapse
radio is 0.16.31501S.17_2_10.23.31501S.10L and the rom is 1.78.401.2, previously was on official T-Mobile DE rom, but currently on LeeDroid. With both roms wifi won't auth with AP in N-mode

Solved by compiling latest compat-wireless for AP.

darkside_ua said:
Solved by compiling latest compat-wireless for AP.
Click to expand...
Click to collapse
Hi, i have the same issue with the original ROM 1.78.401.2.
Could you please explain me how to solve this? My HTC is already rooted...
Thanks

[Q] Cyanogenmod 10 Nightly build(s) wifi issues

Hi all,
I recently purchased a SGS3 and ran the stock ROM for approx 30mins before flashing a CM10 nightly build (i9300 intl). Because of this I am unable to verify if the wifi was working on my home router prior to flashing a custom ROM.
At work I am able to connect to our wifi connection without problemson 2.4ghz or 5ghz. At home I've got a D-Link DSL-G604T wireless router which I am unable to connect to. I've tried changing the wifi channel, password, removing protection, factory reset and installed a seperate CM10 nightly build without any help.
When trying to connect to the WIFI connection I get the following output in adb logcat.
Anyone have any ideas what may be stopping me from connecting ot my wifi?
W/wpa_supplicant( 5841): wlan0: Failed to initiate AP scan
W/wpa_supplicant( 5841): wlan0: Failed to initiate AP scan
W/wpa_supplicant( 5841): wlan0: Failed to initiate AP scan
W/wpa_supplicant( 5841): wlan0: Failed to initiate AP scan
I/wpa_supplicant( 5841): wlan0: Trying to associate with 00:1e:58:80:a2:e2 (SSID
='HOMEWIFI' freq=2452 MHz)
D/CommandListener( 1913): Clearing all IP addresses on wlan0
I/wpa_supplicant( 5841): wlan0: Associated with 00:1e:58:80:a2:e2
I/wpa_supplicant( 5841): wlan0: Authentication with 00:1e:58:80:a2:e2 timed out.
I/wpa_supplicant( 5841): wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00
reason=0
More info of my phone (kernel, build etc): i.imgur.com/PRaEx.png
Cheers

You checked "Yes this is a question"
Guess where it belongs?
Moved to Q&A
Friendly Neighborhood Moderator