History log of /frameworks/base/core/java/android/hardware/camera2/impl/CallbackProxies.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
cad1bfe68b3597741f777a8bf233cd440946936b 23-May-2017 Eino-Ville Talvala <etalvala@google.com> Camera2: Fix broken onCaptureBufferLost callback

Turns out this never worked. 😱

- Add missing oncaptureBufferLost proxy method
- To avoid this issue in the future, change CameraDeviceImpl.CaptureCallback to be
an interface instead of an abstract class; now all implementers _must_ implement
all the methods
- For the short-circuit local callback when no callback is provided by the user,
implement all no-ops explicitly.

Test: Camera CTS continues to pass; manual testing with injected buffer drops
Bug: 62004599
Change-Id: I7732903dbc00e80084162e067de66b5db6cee74c
/frameworks/base/core/java/android/hardware/camera2/impl/CallbackProxies.java
88f1af241045d446358c692e183e5ecb152bad91 30-Sep-2016 Shuzhen Wang <shuzhenwang@google.com> Camera2: Add onCaptureQueueEmpty callback

onCaptureQueueEmpty indicates that the non-repeating
capture request queue of camera device is empty, and
is ready to process a new request.

Test: testMultipleCapture in PerformanceTest.java

Bug: 29006447
Change-Id: If245ff6abf352548ca13a10fcfbd1550b92c1224
/frameworks/base/core/java/android/hardware/camera2/impl/CallbackProxies.java
ad916f7fd3fbb202f2993fea04b0bdad3dcd6de6 11-Apr-2015 Eino-Ville Talvala <etalvala@google.com> Camera2: Add prepare method for output buffer pre-allocation

Normally, buffers for camera output Surfaces are allocated as
needed. This minimizes memory overhead and time to first frame.

However, if allocation takes a long time, as it can do for full-resolution
output buffers, full frame rate may not be maintainable with the added
allocation overhead.

The prepare() method allows an application to indicate that buffers for
a given output Surface should be preallocated by the camera device.
Once the allocation is complete, the onSurfacePrepared callback is invoked.
The application may then use the prepared Surface without concerns about
allocation-caused delays.

Change-Id: I4f616dc87dd4346f408cf1ea37d48a642ceb57da
/frameworks/base/core/java/android/hardware/camera2/impl/CallbackProxies.java
e8df3093f53fa992f89e019b2fc87ff4fac0f335 08-Sep-2014 Eino-Ville Talvala <etalvala@google.com> Camera2: Add frameNumber to CaptureCallback#onCaptureStarted

Otherwise, cannot reliably match up capture progressed and failure callbacks
with the start callback.

Bug: 17421092
Change-Id: I91d92be70a15536b215bac330370ce37e426ec26
/frameworks/base/core/java/android/hardware/camera2/impl/CallbackProxies.java
fd887436bd111e4d2c7307578a51b5070025b7f2 04-Sep-2014 Eino-Ville Talvala <etalvala@google.com> Camera2: Final API revisions

- Rename listeners to callbacks. Listeners are single-method and are interfaces,
while callbacks are abstract may get more methods in the future.
- Use register/unregister for registering callbacks, not add/remove.

Bug: 17389922
Change-Id: Ic6b46ad79cb43a43a85e2a4b63f059d3af99798b
/frameworks/base/core/java/android/hardware/camera2/impl/CallbackProxies.java