I recently caved in and acquired an Oculus Quest. Even if Oculus is now part of the Facebook conglomerate (ugh), this piece of hardware is really impressive, and relatively affordable: you essentially get all the hardware you need to get access to the VR ecosystem for about ~€450. No need for a beefy PC or anything of the sort!
On the technical side, it seems the headset runs a modified Android version (7.1.1 (Nougat) according to Wikipedia). It is relatively easy to enable developer mode and install unsigned APKs. The system supports running “flat” Android apps as well as VR games. There’s a whole ecosystem of custom apps!
All interactions with the headset are supposed to go through the official Oculus app on your smartphone. Using the app, you can stream the view from inside the headset to your phone, tablet, or Chromecast-compatible receiver. Unfortunately, my TV doesn’t have a built-in Chromecast 🙁
If you’re in the same case, and would still appreciate to be able to cast your headset to your TV (VR is much more fun when there’s an audience!), carry on reading!
The steps are pretty simple:
- Get an ADB connection to your Quest
- Run the provided
Provided you have
adb on your system (it’s included in the Windows release), it’s only a matter of plugging your Quest to your computer and running:
$ adb list # Repeat until you see your Quest $ ./scrcpy -c 1200:1000:130:250 -m 1024 -b 8M
With recent ADB versions, you can even use ADB over WiFi! I higly recommend connecting both your PC and Quest to a 5GHz WiFi network though, the difference is incredible!
$ adb shell ip route # Take note of your device ip $ adb tcpip 5555 # Unplug your Quest before the next command $ adb connect IP_ADDRESS $ ./scrcpy -c 1200:1000:130:250 -m 1024 -b 8M
Plug your PC to your living room TV and voilà! You can even tweak the quality and resolution by tinkering with the parameters, just read the documentation 😀
I wrote this article in part to share a cool and useful trick, but also to test my blog’s new automated deployment system! This static website is automatically rebuilt every time I push on my GitHub repository (using the new-ish GitHub Actions) and a Web Hook asks this server to fetch the new version.
This will be the subject of another blog post, where I will also release the small tool I developed in order to easily react to web hooks.