Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

ADBSocket question...and then maybe more #114

rickx started this conversation in Ideas
Discussion options

Hi guys,

thanks for this. I've been using this library's predecessor and this new development looks nice. Before proposing something, I have this question: to use monitoring (DeviceMonitor), one single socket must be used all the time. Is that correct?
Because, if - like I guess - it is, then the whole approach of this library make things very difficult if you want to use it to interact with multiple devices over a single work session (i.e. within the app's lifetime). So, before going further, can you answer this? Maybe I've missed something.

You must be logged in to vote

Replies: 1 comment

Comment options

DeviceMonitor is monitor the device list of connected devices, and it is provided by adb server. The socket disconnect only when you disconnected it or adb is exited. So you just need one monitor per process to monitoring the device list. If you have multiple threads, you can create a static monitor and use reference counter to manage it.

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Ideas
Labels
question Further information is requested
2 participants

AltStyle によって変換されたページ (->オリジナル) /