Join FlipAndroid.COM Telegram Group: https://t.me/joinchat/F_aqThGkhwcLzmI49vKAiw


Emulador de Android no se inicia

Estoy luchando para conseguir el lanzamiento del emulador con éxito después de intentar por más de 2 semanas. Realmente puedo usar alguna ayuda con el problema o consejos para solucionar el mismo problema.

He podido lanzar el emulador con éxito en mi máquina casera usando la configuración muy similar. Se produce un error cuando me conecto desde mi PC de trabajo, creo que hay una configuración que puede estar deteniendo esto, pero no tengo idea de lo que es la configuración y no veo ningún error en los registros que me pueden ayudar a identificar el problema . Este es un problema general con mis colegas, así que estoy seguro de que es una política o configuración de registro que se ha establecido en nuestras estaciones de trabajo.

Si alguien me puede ayudar a identificar la configuración que está deteniendo el lanzamiento del emulador, puedo trabajar con el equipo de TI para realizar los cambios necesarios.

Mi configuración es

  • Android Studio 1.2.1.1
  • SDK / AVD Manager v 24.3.3
  • Windows 7 x64
  • 16 GB de RAM
  • DELL E6540 Laptop | DELL Optiplex 780 de escritorio
  • HAXM instalado
  • Opciones de CPU probadas: Intel x86 / x86_x64 & Arm v7a
  • Opciones de RAM probadas: 768MB, 1GB y 2GB
  • GPU de host: intentado con y apagado
  • La virtualización está habilitada en BIOS

El dispositivo virtual se crea bien, pero nunca se lanza correctamente. Nunca he visto una ventana abierta, he esperado más de 2 horas en varias ocasiones.

Aquí están los registros de dos AVD que creé

AVD 1

Arm v7a | 768 MB de RAM | Android 5.1.1 | API 22 | Host GPU desactivado

AVD 1 | Arm v7a | 768 MB de RAM | Android 5.1.1 | API 22 | Host GPU desactivado

Salida:

emulator:Found AVD name 'avd1' emulator:Found AVD target architecture: arm emulator:Looking for ranchu emulator backed for arm CPU emulator:Probing program: ./emulator64-ranchu-arm.exe emulator:Probing program: ./emulator-ranchu-arm.exe emulator:Probing path for: emulator64-ranchu-arm.exe emulator:Probing path for: emulator-ranchu-arm.exe emulator:Looking for emulator-arm to emulate 'arm' CPU emulator:Probing program: ./emulator-arm.exe emulator:Found target-specific emulator binary: ./emulator-arm.exe emulator:GPU emulation is disabled emulator:Quoted param: [./emulator-arm.exe] emulator:Quoted param: [@avd1] emulator:Quoted param: [-verbose] emulator: found SDK root at C:\Users\Anon\AppData\Local\Android\sdk emulator: Android virtual device file at: C:\Users\Anon\.android\avd\avd1.ini emulator: virtual device content at C:\Users\Anon\.android\avd\avd1.avd emulator: virtual device config file: C:\Users\Anon\.android\avd\avd1.avd/config.ini emulator: using core hw config path: C:\Users\Anon\.android\avd\avd1.avd/hardware-qemu.ini emulator: Found AVD target API level: 22 emulator: Read property file at C:\Users\Anon\AppData\Local\Android\sdk/system-images\android-22\default\armeabi-v7a\/build.prop emulator: No boot.prop property file found. emulator: 'magic' skin format detected: 768x1280 emulator: autoconfig: -skin 768x1280 emulator: autoconfig: -skindir (null) emulator: keyset loaded from: C:\Users\Anon\.android\default.keyset emulator: found magic skin width=768 height=1280 bpp=16 emulator: autoconfig: -kernel C:\Users\Anon\AppData\Local\Android\sdk/system-images\android-22\default\armeabi-v7a\/kernel-qemu emulator: Auto-detect: Kernel image requires legacy device naming scheme. emulator: Auto-detect: Kernel does not support YAFFS2 partitions. emulator: autoconfig: -ramdisk C:\Users\Anon\AppData\Local\Android\sdk/system-images\android-22\default\armeabi-v7a\/ramdisk.img emulator: Using initial system image: C:\Users\Anon\AppData\Local\Android\sdk/system-images\android-22\default\armeabi-v7a\/system.img emulator: autoconfig: -initdata C:\Users\Anon\.android\avd\avd1.avd/userdata.img emulator: autoconfig: -cache C:\Users\Anon\.android\avd\avd1.avd/cache.img emulator: Physical RAM size: 768MB emulator: GPU emulation is disabled emulator: WARNING: CPU acceleration only works with x86/x86_64 system images. Content of hardware configuration file: hw.cpu.arch = arm hw.cpu.model = cortex-a8 hw.ramSize = 768 hw.screen = touch hw.mainKeys = no hw.trackBall = no hw.keyboard = yes hw.keyboard.lid = no hw.keyboard.charmap = qwerty2 hw.dPad = no hw.gsmModem = yes hw.gps = yes hw.battery = yes hw.accelerometer = yes hw.audioInput = yes hw.audioOutput = yes hw.sdCard = no disk.cachePartition = yes disk.cachePartition.path = C:\Users\Anon\.android\avd\avd1.avd/cache.img disk.cachePartition.size = 66m hw.lcd.width = 768 hw.lcd.height = 1280 hw.lcd.depth = 16 hw.lcd.density = 320 hw.lcd.backlight = yes hw.gpu.enabled = no hw.initialOrientation = portrait hw.camera.back = none hw.camera.front = none vm.heapSize = 64 hw.sensors.proximity = yes hw.sensors.magnetic_field = yes hw.sensors.orientation = yes hw.sensors.temperature = yes hw.useext4 = yes kernel.path = C:\Users\Anon\AppData\Local\Android\sdk/system-images\android-22\default\armeabi-v7a\/kernel-qemu kernel.parameters = androidboot.hardware=goldfish android.checkjni=1 kernel.newDeviceNaming = no kernel.supportsYaffs2 = no disk.ramdisk.path = C:\Users\Anon\AppData\Local\Android\sdk/system-images\android-22\default\armeabi-v7a\/ramdisk.img À¿)pV)ußK³ªc¥ú&µß>Oí‡yù®ù×=Vš§Ùïq—#ÊÿŠÿ¿Ù&Òßué—!MáÍFåÿ¾U)›±„yþ¿ƒð—ˆ_ˆøõÊ'Ò?{'é×@zQ¿Ü•úíÈQêñ©•„yÖ/þ[â—"~ü«|ü¶,%~em.img disk.systemPartition.size = 550m disk.dataPartition.path = C:\Users\Anon\.android\avd\avd1.avd/userdata-qemu.img disk.dataPartition.initPath = C:\Users\Anon\.android\avd\avd1.avd/userdata.img disk.dataPartition.size = 550m avd.name = avd1 . QEMU options list: emulator: argv[00] = "./emulator-arm.exe" emulator: argv[01] = "-android-hw" emulator: argv[02] = "C:\Users\Anon\.android\avd\avd1.avd/hardware-qemu.ini" Concatenated QEMU options: ./emulator-arm.exe -android-hw C:\Users\Anon\.android\avd\avd1.avd/hardware-qemu.ini emulator: registered 'boot-properties' qemud service emulator: Using kernel serial device prefix: ttyS emulator: Ramdisk image contains fstab.goldfish file emulator: Found format of system partition: 'ext4' emulator: Found format of userdata partition: 'ext4' emulator: Found format of cache partition: 'ext4' emulator: system partition format: ext4 emulator: Mapping 'system' partition image to C:\Users\Anon\AppData\Local\Temp\\AndroidEmulator\TMP2084.tmp emulator: nand_add_dev: system,size=0x22600000,file=C:\Users\Anon\AppData\Local\Temp\\AndroidEmulator\TMP2084.tmp,initfile=C:\Users\Anon\AppData\Local\Android\sdk/system-images\android-22\default\armeabi-v7a\/system.img,pagesize=512,extrasize=0 emulator: userdata partition format: ext4 emulator: nand_add_dev: userdata,size=0x22600000,file=C:\Users\Anon\.android\avd\avd1.avd/userdata-qemu.img,initfile=C:\Users\Anon\.android\avd\avd1.avd/userdata.img,pagesize=512,extrasize=0 emulator: cache partition format: ext4 emulator: Creating empty cache partition image at: C:\Users\Anon\.android\avd\avd1.avd/cache.img Creating filesystem with parameters: Size: 69206016 Block size: 4096 Blocks per group: 32768 Inodes per group: 4224 Inode size: 256 Journal blocks: 1024 Label: Blocks: 16896 Block groups: 1 Reserved block group size: 7 Created filesystem with 11/4224 inodes and 1302/16896 blocks emulator: nand_add_dev: cache,size=0x4200000,file=C:\Users\Anon\.android\avd\avd1.avd/cache.img,pagesize=512,extrasize=0 emulator: registered 'boot-properties' qemud service emulator: Adding boot property: 'dalvik.vm.heapsize' = '64m' emulator: Adding boot property: 'qemu.sf.lcd_density' = '320' emulator: Adding boot property: 'qemu.hw.mainkeys' = '0' emulator: Adding boot property: 'qemu.sf.fake_camera' = 'none' emulator: Kernel parameters: qemu.gles=0 qemu=1 console=ttyS0 android.qemud=ttyS1 androidboot.hardware=goldfish android.checkjni=1 ndns=3 emulator: autoconfig: -scale 0.801562 

AVD 2

Intel Atom x86 | 1536 MB RAM | Android 4.3.1 | API 18 | Utilizar la GPU de host activada

AVD 2 | Intel Atom x86 | 1536 MB RAM | Android 4.3.1 | API 18 | Utilizar la GPU de host activada

 emulator:Found AVD name 'avd2' emulator:Found AVD target architecture: x86 emulator:Looking for ranchu emulator backed for x86 CPU emulator:Probing program: ./emulator64-ranchu-x86.exe emulator:Probing program: ./emulator-ranchu-x86.exe emulator:Probing path for: emulator64-ranchu-x86.exe emulator:Probing path for: emulator-ranchu-x86.exe emulator:Looking for emulator-x86 to emulate 'x86' CPU emulator:Probing program: ./emulator-x86.exe emulator:Found target-specific emulator binary: ./emulator-x86.exe emulator:GPU emulation enabled using 'host' mode emulator:Quoted param: [./emulator-x86.exe] emulator:Quoted param: [@avd2] emulator:Quoted param: [-verbose] emulator: found SDK root at C:\Users\Anon\AppData\Local\Android\sdk emulator: Android virtual device file at: C:\Users\Anon\.android\avd\avd2.ini emulator: virtual device content at C:\Users\Anon\.android\avd\avd2.avd emulator: virtual device config file: C:\Users\Anon\.android\avd\avd2.avd/config.ini emulator: using core hw config path: C:\Users\Anon\.android\avd\avd2.avd/hardware-qemu.ini emulator: Found AVD target API level: 18 emulator: Read property file at C:\Users\Anon\AppData\Local\Android\sdk/system-images\android-18\default\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: keyset loaded from: C:\Users\Anon\.android\default.keyset emulator: trying to load skin file 'C:\Users\Anon\AppData\Local\Android\sdk/tools/lib/emulator/skins/dynamic//layout' emulator: loaded dynamic skin width=768 height=1280 bpp=16 emulator: autoconfig: -kernel C:\Users\Anon\AppData\Local\Android\sdk/system-images\android-18\default\x86\/kernel-qemu emulator: Auto-detect: Kernel image requires legacy device naming scheme. emulator: Auto-detect: Kernel does support YAFFS2 partitions. emulator: autoconfig: -ramdisk C:\Users\Anon\AppData\Local\Android\sdk/system-images\android-18\default\x86\/ramdisk.img emulator: Using initial system image: C:\Users\Anon\AppData\Local\Android\sdk/system-images\android-18\default\x86\/system.img emulator: autoconfig: -initdata C:\Users\Anon\.android\avd\avd2.avd/userdata.img emulator: autoconfig: -cache C:\Users\Anon\.android\avd\avd2.avd/cache.img emulator: Physical RAM size: 1536MB emulator: GPU emulation enabled using 'host' mode emulator: CPU Acceleration: working emulator: CPU Acceleration status: HAX (version 2) is installed and usable. emulator: Target arch = 'x86' emulator: Auto-config: -qemu -cpu qemu32 Content of hardware configuration file: hw.cpu.arch = x86 hw.cpu.model = qemu32 hw.ramSize = 1536 hw.screen = touch hw.mainKeys = no hw.trackBall = no hw.keyboard = yes hw.keyboard.lid = no hw.keyboard.charmap = qwerty2 hw.dPad = no hw.gsmModem = yes hw.gps = yes hw.battery = yes hw.accelerometer = yes hw.audioInput = yes hw.audioOutput = yes hw.sdCard = no disk.cachePartition = yes disk.cachePartition.path = C:\Users\Anon\.android\avd\avd2.avd/cache.img disk.cachePartition.size = 66m hw.lcd.width = 768 hw.lcd.height = 1280 hw.lcd.depth = 16 hw.lcd.density = 320 hw.lcd.backlight = yes hw.gpu.enabled = yes hw.gpu.mode = host hw.initialOrientation = portrait hw.camera.back = emulated hw.camera.front = emulated vm.heapSize = 64 hw.sensors.proximity = yes hw.sensors.magnetic_field = yes hw.sensors.orientation = yes hw.sensors.temperature = yes hw.useext4 = yes kernel.path = C:\Users\Anon\AppData\Local\Android\sdk/system-images\android-18\default\x86\/kernel-qemu kernel.parameters = androidboot.hardware=goldfish clocksource=pit android.checkjni=1 kernel.newDeviceNaming = no kernel.supportsYaffs2 = yes disk.ramdisk.path = C:\Users\Anon\AppData\Local\Android\sdk/system-images\android-18\default\x86\/ramdisk.img disk.systemPartition.initPath = C:\Users\Anon\AppData\Local\Android\sdk/system-images\android-18\default\x86\/system.img disk.systemPartition.size = 281m disk.dataPartition.path = C:\Users\Anon\.android\avd\avd2.avd/userdata-qemu.img disk.dataPartition.initPath = C:\Users\Anon\.android\avd\avd2.avd/userdata.img disk.dataPartition.size = 200m avd.name = avd2 . QEMU options list: emulator: argv[00] = "./emulator-x86.exe" emulator: argv[01] = "-enable-hax" emulator: argv[02] = "-android-hw" emulator: argv[03] = "C:\Users\Anon\.android\avd\avd2.avd/hardware-qemu.ini" Concatenated QEMU options: ./emulator-x86.exe -enable-hax -android-hw C:\Users\Anon\.android\avd\avd2.avd/hardware-qemu.ini emulator: registered 'boot-properties' qemud service emulator: Using kernel serial device prefix: ttyS emulator: Ramdisk image contains fstab.goldfish file emulator: Could not extract format of system partition! emulator: Could not extract format of userdata partition! emulator: Could not extract format of cache partition! emulator: Probing system image file for partition type: C:\Users\Anon\AppData\Local\Android\sdk/system-images\android-18\default\x86\/system.img emulator: system partition format: yaffs2 emulator: Mapping 'system' partition image to C:\Users\Anon\AppData\Local\Temp\\AndroidEmulator\TMPA30C.tmp emulator: nand_add_dev: system,size=0x11900000,file=C:\Users\Anon\AppData\Local\Temp\\AndroidEmulator\TMPA30C.tmp,initfile=C:\Users\Anon\AppData\Local\Android\sdk/system-images\android-18\default\x86\/system.img emulator: rounding devsize up to a full eraseunit, now 11904000 emulator: Probing userdata image file for partition type: C:\Users\Anon\.android\avd\avd2.avd/userdata.img emulator: userdata partition format: yaffs2 emulator: nand_add_dev: userdata,size=0xc800000,file=C:\Users\Anon\.android\avd\avd2.avd/userdata-qemu.img,initfile=C:\Users\Anon\.android\avd\avd2.avd/userdata.img emulator: rounding devsize up to a full eraseunit, now c810000 emulator: cache partition format: yaffs2 emulator: Creating empty cache partition image at: C:\Users\Anon\.android\avd\avd2.avd/cache.img emulator: nand_add_dev: cache,size=0x4200000,file=C:\Users\Anon\.android\avd\avd2.avd/cache.img emulator: registered 'boot-properties' qemud service emulator: Adding boot property: 'dalvik.vm.heapsize' = '64m' emulator: Adding boot property: 'qemu.sf.lcd_density' = '320' emulator: Adding boot property: 'qemu.hw.mainkeys' = '0' emulator: Adding boot property: 'qemu.sf.fake_camera' = 'both' emulator: Initializing hardware OpenGLES emulation support emulator: OpenGL Vendor=[Google (Intel)] emulator: OpenGL Renderer=[Android Emulator OpenGL ES Translator (Intel(R) HD Graphics 4600)] emulator: OpenGL Version=[OpenGL ES 2.0 (4.0.0 - Build 9.18.10.3220)] emulator: Adding boot property: 'ro.opengles.version' = '131072' emulator: device fd:988 emulator: Kernel parameters: qemu.gles=1 qemu=1 console=ttyS0 android.qemud=ttyS1 androidboot.hardware=goldfish clocksource=pit android.checkjni=1 ndns=3 emulator: trying to find: C:\Users\Anon\AppData\Local\Android\sdk\tools/bios.bin emulator: trying to find: C:\Users\Anon\AppData\Local\Android\sdk\tools/lib/pc-bios/bios.bin emulator: trying to find: C:\Users\Anon\AppData\Local\Android\sdk\tools/vgabios-cirrus.bin emulator: trying to find: C:\Users\Anon\AppData\Local\Android\sdk\tools/lib/pc-bios/vgabios-cirrus.bin emulator: autoconfig: -scale 0.801562 

AVD 3

ARM | 512 MB de RAM | Android 2.3.3 | API 10 | Utilizar la GPU de host desactivada

AVD 3 | ARM | 512 MB de RAM | Android 2.3.3 | API 10 | Utilizar la GPU de host desactivada

 emulator:Found AVD name 'avd3' emulator:Found AVD target architecture: arm emulator:Looking for ranchu emulator backed for arm CPU emulator:Probing program: ./emulator64-ranchu-arm.exe emulator:Probing program: ./emulator-ranchu-arm.exe emulator:Probing path for: emulator64-ranchu-arm.exe emulator:Probing path for: emulator-ranchu-arm.exe emulator:Looking for emulator-arm to emulate 'arm' CPU emulator:Probing program: ./emulator-arm.exe emulator:Found target-specific emulator binary: ./emulator-arm.exe emulator:GPU emulation is disabled emulator:Quoted param: [./emulator-arm.exe] emulator:Quoted param: [@avd3] emulator:Quoted param: [-verbose] emulator: found SDK root at C:\Users\Anon\AppData\Local\Android\sdk emulator: Android virtual device file at: C:\Users\Anon\.android\avd\avd3.ini emulator: virtual device content at C:\Users\Anon\.android\avd\avd3.avd emulator: virtual device config file: C:\Users\Anon\.android\avd\avd3.avd/config.ini emulator: using core hw config path: C:\Users\Anon\.android\avd\avd3.avd/hardware-qemu.ini emulator: Found AVD target API level: 10 emulator: No build.prop property file found. emulator: No boot.prop property file found. emulator: Cannot find target CPU architecture, defaulting to 'arm' emulator: Cannot find target CPU ABI, defaulting to 'armeabi' emulator: found skin 'WQVGA400' in directory: C:\Users\Anon\AppData\Local\Android\sdk/platforms\android-10\skins emulator: autoconfig: -skin WQVGA400 emulator: autoconfig: -skindir C:\Users\Anon\AppData\Local\Android\sdk/platforms\android-10\skins emulator: found skin-specific hardware.ini: C:\Users\Anon\AppData\Local\Android\sdk/platforms\android-10\skins/WQVGA400/hardware.ini emulator: keyset loaded from: C:\Users\Anon\.android\default.keyset emulator: trying to load skin file 'C:\Users\Anon\AppData\Local\Android\sdk/platforms\android-10\skins/WQVGA400/layout' emulator: skin network speed: 'full' emulator: skin network delay: 'none' emulator: autoconfig: -kernel C:\Users\Anon\AppData\Local\Android\sdk/platforms\android-10\images\/kernel-qemu emulator: Auto-detect: Kernel image requires legacy device naming scheme. emulator: Auto-detect: Kernel does support YAFFS2 partitions. emulator: autoconfig: -ramdisk C:\Users\Anon\AppData\Local\Android\sdk/platforms\android-10\images\/ramdisk.img emulator: Using initial system image: C:\Users\Anon\AppData\Local\Android\sdk/platforms\android-10\images\/system.img emulator: autoconfig: -data C:\Users\Anon\.android\avd\avd3.avd/userdata-qemu.img emulator: autoconfig: -initdata C:\Users\Anon\.android\avd\avd3.avd/userdata.img emulator: autoconfig: -cache C:\Users\Anon\.android\avd\avd3.avd/cache.img emulator: Physical RAM size: 256MB emulator: GPU emulation is disabled emulator: WARNING: CPU acceleration only works with x86/x86_64 system images. emulator: Target arch = 'arm' Content of hardware configuration file: hw.cpu.arch = arm hw.ramSize = 256 hw.screen = touch hw.mainKeys = yes hw.trackBall = yes hw.keyboard = yes hw.keyboard.lid = yes hw.keyboard.charmap = qwerty2 hw.dPad = no hw.gsmModem = yes hw.gps = yes hw.battery = yes hw.accelerometer = yes hw.audioInput = yes hw.audioOutput = yes hw.sdCard = yes disk.cachePartition = yes disk.cachePartition.path = C:\Users\Anon\.android\avd\avd3.avd/cache.img disk.cachePartition.size = 66m hw.lcd.width = 240 hw.lcd.height = 400 hw.lcd.depth = 16 hw.lcd.density = 120 hw.lcd.backlight = yes hw.gpu.enabled = no hw.initialOrientation = portrait hw.camera.back = none hw.camera.front = none vm.heapSize = 32 hw.sensors.proximity = yes hw.sensors.magnetic_field = yes hw.sensors.orientation = no hw.sensors.temperature = yes hw.useext4 = yes kernel.path = C:\Users\Anon\AppData\Local\Android\sdk/platforms\android-10\images\/kernel-qemu kernel.parameters = androidboot.hardware=goldfish android.checkjni=1 kernel.newDeviceNaming = no kernel.supportsYaffs2 = yes disk.ramdisk.path = C:\Users\Anon\AppData\Local\Android\sdk/platforms\android-10\images\/ramdisk.img disk.systemPartition.initPath = C:\Users\Anon\AppData\Local\Android\sdk/platforms\android-10\images\/system.img disk.systemPartition.size = 200m disk.dataPartition.path = C:\Users\Anon\.android\avd\avd3.avd/userdata-qemu.img disk.dataPartition.size = 200m avd.name = avd3 . QEMU options list: emulator: argv[00] = "./emulator-arm.exe" emulator: argv[01] = "-android-hw" emulator: argv[02] = "C:\Users\Anon\.android\avd\avd3.avd/hardware-qemu.ini" Concatenated QEMU options: ./emulator-arm.exe -android-hw C:\Users\Anon\.android\avd\avd3.avd/hardware-qemu.ini emulator: registered 'boot-properties' qemud service emulator: Using kernel serial device prefix: ttyS emulator: No fstab.goldfish file in ramdisk image emulator: Probing system image file for partition type: C:\Users\Anon\AppData\Local\Android\sdk/platforms\android-10\images\/system.img emulator: system partition format: yaffs2 emulator: Mapping 'system' partition image to C:\Users\Anon\AppData\Local\Temp\\AndroidEmulator\TMPE615.tmp emulator: nand_add_dev: system,size=0xc800000,file=C:\Users\Anon\AppData\Local\Temp\\AndroidEmulator\TMPE615.tmp,initfile=C:\Users\Anon\AppData\Local\Android\sdk/platforms\android-10\images\/system.img emulator: rounding devsize up to a full eraseunit, now c810000 emulator: Probing userdata image file for partition type: C:\Users\Anon\.android\avd\avd3.avd/userdata-qemu.img emulator: userdata partition format: yaffs2 emulator: nand_add_dev: userdata,size=0xc800000,file=C:\Users\Anon\.android\avd\avd3.avd/userdata-qemu.img emulator: rounding devsize up to a full eraseunit, now c810000 emulator: cache partition format: yaffs2 emulator: nand_add_dev: cache,size=0x4200000,file=C:\Users\Anon\.android\avd\avd3.avd/cache.img emulator: registered 'boot-properties' qemud service emulator: Adding boot property: 'dalvik.vm.heapsize' = '32m' emulator: Adding boot property: 'ro.config.low_ram' = 'true' emulator: Adding boot property: 'qemu.sf.lcd_density' = '120' emulator: Adding boot property: 'qemu.hw.mainkeys' = '1' emulator: Adding boot property: 'qemu.sf.fake_camera' = 'none' emulator: Kernel parameters: qemu.gles=0 qemu=1 console=ttyS0 android.qemud=ttyS1 androidboot.hardware=goldfish android.checkjni=1 ndns=3 emulator: autoconfig: -scale 1 

5 Solutions collect form web for “Emulador de Android no se inicia”

¿Ha instalado correctamente el HAXM?

Me encuentro con el mismo problema antes, antes de aprender que HAXM aún no está habilitado después de descargarlo en android sdk manager. Introduzca aquí la descripción de la imagen

Necesita algunos pasos a seguir para obtener la mejor experiencia del emulador Android * con el controlador Intel HAXM.

Requisitos previos

Intel HAXM requiere el SDK de Android * para ser instalado (versión 17 o superior). Para obtener más información, consulte el sitio web de desarrolladores de Android * ( http://developer.android.com/sdk/ ).

 System Requirements Hardware Requirements: Intel® processor with support for Intel® VT-x, Intel® EM64T (Intel® 64), and Execute Disable (XD) Bit functionality At least 1 GB of available RAM Supported Operating Systems: Microsoft Windows* 8 and 8.1 (32/64-bit) Microsoft Windows* 7 (32/64-bit) Microsoft Windows Vista* (32/64-bit) Important: Intel HAXM cannot be used on systems without an Intel processor, or with an Intel processor that lacks the hardware features described in the "Hardware Requirements" section above. To determine the capabilities of your Intel processor, visit http://ark.intel.com/ Additionally, Intel HAXM can be used only with Android* x86 emulator images provided by Intel. Intel HAXM cannot be used with ARM* Android* emulator images or non-Intel x86 Android* emulator images. 
  1. En el directorio principal de SDK. A pesar de que el gestor de SDK dice "Instalado" en realidad significa que se descargó el ejecutable HAXM de Intel. Deberá ejecutar el instalador desde el directorio "extras" para instalarlo.

2. Extraiga el instalador dentro del directorio "extras" y siga las instrucciones de instalación de su plataforma.

Introduzca aquí la descripción de la imagen

Instalación de Intel® HAXM en Windows *

Advertencia: La instalación de Intel HAXM fallará si su sistema no cumple con los requisitos del sistema, incluido el soporte para las características del procesador Intel, como Intel VT (Intel Virtualization Technology).

Introduzca aquí la descripción de la imagenIntroduzca aquí la descripción de la imagenIntroduzca aquí la descripción de la imagenIntroduzca aquí la descripción de la imagen

Después de todos los pasos funcionará correctamente. Introduzca aquí la descripción de la imagen

Espero que ayude … heres Documentación de Intel

Una idea que puede intentar es crear un AVD para una versión antigua de Android (como 2.1 o 2.2). En mi experiencia esas versiones comienzan razonablemente rápido incluso bajo emulación. Puede que no sea útil para crear proyectos, pero debería ayudarlo a determinar si el emulador funciona en general.

Limpie los datos de las carpetas C:\Users\<username>\.android\ avd and cache Luego inicie la creación de AVD desde cero a través de Introduzca aquí la descripción de la imagen

Estoy utilizando API 22 : Android 5.1.1 . Yo estaba enfrentando el mismo problema entonces he descargado la última imagen del sistema de android sdk manager para ejecutar Nexus 5 emulador.

La imagen del sistema fue

API de Google ARM EABI v7a Imagen del sistema

Y luego seleccionó esta imagen del sistema mientras creaba un dispositivo virtual en el Administrador de dispositivos virtuales de Android. Sólo asegúrese de que ha marcado la casilla de verificación de una instantánea de la tienda . Ahora ejecuta tu emulador.

Debe decidir qué emulador desea utilizar y seleccionar la imagen del sistema de acuerdo con ella. Por ejemplo, Nexus 5 tiene un procesador de brazo (como eso). También debe descargar todas las imágenes del sistema para sus emuladores. Introduzca aquí la descripción de la imagen

Usted podría intentar estos:

1) La piel se establece en WVGA800 por defecto intente cambiar a HVGA .

2) A veces es el problema con la graphic card and drivers (aunque usted mencionó que probó esto en el sistema diferente, pero compruebe si los controladores son iguales?)

3) A veces el problema quizás debido al screen size de screen size del emulador. Intente cambiar lcd.height, lcd.width, skin.name, skin.path en los archivos de configuración

FlipAndroid es un fan de Google para Android, Todo sobre Android Phones, Android Wear, Android Dev y Aplicaciones para Android Aplicaciones.