DeviceMonitor does not work #227
Description
The DeviceMonitor seemed like a cool idea. I thought you could start it up and then have a nice automated managing of devices being added and removed while you do other things.
From what I found in the meantime, that's simply not possible. You can have the DeviceMonitor OR you can have all the rest of the adb functionality available through SharpADBClient, but not both at the same time. Issue being: you have basically 1 port of 127.0.0.1 to work with, and 1 socket to that which gives you reliable feedback. If you use multiple sockets to the same port, the DeviceMonitor will not get anything anymore. So to me...it is basically useless. Unless I'm missing something big here...
I read some other issues here. Some are related to the fact that when a new device connects, it will be in offline state and then after a bunch of milliseconds switch to online. When offline, it will not offer any data other than serial and state. That's a manageable thing. But you can make the devicemonitor work for 1 go to to the adbclient. It will work. But you can't execute other commands without damaging that listening channel.
Any thoughts or experiences?