Missing file: libpulse.so.0 about android-31

[ppoffice]

@rades101 Please update to scrcpy 1.23 and try again.

[ppoffice]

@mpelley
docker-android-sdk/android-30#11 (comment)

[ppoffice]

As a workaround, you may use scrcpy for screen output. You can also create a custom docker image on top of this one to install libpulse.

[rades101]

Hello,

I was trying to start an emulator without a -no-window option, to be able to see the display. Also, I installed libxcursor-dev and libpulse-dev. Unfortunately, I am not able to start the emulator, when emulator -avd first_avd -no-audio & executed I am getting

WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
INFO    | Warning: could not connect to display  ((null):0, (null))

INFO    | Info: Could not load the Qt platform plugin "xcb" in "/opt/android-sdk-linux/emulator/lib64/qt/plugins" even though it was found. ((null):0, (null))

Fatal: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: xcb.
 ((null):0, (null))
INFO    | Fatal: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: xcb.
 ((null):0, (null))

Regarding scrcpy if emulator started with emulator -avd first_avd -no-audio -no-window command UI cannot be casted, since the emulator started in headless mode. So I am getting this error
CRITICAL: Could not initialize SDL: No available video device

For me, interaction with UI is needed just the first time during setting up the device.

Best,
Rade

[ppoffice]

@rades101 You should start the docker container with --network host and run scrcpy on your host OS instead of the container. Also, --network host does not work properly for docker on Windows and macOS. If your docker is running on such OSes, you may need to install a remote desktop server (such as VNC) in your container and connects to it.

[rades101]

@ppoffice thanks for the response! I started the container with --network host, but if the emulator started with emulator -avd first_avd -no-audio -no-window, option -no-window is signal to start the emulator in headless mode, so scrcpy cannot connect to the emulator. And this is the problem that I described in my previous post. Looks there are issues in a container, and the emulator cannot be started in GUI mode.

[ppoffice]

@rades101 Where did you run scrcpy?

PS: I have no problem using scrcpy with the headless emulator:

[rades101]

@ppoffice I run scrcpy from the host. But I got a different error message after I followed your steps from a screenshot.

Btw, for me takes forever to boot a device, what is your hardware specification for ubuntu? In my case, I have 4 CPUs and 8GB of RAM.

[rades101]

After updating scrcpy to v1.23 I was able to see the device UI.
Here are the steps that I followed.

@ppoffice , thank you very much for your support!