Question Windows Subsystem for Android USB device "mounting"? - Windows 11

Hi,
I was looking to use the DJI Fly on Windows through WSA, I was able to install it just fine and it loads, but can't find a way to make it see the controller, can't find a mount option like yhe one find for example on VirtualBox, tried usbipd-win but it doesn't seem to recognize the Subsystem.
Has anyone been able to get any device "mounted"?
Thanks
Oscar

---

No. I don't have a clue. But I am interested.
I wouldn't think that you mount anything.
It's probably like game controls and a UVC interface.
Have you looked under Device Manager to make sure that there are no exclamation marks and that all drivers loaded?
Can you find it in UsbView and paste the right hand pane? https://www.ftdichip.com/Support/Utilities.htm#MicrosoftUSBView

---

Renate said:
No. I don't have a clue. But I am interested.
I wouldn't think that you mount anything.
It's probably like game controls and a UVC interface.
Have you looked under Device Manager to make sure that there are no exclamation marks and that all drivers loaded?
Can you find it in UsbView and paste the right hand pane? https://www.ftdichip.com/Support/Utilities.htm#MicrosoftUSBView
Click to expand...
Click to collapse
The controller is recognized as it should, I'm pretty sure, the device manager shows 3 types under the same device, with one being a com port which I suspect the DJI Fly app uses to communicate the controls, but I expect there to be some kind of menu or command that needs to be run to "attach" the device to the Android Subsystem.

---

Not knowing what the USB interfaces are I couldn't say anything intelligent.
That's why I asked you to tell me what they are in post #2.

---

This is what USB View gives when the controller is connected from the bottom port
Code:
Device Descriptor:
bcdUSB: 0x0200
bDeviceClass: 0xEF
bDeviceSubClass: 0x02
bDeviceProtocol: 0x01
bMaxPacketSize0: 0x40 (64)
idVendor: 0x2CA3
idProduct: 0x1020
bcdDevice: 0x0404
iManufacturer: 0x01
0x0409: "DJI"
iProduct: 0x02
0x0409: "C5"
iSerialNumber: 0x03
0x0409: "3QDCH950010H2U"
bNumConfigurations: 0x01
ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed: High
Device Address: 0x04
Open Pipes: 10
Endpoint Descriptor:
bEndpointAddress: 0x81 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x01 OUT
Transfer Type: Interrupt
wMaxPacketSize: 0x0008 (8)
bInterval: 0x03
Endpoint Descriptor:
bEndpointAddress: 0x82 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x02 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x84 IN
Transfer Type: Interrupt
wMaxPacketSize: 0x0010 (16)
bInterval: 0x10
Endpoint Descriptor:
bEndpointAddress: 0x86 IN
Transfer Type: Interrupt
wMaxPacketSize: 0x0010 (16)
bInterval: 0x10
Endpoint Descriptor:
bEndpointAddress: 0x83 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x03 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x85 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x04 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Configuration Descriptor:
wTotalLength: 0x00BB
bNumInterfaces: 0x06
bConfigurationValue: 0x01
iConfiguration: 0x04
0x0409: "Configuration"
bmAttributes: 0xC0 (Bus Powered Self Powered )
MaxPower: 0x00 (0 Ma)
Interface Descriptor:
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0xFF
bInterfaceSubClass: 0x43
bInterfaceProtocol: 0x01
iInterface: 0x05
0x0409: "MA Channel"
Endpoint Descriptor:
bEndpointAddress: 0x81 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x01 OUT
Transfer Type: Interrupt
wMaxPacketSize: 0x0008 (8)
bInterval: 0x03
Interface Descriptor:
bInterfaceNumber: 0x01
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0xFF
bInterfaceSubClass: 0x43
bInterfaceProtocol: 0x01
iInterface: 0x06
0x0409: "HS-Data Channel"
Endpoint Descriptor:
bEndpointAddress: 0x82 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x02 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Unknown Descriptor:
bDescriptorType: 0x0B
bLength: 0x08
08 0B 02 02 02 02 01 07
Interface Descriptor:
bInterfaceNumber: 0x02
bAlternateSetting: 0x00
bNumEndpoints: 0x01
bInterfaceClass: 0x02
bInterfaceSubClass: 0x02
bInterfaceProtocol: 0x01
iInterface: 0x08
0x0409: "V1 ACM Ctrl"
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x05
05 24 00 10 01
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x05
05 24 01 00 03
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x04
04 24 02 02
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x05
05 24 06 02 03
Endpoint Descriptor:
bEndpointAddress: 0x84 IN
Transfer Type: Interrupt
wMaxPacketSize: 0x0010 (16)
bInterval: 0x10
Interface Descriptor:
bInterfaceNumber: 0x03
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0x0A
bInterfaceSubClass: 0x00
bInterfaceProtocol: 0x00
iInterface: 0x09
0x0409: "V1 ACM Data"
Endpoint Descriptor:
bEndpointAddress: 0x83 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x03 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Unknown Descriptor:
bDescriptorType: 0x0B
bLength: 0x08
08 0B 04 02 02 02 01 0A
Interface Descriptor:
bInterfaceNumber: 0x04
bAlternateSetting: 0x00
bNumEndpoints: 0x01
bInterfaceClass: 0x02
bInterfaceSubClass: 0x02
bInterfaceProtocol: 0x01
iInterface: 0x0B
0x0409: "Log ACM Ctrl"
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x05
05 24 00 10 01
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x05
05 24 01 00 05
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x04
04 24 02 02
Unknown Descriptor:
bDescriptorType: 0x24
bLength: 0x05
05 24 06 04 05
Endpoint Descriptor:
bEndpointAddress: 0x86 IN
Transfer Type: Interrupt
wMaxPacketSize: 0x0010 (16)
bInterval: 0x10
Interface Descriptor:
bInterfaceNumber: 0x05
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0x0A
bInterfaceSubClass: 0x00
bInterfaceProtocol: 0x00
iInterface: 0x0C
0x0409: "Log ACM Data"
Endpoint Descriptor:
bEndpointAddress: 0x85 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x04 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00

---

So, in short, you should have 4 "devices", that is 4 things with drivers.
There are two things that should appear in Device Manager as DJI things.
There are two things that should appear as generic Com Ports.
You can check the drivers for all four.
The last two should have usb2ser.sys
I would guess that the first two would just use WinUsb.
They should have under Details > Inf name something like oem123.inf
You can go to C:\Windows\INF\oem123.inf and see stuff there.
In any case, you should be able to find 4 happy devices in the Device Manager.
There are no Mass Storage devices here, so "mount" is used in some other context.
Code:
Device, VID/PID 2ca3/1020
The device class itself is ef:02:01, Miscellaneous class, Interface Association Descriptor
Unfortunately, you should only use this class:subclass:protocol in interfaces, not devices.
Interface #0
The interface is ff:43:01, proprietary, "MA Channel"
Bulk in/out is 512/8 bytes. Kind of unusual.
Interface #1
The interface is ff:43:01, proprietary, "HS-Data Channel"
Bulk in/out is 512/512
Generic serial port
{
Interface #2
The interface is 02:02:01, CDC control, "V1 ACM Ctrl"
Interrupt in 16
4 CDC descriptors: Header Functional Descriptor, Call Management Functional Descriptor, Abstract Control Management Functional Descriptor, Union Functional Descriptor
Interface #3
The interface is 0a:00:00, CDC data, "V1 ACM Data"
Bulk in/out is 512/512
}
Generic serial port
{
Interface #4
The interface is 02:02:01, CDC control, "Log ACM Ctrl"
Interrupt in 16
4 CDC descriptors: Header Functional Descriptor, Call Management Functional Descriptor, Abstract Control Management Functional Descriptor, Union Functional Descriptor
Interface #5
The interface is 0a:00:00, CDC data, "Log ACM Data"
Bulk in/out is 512/512
}

---

Yes I meant "mount" as in tell WSA to "connect" the devices to the Android system. In Device Manager the COM ports have drivers but the "HS-Data Channel" and "MA Channel" don't have drivers, as it was never meant to be used with Windows.

---

But you can see the two "Channels" in Device Manager?
No problem, just give them Zadig (WinUSB) drivers.
Zadig - USB driver installation made easy
You can't share anything from Windows to the Android subsystem unless it's a device with a driver (I think).