Heh, sorry about the double post, didn't realize I posted that first message.
So I changed my code to handle orientation config changes, rather than letting my activity get killed & recreated, and the problem has gone away. On Aug 30, 10:19 am, David Minor <[email protected]> wrote: > Is the blur done using OpenGL? I am seeing some sort of occasional > deadlock/anr in my GLSurfaceView based app, but only when the phone > wakes up and goes through the blur. > > I have to say that before I found this thread I always wondered why > the blur occurred in some instances and not others. It's not terribly > indicative of what's happening. > > On Aug 18, 9:35 am, Dianne Hackborn <[email protected]> wrote: > > > You can't stop the screen from dimming/blurring. This is always done when > > it rotates without being associated with a physical change (such as a slider > > to reveal a hard keyboard) to give feedback to the user that something is > > happening. > > > On Mon, Aug 17, 2009 at 10:22 PM, SChaser <[email protected]> wrote: > > > > On Aug 3, 11:29 am, Mark Murphy <[email protected]> wrote: > > > > >http://wiki.andmob.org/samplecode > > > > > Look in there for the links to the Rotational Forces series of blog > > > > posts. This one covers what you need: > > > > >http://androidguys.com/?p=2723 > > > > > In your case, you would detect the rotation and change how you draw on > > > > your canvas to match. > > > > Thanks. I tried that and it still doesn't do the trick. > > > > I have a simple layout - a couple of buttons in a listview, a couple > > > of text fields in a listview, and a custom SurfaceView. > > > > The problem is that when I rotate the device (changing orientation), > > > even with the hacks ( and logging to verify that the > > > onConfigurationChange method of my activity is being called), there is > > > still half a second where the screen goes grayish and my SurfaceView > > > is inaccessible to draw on. > > > > Oddly, popping the keyboard in and out also results in an orientation > > > change, but nothing goes gray. > > > > In both cases, based on the log, my methods get called in the same > > > order.and the time from surface destroyed to surface created is > > > virtually identical at about 450 msec. > > > > Help! > > > -- > > Dianne Hackborn > > Android framework engineer > > [email protected] > > > Note: please don't send private questions to me, as I don't have time to > > provide private support, and so won't reply to such e-mails. All such > > questions should be posted on public forums, where I and others can see and > > answer them. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
