启动AVD时出错 - “无法打开文件:(null)/system/build.prop:没有这样的文件或目录”

时间:2013-01-25 00:49:30

标签: android android-emulator

当我使用以下命令从CMD窗口打开AVD时:  C:\ Android \ adt-bundle-windows-x86 \ sdk \ tools> emulator.exe -avd Nexus-7-001 -verbose

一切似乎没问题,直到下面的行“无法打开文件:( null)/system/build.prop:没有这样的文件或目录”

虽然模拟器打开,但尝试选择应用程序会产生错误并且“不幸的是启动器已停止。”

我已卸载并重新下载了ADT =>一样的问题。你能否告诉我是否有办法确保删除所有的ADT?此问题也可能是由旧ADT(以前版本的Eclipse)的残余引起的,还是完全不同的?在Win-7和Vista OS系统上遇到同样的问题。

C:\Android\adt-bundle-windows-x86\sdk\tools>emulator.exe -avd Nexus-7-001 -verbose
.
.
.
emulator: Trace file name is not set

emulator: autoconfig: -scale 0.569531
emulator: Could not open file: (null)/system/build.prop: No such file or directory
emulator: control console listening on port 5554, ADB on port 5555
emulator: can't connect to ADB server: connection refused
emulator: ping program: C:\Android\adt-bundle-windows-x86\sdk\tools\ddms.bat
emulator: ping command: C:\Windows\system32\cmd.exe /C "C:\Android\adt-bundle-windows-x86\sdk\tools\ddms.bat" ping emulator 21.0.1.0 "NVIDIA Corporati
on" "GeForce G210M/PCI/SSE2" "3.0.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

8 个答案:

答案 0 :(得分:1)

1)检查系统映像是否正确安装。

2)检查你所在的显卡的驱动程序。

答案 1 :(得分:1)

我以前遇到过这个问题。要解决此问题,只需使用管理权限启动Eclipse即可。它适用于Windows 7和Windows 8.1。

答案 2 :(得分:1)

这可能是与Android SDK和/或Java未正确设置或过时设置的环境变量路径相关的问题。仔细检查他们是否指出他们指向正确的资源。 您还可以尝试使用提升的命令提示符运行命令并首先重新加载ADB。

答案 3 :(得分:1)

build.prop文件包含Android系统的基本信息。因此,如果找不到该文件,系统(或启动器)将崩溃。 如果系统映像已损坏(下载时可能出错或Android系统搞砸了),您最好使用SDK管理器删除平台。或者,您可以删除已安装SDK的文件夹中platform-<api level you are using>system-images中的platforms文件夹。完成后重新下载平台,AVD应该再次运行!

答案 4 :(得分:0)

它可能与该行无关。

初始化OpenGL时似乎存在一个常见问题(Google地球的工作正常吗?)。在这些情况下,在命令行中,尝试使用“emulator-arm”而不是“emulator”。如果它工作,它可能是一个驱动程序问题(尝试重新安装您的图形驱动程序)。

如果不起作用,请尝试发布整个日志(模拟器-verbose -avd mydevice)。

答案 5 :(得分:0)

我遇到了几乎相同的问题,解决方案是:

  1. 检查内核的API级别
  2. 使用相同的API运行AVD。
  3. 我的错误是:

    D:\programs\adt-bundle-windows-x86_64-20130522\sdk\tools>emulator-arm -kernel D
    \programs\adt-bundle-windows-x86_64-20130522\sdk\emulator-root\Kernel\zImage -s
    ow-kernel -verbose -avd NexusS
    emulator: found SDK root at D:\programs\adt-bundle-windows-x86_64-20130522\sdk
    emulator: Android virtual device file at: C:\Users\Laci\.android\avd\NexusS.ini
    emulator: virtual device content at C:\Users\Laci\.android\avd\NexusS.avd
    emulator: virtual device config file: C:\Users\Laci\.android\avd\NexusS.avd/con
    ig.ini
    emulator: using core hw config path: C:\Users\Laci\.android\avd\NexusS.avd/hard
    are-qemu.ini
    emulator: Found AVD target API level: 8
    emulator: 'magic' skin format detected: 480x800
    emulator: autoconfig: -skin 480x800
    emulator: autoconfig: -skindir (null)
    emulator: keyset loaded from: C:\Users\Laci\.android\default.keyset
    emulator: found SDK root at D:\programs\adt-bundle-windows-x86_64-20130522\sdk
    emulator: trying to load skin file 'D:\programs\adt-bundle-windows-x86_64-20130
    22\sdk/tools/lib/emulator/skins/dynamic//layout'
    emulator: loaded dynamic skin width=480 height=800 bpp=16
    
    emulator: autoconfig: -ramdisk D:\programs\adt-bundle-windows-x86_64-20130522\s
    k/platforms\android-8\images\/ramdisk.img
    emulator: Using initial system image: D:\programs\adt-bundle-windows-x86_64-201
    0522\sdk/platforms\android-8\images\/system.img
    emulator: autoconfig: -data C:\Users\Laci\.android\avd\NexusS.avd/userdata-qemu
    img
    emulator: autoconfig: -initdata C:\Users\Laci\.android\avd\NexusS.avd/userdata.
    mg
    emulator: autoconfig: -cache C:\Users\Laci\.android\avd\NexusS.avd/cache.img
    emulator: Physical RAM size: 256MB
    
    Content of hardware configuration file:
      hw.cpu.arch = arm
      hw.ramSize = 256
      hw.screen = touch
      hw.mainKeys = yes
      hw.trackBall = no
      hw.keyboard = no
      hw.keyboard.lid = yes
      hw.keyboard.charmap = qwerty2
      hw.dPad = no
      hw.gsmModem = yes
      hw.gps = yes
      hw.battery = no
      hw.accelerometer = yes
      hw.audioInput = yes
      hw.audioOutput = yes
      hw.sdCard = yes
      disk.cachePartition = yes
      disk.cachePartition.path = C:\Users\Laci\.android\avd\NexusS.avd/cache.img
      disk.cachePartition.size = 66m
      hw.lcd.width = 480
      hw.lcd.height = 800
      hw.lcd.depth = 16
      hw.lcd.density = 240
      hw.lcd.backlight = yes
      hw.gpu.enabled = no
      hw.camera.back = none
      hw.camera.front = none
      vm.heapSize = 32
      hw.sensors.proximity = yes
      hw.sensors.magnetic_field = yes
      hw.sensors.orientation = yes
      hw.sensors.temperature = yes
      kernel.path = D:\programs\adt-bundle-windows-x86_64-20130522\sdk\emulator-roo
    \Kernel\zImage
      kernel.parameters =  android.checkjni=1
      disk.ramdisk.path = D:\programs\adt-bundle-windows-x86_64-20130522\sdk/platfo
    ms\android-8\images\/ramdisk.img
      disk.systemPartition.initPath = D:\programs\adt-bundle-windows-x86_64-2013052
    \sdk/platforms\android-8\images\/system.img
      disk.systemPartition.size = 200m
      disk.dataPartition.path = C:\Users\Laci\.android\avd\NexusS.avd/userdata-qemu
    img
      disk.dataPartition.size = 2g
      avd.name = NexusS
    .
    QEMU options list:
    emulator: argv[00] = "emulator-arm"
    emulator: argv[01] = "-show-kernel"
    emulator: argv[02] = "-android-hw"
    emulator: argv[03] = "C:\Users\Laci\.android\avd\NexusS.avd/hardware-qemu.ini"
    Concatenated QEMU options:
     emulator-arm -show-kernel -android-hw C:\Users\Laci\.android\avd\NexusS.avd/ha
    dware-qemu.ini
    emulator: registered 'boot-properties' qemud service
    emulator: nand_add_dev: system,size=0xc800000,initfile=D:\programs\adt-bundle-w
    ndows-x86_64-20130522\sdk/platforms\android-8\images\/system.img
    emulator: mapping 'system' NAND image to C:\Users\Laci\AppData\Local\Temp\\Andr
    idEmulator\TMPE31B.tmp
    emulator: rounding devsize up to a full eraseunit, now c810000
    
    emulator: nand_add_dev: userdata,size=0x80000000,file=C:\Users\Laci\.android\av
    \NexusS.avd/userdata-qemu.img
    emulator: rounding devsize up to a full eraseunit, now 80010000
    
    emulator: registered 'boot-properties' qemud service
    emulator: Adding boot property: 'dalvik.vm.heapsize' = '32m'
    emulator: Adding boot property: 'qemu.sf.lcd_density' = '240'
    emulator: Adding boot property: 'qemu.hw.mainkeys' = '1'
    emulator: Adding boot property: 'qemu.sf.fake_camera' = 'none'
    emulator: nand_add_dev: cache,size=0x4200000,file=C:\Users\Laci\.android\avd\Ne
    usS.avd/cache.img
    emulator: Initializing hardware OpenGLES emulation support
    emulator: ERROR: Could not load OpenGLES emulation library: Could not load DLL!
    emulator: WARNING: Could not initialize OpenglES emulation, using software rend
    rer.
    emulator: Kernel parameters: qemu.gles=0 qemu=1 console=ttyS0 android.qemud=tty
    1 android.checkjni=1 ndns=2
    emulator: Trace file name is not set
    
    emulator: autoconfig: -scale 1
    serial0 console
    emulator: Could not open file: (null)/system/build.prop: No such file or direct
    ry
    emulator: control console listening on port 5554, ADB on port 5555
    emulator: sent '0012host:emulator:5555' to ADB server
    emulator: ping program: D:\programs\adt-bundle-windows-x86_64-20130522\sdk\tool
    \ddms.bat
    emulator: ping command: C:\Windows\system32\cmd.exe /C "D:\programs\adt-bundle-
    indows-x86_64-20130522\sdk\tools\ddms.bat" ping emulator 22.0.1.0 "" "" ""
    Uncompressing Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing
    Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing Linux...Uncom
    ressing Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing Linux
    ..Uncompressing Linux...Uncompressing Linux...Uncompressing Linux...Uncompressi
    g Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing Linux...Unc
    mpressing Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing Lin
    x...Uncompressing Linux...Uncompressing Linux...Uncompressing Linux...Uncompres
    ing Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing Linux...U
    compressing Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing L
    nux...Uncompressing Linux...Uncompressing Linux...Uncompressing Linux...Uncompr
    ssing Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing Linux..
    Uncompressing Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing
    Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing Linux...Uncom
    ressing Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing Linux
    ..Uncompressing Linux...Uncompressing Linux...Uncompressing Linux...Uncompressi
    g Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing Linux...Unc
    mpressing Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing Lin
    x...Uncompressing Linux...Uncompressing Linux...Uncompressing Linux...Uncompres
    ing Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing Linux...U
    compressing Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing L
    nux...Uncompressing Linux...Uncompressing Linux...Uncompressing Linux...Uncompr
    ssing Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing Linux..
    Uncompressing Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing
    Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing Linux...Uncom
    ressing Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing Linux
    ..Uncompressing Linux...Uncompressing Linux...Uncompressing Linux...Uncompressi
    g Linux...Uncompressing Linux...Uncompressing Linux...Uncompressing Linux...Unc
    mpressing Linux...Uncompressing Linux...Uncompressing Linux...
    
    ran out of input data
    
     -- System haltedemulator: User-config was not changed.
    

答案 6 :(得分:0)

尝试从头开始重新创建AVD,如果问题仍然存在于整个日志中(模拟器-verbose -avd mydevice)

答案 7 :(得分:0)

重新启动您的模拟器以及SDK。