Question

在我将Hardisk更换为其他MotherBoard i5 3GHz处理器而不重新安装操作系统后，我的AVD仿真器未运行。

操作系统：Ubuntu 10.10

我的模拟器没有通过eclipse运行。当我点击Run As .. Android应用程序。

然后我尝试通过命令提示符运行，然后显示如下错误。

padmakumar@padmakumar-desktop:~$ emulator -avd JellyBelly
Failed to create Context 0x3005
emulator: WARNING: Could not initialize OpenglES emulation, using software renderer.
Segmentation fault

如何解决此错误以运行模拟器？

编辑：使用模拟器-avd JellyBelly -verbose

padmakumar@padmakumar-desktop:~$ emulator -avd JellyBelly -verbose
emulator: found SDK root at /home/padmakumar/android-sdk
emulator: Android virtual device file at: /home/padmakumar/.android/avd/JellyBelly.ini
emulator: virtual device content at /home/padmakumar/.android/avd/JellyBelly.avd
emulator: virtual device config file: /home/padmakumar/.android/avd/JellyBelly.avd/config.ini
emulator: using core hw config path: /home/padmakumar/.android/avd/JellyBelly.avd/hardware-qemu.ini
emulator: Found AVD target API level: 16
emulator: found skin 'WXGA800-7in' in directory: /home/padmakumar/android-sdk/platforms/android-16/skins
emulator: autoconfig: -skin WXGA800-7in
emulator: autoconfig: -skindir /home/padmakumar/android-sdk/platforms/android-16/skins
emulator: found skin-specific hardware.ini: /home/padmakumar/android-sdk/platforms/android-16/skins/WXGA800-7in/hardware.ini
emulator: keyset loaded from: /home/padmakumar/.android/default.keyset
emulator: trying to load skin file '/home/padmakumar/android-sdk/platforms/android-16/skins/WXGA800-7in/layout'
emulator: skin network speed: 'full'
emulator: skin network delay: 'none'
emulator: autoconfig: -kernel /home/padmakumar/android-sdk/system-images/android-16/armeabi-v7a//kernel-qemu
emulator: autoconfig: -ramdisk /home/padmakumar/android-sdk/system-images/android-16/armeabi-v7a//ramdisk.img
emulator: Using initial system image: /home/padmakumar/android-sdk/system-images/android-16/armeabi-v7a//system.img
emulator: autoconfig: -data /home/padmakumar/.android/avd/JellyBelly.avd/userdata-qemu.img
emulator: autoconfig: -initdata /home/padmakumar/.android/avd/JellyBelly.avd/userdata.img
emulator: autoconfig: -cache /home/padmakumar/.android/avd/JellyBelly.avd/cache.img
emulator: autoconfig: -sdcard /home/padmakumar/.android/avd/JellyBelly.avd/sdcard.img
emulator: Physical RAM size: 1024MB

Content of hardware configuration file:
  hw.cpu.arch = arm
  hw.cpu.model = cortex-a8
  hw.ramSize = 1024
  hw.screen = touch
  hw.mainKeys = no
  hw.trackBall = yes
  hw.keyboard = no
  hw.keyboard.lid = no
  hw.keyboard.charmap = qwerty2
  hw.dPad = yes
  hw.gsmModem = yes
  hw.gps = yes
  hw.battery = yes
  hw.accelerometer = yes
  hw.audioInput = yes
  hw.audioOutput = yes
  hw.sdCard = yes
  hw.sdCard.path = /home/padmakumar/.android/avd/JellyBelly.avd/sdcard.img
  disk.cachePartition = yes
  disk.cachePartition.path = /home/padmakumar/.android/avd/JellyBelly.avd/cache.img
  disk.cachePartition.size = 66m
  hw.lcd.width = 800
  hw.lcd.height = 1280
  hw.lcd.depth = 16
  hw.lcd.density = 213
  hw.lcd.backlight = yes
  hw.gpu.enabled = no
  hw.camera.back = emulated
  hw.camera.front = none
  vm.heapSize = 48
  hw.sensors.proximity = yes
  hw.sensors.magnetic_field = yes
  hw.sensors.orientation = yes
  hw.sensors.temperature = yes
  kernel.path = /home/padmakumar/android-sdk/system-images/android-16/armeabi-v7a//kernel-qemu
  kernel.parameters =  android.checkjni=1
  disk.ramdisk.path = /home/padmakumar/android-sdk/system-images/android-16/armeabi-v7a//ramdisk.img
  disk.systemPartition.initPath = /home/padmakumar/android-sdk/system-images/android-16/armeabi-v7a//system.img
  disk.systemPartition.size = 200m
  disk.dataPartition.path = /home/padmakumar/.android/avd/JellyBelly.avd/userdata-qemu.img
  disk.dataPartition.size = 201m
  avd.name = JellyBelly
.
QEMU options list:
emulator: argv[00] = "/home/padmakumar/android-sdk/tools/emulator-arm"
emulator: argv[01] = "-android-hw"
emulator: argv[02] = "/home/padmakumar/.android/avd/JellyBelly.avd/hardware-qemu.ini"
Concatenated QEMU options:
 /home/padmakumar/android-sdk/tools/emulator-arm -android-hw /home/padmakumar/.android/avd/JellyBelly.avd/hardware-qemu.ini
emulator: registered 'boot-properties' qemud service
emulator: nand_add_dev: system,size=0xc800000,initfile=/home/padmakumar/android-sdk/system-images/android-16/armeabi-v7a//system.img
emulator: mapping 'system' NAND image to /tmp/android-padmakumar/emulator-IM8Usk
emulator: rounding devsize up to a full eraseunit, now c810000

emulator: nand_add_dev: userdata,size=0xc900000,file=/home/padmakumar/.android/avd/JellyBelly.avd/userdata-qemu.img
emulator: rounding devsize up to a full eraseunit, now c918000

emulator: registered 'boot-properties' qemud service
emulator: Adding boot property: 'dalvik.vm.heapsize' = '48m'
emulator: Adding boot property: 'qemu.sf.lcd_density' = '213'
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/padmakumar/.android/avd/JellyBelly.avd/cache.img
emulator: Initializing hardware OpenGLES emulation support
Failed to create Context 0x3005
emulator: Can't start OpenGLES renderer?
emulator: WARNING: Could not initialize OpenglES emulation, using software renderer.
emulator: Kernel parameters: qemu.gles=0 qemu=1 console=ttyS0 android.qemud=ttyS1 android.checkjni=1 ndns=2
Segmentation fault

编辑：我创建的任何模拟器都没有运行。

Answer 1

实际上，当您将ADT和SDK升级到第20版时... 这种情况发生在许多人身上，但解决方案是您必须启动“模拟器臂”而不是“模拟器”......所以它可能会起作用...... 有关详细信息，请参阅http://code.google.com/p/android/issues/detail?id=34233此链接...

Answer 2

我遇到了同样的问题

编辑AVD GUI设置。硬件部分，选择新建。点击“财产”下拉列表选择“GPU Emulation”然后“OK” 使用硬件部分的下拉列表将“Gpu Emulation”更改为“YES”。

保存并重试

Answer 3

您可能缺少与模拟器的GLES库的链接，请确保在

中

<Android SDK root>/tools/lib

你有这个.so文件

libEGL_translator.so    
libGLES_CM_translator.so    
libGLES_V2_translator.so    
libOpenglRender.so

您必须将此文件添加到操作系统的全局库集中，您可以从特定路径添加库，只执行以下操作：

sudo gedit /etc/ld.so.conf.d/androidGL.conf
只写入此文件中库的路径，在您的案例<Android SDK root>/tools/lib中，只是一个路径，不指定任何库，该路径中的所有库都将被自动收集
保存并关闭gedit
更新全局库集以使用sudo ldconfig

现在重新尝试运行你的avd。

Answer 4

Failed to create Context 0x3005
emulator: Can't start OpenGLES renderer?

一般情况下，当您的操作系统支持GL驱动器的模拟器大小超出范围时，会发生这种情况。

尝试根据屏幕大小调整模拟器并监控dpi。

希望它会有所帮助。

Answer 5

更改屏幕的分辨率（增加）。这对我来说是个窍门

Answer 6

我也遇到了这个问题。我的症状：

我可以启动Android会话
Eclipse然后显示上述错误
我使用Windows Vista，Android SDK 20和Eclipse 4.2.0

实际问题非常简单（注意我确实有GPU模拟器=是）。事实证明Eclipse无法看到Android会话！

http://www.linkedin.com/groups/Problem-in-executing-code-on-86481.S.138513463

因此我找到了

Android Emulator starts but Eclipse doesn't recognize it

重新启动ADB服务器，并扯掉你的叔叔（也重启Eclipse）解决方案！

我希望能帮到别人。

Answer 7

您必须再次设置所有环境变量路径值。如果您使用安装程序文件来安装sdk，则可能需要再次安装它，因为它与操作系统有一些依赖关系。

Answer 8

如果您使用带有英特尔处理器和NVidia显卡的Windows 8 64位，则应安装Windows更新。具体来说：GForce的NViDIA驱动程序更新，以及HD Graphics的intel公司驱动程序更新。

Answer 9

没有什么可担心这个错误你没有根据平台创建你的Avd Just Make it Proper会向你展示一个例子

1 -Android 2.2，
2 -Api等级8， 3 -SDCard 1024

绝对可以按照平台进行操作！

Answer 10

我遇到了Windows 8 x64的这个问题。确保为您的显卡安装正确的驱动程序。安装正确的驱动程序后，错误消失了。

Answer 11

我所做的就是解决这个问题：

从AVD经理移除设备
再次创建虚拟设备

Answer 12

试试这个：

打开AVD Manager
点击JellyBelly AVD
点击修改
更改“硬件”中的某些值并保存

尝试启动它，让我们知道它是怎么回事

模拟器未运行

12 个答案: