Incorrect save on second image field in Mobile UI

[joebordes]

If you have 2 custom fields of photo type in a module, when you try to press the second field to invoke the camera, you are pushed back to listview (as if you already saved the record) without having the chance to access the camera and capture the picture. Moreover, as a result of this unexpected 'save' operation, the picture stored in the first field gets erased.