| 733ca8dfa76ac34d1f9caff8798d01a4a8f44002 |
|
14-Oct-2014 |
Senpo Hu <senpo@google.com> |
Return more detailed debugging info for logging purposes.
Change-Id: If71afbf8029e9e4d5560eb6a655ece990cf19a19
/frameworks/ex/camera2/portability/src/com/android/ex/camera2/portability/CameraExceptionHandler.java
|
| 318eeb225f4567a8c2a6fe14baa06e8923ebe622 |
|
11-Oct-2014 |
Senpo Hu <senpo@google.com> |
Cleanup: handle API 1 error callback in CameraExceptionHandler.
Portability API used to expose setErrorCallback call which is API 1
only. The new CameraExceptionHandler should be the centralized place
to handle different camera errors.
Bug: 17931297
Change-Id: I0212f96a98e0caca64aca0f947b991b895d8d56b
/frameworks/ex/camera2/portability/src/com/android/ex/camera2/portability/CameraExceptionHandler.java
|
| 2d01b8e2b5ad30ce3c442799cad4c3d26607fc6f |
|
06-Oct-2014 |
Senpo Hu <senpo@google.com> |
Overhaul error handling in AndroidCameraAgentImpl.
DispatchThread could throw RTE when timeout (2500 ms). This CL extends
it to 3500 ms and also re-route the exception to the proper exception
callback instead of surfacing that up to the app. Since a lot of try-catch
block is added, CameraExceptionHandler class is added to keep
CameraAgent.java clean.
The portability layer should ensure the proper use of Camera API 1. With
this assumption, any run time exception thrown by the framework should be
considered fatal. Once it happened, CameraAgent/CameraProxy should be
invalidated. Any subsequent camera commands should be gated as no-ops to
prevent HAL hanging symptom. Users should be guided to exit the app and
recover from the camera error.
Design Doc:
https://docs.google.com/a/google.com/document/d/1t0sEPwGgc387XcoCVC7kT9Y_RSZPxcayla03M4bdn0U/edit
Corresponding CL for the app layer: ag/562383
Bug: 16189216
Change-Id: I33e69aeff0c8e4211e82e0e83133915700c4eb8f
/frameworks/ex/camera2/portability/src/com/android/ex/camera2/portability/CameraExceptionHandler.java
|