这是我的情况:我在Ubuntu 10.04 LTS 64位下有一个XPS
我用eclipse下载了最新的Android SDK。 SDK工作正常,但是当我创建一个新的AVD并运行时。我的AVD加载但未显示。 我不明白,你对我的问题有所了解吗?
感谢的
我从命令行启动我的avd:
romain@XPS-Dak:~/.android$ emulator -verbose -avd Test
emulator: found SDK root at /home/romain/android-sdk-linux
emulator: Android virtual device file at: /home/romain/.android/avd/Test.ini
emulator: virtual device content at /home/romain/.android/avd/Test.avd
emulator: virtual device config file: /home/romain/.android/avd/Test.avd/config.ini
emulator: using core hw config path: /home/romain/.android/avd/Test.avd/hardware-qemu.ini
emulator: Found AVD target API level: 3
emulator: 'magic' skin format detected: 1024x600
emulator: autoconfig: -skin 1024x600
emulator: autoconfig: -skindir (null)
emulator: keyset loaded from: /home/romain/.android/default.keyset
emulator: found SDK root at /home/romain/android-sdk-linux
emulator: trying to load skin file '/home/romain/android-sdk-linux/tools/lib/emulator/skins/dynamic//layout'
emulator: loaded dynamic skin width=1024 height=600 bpp=16
emulator: autoconfig: -kernel /home/romain/android-sdk-linux/platforms/android-3/images//kernel-qemu
emulator: autoconfig: -ramdisk /home/romain/android-sdk-linux/platforms/android-3/images//ramdisk.img
emulator: Using initial system image: /home/romain/android-sdk-linux/platforms/android-3/images//system.img
emulator: autoconfig: -data /home/romain/.android/avd/Test.avd/userdata-qemu.img
emulator: autoconfig: -initdata /home/romain/.android/avd/Test.avd/userdata.img
emulator: autoconfig: -cache /home/romain/.android/avd/Test.avd/cache.img
emulator: Physical RAM size: 512MB
Content of hardware configuration file:
hw.cpu.arch = arm
hw.ramSize = 512
hw.screen = touch
hw.mainKeys = no
hw.trackBall = no
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 = no
disk.cachePartition = yes
disk.cachePartition.path = /home/romain/.android/avd/Test.avd/cache.img
disk.cachePartition.size = 66m
hw.lcd.width = 1024
hw.lcd.height = 600
hw.lcd.depth = 16
hw.lcd.density = 160
hw.lcd.backlight = yes
hw.gpu.enabled = no
hw.camera.back = emulated
hw.camera.front = none
vm.heapSize = 16
hw.sensors.proximity = yes
hw.sensors.magnetic_field = yes
hw.sensors.orientation = yes
hw.sensors.temperature = yes
kernel.path = /home/romain/android-sdk-linux/platforms/android-3/images//kernel-qemu
kernel.parameters = android.checkjni=1
disk.ramdisk.path = /home/romain/android-sdk-linux/platforms/android-3/images//ramdisk.img
disk.systemPartition.initPath = /home/romain/android-sdk-linux/platforms/android-3/images//system.img
disk.systemPartition.size = 200m
disk.dataPartition.path = /home/romain/.android/avd/Test.avd/userdata-qemu.img
disk.dataPartition.size = 200m
avd.name = Test
.
QEMU options list:
emulator: argv[00] = "/home/romain/android-sdk-linux/tools/emulator64-arm"
emulator: argv[01] = "-android-hw"
emulator: argv[02] = "/home/romain/.android/avd/Test.avd/hardware-qemu.ini"
Concatenated QEMU options:
/home/romain/android-sdk-linux/tools/emulator64-arm -android-hw /home/romain/.android/avd/Test.avd/hardware-qemu.ini
emulator: registered 'boot-properties' qemud service
emulator: nand_add_dev: system,size=0xc800000,initfile=/home/romain/android-sdk-linux/platforms/android-3/images//system.img
emulator: mapping 'system' NAND image to /tmp/android-romain/emulator-wbnmYS
emulator: rounding devsize up to a full eraseunit, now c810000
emulator: nand_add_dev: userdata,size=0xc800000,file=/home/romain/.android/avd/Test.avd/userdata-qemu.img
emulator: rounding devsize up to a full eraseunit, now c810000
emulator: registered 'boot-properties' qemud service
emulator: Adding boot property: 'dalvik.vm.heapsize' = '16m'
emulator: Adding boot property: 'qemu.sf.lcd_density' = '160'
emulator: Adding boot property: 'qemu.hw.mainkeys' = '0'
emulator: Adding boot property: 'qemu.sf.fake_camera' = 'back'
emulator: nand_add_dev: cache,size=0x4200000,file=/home/romain/.android/avd/Test.avd/cache.img
emulator: Initializing hardware OpenGLES emulation support
Erreur de segmentation (core dumped)
答案 0 :(得分:16)
你遇到了我在this issue中概述的问题。在SDK libOpenglRender.so
目录中找到您的tools/
,并将其重命名为其他内容。
答案 1 :(得分:0)
尽管如此,这并不是针对OP确切问题的解决方案,而是针对“ android模拟器无法启动,avd”的解决方案。
确保没有其他竞争可以竞争虚拟化。
我正在运行一个无头的Virtual Box映像,并且经历了类似的行为。它会显示为启动状态,但看不到模拟器。 kotlinc
永远不会完成。
答案 2 :(得分:-3)
首次运动时需要耐心等待。加载需要一段时间。