Sometimes `client.listDevices()` returns an error with `null`, like ADB failed to start

[niftylettuce]

Any insight as to why this randomly happens? In order to get listDevices and trackDevices to work again I have to kill my process, then run adb devices manually on command line for the ADB server to start. Why isn't it starting on its own?

[sorccu]

We would have to implement some kind of an overly complex process manager to keep the adb process alive reliably. On our machines we use systemd to watch adb.

On Thursday, 7 January 2016, niftylettuce [email protected] wrote:

Any insight as to why this randomly happens? In order to get listDevices and trackDevices to work again I have to kill my process, then run adb devices manually on command line for the ADB server to start. Why isn't it starting on its own?

— Reply to this email directly or view it on GitHub https://github.com/openstf/adbkit/issues/39.

[rkavalap]

@sorccu For some reason, interestingly this happens every ~6 hrs for me. I try to do listDevices every 5 mins.