

For me;
-
the download is absurdly massive. Although it makes sense that you’d need an Android OS image to run Android, it’s bigger than the copy of Arch I used to run it
-
integration with the host OS is poor - be nice if copy-paste worked, and file transfer was easier
-
super-sluggish, even on quite powerful computers
-
never idle, makes my laptop run hot
Okay, it’s emulating ARM64, and emulators need a lot of CPU, but since Android apps are compiled to “Google’s own version of Java” and are JIT compiled to suit the phone CPU, should be possible just to compile them to AMD64 instead and run native.
If there’s an app that only exists on Android and has no desktop / web equivalent, it’s a workable solution, but it does entail compromises.


Might be a controversial take, but Raspberry Pi’s are pure ass as media servers. They’re profoundly i/o limited, which extends to access to external USB devices as well as ethernet, and lack the oomph required to decode hi-res video streams locally. 1080p can be choppy, forget about 4K.
Pi5 occupies the unhappy spot where it’s too expensive for enthusiast and hobby applications, but inadequate as a desktop PC which benefit from a bit more power.
A mini-PC is a much better fit. An N100 might even be overkill - mine has a Skylake from a decade ago in it, and it crushes ‘media’ activities while gently sipping at electricity.