Termux:X11
Termux:X11 is a native Android application that functions as a full X11 display server. It allows Linux GUI applications running inside Termux (or a proot-distro container) to render their windows directly on your Android screen, without any network protocol or pixel-streaming layer in between.
In the ADL stack, Termux:X11 is the recommended way to display your Linux desktop. It replaces older approaches like VNC with a faster, simpler, and more responsive solution.
How It Works
When you launch Termux:X11, the app creates a Unix domain socket that implements the X11 display protocol. Here is what happens under the hood:
- Termux:X11 starts and listens on display
:0via a shared socket in Termux's tmp directory. - Your Linux environment (Ubuntu under proot-distro) sets
DISPLAY=:0so GUI applications know where to draw. - GUI apps (XFCE, Firefox, file managers) send X11 rendering commands through the socket.
- Termux:X11 receives those commands and composites the output directly onto an Android
SurfaceView, bypassing any encoding or network layer.
Unlike VNC, Termux:X11 never encodes pixels into a network format. The X11 commands travel through a local Unix socket and are rendered directly by the Android GPU. This is why it feels like a native app rather than a remote desktop.
Because the rendering path stays entirely on-device and uses shared memory where possible, input latency is dramatically lower than any streaming-based approach.
Why Termux:X11 Over VNC
VNC was the original way to get a graphical desktop on Termux. It works, but it adds unnecessary overhead. Here is how the two compare:
| Feature | Termux:X11 | VNC (TigerVNC / x11vnc) |
|---|---|---|
| Rendering path | Direct X11 socket | Framebuffer encode/decode |
| Latency | Near-native (~5-10ms) | Noticeable (~30-80ms) |
| Resolution | Matches device display | Fixed at startup |
| Touch input | Native Android events | Simulated mouse via viewer |
| Hardware acceleration | Partial (virpipe possible) | None |
| Setup complexity | Install app + one package | Install server + viewer app |
| CPU overhead | Low | Moderate (encoding) |
On most Android devices, Termux:X11 uses 15-30% less CPU than an equivalent VNC session because it skips the framebuffer encoding step entirely. This translates to better battery life and cooler device temperatures during extended desktop sessions.
For a deeper look at VNC and when it might still be useful (such as remote access from another device), see VNC.
Installation
Termux:X11 requires two components: an Android app and a companion Termux package. Both must be installed for it to work.
Step 1: Install the Android App
Download the latest Termux:X11 APK from the GitHub releases page. Look for the file named app-universal-release.apk under the most recent release.
Open this URL in your Android browser to download the APK:
https://github.com/termux/termux-x11/releasesAfter downloading, tap the APK to install it. You may need to enable "Install from unknown sources" for your browser in Android Settings > Apps > Special access.
There is no official Termux:X11 listing on Google Play. If you find one, it is unofficial and potentially outdated or malicious. Always install from the GitHub releases page or from F-Droid.
Samsung Devices: Auto Blocker
Samsung devices may block the Termux:X11 APK by default. The installer may briefly display "Installing" and then close without installing the app. If Termux:X11 does not appear in Android's app list, temporarily disable Samsung Auto Blocker and allow the browser or file manager opening the APK to install unknown apps.
If the Termux:X11 Android app did not install, follow these steps:
- Open Samsung Settings.
- Go to Security and privacy.
- Open Auto Blocker.
- Temporarily turn Auto Blocker off.
- If Maximum restrictions is enabled, disable it temporarily.
- Go to Security and privacy > More security settings > Install unknown apps.
- Enable the permission for the app opening the APK, such as Samsung Internet, Chrome, or My Files.
- Reopen the APK from My Files or the browser and complete the installation.
- Confirm Termux:X11 appears in Android Settings > Apps.
- Verify from Termux:
pm list packages | grep termux.x11package:com.termux.x11
Re-enable Auto Blocker and remove the temporary unknown-app installation permission after Termux:X11 is installed. These protections should stay on for everyday use.
Step 2: Install the Termux Companion Package
Inside Termux, install the companion package that creates the display socket:
pkg install termux-x11-nightlyThe package downloads and installs in a few seconds. You will see standard apt output confirming the installation.
Step 3: Verify the Installation
Confirm that the termux-x11 command is available:
which termux-x11/data/data/com.termux/files/usr/bin/termux-x11
If you installed Termux from F-Droid, make sure you also installed Termux:X11 from a compatible source (GitHub releases or F-Droid). Mixing Play Store and F-Droid builds causes signature mismatches that prevent the shared socket from working.
Starting Termux:X11
The basic launch sequence involves starting the display server in Termux, then launching your desktop environment inside the Linux container.
Quick Start
From the Termux prompt (not inside Ubuntu):
termux-x11 :0 -ac &Then open the Termux:X11 app on your device. It will show a blank screen, waiting for a desktop to connect.
Next, start your desktop environment inside Ubuntu:
proot-distro login ubuntu --shared-tmp -- bash -c 'export DISPLAY=:0; dbus-launch --exit-with-session startxfce4'Switch to the Termux:X11 app, and your XFCE desktop should appear.
Create a shell script that combines these steps so you can launch your desktop with a single command. See the First Launch guide for a ready-made script.
Configuration
Termux:X11 exposes its settings through the Android app. Open the app, tap the three-dot menu or gear icon, and you will find the following options.
Display Settings
- Resolution mode: Choose between "exact" (uses your device's native resolution) or "scaled" (renders at a lower resolution and upscales). Exact mode looks sharper but uses more GPU resources.
- Display density (DPI): Controls how large UI elements appear. A value of 160-200 works well on phones; 120-160 suits tablets. Adjust this if text and icons appear too small or too large.
- Display orientation: Lock to landscape, portrait, or allow auto-rotation.
If your desktop UI elements look tiny, increase the DPI. If they look oversized and crowd the screen, decrease it. A good starting point is your device's actual DPI divided by 1.5.
Input Settings
- Touch input mode: Choose between "touchpad" (finger movement controls a cursor, like a laptop trackpad) or "direct touch" (tap where you want to click). Touchpad mode is more precise for desktop applications.
- Show additional keyboard: Enables a floating toolbar with keys like Ctrl, Alt, Tab, and Escape that are missing from Android keyboards.
- Capture external mouse/keyboard: When enabled, a connected USB or Bluetooth mouse and keyboard are captured directly by Termux:X11 rather than going through Android input handling.
Use touchpad mode if you are working with desktop applications that have small click targets. Use direct touch mode for casual browsing or when using touch-friendly applications.
Understanding the Display Protocol
Termux:X11 implements the X11 (X Window System) display protocol. X11 is the traditional display system used by Linux desktops for decades. It defines how applications draw windows, handle input events, and communicate with the display server.
Troubleshooting
The most frequent setup error is omitting --shared-tmp from the proot-distro login command. Without this flag, the Linux container cannot see the X11 socket that Termux:X11 created, and every GUI application will fail with a "cannot open display" error.