[Galaxy Tab 3 10.1 Android Development] r2d23cpo:
[MENTION=5707708]Jacker31[/MENTION]

Like I say I am going to try to answer in a single thread. So we do not start looking arround.

@r2d23cpo @Daniel-TAz00 I finally got my kernel working thanks for all of your support. Even though i got some error *i cant remember* when i tried to put it into monitor mode. But i guess i will work around that tomorrow. But one thing weird that it cannot detect my TP-Link adapter that base off Atheros AR9002U even though i enabled Atheros driver.

Happy you compile your working Android kernel.

I think you said your device was a "TL-w772n" There is not much info on it. In fact if you go to TP_Link site you will find they do not show that product.

h__p://www.tp-link.com/en/search/?keywords=TL-w772n

Are you sure it is not TL-WN722N

[IMG="WN722N"]http://www.tp-link.com/resources/images/products/default/TL-WN722N.jpg[/IMG]

802.11g/n	WN722N	man: 0cf3 dev: 9271	USB	Atheros	ath9k_htc	green	in kernel

In any case can you install in your KALI desktop and do "lsusb" here is that data that for example shows my TAB3

Bus 003 Device 005: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Ga

Clearly you will take the info of your Wifi adapter. Then look at the vendor:[product] info display. And do ( I gain with my Tablet 04e8:6860).

lsusb -v -d [COLOR="Blue"]04e8:6860[/COLOR]

Bus 003 Device 005: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II], GT-I9300 Phone [Galaxy S III], GT-P7500 [Galaxy Tab 10.1]
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x04e8 Samsung Electronics Co., Ltd
idProduct 0x6860 GT-I9100 Phone [Galaxy S II], GT-I9300 Phone [Galaxy S III], GT-P7500 [Galaxy Tab 10.1]
bcdDevice 4.00
iManufacturer 2 samsung
iProduct 3 GT-P5210
iSerial 4 12345789123
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 133
bNumInterfaces 4
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 96mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 6 Imaging
bInterfaceSubClass 1 Still Image Capture
bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470)
iInterface 5 MTP
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x001c 1x 28 bytes
bInterval 6
Interface Association:
bLength 8
bDescriptorType 11
bFirstInterface 1
bInterfaceCount 2
bFunctionClass 2 Communications
bFunctionSubClass 2 Abstract (modem)
bFunctionProtocol 1 AT-commands (v.25ter)
iFunction 8 CDC Serial
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 2 Abstract (modem)
bInterfaceProtocol 1 AT-commands (v.25ter)
iInterface 6 CDC Abstract Control Model (ACM)
CDC Header:
bcdCDC 1.10
CDC Call Management:
bmCapabilities 0x00
bDataInterface 2
CDC ACM:
bmCapabilities 0x02
line coding and serial state
CDC Union:
bMasterInterface 1
bSlaveInterface 2
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x000a 1x 10 bytes
bInterval 9
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 7 CDC ACM Data
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 66
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)

And try to realy look what chipset shows.

Also do

dmesg | tail -20

before and after you plug and unplug the adapter. So that we can look at th info printed. I try to figure out what driver is needed.

And finaly you could do "lsmod " that gives you the list of installed modules in your desktop.

Now I am pretty sure you will come back and say it is a TP-LINK TL-WN722N. Just like this site confused it too. h__p://www.wgdd.de/2013/06/getting-tp-link-tl-wn772nc-usb-wlan.html

Finnaly if this is the case you can compile the deriver as a kernel module in your desktop with the process on my previous post. Then go into your device and do a "insmod ath9k_htc.ko" test that it works. Then you can add the "insmod ath9k_htc.ko" into your new Android kernel.

I know long explanation. You will figure it out.