Quest Setup,
Without the Guesswork.

One intended Meta identity across the headset, phone, MQDH, and build enrollment. A ForgeFX work email address does not automatically mean you have a Meta account or access to ForgeFX’s Meta developer organization.

1. Put on the existing headset. Open its profile/account area and identify the active Meta/Horizon profile. On your phone, check the profile in the Meta Horizon app and the paired headset. Record the account email and Horizon username privately.
2. If the headset is new, get the approved account identity from the setup owner before pairing. If it is company-managed or shows a business enrollment screen, stop and ask the setup owner for the managed-device path.
3. On the computer, use a dedicated browser profile or private window to inspect Meta login. Start from Meta’s account sign-in. Confirm the email/profile you are signing into; do not accept a familiar Facebook face as proof.
4. Use the same intended Meta account when MQDH opens its login browser and when accepting the release-channel invitation. Verify the identity again after the browser hands control back to MQDH.
5. Keep your MFA phone/authenticator and recovery email available. Use your password manager. Do not paste passwords, codes, or recovery details into Slack or this guide.

1. Bring the Quest headset, paired controllers, headset charger, and smartphone. For the optional MQDH route, also bring a Windows PC or Mac, its charger, and a USB data cable. A charging-only cable will not work for that route.
2. Charge the headset and battery strap if present; charge or replace controller batteries. Power on the headset and complete basic Wi-Fi, controller pairing, fit, and boundary setup.
3. Enable Bluetooth and any pairing permissions requested by the phone app. Use a clear, well-lit play area and set floor height correctly.
4. Make room on computer and headset for the download, installation, and updates. Keep a spare cable/port available; try direct connection rather than a hub if detection fails.

1. Install/update the official Meta Horizon mobile app. Sign in with the Meta account identified in step 1.
2. Open the headset/device section, select your headset, and confirm it is connected. A new headset needs the pairing flow and any code shown inside it. Do not pair someone else’s device by guesswork.
3. In the headset’s Settings, look for Software Update and About/System information. Record the full installed OS/system version privately for the support check. Menu labels vary by OS.
4. Ask the build owner for the tested Quest OS target and supported headset models. The October 26 build email does not specify them. Do not interpret “latest available” as the tested version.
5. Complete approved updates while charged and online; allow restarts and controller updates. If your headset is newer than the tested version or the target is unavailable, ask the build owner to test/approve that combination. Do not attempt an OS downgrade.

A “release channel” is Meta’s invitation-only distribution list for this app—not a Slack channel. Joining gives your Meta account access to the test build. It does not mean the app has finished installing.

1. First complete account identification and basic headset setup above. Use the Meta account actually signed into your headset, not whichever Facebook account your browser remembers.
2. Open Join the HCS review release channel. This is the exact signup link Devin confirmed in the Executive Review Prep thread. It is the enrollment link, not the APK download.
3. Open that signup link on your phone or computer. If Meta asks you to sign in, use the intended headset account. If the page shows the wrong identity, stop, sign out, and reopen the invitation with the correct account.
4. Check that the invitation is for the intended HCS app. Use the page’s join/accept action and complete any prompts. Exact wording varies; look for confirmation that you joined or already have access. If you see an error or cannot join, send the error to Devin privately without credentials.
5. Put on the headset, confirm the same account is active, and connect to Wi-Fi. Open the app Library. Show all apps, including apps not installed, if your Library has those filters. Locate the HCS app, select it, and choose its download/install action.
6. If the app is already installed but on the wrong channel, open its Library settings and look for Release channels. Select the review channel Devin identifies and apply any offered update. Do not guess a channel just because it says Alpha or Beta.
7. Wait for installation/update to complete, then launch. Continue with step 07 to verify the version and step 08 to take your own in-app screenshot.

If this route works, skip steps 04–06. MQDH, Developer Mode, USB debugging, developer-team membership, and a computer install are not prerequisites for ordinary release-channel enrollment and in-headset installation.

1. Download MQDH from Meta: Windows or macOS. Use the version approved by the technical owner and check the current installer’s system requirements.
2. Run the installer and open MQDH. On Mac, follow the installer/disk-image instructions to place the application in Applications. Ask IT if administrator approval is needed; do not bypass security controls.
3. Sign in with the same intended Meta developer account as the headset. Check which browser account was selected, as described in step 1.
4. Confirm MQDH opens normally. Do not confuse it with Meta Quest Link or a Meta developer website.

1. In Meta Horizon on the phone: open the headset/device area → select your headset → Headset Settings → Developer Mode → On. Some app versions put Devices under the menu.
2. Connect the headset to the computer with the USB data cable. Put the headset on and accept the USB debugging prompt. Select “Always allow from this computer” only for your trusted computer.
3. In MQDH, open Device Manager. Select the correct headset if several are listed. Confirm it shows as connected/Active, not merely remembered from an earlier session.
4. If Windows needs ADB drivers, use Meta’s official Oculus ADB driver download and its installation instructions. The Windows driver step is not needed on Mac.

Use the build links in Devin’s “Halliburton Cementing Services Executive Review Build” email, October 26, 2026, or the copied email in the Executive Review Prep Slack thread. The release-channel signup link is included above with Adam’s authorization. The direct APK download remains in the email and internal thread.

Reference APK filename from that email:
Halliburton Cementing Services-2026.10.26.1535-141.apk

1. Ask the build owner to confirm this is still the intended review build and provide the exact in-app version string and Android version code. The filename is a reference, not proof of the installed version.
2. Release-channel route: open Devin’s enrollment link using your intended Meta account. Accept enrollment. In MQDH’s App Distribution area, locate the HCS app and the approved release channel; use its install-to-device action if available. Confirm the target device and wait for completion.
3. Direct APK alternative: download the exact APK from Devin’s email. Select your connected headset in MQDH’s Device Manager and use the install/drag-and-drop APK control for your MQDH version. Wait for the success result before disconnecting.
4. Record the installed package/version information visible in MQDH and compare it with the build owner’s baseline. Capture MQDH for troubleshooting, but you still need the in-app proof in step 8.

1. Put on the headset. Open the app Library and look for the HCS app. A sideloaded build may be under Unknown Sources, rather than the main app grid. Confirm the exact launcher name/package with the build owner if similar apps appear.
2. Launch it. Complete any required permissions, app login, licensing, content downloads, and calibration. Do not assume a simulation login is the same as your Meta or Microsoft login.
3. Reach a usable simulation/menu screen and use the controls yourself. Then locate its version label. Look on the title/menu screen or an About/Settings panel if the app provides one.
4. Compare the exact visible version with the approved in-app version string from the build owner. Relaunch after restarting the headset to make sure success is repeatable.

1. In the running simulation, face the version display so the app identity and full version are readable. Dismiss system menus or overlays that cover it.
2. On the right controller, hold the Meta/Oculus button, then briefly press and release the right trigger. Do this before a long hold recenters your view. Do not hold the trigger down: that shortcut can record video instead.
3. Alternatively, open the headset system menu → Camera → Take photo, then return to the intended app view for capture. Exact system labels vary by OS.
4. Open the headset’s Gallery/Camera media and inspect the actual photo. It must show the app view and readable version—not the desktop, download page, account screen, or MQDH.
5. Transfer the capture privately: use the Gallery’s available sync/share option to the Meta Horizon phone app, then save it to the phone and attach it in Slack. If sync is unavailable, use MQDH’s capture/media controls for your version to save an actual headset-view screenshot to the computer, then attach that file. Ask support for the exact control if it is not visible.
6. Post it in the existing Executive Review Prep Slack thread, using the caption below. Do not upload proof to this public-link guide, Facebook, or a public album.

Name: [your name]
Headset model: [model]
In-app version shown: [copy exactly]
Approved version matches: [yes / no / awaiting confirmation]
I launched and operated the simulation myself: [yes / no]
Blocker, if any: [brief description]
[Attach the actual in-app screenshot]

Ready means the app works, its visible version matches the approved baseline, and your own screenshot is posted.

If capture is black/blocked or the version is absent, post the blocker. Do not call it complete from an installer success message.

• Before the meeting: charge again, test Wi-Fi, leave the app ready, confirm safe play space, and test casting/screen sharing with another attendee if the group needs to watch.
• Cannot cast: check the computer/headset network and guest isolation/firewall restrictions. Do not turn off organization security controls. A working APK does not guarantee a working cast.
• App will not start: note the exact error and installed version, restart, check storage/content/license/service access, and contact the build owner. Do not substitute another build silently.
• Need help: reply in Executive Review Prep with the failed step, device/OS, exact error, and a cropped screenshot. Keep passwords, MFA codes, recovery details, account emails, and serial numbers out of public captures.
• Greg or Dave blocked: raise it before the review. An Adam-only turn or a screen demo is not a substitute for each partner’s hands-on session.