That's insanity. There has to be a way to write a file and prohibit the system from terminating the thread during write operations. If the camera app got the axe while writing an image, we'd have garbage images from the camera, etc. I have to believe there is a way to actually write a file to mass storage, flush and close the stream, and still have enough of a process running afterward to verify the file. If there was no way to do this, the file system would be a chaotic mess of garbage corrupt files. I run a lot of background copy jobs (root explorer) where I am copying whole directories - video files, etc. to/from CIFS shares over WFi. If there was a high probability of the processed being force closed and corrupting the files, this would presumably have come up from time to time, but I have literally never had a corrupt file on Android. All that said I am a Windows desktop and systems developer - never done mobile development on Android. What little I have read tells me Google is not an easy overlord to abide.