Android emulator blank on "newer" AVDs, even after several hours, on decent machine w/HAXM -


setup: win7/64 android studio 1.4 , 2.0 preview 5 on same machine (i5-2450m w/4 gb, haxm 6.0.1 supported , set @ 2 gb).

i have not tried exhaustively, on handful of avd combinations have tried, can avds running android 2.2 ("froyo", arm, api 8) boot (takes few minutes , slow, works).

anything newer (from api 15-23; on api 15 i've tried both arm , x86 atom) shows emulator window never shows inside phone's screen besides blackness, if left 14 hours.

i know there other emulators out there, wondering why, on decent setup, isn't working.

android studio's output window says this, quickly, , never thereafter:

emulator.exe -avd nexus_5_api_15 emulator: device fd:516 haxm working , emulator runs in fast virt mode emulator: emulator window out of view , recentered emulator: updatechecker: skipped version check 

if try run app anyway, says:

device shell command: pm install -r "/data/local/tmp/com....." error: not access package manager.  system running? 

from on (even hours later, , whether tell install app or not) emulator-x86.exe takes 848 mb of ram, , cpu varies 0-25, although 0.

avd details follows:

name: nexus_5_api_15 cpu/abi: intel atom (x86) path: ...\.android\avd\nexus_5_api_15.avd target: android api 15 (api level 15) skin: 1080x1920 sd card: ...\.android\avd\nexus_5_api_15.avd\sdcard.img snapshot: true hw.lcd.density: 480 hw.dpad: no avd.ini.encoding: utf-8 hw.camera.back: none disk.datapartition.size: 300m skin.dynamic: yes hw.keyboard: yes hw.device.hash2: md5:2fa0e16c8cceb7d385183284107c0c88 hw.ramsize: 768 tag.id: default tag.display: default hw.sdcard: yes hw.device.manufacturer: google hw.mainkeys: no hw.accelerometer: yes hw.trackball: no hw.device.name: nexus 5 hw.sensors.proximity: yes hw.battery: yes hw.sensors.orientation: yes hw.audioinput: yes hw.camera.front: none hw.gps: yes snapshot.present: true vm.heapsize: 64 

i'm not looking "just use genymotion" answer, reason why might occur without giving actual indication of boot problem in output.

update

running logcat shows this. whenever got line saying waiting service surfaceflinger... wait few seconds , output more, pausing @ next waiting service surfaceflinger.... 25 mb of output, , counting...

try clearing emulator /data partition (wipe user data option available in avd manager).


Comments

Popular posts from this blog

get url and add instance to a model with prefilled foreign key :django admin -

css - Make div keyboard-scrollable in jQuery Mobile? -

ruby on rails - Seeing duplicate requests handled with Unicorn -