User downloads and installs Facebook App from Marketplace. User taps Facebook and logs in. User taps Photo in upper middle and selects Camera and takes a photo. The photo is taken but the user is never prompted to either select the photo or retake the photo (as is the case with Flame 2.0). User's only options seem to either restart the device or long presses homescreen to exit Facebook. However, when user returns to that same area within Facebook, the image taken has not been selected or saved.
Prerequisites:
1. Download and install Facebook from Marketplace
Repro Steps:
1) Update a Tarako to BuildID: 20140530014002
2) Tap Facebook, then Photos
3) Tap Camera and take a photo
4) Observe device behavior
Actual:
Device non responsive with no indication to user to select or retake the photo. User's option is to restart device or long press homescreen button to exit area – losing saved work.
Expected:
An on screen message to retake or select the photo and continued functionality without having to restart the device or long press homescreen button.
Notes:
Repro frequency: (5/5, 100%)
See attached: video clip, logcat, firewatch
1.3T Environmental Variables:
Device: Tarako 1.3T
BuildID: 20140530014002
Gaia: e68858693b71d917c9c5ee7e215f7ceea04635f7
Gecko: 1945abae19ff
Version: 28.1
Firmware Version: sp6821a-gonk-4.0-5-12
User Agent: Mozilla/5.0 (Mobile; rv:28.1) Gecko/28.1 Firefox/28.1

jsmith: https://www.youtube.com/watch?v=TQxFOhNBK6A&feature=youtube_gdata_player
This is from today's build which is much better than before. It could take up to a 45 seconds for the camera to load before today's build. You can still see parts where it seems unresponsive.
Gaia e073132c427e85f15408c5d9a9c700b20ee12b8b
Gecko https://hg.mozilla.org/releases/mozilla-b2g28_v1_3t/rev/d78bccbc2a24
BuildID 20140613014003
Version 28.1
ro.build.version.incremental=eng.cltbld.20140613.133443
ro.build.date=Fri Jun 13 13:34:53 EDT 2014
Tarako
This is not the same build as done for the profiling. The profiling runs on a different UA which gives a more minimized version of Facebook. Having said that, there still is a performance issue with the camera app being called from a third party app.

Are we sure the root cause here is related to third party app here? The only thing the app is doing here is exposing an input=file element and allowing the user to select the camera through it. I'd expect this issue to reproduce elsewhere with an input=file element.

I believe we made some changes to email as well as contacts and sms in regards to the interactions between camera/gallery. I am unsure about bluetooth and browser now that I think about it. There might be a gap in coverage there. I don't think you can share camera through blue tooth?
We might see the issue in browser.