Waydroid Android 16: Community Images, Setup and Limits

Official vs community images

What the July 2026 Android 16 build brings

According to its release notes, the WayDroid-ATV build from 17 July 2026 is based on LineageOS 23.2 (Android 16 QPR2). It highlights:

• Full Waydroid integration when used with Waydroid 1.6.3 or later
• Working network without the earlier workaround
• Booting fixes for AMD GPUs and Intel discrete GPUs
• Two-finger touchpad gestures mapped to screen swipes, and a dynamically resizable UI window

Important: that release has no ARM64 images. The notes point ARM64 users to the earlier March 2026 build. The author also asks people not to mirror the builds, so download them only from the original repository.

Before you switch: back up

Changing Android versions is effectively a fresh install. Back up anything important, then do a clean reset as the release notes recommend:

waydroid session stop
rm -rf ~/.local/share/waydroid
sudo rm -rf /var/lib/waydroid/overlay*

This deletes your Android apps and data, so only run it once you've saved what you need.

Method 1: Install through Waydroid's OTA channels

Make sure you're on Waydroid 1.6.3 or newer (waydroid --version), then point init at the community channels:

sudo waydroid init -f \
  -c https://waydroid-atv.github.io/ota/a16-qpr2/system \
  -v https://waydroid-atv.github.io/ota/a16-qpr2/vendor \
  -r lineage \
  -s GAPPS

Afterwards, sudo waydroid upgrade follows that channel for updates. Check the project's OTA page for the current URLs before running these.

Method 2: Install the images manually

Download the system and vendor archives from the WayDroid-ATV releases, extract system.img and vendor.img, then:

sudo mkdir -p /etc/waydroid-extra/images/
sudo cp system.img /etc/waydroid-extra/images/system.img
sudo cp vendor.img /etc/waydroid-extra/images/vendor.img
sudo waydroid init -f

Known trade-offs

• Unofficial: the Waydroid team doesn't support these images, so report problems to the image's own repository.
• Regressions happen: newer Android brings new behaviour, and some apps or features may break between builds.
• Hardware differences: GPU-specific fixes land build by build, so read each release's known issues.
• Going back: return to Android 13 by re-initialising with the official images (sudo waydroid init -f) after another clean reset.

Who should (and shouldn't) try it

Try the Android 16 builds if an app you rely on now requires Android 14 or newer, if you develop apps and need to test newer APIs, or if you simply enjoy running the latest Android. Stay on the official Android 13 images if Waydroid is part of your daily work, if you use ARM64 hardware and need the newest builds, or if you'd rather not troubleshoot after updates.

Checking which Android you're running

After initialising, confirm the version from the host:

sudo waydroid shell
getprop ro.build.version.release   # run inside the Android shell
exit

The getprop line prints the Android release number (for example 13 or 16). You can also check it in Android's Settings → About.

Should you use Android 16 on Waydroid?

If an app you need demands a newer Android version, or you enjoy testing, the community builds are worth trying on a backed-up setup. For a stable daily driver, the official Android 13 images remain the safer choice. Not sure Waydroid is still worth investing in? Read Is Waydroid still maintained?