Develop

Managing your device with MVDH

Updated: Nov 6, 2026
This page covers common tasks you can accomplish in Meta VR Developer Hub (MVDH), such as:

Change the device nickname

Device nicknames help identify devices more easily.
To give your device a nickname:
  1. In MVDH, select Device Manager from the left navigation pane.
  2. Under Devices, to the right of your device, select the gear icon to open the Device Settings window.
  3. Under General and to the right of Device Nickname, select Change.
  4. In the Device Nickname dialog, enter a new nickname for the device.
  5. Select Save to save the new nickname.

Turn off the boundary system

The boundary system creates a virtual boundary to ensure your safety while immersed in the VR experience.
For development and debugging purposes, you can turn off the boundary system.
To turn off the boundary system:
  1. In MVDH, select Device Manager from the left navigation pane.
  2. Under Device Actions, toggle off Boundary.
    You can also press the CTRL + Shift + G keyboard shortcut to turn the boundary system on or off.
Note: During development, you often debug directly in the development environment without wearing the headset, so it’s safe to turn off boundaries. When you are no longer actively developing, turn the boundary system back on.

Turn off the proximity sensor

The proximity sensor ensures the headset goes to sleep when not in use.
For development and debugging purposes, you can turn off the proximity sensor to keep the device in an active state. This can make it much easier for you to capture screenshots, record videos, and step through code.
To turn off the proximity sensor:
  1. In MVDH, select Device Manager from the left navigation pane.
  2. Under Device Actions, turn off Proximity Sensor to keep the headset in the active state. If disconnected from MVDH, the proximity sensor reactivates after 10 minutes, or as otherwise indicated in the MVDH settings.
    You can also press the CTRL + Shift + P keyboard shortcut to toggle this setting.
Note: Turning off the proximity sensor means your device will not go to sleep, and your battery won’t last as long as it would with the proximity sensor on. When you no longer need the headset to be in an active state continuously, turn the headset off, leave the device charging, or turn the proximity sensor back on.

Enable Android Developer Bridge (ADB)

Android Debug Bridge (ADB) is a command-line tool bundled with MVDH which enables you to communicate with your Meta VR device during development. By default, MVDH uses its bundled copy of adb itself. MVDH adds the folder of this copy only to its own PATH, not to the PATH your terminal uses. As a result, installing MVDH doesn’t make the adb command available in a terminal.
To run adb commands in a terminal, use one of these options:
  • Install Android SDK Platform-Tools, which include adb in the platform-tools folder. Add the platform-tools folder to your PATH to run adb by name, or run adb by its full path.
  • Run the copy of adb bundled with MVDH by its full path:
    • On macOS, with MVDH in the Applications folder, the full path is /Applications/Meta VR Developer Hub.app/Contents/Resources/bin/adb. If you installed MVDH in a different folder, use that folder’s path instead. If you updated MVDH from an earlier version, the app can keep its earlier name. In that case, the path is /Applications/Meta Quest Developer Hub.app/Contents/Resources/bin/adb.
    • On Windows, adb.exe is in the resources\bin folder of your MVDH installation folder.
    • To find this folder in MVDH, select Settings, and then on the General tab, select Edit next to the ADB location setting. The Select ADB Location dialog shows the folder as the Default location.
To run the bundled adb from a new macOS terminal, use its full path in quotes. The first command shows the version of adb, and the second lists connected devices:
"/Applications/Meta VR Developer Hub.app/Contents/Resources/bin/adb" version
"/Applications/Meta VR Developer Hub.app/Contents/Resources/bin/adb" devices
To run adb by name, add the folder of the bundled adb to your PATH for the current terminal session only:
export PATH="/Applications/Meta VR Developer Hub.app/Contents/Resources/bin:$PATH"
adb devices
Note: ADB is a utility that is part of the Android SDK⁠, and MVDH includes its own copy for its own use. If you have previously installed the Android SDK, you may have a different ADB version already running on your computer. The different ADB instances can conflict with each other, giving you unexpected results. To avoid version conflicts, use the same adb in your terminal and in MVDH.
If an adb command conflicts with an ADB server of a different version and MVDH can’t switch to a matching adb by itself, MVDH shows a warning message titled Another ADB instance found. If this warning message appears, you can use the existing ADB version installed on your computer by changing the ADB location in MVDH. To open the ADB location setting from the message, select Check settings.
To change the ADB path in MVDH:
  1. In MVDH, select Settings from the left navigation pane.
  2. On the General tab, check that the ADB location setting shows the folder of the ADB installation you want MVDH to use.
  3. To change the path, select Edit next to the ADB location setting. In the Select ADB Location dialog, select Stored ADB location, and then choose an adb file from the Select location list, or select the folder button to add an adb file from your computer. Select Save. MVDH switches to the selected adb without restarting.

Enable ADB over Wi-Fi

With MVDH, you can connect the headset wirelessly to the computer using ADB over Wi-Fi. Ensure that your headset and development machine are connected to the same Wi-Fi network.
To enable ADB over Wi-Fi:
  1. Open the Device Manager page from the left navigation pane.
  2. Under Device Actions, toggle on ADB over Wi-Fi. The status under ADB over Wi-Fi changes to enabled.
  3. Disconnect the USB cable from the headset to continue using your headset wirelessly.
For more information on ADB, see Android Debug Bridge.
Link is a tool that speeds up development by enabling you to stream apps from your development machine directly to your headset.
Note: Link causes your device to behave like a PC VR headset until the tool is explicitly turned off. To speed up testing build time, use Link during XR application development, even if you only intend to release your app as a standalone headset app.
To enable Link with MVDH:
  1. Open the Device Manager page from the left navigation pane.
  2. Under Device Actions, next to Meta Quest Link, open the Select Mode drop-down list, and select either Cable or Air Link connection modes.
  3. Select the button next to the connection mode to toggle on Meta Quest Link.
To switch between Air Link and Cable connection modes:
  1. Under Device Actions, next to Meta Quest Link, toggle off Meta Quest Link.
  2. Under Device Actions, next to Meta Quest Link, open the Select Mode drop-down list, and select either Cable or Air Link.
  3. Select the button next to the connection mode to toggle on Meta Quest Link.
To learn more about using Link, see Link.

Configure MVDH settings

To view and update MVDH settings:
  1. Open MVDH.
  2. In the left navigation pane, select Settings.
  3. Select one of the following four tabs to view and edit settings:
    • General, for general settings, including ADB Path, System Sound, and more.
    • About, for general information about the MVDH installation, such as Meta VR Developer Hub Version and Terms of Service.
    • Notifications, for notification settings.
    • Internal, for additional system settings.
Meta
English (US)
© 2026 Meta