Ice Cream Sandwich and Ad Hoc Wireless Networks - Android Q&A, Help & Troubleshooting

(The procedures can be found at post #4)
It is apparent that prior to ICS, ad hoc wireless networks are not supported: h t t p:// code. google.com/p/android/issues/detail?id=82
Does anyone know if ad hoc wireless is supported under ICS? I can't seem to find ad hoc wireless networks on my U9GT 2 tablet, running Android 4.0.3.

---

Anyone???

---

Saw this useful thread: http://szym.net/2010/12/adhoc-wifi-in-android/
Source Code to wpa_supplicant (ICS): https://github.com/jhonxie/android_external_wpa_supplicant_6/tree/ics
But I still can't get it to work. HELP!

---

After ploughing through the materials on the Internet, I finally got it to work! I believe this method works for any Android device, of any Android version. However, this method is tedious as I couldn't get the system to accept the adhoc configuration in wpa_supplicant.conf.
Here are the steps:
Ignore the first character of my example command-lines as it represents the prompt (i.e. $, #, >)
Run Terminal Emulator and elevate to root privileges / be the superuser. Then run "wpa_cli", the software interface to the wireless stack:
Code:
$ su
# wpa_cli
>
Now that you're in wpa_cli, the first command is to add a network:
Code:
> add_network
5
Take note as the system would output a number. That is the number that represents your adhoc network. In my example, the number is "5".
Next, type the following commands to set (configure) network "5" (be sure to fill in the respective SSID and BSSID):
Code:
> set_network 5 mode 1
OK
> set_network 5 ssid "MyAdHocWiFi"
OK
> set_network 5 bssid aa:BB:cc:DD:ee:FF
OK
> set_network 5 key_mgmt NONE
OK
> enable_network 5
OK
> ap_scan 2
OK
> select_network 5
OK
If you don't know your bssid, run WiFi Analyzer from the Android Market. The system would reply an "OK" after every successfully executed command. If you get a "FAIL", check your syntax - is the an extra / missing quote?
At this point, you should see a bunch of system messages. There might be some error messages but that might not mean the adhoc wireless connection had failed. Check if your device has successfully obtained an IP configuration:
Code:
# busybox ifconfig
Now, you might think this is a hell lot of work... You're right! It should be able to read the configuration file (e.g. /data/misc/wifi/wpa_supplicant.conf) and connect automatically, but I couldn't get wpa_supplicant to accept my adhoc configuration! I'll update this thread when I got it sorted out.
Finally, I am able to tether to my Nokia phone with JoikuSpot!
References:
- http://szym.net/2010/12/adhoc-wifi-in-android/
- http://www.olsr.org/?q=olsr_on_android

---

Do you have something that would work with wpa_supplicant v0.8.x?

---

The wpa_cli command is failing because it cannot be found. Should it be in my system/bin folder? I've since installed busybox and would love to connect to my adhoc network. Suggestions?

---

wendal has kindly compiled the wpa_supplicant that works with adhoc wireless networks (IBSS). For more info, refer here: http://www.slatedroid.com/topic/286...licant-source/page__view__findpost__p__304667

---

Has anyone got that file to work? I always try it but my wireless stays frozen. I've changed the ownership and permissions and still nothing!!!

---

megabiteg said:
Has anyone got that file to work? I always try it but my wireless stays frozen. I've changed the ownership and permissions and still nothing!!!
Click to expand...
Click to collapse
It didn't work for me on my ICS kindle-fire.. According to the log it seems like it doesn't recognize the kindle-fire wireless interface. I am wondering at this point whether each device uses its own wpa_supplicant that works with its own driver or what else. I am going to find out more about it and see if I can get my own wpa_supplicant patched with IBSS and compiled.
Code:
I/ActivityManager( 1400): No longer want com.android.vending (pid 2307): hidden #16
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiStateMachine( 1400): Failed to setup control channel, restart supplicant
E/WifiStateMachine( 1400): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
D/CommandListener( 1296): Setting iface cfg
D/CommandListener( 1296): Trying to bring down tiwlan0
D/CommandListener( 1296): broadcast flag ignored
D/CommandListener( 1296): multicast flag ignored
D/NetworkManagementService( 1400): rsp <213 f0:a2:25:77:b3:22 0.0.0.0 0 [down broadcast multicast]>
D/NetworkManagementService( 1400): flags <[down broadcast multicast]>
E/wpa_supplicant( 2457): Unsupported driver 'tiwlan0'.
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiStateMachine( 1400): Failed to setup control channel, restart supplicant

---

Not working on hidden WPA2 AES Wigi
Hi there, I have a rooted stock ICS Google Nexus. On my workplace, the wifi has hidden SSID with WPA2-Personal and AES. When I try to connect with it, nothing happens. It's does not save on the wpa_supplicant.conf also.
I've tried the compiled wpa_supplicant mentioned on the post, but the same thing happens... I've even tried to edit manually the wpa_supplicant.conf but the wifi crashed after that (thankfully I had a backup).
So any ideas on how to get this thing connected? On my later Atrix with stock 2.3.6 it connected just fine...
Thanks.

---

Hello i tried many adhoc fixes and now i can connect to adhoc network but after 1-2 minutes connection get lost. Does anybody know how to solve the problem?
i use Htc Sensation with ICS

---

I have ICS CM9 on my HTC legend and can't recognise the wirelss network at my office. At home no problem.
If I launch wpa_cli I get:
Using interface 'tiwlan0'
Inteactive mode
>
<2>CTRL-EVENT-SCAN-RESULTS
and the last line continues to loop.
Is it correct? What should I do then and to let this wi fi network accessible?

---

Try this
Hello,
I just got a new Idolian tablet and couldn't connect to my hidden home SSID. I just thought I'd try something really quick and it worked..! I added network in manually but it said not in range. Try temporarily turning the SSID broadcast back on then connect. Mine was successful. I then turned off the SSID broadcast on the router and the wifi off and on again on the tablet and it connected perfectly.
I've been reading this forums for almost a year but this is my 1st post so hopefully it will help someone out as these forums have for me.

---

Has anyone got it to connect and not get the obtaining IP address loop? My device finds the Ad Hoc network for my cars ODB2 wifi adapter but will never connect.

---

Good day friends, I really need to enable ad-hoc on my HTC One X, to use my Brookstone Rover, more'm not getting my wpa_supplicant is v8.
I have a doubt, this command set_network 5 bssid aa: BB: CC: DD: ee: FF, this is the bssid mac network card from my smartphone or mac card that will connect my smartphone?
thank you very much

---

Edit wpa_supplicant.conf instead of wpa_supplicant
I changed data/misc/wifi/wpa_supplicant.conf instead of /system/bin/wpa_supplicant.
Step1:First i scanned my adhoc network using Wifi Manager. It shows adhoc networks. I ignored it's warning and tried to connect. It'll fail.No problem! We now have the adhoc network listed in wpa_supplicant.conf.
Note: you can skip this step if you know how to edit wpa_supplicant.conf manually or if your device already lists adhoc networks on scanning.
Step2: You'll need to root your device if you're doing this through your device itself. If you use adb you may not need to root your device.(I had root access by default through adb. So rooting the device wasn't necessary for me). If you're using pc(windows or linux), i recommend Android Commander. If you're doing this from device itself, use some Root Explorer and Terminal Emulator.
Pull and/or edit data/misc/wifi/wpa_supplicant.conf. Add the following line
ap_scan=2
Find line like
network={
ssid="your adhoc name"
bssid=*some value*
.
.
}
Delete bssid line.
Add/Change the following
scan_ssid=1
priority=1
mode=1
Push back/save the modified file.
chown ownership back to system.wifi. Type the following in adb/Terminal Emulator
#chown system.wifi data/misc/wifi/wpa_supplicant.conf
Ok, done! Now you can turn on wifi and if the specified adhoc network is nearby, your device'll automatically connect to it. Don't scan for new networks. If you do, adhoc support will be lost and you'll have to start over again!
Advantage: Safer than modifying system/etc/wifi/wpa_supplicant binary. Saves you the trouble of compiling modified wpa_supplicant or finding a compiled one for your platform.
Drawback: This is just a temporary solution.You'll have to repeat this process for every new adhoc network as it doesn't enable adhoc forever. It is good for connecting to your home network or other known networks, but if you want to connect to any adhoc network you scan,then this is not your method. Because, wpa_supplicant.conf will be overwritten every time you scan a new network.
For more details refer
http://forum.xda-developers.com/showthread.php?t=1591207

---

error adhoc network
Hello,
I have android 4.2.2 ,Nexus 4
I did the same steps but I can not connect to adhoc network
I receive the output below:
> OK
<3>CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
<4>Failed to initiate AP scan
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-SCAN-RESULTS
<3>Trying to associate with 1a:79:c3:0c:b1:bd (SSID='CCN2' freq=2462 MHz)
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=1a:79:c3:0c:b1:bd
<3>Authentication with 1a:79:c3:0c:b1:bd timed out.
<3>CTRL-EVENT-STATE-CHANGE id=4 state=0 BSSID=1a:79:c3:0c:b1:bd
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-SCAN-RESULTS
<3>Trying to associate with 1a:79:c3:0c:b1:bd (SSID='CCN2' freq=2462 MHz)
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=1a:79:c3:0c:b1:bd
<3>Authentication with 1a:79:c3:0c:b1:bd timed out.
have you any idea about why doesn't work with me.
---------- Post added at 10:28 AM ---------- Previous post was at 10:24 AM ----------
Hello,
I have android 4.2.2 ,Nexus 4
I did the same steps but I can not connect to adhoc network
I receive the output below:
> OK
<3>CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
<4>Failed to initiate AP scan
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-SCAN-RESULTS
<3>Trying to associate with 1a:79:c3:0c:b1:bd (SSID='CCN2' freq=2462 MHz)
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=1a:79:c3:0c:b1:bd
<3>Authentication with 1a:79:c3:0c:b1:bd timed out.
<3>CTRL-EVENT-STATE-CHANGE id=4 state=0 BSSID=1a:79:c3:0c:b1:bd
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
<3>CTRL-EVENT-SCAN-RESULTS
<3>Trying to associate with 1a:79:c3:0c:b1:bd (SSID='CCN2' freq=2462 MHz)
<3>CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=1a:79:c3:0c:b1:bd
<3>Authentication with 1a:79:c3:0c:b1:bd timed out.
have you any idea about why doesn't work with me.

---

fyresg said:
After ploughing through the materials on the Internet, I finally got it to work! I believe this method works for any Android device, of any Android version. However, this method is tedious as I couldn't get the system to accept the adhoc configuration in wpa_supplicant.conf.
Here are the steps:
Ignore the first character of my example command-lines as it represents the prompt (i.e. $, #, >)
Run Terminal Emulator and elevate to root privileges / be the superuser. Then run "wpa_cli", the software interface to the wireless stack:
Code:
$ su
# wpa_cli
>
Now that you're in wpa_cli, the first command is to add a network:
Code:
> add_network
5
Take note as the system would output a number. That is the number that represents your adhoc network. In my example, the number is "5".
Next, type the following commands to set (configure) network "5" (be sure to fill in the respective SSID and BSSID):
Code:
> set_network 5 mode 1
OK
> set_network 5 ssid "MyAdHocWiFi"
OK
> set_network 5 bssid aa:BB:cc:DD:ee:FF
OK
> set_network 5 key_mgmt NONE
OK
> enable_network 5
OK
> ap_scan 2
OK
> select_network 5
OK
If you don't know your bssid, run WiFi Analyzer from the Android Market. The system would reply an "OK" after every successfully executed command. If you get a "FAIL", check your syntax - is the an extra / missing quote?
At this point, you should see a bunch of system messages. There might be some error messages but that might not mean the adhoc wireless connection had failed. Check if your device has successfully obtained an IP configuration:
Code:
# busybox ifconfig
Now, you might think this is a hell lot of work... You're right! It should be able to read the configuration file (e.g. /data/misc/wifi/wpa_supplicant.conf) and connect automatically, but I couldn't get wpa_supplicant to accept my adhoc configuration! I'll update this thread when I got it sorted out.
Finally, I am able to tether to my Nokia phone with JoikuSpot!
References:
- http://szym.net/2010/12/adhoc-wifi-in-android/
- http://www.olsr.org/?q=olsr_on_android
Click to expand...
Click to collapse
Thanks brother! This was what I was looking for everywhere!
The wpa_supplicant method did not work for Me and this did! Thanks a lot!