[android-developers] Re: OpenGL and pause/resume

2009-10-29 Thread boris
I had the same problem, I added android:launchMode="singleTask" to the activity and it worked. See http://groups.google.com/group/android-beginners/msg/06627e594f5a04c8 What do you mean by releasing GLSurfaceView on onDestroy? On Sep 22, 2:23 pm, Robert Green wrote: > You can but you only need t

[android-developers] Re: OpenGL and pause/resume

2009-09-23 Thread Robert Green
if you send me your project, I will be happy to take a look and debug it for you. If not, I don't know what to say. It could be a problem with your projection init or perhaps you have some thread that runs things and it hasn't restarted or initted correctly. On Sep 23, 7:17 am, Guian wrote: >

[android-developers] Re: OpenGL and pause/resume

2009-09-23 Thread Guian
I did what you said and it helped : I don't have this error anymore: ERROR/SurfaceComposerClient(15353): using an invalid surface id=0, identity=1431 should be 1435 However I still get a black screen on resuming the app... the problem is ... elsewhere :( anyway, thank you a lots for your answe

[android-developers] Re: OpenGL and pause/resume

2009-09-23 Thread Guian
allright, I'll check that all. I think I reload my textures but I keep my old vertex buffer IDs... thx a lot! On 22 sep, 19:23, Robert Green wrote: > You can but you only need the callback information for knowing when > the surface has been created/modified or destroyed.  The renderer will > ge

[android-developers] Re: OpenGL and pause/resume

2009-09-22 Thread Robert Green
You can but you only need the callback information for knowing when the surface has been created/modified or destroyed. The renderer will get the same callbacks. The important things are these: Your activity should only be creating one GLSurfaceView in onCreate and releasing it in onDestroy You

[android-developers] Re: OpenGL and pause/resume

2009-09-22 Thread Guian
thx for your answer. I'm not familiar with it, should I use a SurfaceHolder.Callback to be notified when the surface is created and destroy ? On 21 sep, 23:15, Robert Green wrote: > Check to make sure that at the time of resume, you're not hanging on > to old surface holders or anything like tha

[android-developers] Re: OpenGL and pause/resume

2009-09-21 Thread Robert Green
Check to make sure that at the time of resume, you're not hanging on to old surface holders or anything like that. I use GLSurfaceView onPause and onResume and they work correctly for me on the G1 and Emulator. On Sep 21, 8:18 am, Guian wrote: > well, I did put those lines in the onPause/onResu

[android-developers] Re: OpenGL and pause/resume

2009-09-21 Thread Guian
well, I did put those lines in the onPause/onResume methods but still have the black screen with this error in the logcat: ERROR/SurfaceComposerClient(15353): using an invalid surface id=0, identity=1431 should be 1435 Doesn't seem exactly the same error... can anybody help please ? On 30 août

[android-developers] Re: OpenGL and pause/resume

2009-08-30 Thread Cor
In the mean time I found this was a classic RTFM case ;-) If you use GLSurfaceView you have to call view.onPause() and view.onResume() respectively in the activities onPause() and anResume () methods --~--~-~--~~~---~--~~ You received this message because you are