Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getDeviceName change #4927

Closed
mudebug77 opened this issue May 15, 2024 · 2 comments
Closed

getDeviceName change #4927

mudebug77 opened this issue May 15, 2024 · 2 comments

Comments

@mudebug77
Copy link

Is your feature request related to a problem? Please describe.
Currently, it's challenging to identify which device's scrcpy-server is connected when multiple devices are connected simultaneously. This is particularly problematic when managing multiple devices remotely.

Describe the solution you'd like
I would like to propose adding a new parameter to scrcpy-server that allows users to customize the sendDeviceMeta identifier. This parameter would enable users to distinguish between different connected devices by providing a unique identifier or label.

Describe alternatives you've considered
One alternative could be modifying the source code to manually pass device identifiers. However, having a built-in parameter would streamline this process and make it more user-friendly.

Additional context
Adding this feature would enhance the usability of scrcpy-server in scenarios where multiple devices are connected simultaneously, providing users with more control and flexibility.

@rom1v
Copy link
Collaborator

rom1v commented May 15, 2024

@mudebug77
Copy link
Author

I don't want to modify the title of scrcpy; I want to build the scrcpy program myself to manage each device centrally. When scrcpy-server sends sendDeviceMeta, it's not unique. If I have 10 devices, I can only start scrcpy-server for one device at a time using adb, rather than starting scrcpy-server for all devices simultaneously because I can't get a unique identifier for each device.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants