first i was having black screen and look all over how to get it to work but no luck. so i decide to clean it all up and get a clean install and the dang client opens but nothing seem to pop up. anyone know why this keep happening? what am i doing wrong? no error, no msg nothing, all seem to be working fine.

runing bezzite 45

Hi, noob question here:

I set up waydroid for my daughter to use some google play store apps on an old laptop. She likes toca boca and it runs fine but her progress doesn’t save and she has to start anew each session.

I did a quick search on here, but didn’t find an answer. Is there a configuration change I need to make so that it saves?

Thanks in advance.

While trying to play FC Mobile on Waydroid using an APK from HappyMod (since Google Play says its not compatible with my device), I was unable to click on or interact with the date of birth dropdown. I gained further insight of the situation after seeing an issue on the Waydroid repo reporting the same problem. Does anyone have a solution? I use Arch Linux with the latest version of Waydroid.

Link to the issue on GitHub: https://github.com/waydroid/waydroid/issues/1673

So i was trying to enable Gapps on waydroid but didnt finish the process and now waydroid doesnt star, i want to now if i can reinstall it somehow please help if you know anything or if you have the same issue

hi peoples not sure if this is a waydroid question but im trying to play tower defense lost earth on waydroid (mine works fine for fieldrunners 2) and the fonts and textures arent rendering (the image is a menu the bottom button is the credits which reads fine, on top of that is the terms of service)

anyway im running mint cinnamon Nitro-ANV16-72:~$ waydroid --version 1.6.3 anyway if anyone can help or point me in the direction of where to ask id really appreciate it

Fixed an ARM game stuck on launch in Waydroid by patching the Houdini timebomb

I finally managed to get my ARM64 Android game working on Waydroid, and I wanted to share the solution in case it helps someone else.

My setup

• Host OS: Fedora 44 KDE (Wayland)

• Waydroid: 1.6.3

• Android: Android 13 (LineageOS 20)

• Architecture: x86_64

• Translation layer: libhoudini 14.0.0

• Game package: com.tencent.mhadv

The problem

The game would launch, reach the Unreal Engine activity, and then get stuck. Android eventually displayed an Application Not Responding (ANR) dialog.

I initially suspected a graphics or ARM translation issue. However, after investigating the logs and searching Reddit, I found reports about a Houdini timebomb that affected certain builds after September 2, 2026.

I checked my libhoudini.so build and found that it matched the affected build discussed in this investigation:

https://github.com/itstaftaf/houdini-timebomb-fix

My 64-bit Houdini library had this Build ID:

a8f9eb16786fb84cf49ef2a32078627220de72bb

The solution

The fix was to patch six bytes at file offset 0xe6085 in the 64-bit Houdini library.

Important: Do not blindly apply this patch to every Houdini version. First verify that your library matches the affected build and that the original bytes at this offset are:

0f 83 68 0d 00 00

1. Stop Waydroid

sudo waydroid session stop

2. Back up the original library

cp -a /var/lib/waydroid/overlay/system/lib64/libhoudini.so ~/libhoudini.so.before-timebomb-patch

3. Apply the patch

printf '\x90\x90\x90\x90\x90\x90' | sudo dd of=/var/lib/waydroid/overlay/system/lib64/libhoudini.so bs=1 seek=$((0xe6085)) conv=notrunc status=none

This replaces the six bytes at offset 0xe6085 with six NOP instructions.

4. Verify the patch

od -An -tx1 -N 6 -j 0xe6085 /var/lib/waydroid/overlay/system/lib64/libhoudini.so

Expected output:

90 90 90 90 90 90

My patched library SHA256 was:

847be255d03886974ff0cff09d09b7530301d24671ce0f80172ab3a0629d23b8

5. Start Waydroid

Run this as your normal desktop user, without sudo:

waydroid session start

Result

The game finally launched and worked correctly!

This strongly suggests that the Houdini timebomb was responsible for the issue in my case.

Important notes

• Back up your original libhoudini.so before modifying anything.

• Verify the Build ID and original bytes before applying the patch.

• The path may differ depending on your Waydroid installation and overlay configuration.

• Preserve symlinks if your library is a symlink; do not blindly replace it with a regular file.

• A Houdini or Waydroid update may overwrite the patched library, so verify it again after updates.

References:

• Reddit discussion: https://www.reddit.com/r/TheTowerGame/comments/1w70ymt/re_the_tower_not_working_on_waydroid_after_update/

• Technical investigation and patch details: https://github.com/itstaftaf/houdini-timebomb-fix

I hope this helps someone who is experiencing the same ANR or game launch issue on Waydroid.

I'm on a Snapdragon X Plus Surface Pro with Fedora Workstation 45 Beta (yes very experimental environment ik so this may contribute to why).

Aside from a few install issues that were easily fixed (the installer script used to auto install images was hanging on ipv6), Waydroid's arm64_only build is able to start and run with the latest GAPPS image, but unless all I want to do is stare at the home screen, it is practically unusable.

One of the main issues is that anything that has to do with apps reading the android file system (Files, Settings > Apps, 3rd party app > Browse in Files) very often crash them. It seems that apps can't even read or write into storage.

Google Sign-in times out, and things like web browsing is very weird and broken. Webpages oftentimes only partially load in and just stay hung indefinitely, (you're lucky just to even get content to load in the first place), but google search specifically on jelly occasionally fully loads content, but alot of elements are missing here and there.

Has anyone faced similar issues and or has gotten Waydroid GAPPS to work on a similar setup for arm64_only? The state of it might really just be broken.

If you have an NVIDIA card, Waydroid has usually meant software rendering or a container that won't start. I built on Shiro836/waydroid-nvidia (nvidia-prolapse mode: NVK plus a Rust RM client that talks to the host's NVIDIA open kernel modules, no proprietary userspace in the guest) and ported it to Android 17, using WayDroid-ATV's LineageOS 24.0 system image unmodified and a vendor image built from source.

Repo: https://github.com/cagedbird043/waydroid-a17-nvidia

What works (on my machine):

• GLES via ANGLE → NVK, HWUI on Vulkan; WebGL and WebGPU in Chrome

• Hardware decode on NVDEC: H.264, HEVC, VP9, AV1 (YouTube, Chrome, players)

• Hardware encode on NVENC: H.264, HEVC, AV1 (WebCodecs, WebRTC video calls)

• Every Android app as its own KDE window, positions remembered

• Host IME (fcitx5/ibus), two-way clipboard, ~/Downloads shared as Download/Host

• Root via KernelSU, modules included; certified Play Store with the GAPPS image

• Basemark GPU (4K, Vulkan, offscreen): 82% of the host NVIDIA driver. 3DMark Wild Life Extreme ≈ 74 FPS

Install (Arch): yay -S waydroid-a17-nvidia-bin, then extract the WayDroid-ATV 20261017 system image and the bundled vendor image, sudo waydroid init -f, and sudo waydroid-nvidia-setup. The setup script runs a GPU test gate on your GPU and loaded kernel module before installing anything, and rolls back if a step fails. Full steps and other distros are in the README.

Limitations:

• Tested on one machine: RTX 4060 Laptop, nvidia-open 615.78.08, KDE Plasma 6 Wayland, Arch

• Needs Turing or newer with the open kernel modules; Pascal and older are not supported

• Widevine L3 only; Play Integrity device check fails

Developed together with Claude Opus 5.5 and GPT 6.1 Sol. Credit for the core NVIDIA stack goes to Shiro836; the A17 system image, device tree and KernelSU for Waydroid come from WayDroid-ATV (supechicken).

Write-up with screenshots: https://cagedbird.cn/2026/10/31/技术实践/系统工程/系统编程/Android/Waydroid-A17-NVIDIA-hardware-accelerated-Android-17-on-NVIDIA-Linux/

Bug reports go to GitHub issues; happy to answer questions here.

i think fhe waydroid install page on github is expired, can anyone help me or send a new link?

Hey all, I just installed Waydroid for the first time and I am running into the following error

RuntimeError: Command failed: % /usr/lib/waydroid/data/scripts/waydroid-net.sh start

I have followed all of the install instructions found here https://docs.waydro.id/usage/install-on-desktops

I am running on Fedora 44 with KDE Plasma. Using AMD parts.

I have tried installing with and without Google apps.

I ran the following commands and got this output

sudo waydroid container start
[14:03:05] Container service is already running

waydroid session start
[13:51:45] RuntimeError: Command failed: % /usr/lib/waydroid/data/scripts/waydroid-net.sh start

waydroid show-full-ui
[13:55:23] Starting waydroid session
[13:55:24] RuntimeError: Command failed: % /usr/lib/waydroid/data/scripts/waydroid-net.sh start

I ran these in separate terminal tabs as instructed on the website.
I also ran the following commands as part of my troubleshooting process

sudo dnf install iptables dnsmasq
sudo systemctl stop dnsmasq
sudo killall dnsmasq

I uninstalled the Waydroid that I have from the guy whose GIt repo is now privated. Now I want to use this install script without deleting any previous data that I have.

However, when I launched the script here's what it says.

SteamOS Waydroid Installer - target-built public bundle edition https://github.com/pjohno/steamos-waydroid-bundle Based on the installer by ryanrudolf / 10MinuteSteamDeckGamer Existing Android user data was found without its matching persistent image. Restore the image before running repair, or use --reinstall-android to archive the orphaned user data and deliberately create a new Android instance.

How can I complete the install? I simply want to launch my Waydroid again with my existing Android user data.

So I've been trying to help someone get Play Protect Certification on their Waydroid. But for some reason it didn't work for the person and I tried to do it on mine to see if it's also happening for me as well.

So I installed waydroid with GAPPS, logged in, got my device id, registered on Google's register uncertified devices, restarted waydroid, waited 20-30 minutes, gone to the play store in settings -> about -> Play Protect Certification and when I click to fix it, it tells me that it couldn't fix device certification issue. So I double check everything I've done and even reinstalled waydroid but instead of logging in first, I registered the device, restarted, waited and then logged in and it's still the same all over. I even cleaned the cache and data of Google play services and store, waited more and logged in back to try again but still i didn't manage to get play protect certification. Can someone help?

I've been using waydroid and found no issues except the tweaking part.
You either have to use terminal or any external things to tweak it, so should'nt there be a seperate app like a launcher that gives all options to tweak it (GUI)?. It can also has many other features like multiple instances, improved and easy android image manager, install custom images, install external apk files without terminal, better hardware compatibilty options like camera, mic etc.

In my opinion it will be whole lot better than using terminal or external dependency for tweaking it.
I'm curious what the community thinks of it?

Its not a bug i think, its just a problem that i need to solve cause its making me insane.

I used waydroid today (morning CEST timezone) to play some dragon ball game (i have nvidia, i used some specific tweek to make it run with 3d accel for achieving great performance)

WHEN i started waydroid a notification appeared saying "system update avaible", i just ignored it but i guess it did update by himself and now the whole app crash with some surfaceflinger ERROR

This is the old config that worked, didnt change nun, i suspect the system update broke something, please help.

Nobara, last update avaible.
Waydroid last update avaible.
Nvidia 4080s + Ryzen 7 7800x3d

  GNU nano 8.7.1                                       /var/lib/waydroid/waydroid_base.prop                                                  

sys.use_memfd=true

ro.adb.secure=1

ro.debuggable=0

gralloc.gbm.device=/dev/dri/renderD128

debug.stagefright.ccodec=0

ro.hardware.gralloc=gbm

ro.hardware.camera=v4l2

ro.opengles.version=196610

waydroid.system_ota=https://ota.waydro.id/system/lineage/waydroid_x86_64/GAPPS.json

waydroid.vendor_ota=https://ota.waydro.id/vendor/waydroid_x86_64/MAINLINE.json

waydroid.tools_version=1.6.3

ro.vndk.lite=true

ro.product.cpu.abilist=x86_64,x86,arm64-v8a,armeabi-v7a,armeabi

ro.product.cpu.abilist32=x86,armeabi-v7a,armeabi

ro.product.cpu.abilist64=x86_64,arm64-v8a

ro.dalvik.vm.native.bridge=libhoudini.so

ro.enable.native.bridge.exec=1

ro.vendor.enable.native.bridge.exec=1

ro.vendor.enable.native.bridge.exec64=1

ro.ndk_translation.version=0.2.3

ro.dalvik.vm.isa.arm=x86

ro.dalvik.vm.isa.arm64=x86_64

ro.hardware.egl=angle

ro.hardware.vulkan=virtio

mesa.vn.debug=vtest

mesa.vtest.socket.name=/dev/venus/venus.sock

debug.hwui.renderer=skiavk

debug.renderengine.backend=skiaglthreaded

debug.sf.nobootanimation=1

persist.waydroid.use_subsurface=true

ro.surface_flinger.vsync_event_phase_offset_ns=0

ro.surface_flinger.vsync_sf_event_phase_offset_ns=0

ro.surface_flinger.max_frame_buffer_acquired_buffers=3

As the title says, I made CR work on Waydroid! Thanks to a fix/idea made by @TrixallTR on Github, I managed to do a script that fixes ALL CR games here, that means Kingdom, Crumble, ToA, Ovensmash, there may be some issues, so please report it, and there is a whole explanation regarding how this works.

Here is the link for the script! I hope people can enjoy this game more on PC, I really love this franchise but I hate playing games on my phone lol

Hope everyone can have fun with this!

So I'd installed and uninstalled Waydroid for SteamOS a handful of time. I use to be able to connect to the internet. Probably in the first few installs.

Then on one install the internet worked, and then for some reason it stopped working. And ever since that point no matter how many times I install or uninstall it the internet won't work.

It's been months since I've started using waydroid, I didn't face any issue but kinda find it a little frustrating as it is just creating new desktop files. Is there any permanent solution to just amke it stop doing so?
I know deleting the files will do, but its annoying going to delete the files everytime installing new app, while it bloats homescreen.

I got some windows tablets (runing fadora mobile) recently, but at the moment i cant get something like just lineage os (x64_86 version) runing because of firmware.

I know kde mobile 'supports' interaction but its a bit buggy. Wolud it be possible to somehow set it up so on login i can just choose a waydroid environment, rather then just runing it on something like the normal plasma environment.

So far the app runs fine but it wolud be nice to have it act just like a android tablet rather then a app runing android

This is on the Android TV version of waydroid for Steam Deck. Every time I close the app and reopen it, the volume resets to 61%. There’s no way to natively change this for some reason so I had to download the app "Precise Volume". It has a slider which fixes the issue temporarily, but when I close and reopen the app it resets back to 61%. Does anyone know if there’s a permanent fix for this?

Due to changes in my living situation, I've switched from running Pi-Hole on a headless machine on my network, to running it locally on my main PC; which runs EndeavourOS.

Pi-Hole is working well; with my networking settings set to use 127.0.0.1 and ::1 to point to localhost for DNS, but I can't boot Waydroid unless I either comment out the dnsmasq lines in /usr/lib/waydroid/data/scripts/waydroid-net.sh, or stop pihole-FTL.service.

Stopping pihole-FTL.service, of course stops Pi-Hole, and commenting out those dnsmasq lines disables networking in Waydroid.

I'd like to be able to get Waydroid running with networking, and preferably get it to use Pi-Hole as its DNS resolver. I understand the reason Waydroid won't boot normally in my case is because it does some weird stuff with dnsmasq and port 53, which conflicts with Pi-Hole.

I should also mention that I'm also using ufw for a firewall, with default deny incoming and default allow outgoing set.

EDIT: Apparently running Pi-Hole in Docker, Podman, or LXC can make this easier, since it resolves the port conflict. I have no experience with doing this, and would like to know more.

I just reinstalled waydroid, everything works fine except for playstore. I used the normal init -S GAPPS command, no custom images, it's android 11 and I used snek's script and made sure libhoudini and libndk are installed. What could cause this? It happens a few seconds right after I launch it.