Ad-Hoc for xoom using v0.6.x wpa_supplicant

---

I stumbled upon the following thread over in the EVO forum about enabling ad-hoc support for both 0.5.x and 0.6.x wpa_supplicant versions. Following the instructions there, but using a terminal emulator on the xoom I entered:

adb shell wpa_supplicant -v

and it returned v0.6.10 on my (wifi only) xoom.

Now, the problem i'm running into is that the files provided are to be flashed in a recovery--and since the xoom doesn't have one yet, i instead unziped the update, extracted the file, and used root explorer to mount system/bin and replace the "wpa_supplicant". I did a chmod to change the permissions to 775, then flipped my wifi back on to see if it worked....

The result was wifi turned on, but just scanned indefinitely and didn't pick anything up (not even the access points ). Luckily, i made a backup of the original "wpa_supplicant" and restored it using root explorer and fixing permissions as described above. That at least got my wifi up and going again

My question is, does anyone know how to edit the honeycomb file to work with ad-hoc? I'll attach a link below if anyone wants the original to play around with.

I guess it is worth noting that if someone could get this going, i'd be willing to throw a few bucks their way. I'm just stumped, but it seems like it is so close i can almost taste it!

Thanks for your help!

-amruthwo

Stock wpa_supplicant file from Xoom
(lives in system/bin)

Originally Posted by amruthwo

I stumbled upon the following thread over in the EVO forum about enabling ad-hoc support for both 0.5.x and 0.6.x wpa_supplicant versions. Following the instructions there, but using a terminal emulator on the xoom I entered:

adb shell wpa_supplicant -v

and it returned v0.6.10 on my (wifi only) xoom.

Now, the problem i'm running into is that the files provided are to be flashed in a recovery--and since the xoom doesn't have one yet, i instead unziped the update, extracted the file, and used root explorer to mount system/bin and replace the "wpa_supplicant". I did a chmod to change the permissions to 775, then flipped my wifi back on to see if it worked....

The result was wifi turned on, but just scanned indefinitely and didn't pick anything up (not even the access points ). Luckily, i made a backup of the original "wpa_supplicant" and restored it using root explorer and fixing permissions as described above. That at least got my wifi up and going again

My question is, does anyone know how to edit the honeycomb file to work with ad-hoc? I'll attach a link below if anyone wants the original to play around with.

I guess it is worth noting that if someone could get this going, i'd be willing to throw a few bucks their way. I'm just stumped, but it seems like it is so close i can almost taste it!

Thanks for your help!

-amruthwo

Stock wpa_supplicant file from Xoom
(lives in system/bin)

ooooh You are close. Imma gonna play with this over the weekend. I want this.

next question...

---

Ok, i'm drawing a blank here--what can you use to actually view and edit the wpa_supplicant file? I've kind of tried with notepad, but it seems futile with how many of the characters fail to render, basically making my attempts to understand the subtle changes impossible.


Can anyone shed some light on a good program for win/linux that might work better?

Originally Posted by amruthwo

Ok, i'm drawing a blank here--what can you use to actually view and edit the wpa_supplicant file? I've kind of tried with notepad, but it seems futile with how many of the characters fail to render, basically making my attempts to understand the subtle changes impossible.


Can anyone shed some light on a good program for win/linux that might work better?

we cant edit it directly with notepad, we need the source code of HC then add the adhoc code then compile it..

one thing that curious for me is the wpa_supplicant version is the same as in froyo or ginger android, but we can't just put that already adhoc enable compiled wpa_supplicant file to our HC..it will make our wifi can't see any wifi network..

hmm perhaps there is some other file involved..lets dig it..

exactly, i've been rubbing my chin for about a week on this one. I don't see why the froyo/ginger v0.6.10 file doesn't work...

maybe there is another file involved though, i'm going to go digging in the system folder to see if anything looks related i guess.


hopefully source is released soon, it would make this a little easier...

Pretty sure wpa_supplicant is a GPL project so you shouldn't need to wait for HC source for that.

What errors are you seeing in the logcat after replacing it?

i actually didn't record the log, let me do it again and i'll see what the log says. I'll report back.

log file

---

here is a bit of the log when trying to connect to wifi...

basically, it says wpa supplicant unable to initiate ap scan

Being Android noob, and since I'm trying to get this xoom to see ad-hoc networks for work (this is really important.. spent 600, expecting it to connect it to adhoc.. dang it.), would it be worthwhile to port wpa_supplicant from droid x?
Droid x reports 0.6.10. Unlike EVO, since they are both motorola products, they have something in common??

Or maybe, xoom uses a different driver? I see that droid x has tiwlan0 as its wireless, whereas xoom simply says wlan0.
Reading from here: htt p:/ /sz ym . ne t/2 01 0/1 2/a dh oc - w i fi - in - an d ro i d /
(sorry, being a new user, it doesn't let me post a link... )

someone says that wpa_supplicant needs to be compiled with the correct driver.
Does anyone know how to do this? Or am I just wrong? lol

from what i understand, the wpa_supplicant is part of the gpl, not unique to any phone manufacture. I'm no expert on the subject either though. I have no idea what is different in the xoom, but i have used the v0.6.10 which matches that of the xoom, but no dice. If you want to extract one from the droid x and edit it (assuming you know how) then it is definitely worth a shot!

let us know what you find