Smart Glasses · Xreal
Xreal Air 2 Won't Pair
Is your Xreal Air 2 failing to pair with the Nebula app or refusing to connect to your host device? Follow this troubleshooting guide to isolate cable issues, app permissions, and firmware corruption.
Symptoms
- Nebula app remains stuck on 'Searching for glasses' or 'Connect your glasses' screen.
- No video display output while host phone or laptop charges the glasses.
- AR Space mode crashes or freezes immediately upon initiating connection.
- Smart glasses repeatedly disconnect and reconnect every few seconds.
- Host phone displays a 'USB device not recognized' or 'High power consumption' warning.
- Firmware update fails midway through the pairing process in Nebula.
Quick troubleshooting
Step 1
Verify Host Device DP Alt Mode and Cable Compatibility
Ensure the device you are connecting to natively supports DisplayPort Alt Mode over USB-C. Standard phone charging cables or power-only USB-C cords will not transmit video or IMU telemetry data. Use the stock angled Xreal USB-C cable or a verified 10Gbps/4K video-rated replacement cable.
Step 2
Grant Required Permissions and Reset Nebula App
Open your phone's system settings, locate the Nebula app, and ensure all permissions for Bluetooth, Nearby Devices, and Location are fully granted. Clear the app cache and force stop the app. Relaunch Nebula before plugging the glasses back in to establish a fresh handshake.
Step 3
Perform a Web-Based Firmware Reflash
If the glasses refuse to pair through the mobile app, connect them to a PC or Mac running Google Chrome or Edge. Visit Xreal's official web-based firmware update page to manually reflash the MCU and display firmware. This bypasses mobile app handshake failures and restores standard factory parameters.
Step 4
Inspect Ports and Re-seat USB-C Connection
Check both the temple port on the Xreal Air 2 and the host device's USB-C port for dust, lint, or bent pins. Disconnect the cable, wait 15 seconds for the onboard capacitors to discharge, and firmly reconnect the cable until it clicks securely into place.
Likely causes
- Incompatible USB-C port on the host device lacking DisplayPort (DP) Alt Mode.
- Missing Bluetooth, Location, or Nearby Device permissions for the Nebula app.
- Damaged or non-compliant USB-C video cable unable to transmit display and telemetry data.
- Outdated or corrupted internal firmware on the Xreal Air 2 main controller board.
- Host device power management or battery saver mode throttling the USB port.
- Physical hardware failure in the glasses' internal display receiver or flex cable.
What's going on
When your Xreal Air 2 fails to pair, it usually stems from a breakdown in the hybrid protocol handshake required by modern AR glasses. Unlike standard Bluetooth headphones, smart glasses in the Xreal AR Glasses line rely on a dual connection: a high-bandwidth USB-C DisplayPort (DP) Alt Mode signal for video feed, alongside USB data protocols (or Bluetooth bridging) to feed tracking data back to the host device.
If the host device fails to recognize either the video receiver chip or the head-tracking IMU sensor within the glasses, the Nebula application will refuse to complete the pairing process. Understanding whether the connection drop is caused by missing software permissions, improper cable specs, or a hardware-level board issue is key to bringing your display back online.
Symptoms people notice
- Endless pairing loop: The Nebula app continuously scans without discovering the connected frame.
- Black screen with audio only: Sound plays through the temple speakers, but the Micro-OLED panels remain completely dark.
- Intermittent screen mirroring: The display works briefly in basic screen-mirror mode, but switching to spatial AR mode drops the connection.
- Error prompts on host: Your Android, iOS, or PC device reports that an incompatible USB device was connected.
- Firmware update bricking: The glasses become unresponsive after a failed OTA update via the app.
Likely causes
- Incompatible USB-C hardware: Connecting the glasses to a port that lacks native DP Alt Mode capability prevents video signal handshake.
- App permission blocks: Modern mobile operating systems restrict background device discovery if Location, Bluetooth, or Nearby Device permissions are withheld.
- Cable degradation: Internal copper trace strain in the stock USB-C cable—frequently caused by bending near the temple connector—breaks the high-speed data lanes.
- Desynchronized firmware: A discrepancy between the Nebula app version and the onboard MCU microcode halts full AR initialization.
- Host power delivery throttling: Low battery or aggressive OS power-saving modes disabling full-power USB enumeration.
Quick checks first
Before assuming your hardware is defective, run through these foundational checks to isolate common software and cabling traps:
- Bypass adapters and hubs: Plug the glasses directly into the host device. Multi-port dongles and generic adapters frequently lack the necessary DP Alt Mode pass-through capabilities.
- Test screen mirroring mode: Plug the glasses into an iPad, Steam Deck, or DP-compatible laptop without opening Nebula. If you get a desktop image, the display hardware works, pointing to an app or permission issue.
- Reboot the host device: Power cycle your phone or computer to reset its system USB controllers and clear temporary device cache files.
- Check for physical debris: Use a wooden toothpick or canned air to clear dust out of the temple's USB-C recess. Inspect the connector pins on your cable for discoloration or corrosion.
For broader troubleshooting advice across various display models, check our smart glasses troubleshooting portal.
When it's a real hardware fault
If you have verified that your host device supports DP Alt Mode, swapped the cable, and updated the firmware via a web browser, but the glasses still refuse to illuminate or send tracking data, you are likely dealing with a physical hardware defect.
Common hardware points of failure on the Xreal Air 2 include:
- Temple port receptacle damage: Mechanical strain on the angled USB-C connector can cause solder joints to snap off the internal PCB.
- Flex cable fatigue: Repeatedly opening and closing the flexible arms can fatigue the micro-ribbon cables running through the hinge to the display panels.
- Display bridge controller failure: The onboard processing chip responsible for translating DP Alt Mode video feeds to the dual Micro-OLED panels can fail due to power surges or thermal stress.
Soft resets vs board/panel work
Resolving connection issues through software resets, app reinstalls, and web-based firmware flashes is safe, effective, and non-destructive. These steps should always be completed prior to considering hardware intervention.
However, if the failure is traced to internal component breakdown—such as damaged temple connectors, broken ribbon cables, or burnt power control chips—DIY repair becomes extremely risky. Smart glasses rely on tightly integrated, micro-soldered logic boards packed alongside delicate optical engines. Opening the frame without specialized micro-soldering tools and optical alignment equipment risks permanently damaging the Micro-OLED optics and rendering the device unrepairable. If soft resets fail, review our hardware comparisons and teardowns in the reviews section to understand device architecture before seeking hardware remediation.
Next steps
- Confirm host device compatibility with DisplayPort Alt Mode.
- Swap out the USB-C cable for a known-good 10Gbps/4K video cable.
- Clear Nebula app cache, re-grant all permissions, and re-attempt pairing.
- Connect to a PC/Mac to flash firmware directly via Xreal's web installer tool.
- If all software steps fail, evaluate warranty status or professional micro-electronic diagnosis.
Next steps
Try the DIY guide if you're comfortable opening the device. Still stuck? Browse related problems for similar symptoms.

