ADB check — talk to an Android headset from the browser

Standalone headsets — Quest, Pico, VIVE Focus and XR Elite — are Android computers. Their USB port exposes an ADB interface once USB debugging is switched on, and from there the device can be asked for its model, its battery, its storage and its logs. This page opens that channel directly from Chrome: no SDK, no platform-tools, nothing installed.

Turn USB debugging on first

If the picker shows nothing, the headset is almost certainly not exposing ADB yet. In order:

1. Meta Quest — enable developer mode for the account in the Meta Horizon phone app (Developer Mode → on), then in the headset open Settings → System → Developer → USB connection dialog, and accept the prompt that appears when this page connects. Meta's instructions.
2. Pico — Settings → General → About → tap the software version repeatedly to unlock developer options, then Settings → Developer → USB debugging. Pico developer docs.
3. HTC VIVE Focus / XR Elite — Settings → General → About → tap the build number seven times, then Settings → Developer → USB debugging. VIVE support.
4. XREAL Beam / RayNeo X2 and X3 — the same Android steps apply, because they are Android devices with a display attached.

Then plug the headset in with a data cable, press Pick a device, and choose the entry that mentions ADB or the vendor name. The first connection will usually stop at an authorisation prompt on the headset's screen — accept it there, then run the check again.

What the check actually does

It sends the ADB greeting packet and reads the reply. Three outcomes, all informative:

• Connected — the headset answered with its own banner, which carries its model name. That means the cable, the interface and the debugging setting are all correct.
• Waiting for authorisation — ADB is running, and the headset has asked this computer to prove itself. That is the state where a prompt is sitting on the headset screen. Accepting it once is enough for future visits.
• No ADB interface — the port did not expose ADB at all. Either debugging is off, the cable is charge-only, or the device does not run Android.

This page deliberately stops at that handshake: it does not sign anything, does not open a shell, and cannot read a single file. Deeper actions need the authorisation step above and are not attempted here — claiming otherwise would be the easy lie and the wrong one.

When the answer is "no ADB interface"

Work down this list, in order — each step removes one possible cause:

1. Try another cable. Charge-only USB-C cables are extremely common and produce exactly this symptom.
2. Try another port, ideally one directly on the machine rather than through a hub or an adapter.
3. Check the headset's own USB connection dialog. Some firmwares default to "charging only" and need "file transfer" or "debugging" selected each time.
4. If the headset pairs over Wi-Fi for development, wireless ADB is a different path — same protocol, different pipe, and out of scope for this page.

For glasses rather than headsets, the right tool is device check: they expose HID or a serial port, not ADB.

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