ADB functionality.

[ReVanTis]

You can actually operate adb on WSL.
Well, on some level.

By default, WSL will install adb of version 1.10.31.
If you pick the very same version on Windows and start adb server (adb start-server) on Windows, you can actually see and access android devices on WSL.

I assume adb server's inter-process communication is based on network model (on port 5037 as you often see).
So even the server is running on windows, it does not break the client running on WSL as long as they recognize each other with same version number.

Have fun hacking WSL :D

[emmatyping]

So for example, if you adb devices it lists connected devices from bash? I would be very surprised if this is the case.

[ReVanTis]

Hi @ethanhs,
Please kindly have a look :)

[emmatyping]

Wow, great! I am glad you found this. :) I will add this to the list and add something in the notes. Thank you!

[emmatyping]

Fixed in 810914c

[ThaJay]

Awesome, this would enable me to develop React-Native on device. Will check it out

[IPWright83]

I don't believe this works on WSL2? I've got the same ADB version running on both windows and Ubuntu, ensuring I start the windows adb server first (via CMD) and the device list is always empty in the WSL.

[ThaJay]

For me it's very simple: Run the production build via WSL and use ADB through Git Bash on CMD (and everything else works there as well).

I only have to remove the build folder and switch my ./android/local.properties to use the other location for the Android sdk.

# Windows (for running the dev server etc.)
# sdk.dir=/C\:\\Users\\name\\AppData\\Local\\Android\\Sdk
# WSL (for making production builds)
sdk.dir=/usr/lib/android-sdk/