I have an application that launches a thread for drawing a SurfaceView. If I leave the application using the home or back button, I get an "onPause" event where I put the thread in a wait state. In my "onResume" I wake the thread back up.
However, if I "relaunch" the app, I never get an "onResume" event and the application freezes up (I have to do a "Force Quit" on the app). Its not clear to me whether I am starting a new instance of the activity or if it should be waking up the old app. If its launching a new App, I don't understand why it locks up, and if its waking up the old one, why isn't it calling "onResume"? I've tried changing the activity to be singleTask/singleInstance, but it seems to have no effect. Any ideas what might be happening? The activity life-cycle makes sense, but its not clear to me what effect "relaunch" has. Joel --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
