Skip to content

A rootless Android app that boots Alpine Linux: run containers (Podman/Docker/LXC) and GUI desktop apps.

docs: bring the guide in line with the current behavior

ExTvaabbffe5693a
diff --git a/CLAUDE.md b/CLAUDE.md
index 1aba883..4520333 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -161,7 +161,7 @@ Single-activity Compose app: `ui/navigation/NavGraph.kt` routes `setup → home
│ │ │ ├── hostbridge/ # guest->Android bridge (transport, server, dispatcher, notify)
│ │ │ │ └── HeadlessModeManager.kt # single source of truth for server (headless) mode
│ │ │ └── usb/ # UsbPassthroughManager
-│ │ ├── service/PodroidService.kt # foreground service; owns VM lifecycle, wakelock, notification
+│ │ ├── service/PodroidService.kt # foreground service; owns VM lifecycle, wakelock, notification; also VmControlReceiver (boot autostart + START_VM/STOP_VM automation intents)
│ │ ├── data/repository/ # Settings, PortForward, Update, Language, ContainerBackup, ContainerStats (all DataStore)
│ │ ├── di/ # Hilt module
│ │ ├── util/ # NetworkUtils, ShellQuote, HostMetrics + VmLoadSampler (Status screen), DeviceResourcePolicy (load-balance sizing)
diff --git a/README.md b/README.md
index 20cf2d9..92d5d85 100644
--- a/README.md
+++ b/README.md
@@ -51,6 +51,7 @@ docker run -d -p 8080:80 nginx
# expose that container to your phone and LAN, right from the VM shell
podroid-forward add 8080 8080 tcp # TCP or UDP, on both the QEMU and AVF backends
curl http://<phone-ip>:8080
+podroid-forward clean # remove every rule you added, in one go
# SSH in from your laptop (enable SSH in the setup wizard or Settings)
ssh root@<phone-ip> -p 9922 # password: podroid
diff --git a/docs/guide/backends.html b/docs/guide/backends.html
index 2736c16..dcab6a0 100644
--- a/docs/guide/backends.html
+++ b/docs/guide/backends.html
@@ -55,7 +55,7 @@
<p>Go to <strong>Settings &rarr; Advanced &rarr; Backend</strong>. The three options are:</p>
<ul>
<li><strong>Auto</strong> (default) - Podroid probes the device at startup and uses AVF if the feature, both permissions, and non-protected VM support are all present; otherwise it falls back to QEMU. This is the right choice for most users.</li>
- <li><strong>AVF (KVM)</strong> - always use AVF; the VM will fail to start if the prerequisites are not met.</li>
+ <li><strong>AVF (KVM)</strong> - always use AVF. On a device that cannot run it, the VM runs on QEMU instead, and the app states why: a notice on Home, a suffix on the Status screen, and a caption under the AVF chip in Settings.</li>
<li><strong>QEMU (TCG)</strong> - always use software emulation, even on a device that supports AVF.</li>
</ul>
@@ -95,7 +95,7 @@
<p>The two <code>pm grant</code> permissions <strong>persist across reboots and in-place app updates</strong>. You do not need to re-grant them after an OTA or a Podroid update installed over the existing app. However, they are <strong>lost on uninstall</strong>: if you uninstall and reinstall Podroid, run the two <code>pm grant</code> commands again before using AVF.</p>
<h2>How Auto-selection works</h2>
- <p>When the backend is set to Auto, Podroid checks four conditions at startup: (1) the <code>android.software.virtualization_framework</code> feature is present, (2) <code>MANAGE_VIRTUAL_MACHINE</code> is granted, (3) <code>USE_CUSTOM_VIRTUAL_MACHINE</code> is granted, and (4) the device advertises support for <strong>non-protected VMs</strong>. All four must pass. If any fails, Podroid silently falls back to QEMU - no error, the VM just starts with software emulation.</p>
+ <p>When the backend is set to Auto, Podroid checks four conditions at startup: (1) the <code>android.software.virtualization_framework</code> feature is present, (2) <code>MANAGE_VIRTUAL_MACHINE</code> is granted, (3) <code>USE_CUSTOM_VIRTUAL_MACHINE</code> is granted, and (4) the device advertises support for <strong>non-protected VMs</strong>. All four must pass. If any fails, Podroid falls back to QEMU and the VM starts with software emulation - announced in the same places as a forced-AVF fallback: a Home notice, a Status suffix, and a caption under the AVF chip in Settings.</p>
<p>Condition (4) is the non-obvious one. pKVM can operate in two modes: <em>protected</em> (guest memory is encrypted and the host cannot inspect it) and <em>non-protected</em>. Podroid's guest image is a standard Alpine Linux squashfs - it does not meet the signing and measurement requirements for protected VMs. A device that only advertises protected VM support cannot run Podroid's image under AVF, so Auto falls back to QEMU on such devices.</p>
@@ -133,7 +133,7 @@
<tr>
<td>Port forwarding protocols</td>
<td>TCP and UDP</td>
- <td>TCP only (UDP rules are silently ignored)</td>
+ <td>TCP and UDP</td>
</tr>
<tr>
<td>vCPU count</td>
diff --git a/docs/guide/how-it-works.html b/docs/guide/how-it-works.html
index ab433c5..b187d25 100644
--- a/docs/guide/how-it-works.html
+++ b/docs/guide/how-it-works.html
@@ -78,12 +78,12 @@
<p>OpenRC is PID 1 inside the guest. Several app-specific services on the squashfs handle bring-up; the three that drive the boot log are:</p>
<ul>
<li><strong>podroid-bootstrap:</strong> kernel modules, cgroup v2, ZRAM swap, devpts/shm/mqueue mounts, sysctl, hostname.</li>
- <li><strong>podroid-network:</strong> brings up eth0, assigns 10.0.2.15/24, sets the default route and /etc/resolv.conf (SLIRP provides NAT).</li>
+ <li><strong>podroid-network:</strong> brings up eth0, assigns 10.0.2.15/24, sets the default route and /etc/resolv.conf (SLIRP provides NAT). DNS goes to the device's own resolver first (passed in via <code>podroid.dns=</code> on the kernel command line), then 8.8.8.8 and 1.1.1.1 - SLIRP's own 10.0.2.3 forwarder is dead on Android, which has no host /etc/resolv.conf for it to read.</li>
<li><strong>podroid-ready:</strong> emits the "Starting SSH...", "Almost ready...", and "Ready!" markers that the app tracks to update the notification and unlock the terminal.</li>
</ul>
<h2>Guest-to-Android bridge</h2>
- <p>A small daemon, <code>podroid-hostd</code>, lets processes inside the VM reach back to Android. It listens on a guest-local Unix socket and relays one-line requests to the app over the same control transport the VM already uses - a virtio-console port on QEMU, vsock on AVF. Two CLIs are wired to it: <code>podroid-notify</code> posts an Android notification, and <code>podroid-forward</code> creates or removes port-forward rules without leaving the shell. The app posts the notification or writes the rule on the host side. See <a href="networking.html">Networking &amp; ports</a> for usage.</p>
+ <p>A small daemon, <code>podroid-hostd</code>, lets processes inside the VM reach back to Android. It listens on a guest-local Unix socket and relays one-line requests to the app over the same control transport the VM already uses - a virtio-console port on QEMU, vsock on AVF. Two CLIs are wired to it: <code>podroid-notify</code> posts an Android notification, and <code>podroid-forward</code> creates, removes, or (with <code>clean</code>) wipes all user port-forward rules without leaving the shell. The app posts the notification or writes the rule on the host side. See <a href="networking.html">Networking &amp; ports</a> for usage.</p>
<h2>Boot stages</h2>
<p>The app watches the VM's serial console and updates the persistent notification as each stage marker appears. You can follow along in real time during the first boot, where host-key generation adds a visible pause between "Starting SSH..." and the next stage.</p>
@@ -110,7 +110,7 @@
<tbody>
<tr>
<td>Linux 7.1.5 kernel</td>
- <td>Custom-built arm64 guest kernel with overlayfs, cgroups v2, netfilter, FUSE, and VETH built in</td>
+ <td>Custom-built arm64 guest kernel with overlayfs, cgroups v2, netfilter, FUSE, VETH, an NFS v4 server and client, the LIO iSCSI target plus TCP initiator, and Android binder/binderfs built in</td>
</tr>
<tr>
<td>OpenRC (PID 1)</td>
@@ -130,7 +130,7 @@
</tr>
<tr>
<td>podroid-hostd</td>
- <td>Guest-to-Android bridge daemon; relays <code>podroid-notify</code> and <code>podroid-forward</code> requests to the app over a virtio-console port (QEMU) or vsock (AVF)</td>
+ <td>Guest-to-Android bridge daemon; relays <code>podroid-notify</code> and <code>podroid-forward</code> (add / remove / list / clean) requests to the app over a virtio-console port (QEMU) or vsock (AVF)</td>
</tr>
<tr>
<td>Foreground service</td>
diff --git a/docs/guide/networking.html b/docs/guide/networking.html
index 15721dd..9fddb71 100644
--- a/docs/guide/networking.html
+++ b/docs/guide/networking.html
@@ -61,12 +61,12 @@
<tbody>
<tr><td><code>10.0.2.15/24</code></td><td>Guest IP (eth0)</td></tr>
<tr><td><code>10.0.2.2</code></td><td>Default gateway (SLIRP host)</td></tr>
- <tr><td><code>10.0.2.3</code></td><td>Built-in DNS resolver</td></tr>
+ <tr><td><code>10.0.2.3</code></td><td>SLIRP's DNS forwarder - dead on Android, which has no host <code>/etc/resolv.conf</code> for it to read</td></tr>
<tr><td><code>8.8.8.8</code>, <code>1.1.1.1</code></td><td>Fallback DNS (in <code>/etc/resolv.conf</code>)</td></tr>
</tbody>
</table>
- <p>IPv6 is disabled on the QEMU netdev (<code>ipv6=off</code>). Outbound TCP and UDP both work. The <code>podroid-network</code> OpenRC service brings up eth0 with these addresses at boot.</p>
+ <p>IPv6 is disabled on the QEMU netdev (<code>ipv6=off</code>). Outbound TCP and UDP both work. The <code>podroid-network</code> OpenRC service brings up eth0 with these addresses at boot. Because SLIRP's own forwarder is dead, the guest's <code>/etc/resolv.conf</code> lists the device's own resolver first (passed to the guest via <code>podroid.dns=</code> on the kernel command line), then <code>8.8.8.8</code> and <code>1.1.1.1</code>. In airplane mode there is no device resolver, so the list falls back to <code>10.0.2.3</code>, <code>8.8.8.8</code>, <code>1.1.1.1</code>.</p>
<div class="callout note">
<span class="label">AVF backend</span>
@@ -108,7 +108,7 @@
<p>The SSH forward is conditional: if you turn SSH off in Settings, the 9922&rarr;22 rule is not added and dropbear does not start inside the guest. The VNC and PulseAudio forwards are unconditional because the in-app X11 viewer depends on them.</p>
<h2>Adding your own rules</h2>
- <p>Open <strong>Settings &rarr; Port forwards &rarr; Add</strong>. Enter a host port (on the Android device), a VM port (inside the guest), and pick TCP, UDP, or Both. On the QEMU backend rules apply live via the QMP protocol - no VM restart is needed. Rules are persisted across reboots.</p>
+ <p>Open <strong>Settings &rarr; Port forwards &rarr; Add</strong>. Enter a host port (on the Android device), a VM port (inside the guest), and pick TCP, UDP, or Both. On the QEMU backend rules apply live via the QMP protocol - no VM restart is needed. Rules are persisted across reboots. Next to Add there is also a <strong>Clean all</strong> button that removes every user rule at once, behind a confirmation dialog; the app's own SSH, display, and audio forwards are not affected.</p>
<p>A typical setup for a container service listening on guest port 8080:</p>
@@ -126,7 +126,7 @@ curl http://&lt;phone-ip&gt;:8080</code></pre>
<h3>Limits on the rule list</h3>
<p>A host port that something else on the phone is already using cannot be forwarded. That rule alone fails and is retried whenever the list changes; the VM keeps running and every other rule is unaffected. Android hands out ports from 32768 upwards to ordinary apps, so a rule in that range is the most likely one to collide - pick host ports below it when you have the choice.</p>
- <p>Up to 128 rules can be saved. The limit exists because each rule is a listening socket and a row in Settings, and because a shell loop can otherwise add thousands of them in a second. <code>podroid-forward</code> reports an error rather than reporting success once the list is full.</p>
+ <p>Up to 2048 rules can be saved. The limit exists because each rule is a listening socket and a row in Settings, and because a shell loop can otherwise add thousands of them in a second. <code>podroid-forward</code> reports an error rather than reporting success once the list is full.</p>
<h2>Talking back to Android from the guest</h2>
<p>Several command-line tools ship inside the VM so scripts and shell sessions can reach the Android side directly, without the in-app UI. They all work on the QEMU and AVF backends.</p>
@@ -139,8 +139,10 @@ podroid-forward 8888 80
<span class="c"># list current rules</span>
podroid-forward list
<span class="c"># drop a rule</span>
-podroid-forward remove 8888 tcp</code></pre>
- <p>Rules created this way are identical to ones added in Settings: they apply live, persist across reboots, and appear in the Settings list. Both TCP and UDP work on either backend.</p>
+podroid-forward remove 8888 tcp
+<span class="c"># drop every user rule at once (replies "removed N")</span>
+podroid-forward clean</code></pre>
+ <p>Rules created this way are identical to ones added in Settings: they apply live, persist across reboots, and appear in the Settings list. Both TCP and UDP work on either backend. <code>clean</code> removes only user rules - the app's own SSH, display, and audio forwards are untouched.</p>
<h3><code>podroid-notify</code> - post an Android notification</h3>
<pre><code><span class="c"># simplest form</span>
@@ -260,13 +262,15 @@ pasv_addr_resolve=NO
<p>Modern clients use the extended passive command, which returns only a port and reuses the address they are already connected to, so they work whether or not <code>pasv_address</code> is set. Windows Explorer uses the older command, which returns an address as well, and the guest fills that in with its internal address <code>10.0.2.15</code>. The client then tries to open the data connection to an address that does not exist on your network and hangs, usually after the directory listing appears to start. Setting <code>pasv_address</code> to the phone's own address is what fixes it. The phone's address changes when it moves between networks, so it has to be updated to match; the <strong>Status</strong> screen lists every address the phone currently has.</p>
</div>
+ <h3>NFS and iSCSI</h3>
+ <p>The kernel ships an NFSv4 server and client, so the guest can serve NFS - with one constraint. The export must live on an ext4-backed path such as <code>/mnt/persist</code> and be exported with <code>fsid=0</code>, because the overlay root cannot produce NFS filehandles by design. Note that Windows' own NFS client speaks version 3, which also needs the portmapper on port 111 - privileged, so Windows still cannot reach it. The kernel also ships the LIO iSCSI target (<code>targetcli</code>, with fileio and iblock backstores) and the TCP initiator.</p>
+
<h3>What cannot work</h3>
<p>These are not missing features, they are consequences of running as an ordinary app on a stock phone:</p>
<ul>
<li><strong>SMB or Windows file sharing from the guest.</strong> Windows only speaks SMB on port 445, and an unprivileged app cannot bind any port below 1024. A Samba server inside the guest will start, but no Windows machine can be pointed at it on a different port.</li>
<li><strong>Mounting a Windows share inside the guest.</strong> The kernel is built without <code>cifs</code>, so there is no client side either.</li>
- <li><strong>Running an NFS server in the guest.</strong> The kernel is built without NFS server support, so <code>rpc.nfsd</code> cannot start: it fails on a missing <code>/proc/fs/nfsd</code>. Mounting a <em>remote</em> NFS export from inside the guest does work, since the client side is built in. Note that Windows' own NFS client speaks version 3, which also needs the portmapper on port 111, so even an NFS server would not reach it.</li>
<li><strong>Serving DNS or PXE to other machines on the network.</strong> DNS is port 53, DHCP is 67 and 68, TFTP is 69: all privileged, and Android owns DHCP on a tethered network regardless.</li>
</ul>
diff --git a/docs/guide/packages.html b/docs/guide/packages.html
index 3102dc9..a360652 100644
--- a/docs/guide/packages.html
+++ b/docs/guide/packages.html
@@ -150,11 +150,11 @@
<tbody>
<tr>
<td><code>podroid-bootstrap</code></td>
- <td>First service to run. Sets the system clock (AVF path), enables cgroup v2, loads kernel modules, mounts devpts/shm/mqueue, configures ZRAM swap, sets sysctl tunables, sets the hostname, and bind-mounts the persistent ext4 storage onto the Podman/Docker/LXC data directories.</td>
+ <td>First service to run. Sets the system clock (AVF path), enables cgroup v2, loads kernel modules, mounts devpts/shm/mqueue and configfs (<code>/sys/kernel/config</code>, needed by targetcli/LIO), configures ZRAM swap, sets sysctl tunables, sets the hostname, and bind-mounts the persistent ext4 storage onto the Podman/Docker/LXC data directories.</td>
</tr>
<tr>
<td><code>podroid-network</code></td>
- <td>Brings up eth0 (10.0.2.15/24 on QEMU, DHCP on AVF), adds the default route, and writes <code>/etc/resolv.conf</code>.</td>
+ <td>Brings up eth0 (10.0.2.15/24 on QEMU, DHCP on AVF), adds the default route, and writes <code>/etc/resolv.conf</code> with the device's own resolver first, then <code>8.8.8.8</code> / <code>1.1.1.1</code>.</td>
</tr>
<tr>
<td><code>podroid-resize</code></td>
@@ -170,7 +170,7 @@
</tr>
<tr>
<td><code>podroid-hostd</code></td>
- <td>The guest-to-Android bridge daemon (both backends). Listens on a guest-local Unix socket and relays requests from the <code>podroid-notify</code> and <code>podroid-forward</code> CLIs to the Android app over its control transport (a virtio-console port on QEMU, vsock on AVF), which posts the notification or writes the port-forward rule. See <a href="networking.html">Networking &amp; ports</a>.</td>
+ <td>The guest-to-Android bridge daemon (both backends). Listens on a guest-local Unix socket and relays requests from the <code>podroid-notify</code>, <code>podroid-forward</code>, <code>podroid-open</code>, <code>podroid-power</code>, and <code>podroid-server</code> CLIs to the Android app over its control transport (a virtio-console port on QEMU, vsock on AVF), which posts the notification or writes the port-forward rule. See <a href="networking.html">Networking &amp; ports</a>.</td>
</tr>
<tr>
<td><code>podroid-ready</code></td>
@@ -197,7 +197,7 @@
<div class="pagenav">
<a class="prev" href="networking.html"><span class="dir">Previous</span>&larr; Networking &amp; ports</a>
- <a class="next" href="desktop.html"><span class="dir">Next</span>Desktops &amp; X11 viewer &rarr;</a>
+ <a class="next" href="migrations.html"><span class="dir">Next</span>Updates &amp; migrations &rarr;</a>
</div>
<p class="docfoot">Podroid is free software (GPL). Docs for v1.2.7. Found something inaccurate? <a href="https://github.com/ExTV/Podroid/issues">Open an issue</a>.</p>
</main>
diff --git a/docs/guide/settings.html b/docs/guide/settings.html
index 8366776..e351ca9 100644
--- a/docs/guide/settings.html
+++ b/docs/guide/settings.html
@@ -114,8 +114,8 @@
</tr>
<tr>
<td>RAM</td>
- <td>512 MB / 1 GB / 2 GB / 4 GB</td>
- <td>Memory allocated to the VM. Requires a VM restart. Locked while running.</td>
+ <td>512 MB to 16 GB</td>
+ <td>Memory allocated to the VM. The options run from 512 MB up to 16 GB, filtered to what the device can spare (total memory minus about 3 GB of headroom); small phones always keep at least 512 MB / 1 GB / 2 GB. Requires a VM restart. Locked while running.</td>
</tr>
<tr>
<td>CPU cores</td>
@@ -127,6 +127,11 @@
<td>Set at first-run setup</td>
<td>The size of the persistent overlay image (<code>storage.img</code>). Set during setup; changing it requires a full VM reset.</td>
</tr>
+ <tr>
+ <td>Start VM on boot</td>
+ <td>Toggle</td>
+ <td>Off by default. When on, the VM boots after the phone starts - on a PIN-locked phone, after the first unlock. Automation apps can also start and stop the VM with the intent actions <code>com.excp.podroid.action.START_VM</code> (activity intent) and <code>com.excp.podroid.action.STOP_VM</code> (broadcast).</td>
+ </tr>
</tbody>
</table>
@@ -147,8 +152,8 @@
</tr>
<tr>
<td>Port forwards</td>
- <td>Add / Remove</td>
- <td>Add TCP, UDP, or both forwarding rules. Changes apply live via QMP without a VM restart. Can also be managed from inside the VM with <code>podroid-forward</code> (see <a href="networking.html">Networking</a>). The rules the app manages itself - SSH, and the desktop's screen and audio channels - are listed above your own as read-only entries, so a port that is already taken is visible before you try to reuse it.</td>
+ <td>Add / Remove / Clean all</td>
+ <td>Add TCP, UDP, or both forwarding rules. Changes apply live via QMP without a VM restart. Clean all removes every user rule after a confirmation; the app-managed SSH, display, and audio rows are unaffected. Can also be managed from inside the VM with <code>podroid-forward</code> (see <a href="networking.html">Networking</a>). The rules the app manages itself - SSH, and the desktop's screen and audio channels - are listed above your own as read-only entries, so a port that is already taken is visible before you try to reuse it.</td>
</tr>
<tr>
<td>Bandwidth limit</td>
@@ -181,7 +186,7 @@
<tr>
<td>Backend</td>
<td>Auto / AVF (KVM) / QEMU (TCG)</td>
- <td>Auto picks AVF when the device supports it, otherwise QEMU. Requires a VM restart. See the <a href="backends.html">Backends</a> page for details.</td>
+ <td>Auto picks AVF when the device supports it, otherwise QEMU. Forcing AVF on a device that cannot run it falls back to QEMU, and the app says so: the AVF chip gains a caption with the reason, the Home screen shows a notice, and Status appends "AVF unavailable, running QEMU". Requires a VM restart. See the <a href="backends.html">Backends</a> page for details.</td>
</tr>
<tr>
<td>Extra QEMU args</td>
diff --git a/docs/guide/use-cases.html b/docs/guide/use-cases.html
index a9ac83f..9fc37dd 100644
--- a/docs/guide/use-cases.html
+++ b/docs/guide/use-cases.html
@@ -107,7 +107,7 @@
<p>It uses a <code>podroid-backup</code> helper when one is present in the guest, and falls back to plain <code>podman save</code> / <code>podman export</code> otherwise. Backups are written inside the guest to <code>/mnt/downloads/Podroid/backups</code>. With <a href="settings.html">Downloads folder sharing</a> enabled, that path appears on the phone under <code>Download/Podroid/backups</code>; with sharing off, backups stay inside the VM at <code>/var/backups/podroid</code>.</p>
<h2>Checking VM and phone status</h2>
- <p>The <strong>Status</strong> screen (the home screen's <strong>Status</strong> button, or the monitor icon in the header) gives a single view of both sides of the system: phone RAM, storage, CPU cores, and load average (when readable) alongside the VM's status, uptime, active backend (QEMU or AVF), and the phone's IP.</p>
+ <p>The <strong>Status</strong> screen (the home screen's <strong>Status</strong> button, or the monitor icon in the header) gives a single view of both sides of the system: phone RAM, storage, CPU cores, and load average (when readable) alongside the VM's status, uptime, active backend (QEMU or AVF), and the phone's IP. The backend shown is the one actually running: when a forced AVF selection falls back to QEMU, Status says so explicitly ("AVF unavailable, running QEMU").</p>
<p>It also shows a VM CPU-load graph, available on the QEMU backend only - on AVF the screen shows a note that the graph is QEMU-only - plus the VM's allocated RAM, CPU cores, disk-image usage, and bandwidth limit.</p>
<h2>Local Linux development environment</h2>
@@ -174,13 +174,12 @@
<li><strong>Wayland desktops</strong> - GNOME Wayland, Plasma Wayland, sway, and Hyprland do not render in the X11 viewer. Use XFCE or another X11 session instead.</li>
<li><strong>Heavy compilation on TCG</strong> - building LLVM, the Linux kernel, or large Rust crates inside the VM is feasible but very slow (hours, not minutes). Cross-compile on a real machine and copy the result over SSH.</li>
<li><strong>x86 Docker images</strong> - pulling an <code>linux/amd64</code> image runs it under double emulation (QEMU TCG emulating ARM64 guest, which then runs QEMU user-mode emulating x86). Expect 50-100x slowdown. Always prefer <code>linux/arm64</code> images.</li>
- <li><strong>UDP port forwarding on AVF</strong> - UDP rules are silently ignored on the AVF backend; switch to QEMU if you need UDP (e.g. a game server or DNS resolver serving LAN clients).</li>
<li><strong>A full desktop environment at 512 MB RAM</strong> - XFCE with a browser open will page heavily into ZRAM swap at 512 MB. Set RAM to 1 GB or more in Settings if you plan to run a desktop regularly.</li>
</ul>
<div class="callout tip">
<span class="label">Getting better performance</span>
- <p>If TCG is too slow for your workload, the most impactful step is switching to the <a href="backends.html">AVF backend</a> on a Pixel 8 or later - it provides near-native CPU speed. Bumping RAM above 1 GB also helps containers and desktops avoid swap pressure. The <a href="performance.html">Performance &amp; why it's slow</a> page covers every tuning option in detail. For hard limits such as Wayland or UDP-on-AVF, see <a href="limitations.html">Limitations &amp; troubleshooting</a>.</p>
+ <p>If TCG is too slow for your workload, the most impactful step is switching to the <a href="backends.html">AVF backend</a> on a Pixel 8 or later - it provides near-native CPU speed. Bumping RAM above 1 GB also helps containers and desktops avoid swap pressure. The <a href="performance.html">Performance &amp; why it's slow</a> page covers every tuning option in detail. For hard limits such as Wayland, see <a href="limitations.html">Limitations &amp; troubleshooting</a>.</p>
</div>
<div class="pagenav">
diff --git a/docs/index.html b/docs/index.html
index 5fd0e6a..5afd649 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -802,7 +802,7 @@
</tr>
<tr>
<td class="row-label">Configurable RAM / CPUs</td>
- <td class="col-podroid"><span class="check">✓ 512MB–4GB, 1–8 cores</span></td>
+ <td class="col-podroid"><span class="check">✓ 512 MB–16 GB, 1–8 cores</span></td>
<td><span class="cross">✗</span></td>
<td><span class="partial">limited</span></td>
</tr>