Related
Great news everyone! </farnsworth>
ADHOC Wifi Support for Nook Color (stock)!
[EDIT] There appears to be an issue reconnecting when wifi sleeps and comes back on. Researching a permanent fix, in the meantime go to settings -> Wireless and toggle wifi off/on to correct it
This fix will allow you to connect to ADHOC wireless networks ( such as to a laptop or with wifi-tether on an android phone )
Like most other fixes, this requires your nook to be rooted and usb adb working, please follow the guides here and/or at the nook dev wiki first!:
Rooting: http://nookdevs.com/NookColor_Rooting
USB-ADB: http://nookdevs.com/NookColor_USB_ADB
HOWTO enable ADHOC tethering:
1. Download and unzip the attached zip file below, this should give you a wpa_supplicant-adhocfix file
2. *DISABLE WIFI ON YOUR NC*
3. Make a backup of your current wpa_supplicant:
Code:
adb pull /system/bin/wpa_supplicant wpa_supplicant.backup
4. Remount the /system partition RW:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
5. Push the new wpa_supplicant:
Code:
adb push wpa_supplicant.adhocfix /system/bin/wpa_supplicant
6. Fix permissions:
Code:
adb shell chmod 755 /system/bin/wpa_supplicant
7. Remount the /system partition RO:
Code:
adb shell mount -o remount,ro /dev/block/mmcblk0p5 /system
8. Enable WIFI on your NC, you should now be able to see ADHOC networks in the list! ( they'll be displayed with a (*) prefix )
[edit] Credit where credit's due, this was taken from a wpa_supplicant IBSS patch I found via a Google search, if anyone knows the party responsible, let me know so I can credit them properly!
http://szym.net/android/
This is compiled against TI's Omapedia Eclair sources ( http://omappedia.org ) - since this is a different framework than the B&N stock build, I can't guarantee this will work, won't brick your device, etc. Use at your own risk!
If you encounter any problems, please use this thread to let us all know.
That's all there is to it, enjoy!
I can confirm that this will allow you to connect you Nook Color to an adhoc network created by a Jailbroken iPhone 4 and MyWi.
Works great! Thanks!
WHOEVER made this fix....THANK YOU! This was the biggest thing I was missing on my NC! Works great!
Cool you figured this out! For some reason, I've been able to use the adhoc network on my Androidized HTC Leo (HD2) since the first time I tried, even before rooting.
Sent from my Rooted Nook Color using XDA App and iPhone MyWi adhoc connection.
You guys ROCK!!!!!!!!!!
Works great with my Droid now. Thanks!
Confirmed working with Mobile Wi-Fi Router on my VZW Touch Pro2.
Many thanks! Another big step!
Work perfectly on my motorola droid 1 using Wireless tether or Barnacle. Thanks for sharing this with us
Works great with AT&T Samsung Captivate and android-wifi-tether ver. 2.0.5-pre15.
Thank you very much!
My NC is stuck at trying to obtain an IP address from my Droid 1. I'm using Barnacle.
Any ideas?
*edit*
It took several attempts but it finally connected. Being able to get connected anywhere is awesome. Thanks for posting this!
Working great from my epic 4g.
Pro Tip: If you want a quick way to toggle wifi (and a few other settings) tap the clock in the nook's notification bar for a quick settings dialog.
Thanks for this. I can now use my nook at work tethered to my phone. You may want to edit the typo in step 7 as we all caught it but someone may not.
Philosophy757 said:
Thanks for this. I can now use my nook at work tethered to my phone. You may want to edit the typo in step 7 as we all caught it but someone may not.
Click to expand...
Click to collapse
Thanks for noticing, corrected the extra 'o'
As noted in the OP, this is based on TI's omap eclair reference sources, and there *is* a pretty glaring bug.
Basically, if your screen goes to sleep, waking it back up triggers a wifi-reconnect which fails to reinitialize the network properly. Your wifi settings will show 'Connected, no internet' when this happens.
Toggle Wifi off/on to fix this, I'm working on a permanent fix right now and will update when it's working.
Thanks everyone for testing and boosting the ol' ego a little
Some random tips so folks don't repeat the same mistakes I made while doing installing the ad hoc feature.
Don't choose to "forget" a wireless access point because then it doesn't appear again even if the device sees it. You'll have to manually enter the SSID, encryption type, and password to get it to work properly.
While mounting and remounting using adb, if you get a device busy error, disconnect the nook from the computer and come back to it later. Then reconnect and try again. For good measure I also powered down the nook. Not sure what happens if you leave the system folder mounted as RW, but I suspect bad things could happen.
Oh and the fix works like a charm. This is one really nice device.
Works perfect on my NC tethered to my MyTouch 3G ( rooted with CyanogenMod-6.1 )
Many many thanks to the dev. !!
Nice work, and thank you. Working fine with another rooted droid (running CM6.1).
I had the "device busy" error and went ahead and unplugged, then reset to ro with Root Explorer- no problems.
This reminds me of when the Droid first got rooted- took a little while to make progress but every few days that would be another BIG, popular advance.
Thanks so much!!!! Droid1 still has life! Yeah.
Thanks. This works great. One question. Does anyone know where I can get the original wpa_supplicant file? I misspelled it so I don't have a good backup. Thanks.
Original nook wpa_supplicant
Here ya go...
OK. Maybe I can't upload files.
I apologize in advance if this subject is posted elsewhere. Please kindly point me to the thread...
I'm a noob and just bought a viewsonic G-tablet.
I've been searching xda for a day now, and I cannot find a how-to guide on how to make the "adhoc wifi hack" to work on the stock ROM.
I've found this:
http://forum.xda-developers.com/showthread.php?t=754961
But I can't find a definitive answer on how to "flash this in recovery mode" specifically on the G-tab.
I'm assuming to proceed to installing ClockworkMod from (http://forum.xda-developers.com/showthread.php?t=865245)
and then flashing the "adhoc-signed zip file" from there.
I realize ClockworkMod is used to flash ROM's, so I'm wondering if this "adhoc patch" file can be flashed the same way without affecting the stock ROM.
Please let me know if this is the correct path to go down.
Thanks for your help in advance.
what is that
There is an easier solution. Search for the stock enhancement pack in the development forum. You will have to flash the file in CWM or with standard recovery. Instructions are in the post.
Enjoy your AdHoc goodnes.
Okay, I answered my own question, but now have more problems to deal with.
I installed the "adhoc signed zipped" file with CWM. I created a new folder in the gtab root and put the "adhoc signed zipped" file in there. In CWM's menu, there is a selection to install zip/flash from an internal folder.
okay, got adhoc to work. When scanning for networks, the adhoc networks show up with the * as expected. I connected successfully to my wm6.1 phone with wmwifirouter.
However, the gtab cannot load up websites. I do see spurts of data on the phone being passed, but it seems to be spurts and it stops. Browser on gtab say check connection.
So I'm thinking that this has something to do with the adhoc hack on the stock rom. I'm going to bite the bullet and try a non-stock ROM to see if this will resolve the problem.
@jasco: I cannot find the stock enhancement pack in searching... I might need to search harder.
Flashed this to my Gtab to test it out. Completely broke my wifi. No longer will see any wifi or adhoc networks. I had to reflash.
I don't have a phone that I can tether to, but my son does, and I just got this working w his phone.
What I did was:
- unzipped the file from that thread above, and got the wpa_supplicant file from the system/bin dir inside the unzipped dir
- turned off wifi
- used z4root to get temporary root and root explorer to make /system R/W
- used terminal to copy the new wpa_supplicant file to /system/bin
- changed permissions of /system/bin/wpa_supplicant to rwxr-xr-x
- turned wifi on
I was then able to see his SSID, and connect using WEP.
Jim
I would like to try this with my tablet and I am having a hard time understanding these instructions. can you please make a detailed set of instructions with more steps? If you would do this I am sure there would be a lot of people that would be truly grateful, I being one of them.
Thanks,
Waspvl1
All depends....
What if you don't have an Android phone?
I use WM 6.5 phone (in my case HD2) to tether to my G-tab.
Using program WMWiFiRouter. G-tab picks it up as another regular router.
Never had a problem and most important for me, don't have to go through all of the trouble configuring AdHoc.
JMO.
here is an easier method a version of the adhoc from froyo modified to support adhoc.. i was using it on my galaxy s.. now using it on the gtab works fine..
1. you need to be rooted.
2. use rootexplorer
3. turn off wifi
4. back up the existing file in /system/bin to somewhre on your sd or sd2 card.
5. using root explorer copy this file over the one in /system/bin
make sure to put /system in read/write mode (top of root explorer when in that directory) (also need to unzip it first)
I just updated my rooted tether on my droid x and now it works. Gtab sees my adhok without the zip.
yelrx8 said:
Okay, I answered my own question, but now have more problems to deal with.
I installed the "adhoc signed zipped" file with CWM. I created a new folder in the gtab root and put the "adhoc signed zipped" file in there. In CWM's menu, there is a selection to install zip/flash from an internal folder.
okay, got adhoc to work. When scanning for networks, the adhoc networks show up with the * as expected. I connected successfully to my wm6.1 phone with wmwifirouter.
However, the gtab cannot load up websites. I do see spurts of data on the phone being passed, but it seems to be spurts and it stops. Browser on gtab say check connection.
So I'm thinking that this has something to do with the adhoc hack on the stock rom. I'm going to bite the bullet and try a non-stock ROM to see if this will resolve the problem.
@jasco: I cannot find the stock enhancement pack in searching... I might need to search harder.
Click to expand...
Click to collapse
Have exactly the same problem. Been looking for a solution for quite a while. Can't understand why this should be so difficult.
I went another route, but with the same problem.
I thought the "ad-hoc signed zipped" file install from CWM as I've described about was the issue, so I went back to the stock 3389 ROM with the tnt enhancement pack.
Exact same issue, the ad-hoc connection with WMwifirouter is connected, but no internet data will pass on the connection.
Tethering without root?
I'm definitely a noob to all this, although I have had an android phone for about 6 months now. I haven't found any roms to flash to my samsung transform so I haven't gotten root on it yet. Is there a way to tether to my g-tab (Vegan 7) with out gaining root to my phone? By the way, I really like the new rom.
I'm running a wireless tether app on my rooted Droid X and can connect my gTab to it without any updates or hacks or anything else. I'm running stock VEGAn 5.1.1 without any other tweaks.
I'll flash back to VEGAn 5.1.1 and see if tethering works with out having to hack my phone.
rosscopicoterry said:
I'll flash back to VEGAn 5.1.1 and see if tethering works with out having to hack my phone.
Click to expand...
Click to collapse
FWIW, I'm running this ROM and just tried it. It connected fine to my iPhone w/MyWi. No hacking required.
No adhoc transfers with Vegan-Tab Ginger RC1
I've flashed this ROM 5 times now and ran some tests each time. I can connect to my WMWifirouter adhoc network, get an IP, but there is nothing going through...
My understanding is that this rom already has a hacked supplicant. What's my next step? Should I bother trying with the provided wpasupladhoc.6.1.zip above? Thanks in advance.
I cannot figure this thing out for the life of me. Has anyone gone the route of trying to use blutooth to connect from their android phone to the g-tab? I can get it to pair but not connect. G-tab may have to go back if I can't figure this out.
1.2-4349 Ad Hoc tether
lgkahn said:
here is an easier method a version of the adhoc from froyo modified to support adhoc.. i was using it on my galaxy s.. now using it on the gtab works fine..
1. you need to be rooted.
2. use rootexplorer
3. turn off wifi
4. back up the existing file in /system/bin to somewhre on your sd or sd2 card.
5. using root explorer copy this file over the one in /system/bin
make sure to put /system in read/write mode (top of root explorer when in that directory) (also need to unzip it first)
Click to expand...
Click to collapse
Tried it on 1.2-4349 and it appears to work just fine. Immediately detected ad hoc tether on my original Droid running gingerbread.
Does the phone need to be rooted? Or are you putting these files on the g tab?
I think I'm gonna write a small app to enable ad-hoc mode as seen for other android models. Anyone interested ?
Must have:
Single button click to enable ad-hoc wifi mode
Restore option, to revert back to previous state
Check if root is enabled, check if device is supported
Anything missing?
-----------------------------
Update:
App is available in the market.
Reported to work on:
Samung Galaxy Tab GT-P7510, GT-P7500
Samsung GT-I9100 * (Samsung Galaxy S2) reported by PAD
Samsung SPH-D710 Galaxy S2 Epic Touch 4G * reported by Scott
Samsung GT-I9000 * (Galaxy S I)
Nexus S * reported by Arpit
BBK vivo v1 * reported by thesunfei
HTC Desire * reported by Jens
Droid * reported by James
* Requires compatibility check to be disabled.
Probably more devices are supported, I will add them when reported.
Market link: https://market.android.com/details?id=nl.arendmedia.wifiadhocenabler
Discussion: http://www.arenddeboer.com/wifi
This would be great...post a link when ur done
make sure to make two apps one that require pershoot kernel and another one without pershoot kernel just a stock one, if so the app will be great, gd luck.
tarekkkkk said:
make sure to make two apps one that require pershoot kernel and another one without pershoot kernel just a stock one, if so the app will be great, gd luck.
Click to expand...
Click to collapse
Why not check inside the app what kernel is used and act accordingly ?
BTW I have used the same procedure to enable ad-hoc for the stock kernel as well as the pershoot kernel, using the same wpa_supplicant file.
I envision the app should:
Check if the device is supported (for now P75XX)
Request/verify root access.
Check if device is already ad-hoc enabled by this app, if not continue.
Verify if wpa_supplicant in /system/bin/wpa_supplicant is in a sain state (verify md5 hash with original) if it doesn't match warn user if he still wants to continue.
Create a copy of the original wpa_supplicant file.
Copy adhoc-enabled wpa_supplicant to /system/bin/wpa_supplicant, overwriting the existing file.
chmod 755 /system/bin/wpa_supplicant
chown system.wifi /data/misc/wifi/wpa_supplicant.conf
Inform user to reboot for the changes to take effect.
I'm not an expert on wpa_supplicant so any help is appreciated.
adeb2 said:
Why not check inside the app what kernel is used and act accordingly ?
BTW I have used the same procedure to enable ad-hoc for the stock kernel as well as the pershoot kernel, using the same wpa_supplicant file.
I envision the app should:
Check if the device is supported (for now P75XX)
Request/verify root access.
Check if device is already ad-hoc enabled by this app, if not continue.
Verify if wpa_supplicant in /system/bin/wpa_supplicant is in a sain state (verify md5 hash with original) if it doesn't match warn user if he still wants to continue.
Create a copy of the original wpa_supplicant file.
Copy adhoc-enabled wpa_supplicant to /system/bin/wpa_supplicant, overwriting the existing file.
chmod 755 /system/bin/wpa_supplicant
chown system.wifi /data/misc/wifi/wpa_supplicant.conf
Inform user to reboot for the changes to take effect.
I'm not an expert on wpa_supplicant so any help is appreciated.
Click to expand...
Click to collapse
fyi, If you want it to work with all Android versions, don't forget that the wpa_supplicant is not always in the same spot(sometimes in in the /etc folder).
I would also like to see this app. Good luck xD
shaolinx said:
fyi, If you want it to work with all Android versions, don't forget that the wpa_supplicant is not always in the same spot(sometimes in in the /etc folder).
I would also like to see this app. Good luck xD
Click to expand...
Click to collapse
Thanks shaolinx,
It would be great to get all the info for the various devices.
I have started the build and completed the initial verifications, has root, md5hash comparison etc. If anyone can provide details about the location and specific wpa_supplicant files I can add it to this app.
check whenever Wifi On or Off, it will error when you change wpa_supplicant when Wifi on
and afaik not need to reboot for changing wpa_supplicant
Correct Me If I Wrong
AnakTeKa said:
check whenever Wifi On or Off, it will error when you change wpa_supplicant when Wifi on
and afaik not need to reboot for changing wpa_supplicant
Correct Me If I Wrong
Click to expand...
Click to collapse
Good to know, I will request flight-mode before proceeding.
I also noted that after switching to the new wpa_supplicant, the signal strength is no longer visible in the wifi icon. Does anyone know whether this is a known issue ?
adeb2 said:
Good to know, I will request flight-mode before proceeding.
I also noted that after switching to the new wpa_supplicant, the signal strength is no longer visible in the wifi icon. Does anyone know whether this is a known issue ?
Click to expand...
Click to collapse
Mine was stable after replacing the original wpa_supplicant file.
Update:
The app is nearing its final stages of completion. I will probably post the link around Sunday. Have to test it first on the stock rom as well as some of the new ICS roms. First version will be raw and unpolished but should be safe and in good working order. I will rewrite it after the initial release to make it easier to add new devices.
Absolutly YES! very interested
The app is ready, I'm currently pushing it into the Market. Will post the link here shortly.
https://market.android.com/details?id=nl.arendmedia.wifiadhocenabler
Request device support or report bugs in the comments on http://www.arenddeboer.com/wifi
Features:
- Enable WiFi Ad Hoc mode (and keep infrastructure)
- Restore original settings
- Fix WiFi permission issues
Requires:
- Root Access (Superuser)
- BusyBox
Issues:
- No WiFi signal strength visible in taskbar
Please be aware this might potentially brick your device (I have tested the app vigorously on several roms and found no problems). I take of course no responsibility for any real or perceived damage...
Let me know if it works for you so I can improve the app.
Regards
FYI.....Task 13.1 works with adhoc wifi, out of the box!
Thank to the TASK team!
Not sure when they did starting this into the Rom, maybe from Pershoot's kernel?
But thanks anyway. Save me time to copy the WPAsupplicantfile over, which I carry with me from Galaxy tab 7 days!
Hehe, at least it was a nice way of learning root lated tasks in app development But it's still handy as the current kang ics roms do not ship with a modified wpa_supplicant.
when i try to connect it says obtaining ip and after that it disconnects
Ad Hoc Wi-Fi can be a bit tricky to setup, can you create a connection with other devices? I also believe you can make only a single connection between ad hoc devices. So be sure the other device is not already connected.
It was fun working on this app, but is has proven to be difficult to make something that enables Ad Hoc on a wide spectrum of Android devices. Therefor I will no longer be updating the application and will remove the "report to developer" option. My next project: running Linux native on my Galaxy Tab P7510.
Starting point will be this thread by poitee -> http://forum.xda-developers.com/showthread.php?t=1189251
Thanks for the feedback.
Nice! Thanks for the app.
I deleted my apk :-( and it doesn't look like you have a stable version up for download. You think you could hook me up with a link? Thanks man!
I got fed up with crappy wireless reception in a hotel and decided to use my RTL8187 based Alfa USB wireless adapter with my Prime. Here's how it works, pretty rough and open to improvement but it works.
Set up a chroot (ubuntu/debian will work); everything is done within that chroot
Compile and install the drivers for your usb adapter (see the Kernel modules thread for instructions)
apt-get install wicd-curses (or wicd-cli if you prefer), wpasupplicant and dbus plus any of its dependancies
Turn off the broadcom wifi that's controlled by android
insmod your modules (in my case eeprom_93cx6.ko, mac80211.ko, rtl8187)
start dbus and wicd (/etc/init.d/dbus start; /etc/init.d/wicd start)
run wicd-curses (or wicd-cli), refresh the network list and connect to your network
configure dns for android to your dns or to googles (setprop net.dns1 8.8.8.8)
???
Profit
To stop using external usb wifi, reverse the steps; basically:
stop wicd and dbus (/etc/init.d/wicd stop; /etc/init.d/dbus stop)
kill any running dhcp clients (killall dhclient)
rmmod your modules (in my case eeprom_93cx6.ko, mac80211.ko, rtl8187)
To be able to insert mac80211 without it complaining about missing symbols for ewma_init and ewma_add, I had to add lib/average.c to the mac80211 module; it's pretty simple, here's how i did that:
Go to your prime kernel source tree (e.g. /usr/src/linux)
cp lib/average.c net/mac80211/
Edit net/mac80211/Makefile and add average.o to the list of objects for mac80211-y (don't miss the trailing backslash if you add it halfway)
For simplicity sake I've added the modules for an rtl8187 based usb nic to this post. These are built against the 9.4.2.7 kernel source, and work fine for the 9.4.2.11 release (current ICS release as of Feb 07 2012).
Oh and I don't recommend doing this with androids wifi turned on, it kind of breaks it until you reboot your tab. So if you're smart you'll script the above and spit out a nice warning that your broadcom module is still loaded and then exit. I had no problems switching between external USB wifi and built-in wifi as long as I only turned one of them on exclusively.
Enjoy solid wifi on your prime
,can you show screenshots of how much of an improvement it was using a USB wifi device vs. Stock wifi. You should relay this info in the kernel modules thread n SaturnDe can probably clean it up or simplify more or make it easier to implement. He could add it to his driver packs and make a new ATP tweaks version. For quick app enabling of this USB wifi method. This is very cool. I really would like to see how much of an improvement in reception thisngives.
You can't use the external wifi together with the android wifi control, it isn't compatible. So screenshots make no sense. This is why you need the chroot and wicd-curses; that's where you configure your wifi connection, not in android.
As for the increase in reception, it depends on your usb adapter. If you have one with an external antenna that is 6 feet long, you can figure out how much of an improvement that would be. Nothing is stopping you from connecting an even bigger wifi antenna if you want. So, reception increase could be anywhere from a few dB up to long range 5km wifi using powerful long range antennas.
infernix said:
You can't use the external wifi together with the android wifi control, it isn't compatible. So screenshots make no sense. This is why you need the chroot and wicd-curses; that's where you configure your wifi connection, not in android.
As for the increase in reception, it depends on your usb adapter. If you have one with an external antenna that is 6 feet long, you can figure out how much of an improvement that would be. Nothing is stopping you from connecting an even bigger wifi antenna if you want. So, reception increase could be anywhere from a few dB up to long range 5km wifi using powerful long range antennas.
Click to expand...
Click to collapse
Lol, I believe you're being told to do it yourself 'darin. I have a nice little wifi usb adapter, I'll give this all a whirl later on after work.
Certainly not a solution for myself, but a simple workaround for those uncomfortable with modding and who don't mind annoying sticks coming from their tablets/laptops. Not saying anything against this, I just always hated using older laptops with usb adapters and don't see me liking it more on a smaller, more stream-lined device.
buxtahuda said:
Certainly not a solution for myself, but a simple workaround for those uncomfortable with modding and who don't mind annoying sticks coming from their tablets/laptops. Not saying anything against this, I just always hated using older laptops with usb adapters and don't see me liking it more on a smaller, more stream-lined device.
Click to expand...
Click to collapse
FWIW, this can also be used to run aircrack or other wifi security analysis tools with, which aren't able to ever run with the builtin broadcom adapter. So it has other uses too
infernix said:
FWIW, this can also be used to run aircrack or other wifi security analysis tools with, which aren't able to ever run with the builtin broadcom adapter. So it has other uses too
Click to expand...
Click to collapse
Has anyone tried doing so with their ATP? I'd be very interested to know. I've had a bunch of problems with the build-in card in terms of using the bt5 pentest suite so this might potentially solve some of those problems
Yeap, done with BT5 for arm and ALFA AWUS036H (Rtl8187), apt-get the aircrack tool and bang! : monitoring mode enables
Thanks a lot to the OP for the modules !
what version of linux are you guys using? I was trying to install wicd-cli and wicd-curses through my bt5 and had no success. wicd-curses just can't install on arm bt5 for some reason stating that some dependant libraries are incompatible. wicd-cli gives me an fopen error during install and then craps out when I try to run it.
Thanks for the info, one question tho.
Did you have to do anything special to get the wicd client to run, I get the error 'cannot connect to dbus socket' or something to that effect..
I have tried wicd-cli, -curses, and -gtk
Any help would be appreciated.
Dear Sirs,
This may be newbish, but where can I get the source for the kernel modules the op mentioned. I have obtained my kernel source for my phone, but can't seem to find the source I actually need to compile, rtl8187, etc.
Update:
Alright, I found them, they are part of the compat-wireless package. http://www.aircrack-ng.org/doku.php?id=compat-wireless
I still can get it to compile, but I guess I need to learn a little about cross compiling.
I did find a kernel for my device with the modules already built in, used and voila. Cracked a wep key in about 5-10 minutes. I was happy, happy, happy. Then, a ruinous moment occurred. Almost the very second aircrack-ng finished cracking the key, my phone came up with a low battery warning, I was using a awus036h wifi adapter and it was draining my battery fast, I had about 50% to begin and had the 14% warning hit me about 10 minutes in, funny thing is the warning is usually 14%, but this time was 13%, go figure? Anyway seconds after the warning my phone just blanks, turns off. I plug it in and reboot and the battery is at 0% and stuck there, so a word of warning:
An external wifi adapter my require more usb host juice then the battery can safely supply. I have seen people using powered hubs to circumvent draining the phone battery, I would defintiely recommend the practice.
Ok, if the last poster was noobish then i dont even know where i would be because i need help just deciphering wtf OP said.
I realize the drivers for each wireless adapter are going to be a little different... because each wireless adapter is different, but can someone translate this into non geek? I dont even know where to begin.
Can this work using the ubuntu/backtrack/linux installers from the market? Ive muddled my way through that and got linux working that way, or is this completely different?
I just wanted to say THANKS! I now have my Alpha card working in Monitor mode on my TF300T Transformer PAD and man it feels good! I have never been able to get this to work and have been trying to use an external card in backtrack for a loooong time! Thank you 1 million times!
Hi! Thanks for instructions. I got compile and install driver for my G-Sky (rtl8187) on AllWinner A10 (Ainol Aurora II) with android 4.0.4 and 3.0.8 kernel. All network settings were done with tablet's terminal (without PC). Only one problem remains - I can't undestant connecting to wpa networks - it's too difficult. Here: http_://nuzhen-sovet.ru/content/podklyuchenie-vneshnego-wi-fi-adaptera-k-planshetu-na-android-4 you can read my manual with connection to nonWPA networks on russian (read with google translate).
I am wondering if something like this could be used for the folks concerned with bt\wifi fallout. There are plenty of bluetooth dongles out there that are small enough to leave in the dock full time. I have the fallout I just dont use bluetooth enough to care.
BlackUbuntu 12.04 V4: http://kat.ph/blackubuntu-12-04v4-for-android-s3-tested-t7252750.html
So how would I go about this on the galaxy s3 l710.
My alfa card reads on pcap app.
Hi everyone.
I plan on using the Bolse adapter : http://www.mybolse.com/products_more.asp?id=96 that has an Android driver with my Galaxy Note2.
Do I have to go through all these steps with it considering it has an Android driver?
Thanks
infernix said:
I got fed up with crappy wireless reception in a hotel and decided to use my RTL8187 based Alfa USB wireless adapter with my Prime. Here's how it works, pretty rough and open to improvement but it works.
Set up a chroot (ubuntu/debian will work); everything is done within that chroot
Compile and install the drivers for your usb adapter (see the Kernel modules thread for instructions)
apt-get install wicd-curses (or wicd-cli if you prefer), wpasupplicant and dbus plus any of its dependancies
Turn off the broadcom wifi that's controlled by android
insmod your modules (in my case eeprom_93cx6.ko, mac80211.ko, rtl8187)
start dbus and wicd (/etc/init.d/dbus start; /etc/init.d/wicd start)
run wicd-curses (or wicd-cli), refresh the network list and connect to your network
configure dns for android to your dns or to googles (setprop net.dns1 8.8.8.8)
???
Profit
To stop using external usb wifi, reverse the steps; basically:
stop wicd and dbus (/etc/init.d/wicd stop; /etc/init.d/dbus stop)
kill any running dhcp clients (killall dhclient)
rmmod your modules (in my case eeprom_93cx6.ko, mac80211.ko, rtl8187)
To be able to insert mac80211 without it complaining about missing symbols for ewma_init and ewma_add, I had to add lib/average.c to the mac80211 module; it's pretty simple, here's how i did that:
Go to your prime kernel source tree (e.g. /usr/src/linux)
cp lib/average.c net/mac80211/
Edit net/mac80211/Makefile and add average.o to the list of objects for mac80211-y (don't miss the trailing backslash if you add it halfway)
For simplicity sake I've added the modules for an rtl8187 based usb nic to this post. These are built against the 9.4.2.7 kernel source, and work fine for the 9.4.2.11 release (current ICS release as of Feb 07 2012).
Oh and I don't recommend doing this with androids wifi turned on, it kind of breaks it until you reboot your tab. So if you're smart you'll script the above and spit out a nice warning that your broadcom module is still loaded and then exit. I had no problems switching between external USB wifi and built-in wifi as long as I only turned one of them on exclusively.
Enjoy solid wifi on your prime
Click to expand...
Click to collapse
Well, after i read most replies, most don't understand how to get things set up, please describe it a bit more, organize things, like section for requirements, etc.
Explain to Kernel and Kernel Modules and how to build them
For everyone who didn't Understand Step 2, I Will explain and tell you how to do that, Please read it all to Understand:highfive::
What is Kernel?
A Kernel is Simply a Bridge Between Software and Hardware.
So The Drivers are Inside the Kernel itself?
For Short, Yes. In Linux Overall (Android, Ubuntu, etc.), Drivers are Included Inside the Kernel it self, Some say for Performance Improvements.
Your Phone's Android Kernel Include all the Drivers required for your phone to function, And for the Devices that Support USB-OTG there are a Plenty of Drivers Included, However, Drivers like the one's for the RTL8187 Most likely won't be included.
What are Kernel Modules?
Kernel Modules are Files that have *KO Extension That can be loaded Through insmod and Unloaded through rmmod Command-Line Commands, These files is to Extend the Functionality of the Kernel Without Touching/Editing it at all,It Just does some effect Until the Modules are Unloaded/Device Rebooted, Kernel Modules useful Either by Adding a Driver or by adding other things..[/B]
What are the Disadvantages of Kernel Modules?
Well, There's no Difference Expect you need to reload the Kernel Modules after a Reboot or Module Unload, Some Tutorials Show you how can you add a command to load these Modules after each boot up
So A Kernel Module is the Solution for adding a driver without modifying the kernel?
Yes, Kernel Modules is the Solution here, Each USB Device needs it's own Kernel Modules, so you can't Download a Module and Use it, You need to Compile yours.
What is the Requirements to build a Kernel Modules?
1.You need Linux Environment, Use either the Chrooted Linux On you phone, or, better use Ubuntu or any linux Distro on a Computer, Build the Module, and load it on the Chrooted Linux on your phone,
2.You need an Internet Connection in the Linux Environment.
3.You need the Driver Source code for your USB Device. Get them from the Manufacturer if he offer them, if he doesn't, You need to Look in the internet until you find one, if you were unable to find the Source code for you Device but found similar Devices Driver source code, see if the Other Device Driver is Compatible with yours usually a Single Driver work on many Devices, you need to look by your own way
4.You Also need some Programs to install in Order to be able to Compile the Kernel Module, Enter these Commands in a Terminal, Pressing Enter after each Line, and make sure you have the Internet Connection:
HTML:
sudo apt-get install fakeroot
sudo apt-get install build-essential
sudo apt-get install dpkg-dev
sudo apt-get install linux-headers-$(uname -r)
For the most Important Part, make the Kernel Module?
1.Unpack the Kernel source code, if it's Extension is bz2 then use:
HTML:
tar jxvf <package-name>
Where <package-name> is the Compressed File name, and make sure you put it in the Home Folder, if it's Extension is gz or tgz the Unpack it with:
HTML:
tar zxvf <package-name>
2. Second, Find config.mk and Open it with gedit or whatever Text editor you like, at first, there is two lines about WPA Support, make sure they end with y rather than n, Save and close.
3.Third, and last, is to Compile the Kernel Module, Open Terminal and use cd command to get inside the folder that contains the Source code, and Simply Execute:
HTML:
sudo make
And now you own the Kernel module, Now copy the Kernel Module to the root of your Internal Storage, Open up a Terminal and Type:
HTML:
cd /mnt/sdcard
insmod <kernel-module-name>.ko
And make sure Internal Wi-Fi is OFF and now your Kernel Module works, Follow the Guys steps to get it working on Chrooted distro
Troubleshooting:
If you find a similar Device Driver Source Code and after Compiling it doesn't work plug the Device in, Open a Terminal and type:
HTML:
sudo lsusb
and Find your Device in the Output and you should find Numbers for it Looks Like 0x148F,0x2070 or whatever, Write them down.
After Step 2 Follow These Steps:
Find usb_main_dev.c and Under #ifdef Section add the Following Line:
HTML:
{USB_DEVICE(0x148F,0x2070)}, /* Your Device name, this is just a Comment. */
Where You should replace 0x148F,0x2070 with the String you just wrote down.
And then Continue Other Steps and it should work.
Please Click "Thanks" Button if i Helped you
Also, if you had any Problems and fixed them Just tell me so i can add them to Troubleshooting Section.
Hi! Im going on vacation in 2 weeks and I want this to work on my Nexus 5. I run CM12. I think I can manage the kernel part myself (there are a lot of nexus 5 kernels which include the driver of my wifi dongle: TP-Link WN722N). but I don't know how to do the next steps (for example step 4 and 5). Can someone give me a detailed tutorial with command lines? I am familiar with terminal.
My step again:
Nexus 5 running CM12
Wifi dongle: TP-Link WN722N
thanks in advance!
Sorry for the extremely noob question, but will this make the wifi adapter work in the chroot or on the entire device?
I have a Netgear WNDR3700v3 as my main router at my apartment. With it, I connect my Galaxy Nexus as well as my Galaxy Tab 10.1 to the Internet. I've been using CyanogenMod for a few years. So I was really excited when my SGT10.1 got on the CM9 train. When the nightlies started in April, everything was fine. But since May, I've been having horrible trouble with my SGT10.1: I haven't been able to connect to the router. When I use a build from mid-April, everything works. When I use any builds from May I can't connect at all. I CAN connect to my SGN as a hotspot. I just can't connect to my router.
Here is the list of what I've tried:
- Changed router to use WPA (and not WPA2)
- Enabled SSID broadcast on the router
- Switched channels on the router
- Turned the 5GHz radio off (as the device has both a 2.4GHz and a 5GHz radio)
- I've tried Pershoots builds and kernels with no luck.
- I've tried both static and dynamic IP addresses for the SGT10.1
I can still work if I stay on the April builds - but I really do want to keep current on CM9. Any other ideas or thoughts?
if your tab p7500 then try this. search in xda how to use it
real77055 said:
if your tab p7500 then try this. search in xda how to use it
Click to expand...
Click to collapse
I have a P7510. And the issue does not appear to be related to WiFi and country codes. I am able to connect to other WiFi access points (like my hotspot). I just can't connect to the WNDR3700.
is your router on a channel greater than 11?
time_shock said:
is your router on a channel greater than 11?
Click to expand...
Click to collapse
I have run it on Auto as well as on channel 8. I've never used a higher channel.
Questions go in the Q&A section
Step666 said:
Questions go in the Q&A section
Click to expand...
Click to collapse
The distinction between "questions" and issues is certainly murky. This is an issue with recent changes in CM9. It worked in April builds and then didn't work in May builds. Can it be phrased as a question? Well, if you follow "Jeopardy" then anything can be phrased as a question. Are you suggesting that I cross-post this?
select 5GHZ from advanced settings, and you should be able to see it and connect (a current bug that needs to be investigated, if you cant see 5GHZ when on auto). make sure your AP/router is on the latest firmware.
this is what you do:
make sure your AP/router is on latest firmware
flash 0514 from droidbasement
while in recovery after flash, clear out /data/misc/wifi/* folder like so:
adb shell mount /data (after you flash this willl be mounted, so no need to mount it)
adb shell rm -r /data/misc/wifi/*
now reboot.
once in, select advanced in wifi settings, select 5GHZ, select your AP manually, and you should be good to go.
april and may builds are completly different in wifi versions. this was required to get wifi 99% stable for the masses. things will get better once new firmware is released from samsung to be used (currently stock firmware from AOSP is being used).
i myself use an e4200 (dual band) with dd-wrt currently. no issue at all with 5GHZ (except for the aforementioned bug in wifi settings).
pershoot said:
select 5GHZ from advanced settings, and you should be able to see it and connect (a current bug that needs to be investigated, if you cant see 5GHZ when on auto). make sure your AP/router is on the latest firmware.
this is what you do:
make sure your AP/router is on latest firmware
flash 0514 from droidbasement
while in recovery after flash, clear out /data/misc/wifi/* folder like so:
adb shell mount /data (after you flash this willl be mounted, so no need to mount it)
adb shell rm -r /data/misc/wifi/*
now reboot.
once in, select advanced in wifi settings, select 5GHZ, select your AP manually, and you should be good to go.
april and may builds are completly different in wifi versions. this was required to get wifi 99% stable for the masses. things will get better once new firmware is released from samsung to be used (currently stock firmware from AOSP is being used).
i myself use an e4200 (dual band) with dd-wrt currently. no issue at all with 5GHZ (except for the aforementioned bug in wifi settings).
Click to expand...
Click to collapse
my advice is to set this up in stages so you can troubleshoot.
leave the 5GHZ (N only; use auto 20MHZ) open, then try to connect to it. after doing so, then implement security if you like (WPA2), then reauth to it on the tab.
ive found 136 and below channels (this is upper) to work ok, but your mileage may vary. auto should be ok to use (this is what i use currently).
pershoot said:
my advice is to set this up in stages so you can troubleshoot.
leave the 5GHZ (N only; use auto 20MHZ) open, then try to connect to it. after doing so, then implement security if you like (WPA2), then reauth to it on the tab.
ive found 136 and below channels (this is upper) to work ok, but your mileage may vary. auto should be ok to use (this is what i use currently).
Click to expand...
Click to collapse
Thanks for the hints. I've tried the recommended WiFi settings for the router, the recommended build (and kernel) as well as erasing the /data/misc/wifi directory. I even wiped /data altogether. Yet I still can't connect to the WNDR3700v3. I can connect to my SGN CM9 phone (as a hotspots). Obviously its a problem with the new WiFi drivers and the router/build.
The tab sees the network. It even determines whether it is protected or not. But even when open, it doesn't seem to connect - or it can't get an IP address.
BTW, where do I set 20MHz? I can't find this in CM9 WiFi settings or Advanced.
Well, I solved the problem by factory resetting the router. All I can figure is that my previous config exposed a bug in the router or CM9. The config that failed used a different base subnet. When I revert to default 192.168.1.0/24, things began to work.