This bug's been around quite a while; there are a number of issues on http://b.android.com related to it. It's plagued one of my apps in particular for the better part of a year.
While there are some tips for reducing its occurrence (like the eglWaitGL() call you mentioned), and I seem to have stopped it from happening on my N1, I still get sporadic user reports of it. But AFAIK, nobody's linked it to a specific colorspace config before... and that may indeed be what "fixed" it for me, as I've moved to RGB565 wherever possible to conserve memory. If you could create a minimal test case APK for it - one which reliably produces the freeze - that'd be a BIG help. One of the major difficulties with this bug has been its sporadic nature; it's really hard to tell when it's fixed. I'm sure the same applies to any platform or hardware engineers who may have worked on it from their side too. String -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
