Android/scrcpy
1
0
Fork 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity

Update FAQ to match the latest version

Browse source
This commit is contained in:
Romain Vimont 2022-02-22 19:08:15 +01:00
parent 6a9b2f2c36
commit 1f951f1a3a
1 changed files with 26 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

44
FAQ.md
View file

@ -4,23 +4,16 @@
Here are the common reported problems and their status. Here are the common reported problems and their status.
If you encounter any error, the first step is to upgrade to the latest version.
## `adb` issues ## `adb` issues
`scrcpy` execute `adb` commands to initialize the connection with the device. If `scrcpy` execute `adb` commands to initialize the connection with the device. If
`adb` fails, then scrcpy will not work. `adb` fails, then scrcpy will not work.
In that case, it will print this error:
> ERROR: "adb get-serialno" returned with value 1
This is typically not a bug in _scrcpy_, but a problem in your environment. This is typically not a bug in _scrcpy_, but a problem in your environment.
To find out the cause, execute:
```bash
adb devices
```
### `adb` not found ### `adb` not found
@ -32,11 +25,9 @@ in the release, so it should work out-of-the-box.
### Device unauthorized ### Device unauthorized
> ERROR: Device is unauthorized:
> error: device unauthorized. > ERROR: --> (usb) 0123456789abcdef unauthorized
> This adb server's $ADB_VENDOR_KEYS is not set > ERROR: A popup should open on the device to request authorization.
> Try 'adb kill-server' if that seems wrong.
> Otherwise check for a confirmation dialog on your device.
When connecting, a popup should open on the device. You must authorize USB When connecting, a popup should open on the device. You must authorize USB
debugging. debugging.
@ -48,10 +39,16 @@ If it does not open, check [stackoverflow][device-unauthorized].
### Device not detected ### Device not detected
> error: no devices/emulators found > ERROR: Could not find any ADB device
Check that you correctly enabled [adb debugging][enable-adb]. Check that you correctly enabled [adb debugging][enable-adb].
Your device must be detected by `adb`:
```
adb devices
```
If your device is not detected, you may need some [drivers] (on Windows). There is a separate [USB driver for Google devices][google-usb-driver]. If your device is not detected, you may need some [drivers] (on Windows). There is a separate [USB driver for Google devices][google-usb-driver].
[enable-adb]: https://developer.android.com/studio/command-line/adb.html#Enabling [enable-adb]: https://developer.android.com/studio/command-line/adb.html#Enabling
@ -63,12 +60,23 @@ If your device is not detected, you may need some [drivers] (on Windows). There
If several devices are connected, you will encounter this error: If several devices are connected, you will encounter this error:
> error: more than one device/emulator ERROR: Multiple (2) ADB devices:
ERROR: --> (usb) 0123456789abcdef device Nexus_5
ERROR: --> (tcpip) 192.168.1.5:5555 device GM1913
ERROR: Select a device via -s (--serial), -d (--select-usb) or -e (--select-tcpip)
the identifier of the device you want to mirror must be provided: In that case, you can either provide the identifier of the device you want to
mirror:
```bash ```bash
scrcpy -s 01234567890abcdef scrcpy -s 0123456789abcdef
```
Or request the single USB (or TCP/IP) device:
```bash
scrcpy -d # USB device
scrcpy -e # TCP/IP device
``` ```
Note that if your device is connected over TCP/IP, you might get this message: Note that if your device is connected over TCP/IP, you might get this message: