Genymobile
Screen flickering when using scrcpy and Oculus Quest 2
Environment
- OS: Windows 10 & 11
- Scrcpy version: 3.1 & 3.2 (tested on both)
- Installation method: Windows release
- Device model: Oculus quest2
- Android version: 14
Describe the bug
When playing in app, scrcpy runs great. However, when going into the main menu (with camera activated or not) the screen starts flickering or simply turns all black.
Console shows no special message or error code.
scrcpy worked fine with oculust Quest 3
Flickering issue on Quest 3 with --crop and --angle parameters (v76/v77)
Hello,
First of all, thank you for this amazing project — I use scrcpy daily with VR headsets, and it has been incredibly useful.
Recently, I’ve encountered the same flickering issue on Quest 3 (didn't test on quest 2 yet). On Quest 3 specifically, the issue appeared starting from version v76 and continues in v77. Version v75 works fine and does not show this behavior.
The flickering only occurs when a --crop and/or an --angle parameter are used --> (for me for quest 3 --crop 1600:1600:2295:270 --angle -22)
If you have any ideas about what might be causing this or if there’s a temporary workaround, that would be greatly appreciated.
Thanks again for your hard work!
Edit : Actually, I just noticed that this is related to the existing issue thread #5913
After testing I noticed that having an angle or not doesn't change a thing in terms of the cast flickering or not.
If you start casting with no menu's open: so no apps, no settings window, just the tray below it doesn't flicker. But as soon as you launch any app it starts flickering But if you then hit the start casting button in Side quest application a couple of times (new streams opening), eventually one will open with no flickering.
Issue appearing on Quest2 v76.1 aswell (not strap battery, 80% battery on headset)
Whenever a Quest menu appears (quick menu or warning prompt when out of boundary) The stream would start to flickers heavily and require a restart of the stream.
Smaller prompt such as "missing controller"/"low battery controller" doesn't seem to trigger it.
Note : It looks like the resolution of the stream tries to change when this issue occurs ? (could the menu force a new resolution?) => (It is hard to be sure 100% as sometimes the stream just renders pure black and doesn't flicker at all)
It looks like the resolution of the stream tries to change when this issue occurs ?
Interesting.
If you run scrcpy without any filter (no crop/angle), does the resolution change when you open that menu?
If you run
scrcpywithout any filter (no crop/angle), does the resolution change when you open that menu?
Running with the streaming without any other param(crop/resolution) (still quest2 etc.) still gives the same result.
After closer inspection it is hard to tell if the "resolution being reduced" effect is due to the Codec having trouble finding matching pixels between pure black and correct frame. The resolution may not be a correct lead
Playing a bit more with this issue.
It looks to be triggered when a frame could be skipped (abruptly going in or out of the gardian) : I managed to go out of the boundary and getting back slowly and issue didn't occured. But going back abruptly does.
The menu opening doesn't seem to be the issue by itself but HOVERING over interactable element of the menu.
TW: Flashing screen (duh)
The moment I'm hovering a button (any on the menu) it triggers the flickering. During the flickering, I managed to repeat the "frame skip"? again (in the video you can see the flicker is longer when I hover again a button.
Going in and out of sleep doesn't seem to trigger the issue but having a prompt directly being hovered by the pointer when coming back in VR does seem to trigger it.
The "haptic" feedback is trigger when changing the tab of the menu and doesn't trigger the issue. Unless the haptic feedback of the button is different, haptic is not the cause.
Note, we can see the quality being reduced in the gif but it looks to be more a codec issue than resolution being changed at runtime
Thank you all for continuing this support flickering with Quest products.
FYI just today I noticed meta UPDATED the UI entirely. If someone can further test maybe this is fixed or causing the problems..
As of the 30th of May (update 77.1) Quest2 issue still occurs. The UI update is not yet rolled on my tests hmd tho. Will give a heads up as soon as I get it.
For everyone following only this issue, it is more actively investigated in that other issue : #5913
My Oculus Quest 2 is flickering with v74, v76, and v78. Any updates?
My Oculus Quest 2 is flickering with v74, v76, and v78. Any updates?
You can find a "patch" made from the community in the #5913. You will have to place scrcpy-server in the right folder, but it works well.
SOLVED the problem of black screen and screen flickering! I have Quest 3 (update v79) Problem1: In SideQuest with default scrcpy 2.0, I was having black screen at streaming Problem2: When change scrcpy files to latest v3.2 - screen is flickering at streaming
Problem solving 1.Download scrcpy version 2.7: ( https://github.com/Genymobile/scrcpy/releases/tag/v2.7 ) 2.Extract/unzip the downloaded file. 3.Go to the folder where SideQuest is installed, for example: C:\Users...\AppData\Roaming\SideQuest\scrcpy-win64-v2.0 4.Delete everything inside that folder 5.Copy the v2.7 scrcpy files there.
