yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] mg00000:
Retrying since no wireless came back up after reboot.

I tried this but i think i need to give it some kind of command. The C&P and renaming went fine. Then i switched via Root Explorer back to R/O, rebooted the NC, but the wifi toggle (switched from OFF back to ON) wouldn't find wireless connections at all.

I am now going to delete the fix-file and replace it with the original bak-file and retry it. *I didn't remember to dnld Setting Profiles app either so i'll do that.
[Nook Color Android Development] lyam23:
I've tried replacing the wpa_supplicant file yet I can't get the NC tethered to my Droid1.

I see the asterisked access point on the NC. I can communicate with the Droid hotspot to some extent (as shown by the logs of the Wifi Tether app on the D1), yet it always fails to connect. Any ideas what I'm doing wrong?
[Nook Color Android Development] Thirtybird:
+1 to this - it appears that using the ad-hoc supplicant fails to store credentials configured to use EAP on HoneyComb. It definitely works to connect to my droid on ad-hoc, and also our company's guest network (no security, infrastructure mode), but the EAP secured wifi is un-connectible using the fix.
[Nook Color Android Development] Thirtybird:
I had to turn OFF access control on the Droid to get any data to flow.
[Nook Color Android Development] lyam23:
Yeah, I've got that disabled as well. Still no go. I get the message "Obtaining IP address" on the NC for about 30 seconds, then "Connection failed". And then it retries.
[Nook Color Android Development] hellomynameis:
Root Explorer worked great and running with iPhone 4 at 64Mbps
[Nook Color Android Development] Thirtybird:
Any Data encryption set? I had it as open when I had it working - I had already turned off WPA2 while trying to troubleshoot something else.

Do you get notified of a connection on the Droid?
[Nook Color Android Development] mg00000:
Help with the Wpa file. Wifi has not returned to my NC

Edit: This is now resolved. I renamed the wpa folder in /bin as well as the [original] supplicant file itself and it allowed me to paste the adhocfix file right under /bin.

I am not able to reconnect to Wifi after attempting the copy and paste of the fix WPA file. I rebooted again after trying to get the original file back in it's place. Here is what i did, maybe i misssed something you all can tell:

I deleted the new file with was renamed to just be "wpa_supplicant". So now, the orig file which was renamed to be "wpa_supplicant.bak" i renamed since it is the original, i removed the ".bak" and clicked OK.

I now only see this one file within the Wpa_supplicant folder, which is in the /bin folder, under /system.

I went into this renamed original file by long pressing and choosing Permissions, and changed the setting in there to:

-------------------Read---Write---Execute

User >---------------x---------------x

Group >--------------x------x--------x

Others >-------------x------x--------x

I believe that the correct change to this UI was the opposite permission to the "Write" column, am i right? (When i had the new file in place i took the marks out of the "Group", "Others" rows, and placed a check in the "User" row).

I see that the parent folder to Wpa_supplicant is the only folder in the /bin dir that isn't displaying a gold shield/ or badge on the folder icon (When viewed in Root Explorer). I did not notice if this existed prior to my file changes. If this is causing a possible issue can someone suggest a way to revert back; or tell me what i'm missing in my steps above? thanks all!!:)
[Nook Color Android Development] lyam23:
I've tried with encryption off an on. It appears to be connecting, just unable to obtain an ip address.
[Nook Color Android Development] chibucks:
not familiar with root explorer, but i'd imagine it's supposed to have chmod 755 access, which is User: r+w+x (all x in root explorer), Group: r+x (read & execute x), and Others: r+x (read & execute x)

try that, then reboot and see if it helps...
[Nook Color Android Development] KenNashua:
Is the B&N wpasupplicant open-source? Perhaps to fix this as well as the enable/disable a code merge instead needs to be done?
[Nook Color Android Development] jimbobalu:
Awesome, this worked. At first when I enabled wifi it acted strangely turning on and off but it finally settled down and connected to my router. I then started tethering on my Nexus One and the Nook picked it up and acquired an IP address. YAHHHH!!!!
[Nook Color Android Development] jackal424:
Anyone know why that after the nc falls asleep it loses wifi connection, not only that but i no longer see the network. I have turn off wifi and turn it back on.

This didn't happen before this mod.
[Nook Color Android Development] mg00000:
besides asterisk what am i looking for?

The phones 3G; what displays in the nookie's wireless connection listings? I don't see a new network at all. Thx for whoever helps.
[Nook Color Android Development] Juboha:
Thanks.

Works great with Windows XP SP3 wireless setup as adhoc, to share internet connection (don't have a wireless router in the office).
[Nook Color Android Development] fwdixon:
If you didn't set the permissions to match the original file you will have this kind of error. Long press the file and click "set permissions"
[Nook Color Android Development] TLJester:
Does this work with non-Android phones (access points)?

I have a Touch Pro 2 and use that to connect my laptop when traveling.

I tried with my nook, yet it would not get an IP address (though it connected and WPA verified).

Thanks
[Nook Color Android Development] babyqtangel:
@TLJester,

Not sure if this will help you, but my friend has a Nook Color tethering off his Touch Pro 2. His NC (flashed with custom Nookie Froyo) can see and connect to his phone whereas my NC (just autonootered with Stock) can not.

So, if you don't already run custom Nookie Froyo already (and wouldn't mind switching to that ROM), that might be a simpler solution for you.
[Nook Color Android Development] swapdotavi:
Sorry to raise this thread from the dead, but will this work with the current CM7 build? Or is it included? I tried briefly to connect to my phone's hotspot after upgrading from 2.1 (with this fix installed) to CM7 (2.3) and I wasnt able to do so. Do I just need to try again? Or is it safe to push this fix over top of CM7?
[Nook Color Android Development] jtbnet:
I've been using this on CM7 Stable just fine since Adhoc was disabled in CM7 in March...
[Nook Color Android Development] jkurl:
How do you edit this file?
[Nook Color Android Development] jtbnet:
There is no file to edit? /system/bin/wpa_supplicant is an executable that treats scans for adhoc networks just like infrastructure networks... so you just replace the CM7 file with the one in OP and both Adhoc and Infra will be be seen on scan as available and you can connect to either...

This is a bit of an oversimplification else the functionality would not have been diabled in mainline CM7 back in March... in Reality especially in highly network congested areas like a mall the scanning for both Adhoc and Infra and finding many of each can make locking/connecting to any individual one of them problematic using this file... for my general use this hasn't been a problem... one time I noticed the problem I swapped the origianl file back out and had no problem locking to my desired Infrastructure AP...
[Nook Color Android Development] swapdotavi:
This is informative. Thanks :)

So since this is, basically, just a "yes check for adhoc too" flag is it safe to assume the OP's files are still the most current? Or is there an updated one I should use for better results? I just re-rooted, but once I fix some network problems I'm having with an app I want to re-enable adhoc, so I'll be in the market to perform this upgrade again pretty soon.
[Nook Color Android Development] jkurl:
I am good w/ putting where it needs to be w/ either root explorer it adb pushing it.

I would like to know how to edit.
[Nook Color Android Development] :
Didn't work on CM7 stable for me.
[Nook Color Android Development] bekyndnunwind:
Also couldn't get this to work on CM7 stable...
[Nook Color Android Development] vlucchetti:
I have two NC's. One has Nookie Froyo customized, and this adhoc fix works fine. Second one has phiremod 6 on it, and it does not work. I have the two side by side and NF is up and running, P6 just sitting and waiting.

Would be great to get this fixed for cm7 and P6.
[Nook Color Android Development] speckledpig:
Would this work on any other Honeycomb devices? I would like to see this done on the Eee transformer.
[Nook Color Android Development] silentjess:
i hope this works, i've tried many things and although they connect, the disconnect almost immediately too. to e.g. connectify on laptop or barnacle on android phone and following the steps at http://nookdevs.com/NookColor_adhoc_wifi_access
[Nook Color Android Development] speckledpig:
Please let us know if you have any success with this.
[Nook Color Android Development] Tool Belt:
Anyone get MN 1.2 to connect to adhoc?
[Nook Color Android Development] vlucchetti:
FWIW, just installed Phiremod 6.2. Turned wireless tether on with my android phone. NC found it, and connected without me doing anything. I am quite the happy camper.
[Nook Color Android Development] :
Just do this:

http://xdaforums.com/showpost.php?p=13063505&postcount=39
[Nook Color Android Development] vlucchetti:
I tried this before when I was on Phiremod 6.1, and it did not work. In 6.2, adhoc = 0 and it connects to my phone.
[Nook Color Android Development] Tool Belt:
That 0-1change did not work on MN 1.2
[Nook Color Android Development] SoFresh99:
My NC has connected ad-hoc to my (stock VM optimus V using Quick settings) phone with no mods, both in autonootered 1.0.1 and now in rooted 1.2. I didn't know it wasn't supposed to work.
[Nook Color Android Development] cesar2010:
Same here NC now works with MyWi on my iphone 4 after update to Phiremod 6.2; wasn't working on 6.1. another happy camper.
[Nook Color Android Development] Tool Belt:
And we are sure these are ad-hoc networks?
[Nook Color Android Development] greenmky:
Optimus V isn't an ad-hoc connection - it's producing an infrastructure-style hotspot. Some phones do, some don't - depends on drivers and OS and some other stuff (to be short).

I've got one and it works great with the NC. But - not all phones do - some produce an ad-hoc hotspot which the NC doesn't play nice with.
[Nook Color Android Development] Tool Belt:
Thanks. Yeah my Eclair Axis is ad-hoc. I really would like to see an ad-hoc fix.
[Nook Color Android Development] rsptexas:
Possible Fix Requires Recompiling Old Patched Versions

The old patched (recompiled) versions of wpa_supplicant at http://nookdevs.com/NookColor_adhoc_wifi_access worked flawlessly on NC 1.0, 1.1, Honeycomb preview, etc., but it does not work, apparently, on NC 1.2.

That version was taken from a wpa_supplicant IBSS patch found via a Google search, http://szym.net/android/ and was compiled against TI's Omapedia Eclair sources ( http://omappedia.org ) - although that was a different framework than the B&N stock build, it worked. See http://szym.net/2010/12/adhoc-wifi-in-android/.

On further reading on other xda forums, e.g., the HTC Hero, G Touch forum at http://xdaforums.com/showthread.php?t=754961, that have dealt with the same issue, and found a solution. It appears that NC Android 1.2 uses a newer Android v0.6.x wpa_supplicant and thus the fixed ad hoc wpa_supplicant must be recompiled with new developer libraries -- whereas 1.0, 1.1, the Honeycomb preview, etc. are built from 1.1 or older developer developer libraries.

If someone can do this, the problem should be solved.

------------ Update ----------

Another device forum has apparently successfully "fixed" the new version 6 of the wpa_supplicant to implement a working ad hoc version for their device ... regretfully, however, their fixed version 6 binary file will not work on the Nook Color (e.g., different sdk, libraries, processor, etc.). Hopefully, someone with sum Nook Color programming experience can borrow the source code and finally resolve this matter on the Nook Color 1.2. See http://xdaforums.com/showpost.php?p=10675148&postcount=876
[Nook Color Android Development] kgbcapthowdy:
so i just got this and cm7 going. Pushed the new wpa file and it sees ad hoc but no connection. Am i under the right impression ad hoc is not supported as of right now and only infrastructure? I pushed the backup back into the NC and it actually is seeing adhoc networks but not connecting. Thanks and sorry if this has been answered before.
[Nook Color Android Development] DetCochese:
It was working fine for me yesterday and today, it crapped out. It sees the phone, but as soon as I try to connect with the NC, it goes into the not in range box, even though it is showing as an available connection right above it. Frustrating.
[Nook Color Android Development] BroDroid:
I tried that also, and it didn't work at first. I changed the wireless frequency channel in the app on my phone. I changed it to channel 1 and now my NOOKcolor connects with no problem.
[Nook Color Android Development] kumarnarain:
wpa supplicant for nook color 1.2

Hai

I am unable to use the adhoc mode for my nook color 1.2 Has this been recompiled for 1.2? PLease let me know if it is available somewhere

regards

kumar
[Nook Color Android Development] caveboy:
IPhone 4 with cyanogen mod

Any luck with this config? I tried Mywii and PDAnet with no luck
[Nook Color Android Development] johnopsec:
Lets try this again... Maybe I can attach a zip file...

If this works, there will be two zip files...

I have found that the Adhoc enabled wpa_supplicant file didn't play nice with respect to wifi sleep policy.

View attachment wpa_supplicant.backup.zip is the original Nook Color wpa_supplicant file.

View attachment switch-adhoc.zip contains the original wpa_supplicant, the adhoc enabled wpa_supplicant and two scripts, adhoc and infrastructure.

Instructions for using the second:

unzip the file to a work directory on your computer.

adb shell mount -o remount rw /system

adb push wpa_supplicant.infrastructure /system/bin

adb push wpa_supplicant.adhoc /system/bin

adb push adhoc /system/bin

adb push infrastructure /system/bin

adb shell chmod 755 /system/bin/wpa_supplicant.infrastructure

adb shell chmod 755 /system/bin/wpa_supplicant.adhoc

adb shell chmod 755 /system/bin/adhoc

adb shell chmod 755 /system/bin/infrastructure

adb shell mount -o remount,ro /dev/block/mmcblk0p5 /system

After this is done, you can switch back and forth between the original and the adhoc enabled wpa_supplicant by starting a shell on the Nook Color and running the following commands:

To switch to adhoc mode:

su

adhoc

To switch to infrastructure mode:

su

infrastructure

Hope this helps people out.
[Nook Color Android Development] Droidish:
I made a thread about disabling the wifi sleep policy using spare parts. I don't have the link handy but you should be able to find it easy enough.

EDIT: http://xdaforums.com/showthread.php?t=866502

PS Awesome fix.
[Nook Color Android Development] johnopsec:
From my testing, when you set the wifi sleep policy to "never" in Spare Parts, the Nook Color wifi will still sleep when the screen blanks or you short-press the power button to lock the Nook - IF you're running on battery. If it's plugged into the charger, wifi doesn't sleep after setting it to "Never".

With the Adhoc enabled wpa_supplicant, wifi seems to ignore the policy and always sleeps whenever the Nook Color is locked or the screen blanks.
[Nook Color Android Development] monsterpt:
Is this possible to do within root explorer and a terminal emulator? My comp is out of order.

If so can someone run through the process for me.
[Nook Color Android Development] rogerdugans:
I also had some trouble last night and found exactly the same issues, so happy to see that somebody else already wrote scripts to change back and forth. I suck at scripting.

It should be possible to do all of the above steps with root explorer and a terminal.

I will restore the original file to get wifi working and if nobody else has done so when I am done, I'll try to add the swap scripts using just the NC and post the steps.
[Nook Color Android Development] monsterpt:
Awesome, thanks. Its been awhile since I did any of this on the droid.
[Nook Color Android Development] rogerdugans:
Hopefully someone else gets to this for you fairly soon.

I now have wifi for about 30 seconds at a shot, lol.

Note that I do NOT blame either of the wifi fixes one bit-

I have been mucking about with this thing tremendously and I've been waiting to see how long before I had to do a full reset.

It looks like now. ;)
[Nook Color Android Development] cweber01:
not working for me?

Thanks for the fix can't wait to get it working but I can't seem to get it to work for me.

I am using Baranacle on a mytouch.

One the fix is applied will the mytouch network show up in the list of available wifi networks on the nook or do I need to manually create it?

I've tried manually entering without luck. Tried w/wo security.

When you enter SSID do you need to include the asterisk in front or is it assumed by the system?

Any ideas?

Thanks
[Nook Color Android Development] johnopsec:
It will show up in the list. You don't add it manually.
[Nook Color Android Development] rfbarr:
I am not sure why but when i try to open a shell and type su it says su: not found.

I can connect to an ADHOC network so I know it works. Just not sure why the scripting thing did not work.
[Nook Color Android Development] droiddog:
Thanks. This is great. Two questions:

1. Do you need the original wpa_supplicant file pushed back into the folder?

2. What terminal emulator do you use?

Thanks again.
[Nook Color Android Development] rogerdugans:
Sorry for the long absence- family drama a couple of hours away.

While witing around in the midst of it I was able to get the adhoc/infrastrure scripts installed and partially tested completely on the nook using Root Explorer and terminal.

I downloaded the files on my droid, pulled the microsd out and put it in the nook. Copied them to My Files and pulled the card back out (mount/unmount properly of course.)

I unzipped the scripts and used Root Explorer to make /system/bin rw.

Copied the files into /system/bin

Started a terminal session and typed su and then went to that directory-

su

cd /system/bin

ls

(ls to make sure the files are there.)

and then

chmod 755 /system/bin/wpa_supplicant.adhoc

chmod 755 /system/bin/wpa_supplicant.infrastructure

chmod 755 /system/bin/adhoc

chmod 755 /system/bin/infrastructure

Used Root Explorer to make /system/bin ro again.

For good measure I rebooted the nook- in the terminal: reboot

After the reboot I opened terminal and did

su

adhoc

and I was able to connect to the wireless tether on my Droid. :)

Unfortunately I did continue to have problems with dropping the connection- finally told the screen to not time out for an hour and that seemed to take care of that. I was able to download 2 books into the Android Kindle software over the tether.

I just got home and have not yet checked infrastructure mode.

ETA:

I just spent a couple of minutes in infrastructure and I'm still having issues- connect and in about 30 seconds I get lost signal- connected, no internet.

rebooted, switched wifi on and off a few times and reran the infrastructure script a few times- no change.
[Nook Color Android Development] rogerdugans:
Ok, there is still some sort of issue somewhere. I am sending this while tethered to the droid but I can't keep an infrastructure connection open longer than 30 seconds.

Screen and wifi are not timing out as far as I can tell.

I have gone so far as to delete the symlink the script created for infrastructure and copied the real file back in as wpa_supplicant. I have powered down, booted up and no joy.

Suggestions?
[Nook Color Android Development] rogerdugans:
Delete me- slow connection, double posted
[Nook Color Android Development] macndroid:
G1 works

I previously tried a version of the wpa_supplicant from the site ref by the OP but didn't go so far as to do the recompile. The pre-compiled wpa_supplicant didn't work (have an old thread around here) but this one did!

Good old HTC Dream/G1 + Wifi ether + Nook color = happyness
[Nook Color Android Development] forcedfab:
Does anyone know how to setup the NC to use a proxy when connected to my EVO . When I enable my 3g hotspot feature , the NC no connects no problem , but using Cricket as my provider , my phone is setup to use wap.mycricket.com on port 8080 for web/data connections thru iptables and autostart root program . Wondering if I could modify my setup on my phone to work on the NC . Would be nice to tether to the NC when traveling , the 4.3" evo screen is nice , but the NC would be even better .

here is some basic info that describes setting up the internet connection on the droid , the evo is very similar .

go to the market using WI-FI and download and install Autostart.exe.

Open the Voice Dialer on the phone and say “Open APNs” and click open.

Click on the Verizon and edit everything to match below:

Name - Cricket

APN internet

Proxy wap.mycricket.com

Port 8080

Username yourphonenumber@mycricket.com

Password cricket

Server wap.mycricket.com

MMSC http://mms.mycricket.com/servlets/mms

MMS Proxy wap.mycricket.com

MMS Port 8080

MCC 310

MNC 004

Authentication Type PAP or CHAP

APN type <Not set>

Now click the menu button and click Save.

Before starting the next step make sure you have the u2nl file in your this folder c:/android/tools and also that you have you autostart.sh file in this folder c:/android/tools.

Now go to command prompt and type the following commands,

cd c:\android\tools

adb shell

mkdir /data/opt/

exit

adb remount

adb push c:\android\tools\u2nl /system/bin/u2nl

adb push c:\android\tools\autostart.sh /data/opt/autostart.sh

Now:

adb shell

chmod 0755 /system/bin/u2nl

chmod 0755 /data/opt/autostart.sh

reboot

Now, once your phone has rebooted, you should have working web, mms, app, gps, and all. If you don’t go back and check all the steps to insure you did everything exactly right.
[Nook Color Android Development] rogerdugans:
Just to follow up one the difficulties I had earlier- still having them.

Right now I CAN use either infrastructure or adhoc modes but I need to manually rename the files for whichever I need and reboot to change between them.

The script TRIES to do it, but it fails. The ONLY thing I noticed about this is that the perms for the symlink are not the same as for the actual files.

I have not gotten any further into it yet as I switched to getting the market installed instead. ;)

I will try further and see if I can get anywhere, but...

the fact is that I am not a guru or a hacker anyway.

I am just a hack who benefits from the work of others.
[Nook Color Android Development] webvan:
I wonder if the best solution wouldn't be to use the gscripts posted here : http://www.chinadigitalcomm.com/android-a81/a81e-connect-to-ad-hoc-wifi-t1413-10.html by SlavaNN - they work fine on the Witstech A81.
[Nook Color Android Development] johnopsec:
When you open a shell, do you get a $ or a # for your prompt?

You need to be root to run the scripts. If you don't have su installed, I suggest you install z4root which will give you everything you need.
[Nook Color Android Development] johnopsec:
The original is called wpa_supplicant.infrastructure in the zip that I uploaded. The scripts simply symlink wpa_supplicant to either the infrastructure or the adhoc version.

I personally use connectbot for a terminal.
[Nook Color Android Development] droiddog:
Thanks. It works great.
[Nook Color Android Development] rfbarr:
Yea I did not have superuser installed. Funny thing though if I left out the su and just ran the adhoc or infrastructure script it would work. either way I got superuser installed yesterday.