diff options
| author | James Dong <jdong@google.com> | 2012-04-28 21:30:46 -0700 |
|---|---|---|
| committer | James Dong <jdong@google.com> | 2012-04-30 12:01:06 -0700 |
| commit | 248ba23ad28c1f8fb69904663204df08c5818700 (patch) | |
| tree | 4623a1781ae4ad62ce30b2a8c4ce2448a9898099 /docs/html/sdk/api_diff/4/changes | |
| parent | 427db9b3d10d5c203d0351e683c3cddfd270250c (diff) | |
Fix a race condition in Camera API for handling focus
In the case where a previous AF completion was outstanding but before the completion
notification reached the application, the application cancelled this AF request, and
then started a new AF request. Right after the new AF request, the AF completion
notification for earlier AF request reached the application. The application
could not tell the AF completion notification was meant for the cancelled AF, but
thought the new AF was successfully completed. Subsequently, the application trid to
take a picture, which failed as a result.
The fix is to add an explicit lock in the Camera.java class to fix the race condition to
synchornize autoFocus(), cancelAutoFocus() and the callback of the pending AF
completion message.
o related-to-bug: 6026480
Change-Id: I33d244d908ac066698e792f641ba88fe228b14a9
Diffstat (limited to 'docs/html/sdk/api_diff/4/changes')
0 files changed, 0 insertions, 0 deletions