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

  • wildbus8979
    231·
    7 months ago

    If you’re going to run waydroid in a VM, why not just run Android in a VM?

    Also why. The. Hell. Are. People. Still. Using. Virtualbox? What is this? 2005? You’re already running a kernel with built in world tier type 1 virtualization.

    • MonkderDritte@feddit.de
      2·
      7 months ago

      Also why. The. Hell. Are. People. Still. Using. Virtualbox?

      Couldn’t get any Qemu-manager to work (and no time to master running it with scripts) and Vmware can use KVM as hypervisor. Virtualbox not?

      • wildbus8979
        8·
        7 months ago

        No, VirtualBox is a Type 2 hypervisor.

        I’m not sure what qemu-manager is, but virt-manager works out of the box on Debian at least. There are no scripts needed, it’s a UI.

    • GenderNeutralBro@lemmy.sdf.orgEnglish
      1·
      7 months ago

      Is there an easy way to run Android in a VM?

      It’s been a long time since I looked, but I never had great success. The only AMD64 builds I could find were ancient. Getting apps installed was difficult. And my understanding (correct me if I’m wrong) is that Waydroid delivers apps in windows without a whole Android UI around them.

      The best option I found was using the Android Studio simulator.

          • Landless2029@lemmy.world
            1·
            7 months ago

            I’m trying to run blissos now in hyperv with no luck.

            Did you make any progress?

            I’m trying to find a bluestacks alternative

            • Quack Doc@lemmy.world
              1·
              6 months ago

              currently hyper-v has no graphics, qemu reccomended but hyperv should work if you force sofware rendering for gpu

            • GenderNeutralBro@lemmy.sdf.orgEnglish
              1·
              7 months ago

              Not really. I tried in AQEMU and also VirtualBox. I got the installer to run, but I never got it to boot into a GUI, either in the LiveCD or installation. Not sure what I’m doing wrong. Maybe I should try the stable 12L build instead of 13.

              • Landless2029@lemmy.world
                1·
                7 months ago

                For now I tried Google play games beta. It’s a type 1 vm instance instead of bluestacks being type 2.

                Super easy to setup. At least Google is the one spying on me instead of china.

    • n2burns@lemmy.ca
      21·
      7 months ago

      Also why. The. Hell. Are. People. Still. Using. Virtualbox? What is this? 2005? You’re already running a kernel with built in world tier type 1 virtualization.

      Honestly, for me, it’s probably just momentum at this point. I’ve been using Virtualbox for at least 15, maybe 20 years now. I don’t use it much anymore with how good docker, etc. have become. Any recommendation on what I should be using instead?

      • wildbus8979
        13·
        7 months ago

        Qemu, which is the standard KVM front end. Also does emulation when you need other architectures (great for prepping Pi images for example). If you need a UI virt-manager is a UI for libvirt that supports Qemu and lxc (even remotely through ssh). It’s been around since 2009.

    • sic_semper_tyrannis@lemmy.todayOP
      3·
      7 months ago

      This is interesting though at first glance seems a little over my head. I’ll read more into it. Thank you.

      PS. This is another comment I can only see and reply to in my inbox. I can’t see it on my post. I don’t know if this is a Lemmy, server, or Voyager issue.

  • db2@lemmy.world
    8·
    7 months ago

    I have waydroid working great in the latest Mint. You need Weston so Waydroid has a Wayland to connect to.

    e: or use the experimental Wayland in 21.3 but it’s not ready for daily driving

    • db2@lemmy.world
      5·
      7 months ago

      Here’s the script I use to start and stop Waydroid:

      #!/bin/bash
PID=$(pgrep "weston")
if [ "$?" -eq "0" ]; then
    waydroid session stop
    kill $PID
    exit
fi
weston --width=1920 --height=1080 --socket=wayland-1 &>/dev/null &
sleep 2
WAYLAND_DISPLAY=wayland-1 XDG_SESSION_TYPE=wayland waydroid show-full-ui

      Change the resolution to whatever you need it to be. Run it once to start, again to stop. It just lives on my desktop.

  • Possibly linux@lemmy.zipEnglish
    4·
    7 months ago

    You need a GPU.

    First, ditch VirtualBox as it isn’t a type 1 hypervisor. Next setup virtual manager and then enable GPU.

    If you need more help let me know.

  • Quack Doc@lemmy.world
    1·
    7 months ago

    Waydroid works inside of Avian perfectly fine, but I would still generally recommend either just using Bliss OS or the native host. You can run Waydroid using something like Cage or Weston if you’re on X11.

    If you are running on something like VirtualBox, you may need to disable hardware acceleration for GPUs. QEMU has working GPU acceleration.