4 ms·

In my experience those always behave terrible under Linux, regardless of what hardware I use(including my current dual-xeon with combined 28 cores setup and 64g

In my experience those always behave terrible under Linux, regardless of what hardware I use(including my current dual-xeon with combined 28 cores setup and 64gb of ram). Never tried the emulator under other OS-es, it might be alright there.

jeroenhd 5y ago
I've honestly never had trouble with the Android emulator on either Ubuntu or Manjaro, except for lacking drivers from Intel and Nvidia. I assume you've already done the basic troubleshooting steps (forcing the emulator to a single NUMA node, giving it more RAM, etc) so I can't tell you what's going on, but I can share my experience for everyone else reading this: If you've got problems like choppiness or unresponsiveness, you should check if GPU hardware acceleration is enabled in the settings and if your GPU driver hasn't been blacklisted for known stability issues. Things like KVM should also be enabled of course, but I'm pretty sure you're warned about that if you don't have it enabled. AMD and Intel both had a mobile Linux GPU driver blacklisted for hardware acceleration for a while, which made the emulator on my old laptop switch back to software based rendering, which was slow as molasses for obvious reasons. I've also learned not to run Android emulators with less than 3GiB of RAM anymore because that's the minimum a mobile OS requires these days, apparently. Also give the emulator at least 2 cores and run everything from an SSD, bbecause those are the specs the OS expects. If you don't like Google's emulator, I've also found Android x86 in Virtualbox to be reasonably stable after messing with the config for a bit. You need to mess around with it to get ADB debugging to work and to get the screen in a phone-like resolution, and you need to follow a guide to get Google's APIs on there, but after that it's pretty much good to go as far as basic Android dev goes. It's much more configurable in terms of changing specs and it doesn't seem to mind the lack of GPU acceleration as much.
- axegon_ 5y ago
  Yeah, done all that, it was never as smooth as an actual device. It's fine though, more screens for development and one dedicated to testing which is more comfortable for me at least(disclosure I only occasionally do apps, just a once in a while "hey that'd be cool to have").

jeroenhd 5y ago

I've honestly never had trouble with the Android emulator on either Ubuntu or Manjaro, except for lacking drivers from Intel and Nvidia. I assume you've already done the basic troubleshooting steps (forcing the emulator to a single NUMA node, giving it more RAM, etc) so I can't tell you what's going on, but I can share my experience for everyone else reading this: If you've got problems like choppiness or unresponsiveness, you should check if GPU hardware acceleration is enabled in the settings and if your GPU driver hasn't been blacklisted for known stability issues. Things like KVM should also be enabled of course, but I'm pretty sure you're warned about that if you don't have it enabled. AMD and Intel both had a mobile Linux GPU driver blacklisted for hardware acceleration for a while, which made the emulator on my old laptop switch back to software based rendering, which was slow as molasses for obvious reasons. I've also learned not to run Android emulators with less than 3GiB of RAM anymore because that's the minimum a mobile OS requires these days, apparently. Also give the emulator at least 2 cores and run everything from an SSD, bbecause those are the specs the OS expects. If you don't like Google's emulator, I've also found Android x86 in Virtualbox to be reasonably stable after messing with the config for a bit. You need to mess around with it to get ADB debugging to work and to get the screen in a phone-like resolution, and you need to follow a guide to get Google's APIs on there, but after that it's pretty much good to go as far as basic Android dev goes. It's much more configurable in terms of changing specs and it doesn't seem to mind the lack of GPU acceleration as much.

axegon_ 5y ago
Yeah, done all that, it was never as smooth as an actual device. It's fine though, more screens for development and one dedicated to testing which is more comfortable for me at least(disclosure I only occasionally do apps, just a once in a while "hey that'd be cool to have").