← DepthSnap / Devices · Tools · About

Device hub — what can be checked, and on which transport

Not every device is reachable the same way. Glasses are usually a USB peripheral that answers a small command protocol; standalone headsets are Android computers that answer ADB, and only after developer mode is switched on. This page is the map: which device, which transport, which check runs today, and where the vendor’s own firmware and support pages live.

If something is already wrong, the faster route is to start from the symptom rather than from the brand: something is wrong — start here. It asks what you see, then points at the single thing to change.

BrandKindTransportChecks that run today
VITUREUSB glasseshid + display-mode + firmware-readhid, display-mode, firmware-read
XREALUSB glasseshid + display-mode + serial + sensorhid, display-mode, serial, sensor
RayNeoUSB glasseshid + display-modehid, display-mode
RokidUSB glasseshid + sensor + state-readhid, sensor, state-read
Mad GazeSerial glassesserialserial
Meta QuestStandalone Android headsetadbadb
PicoStandalone Android headsetadbadb
HTC VIVEStandalone Android headsetadbadb

VITURE

No on-board OS: the glasses are a display + IMU peripheral driven over USB.

ModelUSB idProtocolCheck it
One35CA:0001vitureDevice check (HID)
Pro35CA:101DvitureDevice check (HID)
PRO 2 XR35CA:1301viture (classic only)Device check (HID)

Vendor pages: Firmware update · FAQ

Official help: contact / support · FAQ

No standalone manual page was found (the /pages/user-manual path 404s); the FAQ carries the setup and firmware guidance.

XREAL

Air-series glasses are USB peripherals; Beam / Beam Pro are separate Android devices.

ModelUSB idProtocolCheck it
Air3318:0424nrealDevice check (HID)
Air 23318:0428nrealDevice check (HID)
Air 2 Pro3318:0432nrealDevice check (HID)
Air 2 Ultra3318:0426nrealDevice check (HID)

Vendor pages: Firmware update · Support

Official help: FAQ · FAQ

Support is a portal rather than a single contact page; the support index links to per-product help and warranty routes.

RayNeo

Air-series are USB peripherals; X2 / X3 are standalone Android AR glasses.

ModelUSB idProtocolCheck it
Air 3S Pro / Air 4 Pro1BBB:AF50rayneoDevice check (HID)
Air 3S Pro (alternate id)0F65:AF50rayneoDevice check (HID)

Vendor pages: Download centre · Hardware update guide

Official help: FAQ · FAQ

Per-product FAQ pages exist; there is no single contact page (that path 404s), so RMA goes through the product support pages.

Rokid

Max / Air are USB peripherals; AR Studio and Max Pro couple with Android compute units.

ModelUSB idProtocolCheck it
Air04D2:162FrokidDevice check (HID)
Max04D2:162DrokidDevice check (HID)

Vendor pages: Downloads · Firmware update guide

Official help: contact / support · FAQ

Academy articles are the closest thing to a manual, including the firmware update walkthrough.

Mad Gaze

Glow series talk over a virtual serial port rather than HID, so they need Web Serial.

ModelUSB idProtocolCheck it
Glow / Glow Plus—:—madgaze (serial)Device check (Web Serial)

Official channel: none reachable — madgaze.com did not resolve from here on 2026-11-05, so there is no official channel to point at. Glow owners are effectively on their own; the serial checks on the device-check page still work.

Meta Quest

Standalone Android headset. Nothing is reachable over HID; the useful channel is ADB, which needs developer mode plus USB debugging.

ModelUSB idProtocolCheck it
Quest 2 / 3 / Pro2833:—adbADB probe (WebUSB)

Vendor pages: Developer mode and USB debugging · Native Android development

Official help: contact / support · FAQ

The help centre doubles as manual and contact route; developer-mode instructions live in one article.

Pico

Standalone Android headset; ADB is the diagnostic channel, developer mode is enabled in the headset settings.

ModelUSB idProtocolCheck it
Neo 3 / 4 / 4 Ultra2FB8:—adbADB probe (WebUSB)

Vendor pages: Developer documentation · Developer FAQ

Official help: contact / support · FAQ

Consumer support and developer docs are separate sites; both are linked.

HTC VIVE

Focus and XR Elite run Android; the browser can only see them over ADB.

ModelUSB idProtocolCheck it
Focus 3 / XR Elite0BB4:—adbADB probe (WebUSB)

Vendor pages: Support · VIVE XR Elite help

Official help: contact / support · FAQ

Support index has per-product manuals and the contact route.

Three transports, three different questions

HID answers “is this device alive and what does it think it is” — identity, report rate, sensor values, display mode. It needs no permission beyond picking the device once. Serial is only for glasses that speak a serial protocol instead of HID; it is the same idea on a different pipe. ADB is for Android headsets, and it can answer much deeper questions — battery, storage, running services, crash logs — but the headset has to be put into developer mode and the prompt on its screen has to be accepted. If the prompt never appears, that is itself the finding.

Both probes are read-only. Nothing is installed, nothing is flashed, and no data leaves the browser.

What we will not pretend to know

A browser can reach three transports and no others: HID reports, a serial port, and USB endpoints (which is how ADB is reached). Anything that needs a kernel driver, a vendor daemon, or the display link itself is out of scope here — DP Alt-Mode negotiation, panel brightness measured from the panel, cable bandwidth. When a check cannot run, the page says so and leaves it out of the score instead of counting it as a pass.

Rankings by popularity are not given because we have no data to rank with; brands appear in the order they were added. If a device is missing, the useful thing to send is its USB vendor and product id — that is enough to identify which transport it exposes.

DepthSnap — free browser-based 2D to 3D SBS converter. No upload, no signup, no watermark.