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

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. 利用scatter()绘制颜色映射的二次方曲线

    程序如下: import matplotlib.pyplot as plt x_value = list(range(1, 1001)) y_value = [x**2 for x in x_valu ...

  2. Python存储数据的方式

    在Python开发中,数据存储.读取是必不可少的环节,而且可以采用的存储方式也很多,常用的方法有json文件.csv文件.MySQL数据库.Redis数据库以及Mongdb数据库等. 1. json文 ...

  3. WPF 使用Win32API 让控件置于WebBrowser上方

    WPF中Webbrowser控件使用HwndHost所以webbrowser会在所有控件的前方.所以webbrowser会覆盖所有同级的控件. 现在通过使用Win32API 可以避免这个情况. 最主要 ...

  4. Web安全-之文件上传漏洞场景

    1   上传漏洞危害介绍 上传是Web中最常见的功能,如果上传功能存在设计.编码缺陷,就容易形成上传漏洞,从而成为致命的安全问题,攻击者可以通过上传脚本木马,实现查看/篡改/删除源码和任意涂鸦网页,可 ...

  5. IO到NIO的一个转变

    本内容来源:Jack视频讲解和自己的一个理解. 1.故事还得从网络模型或者IO开始聊起 2.你有想过传统IO真正存在的问题吗? 3.如果你是设计者,IO可以怎样改进? 4.NIO原理分析以及代码实现 ...

  6. ubuntu 下 shell 搜索命令

    一.在当前目录及其子目录查找以mesos开头,并以.jar结尾的文件,并打印出来 sudo find ./ -name mesos*.jar -print 二.whereis, locate 也有类似 ...

  7. 如何用vue-cli3脚手架搭建一个基于ts的基础脚手架

    目录 准备工作 搭建项目 vue 中 ts 语法 项目代理及 webpack 性能优化 其他 忙里偷闲,整理了一下关于如何借助 vue-cli3 搭建 ts + 装饰器 的脚手架,并如何自定义 web ...

  8. Spring Boot 整合 Druid

    Spring Boot 整合 Druid 概述 Druid 是阿里巴巴开源平台上的一个项目,整个项目由数据库连接池.插件框架和 SQL 解析器组成.该项目主要是为了扩展 JDBC 的一些限制,可以让程 ...

  9. Swoole高效跟传统的web开发有什么区别?

    一.swoole的运行模式 Swoole高效跟传统的web开发有什么区别,除了传统的LAMP/LNMP同步开发模式,swoole的异步开发模式是怎么样的. 1.1.传统web开发模式 PHP web开 ...

  10. set容器

    set容器简介: 1) set是一个集合容器,其中所包含的元素是唯一的,集合中的元素按一定的顺序排列.元素插入过程是按排序规则插入,所以不能指定插入位置. 2) set采用红黑树变体的数据结构实现,红 ...