Abstract: A computing device performs a first operation before a first commit deadline, resulting in a first frame being rendered and displayed in a first cycle. A second operation is performed, before a second commit deadline, resulting in a second frame being rendered and displayed in a second cycle. A time remaining to a third commit deadline is determined, using the current time. A third operation is predicted, performable before a third commit deadline. An additional operation is predicted, performable for a future cycle. A total processing time for the third and additional operations is determined, being less than the remaining time. The third and additional operations are performed for use in a future cycle. The result of the third operation is used to render a third frame for the third cycle. The result of the additional operation is used to render an additional frame before a future render deadline.

Abstract: An access control system is provided to prevent the surreptitious granting of access to privacy related functionality on an electronic device. Software-based events to grant access to device functionality can be validated by confirming that the software event corresponds with a hardware input event. This validation prevents the spoofing of a user interface input that may be used to fraudulently grant access to specific functionality.

Abstract: Aspects of the subject technology relate to providing frame rate arbitration for electronic devices. Frame rate arbitration can include determining a global frame rate based on frame rate parameters from one or more animation sources, and providing the global frame rate to the animation sources. The frame rate parameters for various animations sources can have differing preferred, minimum, and/or maximum frame rates, and the global frame rate may be determined for concurrent display of multiple animations from the multiple animation sources. In one or more implementations, frame rate arbitration can also be performed based on frame rate parameters from an input source.

Abstract: An electronic device may include a display. Control circuitry may operate the display at different frame rates such as 60 Hz, 80 Hz, and 120 Hz. The control circuitry may determine which frame rate to use based on a speed of animation on the display and based on a type of animation on the display. To mitigate the appearance of judder as the display frame rate changes, the control circuitry may implement techniques such as hysteresis (e.g., windows of tolerance around speed thresholds to ensure that the display frame rate does not change too frequently as a result of noise), speed thresholds that are based on a user perception study, consistent latency between touch input detection and corresponding display output across different frame rates (e.g., using a fixed touch scan rate that is independent of frame duration), and animation-specific speed thresholds for triggering frame rate changes.

Abstract: A computing device performs a first operation before a first commit deadline, resulting in a first frame being rendered and displayed in a first cycle. A second operation is performed, before a second commit deadline, resulting in a second frame being rendered and displayed in a second cycle. A time remaining to a third commit deadline is determined, using the current time. A third operation is predicted, performable before a third commit deadline. An additional operation is predicted, performable for a future cycle. A total processing time for the third and additional operations is determined, being less than the remaining time. The third and additional operations are performed for use in a future cycle. The result of the third operation is used to render a third frame for the third cycle. The result of the additional operation is used to render an additional frame before a future render deadline.

Abstract: An access control system is provided to prevent the surreptitious granting of access to privacy related functionality on an electronic device. Software-based events to grant access to device functionality can be validated by confirming that the software event corresponds with a hardware input event. This validation prevents the spoofing of a user interface input that may be used to fraudulently grant access to specific functionality.