From 9895959a71b699fbdf0ef24581276a3a412fdf1a Mon Sep 17 00:00:00 2001 From: Shuzhen Wang Date: Mon, 9 May 2022 00:04:55 +0000 Subject: [PATCH] Camera: Clarify benefit of readout vs exposure timestamp Update developer doc with minor clarification. Test: Build Bug: 229097448 Bug: 229773853 Change-Id: Ice7c88a47366759c6024de7a9a30a8114c1ff655 --- core/java/android/hardware/camera2/CameraCaptureSession.java | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/core/java/android/hardware/camera2/CameraCaptureSession.java b/core/java/android/hardware/camera2/CameraCaptureSession.java index 5dbe9bff328e1..5b1973ad2dd47 100644 --- a/core/java/android/hardware/camera2/CameraCaptureSession.java +++ b/core/java/android/hardware/camera2/CameraCaptureSession.java @@ -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.

+ * 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.

* *

This timestamp may not match {@link CaptureResult#SENSOR_TIMESTAMP the result * timestamp field}. It will, however, match the timestamp of buffers sent to the