MoreSpace turns an Android tablet or phone into an extra Linux display. The host daemon creates a virtual output, streams it to Android, and maps input back to the desktop so the device can behave like part of the workstation.
The hard part is not drawing a pretty preview. The hard part is making a display tool survive real Linux differences: Wayland and X11, GNOME and Plasma, wlroots compositors, Secure Boot, EVDI, udev permissions, GPU encoder behavior, USB quirks, Wi-Fi jitter, and devices with very different screen sizes.
Engineering priorities
- Responsiveness: protect latency by dropping stale work before encoding when the sender is backed up.
- Compatibility: detect the desktop stack and use the right output-management path for that session.
- Recoverability: verify host updates with SHA256 and keep a rollback path when a new build is wrong for a machine.
- Control: expose practical settings for resolution, refresh rate, scale, quality, latency threshold, codec, and display mode.
- Privacy: keep display and input traffic between your own Linux computer and Android device.
What it is good for
Terminals, documentation, chat, dashboards, logs, reference windows, monitoring, drawing, and temporary travel setups where carrying a second monitor is annoying but an Android device is already nearby.
What it does not hide
Linux graphics stacks vary. Some systems need EVDI or device permission setup, Secure Boot can block kernel modules, and mirror mode depends on desktop output-management support. MoreSpace exposes diagnostics and tuning commands because those details matter.
Support
If you hit a problem with setup, display detection, latency, input mapping, or a specific distro, contact [email protected] with the distro, desktop environment, Wayland or X11 session, kernel version, Android device model, and morespace info output.