I tried using Waydroid on Linux Mint (Edge) only to have it not work and realized that it requires Wayland, and Mint uses X11. So I used VirtualBox to install Fedora 40 Gnome which does use Wayland.

I installed Waydroid as per the instructions and am having seemingly the same issue as on Mint. After downloading “Vanilla” Android and clicking “Done” everything exits out. So I launch the Waydroid application but nothing ever happens.

I then try to manually start Waydroid in terminal but always get “ERROR: WayDroid container service is already running”. Then I skip to the second step “waydroid session start” but receive “OSError: container failed to start”.

Am I doing something wrong? Is it simply because the VM is causing the issues? Or does WayDroid not work well on Fedora? Thanks

  • AssortedBiscuits [they/them]@hexbear.net
    link
    fedilink
    English
    arrow-up
    1
    ·
    9 months ago

    I was able to get Waydroid to work in a Debian VM, so unless there’s something weird about how VirtualBox handles things, Waydroid shouldn’t care whether it’s running in a VM or not.

    What happens when you run waydroid status or waydroid show-full-ui?

    • sic_semper_tyrannis@lemmy.todayOP
      link
      fedilink
      arrow-up
      2
      ·
      9 months ago

      I’m not on my computer currently but I did try show-full-ui. I just remember it didn’t work correctly either. Good to know it can work in a VM though.

      PS. I can see your comment in my inbox and reply from there but when I’m on my post your comment doesn’t appear. Some odd Lemmy thing?

      • AssortedBiscuits [they/them]@hexbear.net
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        9 months ago

        PS. I can see your comment in my inbox and reply from there but when I’m on my post your comment doesn’t appear. Some odd Lemmy thing?

        I have no idea why that would happen. Probably something weird about Lemmy.

        As for Waydroid, it’s kinda finicky in how to start. Use something like btop or ps aux|grep waydroid to check whether you have multiple processes that are all running waydroid session start. It should just be two processes: /usr/bin/waydroid -w container start and /usr/bin/waydroid session start. I remember I had multiple /usr/bin/waydroid -w container start that I had to kill before it worked for the first time.

        The devs behind Waydroid also have their own distro set up for Waydroid. You can try that as well: https://waydro.id/#wdlinux