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

Non-USB Debugging Mode (Mobile) #5020

Open
bananaNuggets75 opened this issue Jun 24, 2024 · 1 comment
Open

Non-USB Debugging Mode (Mobile) #5020

bananaNuggets75 opened this issue Jun 24, 2024 · 1 comment

Comments

@bananaNuggets75
Copy link

Description

Implement a mode in scrcpy that allows users to connect and control their Android devices without needing to enable USB debugging. This feature is particularly useful for users with broken or non-functional screens.

Approaches

  • Automatic Enabling of USB Debugging

Benefits

  • Helps users with broken screens.
  • Expands the usability of scrcpy to more scenarios.
  • Enhances user experience and accessibility.

This feature would be helpful to improve scrcpy utility and for the users with broken/not usable displays for their mobile devices

@Giantvince1
Copy link

Giantvince1 commented Jun 24, 2024

Unfortunately, this is completely impossible due to how Android works at its core. The USB debugging feature is only able to be turned on by the user directly, meaning that scrcpy would have to somehow know the screen's resolution AND display density before even beginning to control it via UHID to turn on USB debugging. Not only that but the process is rather complicated and differs from phone to phone, especially with Samsung or OnePlus devices. Other OEMs implement skins of their own as well, but that's the best example I could think of that I know changes around even how the Settings page works.

Edit: I should be more clear here; scrcpy CAN control the device using OTG mode without USB debugging enabled. HOWEVER, it is UNABLE to display the screen in any capacity, NOR can it capture audio, without having USB (or wireless) debugging enabled beforehand. This means that your physical screen must work at least well enough for you to navigate settings in order to enable USB debugging manually. It doesn't have to respond to touch, but as long as you can see enough of the screen to know what you're doing, you'll be fine.

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