My solution is to set the graphics options on my Android virtual device to Software instead of Automatic or Hardware.
I believe this is a solution as I am working on a windows machine without a dedicated graphics card.
Read More:
- Failed to connect to ESP32: Timed out waiting for packet header
- A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header
- A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header
- esp32:A fatal error occurred: Timed out waiting for packet header
- Waiting for another pilot command to release the startup lock
- Failure: waiting for status update. MMC read failed
- [HMR] Waiting for update signal from WDS…
- How to eliminate ADB error “more than one device and emulator”
- An error is reported after Android studio creates a new virtual machine. Emulator: emulator: error: unknown AVD name
- Adb error: more than one device/emulator error handling
- An error is reported when starting the Android emulator: Emulator: audio: Failed to create voice `goldfish_audio_in’
- Ubuntu cannot access USB device, failed to create a proxy device for the USB device
- Putty prompt connection time out
- A new virtual machine cannot be connected to the network (error fetching interface information device not found),
- Vitis: platform out of date, makefile error at compile time; The modified application compiles to undefined reference
- emulator: ERROR: x86 emulation currently requires hardware acceleration! Abnormal problem solved
- When vivado2017 is started, the “error when launching” dialog box will pop up vivado.bat : Launcher time out”
- Failed to dlsym make_device: undefined symbol: make_device
- How to Solve Error: The emulator process for AVD was killed.
- Tensorflow 2.1.0 error resolution: failed call to cuinit: CUDA_ ERROR_ NO_ DEVICE: no CUDA-capable device is detected