Dashboard
Battery
—
Storage used
—
RAM used
—
CPU temp
—
Device info
Connect a device to see info.
Quick actions
ADB Terminal
adb $
Quick commands
devices
connect
disconnect
model
build id
build type
debuggable
battery
3rd party pkgs
storage
cpu top
reboot
reboot btl
reboot rec
reboot sideload
enable dev
uploader on
120 hz
90 hz
72 hz
clear logcat
screenshot
screenrecord
reset density
restart ui
home key
help
Device Setup Wizard
Connect your Quest 2/3/Pro via USB-C data cable and enable ADB debugging.
✓
Install ADB platform tools
Ensure
adb is in PATH. Download from Android SDK platform-tools or install via your package manager (brew install android-platform-tools).✓
Enable developer mode in Meta Horizon app
Meta Horizon app → Menu → Devices → [your headset] → Developer Mode → toggle On. Requires Meta developer organization membership (free at developer.oculus.com).
3
Connect via USB-C data cable
Use a USB-C data cable (not charge-only). Put on headset and accept the "Allow USB Debugging" prompt. Tick "Always allow from this computer".
4
Verify connection
Run
adb devices — your device should be listed as "device". If shown as "unauthorized" — re-accept the USB debugging prompt inside the headset.Network Scanner
Scans your local network for Quest devices listening on ADB port 5555. Works via WebSockets if a local ADB proxy is running; otherwise shows demo results.
App Manager
Batch Installer
Queue multiple APKs for sequential installation. Drag & drop supported where the browser allows file system access.
Beat Saber
Virtual Desktop
Gorilla Tag
Pistol Whip
VRChat
0 files queued
OBB Manager
OBB expansion files must be named exactly
main.<version>.<package>.obb and placed in /sdcard/Android/obb/<package>/Push OBB
list obb dir
push obb
stat obb
File Browser
📁/sdcard
Logcat
0 lines
Performance Monitor
0%
CPU
0%
GPU
0%
RAM
—
Temp
FPS
—
Frame time
—
CPU freq
—
GPU freq
—
cpuinfo
meminfo
gfxinfo
top
thermal zone
cpuinfo raw
boost perf
normal perf
batterystats
Display Settings
Refresh rate
Current: 90 Hz · 120 Hz requires Quest 3 or Quest Pro
Resolution & rendering
1.0×
0.7× (perf)1.0× (default)1.5× (quality)
Level 2
OffLowMediumHighHigh+
Display toggles
Chromatic aberration correction
setprop debug.oculus.ca 1
Eye tracking (Quest Pro / Quest 3)
setprop debug.oculus.eyetracking 1
Dynamic resolution scaling
setprop debug.oculus.drs.enabled 1
Passthrough high-res mode
setprop debug.oculus.passthroughHR 1
Night display (warm color temperature)
settings put secure night_display_activated 1
Developer Overlay
Performance HUD overlays appear inside the headset during VR sessions. Changes apply immediately — no reboot needed.
Performance HUD
FPS counter
setprop debug.oculus.hud fps
GPU utilization
setprop debug.oculus.hud gpu
CPU utilization
setprop debug.oculus.hud cpu
Memory usage
setprop debug.oculus.hud mem
Thermal throttle status
setprop debug.oculus.hud thermal
App timing (frame breakdown)
setprop debug.oculus.hud apptiming
Network latency (Air Link)
setprop debug.oculus.hud network
Tracking & guardian debug
Tracking camera overlay
setprop debug.oculus.hud tracking
Guardian wireframe debug
setprop debug.oculus.hud guardian
Audio Settings
Volume levels
75%
80%
50%
Audio toggles
Headphone jack (3.5mm)
persist.oculus.headphone.mode 1
Microphone noise cancellation
debug.oculus.mic.nc 1
Mute speakers during screen record
debug.oculus.silence.speakers 1
max vol
mute
audio dump
audio flinger
Controllers
Left controller
Battery
82%
FW v22.0.0.5 · Connected
Right controller
Battery
64%
FW v22.0.0.5 · Connected
dump input
L battery
R battery
haptic 100%
haptic off
pair mode
Guardian / Boundary
Boundary mode
Stationary: 1m radius circle around you. No room-scale setup required.
Boundary settings
Show guardian in VR
Always-visible boundary
Passthrough on boundary approach
Floor height adjustment
0 cm
-30 cm0 (auto)+30 cm
reset boundary
clear all
reset floor
dump guardian
Diagnostics
Firmware Manager
Current build
Not connected
Latest available
—
Connect device and click Check for Updates.
Bootloader Unlocker
Userdebug builds only
Warning: Unlocking the bootloader wipes ALL user data and voids warranty on some builds. Only works on userdebug firmware. This operation cannot be undone without re-locking (which also wipes data).
✓
Verify userdebug build
Build type must be "userdebug". Check in Dashboard → Device Info. Bootloader unlock is blocked on "user" (retail) builds.
2
Enable OEM unlock
Settings → Developer settings → OEM unlock → toggle On.
3
Reboot to bootloader
Run
adb reboot bootloader — device enters fastboot mode.4
Run unlock command
Run
fastboot oem unlock — confirm on-device prompt.5
Device wipes and reboots
All user data erased. Bootloader is unlocked on next boot.
Firmware Converter
Userdebug → User
Converts a userdebug firmware package to user (retail) build type by patching build.prop and removing debug-only components. Runs entirely in-browser — no data leaves your machine.
build.prop changes (preview)
Mixed Reality Capture
MRC composites a real-world camera feed with the VR render. Requires an external camera connected to your PC and configured here.
Camera configuration
Chroma key (greenscreen)
Alignment calibration
ADB Macros
Pre-built command sequences for common workflows. Click a macro to run it in the ADB terminal.
Screenshot & Mirror
Preview
📷No screenshot yet
Settings
ADB connection
Auto-reconnect on disconnect
Use WebUSB when available
Device profile
Tool preferences
Confirm destructive actions
Auto-pull screenshots after capture
Dark theme (always on)