Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid emulator hangs without any error message on windows 7
    text
    copied!<p>** NOTE: I no longer use this environment so there is no way for me to test the answers and accept one. I'm sorry. **</p> <p>I know that there are lots of answers to my question but all of them ask for the erros in the logs messages and I fail to see any error in my logs.</p> <p>I'm trying to run emulator.exe in a windows 7.(1)</p> <p>I tried to run the emulator with vervose. The log is below and, theoretically the most significant messages are the last although I fail to see any significance to them all:</p> <pre><code>C:\Users\ASUS\workspace\Android\android-sdk\tools&gt;emulator.exe -avd 22 -verbose emulator: found SDK root at C:\Users\ASUS\workspace\Android\android-sdk emulator: root virtual device file at C:\Users\ASUS\.android/avd/22.ini emulator: virtual device content at C:\Users\ASUS\.android\avd\22.avd emulator: virtual device config file: C:\Users\ASUS\.android\avd\22.avd/config.ini emulator: locking user data image at C:\Users\ASUS\.android\avd\22.avd/userdata-qemu.img emulator: locking cache image at C:\Users\ASUS\.android\avd\22.avd/cache.img emulator: locking SD Card image at C:\Users\ASUS\.android\avd\22.avd/sdcard.img emulator: ignoring non-existing snapshots at C:\Users\ASUS\.android\avd\22.avd/snapshots.img: No such file or directory emulator: found skin 'QVGA' in directory: C:\Users\ASUS\workspace\Android\android-sdk/platforms\android-8\skins emulator: autoconfig: -skin QVGA emulator: autoconfig: -skindir C:\Users\ASUS\workspace\Android\android-sdk/platforms\android-8\skins emulator: keyset loaded from: C:\Users\ASUS\.android\default.keyset emulator: trying to load skin file 'C:\Users\ASUS\workspace\Android\android-sdk/platforms\android-8\skins/QVGA/layout' emulator: skin network speed: 'full' emulator: skin network delay: 'none' QEMU options list: emulator: argv[00] = "emulator.exe" emulator: argv[01] = "-kernel" emulator: argv[02] = "C:\Users\ASUS\workspace\Android\android-sdk/platforms\android-8\images\/kernel-qemu" emulator: argv[03] = "-netspeed" emulator: argv[04] = "full" emulator: argv[05] = "-netdelay" emulator: argv[06] = "none" emulator: argv[07] = "-initrd" emulator: argv[08] = "C:\Users\ASUS\workspace\Android\android-sdk/platforms\android-8\images\/ramdisk.img" emulator: argv[09] = "-nand" emulator: argv[10] = "system,size=0x4e00000,initfile=C:\Users\ASUS\workspace\Android\android-sdk/platforms\android-8\images\/system.img" emulator: argv[11] = "-nand" emulator: argv[12] = "userdata,size=0x4200000,file=C:\Users\ASUS\.android\avd\22.avd/userdata-qemu.img" emulator: argv[13] = "-nand" emulator: argv[14] = "cache,size=0x4200000,file=C:\Users\ASUS\.android\avd\22.avd/cache.img" emulator: argv[15] = "-hda" emulator: argv[16] = "C:\Users\ASUS\.android\avd\22.avd/sdcard.img" emulator: argv[17] = "-loadvm" emulator: argv[18] = "default-boot" emulator: argv[19] = "-savevm-on-exit" emulator: argv[20] = "default-boot" emulator: argv[21] = "-serial" emulator: argv[22] = "android-kmsg" emulator: argv[23] = "-serial" emulator: argv[24] = "android-qemud" emulator: argv[25] = "-lcd-density" emulator: argv[26] = "120" emulator: argv[27] = "-append" emulator: argv[28] = "qemu=1 console=ttyS0 android.checkjni=1 android.qemud=ttyS1" emulator: argv[29] = "-m" emulator: argv[30] = "96" emulator: argv[31] = "-android-avdname" emulator: argv[32] = "22" emulator: argv[33] = "-android-hw" emulator: argv[34] = "C:\Users\ASUS\AppData\Local\Temp\\AndroidEmulator\TMP4144. tmp" Concatenated QEMU options: emulator.exe -kernel C:\Users\ASUS\workspace\Android\android-sdk/platforms\android-8\images\/kernel-qemu -netspeed full -netdelay none -initrd C:\Users\ASUS\workspace\Android\android-sdk/platforms\android-8\images\/ramdisk.img -nand system ,size=0x4e00000,initfile=C:\Users\ASUS\workspace\Android\android-sdk/platforms\android-8\images\/system.img -nand userdata,size=0x4200000,file=C:\Users\ASUS\.android\avd\22.avd/userdata-qemu.img -nand cache,size=0x4200000,file=C:\Users\ASUS\.android\avd\22.avd/cache.img -hda C:\Users\ASUS\.android\avd\22.avd/sdcard.img -loadvm default-boot -savevm-on-exit default-boot -serial android-kmsg -serial android-qemud -lcd-density 120 -append qemu=1 console=ttyS0 android.checkjni=1 android.qemud=ttyS1 -m 96 -android-avdname 22 -android-hw C:\Users\ASUS\AppData\Local\Temp\\AndroidEmulator\TMP4144.tmp emulator: registered 'boot-properties' qemud service emulator: mapping 'system' NAND image to C:\Users\ASUS\AppData\Local\Temp\\AndroidEmulator\TMP4902.tmp emulator: rounding devsize up to a full eraseunit, now 4e1e000 emulator: registered 'boot-properties' qemud service emulator: Adding boot property: 'dalvik.vm.heapsize' = '24m' emulator: Adding boot property: 'qemu.sf.lcd_density' = '120' emulator: Trace file name is not set emulator: control console listening on port 5554, ADB on port 5555 emulator: sent '0012host:emulator:5555' to ADB server emulator: ping program: C:\Users\ASUS\workspace\Android\android-sdk\tools\ddms.bat emulator: ping command: C:\windows\system32\cmd.exe /C "C:\Users\ASUS\workspace\Android\android-sdk\tools\ddms.bat" ping emulator 10.0 goldfish_fb_get_pixel_format:167: display surface,pixel format: bits/pixel: 16 bytes/pixel: 2 depth: 16 red: bits=5 mask=0xf800 shift=11 max=0x1f green: bits=6 mask=0x7e0 shift=5 max=0x3f blue: bits=5 mask=0x1f shift=0 max=0x1f alpha: bits=0 mask=0x0 shift=0 max=0x0 </code></pre> <p>I am also attaching a screenshot with the look of the emulator when it hangs: EDIT: Wops, I'm not able to attach screenshots, lack of reputation, sorry. <a href="https://i.stack.imgur.com/GH8fu.png" rel="nofollow noreferrer">http://i.stack.imgur.com/GH8fu.png</a></p> <p>I let it "run" for more than 20 minutes and I tried like a dozen of times with the same results.</p> <p>Any hint will be greatly apreciated. Thanks!</p> <p>(1) Full specs of the computer are: Windows 7. 1.66Ghz Intel Atom x2 (32b) 2 GB ram</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload