nyan Real / Spatial Wall User Manual
Put on the glasses and multiple displays appear in the space in front of you. As you turn your head, your viewpoint moves while the displays stay in place. This manual covers connection, basic setup, everyday use, and troubleshooting.
Individual settings explain themselves — hover any control in the app for its tooltip. This manual covers what comes before that: what each part is for, and in what order to use it.
Support information reflects implementation and test records through November 5, 2026. Screenshots show the September 10 development build on Windows with XREAL 1S connected and the master switch on. Available settings and controls vary by OS and glasses model.
About this app
Connect a supported pair of glasses over USB and your PC's displays are arranged in space as a wall, redrawn as you move your head. Physical and virtual displays can both join, and sound can come from where each window sits.
There are two halves.
- Display Wall — lays your displays out in space. The guiding idea is that your OS display arrangement becomes the wall: rearrange the screens the way you always do, in the OS, and the layout in space follows. You can also focus a single display, fold the wall like a folding screen, or change its distance.
- Audio Wall — finds the apps that are playing audio and mixes them so each one is heard from the direction of its window. No per-app setup.
The Spatial Wall desktop app contacts no server on the internet. It makes no automatic update check and sends no usage or crash data. Network communication is limited to these local paths:
- Phone remote and glasses bridge — devices on the same LAN
- XREAL One-family device link — direct communication with the glasses over TCP/IP through USB Ethernet
- Tab audio from the Chrome extension — loopback on the same PC (
127.0.0.1) - Local control from Stream Deck and similar tools — loopback on the same PC (
127.0.0.1)
The Android app's RDP client contacts an internet server only when you connect through an RD Gateway you specify. Direct RDP connections are limited to the LAN.
The phone's browser separately loads the official remote entry and checks its updates from the support website. After offline preparation, the remote can run without internet access. When you choose to download the Android app, the browser gets the signed APK directly from your registered PC on the LAN.
Support is not automated either. To report a problem you copy the details from "About" and paste them into a GitHub Issue by hand.
Supported glasses: XREAL (One Pro / 1 Pro+ / One / 1S / Air 2 Pro / Air 2 / Air), ROG XREAL R1, xbx a01 / a01+, RayNeo Air, Rokid (Max / Air), VITURE (Pro / One / One Lite), EPSON MOVERIO (BT-40 / BT-30C), Nreal Light and MAD Gaze Glow. What each model can do differs — see supported-glasses page for the details.
Where it runs: the same app runs on Windows, Linux and macOS.
| OS | Requirement |
|---|---|
| Windows | 64-bit Windows 10 version 2004 (build 19041) or later. Audio Wall capture of individual apps requires Windows 11 or later |
| Linux (GNOME) | GNOME 46 or later, Wayland session |
| Linux (Raspberry Pi) | Raspberry Pi OS trixie or later with labwc |
| macOS | macOS 14.4 or later (experimental; some features are missing) |
On any of them you also need a USB-C port that carries video (or an HDMI adapter) and the glasses themselves. The desktop app needs no internet connection. The phone remote and glasses bridge require the phone and PC to be on the same LAN. The appendix has a table of what differs per OS.
Installing and first run
Windows
Both the installer (nyan-real-spatial-wall-*-installer.exe) and the portable
ZIP work. The portable build just needs extracting; run spatial-wall.exe and
nothing is installed.
About code signing: the current builds are unsigned, so Windows SmartScreen may warn on first run. Choose "More info" then "Run anyway".
Linux (GNOME)
Install the .deb with apt install. Virtual displays go through GNOME's own
screen-sharing support (Mutter ScreenCast), so there is no driver to add.
After installing or updating, log out and back in to activate the bundled GNOME
Shell integration. While the app warns that this integration is unavailable,
some features are restricted, including focus and using only glasses plus
virtual displays without a normal monitor.
Linux (Raspberry Pi / labwc)
Install the Pi-specific .deb. Virtual displays use labwc's own support, and the
package adds the udev rules that let the app reach the glasses over USB.
macOS
Experimental. Use the current package supplied through your purchase or distribution channel. It is a Developer ID–signed app notarized by Apple, with separate packages for Apple silicon and Intel Macs.
From here on, using the app is the same everywhere.
The app shows a resident icon: in the notification area on Windows and Linux, and in the menu bar on macOS. Closing its window does not quit it. Use the icon to reopen the window or choose "Quit" from its menu.
What you see first is the operation panel across the top and the category list down the left.
- Enabled — the master switch. Turning it off stops glasses output, the sensor connection, and Audio Wall. Virtual displays behave as described under display combinations below.
- 3DoF (head tracking) — with it off, the wall normally stays locked to your view. Enable "Gimbal when 3DoF is off" in "Glasses" to follow larger head movements smoothly.
- Center — re-places the wall so the direction you are facing becomes forward.

You can go through the settings before connecting anything. Once the glasses are connected and ready for display, the status changes to "Running". The "3DoF" switch at the top shows whether head tracking is enabled.
Click a heading with a ▶ arrow to expand or collapse the advanced adjustments in Display Wall or Audio Wall, or the Glasses settings. These groups start collapsed and keep their open or closed state when you switch categories until you quit the app. Collapsing a group does not change its settings. Basic controls such as layout, screen curve, and audio enable and output remain visible, as do all Tap controls, Remote control, Power saving, and Video effects settings.
Connecting the glasses
Turn the master switch on and plug in over USB for automatic detection. Click the status indicator at the top (such as "Running") to check the detected model, IMU transport, and glasses display. The Glasses category contains display mode, SBS output, FoV, and related settings.
In the normal display path, the glasses need to be a separate extended display. A clone, or "second screen only", would hide the very monitors the wall is supposed to capture. By default the app makes them an extended display and tucks them into a corner of the desktop — a corner that touches the rest at a single point, so neither the cursor nor a dragged window can bleed onto the glasses. While cloned, the glasses and the mirrored monitor share one desktop source, so wall output stays off until Windows finishes giving the glasses their own extended source. On Windows, Spatial Wall can also reactivate a disabled supported-glasses target.
As a conditional feature, when a display mode's hardware EDID contains the
Microsoft HMD VSDB, Windows classifies the glasses as HeadMounted and removes
them from the desktop. Spatial Wall detects this state automatically, acquires
the display exclusively, and drives it directly. It cannot turn ordinary
glasses into an HMD through a setting. Extended-display layout, corner tucking,
the glasses cursor fence, and Fullscreen Exclusive do not apply while this HMD
path is active. See "Tested configurations and known limitations" in the
appendix for eligibility and tested hardware.
Once connected, check these three.
- Display mode — 2D or 3D SBS, and the refresh rate. "Restore saved display mode on connection" is off by default. Manual choices are remembered even while it is off, and the setting also restores normal modes. If the last remembered mode is HMD-capable, enable it only on a PC that enters that mode reliably. When XREAL One / One Pro / 1S is connected directly to the PC, both 2D and 3D SBS use 60 Hz modes while the master switch is on. Other refresh rates are unavailable during this time, and this startup mode selection takes priority over restoring a saved display mode.
- SBS output — "Auto" gets most modes right. Only half-SBS modes cannot be told apart by resolution, so switch those on by hand.
- Brightness and volume — use the operation panel at the top. Controls such as brightness and the glasses' amplifier volume appear when the model supports them. The amplifier inside the glasses and the PC's volume multiply, so if the PC is already at 100% and it is still quiet, raise the glasses' own volume.
First-time magnetic calibration
For supported glasses connected directly to a Mac or PC, you can turn on MAG yaw correction under Advanced. If the app asks you to recalibrate the gyroscope, set the glasses on a stable surface and keep them still until it finishes.
For magnetic calibration, hold the glasses near where you normally wear them, away from magnets and metal desks. Slowly turn them well to the left and right, point them up and down, then tilt them toward each shoulder. Repeat these movements. A level sweep alone gives the app too little information to calibrate all three axes. On XREAL 1 Pro+, hold the front of the frame so your fingers don't cover the wear sensor on the inside of the right temple. For models it can identify individually, the app saves the verified calibration and uses it again when you reconnect the same glasses. The MAG field in the status details tells you whether the app is using the model default or a calibration for these glasses. If it reports interference, magnetic correction pauses at that position or angle; the saved calibration stays available.
Tap controls (supported models)
Tap the temple twice or three times for play/pause, volume, centering and so on. If the response is unreliable, calibrate from the "Tap controls" category — the prompts appear inside the glasses.
Idle sleep
After a period without motion the app sleeps and blanks the screen; move to wake it. The timeout and sensitivity live under "Power saving". The idle-sleep switch, timeout, and sensitivity share one card. Frame skip and wall capture rate appear in a separate card and work independently of idle sleep.
Building the wall
The Display Wall category decides which displays join the wall and how they are arranged.

The diagram's two states
Normally the diagram is for looking at the wall. It shows only the displays and widgets that are on the wall, and clicking a tile focuses that screen (see below). Scroll to zoom, drag to pan while zoomed, and double-click empty space to fit the whole wall again.
To change the wall, press Arrange above the diagram. Adding or removing displays, rearranging them, and adding or setting up widgets and virtual displays all happen only in this state. Displays that are off the wall appear in the diagram only while arranging. Press Done arranging when finished. The split exists so that a stray click cannot drop a display off the wall.
Choosing displays
The diagram shows the OS's current display arrangement. Press Arrange, then click a tile to toggle whether that display belongs to the wall. Excluded tiles are dimmed, and the last remaining display cannot be removed. A virtual display created by Spatial Wall also cannot be removed from the wall while it is the main display; make another display main first. The glasses' own display never joins the wall.
Arranging them
Spatial Wall has no layout-mode selector: the OS display arrangement is the wall. Press Arrange, then drag a tile in the diagram to edit that arrangement. Apply writes the new positions to the OS; Cancel discards the edit. Arranging cannot be finished until one of them settles it. Changes made in the OS's display settings are reflected in the wall as well.
Turn on "Show display borders" to add a thin black separator between adjacent displays. There are no numeric controls for display gaps or outer padding.
Setting your viewpoint
"Center on display" appears directly below the diagram in "Display Wall", followed by screen curve and folding-screen mode. Open Advanced adjustments to change display borders, screen distance, size factor, or the live view pointer size.
- Center — makes the direction you are facing forward. Nominate a display and that display is what ends up in front of you.
- Focus — click a tile in the diagram to show only that screen. The diagram then shows that screen alone, with the current target at its top left, such as "All › 2 Display name"; press All to return to the whole wall. To show just a widget, enable Include in focus targets in its settings, then click its tile. Focusing needs two or more screens on the wall, or a widget that is a focus target. Shortcut keys and the phone remote switch it as well.
- Screen distance — how far the wall sits. Physical size is preserved, so closer looks bigger. Below 0.5 m tires the eyes, so treat that as a brief effect rather than a working distance.
- Screen size factor — adjusts the wall's physical size independently of its distance.
- Screen curve / Folding-screen mode — curves the wall towards you. In folding-screen mode the curve is taken at the seams between displays instead of as a smooth arc, so no single display is ever bent through its middle.
Widgets
Press Arrange on the diagram, then use "Add widget" to pin a small panel such as a clock to an edge of the wall. While arranging, click its tile to show or hide it, drag to move it, drag its lower-right corner to resize it, and right-click to open its settings.
Virtual displays
Short on physical monitors? Add virtual displays and the wall grows. Choose a resolution under "Virtual displays" in "Display Wall", then click "Add". You can also press Arrange on the diagram and right-click empty space to add one. While arranging, right-click a virtual-display tile to change its resolution or remove it.
While arranging, right-click either a physical (N) or virtual (V) display to choose an OS-supported resolution or display scale. Resolutions are sorted by width and height, largest first; scales are sorted smallest first. Choices depend on the display and OS. On macOS, scale selects the available standard/HiDPI modes for the pixel resolution. On labwc, enter a percentage because the compositor does not provide a scale list. Unavailable settings remain disabled with an explanation in the tooltip.
On Windows this needs a driver — nyan Real / Virtual Display Driver (recommended) or ParsecVDisplay. Drivers are not bundled, so install one separately. Linux and macOS use the OS's own support and need nothing installed.
Virtual displays you add exist only while this app runs. Their previous configuration is restored the next time you start it.
Adding or removing a virtual display changes only that one display. Removing one of several leaves the others running, and adding one after removing all of them resumes operation automatically. These changes do not put the whole set into idle mode.
What each display combination does
In the table below, G is a recognised glasses display, V is a virtual
display created by Spatial Wall, and N is any other normal display. Multiple
N or V displays follow the same rules.
| Connected displays | While the master is on | Main display | When the master is off or G disconnects |
|---|---|---|---|
| G only | There is no N or V to put on the wall, so wall output stays idle | G (not applicable on Pi) | No change |
| G + N | N is shown on the wall through G | N | Only the wall on G stops; N remains usable |
| G + V | Spatial Wall first proves that V is really visible through G | V becomes main automatically on Windows, GNOME, and macOS. Pi has no global main-display concept | With no N to escape to, V automatically goes idle for safety. Turning the master on restores it |
| G + N + V | N and V are shown on the same wall | Normally N. On Windows, GNOME, and macOS, right-click N or V in the Display Wall diagram to choose it | Windows, GNOME, and macOS return to N and keep V connected. Windows and macOS restore an explicit choice after the master is turned on again; on GNOME, choose it again. Pi makes V idle |
V is made main automatically only when there is exactly one G, at least one V, and no N, and a current V frame has actually been shown through G. It is not automatic when an N is present or multiple glasses displays are detected. Windows Direct HMD output puts G outside the desktop and therefore follows the HMD-output path instead of this table.
To choose V with "Make main display", the display must belong to the wall and be viewable through the glasses. It cannot be selected while the glasses are asleep or a single target is focused. On GNOME, the V choice lasts for the current app session; choose it again after master-off, glasses disconnection, or restarting the app. Idle sleep preserves the choice across wake. The Pi build has no OS-level main-display concept.
Going idle and resuming
Virtual displays are only visible through the glasses, so any window left on one goes missing when you take the glasses off. Go idle & recall windows disconnects the virtual displays temporarily, and the OS moves their visible windows to the remaining displays. Resume & restore windows restores the previous virtual-display configuration and the recalled windows. Going idle is unavailable while the wall is being shown, so turn the master off first. Resume also works without the glasses. Turning the master on with the glasses present resumes automatically.
Normally, if an N remains available, merely turning the master off or disconnecting the glasses does not make V idle. The invisible displays remain reachable through the diagram's live view. The exceptions are topologies with no safe escape, such as G + V, and the Pi build. The app may also make V idle while the computer sleeps to protect the display layout, then resume it after the physical displays have settled following wake.
The diagram's live view
Press ▶ Live view above the diagram, and every tile on the wall shows what that screen is showing now, with the mouse pointer. Without opening another window, you can work in windows on virtual displays you cannot otherwise see while the glasses are off. Click a tile to focus it and that one screen fills the diagram.
- The tile of the display this settings window is on gets no picture: you are already looking at that screen.
- It runs only while the diagram can be seen. Switching to another category, minimizing the window, or scrolling the diagram out of view stops it; coming back resumes it.
- The state is not saved. Every launch starts with it stopped.
- A still screen is not redrawn. The pointer is drawn separately, so it keeps moving smoothly.
- A shrunken screen shrinks its pointer, so it is drawn at least as large as "Live view pointer size" (Small, Medium, Large) under Advanced adjustments. When a zoomed-in tile shows it larger than that, it is drawn at true scale.
- While the wall is not shown in the glasses, changing the focus does not move the mouse pointer.
- Stopping the live view does not disconnect any virtual display. Use Go idle & recall windows / Resume & restore windows to disconnect and restore them.
The Raspberry Pi version has not been checked on a device yet.
Keeping the cursor out of trouble
On Windows and macOS, the glasses display and the virtual displays each have a "keep the cursor off" option. With it on, the cursor tunnels through to the display on the far side instead of getting stranded. The virtual-display option, "Keep the cursor out while not visible in the glasses", applies while a display is invisible, such as during sleep or with the glasses disconnected. When focusing one display, that visible virtual display remains mouse-operable; the other invisible virtual displays stay fenced. This also applies over the glasses bridge. While the diagram's live view is showing the virtual displays, the cursor is let in so you can work there. The glasses option is hidden while the glasses are an HMD outside the desktop, where no cursor can enter them. macOS asks for Input Monitoring permission the first time. GNOME and Raspberry Pi use different input controls, so this option is not shown there.
Tip: if the cursor occasionally jumps to the far edge of the adjacent display, turn off Windows Settings > System > Display > Multiple displays > "Make it easier to move the cursor between displays". It interferes with the fence.
Sound
Output
The "Audio output" selector in "Audio Wall" chooses the device that plays Spatial Wall's audio. "Auto: glasses" switches to the glasses' USB audio once per connection. Pick a specific device and the choice is remembered while that device is away, then re-applied when it returns.
Volume and mute are in the operation panel at the top. While the glasses bridge is the active output, these controls adjust the phone's media volume instead.
Audio Wall
Turn on spatial audio in the "Audio Wall" category and the app
finds whatever is playing, then mixes each app so it is heard from the direction
of its window. There is no per-app setup. To keep something out of the mix, add
its executable name to the exclusion list (for example discord.exe).
Direction is per app. An app spread across several screens collapses to a single direction.
Browser tabs
On Chrome or Edge 116 or later, install the "nyan Real Audio Wall connector" extension to place each tab's audio individually. It works on Windows, Linux and macOS. DRM media and cross-origin media without CORS permission keep playing normally in the browser and are not spatialized. Audio generated directly with Web Audio may not be captured either.
Controlling it
Cover the physical screens (Privacy mode)
On Mac and Windows, once the wall is visible in your glasses, turn on Privacy mode in the top operation panel. By default, the switch sits between 3DoF and View pointer. A dark cover hides the physical desktop from people nearby. Your glasses still show the desktop underneath, and clicks, drags, and scrolling reach the apps you see. Virtual displays and the glasses output stay uncovered. Mirrored displays that cannot be covered independently may prevent the mode from starting.
While focused on a display or widget, move the mouse to the top edge of a covered physical screen. The usual focus switcher appears in front of the cover. Choose All to return to the whole wall, or pick another display number or widget. The privacy cover stays on, and the switcher hides when you move the pointer away.
Use the shortcut printed on the cover to remove it. The default is Control + Shift + H on Mac or Ctrl + Alt + H on Windows. The cover stays in place when you change focus or unplug the glasses. Without glasses, the markers disappear and the displayed shortcut still restores the desktop. Quitting Spatial Wall or losing the exit shortcut removes the cover. Dim markers appear only with camera 6DoF enabled on a One-series device with Eye or on Nreal Light. Marker sites periodically go dark and the shortcut changes position to give lit pixels a rest. This mode is for physical screen privacy; what other apps record or share depends on their capture method.
With a One-series device and Eye using the built-in 6DoF tracker, Glasses → Glasses display & output → Steady the wall with privacy markers (experimental) lets you compare stabilization on and off while the same patterns remain visible. It starts off and uses a single covered physical monitor. If only one marker can be identified, it can steady sideways motion while still allowing you to lean toward it. In the 6DoF debug widget, circles are ordinary tracked features. Pink outlines show where the camera recognized a privacy marker; they turn mint when marker stabilization is active. Text also shows the recognition count and stabilization state. You can check marker recognition with stabilization turned off.
View pointer
On Windows, GNOME Wayland, Raspberry Pi (labwc) and macOS, directly connected glasses can move the OS cursor with your head direction. Enable "View pointer" in the top operation panel; it is off by default. The glasses must be connected and calibrated, with head tracking enabled. Gaze control starts after the mouse is idle and yields when mouse movement exceeds the tolerance. Adjust both values under "Glasses" > "Glasses display & output".
GNOME requires the bundled Shell extension. Log out and back in after installing or updating the package. On macOS, allow Spatial Wall in System Settings > Privacy & Security > Accessibility and Input Monitoring. Restart the app if macOS requests it. Without these permissions, gaze movement remains stopped. On Pi, the logged-in user needs read access to pointing devices such as the mouse. Small physical mouse movements still reach the OS and may briefly move the cursor during gaze control.
GNOME, Pi and macOS support cursor movement and left-button dragging inside wall desktops; widget clicks, menus and moving widgets are unsupported. When looking at a widget or empty space, the cursor stays at its last desktop position, and clicks still go to that position. Detecting mouse movement and held buttons may be delayed; the OS handles left, right and middle clicks normally. Holding the right or middle button freezes gaze movement. The glasses bridge also supports view pointer; cursor tracking, clicks and dragging were checked on Windows with SC-52D. Equivalent worn-glasses checks with GNOME/macOS hosts remain pending. Standalone Android RDP also provides the view-pointer button and sends pointer input to the PC whose screen you are looking at.
Shortcut keys ("Remote" > "Shortcut keys")
Centering, focus (next / previous / off), toggling 3DoF and the master switch can be bound to global hotkeys on Windows, GNOME, Raspberry Pi (labwc) and macOS. They keep working while another app has the foreground. On GNOME and macOS, the default master shortcut is Control+Shift+Esc.
Select a field and press the new combination, then click outside the field to apply it. Use the field’s clear button to disable a shortcut, or Reset to defaults to restore all shortcuts. Combinations reserved by the desktop or another app may not work. GNOME manages these as standard custom shortcuts while Spatial Wall is running; edit them in Spatial Wall. No logout is needed.
"Toggle view pointer" defaults to Ctrl+Alt+P on Windows, GNOME and Pi, and Control+Shift+P on macOS. This experimental feature supports glasses connected to the PC and shows an in-glasses on/off confirmation.
Phone remote ("Remote")
Turns a phone on the same network into a touchpad remote — a PC on wired Ethernet and a phone on Wi-Fi still reach each other, as long as it is the same network. Use Chrome / Chromium 156 or later on Android or desktop. iPhone and iPad browsers are not supported. Scan the PC's QR code to open the official remote entry, then select Register and connect. No app installation or certificate-fingerprint comparison is needed. Allow the browser's local-network access request when it appears. The page offers mouse control, text input, centering, gyro bias recalibration, focus, and volume. Use the keyboard button to compose text on the phone and send it to the PC's input field. In the remote's settings, "Display Wall" groups the layout diagram, center display, screen distance, size factor, and curve.
The remote's wall diagram works like the PC's. Tap a tile to focus that screen and Whole wall to go back. Press Arrange before rearranging screens or moving them on or off the wall. Press ▶ and every tile shows what that screen is showing now, with the mouse pointer. Pinch with two fingers to zoom, and drag with one finger to pan while zoomed. The pointer is drawn at least as large as the PC's "Live view pointer size".
The browser needs internet access to load the official entry for the first time and to check for its updates. After the entry reports that offline preparation is complete, it can open from its saved copy on subsequent visits without internet access. Clearing or losing browser data requires another online visit. Close all remote tabs and remote app windows to apply a pending update. If a remote left open during an update can no longer load the controls, close them all and reopen the remote while online. The controls themselves are loaded from your PC, so they match that PC's Spatial Wall version. Screen images, inputs and control state travel directly between the phone and PC on your LAN.
To put the remote on your Android home screen, open the official entry in Chrome while online. In the Chrome menu, choose Add to Home screen and then Install. The icon opens the remote in its own window. It uses the PCs already saved in that Chrome profile, so you can reconnect without scanning the QR again.
On Windows, the PC prefers a LAN with a default gateway when choosing the address for your phone. If several adapters are available, open Remote on the PC and use Address shown to phones to choose the adapter on your phone’s network. This updates both the QR code and the PC address shown for manual entry. Select Automatic to let the PC choose again.
When the QR cannot be scanned (say the glasses are your only display), use Pair with code on the PC. Open the official entry, enter the PC address and port shown in Spatial Wall, and enter its six-digit code. QR invitations and codes expire after 60 seconds and are single-use after successful registration.
A registered phone can control Spatial Wall. When using VR Bridge on Windows, it can also act as a left-hand or right-hand SteamVR controller. If you connect the glasses to your phone, turn on Allow glasses bridge on the PC before registration. The PC’s registered-device list shows which devices have bridge access. After registration, choose the PC under Saved PCs in the browser. Automatic reconnection does not require another code while the registration and browser permission remain valid.
To revoke one device, use its Forget button in the PC's registered-device list. To remove all registered devices, select Forget all devices under Remote on the PC. Revocation disconnects affected control, video and audio sessions and also removes access for devices that are currently offline. Each device must pair again, for example by scanning the QR code, before reconnecting. The QR code is for scanning; clicking it on the PC does not remove registrations. Removing a registration in the browser only clears that browser's copy; use the PC's device list to revoke access. Use a private browser profile on a device you control.
If Windows Firewall asks on first enable, allow Spatial Wall on your private network. The browser needs both TCP and UDP on the displayed port; the Android app uses TCP. Guest Wi-Fi or client isolation may prevent devices from connecting. Control, video, audio and app downloads use authenticated encryption. Keep QR invitations and codes private, and turn the remote off when it is not needed. If your app or pairing link predates device registration, install the current app and register it using the new QR code shown on the PC.
Glasses bridge ("Remote")
A way to connect the glasses to an Android phone instead of the PC. The app on the phone receives wall video from the PC, calculates head orientation using the glasses’ sensors, and sends that orientation to the PC. This is useful when you would rather not tie up a PC port or want to sit away from the machine. Windows, GNOME and macOS can send video and audio by treating the glasses as an Android external display (Presentation). On macOS this uses Screen Recording and Audio Recording permission. The appendix lists the tested configuration and known limitations. The external Video Input widget remains Windows-only.
To install or update the Android app, use an Android 11 or later phone with a 64-bit ARM processor. A regular Chrome tab works, as does the home screen remote.
- Open the browser remote and connect to your saved PC. On first use, scan the PC's QR code to register the browser.
- Select Android app at the top, then Get app from PC. Once the browser has verified the download, select Save APK. The APK comes directly from that PC's Spatial Wall installation.
- Open the saved
SpatialWall.apkfrom Downloads and confirm the installation or update in Android. If Google Play Protect recommends a scan, choosing Scan sends the app to Google for analysis. If Google Play Protect shows Harmful app blocked, dismiss the warning and stop. Leave Play Protect enabled.
Android app updates. When the app connects to a PC, it offers an update if the PC has a newer version or a different APK with the same version number. An older version on the PC does not trigger an offer. Tap the update notice in the app to get the APK from the connected PC and verify its product signature. If Android asks the first time, enable Allow from this source for Spatial Wall and return to the app. Tap Update on the Android confirmation screen. Your PC selection and registration carry over. For an app that predates in-app updates, use steps 1–3 above once. Apps that send head tracking data in the older format cannot connect to the updated glasses bridge. An in-place update with the same signing certificate preserves the app's saved PC registrations.
After the first installation, register the Android app separately from the browser. Return to the browser used for installation, select Android app, Hand off to app, then Open in Android app, and confirm the PC in Android. There is no need to scan the QR again. The app inherits the permissions granted when the browser was registered. If the prepared link expires, prepare another from the same page. You can also open the app from a fresh QR or enter the PC address and a fresh six-digit code in the app.
On a phone with the Android app installed, scanning the PC's QR code with the camera opens the app directly instead of the browser. Check the address and permissions shown, then tap Register and connect. The PC is listed under its own name (a name you set yourself is kept). If the browser opens instead, use Android app, Hand off to app as before.
If the app says “Glasses bridge not allowed by this PC”, open Remote on the PC, turn on Allow glasses bridge, then select Pair with code. In the phone app, select Pair for glasses bridge, enter the new six-digit code and tap Save and connect. This registers the app with bridge access. Repeating the handoff from the same browser gives the app that browser’s original permissions. If the PC still lists the old registration for the same app, you can forget the entry marked Glasses bridge not allowed.
Saved PC credentials are protected by Android Keystore and excluded from backups; normal reconnection does not ask for biometric authentication. Losing or erasing saved registrations requires registration again. RDP credentials have their separate authentication rules described below.
Once the phone app connects, "Remote" shows its state: the glasses' brightness, display mode and external display, plus whether the IMU and video channels are up. Model-specific settings behave the same over the bridge as they do when the glasses are plugged straight into the PC.
The glasses’ magnetic heading and detailed magnetometer readings stay on the phone. If your glasses have a supported magnetometer, calibrate it and turn on Use magnetic sensor in the compass widget to show magnetic north in both 2D and SBS wall modes. On the PC, the MAG row in the status details shows the correction status.
Connecting to RDP from Android
Choose "RDP" on the Android home screen, or open "RDP ▾" at the top of the remote. Register the PC's hostname, username and optional domain. For access outside the LAN, register an RD Gateway in the destination screen's settings and select it for the PC. Gateway credentials can be shared, match the PC's credentials, or be specific to that PC. The PC must accept RDP connections; the Spatial Wall desktop app is not required.
Destinations are encrypted on the phone. Unlocking and saving require biometrics or the device's screen-lock authentication. Saving passwords is optional. Closing the destination screen locks the saved data and keeps active sessions running. Use "Disconnect" at the top of the remote to disconnect. Saved data is excluded from backups and device migration; reinstalling or losing the encryption key requires registering it again. Resetting saved destinations deletes all entries and keys.
An untrusted certificate or a hostname mismatch stops the connection for review. Compare the SHA-256 fingerprint with the PC or Gateway through a trusted channel, then use "Trust and save" with device authentication to trust it for that destination. Certificate changes require another review; expired or malformed certificates are rejected. Direct connections are LAN-only. Browser sign-in and interactive MFA are unsupported.
Arrange multiple PCs and multiple monitors per connection in a wall of up to 15 screens. Per-screen resolution, focus, touchpad and keyboard input, view pointer, 3DoF, supported glasses' 6DoF, and audio playback are available. Clipboard, file and microphone forwarding are unsupported. On SC-52D, device authentication, encrypted storage, Gateway video/input/glasses audio, multiple PCs, and arranging three 4K screens have been checked. Long sessions and other phones and Gateway configurations remain under validation. Third-party licenses are available from the destination screen's settings.
Stream Deck ("Remote" > "Stream Deck")
Turning on "Accept control from this PC" opens a loopback-only (127.0.0.1) control port, so the Stream Deck plugin can trigger the same actions as the global hotkeys. It is unreachable from other machines, so there is no token.
Plugin 0.1.36 and later includes "Toggle view pointer" for supported configurations with glasses connected to the PC. Add it to a key to toggle the mode and see its current setting, including changes made through settings or hotkeys.
Start at login ("Advanced")
Windows, packaged Linux builds and the macOS app bundle can start with the desktop session. macOS may open System Settings > General > Login Items for approval. The control window's previous visible or hidden state is remembered. Close the window beforehand if you want only the resident icon at login; the icon can reopen it at any time.
Tuning the picture and the load
Smoothness ("Power saving")
- Wall capture rate — the capture ceiling. "Auto" is fine; drop to 45 Hz or Eco (30 Hz) to lighten the load.
- Frame skip — skips rendering while nothing moves, to save power. With headroom to spare, turning it off makes motion resume more smoothly.
Picture ("Video effects")
- Banding reduction (deband) — cuts the banding visible in dark gradients.
- Edge smoothing — settles the shimmer on text and thin lines.
Blur and flicker (Glasses)
- Automatic low persistence — XREAL Air and a01 families use the glasses' low-persistence brightness curve while 3DoF is enabled and return to the factory curve when it is disabled. No Duty adjustment is needed.
- Nreal Light — uses the glasses' normal drive in 2D and low-persistence drive in 3D. Adjust brightness with the glasses' buttons or the app; there is no manual Duty setting. The glasses bridge also supports Full-SBS at 60 Hz, including IPD parallax with 6DoF tracking. If switching back to SBS fails, wait briefly, then turn the master off and on again.
- Glasses Fullscreen Exclusive (Windows, "Advanced") — normally unnecessary. Try it only where scanout falls below the panel's nominal Hz (some NVIDIA hybrid setups). It belongs to the desktop path and is disabled while DisplayCore drives an HMD.
Appearance ("Appearance")
Display language defaults to "Auto (follow OS)". You can explicitly choose English or Japanese. After changing it, restart Spatial Wall when prompted to apply the new language.
The theme defaults to "Auto (follow OS)"; Light and Dark can be forced. With Ubuntu 24.04's stock Qt 6.4, Auto uses the light theme and does not follow live OS theme changes, while Light and Dark remain available manually.
"Show cursor direction compass" shows or hides the system tray compass that points toward the mouse cursor. It is on by default. Changes apply immediately and are remembered the next time Spatial Wall starts.

When something is wrong
The glasses are not detected
- Check that the USB cable carries both video and data. Charge-only cables cannot work.
- On XREAL One-family models, USB Ethernet / TCP/IP must be enabled on the glasses. 3DoF will not work without it (the app says so inside the glasses).
- On XREAL Air-family / xbx a01-family models, DP audio mode disconnects the USB sensor connection, so the app cannot acquire sensor data. Switch the glasses to USB audio.
Nothing shows in the glasses, or the desktop vanished
- In the normal desktop path, check that the display mode is not "Duplicate" or "Second screen only". Leaving "Force glasses to an extended display" on fixes this on every connection on Windows by identifying the supported glasses' physical target and repairing its disabled or cloned-source state.
- If the display stays dark after switching into an HMD-capable mode, turn off "Restore saved display mode on connection" and reconnect the cable. If the normal display still does not return, restart Windows. Do not force-quit the app while it is waiting to verify the return to the normal display path.
- See "Tested configurations and known limitations" in the appendix for the GPU-specific status of direct HMD output.
Stutter or dropped frames
- Lower "Wall capture rate".
- Turning frame skip off can smooth out the moment motion resumes.
- Only in the normal desktop path, if you suspect scanout has dropped to 60 Hz, try Fullscreen Exclusive.
No sound, or sound from the wrong direction
- Check that "Audio output" is pointed at the glasses.
- Audio Wall works per app; move a window to another display and its direction changes with it.
- When using Audio Wall, set the Windows default output to a device you do not use for listening. If both the default output and Spatial Wall output are audible, you will hear the sound twice.
The cursor gets lost
On Windows and macOS, turn on the "keep the cursor off" options. macOS asks for Input Monitoring permission the first time. On GNOME, Raspberry Pi, or when the cursor has already moved to an invisible display, use the diagram's live view to control it.
On macOS, Control + Shift + Esc turns the master switch off and removes
Spatial Wall from the glasses. If a virtual display managed by Spatial Wall is
the main display, the app first moves the main-display role to a visible physical
display.
Still stuck
"About" > "Copy support information" puts the product, version, OS, the GPU actually used and its driver version when available, connected glasses and runtime state, display layout, virtual-display backend and status, and support-approved effective settings on the clipboard. With nyan Real / Virtual Display Driver, it also includes the driver and app protocol versions. Connection tokens, output paths, display and audio-device identifiers, and other potentially private or secret settings are excluded. Paste it into "Copied support information" in the support form without editing it. Select the OS, enter the supported glasses model, then fill in "What happened" and "Steps to reproduce" separately. Before attaching logs or screenshots, check that they contain no private or secret information.
Appendix
What differs per OS
✅ Supported · 🟡 Conditional · — Unsupported
| Feature | Windows | GNOME | Raspberry Pi | macOS |
|---|---|---|---|---|
| Display Wall / Audio Wall | ✅ | ✅ | ✅ | ✅ |
| Virtual displays | ✅ separate driver required | ✅ built into the OS | ✅ built into the OS | ✅ built into the OS |
| Diagram live view | 🟡 checked with the glasses disconnected | 🟡 checked with the glasses disconnected | 🟡 not checked on a device | ✅ |
| Cursor fence | ✅ | — | — | ✅ requires Input Monitoring permission |
| View pointer | 🟡 PC direct and glasses bridge checked | 🟡 Shell integration required; direct tracking and left click checked; desktops only | 🟡 input-device read access required; basic direct tracking checked; desktops only | 🟡 Accessibility and Input Monitoring required; basic direct tracking checked; desktops only |
| Tap controls | ✅ | ✅ | ✅ | ✅ requires Accessibility permission |
| Phone remote | ✅ | ✅ | ✅ | ✅ requires Accessibility permission |
| Global hotkeys | ✅ | ✅ | ✅ | ✅ |
| Glasses bridge output | ✅ | ✅ video, widgets, 3DoF, and audio | — | 🟡 video, 3DoF, and audio verified on Intel Mac; Apple Silicon unverified |
| Privacy mode (cover physical screens) | ✅ | — | — | ✅ |
| Flat-wall screenshot | ✅ | ✅ | ✅ | — not needed: macOS screenshots do not freeze the glasses, so the Capture button is not shown |
The view pointer through Android from GNOME and macOS has not yet been checked while wearing the glasses.
macOS as a whole is experimental. Features that are unavailable on macOS are hidden from the UI. Direct connections to MOVERIO BT-40 on macOS support head tracking, magnetic correction, brightness adjustment, automatic brightness, 2D/Half-SBS switching, and convergence linking. BT-30C hardware operation on macOS remains unverified. Direct connections to MAD Gaze Glow are also supported: natural head tracking, brightness changes, 2D/Full-SBS switching, panel sleep/wake, and reconnecting from the app have been verified with GLOW Plus. Worn 3D viewing, physical unplug/replug, system sleep/wake, long sessions, and other Glow models remain unverified on macOS. Android supports head tracking, brightness adjustment and 3D display; BT-40 also supports automatic brightness and convergence linking. See the supported-glasses page for hardware verification by model.
GNOME glasses bridge output is included in standard builds from October 4, 2026. It supports physical and virtual displays, widget video, 3DoF, and Audio Wall. Keep a physical PC screen available for login and unlocking: the GNOME lock screen cannot be streamed to Android. The cursor is drawn separately from video updates, except with some capture methods that embed it in the video, where it moves at the video update rate. HEVC/HW and AVC/HW are preferred, with AVC/SW as fallback. Multiple displays can increase GPU/CPU load and latency. Hardware verification so far used GNOME 50.1 and SC-52D; other combinations remain unverified.
Tested configurations and known limitations
The following configuration-specific results cover records through October 29, 2026.
| Path | Tested configuration | Known limitations |
|---|---|---|
| macOS direct MOVERIO BT-40 connection | Apple A18 Pro / macOS 27.2 / BT-40. Natural head tracking with magnetic correction, dedicated HMD output at 1920×1080 and 60 Hz, automatic recovery after unplugging and reconnecting, and working settings and menus verified. Restoring magnetic calibration and resuming correction also verified. | When prompted, place the glasses on a desk and manually recalibrate the gyroscope (about 20–50 seconds). Worn 3D viewing, long sessions, repeated reconnections, and BT-30C remain unverified. |
| Windows direct HMD output | Windows 11 Pro (build 26200) / RTX 3060 / xbx a01+ with an HMD VSDB. Acquisition and scanout verified at 2D 90 Hz and 3D SBS 72 Hz. | Only display modes with a Microsoft HMD VSDB are eligible. A Radeon 780M system (driver 32.0.31035.1003) did not expose an HMD Target. Intel UHD (driver 32.0.101.7088) was not stable in its classification; acquisition and scanout remain unverified. |
| macOS glasses bridge | Intel Mac / macOS 15.7 / SC-52D / XREAL Air. Video from one physical and two virtual displays, 3DoF, audio, and automatic reconnection after restarting Spatial Wall were verified. | Apple Silicon is unverified. External Video Input is Windows-only. |
| Windows glasses bridge | Surface Duo / Android 12 / xbx a01+. Remote control, 1080p video, and reconnection verified. | A 4K display can remain black. Use focus on a 1080p display with this configuration. Head-tracking feel while wearing the glasses, audible playback, and long sessions remain unverified. |
| GNOME glasses bridge | GNOME 50.1 / Intel N100 / SC-52D / XREAL Air 2. HEVC video and head tracking for physical/virtual displays and widgets, AVC/HW fallback, native-resolution streaming, and sharper static text verified. | The GNOME lock screen cannot be streamed. Other GPUs/phones and long sessions remain unverified. |
| Windows glasses bridge | SC-52D / XREAL 1 Pro+. Worn checks covered 2D/SBS video and tracking, return to 2D, and Eye position tracking in 2D. | SBS combined with Eye and long-term stability remain unverified. |
Where settings live
Settings and logs are under %APPDATA%\nyan-real\ (the platform's user config
directory on Linux and macOS). You can open the log-storage folder from the app.
A failed save leaves the saved file intact. When settings change, the previous valid
settings are kept in settings.json.bak; saving identical contents does not rotate
the backup. If settings.json is missing or damaged at startup, the app recovers a
readable backup and shows a notice in the window and through the tray icon.
Recent changes may be missing.
If neither file can be read, the app starts with defaults and pauses saving to preserve the original files. Restore the files and restart, or use "Advanced" > "Reset settings to defaults" to resume saving. For a save failure, check disk space, folder permissions, and the log. Change a setting after fixing the cause to retry. Backups contain private settings; do not attach them directly to a support request. Phone registrations are kept separately in protected storage and are not restored from this backup. If registration storage fails, remote connections stop.
Resetting
"Advanced" > "Reset settings to defaults" returns app settings to their initial state. This cannot be undone. Registered phones remain registered; remove them from the phone remote's device list or use Forget all devices.
Checking the version
"About" shows the version and build time. Right-clicking spatial-wall.exe and
opening Properties > Details shows it too.
Licenses
"About" > "View the license agreement" opens the terms this app is licensed
under — the same text the installer shows before it copies anything. It also
sits next to the app as EULA.ja.txt / EULA.en.txt; the Japanese text is the
authoritative one.
"About" > "View third-party licenses" lists what is bundled and under which
license. Where a component requires its full license text to travel with the
app, that text is in licenses/ next to the app.