scrcpy/FAQ.md

235 lines
6.4 KiB
Markdown
Raw Normal View History

2018-03-11 17:34:11 +08:00
# Frequently Asked Questions
2021-05-28 16:18:36 +08:00
[Read in another language](#translations)
2018-03-11 17:34:11 +08:00
Here are the common reported problems and their status.
2022-02-23 02:08:15 +08:00
If you encounter any error, the first step is to upgrade to the latest version.
2018-03-11 17:34:11 +08:00
## `adb` and USB issues
2018-03-11 17:34:11 +08:00
2020-02-24 01:51:36 +08:00
`scrcpy` execute `adb` commands to initialize the connection with the device. If
`adb` fails, then scrcpy will not work.
2018-03-11 17:34:11 +08:00
2020-02-24 01:51:36 +08:00
This is typically not a bug in _scrcpy_, but a problem in your environment.
### `adb` not found
You need `adb` accessible from your `PATH`.
On Windows, the current directory is in your `PATH`, and `adb.exe` is included
in the release, so it should work out-of-the-box.
### Device not detected
2022-02-23 02:08:15 +08:00
> ERROR: Could not find any ADB device
2021-03-04 22:19:00 +08:00
Check that you correctly enabled [adb debugging][enable-adb].
2022-02-23 02:08:15 +08:00
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].
2018-03-11 17:34:11 +08:00
2021-03-04 22:19:00 +08:00
[enable-adb]: https://developer.android.com/studio/command-line/adb.html#Enabling
2018-03-11 17:34:11 +08:00
[drivers]: https://developer.android.com/studio/run/oem-usb.html
[google-usb-driver]: https://developer.android.com/studio/run/win-usb
2018-03-11 17:34:11 +08:00
### Device unauthorized
2022-08-21 19:51:12 +08:00
> ERROR: Device is unauthorized:
> ERROR: --> (usb) 0123456789abcdef unauthorized
> ERROR: A popup should open on the device to request authorization.
When connecting, a popup should open on the device. You must authorize USB
debugging.
If it does not open, check [stackoverflow][device-unauthorized].
[device-unauthorized]: https://stackoverflow.com/questions/23081263/adb-android-device-unauthorized
2020-02-24 01:51:36 +08:00
### Several devices connected
If several devices are connected, you will encounter this error:
2022-08-21 19:51:12 +08:00
> 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)
2022-02-23 02:08:15 +08:00
In that case, you can either provide the identifier of the device you want to
mirror:
```bash
scrcpy -s 0123456789abcdef
```
2020-02-24 01:51:36 +08:00
2022-02-23 02:08:15 +08:00
Or request the single USB (or TCP/IP) device:
2020-02-24 01:51:36 +08:00
```bash
2022-02-23 02:08:15 +08:00
scrcpy -d # USB device
scrcpy -e # TCP/IP device
2020-02-24 01:51:36 +08:00
```
2022-01-24 15:55:27 +08:00
Note that if your device is connected over TCP/IP, you might get this message:
2020-02-24 01:51:36 +08:00
> adb: error: more than one device/emulator
> ERROR: "adb reverse" returned with value 1
> WARN: 'adb reverse' failed, fallback to 'adb forward'
This is expected (due to a bug on old Android versions, see [#5]), but in that
case, scrcpy fallbacks to a different method, which should work.
[#5]: https://github.com/Genymobile/scrcpy/issues/5
### Conflicts between adb versions
> adb server version (41) doesn't match this client (39); killing...
This error occurs when you use several `adb` versions simultaneously. You must
find the program using a different `adb` version, and use the same `adb` version
everywhere.
You could overwrite the `adb` binary in the other program, or ask _scrcpy_ to
use a specific `adb` binary, by setting the `ADB` environment variable:
```bash
# in bash
export ADB=/path/to/your/adb
2020-02-24 01:51:36 +08:00
scrcpy
```
```cmd
:: in cmd
set ADB=C:\path\to\your\adb.exe
scrcpy
```
```powershell
# in PowerShell
$env:ADB = 'C:\path\to\your\adb.exe'
scrcpy
```
2020-02-24 01:51:36 +08:00
### Device disconnected
If _scrcpy_ stops itself with the warning "Device disconnected", then the
`adb` connection has been closed.
Try with another USB cable or plug it into another USB port. See [#281] and
[#283].
[#281]: https://github.com/Genymobile/scrcpy/issues/281
[#283]: https://github.com/Genymobile/scrcpy/issues/283
## HID/OTG issues on Windows
On Windows, if `scrcpy --otg` (or `--hid-keyboard`/`--hid-mouse`) results in:
> ERROR: Could not find any USB device
(or if only unrelated USB devices are detected), there might be drivers issues.
Please read [#3654], in particular [this comment][#3654-comment1] and [the next
one][#3654-comment2].
[#3654]: https://github.com/Genymobile/scrcpy/issues/3654
[#3654-comment1]: https://github.com/Genymobile/scrcpy/issues/3654#issuecomment-1369278232
[#3654-comment2]: https://github.com/Genymobile/scrcpy/issues/3654#issuecomment-1369295011
2020-02-24 01:51:36 +08:00
## Control issues
### Mouse and keyboard do not work
On some devices, you may need to enable an option to allow [simulating input].
2019-08-15 04:24:26 +08:00
In developer options, enable:
> **USB debugging (Security settings)**
> _Allow granting permissions and simulating input via USB debugging_
Rebooting the device is necessary once this option is set.
[simulating input]: https://github.com/Genymobile/scrcpy/issues/70#issuecomment-373286323
2020-02-24 01:51:36 +08:00
### Special characters do not work
2021-10-22 03:38:01 +08:00
The default text injection method is [limited to ASCII characters][text-input].
A trick allows to also inject some [accented characters][accented-characters],
but that's all. See [#37].
Since scrcpy v1.20, it is possible to simulate a [physical keyboard][hid] (HID).
2020-02-24 01:51:36 +08:00
[text-input]: https://github.com/Genymobile/scrcpy/issues?q=is%3Aopen+is%3Aissue+label%3Aunicode
[accented-characters]: https://blog.rom1v.com/2018/03/introducing-scrcpy/#handle-accented-characters
[#37]: https://github.com/Genymobile/scrcpy/issues/37
2021-10-22 03:38:01 +08:00
[hid]: README.md#physical-keyboard-simulation-hid
2020-02-24 01:51:36 +08:00
## Client issues
### Issue with Wayland
By default, SDL uses x11 on Linux. The [video driver] can be changed via the
`SDL_VIDEODRIVER` environment variable:
[video driver]: https://wiki.libsdl.org/FAQUsingSDL#how_do_i_choose_a_specific_video_driver
```bash
export SDL_VIDEODRIVER=wayland
scrcpy
```
On some distributions (at least Fedora), the package `libdecor` must be
installed manually.
See issues [#2554] and [#2559].
[#2554]: https://github.com/Genymobile/scrcpy/issues/2554
[#2559]: https://github.com/Genymobile/scrcpy/issues/2559
2019-08-15 04:24:26 +08:00
### KWin compositor crashes
On Plasma Desktop, compositor is disabled while _scrcpy_ is running.
As a workaround, [disable "Block compositing"][kwin].
[kwin]: https://github.com/Genymobile/scrcpy/issues/114#issuecomment-378778613
2019-08-15 04:24:26 +08:00
2020-02-24 01:51:36 +08:00
## Crashes
### Exception
2019-08-15 04:24:26 +08:00
If you get any exception related to `MediaCodec`:
2019-08-15 04:24:26 +08:00
```
ERROR: Exception on thread Thread[main,5,main]
java.lang.IllegalStateException
at android.media.MediaCodec.native_dequeueOutputBuffer(Native Method)
2019-08-15 04:24:26 +08:00
```
2020-12-14 16:04:14 +08:00
then try with another [encoder](doc/video.md#codec).
2021-05-28 16:18:36 +08:00
## Translations
Translations of this FAQ in other languages are available in the [wiki].
2021-05-28 16:18:36 +08:00
[wiki]: https://github.com/Genymobile/scrcpy/wiki
2023-03-28 14:30:43 +08:00
Only this FAQ file is guaranteed to be up-to-date.