Open limikael opened 10 years ago
Some more info, the following was tried in the emulator.
If I press the home button, and then re-activate the app, things work ok. However, if I press the back button and then re-activate it doesn't work.
I think that in the first case the app get's paused, whereas in the later case it gets destroyed and created, and it is this that doesn't work.
I placed I console log in the onDestroy method, and this log comes out when pressing the back button, which is how I draw this conclusion. Also, together with that log I see:
06-02 05:12:09.820: E/libEGL(1535): call to OpenGL ES API with no current context (logged once per thread)
This is on destroy. On re-activating the app I see this trace:
06-02 05:18:15.660: D/ejecta(1583): Event: Canvas was created
But the screen is just empty.
Let me know what you need more!
After some fiddling around my intuition tells me that maybe this has something to do with the API version, but I could be completely wrong since I'm a noob when it comes to Android development.
I am however able to reproduce the issue with a simple test that just creates a GLSurfaceView and I asked a question here about that:
http://stackoverflow.com/questions/23999057/simple-glsurfaceview-test-crashes
I'm also encounter this issue on Galaxy Tab 2 running Android 4.4.4 (Kitkat).
06-27 18:57:46.039 9238-9238/com.impactjs.ejecta.sample E/libEGL: call to OpenGL ES API with no current context (logged once per thread)
Hi,
As soon as I switch to another activity and back again the app Ejecta-X freezes. This happens both in the emulator and on my Nexus 7 tablet.
Sorry for the lack of further information, I'm happy to do more tests and provide what you need. What information would be useful for investigating this?