gpt4 book ai didi

Android 模拟器在 Windows 7 上挂起,没有任何错误消息

转载 作者:行者123 更新时间:2023-11-29 02:13:38 25 4
gpt4 key购买 nike

** 注意:我不再使用这个环境,所以我无法测试答案并接受答案。对不起。 **

我知道我的问题有很多答案,但所有答案都在日志消息中询问错误,而我在日志中没有看到任何错误。

我正在尝试在 Windows 7 中运行 emulator.exe。(1)

我试着用 vervose 运行模拟器。日志在下面,理论上最重要的消息是最后一条消息,尽管我看不出它们对所有消息有任何意义:

C:\Users\ASUS\workspace\Android\android-sdk\tools>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

我还附上了模拟器挂起时的截图:编辑:Wops,我无法附上屏幕截图,缺乏声誉,抱歉。 http://i.stack.imgur.com/GH8fu.png

我让它“运行”了 20 多分钟,我尝试了十几次,结果都一样。

任何提示将不胜感激。谢谢!

(1) 计算机的完整规范为:Windows 7的。1.66Ghz 英特尔凌动 x2 (32b)2 GB 内存

最佳答案

尝试在运行于 AMD phenom 处理器的 ubuntu 中启动 API 15 x86 时,我遇到了类似的问题。 API 19 x86 可以正常启动,API 12 arm 也可以。 API 12 x86 不可用。我一直尝试启动 API 15 x86,它会卡在同一个 goldfish_fb_pixel_format:... .

我的解决方案是使用 API 15 arm (armeabi-v7a) 而不是 x86。它现在似乎正在工作。

问题可能出在我的系统配置上。我使用的是较旧的 AMD 芯片组,SSSE3 不可用。可能是系统镜像下载错误:我在下载 API 15 x86 时网络连接速度很慢,也许是下载出错了?我怀疑它..但可能。当我下载 API 15 arm 时,它既好又快。无论哪种情况,我现在都很满意我有一些东西可以测试 API 15。

有两个地方可以删除下载的图片。

  1. ~/Android/system-images/android-<version>/default/<platform>
  2. ~/.android/avd/<the_avd_you_created>.avd

如果您想尝试重新下载,请确保先删除这两个目录,然后重新启动 AVD 管理器。

关于Android 模拟器在 Windows 7 上挂起,没有任何错误消息,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/5769374/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com