title: Opening the camera in a different process
body: <p>One of my apps has a serious activity recreation issue in some <code>Kitkat Samsung</code> devices. The problem appears more frequently when taking pictures, and it isn't observed in crappy <code>Jellybean Samsung</code>s with half the RAM. Logs show a low memory condition, although no <code>OutOfMemoryException</code>s are being thrown. I think there's a more aggressive activity closing policy in <code>Kitkat</code> (or else the default camera app is leaky).</p>
  
  <p>I was wondering whether the OS closes my activities when my app's memory is high, or  instead it closes them when the total memory used by all apps is high. If the OS had a per-process threshold, then maybe opening the camera in a different process might help.</p>
  
  <p>I know it is possible to start a service in its own process using the <code>process</code> attribute in the manifest. Assuming no equivalent attribute exists for <code>Activities</code>, if I started a proxy service in its own process and then started an activity from this service, would the activity run in this process as well?</p>