SO_REUSEPORT unavailable on compiling system to run emulator for andriod on Ubuntu

Question

I was trying to install SDK and Emulator without the Andriod studio on Ubuntu 20.04. But got stuck at this error.

E0520 11:06:29.866803544    5261 socket_utils_c         


        

Answer 1

Install Android SDK Platform tools. if already exist uninstall and install Android SDK Platform tool in ubuntu 20.04

Answer 2

I got the solution from this article:

So in order to fix this, I just disabled the Camera by switching the option from Emulated to None and that was all.

Don't ask why this works, but it seemed to solve it for me.

Answer 3

Seems a GPU issue, try :

sudo ubuntu-drivers autoinstall

Or (or both) change graphic emulated performance to software if your emulated device allow it.

Had same issue with linux mint android studio .. Hope it will help.

Answer 4

Though not directly affected by the error you described, when stuck at this point (namely, when supposed to be connecting back to the ADB server, but can't), this can be a result of a corrupted quick-boot snapshot.

What worked for me is to hard-delete the existing quick-boot snapshot, and have the emulator regenerate it on the next run.

To delete the snapshots:

rm -fr ~/.android/avd/<AVD name>/snapshots/default_boot

To regenerate the next snapshot, rerun the emulator as you normally would, then kill it after if full loads. But first, make sure that it is configured for saving a quick-boot snapshot on exit:

Edit quickbootChoice.ini, for example:

vi ~/.android/avd/<AVD name>/quickbootChoice.ini

The only line there should be:

saveOnExit = true

---

If you wish to see whether any of this is likely to help you before making any changes, run the emulator with the -no-snapshot argument applied, beforehand. For example:

$ANDROID_SDK_ROOT/emulator/emulator -no-snapshot @Pixel_API_29 &

(Or find a way to do this through Android Studio)

A note regarding other answers here that advised configuring the camera differently (which seems unrelated): It is very likely that changing the camera setting, for the Emulator, is considered a configuration change - which ends up in forcing a cold-boot (i.e. skipping usage of the quick-boot snapshot), which can explain why it works (but with no voodoo involved).