It happens exclusively when I suddenly turn off the display when my app is started again, i.e. the sequence is something like:
Activity.onStart() -> Activity.onResume() -> GLSurfaceView.onResume() - > Activity.onPause() -> GLSurfaceView.onPause() -> "Surface is invalid (no such device)" in log An assumption: GlSurfaceView cannot be repainted because it's still paused. In other words, it is tried to be repainted by the system when the GLSurfaceView is already paused. I guess this is the phenomena mentioned by Fredrik Lanker (Sony Ericsson) in July 2011: http://markmail.org/message/l7ffpanbpozs6nu7 The only difference is that my GLSurfaceView is paused for a different reason (which is irrelevant). Can I ignore it? On máj. 19, 06:32, Yan <[email protected]> wrote: > At what exact points in your code does this happen? > > On May 17, 9:55 pm, Tamás Kovács <[email protected]> wrote: > > > > > > > > > This is a logcat ERROR entry which I get in 3 (three) instance at the > > same time, but the game I develop works fine. I'm just worried because > > this is an error, not a warning. I get the 3 identical entries when my > > game screen (GLSurface) is resumed due to Activity.onResume(). The > > screen behavior is absolutely fine in the same practice. > > > Details: my game is subject to GLSurfaceView.onResume() as well as > > orientation change (i.e. it's set to landscape in the manifest and in > > configchanges, but obviously Android needs to change orientation to > > landscape when I return from my home screen to the game). So I get the > > error shortly after the GL thread is resumed (during texture > > reloading). > > > Should I worry? It's an Error, after all. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
