Interesting....very interesting. I just programmed an application that does this routine, and I didn't realize why the Parent activity has been destroyed before it went to onActivitityResult() after lots of hours trying to bug it, and using all "launchMode=.." that makes logic, I couldn't find a solution to this matter.
Then I noticed that on my Galaxy Tab 7" which runs on 2.3.3, the activity is actually destroyed before coming back, but on my Galaxy S2, it goes straight forward to the onActivityResult() and works perfectly fine. There must be some kind of a solution for this situation. I believe other applications use much more memory than mine and still works perfectly fine with it. so if anyone happens to find a solution it would be much appreciated. thanks a lot. -- 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
