Genymobile / Genymobile/scrcpy
Texture resolution does not match the device resolution.
- Dominant language
- C
- Stars
- 150k
- Forks
- 13.7k
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 2
Description
- [x] I have read the [FAQ](https://github.com/Genymobile/scrcpy/blob/master/FAQ.md).
- [x] I have searched in existing [issues](https://github.com/Genymobile/scrcpy/issues).
**Environment**
- OS: Windows 10
- scrcpy version: 2.1.1
- installation method: Windows release
- device model: Mumu12 Android Emulator v.3.5.22 (2201)
- Android version: 12
**Describe the bug**
The emulator resolution is 960X540, which is verified by scrcpy and adb cmd.
```
>adb shell wm size
Physical size: 540x960
```
or
```
>scrcpy --list-displays
scrcpy 2.1.1
INFO: ADB device found:
INFO: --> (tcpip) 127.0.0.1:16384 device V2199GA
scr...1 file pushed, 0 skipped. 1.6 MB/s (56995 bytes in 0.034s)
[server] INFO: List of displays:
--display=0 (960x540)
--display=2 (960x540)
```
However, when I use scrcpy, the screen resolution is 960X536. The display resolution height (536) is a little lower than origin height (540), as shown by the scrcpy cmd.
```
>scrcpy --display=0
scrcpy 2.1.1
INFO: ADB device found:
INFO: --> (tcpip) 127.0.0.1:16384 device V2199GA
scr...1 file pushed, 0 skipped. 1.6 MB/s (56995 bytes in 0.034s)
[server] INFO: Device: [vivo] vivo V2199GA (Android 12)
INFO: Renderer: direct3d
INFO: Texture: 960x536
```
When I set the emulator device resolution to any other value e.g.1920X1080, 1280X720, the texture resolution keeps the same.
Once I set the emulator device resolution to 960X540, the texture resolution is 960X536.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the discrepancy with `adb shell wm size`, `scrcpy --list-displays`, and `scrcpy --display=0` on the reported emulator setup. The issue names no source file or test entry point, so the renderer and display-size handling will need to be located first. Done means the texture resolution matches the selected device display across the reported resolutions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100