omawaydroid installs Android 17 on Omarchy in one command, built on Waydroid and WayDroid-ATV

Android apps on Omarchy are now one command away. Greyforge Labs released omawaydroid 0.1.0 on October 26, 2026. The MIT-licensed shell script describes itself as “Waydroid that just works on Omarchy and Arch Linux.” It installs Waydroid, fixes the firewall so Android gets a network connection, downloads Android 13, 16 or 17, and starts the container. “Android 17 with October’s security patch now installs on Omarchy in one command,” the developer posted on X the same day.

Here’s the command to run as your normal user. It asks for sudo when it needs root: bash <(curl -fsSL https://raw.githubusercontent.com/GreyforgeLabs/omawaydroid/main/omawaydroid.sh) install --android 17. If you want to keep the script around for later, the README also gives a way to download the v0.1.0 release and check its SHA-256 before running it. When the install finishes, waydroid show-full-ui opens Android, and Android apps appear in your normal app menu.

Android 13 is the default and uses the official Waydroid images. Android 16 and 17 come from images built by the WayDroid-ATV project. According to the README, Android 17 has the October 2026 security patch as of v0.1.0. Android 16 is pinned to a build from August 3, 2026 and only comes with Google apps. If you don’t want Google apps, add --vanilla. omawaydroid uses the standard waydroid package from the Arch repositories and doesn’t modify it. sudo waydroid upgrade keeps the images up to date afterwards.

The README lists the Omarchy problems it fixes:

• No network behind ufw. Omarchy’s default firewall blocks Waydroid’s DHCP, so Android has no IP address. The script adds only the waydroid0 rules that are missing, never changes rules you made, and removes only its own on uninstall.
• Stalled downloads. Images come from the fastest mirror that works. Downloads resume if they’re interrupted, and every image is checked against its SHA-256.
• Android 16 and 17 apps that open no window. A small launcher wrapper in ~/.local/bin opens apps started from the app menu inside the Android window.

There’s also a read-only doctor command. It checks the Wayland session, the kernel’s binder driver, memory, disk, the firewall and the container, and gives a fix for each problem it finds. It also looks for a leftover binder_linux-dkms module. An issue filed on the Omarchy repo on October 25, 2026, which is still open, reports that this old Waydroid workaround clashes with the binder driver now built into Omarchy’s 7.2.8-9 kernel and leads to random freezes. If you change your mind, uninstall reverts only what omawaydroid changed, and uninstall --purge also removes Waydroid and all Android data.

The firewall fix could reach everyone. Greyforge Labs has submitted it to Waydroid in pull request #2458. The PR is still open and covers ufw and Docker setups that leave Android without an address.

The performance figures come from the developer’s own test machine, which runs Omarchy with kernel 7.2.8, Hyprland and an AMD GPU. There, the README says a full install takes about 2.5 minutes on a typical connection and Android 17 cold-starts in 19 seconds. It also says SuperTuxKart runs at 60 FPS, including through ARM translation.

Requirements: an x86_64 Arch-based system (Omarchy, Arch, EndeavourOS or CachyOS), a Wayland session, a kernel with binder (Omarchy’s 7.2.8-9 or newer, or Arch’s linux, linux-zen or linux-lts), about 2 GB of free memory, and 8 GB of free disk under /var/lib. It’s a 0.1.0 release from a community developer, not an official Omarchy feature. Still, if you’ve wanted Android apps on your Omarchy desktop, this is the easiest way to get them so far.

Source: https://github.com/GreyforgeLabs/omawaydroid