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

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. 记一次将本地工程上传到github的过程

    记一次将本地工程上传到github的过程 1.首先,进入本地工程所在文件夹,运行git init将工程初始化为git仓库: XH@DESKTOP-82MT9LU MINGW64 ~/Desktop/t ...

  2. python实现一可升降式的冒泡排序

    前几天看了个冒泡的排序,这里手敲了一下代码,简单记录如下: def bubble_sort(arr, order='asc'): # #可选升降序的冒泡排序, order>0升序,order&l ...

  3. 【Android - 自定义View】之View的draw过程解析

    draw(绘制)过程的作用是将View绘制到屏幕上面.View中有 draw() 方法和 onDraw() 方法,但onDraw()方法是空方法:ViewGroup中没有draw()方法,也没有onD ...

  4. [ch04-03] 用神经网络解决线性回归问题

    系列博客,原文在笔者所维护的github上:https://aka.ms/beginnerAI, 点击star加星不要吝啬,星越多笔者越努力. 4.3 神经网络法 在梯度下降法中,我们简单讲述了一下神 ...

  5. python-模块,异常,环境管理器

    模块 Module 什么是模块: 1.模块是一个包含有一系列数据,函数,类等组成的程序组 2.模块是一个文件,模块文件名通常以.py结尾 作用: 1.让一些相关数据,函数,类等有逻辑的组织在一起,使逻 ...

  6. 浅析vue混入(mixin)

    vue中的混入,可以在一定程度上提高代码的复用性.通俗来说,混入类似于“继承”,当前组件对象继承于组件对象,一般情况下遵循“就近原则”.但是与继承不同的是,继承一般都跟随着属性的重写与合并,混入在不同 ...

  7. PAT(甲级)2019年秋季考试

    第一题用搜索,超时了,待补 更新第一题思路 dfs + 剪枝,首先确定 n的最后一位数字肯定是9,为什么呢,因为 任意两个相邻的数肯定互为质数(gcd=1),所以 n 的末尾肯定是9,这样n+1产生的 ...

  8. Linux入侵痕迹检测方案【华为云技术分享】

    背景说明 扫描是一切入侵的基础,通过扫描来发现目标主机是否为活动主机.操作系统是什么版本.开放了哪些服务等.扫描技术纷繁复杂,新的扫描技术也层出不穷,不可能穷举所有扫描技术,下面按入侵步骤对主机扫描. ...

  9. ubuntu部署.Net Core3.1(Nginx+pm2)

    前言 虽然.NetCore已经出来很久了,但是很多初学者还是不会在linux部署.所以写一篇初学者在ubuntu下部署Core的全过程,大佬请无视. 环境搭建 ubuntu18.04 NetCore3 ...

  10. vue反向代理(解决跨域)

    1,vue中有提供反向代理的接口,就是config/index.js中的proxyTable,我的脚手架版本是2.9.6,proxyTable配置初始为空,如下图. 2,将proxyTable配置如下 ...