Skip to content

Conversation

@rsanjuan87
Copy link

@rsanjuan87 rsanjuan87 commented Sep 14, 2025

feat: allow to resize virual display as the scrcpy window size
imagen
left: no resizable virtual display after resize window
rigth: resizable virtual display after resize window

imagen

left: --new-display=:r6 ( window size * 6 )
center: --new-display (no reszizable)
right: --new-display=:r (window size * autofactor: calculated from device screen and default initial window size, this case autofactor = 2)

The resizable factor allows you to scale the size to avoid losing image quality.

usage example:

--new-display=1920x1080/420:r2
--new-display=:r
--new-display=/420:r

:rN

r: to indicate resizable screen
N: factor to multiply

tested on: MacOS Tahoe & Redmi Note 11 Pro 5G, & Android Studio Emulator (Android 16)

fixing #6350

@rsanjuan87 rsanjuan87 marked this pull request as ready for review September 14, 2025 14:53
@notchyves
Copy link

This is an actually great commit, and would make it much easier to use on wider displays such as mine!

@rom1v
Copy link
Collaborator

rom1v commented Sep 16, 2025

I don't really understand the meaning of "resolution factor", in particular how it provides additional information not already encoded into width×height/dpi.

@rsanjuan87
Copy link
Author

rsanjuan87 commented Sep 16, 2025

I don't really understand the meaning of "resolution factor", in particular how it provides additional information not already encoded into width×height/dpi.

(no resolution) "resizable" factor is to multiply the real window size to send to the virtual display resolution
ex: window size 100x50 with factor 2, will resize the virtual display to 200x100
this will avoid small screen resolution (as same window size)
the width×height/dpi is not applicable as the window will resize the display, you may indicate the initial resolution but after resizing the scrcpy window will resize the display

the autofactor (:r with out N factor) will calculate the factor with default window size and default resolution

@cusanarecords-art
Copy link

Wie kann ich das beweisen? think it's good to have a screen that can adapt to what I need and not just the one that's already created or the actual screen on the device.

@ivonnefbr
Copy link

Has Chrome switched to desktop mode?

feat: allow to resize virual display as the scrcpy window size imagen left: no resizable virtual display after resize window rigth: resizable virtual display after resize window
imagen

left: --new-display=:r6 ( window size * 6 ) center: --new-display (no reszizable) right: --new-display=:r (window size * autofactor: calculated from device screen and default initial window size, this case autofactor = 2)

The resizable factor allows you to scale the size to avoid losing image quality.

usage example:

--new-display=1920x1080/420:r2
--new-display=:r
--new-display=/420:r

:rN

r: to indicate resizable screen N: factor to multiply

tested on: MacOS Tahoe & Redmi Note 11 Pro 5G, & Android Studio Emulator (Android 16)

fixing #6350

@miltongg
Copy link

miltongg commented Sep 16, 2025

feat: allow to resize virual display as the scrcpy window size imagen left: no resizable virtual display after resize window rigth: resizable virtual display after resize window

imagen left: --new-display=:r6 ( window size * 6 ) center: --new-display (no reszizable) right: --new-display=:r (window size * autofactor: calculated from device screen and default initial window size, this case autofactor = 2)

The resizable factor allows you to scale the size to avoid losing image quality.

usage example:

--new-display=1920x1080/420:r2
--new-display=:r
--new-display=/420:r

:rN

r: to indicate resizable screen N: factor to multiply

tested on: MacOS Tahoe & Redmi Note 11 Pro 5G, & Android Studio Emulator (Android 16)

fixing #6350

Good addition! The resizable virtual display makes scaling much more flexible while preserving image quality — really improves usability and customization

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

Successfully merging this pull request may close these issues.

7 participants