Android 仿真器 无法启动排查

Posted shanyou

tags:

篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了Android 仿真器 无法启动排查相关的知识,希望对你有一定的参考价值。


从命令行启动仿真器,可以查看其输出。


Microsoft Windows [版本 10.0.18362.145]
(c) 2019 Microsoft Corporation。保留所有权利。

C:\Users\geffzhang>msinfo32

C:\Users\geffzhang>sc query intelhaxm

SERVICE_NAME: intelhaxm
         TYPE               : 1  KERNEL_DRIVER
         STATE              : 1  STOPPED
         WIN32_EXIT_CODE    : 31  (0x1f)
         SERVICE_EXIT_CODE  : 0  (0x0)
         CHECKPOINT         : 0x0
         WAIT_HINT          : 0x0


C:\Users\geffzhang>c:\android\android-sdk\emulator\emulator.exe -list-avds
Android_Accelerated_x86_Oreo

C:\Users\geffzhang>c:\Android\android-sdk\emulator\emulator.exe -partition-size 512 -no-boot-anim -verbose -feature WindowsHyperversorPlatform -avd Android_Accelerated_x86_Oreo -prop monodroid.avdname=Android_Accelerated_x86_Oreo
emulator: Android emulator version 27.2.9.0 (build_id 4773671) (CL:18fc969f023e3b369b34b08db237dd9addfe100a)
emulator: Found AVD name ‘Android_Accelerated_x86_Oreo‘
emulator: Found AVD target architecture: x86
emulator: argv[0]: ‘c:\Android\android-sdk\emulator\emulator.exe‘; program directory: ‘c:\Android\android-sdk\emulator‘
emulator:  Found directory: c:\Android\android-sdk/system-images\android-27\google_apis\x86\

emulator: Probing for c:\Android\android-sdk/system-images\android-27\google_apis\x86\/kernel-ranchu: file exists
emulator: Auto-config: -engine qemu2 (based on configuration)
emulator:  Found directory: c:\Android\android-sdk/system-images\android-27\google_apis\x86\

emulator: emuDirName: ‘c:\Android\android-sdk\emulator‘
emulator:  Found directory: c:\Android\android-sdk/system-images\android-27\google_apis\x86\

emulator: Probing for c:\Android\android-sdk/system-images\android-27\google_apis\x86\/kernel-ranchu-64: file missing
emulator: try dir c:\Android\android-sdk\emulator
emulator: Trying emulator path ‘c:\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-i386.exe‘
emulator: Found target-specific 64-bit emulator binary: c:\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-i386.exe
emulator: Adding library search path: ‘c:\Android\android-sdk\emulator/lib64‘
emulator: Adding library search path: ‘c:\Android\android-sdk\emulator/lib64/gles_swiftshader‘
emulator: Adding library search path: ‘c:\Android\android-sdk\emulator/lib64/gles_angle‘
emulator: Adding library search path: ‘c:\Android\android-sdk\emulator/lib64/gles_angle9‘
emulator: Adding library search path: ‘c:\Android\android-sdk\emulator/lib64/gles_angle11‘
emulator: Adding library search path for Qt: ‘c:\Android\android-sdk\emulator\lib64\qt\lib‘
emulator: Setting Qt plugin search path: QT_QPA_PLATFORM_PLUGIN_PATH=c:\Android\android-sdk\emulator\lib64\qt\plugins
emulator: Setting Qt to use software OpenGL: QT_OPENGL=software
emulator: Quoted param: [c:\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-i386.exe]
emulator: Quoted param: [-partition-size]
emulator: Quoted param: [512]
emulator: Quoted param: [-no-boot-anim]
emulator: Quoted param: [-verbose]
emulator: Quoted param: [-feature]
emulator: Quoted param: [WindowsHyperversorPlatform]
emulator: Quoted param: [-avd]
emulator: Quoted param: [Android_Accelerated_x86_Oreo]
emulator: Quoted param: [-prop]
emulator: Quoted param: [monodroid.avdname=Android_Accelerated_x86_Oreo]
emulator: Running :c:\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-i386.exe
emulator: qemu backend: argv[00] = "c:\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-i386.exe"
emulator: qemu backend: argv[01] = "-partition-size"
emulator: qemu backend: argv[02] = "512"
emulator: qemu backend: argv[03] = "-no-boot-anim"
emulator: qemu backend: argv[04] = "-verbose"
emulator: qemu backend: argv[05] = "-feature"
emulator: qemu backend: argv[06] = "WindowsHyperversorPlatform"
emulator: qemu backend: argv[07] = "-avd"
emulator: qemu backend: argv[08] = "Android_Accelerated_x86_Oreo"
emulator: qemu backend: argv[09] = "-prop"
emulator: qemu backend: argv[10] = "monodroid.avdname=Android_Accelerated_x86_Oreo"
emulator: Concatenated backend parameters:
  c:\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-i386.exe -partition-size 512 -no-boot-anim -verbose -feature WindowsHyperversorPlatform -avd Android_Accelerated_x86_Oreo -prop monodroid.avdname=Android_Accelerated_x86_Oreo
emulator: Android virtual device file at: C:\Users\geffzhang\.android\avd\Android_Accelerated_x86_Oreo.ini
emulator: virtual device content at C:\Users\geffzhang\.android\avd\Android_Accelerated_x86_Oreo.avd
emulator: virtual device config file: C:\Users\geffzhang\.android\avd\Android_Accelerated_x86_Oreo.avd/config.ini
emulator: using core hw config path: C:\Users\geffzhang\.android\avd\Android_Accelerated_x86_Oreo.avd/hardware-qemu.ini
emulator: using snapshot lock path: C:\Users\geffzhang\.android\avd\Android_Accelerated_x86_Oreo.avd/snapshot.lock
emulator: Found AVD target API level: 27
emulator: Read property file at c:\Android\android-sdk/system-images\android-27\google_apis\x86\/build.prop
emulator: No boot.prop property file found.
emulator: ‘magic‘ skin format detected: 768x1280
emulator: autoconfig: -skin 768x1280
emulator: autoconfig: -skindir (null)
emulator: autoconfig: -kernel c:\Android\android-sdk/system-images\android-27\google_apis\x86\/kernel-ranchu
emulator: Target arch = ‘x86‘
emulator: Auto-config: -qemu -cpu qemu32
emulator: Auto-detect: Kernel image requires new device naming scheme.
emulator: Auto-detect: Kernel does not support YAFFS2 partitions.
emulator: autoconfig: -ramdisk c:\Android\android-sdk/system-images\android-27\google_apis\x86\/ramdisk.img
emulator: Using initial system image: c:\Android\android-sdk/system-images\android-27\google_apis\x86\/system.img
emulator: Using initial vendor image: c:\Android\android-sdk/system-images\android-27\google_apis\x86\/vendor.img
emulator: autoconfig: -data C:\Users\geffzhang\.android\avd\Android_Accelerated_x86_Oreo.avd/userdata-qemu.img
emulator: autoconfig: -initdata C:\Users\geffzhang\.android\avd\Android_Accelerated_x86_Oreo.avd/userdata.img
emulator: autoconfig: -cache C:\Users\geffzhang\.android\avd\Android_Accelerated_x86_Oreo.avd/cache.img
emulator: autoconfig: -sdcard C:\Users\geffzhang\.android\avd\Android_Accelerated_x86_Oreo.avd/sdcard.img
emulator: Increasing RAM size to 1024MB
emulator: VM heap size 64MB is below hardware specified minimum of 256MB,setting it to that value
emulator: System image is read only
emulator: Found 4 DNS servers: 202.96.134.133 192.168.1.1 fec0:0:0:ffff::1 fec0:0:0:ffff::2
emulator: WARNING: [FeatureControl] Bad feature name: ‘WindowsHyperversorPlatform‘
emulator: found magic skin width=768 height=1280 bpp=16

emulator: CPU Acceleration: DISABLED
emulator: CPU Acceleration status: Please disable Hyper-V before using the Android Emulator.  Start a command prompt as Administrator, run ‘bcdedit /set hypervisorlaunchtype off‘, reboot.
emulator: ERROR: x86 emulation currently requires hardware acceleration!
Please ensure Windows Hypervisor Platform (WHPX) is properly installed and usable.
CPU acceleration status: Please disable Hyper-V before using the Android Emulator.  Start a command prompt as Administrator, run ‘bcdedit /set hypervisorlaunchtype off‘, reboot.

C:\Users\geffzhang>


上述说明需要如下操作才能使用仿真器:


emulator: CPU Acceleration: DISABLED
emulator: CPU Acceleration status: Please disable Hyper-V before using the Android Emulator.  Start a command prompt as Administrator, run ‘bcdedit /set hypervisorlaunchtype off‘, reboot.
emulator: ERROR: x86 emulation currently requires hardware acceleration!
Please ensure Windows Hypervisor Platform (WHPX) is properly installed and usable.
CPU acceleration status: Please disable Hyper-V before using the Android Emulator.  Start a command prompt as Administrator, run ‘bcdedit /set hypervisorlaunchtype off‘, reboot.

以上是关于Android 仿真器 无法启动排查的主要内容,如果未能解决你的问题,请参考以下文章

markdown 修复Firebase功能无法启动仿真器错误

C++程序启动时报“0xC000007B”无法启动的问题排查

无法启动任何模拟器

Wi-fi无法连接到Android Studio模拟器

K8S故障排查指南:部分节点无法启动Pod资源-Pod处于ContainerCreating状态

MSP430 CCS6.2无法启动仿真