Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge "Camera: Clarify benefit of readout vs exposure timestamp" into tm-d1-dev am: 26f673480d

Browse Source 
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/18218749

Change-Id: I0f7ed28d2cdbd358153e5fba19895cf349a363ff
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
This commit is contained in:
TreeHugger Robot
2022-05-09 20:45:24 +00:00
committed by Automerger Merge Worker
parent 1cb353fff4 26f673480d
commit 80e6efa582
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
core/java/android/hardware/camera2/CameraCaptureSession.java
View File

@@ -1241,8 +1241,9 @@ public abstract class CameraCaptureSession implements AutoCloseable {
* {@link #onCaptureStarted}. Unlike {@link #onCaptureStarted}, instead of passing
* a timestamp of start of exposure, this callback passes a timestamp of start of
* camera data readout. This is useful because for a camera running at fixed frame
* rate, the start of readout is at fixed interval, but not necessary for the start
* of exposure.</p>
* rate, the start of readout is at fixed interval, which is not necessarily true for
* the start of exposure, particularly when autoexposure is changing exposure duration
* between frames.</p>
*
* <p>This timestamp may not match {@link CaptureResult#SENSOR_TIMESTAMP the result
* timestamp field}. It will, however, match the timestamp of buffers sent to the