i dont know exactly how its done i did little research and i use egl context created in java but rest is handled in c++, in order to delete oglbuffers you need to delete them inside opengl thread. So where ever you place 'glDraw' function you should make a switch like if(killme) { glDeleteBuffers, glDeleteTextures etc }

if drawing function will work then freeing should be called inside that function, anyway i am not sure how does that work in native activity (i told you the case for java es initialized thing)

anyway it should work the same for native activity, this is the one thing i hate about android : )

any way i am not sure if this is my apps fault but when its supposed to be paused (because android pauses the activity it should be reopened very fast (they say that) but the thing is it starts the app again, and uses the data from old ogl context which is now used by something else. (this is the case for wrong buffer, texture etc deletion) the best way would be to handle home and back button and kill the process (stop activity, kill it destory it) so app will crash and whole resources that are stored for the game are being set that can be rewritten (giving Appname has stopped working on exit) well i wasnt aware of the thing that i need to destroy all objects, in opengl thread, need to write a specific function that does that (few hundred opengl glDeleteXX(); calls .... so i warn you you better list all the things you need to delete right away so you wont have to digh through whole code of the project just to see what have you created...

btw take a look at: https://groups.google.com/forum/#!topic/android-ndk/bWD2vMXOyDo

especially that sounds reasonable:

You do not need to destroy *anything* --- Android does it for you. In

fact, you can't stop it! The last point you can do anything OpenGL
related is in the SurfaceHolder.Callback.onSurfaceDestroyed() method,
which is called immediately before the context gets destroyed. As soon
as you return from this method, your OpenGL context is invalid and you
must not touch it (or bad stuff happens).

It would be nice if Android actually caught attempts to access the
context when it was invalid and failed gracefully, but... this does not
seem to happen.

What we do in our system (we make an interface layer allowing people to
write apps using OpenKODE and EGL and OpenGL, on top of various
platforms including Android: see http://antixlabs.com) is that when the
game calls eglSwapBuffers() from the rendering thread it takes and
releases a semaphore. When onSurfaceDestroyed() is called from the UI
thread we take this semaphore and wait. This causes the rendering thread
to halt at a known point. Once this has happened we change state so that
the rendering thread no longer accesses the OpenGL context, and then
allow Android to proceed to destroy it. It was a pig to get right, but
does actually appear to work.

i really dont know for now, i just did a quick test because

in order to setup egl in java you have to set GLSurfaceView etc it has something like Pause and Resume Method

//this is code from java activity

	@Override
	protected void onPause() {
		super.onPause();

		if (rendererSet) {
//			glSurfaceView.onPause();
		}
	}

	@Override
	protected void onResume() {
		super.onResume();

		if (rendererSet) {
//			glSurfaceView.onResume();
		}
	}

like you see i commented these out and hit home button then reopened the applciation it opened in less than 2 seconds

i tried even to open other programs after launching my app, and then had to hold home button and select my app, it opened in less than 2 seconds again, so i think its up to you if you want to delete contex or pause the rendering just by using some switch liek if(notpaused) glDraw();

im not sure what happnes if other application will request the memory that is taken by your app (if it will take it) or wont launch at all

so hitting back button doesnt seem to pause the application (looks like home button does that only)

i think overriding these onpause onresume will allow you to do pretty much the same thing, still hittong back button needs to be properly handled (properly destroying all shaders, textures, buffers) <- that pisses me off coz i have lots of classes that have implemented destructors and they are 'static' meaning i dont do someclass * ashader = new someclass(); then delete ashader;

its just someclass ashader;