Lines Matching full:captures
541 latest capture result received from the camera device, since additional captures
602 may be fired for captures for which the
611 captures.
615 will always be fired for captures for which the
1017 START for multiple captures in a row means restarting the AF operation over
1058 latest capture result received from the camera device, since additional captures
1464 collected from manual captures with OFF_KEEP_STATE will be
1677 In this scene mode, the camera device captures images
1688 Therefore, HDR captures operate at a much slower rate
1689 than regular captures.
1695 devices, captures that target a JPEG-format output will
1709 captures, and only JPEG outputs are supported for LEGACY
1710 HDR captures. Using a RAW output for HDR capture is not
2836 with YUV or PRIVATE reprocessing, where the application continuously captures
4016 with YUV or PRIVATE reprocessing, where the application continuously captures
5670 For example, consider JPEG captures which have the following
6193 to use android.sensor.dynamicWhiteLevel for captures when supported
6226 The timestamps provided for captures are always in nanoseconds and monotonic, but
6644 android.sensor.opticalBlackRegions directly for captures when
6726 timestamps for other captures from the same camera device, but are
6963 device returns captures from the image sensor.
8564 values may not be consistent across captures.
8670 could include any in-progress captures not yet returned by the camera