Buildozer compatability with usbipd inside WSL2 issue

[jlapp12]

Hello,

I am working on trying to deploy an Android app project using Buildozer. In the documentation of (https://buildozer.readthedocs.io/en/latest/index.html) I learned that WSL is how to use Buildozer for Windows. I also learned that WSL2 does not support native USB support, and so I attempted to implement a solution using usbipd-win. So when I deploy the .\adb.exe devices command, the device will be picked up, but currently, when I run buildozer -v android deploy run, my application is waiting forever. This is because there is no connection made inside WSL, as there is no USB connection. WSL does not support it out the gate. (https://buildozer.readthedocs.io/en/latest/quickstart.html#run-my-application)

I tried utilizing usbipd-win, but realized that there is an issue. When I use the .\adb.exe devices command, (https://buildozer.readthedocs.io/en/latest/quickstart.html#run-my-application), this means that my phone will be tied up in Windows. Therefore, when I try to get the usbipd framework to work, the command usbipd attach --wsl --busid <busid> (https://learn.microsoft.com/en-us/windows/wsl/connect-usb) will be denied as the phone is stuck in Windows land.

I am trying to think of any way to avoid this. Currently, I am trying to test the app via buildozer, but really, I am unsure how to send the data over USB, since WSL does not support that. I tried usbipd, but unless there is something I am missing, when I try to run the deploy, I need to have the ADB daemon working ( .\adb.exe devices), and I also need to have the usbipd connected so that the data can be transferred as there is no native compatability for WSL USB data transfer, but I cannot have my phone in superposition.

If you think there is any solution to my problem, or I am gravely missing something, please let me know.

I thank you for reading this.

[jlapp12]

... disregard.