Screen outpout laggy (Input via mouse works fine)

[ChupeteSobarzo]

• [Y ] I have read the FAQ.
• [ Y] I have searched in existing issues.

Environment

• OS:Windows
• scrcpy version: scrcpy-win64-v2.1.1
• installation method:Windows release
• device model: Samsung note 9
• Android version: 10

When running the screen on pc gets really laggy and runs at around 1 fps, the input on the phone gets almost no delay.

Screen is a little broken (Gets buggy sometimes, so i cant use it really) so i checked #1285 and #2884 and tried recording through

adb shell screenrecord /sdcard/file.mp4
adb pull /sdcard/file.mp4

The pulled video is fine.

Also tried solutions listed in #3064 and doesnt seem to affect.

Any help?

scrcpy-win64-v2.1.1\scr... file pushed, 0 skipped. 46.7 MB/s (56995 bytes in 0.001s)
[server] INFO: Device: [samsung] samsung SM-N9600 (Android 10)
[server] WARN: Audio disabled: it is not supported before Android 11
INFO: Renderer: direct3d
WARN: Demuxer 'audio': stream explicitly disabled by the device
INFO: Texture: 512x960

[rom1v]

Screen is a little broken

Try scrcpy --turn-screen-off.

The pulled video is fine.

And with scrcpy --record=file.mp4?

[ChupeteSobarzo]

It ran perfectly with scrcpy --record=file.mp4

INFO: Recording started to mp4 file: file.mp4
INFO: Renderer: direct3d
WARN: Demuxer 'audio': stream explicitly disabled by the device
WARN: Audio stream recording disabled
INFO: Texture: 512x960

Perfectly smooth run, tried again with no record on and it lags again.
Its a fix for now... I can use it and record always i guess but maybe replicate that without recording would be nice

scrcpy --turn-screen-off Runs better than normal but still laggier than recording

[rom1v]

Perfectly smooth run, tried again with no record on and it lags again.

Wait, you mean that the content in the window in real time is smoother with scrcpy --turn-screen-off --record=file.mp4 than scrcpy --turn-screen-off? That can't be true (i.e. that's a coincidence), the recorder is only a client-side additional component 😮

Add --print-fps to both commands and compare what happens.

[ChupeteSobarzo]

You were right, apparently it ran smoothly the first time with the recorder and kinda laggy the second time with screen off but the events werent connected because it runs smoothly with both of those now.
It actually runs smoothly when i run it without those now too!
Not quite sure of the reasons but its working perfectly now! thank you so much.

On another note after i managed to run the app it wont accept mouse input apparently, as it wont transfer to an event in the app and it works fine outside it... Is there a touch event input? So when i click it generates a touch event instead of an actual mouse click on the phone? Just asking im not really sure how the mouse translates to the actual phone but i read some other issues and thats the picture that im getting.

[ChupeteSobarzo]

[Update]
Ok so i have done a few more tests and i have identified that the issue is with the specific cellphone (Note 9) in the specific app (MH Now)
Tried with another phone (Note 11 with input via usb depuration enabled) and it worked perfectly, samsung doesnt have this config so i dont know how i could make it work for the note 9