I tried to reproduce what you are describing, but no luck:
http://androidgecko.com/project.zip
Look and say if I missed something.
Know that when another application comes to the fore (the camera in this case), the android can kill previous processes to free up memory (not even for the operations described in the Google documentation, but the entire PID), which can cause problems.
I have seen this behavior, especially on older phones, when you launch Gallery or Camera apps from within your app.
This is one of the reasons that applications like Facebook have their own Gallery / Camera implementation (so the PID is not killed because it's the first one).
However, even if the PID is killed, you should see the activity, that is, its onCreate
with savedInstanceState
, which is not null, should fire .. and then onActivityResult
..
check out my example and let me know how I can reproduce your problem.
Androidgecko
source share