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

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 仿真器 无法启动排查的更多相关文章

  1. Android应用程序启动时发生AndroidRuntime : ClassNotFoundException for Activity class的解决方法

    在android应用程序启动时抛出下面异常导致启动失败:07-09 17:12:35.709: ERROR/AndroidRuntime(3866): Uncaught handler: thread ...

  2. 【Android端 APP 启动时长获取】启动时长获取方案及具体实施

    一.什么是启动时长? 1.启动时长一般包括三种场景,分别是:新装包的首次启动时长,冷启动时长.热启动时长 冷启动 和 热启动 : (1)冷启动:当启动应用时,后台没有该程序的进程,此时启动的话系统会分 ...

  3. Android Studio 无法启动模拟器的一种可能是你装的是Ghost版的系统

    我遇到的问题是,打开模拟器,进度条走到最后,突然出现了emulator error,然后模拟器就无法启动(不好意思当时没有截图).我是在Ghost版 win7系统下运行Android Studio 的 ...

  4. android Activity的启动模式

    Android中Activity启动模式详解   在Android中每个界面都是一个Activity,切换界面操作其实是多个不同Activity之间的实例化操作.在Android中Activity的启 ...

  5. Android Activity的启动过程

    文章编辑的太长了,请移步我的csdn博客:http://blog.csdn.net/xyh269 Android Activity的启动过程原文链接:http://blog.csdn.net/xyh2 ...

  6. Android手机app启动的时候第一个Activity必须是MainActivity吗

    原文:Android手机app启动的时候第一个Activity必须是MainActivity吗 Android手机APP启动的第一个Activity是可以自己设置的,不是必须的MainActivity ...

  7. Android 4.2启动代码分析(一)

    Android系统启动过程分析 Android系统的框架架构图如下(来自网上):   Linux内核启动之后----->就到Android的Init进程 ----->进而启动Android ...

  8. Cocos2d-x3.3RC0的Android编译Activity启动流程分析

    本文将从引擎源代码Jni分析Cocos2d-x3.3RC0的Android Activity的启动流程,以下是具体分析. 1.引擎源代码Jni.部分Java层和C++层代码分析 watermark/2 ...

  9. Android开机动画启动流程

    android开机动画启动流程   从android的Surface Flinger服务启动分析知道,开机动画是在SurfaceFlinger实例通过调用startBootAnim()启动的. 下面我 ...

随机推荐

  1. Dictionary的遍历

    Dictionary<string, int> list = new Dictionary<string, int>(); list.Add("d", 1) ...

  2. Kafka分区分配策略分析——重点:StickyAssignor

    “ 为什么Kafka在RangeAssigor.RoundRobinAssignor的基础上,又新增了PartitionAssignor,它解决了什么问题?” 背景 用过Kafka的同学应该都知道Ka ...

  3. Android Selector和Shape的用法

    一.Shape的用法 :shape用于设定形状,可以在selector,layout等里面使用,有6个子标签,各属性如下: 填充:设置填充的颜色 间隔:设置四个方向上的间隔 大小:设置大小 圆角:同时 ...

  4. Rancher1-简单介绍-认识rancher

    认识rancher 一.简介 1.什么rancher Rancher是一个开源软件平台,使组织能够在生产中运行和管理Docker和Kubernetes.使用Rancher,组织不再需要使用一套独特的开 ...

  5. Bomb后端云使用

    Bomb是后台云托管工具,在Bomb官网注册会员,即可免费使用后台数据库服务.https://www.bmob.cn/app/list 创建应用后,在设置里获取密钥.根据官方文档集成. 在集成后运行时 ...

  6. 揭秘 iOS App Extension 开发 —— Today 篇

    转自:http://www.cocoachina.com/ios/20160619/16760.html 本文授权转载,作者:Cyandev(简书) 从 iOS 8 开始,苹果引入了全新的 App E ...

  7. [TimLinux] CSS 计数功能实现递归目录

    内容引用自<css世界>: count-reset 与 counter 为父子关系,兄弟关系会导致序号混乱 调用一次 count-increment 将给序号进行一次报数,调用 count ...

  8. HDU1846 Brave Game(巴什博弈)

    十年前读大学的时候,中国每年都要从国外引进一些电影大片,其中有一部电影就叫<勇敢者的游戏>(英文名称:Zathura),一直到现在,我依然对于电影中的部分电脑特技印象深刻. 今天,大家选择 ...

  9. Selenium 4.0 Alpha更新日志

    早在2018年8月,整个测试自动化社区就发生了一件重大新闻:Selenium的创始成员Simon Stewart在班加罗尔Selenium会议上正式确认了Selenium 4的发布日期和一些重要更新. ...

  10. leetcode -- 寻找两个有序数组的中位数

    题目: 给定两个大小为 m 和 n 的有序数组 nums1 和 nums2. 请你找出这两个有序数组的中位数,并且要求算法的时间复杂度为 O(log(m + n)). 你可以假设 nums1 和 nu ...