In general WALT Android app has no special requirements but since WALT usually takes up the only available USB connector on the phone, the typical development using ADB via USB becomes difficult. Below are some options to overcome this problem.
ADB can work over TCP connections. The official documentation assumes that the TCP connection is established over WiFi, but a wired Ethernet connection can be used in the same way and is reported to work much better with ADB. Android will recognize and use most USB-Ethernet adapters out of the box.
adb tcpip 5555
(you can replace 5555 with any port)Note, this setup is sensitive to the order in which you connect the different components and adapters, experiments with it.
A ChromeOS device with Android (e.g. Asus Flip) is another convenient option.
Since Android on ChromeOS has no access to USB, it requires a TCP bridge script implemented in walt.py. Detailed instructions in Chromeos.md.
In order to set up your for Android development, use either the official guide for Android development on ChromeOS. Or the following short list:
ifconfig
to get the ip address of eth0 (or wlan0 if using wireless)ssh root@ip_addr
to verify that Chromebook is accessibleadb connect ip_addr:22
. From this point on Android studio and adb on your workstation should treat the Chromebook just like a regular Android deviceiptables -A INPUT -p tcp --dport 50007 -j ACCEPT
python walt.py -t bridge