summaryrefslogtreecommitdiffstats
path: root/camera
diff options
context:
space:
mode:
Diffstat (limited to 'camera')
-rw-r--r--camera/docs/docs.html16
-rw-r--r--camera/docs/metadata_definitions.xml16
2 files changed, 16 insertions, 16 deletions
diff --git a/camera/docs/docs.html b/camera/docs/docs.html
index 1905f99..735ee1e 100644
--- a/camera/docs/docs.html
+++ b/camera/docs/docs.html
@@ -17500,14 +17500,14 @@ size or CFA pattern),<wbr/> a logical camera can still advertise RAW capability.
case,<wbr/> when the application configures a RAW stream,<wbr/> the camera device will make sure
the active physical camera will remain active to ensure consistent RAW output
behavior,<wbr/> and not switch to other physical cameras.<wbr/></p>
-<p>To maintain backward compatibility,<wbr/> the capture request and result metadata tags
-required for basic camera functionalities will be solely based on the
-logical camera capabiltity.<wbr/> Other request and result metadata tags,<wbr/> on the other
-hand,<wbr/> will be based on current active physical camera.<wbr/> For example,<wbr/> the physical
-cameras' sensor sensitivity and lens capability could be different from each other.<wbr/>
-So when the application manually controls sensor exposure time/<wbr/>gain,<wbr/> or does manual
-focus control,<wbr/> it must checks the current active physical camera's exposure,<wbr/> gain,<wbr/>
-and focus distance range.<wbr/></p></span>
+<p>The capture request and result metadata tags required for backward compatible camera
+functionalities will be solely based on the logical camera capabiltity.<wbr/> On the other
+hand,<wbr/> the use of manual capture controls (sensor or post-processing) with a
+logical camera may result in unexpected behavior when the HAL decides to switch
+between physical cameras with different characteristics under the hood.<wbr/> For example,<wbr/>
+when the application manually sets exposure time and sensitivity while zooming in,<wbr/>
+the brightness of the camera images may suddenly change because HAL switches from one
+physical camera to the other.<wbr/></p></span>
</li>
<li>
<span class="entry_type_enum_name">MONOCHROME (v3.3)</span>
diff --git a/camera/docs/metadata_definitions.xml b/camera/docs/metadata_definitions.xml
index d682c65..2c49c13 100644
--- a/camera/docs/metadata_definitions.xml
+++ b/camera/docs/metadata_definitions.xml
@@ -5450,14 +5450,14 @@ xsi:schemaLocation="http://schemas.android.com/service/camera/metadata/ metadata
the active physical camera will remain active to ensure consistent RAW output
behavior, and not switch to other physical cameras.
- To maintain backward compatibility, the capture request and result metadata tags
- required for basic camera functionalities will be solely based on the
- logical camera capabiltity. Other request and result metadata tags, on the other
- hand, will be based on current active physical camera. For example, the physical
- cameras' sensor sensitivity and lens capability could be different from each other.
- So when the application manually controls sensor exposure time/gain, or does manual
- focus control, it must checks the current active physical camera's exposure, gain,
- and focus distance range.
+ The capture request and result metadata tags required for backward compatible camera
+ functionalities will be solely based on the logical camera capabiltity. On the other
+ hand, the use of manual capture controls (sensor or post-processing) with a
+ logical camera may result in unexpected behavior when the HAL decides to switch
+ between physical cameras with different characteristics under the hood. For example,
+ when the application manually sets exposure time and sensitivity while zooming in,
+ the brightness of the camera images may suddenly change because HAL switches from one
+ physical camera to the other.
</notes>
</value>
<value optional="true" hal_version="3.3" >MONOCHROME