You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Scrcpy is not working on the latest Meta Quest OS versions (Meta Horizon OS >= 74) #5913
OS: Windows
Scrcpy version: 3.1
Installation method: Windows release
Device model: Meta Quest 2/3
Android version: 12
Describe the bug
I tested scrcpy on Quest 2 and the Quest 3 with the latest OS version (74) and I have now a black screen. It was working fine with the previous OS versions. Do you have any news about Meta blocking tools such as scrcpy ?
Update (17/11/25):
A workaround has been found for this issue : #5913 (comment)
Please note that this is only a workaround — not a perfect solution, and not a definitive fix for the issue.
changed the title [-]Scrpcy is not working on Meta Quest (Meta Horizon OS 74)[/-][+]Scrcpy is not working on the latest Meta Quest OS version (Meta Horizon OS 74)[/+]on Mar 10, 2025
Update: I reached the Meta technical support who told me : "The scrcpy to our knowledge uses hidden AOSP (Android open source project, which is the foundation of the Horizon OS in Meta Quest devices) features, so changes in either can result in the scenario you've encountered. As scrcpy is a third party solution, from Meta's side we are unable to provide any support for it." So I guess this the end of the scrcpy compatibility (with the pro plan at least)
I'm having this problem with Horizon OS 74 and scrpy 3.1 but do not have Quest for Business installed afaik. (Also where do you check to make sure it's not installed, and/or remove it to test this)
I'm having this problem with Horizon OS 74 but do not have Quest for Business installed afaik. (Also where do you check to make sure it's not installed, and/or remove it to test this)
I also had the issue on non quest for business devices recently, so it seems this issue will concern everyone eventually. You need to pay for the quest for business mode, so it can't be enabled by accident
I mean i get a blank screen. (see the issue description)
I'm not sure how it's related to cropping
Describe the bug
I tested scrcpy on Quest 2 and the Quest 3 with the latest OS version (74) and I have now a black screen. It was working fine with the previous OS versions. Do you have any news about Meta blocking tools such as scrcpy ? If so, that really sucks.
Thank you for the update on the binary TESTED just now on Quest 2 with all the latest software PTC v83 Menus working just fine no flickering:) with binary server fix.
Ty all involved.
1222.1.mp4
Hey, what command arguments did you use? I still have the problem, even with the fix.
EDIT: It works now, idk why, but I still would like the command because I see both eyes, i want to have a normal screen format.
@kevinagnes@ashmanmedia@joranmarcy@danielburongarcia if any of you happen to see this, would you be able to test this build? The previous workaround broke the original Quest model, but I don't have access to a Quest 2 or 3 to test if my fix didn't break anything. I've attached server/client builds for convenience, but you can build it from https://github.com/doyle31/scrcpy if you want to.
@kevinagnes@ashmanmedia@joranmarcy@danielburongarcia if any of you happen to see this, would you be able to test this build? The previous workaround broke the original Quest model, but I don't have access to a Quest 2 or 3 to test if my fix didn't break anything. I've attached server/client builds for convenience, but you can build it from https://github.com/doyle31/scrcpy if you want to.
@doyle31
I tested it, and it works PRETTY MUCH but when using crop it flickers?.
Meta Quest 3, firmware 2.7
See video.
https://youtu.be/YtAQeeh6WFM
My bat file with any info I shouldn't be using.
@echo off
adb -e shell am broadcast -a com.oculus.vrpowermanager.prox_close
adb -e shell setprop debug.oculus.guardian_pause 0
scrcpy.exe --display-id=0 --max-size=1776 --crop=1776:993:150:608
--tcpip=+192.168.1.155 --video-codec=h265 --print-fps --max-fps=60
--keyboard=disabled --no-control --pause-on-exit=if-error %*
@kevinagnes Thanks! @ashmanmedia I'm not very familiar with scrcpy, but that sounds like a problem with it or Meta's code, not the changes that I made. Thanks for me helping test this.
@kevinagnes@ashmanmedia@joranmarcy@danielburongarcia if any of you happen to see this, would you be able to test this build? The previous workaround broke the original Quest model, but I don't have access to a Quest 2 or 3 to test if my fix didn't break anything. I've attached server/client builds for convenience, but you can build it from https://github.com/doyle31/scrcpy if you want to.
Activity
[-]Scrpcy is not working on Meta Quest (Meta Horizon OS 74)[/-][+]Scrcpy is not working on the latest Meta Quest OS version (Meta Horizon OS 74)[/+]marcynumix commentedon Mar 11, 2025
Update: It seems it is blocking scrpcy only when Quest for Business is installed and configured on the headset
marcynumix commentedon Mar 11, 2025
Update: I reached the Meta technical support who told me : "The scrcpy to our knowledge uses hidden AOSP (Android open source project, which is the foundation of the Horizon OS in Meta Quest devices) features, so changes in either can result in the scenario you've encountered. As scrcpy is a third party solution, from Meta's side we are unable to provide any support for it." So I guess this the end of the scrcpy compatibility (with the pro plan at least)
jamie-pate commentedon Mar 15, 2025
I'm having this problem with
Horizon OS 74and scrpy 3.1 but do not haveQuest for Businessinstalled afaik. (Also where do you check to make sure it's not installed, and/or remove it to test this)jamie-pate commentedon Mar 15, 2025
Meta lists scrcpy in their docs, maybe you can send them this link and request them to escalate?
https://creator.oculus.com/create-build/capturing-video-from-a-quest-headset/#stereoscopic-capture
marcynumix commentedon Mar 17, 2025
I also had the issue on non quest for business devices recently, so it seems this issue will concern everyone eventually. You need to pay for the quest for business mode, so it can't be enabled by accident
marcynumix commentedon Mar 17, 2025
Thanks for the link, I will send it to Meta
rom1v commentedon Mar 17, 2025
It should work with scrcpy 3.x. (#4162, fixed by #5455)
marcynumix commentedon Mar 18, 2025
Update: Meta support told me they were investigating the issue
jamie-pate commentedon Mar 18, 2025
3.1 does not work for me 🤔
rom1v commentedon Mar 18, 2025
You mean cropping is not applied? 🤔
jamie-pate commentedon Mar 18, 2025
I mean i get a blank screen. (see the issue description)
I'm not sure how it's related to cropping
kevinagnes commentedon Apr 3, 2025
I got it working with a Quest3 (v76) with Meta For Business MDM, by passing the device id 0
--display-id=0When listing the displays:
rom1v commentedon Apr 3, 2025
0 is the default, so passing
--display-id=0should have absolutely no impact.marcynumix commentedon Apr 3, 2025
I just tested this morning (without the --display-id argument) and scrcpy was suddenly working again with the MDM. Go figure.
214 remaining items
Yarkhan commentedon Jan 26, 2026
Tested the fix on a quest 2 and it works as well. Thanks a lot rom1v!
asteroidlordfr commentedon Mar 20, 2026
@ashmanmedia Could you send that compiled version somewhere?
unedagare-ux commentedon Apr 23, 2026
Any chance to do it on macOS?
Add hacky workaround to fix Meta Quest flickering
shohiduzjaman7 commentedon May 15, 2026
How to lock/unlock the mouse like BlueStacks to play PUBG .. ?
Caitex212 commentedon Jun 25, 2026
Hey, what command arguments did you use? I still have the problem, even with the fix.
EDIT: It works now, idk why, but I still would like the command because I see both eyes, i want to have a normal screen format.
doyle31 commentedon Aug 2, 2026
@kevinagnes @ashmanmedia @joranmarcy @danielburongarcia if any of you happen to see this, would you be able to test this build? The previous workaround broke the original Quest model, but I don't have access to a Quest 2 or 3 to test if my fix didn't break anything. I've attached server/client builds for convenience, but you can build it from https://github.com/doyle31/scrcpy if you want to.
scrcpy-linux-x86_64-247f93e8.tar.gz
scrcpy-win32-247f93e8.zip
scrcpy-win64-247f93e8.zip
scrcpy-server-247f93e8.tar.gz
SHA256SUMS.txt
ashmanmedia commentedon Aug 2, 2026
doyle31 commentedon Aug 2, 2026
Cool, thanks!
kevinagnes commentedon Aug 4, 2026
I will try this tomorrow morning and get back to you.
ashmanmedia commentedon Aug 5, 2026
doyle31 commentedon Aug 5, 2026
@kevinagnes Thanks!
@ashmanmedia I'm not very familiar with scrcpy, but that sounds like a problem with it or Meta's code, not the changes that I made. Thanks for me helping test this.
UnitedShoes commentedon Oct 2, 2026
I can confirm this works on my Quest 2. I tried the release 4.1 package, fresh install, I got a cryptic error. This build fixed it for me!
rom1v commentedon Oct 2, 2026
The fix you tested was only for Quest 1. It should not have impact on Quest 2. What "cryptic error" did you get?