Android Emulation on Desktop: the right answer

Questions
1

I’ve read the other questions on this topic. No one seems to have given a very confident or deeply-explained answer that they stand behind.

Our options seem to look like this:

  • Waydroid in a VM (Open-source, often suggested and used in the Linux community, insecure)
  • Android Studio/Android SDK (Sometimes suggested here, likely more secure, seems to ask your consent for data collection, but is still from Google.)
  • Feel free to list any others.

What are the pros and cons of each?
What is the answer you would confidently stand behind, and your reasoning?

Waydroid is probably safe enough in a VM, but considering performance and other things, is it an actually good setup for daily-driving?

Do we trust the privacy and security guarantees of source-available Android SDK, even if the binaries are proprietary and from Google? If it’s for developers, could that encumber the daily-driving experience?

2

There’s also:

  • Android-x86 (FOSS, not maintained, but Waydroid uses old versions: could this be better than Waydroid?)

And there are some options I don’t consider to count.

  • GrapheneOS desktop mode
  • BlissOS (not public yet)
3

Waydroid uses LXC, so running it directly on the host makes it easy to set up, but the isolation is weaker than running Android inside a VM.

You can run Waydroid inside a QEMU/KVM VM to get another isolation layer, but then you have a VM running LXC, which adds complexity and some overhead. I don’t think that’s a very practical setup for daily use.

The Android Studio emulator is probably the better choice if isolation is the priority, since it uses a proper virtual machine. But it is also quite resource-heavy, and on Linux it relies on KVM for hardware-accelerated virtualization.