[How To] Activate Wifi - Barnes & Noble Nook Tablet

After many hours of research and trial and error we finally have a working Wifi setup on CM7!
This is what we learned:
-There are specific wifi drivers that must be compiled alongside the kernel (twilan_drv.ko)
-The .ini file are developed when building the drivers that also must be used
-The stock firmware.bin file can be used
-The wifi drivers must be calibrated to work properly and efficiently. This can be done by referencing the WifiBackupConfiguration file found on the /Rom partition
-This device uses the Ti wl1273 wifi/Bluetooth card but is compiled using the wl1283 drivers (The Kindle Fire drivers worked perfectly! Boo you B&N for the no-show)
Here are some simple steps to get it working on your device:
1. Build a kernel (there are several other threads that talk to this like: http://www.nooktabletdev.org/index.php/Making_a_Boot_Image)
2. Get the Kindle Fire Source: http://kindle-src.s3.amazonaws.com/Kindle_src_6.2.2_user_3205220.tar.gz
3. Build the drivers:
Code:
cd <path to KF source>/Source/mydroid/hardware/ti/wlan/wl1283/platforms/os/linux/
make ARCH=arm CROSS_COMPILE=/opt/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- KERNEL_DIR=<path to NT source>kernel/android-2.6.35 TNETW=1273
cd ../../../..
cd wl1283_softAP/platforms/os/linux/
make ARCH=arm CROSS_COMPILE=/opt/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- KERNEL_DIR=<path to NT source>kernel/android-2.6.35 TNETW=1273
NOTE: You can use whatever Cross Compiler you want. I found the most success using CodeSourcery Lite (2009 or 2010) for Ubuntu 11.10. Another common path is
Code:
~/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
If you are getting build errors it is probably because your kernel path is wrong or you need to try another set of CROSS-COMPILER files.
Note the line 'TNETW=1273' when building. That is the key to building the correct driver version.
4. Copy the drivers and ini files to your /system/etc/wifi folder:
Grab the twlan_drv.ko from the wl1283/platforms/os/linux folder. Also grab the tiwlan.ini file from wl1283/platforms/os/linux folder. Push both of these to your /system/etc/wifi folder.
Next grab the tiap_drv.ko and tiwlan_ap.ini from the wl1283_softAP/platforms/os/linux/ and wl1283_softAP/config folders. Push these to the /system/etc/wifi/softap folder.
5. Ensure your init.omap4430.rc has access to WifiBackupConfiguration
6. Build and install your boot.img using the kernel from step 1
Done! Enjoy the internet again

So, now all that needs to be fixed is SOD? Good news, thank you all for your hard work.

Mephikun said:
So, now all that needs to be fixed is SOD? Good news, thank you all for your hard work.
Click to expand...
Click to collapse
Fixing SoD should be usable enough for first Alpha. Then it is tweaking small things, having everyone find bugs, and fixing them!

Goncezilla said:
Fixing SoD should be usable enough for first Alpha. Then it is tweaking small things, having everyone find bugs, and fixing them!
Click to expand...
Click to collapse
Can't wait to start testing and finally help with the development

If bluetooth is on the same chip as wifi, will this also make bluetioth function?

travisn000 said:
If bluetooth is on the same chip as wifi, will this also make bluetioth function?
Click to expand...
Click to collapse
As of right now bluetooth does not function with these drivers (even though it is turned on in the kernel).
There are however some init.omap4430.rc services that look like they could be enabled to activate blutooth. We are going to try this out soon but are currently working some higher priority functionality issues.
I'll be sure to ammend this thread if we get blutooth working

Related

Toshiba Folio 100 - Kernel / Tweaks - improvements

the FolioMod thread is start to get rather big, and maybe its time for another one with Kernel and Tweaks for our Folio..
I suggest we write tweaks / Kernels and maybe apps here too?
Wiki pages available here and here
Other non-FolioMod , but folio100 threads General questions thread
I requested an admin to include a Folio sub-forum, let's see if they can help us.
I'm starting with a keyboard recomendation for every Tablet with 7-10 inches:
htt p://dl.dropbox.com/u/13094844/com.beansoft.keyboardplus-1.apk
hi,
i am on foliomod 1.2.
Correct the version Folio Widget 0.3.1.
how I run both the CPU and the best optimal parameters Please.
I am also on FolioMod 1.2.
Is there a possibility to include usbnet.ko-driver? I'd like to use a USB-Ethernet interface, but the kernel driver is missing on the Folio.
Where can I get the Kernel sources and the correct kernel configuration file to compile the module?
wineraser said:
Is there a possibility to include usbnet.ko-driver? I'd like to use a USB-Ethernet interface, but the kernel driver is missing on the Folio.
Where can I get the Kernel sources and the correct kernel configuration file to compile the module?
Click to expand...
Click to collapse
look in the WIKI as mentioned in FolioMod post #1 (now also added to this thread in post #1)
Hello from Italy!
I'm using original Toshiba rom, updated (for now
I'm trying to use the FolioWidget 0.3.1 but I cannot install it; if I rename it to .apk , my Folio100 says is not correct
If I leave as .zip, It starts ES File explorer...
How can I install it? thank you.
ps: SOLVED, probably the first time the zip was corrupted
Folio Accelerometer Fix - BETA
This is a first BETA version of the rotation/accelerometer fix for the Folio 100, tested on FolioMod 1.2 only.
Checked with these applications:
- Wave Blazer Lite
- Raging Thunder 2 Lite
- Abduction! 2
Known Issues:
- Compass is not working, i.E any Compass app or for example Google Sky Map does not point you in the correct direction.
Note, this is NOT an update zip, at the moment I have no SDCard to verify that the update works, therefore you must push the files manually onto the device. Or wait until someone provides an update zip for these files.
Installation instructions.
- unzip the attached zip file into any directory you like
- enter the bin directory, where you should find 2 files (framework.jar, libsurfacflingeR_client.so)
- verify that your device is connected by running adb devices from a command line
- Remount the system partion read/write by entering: adb remount
- push the framework.jar to the device: adb push framework.jar /system/framework/
- push the sufraceflinger library to the device: adb push libsurfaceflinger_client.so /system/lib/
- reboot the device
Make sure you make a backup from the original files, I wont be able to fix any issues until next week, as I am away from my PC, still as my Folio is with me I'll check the boards to see if any issues have come up.
For developers/dexter:
the zip also includes the files I've modified for the fix, these are based on the NVIDIA tree. I hope that all modified locations shoukld be marked with // XXX:
Installation instructions.
- unzip the attached zip file into any directory you like
- enter the bin directory, where you should find 2 files (framework.jar, libsurfacflingeR_client.so)
- verify that your device is connected by running adb devices from a command line
- Remount the system partion read/write by entering: adb remount
- push the framework.jar to the device: adb push framework.jar /system/framework/
- push the sufraceflinger library to the device: adb push libsurfaceflinger_client.so /system/lib/
- reboot the device
Any easier way to do this ???
this is done on the Toshiba Folio itself or from a computer?
How do i "verify that your device is connected by running adb devices from a command line" ?
Is there any software required to do this ?
Sorry for asking so many questions, really a noob here and really tempted to get my folio fixed. I am running on dexter's foliomod 1.2, so far it works great, but the accelerometer doesnt seem to work correctly. I've tried some games like ibeer, the orientation is totally out. Hope that this can be fixed.
Eugene
weeds2000 said:
Note, this is NOT an update zip, at the moment I have no SDCard to verify that the update works, therefore you must push the files manually onto the device. Or wait until someone provides an update zip for these files.
Installation instructions.
- unzip the attached zip file into any directory you like
- enter the bin directory, where you should find 2 files (framework.jar, libsurfacflingeR_client.so)
- verify that your device is connected by running adb devices from a command line
- Remount the system partion read/write by entering: adb remount
- push the framework.jar to the device: adb push framework.jar /system/framework/
- push the sufraceflinger library to the device: adb push libsurfaceflinger_client.so /system/lib/
- reboot the device
Click to expand...
Click to collapse
Here is the update.zip edition and rollback edition.
remember to rename files to update.zip and install via recovery.
Dexter_nlb said:
Here is the update.zip edition and rollback edition.
remember to rename files to update.zip and install via recovery.
Click to expand...
Click to collapse
it works great with asphalt 5!!!
still some issue, but not related, with white texture in games like assassins creed...
Dexter_nlb said:
Here is the update.zip edition and rollback edition.
remember to rename files to update.zip and install via recovery.
Click to expand...
Click to collapse
I tought compass needs GPS? (and we don't have a GPS chip?)
@killerbie
no, e compass is electroic magnetic sensor.. but also a accelerator chip here...
the hardware GPS is for sat position reception.
Do This update work on stock rom, too?
girello71 said:
Do This update work on stock rom, too?
Click to expand...
Click to collapse
i dont think installer works on stock recovery..
Hello
Tested in the FolioTNTMod and didn't start after the ecompass.zip, ecompass_rollback didn't solve, so had to resinstall, just advertising, don't know if generic or just my setup.
viaper said:
Hello
Tested in the FolioTNTMod and didn't start after the ecompass.zip, ecompass_rollback didn't solve, so had to resinstall, just advertising, don't know if generic or just my setup.
Click to expand...
Click to collapse
confirmed.
does not work with clean TNT. just flashes the bootlogo over and over.
i'll wait for fmod1.3 though
edit: i didn't have the patience
works great on 1.2
kepler1982 said:
edit: i didn't have the patience
works great on 1.2
Click to expand...
Click to collapse
been busy with other tasks, so the orientation is working with some new games now or simply handled like we got a portrait tablet?
It should handle things like a portrait device. The changes in surfaceflinger library do just that. Within the Sensormanager class sensor values are rotated back 90 degrees. The fix for compass could be as simple as not rotating the sensor values if the sensor type matches the compass sensor.
The fix does not work with TNT mod because the framework jars are different (a plain Nvidia framework.jar does not work either) However it should be possible to add these changes to the tnt framework.
weeds2000 said:
It should handle things like a portrait device. The changes in surfaceflinger library do just that. Within the Sensormanager class sensor values are rotated back 90 degrees. The fix for compass could be as simple as not rotating the sensor values if the sensor type matches the compass sensor.
Click to expand...
Click to collapse
i tested it with the 3D Tilt game, it works (not perfect but close).
and im including your changes into the v1.3 FolioMod im preparing now..
a quick test of Asphalt also shows its working fine...
its worth including for sure..
as long as we got full 360 rotation, it works great..
ps: Tnt does not have full 360 rotation, nvidia edition got it with my my patched framework..
3G USB modem support possible ?
The ZT180 has support for 3G USB modem (Huawei make).
Assuming there is no hardware support in that machine I would speculate that
what is needed is,
a) A driver for the kernel
b) Changes to the framwork (?)
c) An app to handle it (AT commands probably).
Anyone have input on this ?

[GUIDE] Using external USB wifi

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?

[Q] Compile & load kernel module for DVB-T USB dongle

I'm attempting to compile and load kernel modules to make my Nova-T Stick USB DVB-T dongle work with my TF201 Asus TFP. Any one have a step-by-step guide for doing this?
I first attempted to go down the cross-compile on ubuntu host machine, then I went to chrooted ubuntu on the target, now back to ubuntu host. I have managed to build a number of .ko's, and insmod'ed some of them on the TFP. When doing a lsmod, I get:
dib7000m 12318 0 - Live 0xbf1cc000
dib7000p 23027 0 - Live 0xbf1b9000
dvb_ttusb_budget 12571 0 - Live 0xbf11a000
dibx000_common 4990 2 dib7000m,dib7000p, Live 0xbf113000
dib0070 6585 0 - Live 0xbf0fc000
dvb_pll 7922 0 - Live 0xbf0cc000
dvb_core 77241 2 dib7000p,dvb_ttusb_budget, Live 0xbf0b7000
bcm4329 207334 0 - Live 0xbf082000
Click to expand...
Click to collapse
But when I plug in USB dongle, I don't get any dvb-usb messages in dmesg. Only the standard usb ones.
To compile them, I took the kernel from Asus website, built using prebuilt ARM cross-compiler from AOSP (make menuconfig, and then make modules).
Any ideas anyone?
More info
Also,
cat /proc/devices
Click to expand...
Click to collapse
gives me amoung other things: 212 DVB, which looks good to me. Just no dvb-usb messages in dmesg still.
Anyone have the ko's for all DVB tuners, and the correct order to insmod them? This will be useful for many people surely...
And yet more info
After inserting the USB Tuner into an Ubuntu laptop, I can see using lsmod that some modules used are dvb_usb_dib0700, and dvb_usb.
However when I build the Asus Kernel after changing the .config, I cannot for the life of me get these 2 missing ko's built. Any one know of the options required in make menuconfig to get this working?
solution
OK, I didn't realise that Remote Control stuff needs to be enabled (to get rc-core) in make menuconfig before stuff relating the USB DVB shows up. Now I've got my kernel modules.
Modprobe in chroot ubuntu doesn't seem to work, so I insmod a whole load of them in a certain order and finally the USB stick is recoginised as DVB-T.
Now for some reason I get ActivityManager: Segmentation Fault on my Prime when installing APKs from my host machine. Life is never easy...
More detail?
Hi
Thanks for posting this as I am interested in doing the same thing. Can you outline your process in a bit more detail so I could followsuit. Or maybe share the modules you created?
Thanks
robb001 said:
Hi
Thanks for posting this as I am interested in doing the same thing. Can you outline your process in a bit more detail so I could followsuit. Or maybe share the modules you created?
Thanks
Click to expand...
Click to collapse
I think I managed to build the kernel modules and insmod them in the end. If you plug tuner into a host machine and do an lsmod before and after, you will find the dependency order for all the kernel modules you need. You need to generate all of these .ko files and insmod all of them in exactly the correct order. Search through make menuconfig to find all the required modules components including any related remote control ones, general DVB and USB ones too. It is possible to do it this way using insmod.... however....
I also did it a different way in the end to get some other benefits. Build Cyanogenmod 10 from source, and modify the kernel (as before), and just boot this custom ROM with all the required ko's already in place - seems to be an easier path with more help available on forums etc...
After this you need to make sure that after you plug in the DVB adapter, you change the permissions of the dvb nodes to 777 (or similar) before you can use them from an app.
Good luck! It is all possible!
Thanks for your very prompt reply. I am fairly familiar with linux and command line but not heavily in to compiling modules and kernels.
barkside said:
You need to generate all of these .ko files and insmod all of them in exactly the correct order.
Click to expand...
Click to collapse
To do this don't I need to have the kernel sources, headers and some tools like "make" available and carry all of this out on the actual target hardware with the appropriate kernel version? I.e. not on a host machine?
barkside said:
I also did it a different way in the end to get some other benefits. Build Cyanogenmod 10 from source, and modify the kernel (as before), and just boot this custom ROM with all the required ko's already in place - seems to be an easier path with more help available on forums etc...
Click to expand...
Click to collapse
This sounds like a good way to go but first have to do the above generating of module files?
I think perhaps I need to do some more research on this subject.
robb001 said:
I.e. not on a host machine?
Click to expand...
Click to collapse
No you need to do it all on a host linux machine. Do do it with insmoding, you need to download the kernel from Asus for your corresponding target kernel version. This includes everything you need. Then you need to just enable the building of the new DVB stuff by modifying the kernel config (use make menuconfig), then build the kernel - this gives you a lot of stuff including the ko files.
robb001 said:
This sounds like a good way to go but first have to do the above generating of module files?
I think perhaps I need to do some more research on this subject.
Click to expand...
Click to collapse
More research is a good idea. It is not simple. But cyanogenmod has lots of help available - read its wiki on building from source etc. So to clarify - you either 1) build kernel modules when building the kernel and insmod them onto the target, or 2) build the entire CM10 source and flash this new custom ROM (which will be complete with the DVB stuff once you enable them in CM10 kernel config). Go with 2) and see how you get on.

TP-LINK WN722N (ath9k driver) install on Ubuntu touch 15.04 (Nexus 10- Manta)

I've been through all the relevant threads on AskUbuntu and they are either outdated, conflicting and/or dont work.
My Nexus10 sees the atheros AR9271 device on Bus 001 USB but does not create an additional WLAN for it.(wlan0 is the normal integrated wifi) I assume I need the ath9k or ath9k_htc driver? I installed backports 4.4.2-1 and unzipped it. If I try to do a 'make' or 'make clean' I get:'your kernel headers are incomplete/not installed'. I've already got the latest version of build-essential. If I try to install 'firmware-atheros', it cannot find the package. I've been through several other things to no avail.
I've read the driver is installed with 15.x+ anyway, true? and if so how to install it? If someone could do a step-by-step wifi driver install for a U-touch or at least Ubuntu 15.x I'd be very very grateful.
I do not want to bridge the 722n, I want to use it instead of the integrated card. Not even there yet, but just in case it matters.
Thanks!
roninisc said:
I've been through all the relevant threads on AskUbuntu and they are either outdated, conflicting and/or dont work.
My Nexus10 sees the atheros AR9271 device on Bus 001 USB but does not create an additional WLAN for it.(wlan0 is the normal integrated wifi) I assume I need the ath9k or ath9k_htc driver? I installed backports 4.4.2-1 and unzipped it. If I try to do a 'make' or 'make clean' I get:'your kernel headers are incomplete/not installed'. I've already got the latest version of build-essential. If I try to install 'firmware-atheros', it cannot find the package. I've been through several other things to no avail.
I've read the driver is installed with 15.x+ anyway, true? and if so how to install it? If someone could do a step-by-step wifi driver install for a U-touch or at least Ubuntu 15.x I'd be very very grateful.
I do not want to bridge the 722n, I want to use it instead of the integrated card. Not even there yet, but just in case it matters.
Thanks!
Click to expand...
Click to collapse
anyone anyone, Beuller...
Hey, saw this was unanswered and figured I could help. First off, you will not be able to compile or install headers in the Ubuntu Touch system, as /lib/modules/<kernel version> is a bind-mount into the read-only LXC system image, one way to work around this issue on device is to mount the LXC container's system image read-write somewhere, move out the lib/modules directory to someplace else, umount, reboot and then link your moved lib/modules back into /lib/modules. You will need to do this compilation outside of your Nexus 10 in a cross-compilation environment or in an armhf chroot (imho, a chroot running the ARM build of Ubuntu works very well for this).
Once you have that, you can install the kernel package for your device (which I believe are labeled linux-headers-manta and linux-image-manta respectively) and build the driver you seek. However the kernel already comes with backports 4.4.2 in it's tree, so you may be able to apt-get source linux-image-manta and build the driver and/or the kernel itself if you wish. (I believe building the kernel builds the firmware needed for the drivers as well, but I have no way of knowing as I haven't actually rebuilt any drivers with firmware yet in my foray into linux-image-flo's source.)
One piece of advice: Make sure to join together the config.*.ubuntu files under the debian.flo and debian.master folders to get the working .config for your device. The defconfig from arch/arm/configs doesn't have all the needed options for uTouch and won't boot it.
Your 'thanks meter' improved, and big thanks for answering, but this is beyond my level. Was hoping I could run an external wifi stick on a tablet with some flavor of linux, but looks like a no go for mortal users.
roninisc said:
Your 'thanks meter' improved, and big thanks for answering, but this is beyond my level. Was hoping I could run an external wifi stick on a tablet with some flavor of linux, but looks like a no go for mortal users.
Click to expand...
Click to collapse
Sadly at this time, it definitely seems to be. The normal linux way of building drivers doesn't work on here because the modules directory (/lib/modules/3.4.0-5-flo) is read-only, also due to this kernel headers cannot be installed, this can be worked around, but it is definitely not something that the casual user can do easily. I hope this will change so I could start compiling modules and NOT need to rebuild the entire kernel for it.
Glad I could be of help and I love answering questions, I am currently using Ubuntu Touch as my main OS on my Nexus 7 as I'm trying to make it into my own portable workstation. So I'm constantly digging into the system and learning what I can, and I love to share.

WN722N v2/v3 driver for Nethunter

Storytime ;D
So many people asking for WN722N v2/v3 in the web including myself. I actually bought one extra for nethunter. So because the driver is not included from stock, i compiled it myself.
Here is the driver src link: https://github.com/aircrack-ng/rtl8188eus/
(Compiled driver uploaded below)
Requirements
4.14.83-Re4son-OOS Kernel (is included in 2020.1 Nethunter package) (https://images.offensive-security.com/nethunter/nethunter-oneplus7-oos-pie-kalifs-full-2020.1.zip)
onto OOS 9.5.8 (https://forum.xda-developers.com/oneplus-7/how-to/oneplus-7-repo-oxygen-os-builds-t3937152)
-> I recommend using Pie, since i could not get Q working with Nethunter.
Restore, Unbrick, Downgrade, Upgrade
MSM tool (only OOS): https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
Repo of OOS Builds: https://forum.xda-developers.com/oneplus-7/how-to/oneplus-7-repo-oxygen-os-builds-t3937152
Downgrade package: https://www.getdroidtips.com/how-to...pro/#Download_OnePlus_77_Pro_rollback_package
Warning
Use it at your own risk. This was my first time compiling anything like this... I am not responsible for any kind of damage. Only tested on GM1903!
Installation
Actually i don't know... normally it would get loaded into /system/lib/modules but this folder does not exist for OP7?
I ended up just putting into /storage/emulated/0/ and then loading it with
insmod /storage/emulated/0/8188eu.ko
(/unload) rmmod /storage/emulated/0/8188eu.ko
Activating monitor mode:
airmon check kill
ip link set wlan1 down
iw dev wlan1 set type monitor
If error "No such device -19" simply unload and reload the driver.
Some screenshots (I have a v3)
This is awesome and your work is much appreciated! the guide was clear but I didn't really get the installation part. Could you please clear it up for me, I'm using the global oneplus 7 pro 12 gb ram. do I just place the file into /system/lib/modules or do I have to run an additional command?
danielqf45 said:
This is awesome and your work is much appreciated! the guide was clear but I didn't really get the installation part. Could you please clear it up for me, I'm using the global oneplus 7 pro 12 gb ram. do I just place the file into /system/lib/modules or do I have to run an additional command?
Click to expand...
Click to collapse
In my research i found out, that most are putting it into /system/lib/modules. However this folder does not exist on OP7. I've ended up putting it into /storage/emulated/0/ and then loading the driver with the command already descriped in the tutorial.
If I do that, and have the adapter connected my phone reboots.
What does it do?

Categories

Resources