Geek Answers Handbook

The emulator does not start the OpenGL application, the messages of which "Unfortunately, OpenGL ES 2.0 Basic has stopped"

I got an OpenGl example through the developer's site.

My problem is that it does not start the application.

Here is my logcat:

10-17 14:43:12.574: E/Trace(684): error opening trace file: No such file or directory (2) 10-17 14:43:13.523: D/libEGL(684): Emulator without GPU support detected. Fallback to software renderer. 10-17 14:43:13.523: D/libEGL(684): loaded /system/lib/egl/libGLES_android.so 10-17 14:43:13.573: I/Choreographer(684): Skipped 44 frames! The application may be doing too much work on its main thread. 10-17 14:43:13.643: D/gralloc_goldfish(684): Emulator without GPU emulation detected. 10-17 14:43:13.653: W/dalvikvm(684): threadid=11: thread exiting with uncaught exception (group=0x40a13300) 10-17 14:43:13.653: E/AndroidRuntime(684): FATAL EXCEPTION: GLThread 78 10-17 14:43:13.653: E/AndroidRuntime(684): java.lang.IllegalArgumentException: No configs match configSpec 10-17 14:43:13.653: E/AndroidRuntime(684): at android.opengl.GLSurfaceView$BaseConfigChooser.chooseConfig(GLSurfaceView.java:863) 10-17 14:43:13.653: E/AndroidRuntime(684): at android.opengl.GLSurfaceView$EglHelper.start(GLSurfaceView.java:1024) 10-17 14:43:13.653: E/AndroidRuntime(684): at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1401) 10-17 14:43:13.653: E/AndroidRuntime(684): at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1240) 10-17 14:43:14.233: I/Choreographer(684): Skipped 83 frames! The application may be doing too much work on its main thread. 10-17 14:43:16.963: I/Choreographer(684): Skipped 260 frames! The application may be doing too much work on its main thread. 10-17 14:43:16.963: I/Process(684): Sending signal. PID: 684 SIG: 9

What I tried:

  • I searched the Internet and found that someone can do this by setting up GPU emulation as yes
  • Updated my AVD emulator

How my emulator is configured:

  • Target-4.1.2. - API level 16
  • ARM (armeabi-v7a)
  • Size: 1000mib
  • Leather: default (WVGA800)
  • Equipment: MaxVm: 48; LCD abstract density: 240; Device Memory Size: 512; GPU emulation: yes;

Can someone help me fix this problem?

I want to add that I use Eclipse, and I tried reinstalling everything (Eclipse and SDK) so far no luck.

+8
android android-emulator opengl-es
source share
2 answers

GPU emulator bandwidth is unstable, I recommend using a real device. He accidentally crashed my OpenGL ES 2.0 applications on both Win7 (Intel GPU) and Ubuntu (nVidia GPU).

As you can see, it reports that it cannot detect OpenGL and returns to the software rendering.

+2
source share

I tried the exact same steps and I was able to run it here. I could see the Greenish Triangle.

Make sure you build the project with API level 14 (which I did)

Also try the classic AVD recreation step.

0
source share

More articles:


All Articles