Install the host
Download the host AppImage from the download page, make it executable if your file manager did not, and run ./<downloaded-file> install.
Setup and troubleshooting
Help
Start with the Linux host, connect Android over USB or Wi-Fi, then use the CLI to inspect and tune the session.
Open Android
Install MoreSpace from Google Play and keep the app open while connecting. The Android side receives the stream and sends input events back.
Prefer USB first
USB usually gives the most predictable latency. Grant the USB permission prompt to MoreSpace when Android asks.
Tune only if needed
Run morespace client preset first. Then adjust width, Hz, scale, quality, or latency threshold if your device needs a different balance.
First checks
- Run
morespace daemon statusto confirm the user service is installed and the daemon is running. - Run
morespace statusfor the current mode, resolution, refresh rate, scale, and connected device, andmorespace doctorfor a check of the system pieces MoreSpace needs. - For USB, confirm Android granted USB access to MoreSpace and the host can see the device.
- For Wi-Fi, keep both devices on the same network and set the remembered target with
morespace connect <IP>if automatic discovery is not enough. - Use
morespace update --checkbefore reporting an issue, thenmorespace updateif a newer host build is available.
If latency feels high
- Use USB before judging performance over Wi-Fi.
- Lower the virtual display width with
morespace client width <px>. - Lower refresh rate with
morespace client hz 60or below on weak hardware. - Move toward lower latency with
morespace client quality 1. - Keep the Android device charging; some devices throttle decoding or networking aggressively on battery.
If the display does not appear
- Check Secure Boot. DKMS-built EVDI modules may not load until signed or trusted.
- Confirm the virtual output appears in your desktop display settings after the daemon starts.
- On Plasma, give KScreen a moment to settle after the virtual output appears; MoreSpace also re-applies placement where needed.
- On GNOME, output activation depends on Mutter display configuration and the running session.
- On wlroots-style desktops, make sure the session exposes an output control path such as
wlr-randr.
Frequently asked questions
Which Linux desktops does MoreSpace support?
MoreSpace has explicit support paths for GNOME/Mutter, KDE Plasma/KWin, wlroots-style compositors (Sway, Hyprland), niri, COSMIC-style sessions, and X11 through xrandr.
Does MoreSpace work over Wi-Fi or only USB?
Both. USB gives the most predictable latency, and Wi-Fi streaming also works, with automatic IP exchange when the cable is disconnected.
Does MoreSpace support touch and stylus input?
Yes. MoreSpace maps multi-touch gestures and pressure-sensitive stylus input back to your Linux desktop applications.
How do I fix high latency?
Prefer USB over Wi-Fi, lower the virtual display width or refresh rate, and move toward lower-latency presets with morespace client quality 1. Keep the Android device charging.
The display does not appear on my desktop. What should I check?
Check Secure Boot, confirm the virtual output appears in your desktop display settings, and run morespace daemon status to see the detected display protocol and encoder. wlroots-style sessions need an output control path such as wlr-randr.
How do updates and rollback work?
morespace update downloads the newest AppImage, verifies its SHA256, and switches the current symlink. morespace rollback switches back to the previous build if the new one is a poor fit.
Desktop notes
MoreSpace has explicit paths for GNOME/Mutter, KDE Plasma/KWin, wlroots-style sessions, Sway, Hyprland, niri, COSMIC-style detection, and X11 through xrandr. Extend mode is the default. Mirror mode depends on whether the active desktop exposes the output management MoreSpace needs.
What to send with a bug report
Contact Helpdesk
Need direct assistance with your display setup, EVDI configuration, or licensing? Reach out below and our support team will get back to you promptly.