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 仿真器 无法启动排查的更多相关文章
- Android应用程序启动时发生AndroidRuntime : ClassNotFoundException for Activity class的解决方法
在android应用程序启动时抛出下面异常导致启动失败:07-09 17:12:35.709: ERROR/AndroidRuntime(3866): Uncaught handler: thread ...
- 【Android端 APP 启动时长获取】启动时长获取方案及具体实施
一.什么是启动时长? 1.启动时长一般包括三种场景,分别是:新装包的首次启动时长,冷启动时长.热启动时长 冷启动 和 热启动 : (1)冷启动:当启动应用时,后台没有该程序的进程,此时启动的话系统会分 ...
- Android Studio 无法启动模拟器的一种可能是你装的是Ghost版的系统
我遇到的问题是,打开模拟器,进度条走到最后,突然出现了emulator error,然后模拟器就无法启动(不好意思当时没有截图).我是在Ghost版 win7系统下运行Android Studio 的 ...
- android Activity的启动模式
Android中Activity启动模式详解 在Android中每个界面都是一个Activity,切换界面操作其实是多个不同Activity之间的实例化操作.在Android中Activity的启 ...
- Android Activity的启动过程
文章编辑的太长了,请移步我的csdn博客:http://blog.csdn.net/xyh269 Android Activity的启动过程原文链接:http://blog.csdn.net/xyh2 ...
- Android手机app启动的时候第一个Activity必须是MainActivity吗
原文:Android手机app启动的时候第一个Activity必须是MainActivity吗 Android手机APP启动的第一个Activity是可以自己设置的,不是必须的MainActivity ...
- Android 4.2启动代码分析(一)
Android系统启动过程分析 Android系统的框架架构图如下(来自网上): Linux内核启动之后----->就到Android的Init进程 ----->进而启动Android ...
- Cocos2d-x3.3RC0的Android编译Activity启动流程分析
本文将从引擎源代码Jni分析Cocos2d-x3.3RC0的Android Activity的启动流程,以下是具体分析. 1.引擎源代码Jni.部分Java层和C++层代码分析 watermark/2 ...
- Android开机动画启动流程
android开机动画启动流程 从android的Surface Flinger服务启动分析知道,开机动画是在SurfaceFlinger实例通过调用startBootAnim()启动的. 下面我 ...
随机推荐
- day20191113笔记
默写:程序=数据结构+操作系统. 一.文件上传 1.导入commons-fileupload.jar commons-io.jar 2.配置 <bean id="multipartRe ...
- Vue-Property-Decorator源码分析
概述 vue-property-decorator是基于vue组织里vue-class-component所做的拓展,先来了解一下vue-class-component Vue-Class-Compo ...
- 少用float浮动?
在css中,float 属性定义元素在哪个方向浮动.也是我在css样式中常用到的属性,后来浏览了一些公司项目代码,发现float属性极少有人使用.随后做了一些调查和研究: 1.在ie6以下,float ...
- Vue引入
Vue引入 概念: 1.el:实例 new Vue({ el: '#app' }) // 实例与页面挂载点一一对应 // 一个页面中可以出现多个实例对应多个挂载点 // 实例只操作挂载点内部内容 2. ...
- c 语言I博客作业02
这个作业属于哪个课程 C语言程序设计1 这个作业要求在哪里 https://edu.cnblogs.com/campus/zswxy/SE2019-2/homework/8687 我在这个课程的目标是 ...
- Python常用转义字符
\ 在行尾时是 续行符 \\ 反斜杠符号 \' 单引号 \" 双引号 \a 响铃 \b 退格 \e 转义 \000 空 \n 换行 \v 纵向制表符 \t ...
- CF832D Misha, Grisha and Underground
有一棵n个节点的树,一共q 次询问 每次询问给定3个点,求两条起点终点在这三个点上且不完全重合的路径的最多公共节点数 简单LCA求距离,令a为汇合点,那么答案就是(dis(a,b) + dis(a,c ...
- 大数据之Linux基础
回顾这一个多月以来闭关学大数据的一些相关重要知识,就当复习,顺便以备以后查看 Linux学习第一步自然是安装Linux. 关于Linux 首先介绍下Linux,Linux系统很多程序员开发者其实都耳熟 ...
- Mysql基础03-函数
函数 字符串函数 函数 用法 CONCAT(S1,S2,......,Sn) 连接S1,S2,......,Sn为一个字符串 CONCAT_WS(s, S1,S2,......,Sn) 同CONCAT ...
- Keras开发一个神经网络
关于Keras:Keras是一个高级神经网络API,用Python编写,能够在TensorFlow,CNTK或Theano之上运行. 使用一下命令安装: pip install keras 在Kera ...