Lines Matching full:trigger
2274 <p>If AE precapture is triggered (see <a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a>)
2280 Similarly,<wbr/> AE precapture trigger CANCEL has no effect when AE is already locked.<wbr/></p>
2339 <a href="#controls_android.control.awbLock">android.<wbr/>control.<wbr/>awb<wbr/>Lock</a>,<wbr/> and <a href="#controls_android.control.afTrigger">android.<wbr/>control.<wbr/>af<wbr/>Trigger</a>
2361 (triggered by <a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a>) and
2372 (triggered by <a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a>) and
2592 android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger
2607 <span class="entry_type_enum_notes"><p>The trigger is idle.<wbr/></p></span>
2613 <p>The exact effect of the precapture trigger depends on
2627 <p>Whether the camera device will trigger a precapture
2651 set to START,<wbr/> the camera device will trigger the auto-exposure (AE)
2654 precapture metering trigger,<wbr/> and return to its initial AE state.<wbr/>
2657 CANCEL trigger will unlock the AE and return to its initial AE state.<wbr/></p>
2676 the AE precapture trigger.<wbr/> Note that,<wbr/> the CANCEL was added in API level 23,<wbr/> and must not
2678 <p>The exact effect of auto-exposure (AE) precapture trigger
2682 <p>On LEGACY-level devices,<wbr/> the precapture trigger is not supported;
2683 capturing a high-resolution JPEG image will automatically trigger a
2686 <p>Using the precapture trigger and the auto-focus trigger <a href="#controls_android.control.afTrigger">android.<wbr/>control.<wbr/>af<wbr/>Trigger</a>
2689 focus sweep),<wbr/> the camera device may delay acting on a later trigger until the previous
2690 trigger has been fully handled.<wbr/> This may lead to longer intervals between the trigger and
2693 <p>If both the precapture and the auto-focus trigger are activated on the same request,<wbr/> then
2703 <p>The HAL must support triggering the AE precapture trigger while an AF trigger is active
2704 (and vice versa),<wbr/> or at the same time as the AF trigger.<wbr/> It is acceptable for the HAL to
2705 treat these as two consecutive triggers,<wbr/> for example handling the AF trigger and then the
2706 AE trigger.<wbr/> Or the HAL may choose to optimize the case with both triggers fired at once,<wbr/>
2741 the autofocus trigger action is called.<wbr/> When that trigger
2754 autofocus trigger action is called.<wbr/> When that trigger is
2759 <p>When that trigger is activated,<wbr/> AF will transition to
2772 movement and no overshoots.<wbr/> When the AF trigger is not
2775 states as appropriate.<wbr/> When the AF trigger is activated,<wbr/>
2778 lens position until a cancel AF trigger is received.<wbr/></p>
2792 possible.<wbr/> When the AF trigger is not involved,<wbr/> the AF
2796 trigger is activated,<wbr/> the algorithm should finish its
2799 lens position until a cancel AF trigger is received.<wbr/></p>
2800 <p>When the AF cancel trigger is activated,<wbr/> the algorithm
2844 dependent.<wbr/> It is recommended to lock AF by using <a href="#controls_android.control.afTrigger">android.<wbr/>control.<wbr/>af<wbr/>Trigger</a> before
2857 <p>When afMode is AUTO or MACRO,<wbr/> the lens must not move until an AF trigger is sent in a
2858 request (<a href="#controls_android.control.afTrigger">android.<wbr/>control.<wbr/>af<wbr/>Trigger</a> <code>==</code> START).<wbr/> After an AF trigger,<wbr/> the afState will end
2865 scan whenever it's not locked.<wbr/> When the lens is locked after an AF trigger
2978 android.<wbr/>control.<wbr/>af<wbr/>Trigger
2993 <span class="entry_type_enum_notes"><p>The trigger is idle.<wbr/></p></span>
2997 <span class="entry_type_enum_notes"><p>Autofocus will trigger now.<wbr/></p></span>
3002 state,<wbr/> and cancel any currently active trigger.<wbr/></p></span>
3009 <p>Whether the camera device will trigger autofocus for this request.<wbr/></p>
3032 <p>When included and set to START,<wbr/> the camera device will trigger the
3033 autofocus algorithm.<wbr/> If autofocus is disabled,<wbr/> this trigger has no effect.<wbr/></p>
3034 <p>When set to CANCEL,<wbr/> the camera device will cancel any active trigger,<wbr/>
3040 <p>See <a href="#dynamic_android.control.afState">android.<wbr/>control.<wbr/>af<wbr/>State</a> for what the trigger means for each AF mode.<wbr/></p>
3041 <p>Using the autofocus trigger and the precapture trigger <a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a>
3044 focus sweep),<wbr/> the camera device may delay acting on a later trigger until the previous
3045 trigger has been fully handled.<wbr/> This may lead to longer intervals between the trigger and
3055 <p>The HAL must support triggering the AF trigger while an AE precapture trigger is active
3056 (and vice versa),<wbr/> or at the same time as the AE trigger.<wbr/> It is acceptable for the HAL to
3057 treat these as two consecutive triggers,<wbr/> for example handling the AF trigger and then the
3058 AE trigger.<wbr/> Or the HAL may choose to optimize the case with both triggers fired at once,<wbr/>
3444 <p>The precapture trigger
3893 <li><a href="#controls_android.control.afTrigger">android.<wbr/>control.<wbr/>af<wbr/>Trigger</a></li>
3894 <li><a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a></li>
3926 <p>Switching into or out of this mode may trigger some camera ISP/<wbr/>sensor
5635 CAMERA2_<wbr/>TRIGGER_<wbr/>PRECAPTURE_<wbr/>METERING trigger received yet
5637 trigger</p>
5896 <p>If AE precapture is triggered (see <a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a>)
5902 Similarly,<wbr/> AE precapture trigger CANCEL has no effect when AE is already locked.<wbr/></p>
5961 <a href="#controls_android.control.awbLock">android.<wbr/>control.<wbr/>awb<wbr/>Lock</a>,<wbr/> and <a href="#controls_android.control.afTrigger">android.<wbr/>control.<wbr/>af<wbr/>Trigger</a>
5983 (triggered by <a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a>) and
5994 (triggered by <a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a>) and
6214 android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger
6229 <span class="entry_type_enum_notes"><p>The trigger is idle.<wbr/></p></span>
6235 <p>The exact effect of the precapture trigger depends on
6249 <p>Whether the camera device will trigger a precapture
6273 set to START,<wbr/> the camera device will trigger the auto-exposure (AE)
6276 precapture metering trigger,<wbr/> and return to its initial AE state.<wbr/>
6279 CANCEL trigger will unlock the AE and return to its initial AE state.<wbr/></p>
6298 the AE precapture trigger.<wbr/> Note that,<wbr/> the CANCEL was added in API level 23,<wbr/> and must not
6300 <p>The exact effect of auto-exposure (AE) precapture trigger
6304 <p>On LEGACY-level devices,<wbr/> the precapture trigger is not supported;
6305 capturing a high-resolution JPEG image will automatically trigger a
6308 <p>Using the precapture trigger and the auto-focus trigger <a href="#controls_android.control.afTrigger">android.<wbr/>control.<wbr/>af<wbr/>Trigger</a>
6311 focus sweep),<wbr/> the camera device may delay acting on a later trigger until the previous
6312 trigger has been fully handled.<wbr/> This may lead to longer intervals between the trigger and
6315 <p>If both the precapture and the auto-focus trigger are activated on the same request,<wbr/> then
6325 <p>The HAL must support triggering the AE precapture trigger while an AF trigger is active
6326 (and vice versa),<wbr/> or at the same time as the AF trigger.<wbr/> It is acceptable for the HAL to
6327 treat these as two consecutive triggers,<wbr/> for example handling the AF trigger and then the
6328 AE trigger.<wbr/> Or the HAL may choose to optimize the case with both triggers fired at once,<wbr/>
6387 <a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a> to START.<wbr/> Currently
6390 <a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a> to CANCEL.<wbr/></p>
6547 <td align="center">Precapture trigger is ignored when AE is already locked</td>
6553 <td align="center">Precapture trigger is ignored when AE is already locked</td>
6557 <td align="center"><a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a> is START</td>
6563 <td align="center"><a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a> is CANCEL</td>
6570 without application intervention (i.<wbr/>e.<wbr/> mode switch,<wbr/> trigger,<wbr/> locking).<wbr/> Any state that
6593 <td align="center"><a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a> is START,<wbr/> sequence done</td>
6599 <td align="center"><a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a> is START,<wbr/> sequence done</td>
6605 <td align="center"><a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger
6611 <td align="center"><a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a> is CANCEL,<wbr/> converged</td>
6663 the autofocus trigger action is called.<wbr/> When that trigger
6676 autofocus trigger action is called.<wbr/> When that trigger is
6681 <p>When that trigger is activated,<wbr/> AF will transition to
6694 movement and no overshoots.<wbr/> When the AF trigger is not
6697 states as appropriate.<wbr/> When the AF trigger is activated,<wbr/>
6700 lens position until a cancel AF trigger is received.<wbr/></p>
6714 possible.<wbr/> When the AF trigger is not involved,<wbr/> the AF
6718 trigger is activated,<wbr/> the algorithm should finish its
6721 lens position until a cancel AF trigger is received.<wbr/></p>
6722 <p>When the AF cancel trigger is activated,<wbr/> the algorithm
6766 dependent.<wbr/> It is recommended to lock AF by using <a href="#controls_android.control.afTrigger">android.<wbr/>control.<wbr/>af<wbr/>Trigger</a> before
6779 <p>When afMode is AUTO or MACRO,<wbr/> the lens must not move until an AF trigger is sent in a
6780 request (<a href="#controls_android.control.afTrigger">android.<wbr/>control.<wbr/>af<wbr/>Trigger</a> <code>==</code> START).<wbr/> After an AF trigger,<wbr/> the afState will end
6787 scan whenever it's not locked.<wbr/> When the lens is locked after an AF trigger
6900 android.<wbr/>control.<wbr/>af<wbr/>Trigger
6915 <span class="entry_type_enum_notes"><p>The trigger is idle.<wbr/></p></span>
6919 <span class="entry_type_enum_notes"><p>Autofocus will trigger now.<wbr/></p></span>
6924 state,<wbr/> and cancel any currently active trigger.<wbr/></p></span>
6931 <p>Whether the camera device will trigger autofocus for this request.<wbr/></p>
6954 <p>When included and set to START,<wbr/> the camera device will trigger the
6955 autofocus algorithm.<wbr/> If autofocus is disabled,<wbr/> this trigger has no effect.<wbr/></p>
6956 <p>When set to CANCEL,<wbr/> the camera device will cancel any active trigger,<wbr/>
6962 <p>See <a href="#dynamic_android.control.afState">android.<wbr/>control.<wbr/>af<wbr/>State</a> for what the trigger means for each AF mode.<wbr/></p>
6963 <p>Using the autofocus trigger and the precapture trigger <a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a>
6966 focus sweep),<wbr/> the camera device may delay acting on a later trigger until the previous
6967 trigger has been fully handled.<wbr/> This may lead to longer intervals between the trigger and
6977 <p>The HAL must support triggering the AF trigger while an AE precapture trigger is active
6978 (and vice versa),<wbr/> or at the same time as the AE trigger.<wbr/> It is acceptable for the HAL to
6979 treat these as two consecutive triggers,<wbr/> for example handling the AF trigger and then the
6980 AE trigger.<wbr/> Or the HAL may choose to optimize the case with both triggers fired at once,<wbr/>
7033 triggered by AF trigger.<wbr/></p>
7042 <p>This state is reached only after an explicit START AF trigger has been
7043 sent (<a href="#controls_android.control.afTrigger">android.<wbr/>control.<wbr/>af<wbr/>Trigger</a>),<wbr/> when good focus has been obtained.<wbr/></p>
7045 a new AF trigger is sent to the camera device (<a href="#controls_android.control.afTrigger">android.<wbr/>control.<wbr/>af<wbr/>Trigger</a>).<wbr/></p></span>
7051 <p>This state is reached only after an explicit START AF trigger has been
7052 sent (<a href="#controls_android.control.afTrigger">android.<wbr/>control.<wbr/>af<wbr/>Trigger</a>),<wbr/> when good focus cannot be obtained.<wbr/></p>
7054 a new AF trigger is sent to the camera device (<a href="#controls_android.control.afTrigger">android.<wbr/>control.<wbr/>af<wbr/>Trigger</a>).<wbr/></p></span>
7131 <td align="center">AF_<wbr/>TRIGGER</td>
7161 <td align="center">AF_<wbr/>TRIGGER</td>
7173 <td align="center">AF_<wbr/>TRIGGER</td>
7186 without application intervention (i.<wbr/>e.<wbr/> mode switch,<wbr/> trigger,<wbr/> locking).<wbr/> Any state that
7203 <td align="center">AF_<wbr/>TRIGGER</td>
7209 <td align="center">AF_<wbr/>TRIGGER</td>
7215 <td align="center">AF_<wbr/>TRIGGER</td>
7221 <td align="center">AF_<wbr/>TRIGGER</td>
7246 <td align="center">AF_<wbr/>TRIGGER</td>
7264 <td align="center">AF_<wbr/>TRIGGER</td>
7270 <td align="center">AF_<wbr/>TRIGGER</td>
7294 <td align="center">AF_<wbr/>TRIGGER</td>
7300 <td align="center">AF_<wbr/>TRIGGER
7306 <td align="center">AF_<wbr/>TRIGGER</td>
7318 <td align="center">AF_<wbr/>TRIGGER</td>
7349 <td align="center">AF_<wbr/>TRIGGER</td>
7367 <td align="center">AF_<wbr/>TRIGGER</td>
7373 <td align="center">AF_<wbr/>TRIGGER</td>
7397 <td align="center">AF_<wbr/>TRIGGER</td>
7403 <td align="center">AF_<wbr/>TRIGGER</td>
7409 <td align="center">AF_<wbr/>TRIGGER</td>
7421 <td align="center">AF_<wbr/>TRIGGER</td>
7435 camera device.<wbr/> When a trigger is included in a mode switch request,<wbr/> the trigger
7452 <td align="center">Mode switch without trigger,<wbr/> initial state must be INACTIVE</td>
7456 <td align="center">CAF-->AUTO mode switch with AF_<wbr/>TRIGGER</td>
7457 <td align="center">trigger-reachable states from INACTIVE</td>
7458 <td align="center">Mode switch with trigger,<wbr/> INACTIVE is skipped</td>
7464 <td align="center">Mode switch without trigger,<wbr/> passive transient state is skipped</td>
7480 android.<wbr/>control.<wbr/>af<wbr/>Trigger<wbr/>Id
7516 <p>Must be 0 if no CAMERA2_<wbr/>TRIGGER_<wbr/>AUTOFOCUS trigger
7518 ignores the trigger</p>
7904 <p>The precapture trigger may be used to start off a metering
8132 without application intervention (i.<wbr/>e.<wbr/> mode switch,<wbr/> trigger,<wbr/> locking).<wbr/> Any state that
8539 <li><a href="#controls_android.control.afTrigger">android.<wbr/>control.<wbr/>af<wbr/>Trigger</a></li>
8540 <li><a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a></li>
8572 <p>Switching into or out of this mode may trigger some camera ISP/<wbr/>sensor
9595 (<a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a>),<wbr/> otherwise,<wbr/> the image may be incorrectly exposed.<wbr/></p>
10032 (<a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a>),<wbr/> otherwise,<wbr/> the image may be incorrectly exposed.<wbr/></p>
14250 android.<wbr/>quirks.<wbr/>trigger<wbr/>Af<wbr/>With<wbr/>Auto
14268 trigger.<wbr/></p>
14287 <p>HAL implementations should implement AF trigger
15777 <li><a href="#controls_android.control.afTrigger">android.<wbr/>control.<wbr/>af<wbr/>Trigger</a></li>
15778 <li><a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a></li>
15813 <p>Switching to a FPS range that has different maximum FPS may trigger some camera device
25720 <p><code>LIMITED</code> devices and above require the use of <a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a>
25760 <p>In addition,<wbr/> the <a href="#controls_android.control.aePrecaptureTrigger">android.<wbr/>control.<wbr/>ae<wbr/>Precapture<wbr/>Trigger</a> is not functional on <code>LEGACY</code>
25762 as triggering a still capture,<wbr/> internally executing a precapture trigger.<wbr/> This may
