Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Problem with the emulator since the update

I have had a problem with my emulator Android Studio for a few days, when I try to compile my code, my event log marks this:

09:13   Emulator: socketTcpLoopbackClientFor: error: fd 44088 above FD_SETSIZE (32768)

09:13   Emulator: socketTcpLoopbackClientFor: error: fd 44088 above FD_SETSIZE (32768)

09:13   Emulator: emulator: ERROR: AdbHostServer.cpp:102: Unable to connect to adb daemon on port: 5037

What can i do to fix this thank you in advance

like image 299
pierrot0630 Avatar asked May 19 '20 07:05

pierrot0630


People also ask

Why is the emulator not working?

If the Android Emulator does not start properly, this problem is often caused by problems with HAXM. HAXM issues are often the result of conflicts with other virtualization technologies, incorrect settings, or an out-of-date HAXM driver. Try reinstalling the HAXM driver, using the steps detailed in Installing HAXM.

Why is my emulator stuck?

Fix 4 – Uninstall and Reinstall AVD From Android Studio, select “Tools” > “SDK Manager” > “SDK Tools“. Uncheck “Android Emulator“. Select “Apply” to have the emulator uninstalled. Once the emulator has been removed, check the “Android Emulator” box again, then select “Apply” to reinstall it.

How do I fix an emulator crash?

In AVD manager open settings for your virtual device. In the Emulated Performance section open the dropdown for Graphics . Change it from Automatic to Software . Hit the Finish button to save new setting and try starting the emulator again.


1 Answers

UPDATE: This issue has been fixed in version 30.0.26 as mentioned here. The temporary fix mentioned below may not be needed anymore.


Yes, this issue is seen in version 30.0.12 of android emulator.

As a temporary fix, which will work only on emulators without PlayStore, disable Multi-core cpu option

Avd Manager -> Select emulator -> edit -> Advanced Settings -> Multi-core CPU -> UNCHECK this option

The devices with PlayStore images do not allow changing anything about the device this won't work.

I have not seen any major lag by disabling the multi-core cpu option. Emulator is just as responsive and loads under 2 seconds, ready to be used.

Tested on Ryzen 5 1600, 16gb RAM, Windows 10 Pro, emulator 30.0.12.

like image 142
Doc Avatar answered Sep 23 '22 16:09

Doc