Run Android OpenGL in Background as Rendering Resource for App?

Question

I want to run an Android OpenGL-ES surface in the background of my app to provide dynamic graphical resources (bitmaps, etc.) for the application. The OpenGl GLSurfaceView is not the visible screen of my app; it is only used as a rendering factory to manufacture graphics for use by the main activity.

Does anyone know how to make an Android GLSurfaceView run when it is not an active view? The Google Android documentation is clear that when a GLSurfaceView loses its status as a primary view, the surface is destroyed along with all of its resources.

Is there any way to keep a GLSurfaceView and its associated GLSurfaceView.Renderer running normally when it is not (and never is) the application's primary view?

I think that you can do it using RenderBuffer object, attaching it to a FBO and drawing to it. — Nativ, Nov 06 '13 at 14:12
or(worked for me), set it's view size 1pixel&1pixel, put it visible(user cannot see it) and in OnDraw bind FBO to the main texture and render it — Nativ, Nov 11 '13 at 13:07
related for opengl: http://stackoverflow.com/questions/3191978/how-to-use-glut-opengl-to-render-to-a-file — Ciro Santilli OurBigBook.com, Feb 16 '17 at 10:22

score 8 · Answer 1 · answered Jul 15 '11 at 13:05

For what you're trying to do, you should skip the GLSurfaceView entirely. Since you just want to do some OpenGL offscreen rendering, you can make use of an EGL pixel buffer and convert it to a bitmap. See this thread on anddev for a solution. I've used it very successfully in a few of my apps.

The implementation towards the bottom of that thread is a bit buggy, since it does some very simple EGL choosing. I'd recommend implementing a more robust chooser, which you can find in Robert Green's GLWallpaperService, if you'd like.

Another change I ended up making was to remove the vertical pixel mirroring. I just ended up flipping my viewport in onSurfaceCreate, rather than manually flip rendered pixels when writing to the bitmap.

Good luck!

score 2 · Answer 2 · answered Jun 29 '11 at 17:12

2

I would strongly recommend you don't try to do this. Many current drivers on Android devices don't support multiple active GL contexts across processes; if the driver does support this, the feature has not been exercised much because Android itself does not do this, so there are likely to be nasty bugs that result.

Multiple GL context is only being used by the platform starting with Android 3.0.

answered Jun 29 '11 at 17:12

hackbod

90,665
16
140
154

Does this mean 2 GLSurfaceViews in one window will not work prior to Android 3.0? – Michael Apr 24 '13 at 09:00

Run Android OpenGL in Background as Rendering Resource for App?

2 Answers2

Linked