Patent Grant
12182373
The present disclosure relates generally to computer user interfaces, and more specifically to techniques for displaying user interfaces with managed display usage.
Electronic devices may include screens for displaying user interfaces. Over time, non-uniform use of screens may lead to discoloration of portions of the screen and decreased quality of displayed images.
Some techniques for displaying user interfaces using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.
Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces with managed display usage. Such methods and interfaces optionally complement or replace other methods for managing display usage. Such methods improve image quality (e.g., reduce deterioration of image quality) of displayed user interfaces as an electronic device ages and improve the durability of display devices used to display user interfaces. In addition, such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges. Furthermore, such methods and interfaces also reduce the number of unnecessary, extraneous, or repetitive inputs required at computing devices, such as smartphones and smartwatches.
In accordance with some embodiments, a method is described. The method comprises: at a computer system that is in communication with a display generation component: while the computer system is in a first mode, displaying, via the display generation component, a first user interface that includes one or more user interface elements including a first user interface element, where the user interface is associated with a first application; while displaying the first user interface in the first mode, detecting that the computer system has met one or more criteria for transitioning from the first mode to a second mode, wherein the second mode is a tower power mode; in response to detecting that the computer system has met one or more criteria for transitioning from the first mode to the second mode, entering the second mode, including displaying a second user interface that is associated with the first application where the second user interface corresponds to the first user interface and is displayed at a location that occupies at least a portion of a display region that was occupied by the first user interface and includes one or more user interface elements including a second user interface element; and while the computer system is in the second mode, updating an appearance of the second user interface element periodically while maintaining the computer system in the second mode, wherein: in accordance with a determination that one or more time-sensitive update criteria are not satisfied, the appearance of the second user interface element is periodically updated at a first update frequency; and in accordance with a determination that the one or more time-sensitive update criteria are satisfied, the appearance of the second user interface element is periodically updated at a second update frequency different from the first update frequency, wherein the second update frequency is greater than the first update frequency.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component, and the one or more programs include instructions for: while the computer system is in a first mode, displaying, via the display generation component, a first user interface that includes one or more user interface elements including a first user interface element, where the user interface is associated with a first application; while displaying the first user interface in the first mode, detecting that the computer system has met one or more criteria for transitioning from the first mode to a second mode, wherein the second mode is a lower power mode; in response to detecting that the computer system has met one or more criteria for transitioning from the first mode to the second mode, entering the second mode, including displaying a second user interface that is associated with the first application where the second user interface corresponds to the first user interface and is displayed at a location that occupies at least a portion of a display region that was occupied by the first user interface and includes one or more user interface elements including a second user interface element; and while the computer system is in the second mode, updating an appearance of the second user interface element periodically while maintaining the computer system in the second mode, wherein: in accordance with a determination that one or more time-sensitive update criteria are not satisfied, the appearance of the second user interface element is periodically updated at a first update frequency; and in accordance with a determination that the one or more time-sensitive update criteria are satisfied, the appearance of the second user interface element is periodically updated at a second update frequency different from the first update frequency, wherein the second update frequency is greater than the first update frequency.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component, and the one or more programs include instructions for: while the computer system is in a first mode, displaying, via the display generation component, a first user interface that includes one or more user interface elements including a first user interface element, where the user interface is associated with a first application; while displaying the first user interface in the first mode, detecting that the computer system has met one or more criteria for transitioning from the first mode to a second mode, wherein the second mode is a lower power mode; in response to detecting that the computer system has met one or more criteria for transitioning from the first mode to the second mode, entering the second mode, including displaying a second user interface that is associated with the first application where the second user interface corresponds to the first user interface and is displayed at a location that occupies at least a portion of a display region that was occupied by the first user interface and includes one or more user interface elements including a second user interface element; and while the computer system is in the second mode, updating an appearance of the second user interface element periodically while maintaining the computer system in the second mode, wherein: in accordance with a determination that one or more time-sensitive update criteria are not satisfied, the appearance of the second user interface element is periodically updated at a first update frequency; and in accordance with a determination that the one or more time-sensitive update criteria are satisfied, the appearance of the second user interface element is periodically updated at a second update frequency different from the first update frequency, wherein the second update frequency is greater than the first update frequency.
In accordance with some embodiments, a computer system is described. The computer system is in communication with a display generation component, and comprises one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: while the computer system is in a first mode, displaying, via the display generation component, a first user interface that includes one or more user interface elements including a first user interface element, where the user interface is associated with a first application; while displaying the first user interface in the first mode, detecting that the computer system has met one or more criteria for transitioning from the first mode to a second mode, wherein the second mode is a lower power mode; in response to detecting that the computer system has met one or more criteria for transitioning from the first mode to the second mode, entering the second mode, including displaying a second user interface that is associated with the first application where the second user interface corresponds to the first user interface and is displayed at a location that occupies at least a portion of a display region that was occupied by the first user interface and includes one or more user interface elements including a second user interface element; and while the computer system is in the second mode, updating an appearance of the second user interface element periodically while maintaining the computer system in the second mode, wherein: in accordance with a determination that one or more time-sensitive update criteria are not satisfied, the appearance of the second user interface element is periodically updated at a first update frequency; and in accordance with a determination that the one or more time-sensitive update criteria are satisfied, the appearance of the second user interface element is periodically updated, at a second update frequency different from the first update frequency, wherein the second update frequency is greater than the first update frequency.
In accordance with some embodiments, a computer system is described. The computer system is in communication with a display generation component, and comprises: means for displaying, while the computer system is in a first mode, via the display generation component, a first user interface that includes one or more user interface elements including a first user interface element, where the user interface is associated with a first application; means for detecting, while displaying the first user interface in the first mode, that the computer system has met one or more criteria for transitioning from the first mode to a second mode, wherein the second mode is a lower power mode; means for, in response to detecting that the computer system has met one or more criteria for transitioning from the first mode to the second mode, entering the second mode, including means for displaying a second user interface that is associated with the first application where the second user interface corresponds to the first user interface and is displayed at a location that occupies at least a portion of a display region that was occupied by the first user interface and includes one or more user interface elements including a second user interface element; and means for updating, while the computer system is in the second mode, an appearance of the second user interface element periodically while maintaining the computer system in the second mode, wherein: in accordance with a determination that one or more time-sensitive update criteria are not satisfied, the appearance of the second user interface element is periodically updated at a first update frequency; and in accordance with a determination that the one or more time-sensitive update criteria are satisfied, the appearance of the second user interface element is periodically updated at a second update frequency different from the first update frequency, wherein the second update frequency is greater than the first update frequency.
In accordance with some embodiments, a method is described. The method comprises: at a computer system that is in communication with a display generation component: while the computer system is in a first mode, displaying, via the display generation component, a first user interface that is associated with a first application and that includes a plurality of user interface elements including a first user interface element depicting a first set of information; while displaying the first user interface, detecting that the computer system has met one or more criteria for transitioning from the first mode to a second mode; and in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode: in accordance with a determination that the first application is authorized to display the first set of information while the computer system is in the second mode, displaying a second user interface associated with the first application, wherein: the second user interface corresponds to the first user interface and is displayed at a location that occupies at least a portion of a display region that was occupied by the first user interface, the second user interface is darker than the first user interface, and the second user interface includes a second user interface element depicting the first set of information; and in accordance with a determination that the first application is not authorized to display the first set of information while the computer system is in the second mode, displaying a third user interface different from the first user interface and the second user interface, wherein: the third user interface is displayed at a location that occupies at least a portion of the display region that was occupied by the first user interface, and the third user interface does not include the first set of information.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component, and the one or more programs include instructions for: while the computer system is in a first mode, displaying, via the display generation component, a first user interface that is associated with a first application and that includes a plurality of user interface elements including a first user interface element depicting a first set of information; while displaying the first user interface, detecting that the computer system has met one or more criteria for transitioning from the first mode to a second mode; and in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode: in accordance with a determination that the first application is authorized to display the first set of information while the computer system is in the second mode, displaying a second user interface associated with the first application, wherein: the second user interface corresponds to the first, user interface and is displayed at a location that occupies at least a portion of a display region that was occupied by the first user interface, the second user interface is darker than the first user interface, and the second user interface includes a second user interface element depicting the first set of information; and in accordance with a determination that the first application is not authorized to display the first set of information while the computer system is in the second mode, displaying a third user interface different from the first user interface and the second user interface, wherein: the third user interface is displayed at a location that occupies at least a portion of the display region that was occupied by the first user interface, and the third user interface does not include the first set of information.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component, and the one or more programs include instructions for: while the computer system is in a first mode, displaying, via the display generation component, a first user interface that is associated with a first application and that includes a plurality of user interface elements including a first user interface element depicting a first set of information; while displaying the first user interface, detecting that the computer system has met one or more criteria for transitioning from the first mode to a second mode; and in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode: in accordance with a determination that the first application is authorized to display the first set of information while the computer system is in the second mode, displaying a second user interface associated with the first application, wherein: the second user interface corresponds to the first user interface and is displayed at a location that occupies at least a portion of a display region that was occupied by the first user interface, the second user interface is darker than the first user interface, and the second user interface includes a second user interface element depicting the first set of information; and in accordance with a determination that the first application is not authorized to display the first set of information while the computer system is in the second mode, displaying a third user interface different from the first user interface and the second user interface, wherein: the third user interface is displayed at a location that occupies at least a portion of the display region that was occupied by the first user interface, and the third user interface does not include the first set of information.
In accordance with some embodiments, a computer system is described. The computer system is in communication with a display generation component, and comprises one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: while the computer system is in a first mode, displaying, via the display generation component, a first user interface that is associated with a first application and that includes a plurality of user interface elements including a first user interface element depicting a first set of information; while displaying the first user interface, detecting that the computer system has met one or more criteria for transitioning from the first mode to a second mode; and in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode: in accordance with a determination that the first application is authorized to display the first set of information while the computer system is in the second mode, displaying a second user interface associated with the first application, wherein: the second user interface corresponds to the first user interface and is displayed at a location that occupies at least a portion of a display region that was occupied by the first user interface, the second user interface is darker than the first user interface, and the second user interface includes a second user interface element depicting the first set of information; and in accordance with a determination that the first application is not authorized to display the first set of information while the computer system is in the second mode, displaying a third user interface different from the first user interface and the second user interface, wherein: the third user interface is displayed at a location that occupies at least a portion of the display region that was occupied by the first user interface, and the third user interface does not include the first set of information.
In accordance with some embodiments, a computer system is described. The computer system is in communication with a display generation component, and comprises: means for displaying, while the computer system is in a first mode, via the display generation component, a first user interface that is associated with a first application and that includes a plurality of user interface elements including a first user interface element depicting a first set of information; means for detecting, while displaying the first user interface, that the computer system has met one or more criteria for transitioning from the first mode to a second mode; and means for, in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode: in accordance with a determination that the first application is authorized to display the first set of information while the computer system is in the second mode, displaying a second user interface associated with the first application, wherein: the second user interface corresponds to the first user interface and is displayed at a location that occupies at least a portion of a display region that was occupied by the first user interface, the second user interface is darker than the first user interface, and the second user interface includes a second user interface element depicting the first set of information; and in accordance with a determination that the first application is not authorized to display the first set of information while the computer system is in the second mode, displaying a third user interface different from the first user interface and the second user interface, wherein: the third user interface is displayed at a location that occupies at least a portion of the display region that was occupied by the first user interface, and the third user interface does not include the first set of information.
In accordance with some embodiments, a method is described. The method comprises: at a computer system that is in communication with a display generation component: while the computer system is in a first mode, displaying, via the display generation component, a first user interface that is associated with a first application and that includes a first set of one or more user interface elements including a first user interface element, wherein: the appearance of the first user interface element is periodically updated at a first update frequency, and the first user interface is displayed at a first zoom level; while displaying the first user interface, detecting that the computer system has met one or more criteria for transitioning from the first mode to a second mode; and in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode, displaying a second user interface that is different from the first user interface and is associated with the first application, wherein: the second user interface corresponds to the first user interface and is displayed at a location that occupies at least a portion of a display region that was occupied by the first user interface, the second user interface includes a second set of one or more user interface elements including a second user interface element, the appearance of the second user interface element is periodically updated at a second update frequency that is different from the first update frequency and corresponds to a lower update frequency than the first update frequency, and the second user interface is displayed at a second zoom level different from the first zoom level.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component, and the one or more programs include instructions for: while the computer system is in a first mode, displaying, via the display generation component, a first user interface that is associated with a first application and that includes a first set of one or more user interface elements including a first user interface element, wherein: the appearance of the first user interface element is periodically updated at a first update frequency, and the first user interface is displayed at a first zoom level; while displaying the first user interface, detecting that the computer system has met one or more criteria for transitioning from the first mode to a second mode; and in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode, displaying a second user interface that is different from the first user interface and is associated with the first application, wherein: the second user interface corresponds to the first user interface and is displayed at a location that occupies at least a portion of a display region that was occupied by the first user interface, the second user interface includes a second set of one or more user interface elements including a second user interface element, the appearance of the second user interface element is periodically updated at a second update frequency that is different from the first update frequency and corresponds to a lower update frequency than the first update frequency, and the second user interface is displayed at a second zoom level different from the first zoom level.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component, and the one or more programs include instructions for: while the computer system is in a first mode, displaying, via the display generation component, a first user interface that is associated with a first application and that includes a first set of one or more user interface elements including a first user interface element, wherein: the appearance of the first user interface element is periodically updated at a first update frequency, and the first user interface is displayed at a first zoom level; while displaying the first user interface, detecting that the computer system has met one or more criteria for transitioning from the first mode to a second mode; and in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode, displaying a second user interface that is different from the first user interface and is associated with the first application, wherein: the second user interface corresponds to the first user interface and is displayed at a location that occupies at least a portion of a display region that was occupied by the first user interface, the second user interface includes a second set of one or more user interface elements including a second user interface element, the appearance of the second user interface element is periodically updated at a second update frequency that is different from the first update frequency and corresponds to a lower update frequency than the first update frequency, and the second user interface is displayed at a second zoom level different from the first zoom level.
In accordance with some embodiments, a computer system is described. The computer system is in communication with a display generation component, and comprises one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: while the computer system is in a first mode, displaying, via the display generation component, a first user interface that is associated with a first application and that includes a first set of one or more user interface elements including a first user interface element, wherein: the appearance of the first user interface element is periodically updated at a first update frequency, and the first user interface is displayed at a first zoom level; while displaying the first user interface, detecting that the computer system has met one or more criteria for transitioning from the first mode to a second mode; and in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode, displaying a second user interface that is different from the first user interface and is associated with the first application, wherein: the second user interface corresponds to the first user interface and is displayed at a location that occupies at least a portion of a display region that was occupied by the first user interface, the second user interface includes a second set of one or more user interface elements including a second user interface element, the appearance of the second user interface element is periodically updated at a second update frequency that is different from the first update frequency and corresponds to a lower update frequency than the first update frequency, and the second user interface is displayed at a second zoom level different from the first zoom level.
In accordance with some embodiments, a computer system is described. The computer system is in communication with a display generation component, and comprises: a means for displaying while the computer system is in a first mode, via the display generation component, a first user interface that is associated with a first application and that includes a first set of one or more user interface elements including a first user interface element, wherein: the appearance of the first user interface element is periodically updated at a first update frequency, and the first user interface is displayed at a first zoom level; means for detecting, while displaying the first user interface, that the computer system has met one or more criteria for transitioning from the first mode to a second mode; and means for, in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode, displaying a second user interface that is different from the first user interface and is associated with the first application, wherein: the second user interface corresponds to the first user interface and is displayed at a location that occupies at least a portion of a display region that was occupied by the first user interface, the second user interface includes a second set of one or more user interface elements including a second user interface element, the appearance of the second user interface element is periodically updated at a second update frequency that is different from the first update frequency and corresponds to a lower update frequency than the first update frequency, and the second user interface is displayed at a second zoom level different from the first zoom level.
Executable instructions for performing these functions are, optionally, included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are, optionally, included in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.
Thus, devices are provided with faster, more efficient methods and interfaces for managing display usage, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for managing display usage.
For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.
There is a need for electronic devices that provide efficient methods and interfaces for managing display usage. For example, prolonged display of user interfaces that include non-moving graphical objects (e.g., static images) over time causes screen burn-in or image ghosting. This is particularly true for portable multifunction devices with reduced-sized displays, since elements of a displayed user interface are often displayed repetitively at fixed positions on a display. Techniques that thoughtfully manage what is included on a user interface, how it is displayed, and when it is displayed minimize screen burn-in and image ghosting. Such techniques can reduce the cognitive burden on a user who accesses user interfaces, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs and excessive display brightness, and improve the wear characteristics of display devices used to display user interfaces.
Below,
Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the terms “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad). In some embodiments, the electronic device is a computer system that is in communication (e.g., via wireless communication, via wired communication) with a display generation component. The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. As used herein, “displaying” content includes causing to display the content (e.g., video data rendered or decoded by display controller 156) by transmitting, via a wired or wireless connection, data (e.g., image data or video data) to an integrated or external display generation component to visually produce the content.
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 optionally controls access to memory 102 by other components of device 100.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111, Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
A quick press of the push button optionally disengages a lock of touch screen 112 or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) optionally turns power to device 100 on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects.
Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.
A touch-sensitive display in some embodiments of touch screen 112 is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Patents: U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 is described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed. Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.
Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more depth camera sensors 175.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 optionally also includes one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 (
Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RI circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.
Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 are, optionally, used to manage an address hook or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced. Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or MIPS).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext. Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 are, optionally, used to receive, display, modify, and store maps and data associated with maps driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.
Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. For example, video player module is, optionally, combined with music player module into a single module (e.g., video and music player module 152,
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2. (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 optionally also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100,
Each of the above-identified elements in
Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device 100.
It should be noted that the icon labels illustrated in
Although some of the examples that follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No, PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, published as WIPO) Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.
In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.
Input mechanism 508 is, optionally, a microphone, in some examples. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
Memory 518 of personal electronic device 500 can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including processes 700-1100 (
As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (
As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in
As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation.
In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.
The intensity of a contact on the touch-sensitive surface is, optionally, characterized, relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.
In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input).
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.
As used herein, an “installed application” refers to a software application that has been downloaded onto an electronic device e.g., devices 100, 300, and/or 500) and is ready to be launched (e.g., become opened) on the device. In some embodiments, a downloaded application becomes an installed application by way of an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the operating system of the computer system.
As used herein, the terms “open application” or “executing application” refer to a software application with retained state information (e.g., as part of device/global internal state 157 and/or application internal state 192). An open or executing application is, optionally, any one of the following types of applications:
As used herein, the term “closed application” refers to software applications without retained state information (e.g., state information for closed applications is not stored in a memory of the device). Accordingly, closing an application includes stopping and/or removing application processes for the application and removing state information for the application from the memory of the device. Generally, opening a second application while in a first application does not close the first application. When the second application is displayed and the first application ceases to be displayed, the first application becomes a background application.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.
In particular,
Upon determining that mode change criteria have been met, the device transitions from a first mode to a second mode (e.g., a low power mode). In some embodiments, while operating in the second mode, device 600 conserves energy by operating one or more processors of the device at a reduced load, such as by waking (e.g., enabling or turning on) one or more processors of the device at increased intervals (e.g., a reduced rate; less often) compared to operation in the first mode. In some embodiments, a processor includes hardware (e.g., a microprocessor or the like). In some embodiments, a processor includes one or more software components (e.g., software modules for performing various functions; a module for displaying information from applications on a display device; a module for processing sensor data received by the device, a module for performing calculations necessary to perform or implement various features of the device, etc.).
Among the visual characteristics described below that may be altered upon transitioning device modes is the overall brightness of a displayed user interface (e.g., average pixel luminance (APL), average lumen output, total lumen output, average illuminance, and/or total illuminance of the pixels comprising the user interface on the display; brightness expressed in nits, lux, and/or lumens). To illustrate this,
Throughout this disclosure, the concept of brightness levels are also discussed with respect to individual graphical elements or groups of graphical elements included in various clock face user interfaces (e.g., affordances, graphical elements included within affordances, complications, clock face elements, backgrounds, indicators, etc.) displayed by device 600 on display 602. Similar to the brightness level of a clock face user interface, the brightness level of a graphical element as displayed within a clock face user interface on display 602 may also by varied (e.g., using the techniques described below). Please note, however, that as depicted throughout the figures described below, brightness scale 630 reflects an overall brightness level of a respective clock face user interface (e.g., the entire clock face user interface being displayed, not the brightness level of individual graphical elements or groups of graphical elements within the respective clock face user interface), unless otherwise noted. Furthermore, brightness scale 630 is not part of any user interface displayed on device 600.
In addition to brightness scale 630, the relative displayed brightness of a clock face user interface and elements constituting the clock face user interfaces described below (e.g., graphical objects displayed in or on the user interface, backgrounds, etc.) are also represented by the depicted shading intensities in each figure (e.g., white or lighter greys indicating more brightly displayed elements; darker greys indicating less brightly displayed elements).
In some embodiments, brightness levels can be adjusted (increased or decreased) using alpha blending. In some embodiments, decreasing a brightness level includes using alpha blending without altering a backlight of the electronic device to create a simulated or real backlight level. For instance, the device can alpha blend image data representing a clock face user interface (or a portion of a clock face user interface such as an affordance or complication) with an increasingly opaque black masking layer to increasingly dim the clock face user interface as displayed on the screen (e.g., so that the user interface fades to black).
In some embodiments, a brightness level of a graphical object in a clock face user interface is changed by altering the shape or composition of the graphical object itself. For example, the brightness of a white clock hand by may decreased by reducing the thickness of the clock hand (e.g., removing white pixels from the element). In some embodiments, a brightness level of a graphical object is altered (e.g., reduced or dimmed) by replacing solid-colored regions of the object with a similarly colored outlines of the solid-colored regions. In some embodiments, a brightness level of a graphical object is reduced or dimmed by altering its colors, for example, by replacing lighter colors (e.g., white, light greys, yellows, etc.) with darker colors (black, dark greys, blues, etc.). Any combination of the brightness altering techniques described above or similar techniques well-known in the art, may be used for adjusting brightness levels of graphical objects and clock face user interfaces in accordance with the embodiments described below.
In general, different brightness levels can be achieved using various techniques, which can be employed separately or concurrently. In some embodiments, the brightness level of a graphical element is changed by changing (e.g., brightening, dimming) the brightness of some (or all) pixels of the graphical element. In some embodiments, the brightness level of the graphical element is changed by modifying the graphical element so that fewer (or more) pixels are lit up, such as by thinning (or thickening) lines of the graphical element, and removing (or adding) a background of the graphical element, reducing (or enlarging) a size of the graphical element.
Turning now to
As illustrated in
At
In
At
Corresponding elements in timer user interface 614-2 are displayed by device 600 differently than they were previously displayed in timer user interface 614-1. In
In some embodiments, the change in brightness levels between corresponding elements (e.g., affordances and/or objects) in timer user interfaces 614-1 and 614-2 are not uniform (e.g., timer indication 616-1 is changed from white to a first color in timer indication 616-2, and button 618-1 is changed from white to a second, different color in button 618-2). In some embodiments, device 600 displays one or more elements in timer user interface 614-2 at a reduced size compared to their corresponding elements in timer user interface 614-1.
In addition to displaying timer indication 616-2 at a lower brightness level, device 600 displays timer indication 616-2 at a lower level of precision (e.g., a lower level of accuracy) than timer indication 616-1. As was shown in
Furthermore, as discussed above, while device 600 was operating in the standard display mode, device 600 periodically updated timer indication 616-1 at a first update frequency. In
At
At
At
In some embodiments, while device 600 is operating in the low power mode, user interface objects, such as timer indication 616-2, are updated at different update frequencies based on whether one or more time-sensitive update criteria are met. For example, in
In
At
By increasing the update frequency of timer indication 616-2. (e.g., from the second update frequency to the third update frequency) when one or more time-sensitive update criteria are satisfied, device 600 can conserve power with less frequent updates when frequent updates are not needed (e.g., updating once every 25 seconds when there is greater than one minute remaining in the timer), and can also provide more useful information and/or a greater level of accuracy by increasing the frequency of updates in more time-sensitive scenarios (e.g., updating once every half second in the last minute of the timer). In some embodiments, the timer application and/or one or more elements of timer user interface 614-2 are updated at a higher frequency than the second update frequency (e.g., at the first update frequency, at the third update frequency, and/or a different update frequency) while the timer indication 616-2 is updated at the second update frequency. For example, in some embodiments, the timer application and/or one or more elements of timer user interface 614-2 are updated at a higher frequency than the second update frequency when there are less than two minutes remaining on the timer, and/or for all time periods (e.g., whereas the timer indication 616-2 is updated at the second update frequency for all time periods except for when there is less than one minute remaining on the timer).
At
In
In some embodiments, while device 600 is operating in the standard display mode, device 600 periodically updates one or more elements of stopwatch user interface 632-1 (e.g., elapsed time indication 634-1) at a first update frequency (e.g., more than once per second, every hundredth of a second, and/or every twentieth of a second). Additionally, while device 600 is operating in the standard display mode, device 600 displays elapsed time indication 634-1 at a first level of precision. In
At
At
At
At
As discussed above, corresponding elements in stopwatch user interface 632-2 are displayed by device 600 differently than they were previously displayed in stopwatch user interface 632-1. In
In some embodiments, the change in brightness levels between corresponding elements (e.g., affordances and/or objects) in stopwatch user interfaces 632-1 and 632-2 are not uniform. In some embodiments, one or more elements in stopwatch user interface 632-2 are displayed at a reduced size compared to their corresponding elements in stopwatch user interface 632-1.
While device 600 was operating in the standard display mode, device 600 periodically updated elapsed time indication 634-1 at a first update frequency (e.g., more than once a second, every hundredth of a second, and/or every twentieth of a second). As discussed above with reference to
Furthermore, in some embodiments, as also discussed above with reference to
In the example scenario depicted in
In
In the depicted embodiment, while certain non-static content in stopwatch user interface 632-2, such as elapsed time indication 634-2, is shown at a lower level of precision compared to stopwatch user interface 632-1 (e.g., shown at a lower level of precision when device 600 is in the low power display mode than when device 600 is in the standard display mode), static content is shown at the same level of precision as stopwatch user interface 632-1 (e.g., static content is shown at the same level of precision regardless of whether device 600 is in the low power display mode or in the standard display mode). For example, lap time indication 646-2 is shown at the same level of precision as lap time indication 646-1 (e.g., with lap time shown to the hundredth of a second).
At
At
As shown in
Stopwatch complication 658-2 is displayed at a lower brightness level than stopwatch complication 658-1. In
At
At
At
At
At
At
At
In
In the depicted example, one or more time-sensitive update criteria include a criterion that is satisfied when less than a threshold amount of time remains until a next scheduled alarm (e.g., less than one minute until the next scheduled alarm). In
At
At
In some embodiments, while device 600 is operating in the standard display mode, device 600 periodically updates one or more elements of navigation user interface 680-1 (e.g., next direction indication 682-1, map 684-1, and/or current location indication 686) at a first update frequency (e.g., more than once per second, every hundredth of a second, and/or every twentieth of a second).
Navigation user interface 680-2 is displayed at a lower brightness level than navigation user interface 680-1. Navigation user interface 680-2 includes next direction indication 682-2 and map 684-2. In the depicted embodiment, while operating in the low power display mode, device 600 does not display a current location indicator as part of navigation user interface 680-2.
In some embodiments, when operating in the standard display mode, device 600 displays map 684-1 at a first zoom level, and when operating in the low power display mode, device 600 displays map 684-2 at a second zoom level different from the first zoom level, wherein the second zoom level represents a zoomed out zoom level compared to the first zoom level. An example of such an implementation is depicted in
In the depicted example, one or more time-sensitive update criteria include a criterion that is met when less than a threshold distance remains until a next navigation instruction (e.g., less than one mile until the next navigation instruction). In
In 6AE (and also in
In
In
As described below, method 700 provides an intuitive way for managing display usage. The method reduces power usage and the likelihood of screen burn-in. The method also reduces the cognitive burden on a user for managing display usage, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a device to automatically manage display usage faster and more efficiently conserves power and increases the time between battery charges.
In some embodiments, a computer system (e.g., a smart phone, a smart watch, and/or a tablet) that is in communication with a display generation component (e.g., a display controller; a touch-sensitive display system; and/or a display (e.g., integrated and/or connected)), while the computer system is in a first mode (702) (e.g., a higher power consumption mode (e.g., a mode that corresponds to a brighter display, increased performance, and/or more frequent display updates)), displays (704), via the display generation component, a first user interface (e.g., 614-1, 626-1, 632-1, 650-1, and/or 680-1) that includes one or more user interface elements including a first user interface element (e.g., 616-1, 634-1, 658-1, 670-1, 682-1, and/or 684-1), where the user interface is associated with a first application (e.g., a timer application, a stopwatch application, an alarm clock application, and/or a navigation application).
While displaying the first user interface in the first mode (706), the computer system detects (708) that the computer system has met one or more criteria for transitioning from the first mode to a second mode, wherein the second mode is a lower power mode (e.g., reaching a duration of time since a last input, a wrist down gesture, and/or a hand cover gesture).
In response to detecting that the computer system has met one or more criteria for transitioning from the first mode to the second mode (710), the computer system enters the second mode, including displaying a second user interface (e.g., a low power user interface) (e.g., 614-2, 626-2, 632-2, 650-2, and/or 680-2) that is associated with the first application where the second user interface corresponds to the first user interface and is displayed at a location that occupies at least a portion of a display region that was occupied by the first user interface and includes one or more user interface elements including a second user interface element (e.g., 616-2, 634-2, 658-2, 670-2, 682-2, and/or 684-2). In some embodiments, the second user interface is a low power version of the first user interface. In some embodiments, the second user interface differs from the first user interface in one or more visual characteristics (e.g., size of elements, color, hue, saturation, opacity, shape). In some embodiments, the second user interface element corresponds to the first user interface element (e.g., is a low power version of the first user interface element). In some embodiments, the second user interface element differs from the first user interface element in one or more visual characteristics (e.g., brightness, size, color, hue, saturation, opacity, shape). In some embodiments, displaying the second user interface includes replacing display of the first user interface with the second user interface.
While the computer system is in the second mode (714), the computer system updates (716) an appearance of the second user interface element (e.g., 616-2, 634-2, 658-2, 670-2, 682-2, and/or 684-2) (in some embodiments, updating an appearance of the one or more user interface elements of the second user interface) periodically while maintaining the computer system in the second mode (e.g., while maintaining a dimmer display, decreased performance and/or less frequent display updates).
In accordance with a determination that one or more time-sensitive update criteria are not satisfied (e.g., in accordance with a determination that a time-sensitive update has not been detected) (718), the appearance of the second user interface element (in some embodiments, the appearance of the one or more user interface elements of the second user interface) is periodically updated at a first update frequency (e.g., 30 seconds, 1 minute, 2 minutes) (e.g.,
In some embodiments, while the computer system is in the first mode and the first user interface is displayed (e.g., user interface 614-1 in
In some embodiments, after periodically updating the appearance of the second user interface element (in some embodiments, the appearance of the one or more user interface elements of the second user interface) one or more times at the second update frequency (e.g., while the one or more time-sensitive update criteria are satisfied) (e.g., while also maintaining the computer system in the second mode), the computer system detects that the one or more time-sensitive update criteria are no longer satisfied (e.g., determining that one or more time-sensitive updates are no longer detected); and, in response to detecting that the one or more time-sensitive update criteria are no longer satisfied, the computer system periodically updates the appearance of the second user interface element (in some embodiments, the appearance of the one or more user interface elements of the second user interface) at the first update frequency while the one or more time-sensitive update criteria are not satisfied) (e.g., while also maintaining the computer system in the second mode).
In some embodiments, after periodically updating the appearance of the second user interface element (in some embodiments, the appearance of the one or more user interface elements of the second user interface) one or more times at the first update frequency (e.g., while the one or more time-sensitive update criteria are not satisfied) (e.g., while also maintaining the computer system in the second mode), the computer system detects that the one or more time-sensitive update criteria are satisfied (e.g., detecting one or more time-sensitive updates); and, in response to detecting that the one or more time-sensitive update criteria are satisfied, the computer system periodically updates the appearance of the second user interface element (in some embodiments, the appearance of the one or more user interface elements of the second user interface) at the second update frequency (e.g., while the one or more time-sensitive update criteria are satisfied) (e.g., while also maintaining the computer system in the second mode).
In some embodiments, while the computer system is in the second mode, the computer system detects that the computer system has met one or more criteria for transitioning from the second mode to the first mode (e.g., a higher power consumption mode (e.g., higher power consumption in the second mode than in the first mode)) (e.g., a wrist raise gesture, and/or a user input (e.g., a touch-screen user input, a user input via a rotatable and/or depressible input mechanism)); and, in response to detecting that the computer system has met one or more criteria for transitioning from the second mode to the first mode, the computer system enters the first mode; and, while the computer system is in the first mode, the computer system updates the appearance of the first user interface element (in some embodiments, the appearance of the one or more user interface elements of the first user interface) over time according to a third update frequency that is different from the first update frequency, wherein the third update frequency corresponds to a greater update frequency than the first update frequency. In some embodiments, the third update frequency corresponds to a greater update frequency than the first update frequency and the second update frequency.
In some embodiments, the one or more time-sensitive update criteria includes a first criterion that is satisfied when the first application is a foreground application (722) (e.g., an application operating in the foreground) (e.g., wherein the first criterion is not satisfied when the first application is not a foreground application (e.g., is a background application)) (e.g.,
In some embodiments, the second user interface element is a complication (e.g., 658-2) corresponding to the first application (724) (e.g., a complication that displays data received from the first application). In some embodiments, a complication refers to a clock face feature other than those used to indicate the hours, minutes, or seconds of a current time associated with the device. In some embodiments, complications provide data obtained from an application. In some embodiments, a complication includes an affordance that when selected launches a corresponding application. In some embodiments, a complication is displayed at a fixed, predefined location on the display while the device is in a particular power consumption mode. In some embodiments, in response to detecting a sequence of one or more inputs, the device may change or edit an aspect of a complication. For example, this could be used to change application data displayed by an application complication. In some embodiments, the complication may indicate a first set of information obtained by an application (e.g., application data) (for example, if the application is a weather application, a set of information could be a forecasted weather condition, a current temperature, etc), and upon editing, the complication could be updated to indicate a second set of information from the same application (e.g., if the application is a weather application, the display could be edited from showing a current temperature to showing current precipitation). In some embodiments, in response to detecting a sequence of one or more inputs, the device may change or edit a complication to indicate a set of information from a different application (e.g., if the application is a weather application, the display could be edited from showing weather to showing data from a calendar application). Updating a complication at a reduced update frequency when time-sensitive update criteria are not satisfied reduces power usage and improves the battery life of the device, while still providing periodic updates to the second user interface element. Updating a complication at an increased update frequency when time-sensitive update criteria are satisfied provides more timely visual updates to the user when such timely feedback is needed (e.g., when displaying time-sensitive information), thereby providing the user with improved visual feedback. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient by helping the user to provide proper inputs and reducing user mistakes when operating/interacting, with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the first application is a timer application (e.g., an application that counts down from a starting time) (e.g.,
In some embodiments, the first application is a stopwatch application (e.g., an application that measures how much time has elapsed from a starting condition (e.g., from a start input provided by a user)) (e.g.,
In some embodiments, the first application is an alarm clock application (e.g., an application that causes the computer system to output an alarm (e.g., a visual output, an auditory output, and/or a haptic output) at a predefined (e.g., user-defined) time) (e.g.,
In some embodiments, while in the second mode: at a first time, in accordance with a determination that the one or more time-sensitive update criteria are not satisfied, the computer system updates the appearance of the second user interface element (e.g., 616-2) periodically at the first update frequency while maintaining the computer system in the second mode (e.g., 616-2 in
In some embodiments, the second user interface element (e.g., 616-2) corresponds to the first user interface element (e.g., 616-1) (e.g., displays information corresponding to information displayed by the first user interface element) (e.g., is a low power version of the first user interface element) and is different from the first user interface element in one or more visual characteristics (e.g., brightness, position, size, color, hue, saturation, opacity, and/or shape) (e.g., 616-2 differs in color and/or brightness from 616-1); and updating the appearance of the second user interface element periodically while maintaining the computer system in the second mode comprises updating the appearance of the second user interface element periodically (e.g., regardless of whether at the first update frequency or at the second update frequency) while maintaining at least some of the one or more visual characteristics that are different from the first user interface element (e.g., 616-2 in
In some embodiments, while in the second mode: at a first time, in accordance with a determination that the one or more time-sensitive update criteria are not satisfied, the computer system updates the appearance of the second user interface element periodically at the first update frequency while maintaining the computer system in the second mode (e.g., 616-2 in
In some embodiments, the second user interface comprises a third user interface element (e.g., 646-2) (e.g., different from and/or separate from the second user interface element). The third user interface element displays a second set of information (e.g., different from the first set of information). At the first time, while the appearance of the second user interface element (e.g., 634-2) is updated periodically at the first update frequency and the first set of information is displayed at the first level of precision (e.g., 634-2 in
In some embodiments, the first application is a turn-by-turn navigation application (e.g., an application that provides turn-by-turn navigation directions for a user (e.g., navigation directions that are periodically and/or automatically updated based on a current position and/or location of the computer system)) (e.g.,
Note that details of the processes described above with respect to method 700 (e.g.,
In particular,
In some embodiments disclosed below, in response to determining that one or more mode change criteria have been met, a device transitions from a standard display mode (e.g., a higher power consumption mode) into a low power display mode (e.g., a lower power consumption mode), and replaces display of a higher power consumption user interface with a lower power consumption user interface. In some embodiments, the lower power consumption user interface varies based on whether a corresponding lower power consumption user interface is available for the higher power consumption user interface. In some embodiments, the lower power consumption user interface also varies based on whether the device (and/or an application) is authorized to display certain types of information while in the low power display mode. For example, if the device is displaying a higher power consumption user interface associated with (e.g., generated by) a first application when the one or more mode change criteria are met, and a corresponding lower power consumption user interface is not available, in some embodiments, the device displays a default lower power consumption user interface e.g., that is not generated by the application). In contrast, if a corresponding lower power consumption user interface is available, a determination is made as to whether the device and/or the first application are permitted to display the corresponding lower power consumption user interface (e.g., based on one or more user settings set by a user) and, if so permitted, a further determination is made as to whether the device and/or the first application are permitted to display all of the information that is displayed in the higher power consumption user interface in the lower power consumption user interface, or only a subset of the information. The examples shown in
At
As illustrated in
While displaying wallet user interface 802-1, device 600 determines that one or more mode change criteria have been met (e.g., detecting a wrist-down gesture using, for example, motion sensors; and/or no input of certain types for a threshold duration of time). In response to determining that the one or more mode change criteria have been met, device 600 transitions out of the standard display mode and into a low power display mode (e.g., from a higher power consumption mode to a lower power consumption mode). Furthermore, in response to determining that the one or more mode change criteria have been met, device 600 replaces display of wallet user interface 802-1 (e.g., a higher power consumption user interface) with a lower power consumption user interface. In some embodiments, the lower power consumption user interface varies based on various determinations.
Corresponding elements in wallet user interface 802-2 are displayed by device 600 differently than they were previously displayed in wallet user interface 802-1. In
In some embodiments, the change in brightness levels between corresponding elements (e.g., affordances and/or objects) in wallet user interfaces 802-1 and 802-2 are not uniform. In some embodiments, device 600 displays one or more elements in wallet user interface 802-2 at a reduced size compared to their corresponding elements in wallet user interface 802-1.
In
As shown in
In some embodiments, even if wallet user interface 802-1 does have (e.g., does provide and/or define) a corresponding lower power consumption user interface (e.g., wallet user interface 802-2), device 600 displays user interface 806 in accordance with a determination that device 600 (e.g., and/or the wallet application) is not authorized to display application information pertaining to the wallet application (e.g., one or more user interfaces provided by and/or generated by the wallet application) when in the low power display mode. In some embodiments, user interface 806 represents a default low power consumption user interface to be used in scenarios in which device 600 and/or an application are not authorized to display application information pertaining to the application when device 600 is in the low power display mode. In some embodiments, such restrictions can be specified by a user (e.g., via one or more user settings),
As illustrated in
While displaying messaging user interface 810-1, device 600 determines that one or more mode change criteria have been met. In response to determining that the one or more mode change criteria have been met, device 600 transitions out of the standard display mode and into a low power display mode (e.g., from a higher power consumption mode to a lower power consumption mode). Furthermore, in response to determining that the one or more mode change criteria have been met, device 600 replaces display of messaging user interface 810-1 (e.g., a higher power consumption user interface) with a lower power consumption user interface. As discussed above, in some embodiments, the lower power consumption user interface varies based on various determinations.
Corresponding elements in messaging user interface 810-2 are displayed by device 600 differently than they were previously displayed in messaging user interface 810-1. In
In some embodiments, the change in brightness levels between corresponding elements (e.g., affordances and/or objects) in messaging user interfaces 810-1 and 810-2 are not uniform. In some embodiments, device 600 displays one or more elements in messaging user interface 810-2 at a reduced size compared to their corresponding elements in messaging user interface 810-1.
As shown in
In some embodiments, even if messaging user interface 810-1 does have a corresponding lower power consumption user interface (e.g., messaging user interface 810-2), device 600 displays user interface 816 in accordance with a determination that device 600 is not authorized (e.g., and/or the messaging application is not authorized) to display application information pertaining to the messaging application. In some embodiments, such restrictions can be specified by a user (e.g., via one or more user settings).
While displaying fitness user interface 820-1, device 600 determines that one or more mode change criteria have been met. In response to determining that the one or more mode change criteria have been met, device 600 transitions out of the standard display mode and into a low power display mode (e.g., from a higher power consumption mode to a lower power consumption mode). Furthermore, in response to determining that the one or more mode change criteria have been met, device 600 replaces display of fitness user interface 820-1 (e.g., a higher power consumption user interface) with a lower power consumption user interface. As introduced above, in some embodiments, the lower power consumption user interface varies based on various determinations.
As shown in
In some embodiments, even if fitness user interface 820-1 does have a corresponding lower power consumption user interface (e.g., fitness user interface 820-2), device 600 displays user interface 826 in accordance with a determination that device 600 is not authorized (e.g., and/or the fitness application is not authorized) to display application information pertaining to the fitness application. In some embodiments, such restrictions can be specified by a user (e.g., via one or more user settings).
As illustrated in
While displaying notification center user interface 830, device 600 determines that one or more mode change criteria have been met. In response to determining that the one or more mode change criteria have been met, device 600 transitions out of the standard display mode and into a low power display mode (e.g., from a higher power consumption mode to a lower power consumption mode). Furthermore, in response to determining that the one or more mode change criteria have been met, device 600 replaces display of notification center user interface 830 (e.g., a higher power consumption user interface) with a lower power consumption user interface.
As shown in
In some embodiments, even if notification center user interface 830 does have a corresponding lower power consumption user interface, device 600 displays user interface 834 in accordance with a determination that device 600 is not authorized to display application information pertaining to the notification center. In some embodiments, such restrictions can be specified by a user (e.g., via one or more user settings).
In some embodiments, device 600 provides users with one or more user settings that can be manipulated by a user to define whether notification information for certain applications can be displayed while device 600 is in the lower power display mode (see, e.g.,
Even if device 600 is authorized to display application information and/or notification information for one or more applications in the low power display mode, in some embodiments, device 600 is not authorized to display notification information in notification center user interface 830 while operating in the low power display mode. For example, in the example scenario depicted in
At
Corresponding elements in clock face user interface 838-2 are displayed by device 600 differently than they were previously displayed in clock face user interface 838-1. In
In addition to being displayed at a lower brightness level, clock face user interface 838-2 includes less content than clock face user interface 838-1. For example, in
In some embodiments, device 600 maintains display of virtual assistant user interface 856 until device 600 determines that a voice input from a user is completed (e.g., a threshold amount of time has passed without audio input) and/or until a user provides a user input (e.g., a gesture) corresponding to a request to cease display of virtual assistant user interface 856. In some embodiments, while virtual assistant user interface 856 is displayed, device 600 is prevented from transitioning from the standard display mode to the low power display mode. For example, in some embodiments, the one or more mode change criteria includes a criterion that is met when virtual assistant user interface 856 is not displayed and/or when the virtual assistant application is not actively receiving an audio input.
At
At
At
At
Returning to
User interface 872 also includes options 875A, 875B, and 875C. Option 875A is selectable to enable or disable displaying complication data when device 600 is in the low power display mode. If option 875A is disabled, device 600 is not authorized to display any complication data for any application when device 600 is in the low power display mode. If option 875A is enabled, device 600 is authorized to display complication data for applications that are individually authorized (e.g., via options 887A-887G in
Returning to
Returning to
In
In
As described below, method 900 provides an intuitive way for managing display usage. The method reduces power usage and the likelihood of screen burn-in. The method also reduces the cognitive burden on a user for managing display usage, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a device to automatically manage display usage faster and more efficiently conserves power and increases the time between battery charges.
In some embodiments, a computer system (e.g., a smart phone, a smart watch, and/or a tablet) that is in communication with a display generation component (e.g., a display controller; a touch-sensitive display system; and/or a display (e.g., integrated and/or connected)), while the computer system is in a first mode (902) (e.g., a higher power consumption mode (e.g., a mode that corresponds to higher power consumption than a lower power consumption mode) (e.g., a mode that corresponds to a brighter display, increased performance, and/or more frequent display updates)), displays (904), via the display generation component, a first user interface (e.g., 802-1, 810-1, 820-1, 830, 838-1, 858-1, 862-1) that is associated with (e.g., generated by) a first application and that includes a plurality of user interface elements including a first user interface element depicting a first set of information (e.g., a number, a set of characters, and/or a string) (e.g., 804B-1, 812-1, 822-1, 832A, 832B, 840-1, 842-1, 844-1, 846-1, 848-1, 850-1, 852-1, 852-1, 854-1, 860-1, 864-1).
While displaying the first user interface (906), the computer system detects (908) that the computer system has met one or more criteria for transitioning from the first mode to a second mode (e.g., a lower power consumption mode (e.g., lower power consumption in the second mode than in the first mode)) (e.g., reaching a duration of time since a last input, a wrist down gesture, and/or a hand cover gesture). In response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode (910), and in accordance with a determination that the first application is authorized to display the first set of information while the computer system is in the second mode (912), the computer system displays (914) a second user interface (e.g., 802-2 in
In response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode (910), and in accordance with a determination that the first application is not authorized to display the first set of information while the computer system is in the second mode (916), the computer system displays (918) a third user interface (e.g., 802-2 in
In some embodiments, the determination that the first application is not authorized to display the first set of information while the computer system is in the second mode comprises a determination that the first application is not associated with (e.g., does not have, does not specify, is not configured to generate) a corresponding low power state user interface. In some embodiments, the determination that the first application is authorized to display the first set of information while the computer system is in the second mode comprises a determination that the first application is associated with (e.g., has, specifies, is configured to generate) a corresponding low power state user interface.
In some embodiments, displaying the second user interface associated with the first application includes replacing display of the first user interface with the second user interface. In some embodiments, displaying the third user interface includes replacing display of the first user interface with the third user interface. In some embodiments, the method further comprises: after displaying the third user interface (e.g., in accordance with the determination that the first application is not authorized to display the first set of information while the computer system in the second mode), detecting that the computer system has met one or more criteria for transitioning from the second mode to the first mode (e.g., a wrist up gesture, a tap input, a button input, and/or a rotatable and/or depressible input mechanism input); and in response to detecting that the computer system has met the one or more criteria for transitioning from the second mode to the first mode, displaying the first user interface (e.g., replacing display of the third user interface with the first user interface), wherein the first user interface includes the first user interface element depicting the first set of information.
In some embodiments, the method further comprises: after displaying the second user interface in accordance with the determination that the first application is authorized to display the first set of information while the computer system is in the second mode), detecting that the computer system has met one or more criteria for transitioning from the second mode to the first mode (e.g., a wrist up gesture, a tap input, a swipe input, a button input, and/or a rotatable and/or depressible input mechanism input); and in response to detecting that the computer system has met the one or more criteria for transitioning from the second mode to the first mode, displaying the first user interface (e.g., replacing display of the second user interface with the first user interface), wherein the first user interface includes the first user interface element depicting the first set of information.
Displaying a third user interface that does not include the first set of information when it is determined that the first application is not authorized to display the first set of information while the computer system is in the second mode enhances security and can prevent unauthorized users from viewing sensitive information. Displaying a third user interface that does not include the first set of information when it is determined that the first application is not authorized to display the first set of information while the computer system is in the second mode also enhances the operability of the device and makes the user-device interface more efficient (e.g., by restricting unauthorized access) which, additionally, reduces power usage and improves battery life of the device by limiting the performance of restricted operations.
Displaying a second user interface and/or a third user interface in response to a determination that the computer system has met one or more criteria for transitioning from the first mode to the second mode provides the user with visual feedback about the state of the device (e.g., that the device is operating in a second mode (e.g., a lower power consumption mode)). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, displaying the third user interface includes displaying (920), at a location in the third user interface that corresponds to a location of the first set of information in the first user interface, a user interface element (e.g., 804B-3, 812-3, 822-2, 864-2) that does not convey the substance of the first set of information (e.g., a redaction element or an obscured (e.g., redacted) representation of the first set of information). In some embodiments, the user interface element that is displayed at the location that corresponds to the first set of information in the first user interface is displayed along with user interface elements that convey the substance of second information that was displayed in the first user interface (e.g., displaying the redaction element or the obscured representation of the first set of information while concurrently displaying a non-obscured representation of the second set of information) (e.g., one or more blocks of color (e.g., one or more solid blocks of color), and/or a blurred representation) (e.g., a representation of the first set of information that prevents a user (e.g., makes it impossible for a user) from seeing the first set of information) (e.g., a representation of the first set of information that represents the first set of information, but does not display the first set of information (e.g., a solid block of color that represents the first set of information)).
In some embodiments, if the first application is authorized to display the first set of information while the computer system is in the second mode, the second user interface displays the first set of information at a first position (e.g., within a first region) of the display generation component. If the first application is not authorized to display the first set of information while the computer system is in the second mode, the third user interface displays an obscured representation of the first set of information at the first position (e.g., within the first region) of the display generation component.
Obscuring the first set of information when it is determined that the first application is not authorized to display the first set of information while the computer system is in the second mode enhances security and can prevent unauthorized users from viewing sensitive information. Obscuring the first set of information when it is determined that the first application is not authorized to display the first set of information while the computer system is in the second mode also enhances the operability of the device and makes the user-device interface more efficient (e.g., by restricting unauthorized access) which, additionally, reduces power usage and improves battery life of the device by limiting the performance of restricted operations.
In some embodiments, the first user interface (e.g., 802-1, 810-1, 820-1, 838-1) includes a third user interface element (e.g., 804A-1, 804C-1, 814A-1, 814B-1, 814C-1, 814D-1, 814E-1, 814F-1, 824-1, 840-1, 854-1) depicting a second set of information, and displaying the third user interface comprises: in accordance with a determination that the first application is not authorized to display the first set of information while the computer system is in the second mode and that the first application is authorized to display the second set of information while the computer system is in the second mode, the third user interface does not include (e.g., does not display) the first set of information and the third user interface includes a fourth user interface element (e.g., 804A-2, 804C-2, 814A-2, 814B-2, 814C-2, 814D-2, 814E-2, 814F-2, 824-2, 840-2, 854-2) depicting (e.g., displaying) the second set of information. In some embodiments, displaying the second user interface associated with the first application further comprises: in accordance with a determination that the first application is authorized to display the first set of information while the computer system is in the second mode and is not authorized to display the second set of information while the computer system is in the second mode, the second user interface includes the second user interface element depicting the first set of information and does not include (e.g., does not display) the second set of information.
Displaying a third user interface that does not include the first set of information when it is determined that the first application is not authorized to display the first set of information while the computer system is in the second mode enhances security and can prevent unauthorized users from viewing sensitive information. Displaying a third user interface that does not include the first set of information when it is determined that the first application is not authorized to display the first set of information while the computer system is in the second mode also enhances the operability of the device and makes the user-device interface more efficient (e.g., by restricting unauthorized access) which, additionally, reduces power usage and improves battery life of the device by limiting the performance of restricted operations.
In some embodiments, the first set of information (e.g., 804B-1) comprises a plurality of characters including a first character and a second character; and the user interface element (e.g., 804B-3) that does not convey the substance of the first set of information comprises an obscured representation of the first set of information, including: an Obscured representation of the first character, and an obscured representation of the second character (e.g., 804B-3 in
In some embodiments, the first set of information (e.g., 804B-1, 8221) comprises a plurality of strings including a first string and a second string; and the user interface element (e.g., 804B-3, 822-2) that does not convey the first set of information comprises an obscured representation of the first set of information, including: an obscured representation of the first string, and an obscured representation of the second string (e.g., 804B-3 in
In some embodiments, while the computer system is in the first mode and the first user interface (e.g., 802-1, 862-1) is displayed, the first set of information occupies a first region of the display generation component that includes one or more other graphical elements other than the first set of information, and displaying the third user interface comprises displaying an obscured representation (e.g., 804B-3 in
In some embodiments, while the computer system is in the first mode, the computer system displays, via the display generation component, a fourth user interface (e.g., 802-1, 810-1, 820-1, 830, 838-1, 858-1, 862-1) that is associated with a second application different from the first application and that includes a plurality of user interface elements including a fifth user interface element (e.g., 804B-1, 812-1, 822-1, 832A, 832B, 840-1, 842-1, 844-1, 846-1, 848-1, 850-1, 852-1, 852-1, 854-1, 860-1, 864-1) depicting a third set of information. While displaying the fourth user interface, the computer system detects that the computer system has met one or more criteria for transitioning from the first mode to the second mode. In response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode, and in accordance with a determination that the second application is authorized to display the third set of information, the computer system displays a fifth user interface (e.g., 802-2 in
In some embodiments, the third user interface and the sixth user interface are substantially similar. In some embodiments, for a plurality of applications that are not associated with (e.g., do not have, do not specify, and/or are not configured to generate) a corresponding low power state user interface, when the device transitions from the first mode to the second mode (e.g., a lower power consumption mode), the device displays a substantially similar low power state user interface. For example, in some embodiments, the low power state user interface includes a blurred representation of a previously displayed user interface in a background portion overlaid by a time indicator. For example, in some embodiments, the third user interface includes a blurred representation of the first user interface overlaid by a time indicator, and the sixth user interface includes a blurred representation of the fourth user interface overlaid by the time indicator.
Providing a third user interface that omits and/or obscures sensitive information for a plurality of applications enhances security and can prevent unauthorized users from viewing sensitive information. Providing a third user interface that omits and/or obscures sensitive information for a plurality of applications also enhances the operability of the device and makes the user-device interface more efficient (e.g., by restricting unauthorized access) which, additionally, reduces power usage and improves battery life of the device by limiting the performance of restricted operations.
In some embodiments, the third user interface includes an obscured version of content from the first user interface that is obscured in a respective manner (e.g., blurred representation 808B) and the sixth user interface includes an Obscured version of content from the fourth user interface that is obscured in the respective manner (e.g., blurred representations 818B, 828B, 836B).
In some embodiments, the third user interface comprises: an obscured representation (e.g., a blurred representation) of at least a portion of the first user interface (e.g., 808B, 818B, 828B, 836B); and a time indicator (e.g., 808A, 818A, 828A, 836A) at a position on the display generation component overlapping at least a portion of the obscured representation of the at least a portion of the first user interface (e.g., a time indicator overlaid on the obscured representation of the first user interface); and the sixth user interface comprises: an obscured representation (e.g., a blurred representation) of at least a portion of the fourth user interface (e.g., 808B, 818B, 828B, 836B); and a time indicator (e.g., 808A, 818A, 828A, 836A) at a position on the display generation component overlapping at least a portion of the obscured representation of the at least a portion of the fourth user interface (e.g., a time indicator overlaid on the obscured representation of the fourth user interface). Obscuring the first user interface that includes sensitive information enhances security and can prevent unauthorized users from viewing sensitive information. Obscuring the first user interface that includes sensitive information also enhances the operability of the device and makes the user-device interface more efficient (e.g., by restricting unauthorized access) which, additionally, reduces power usage and improves battery life of the device by limiting the performance of restricted operations. Displaying a third user interface that includes an obscured representation of the first user interface also provides the user with visual feedback about the state of the device (e.g., that the device is operating in a second mode (e.g., a lower power consumption mode)). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the respective manner of obscuring content that is used for the third user interface and the sixth user interface is used for a plurality of applications (e.g.,
In some embodiments, while the computer system is in the first mode, the computer system displays a settings user interface (e.g., different from the first user interface, the second user interface, and/or the third user interface) comprising a plurality of selectable options (e.g., 895A-895G) corresponding to a plurality of applications (e.g., a plurality of applications installed on the computer system), including a first selectable option (e.g., 895A-895G) corresponding to (e.g., corresponding uniquely to) the first application and a second selectable option (e.g., 895A-895G) corresponding to (e.g., corresponding uniquely to) a second application different from the first application, wherein: the first selectable option has a state selected from a plurality of states including an enabled state and a disabled state, wherein the enabled state of the first selectable option authorizes the first application to display one or more low power user interfaces corresponding to (e.g., generated by) the first application when the computer system is in the second mode and the disabled state of the first selectable option prohibits the first application from displaying one or more low power user interfaces corresponding to (e.g., generated by) the first application when the computer system is in the second mode, and the second selectable option has a state selected from a plurality of states including an enabled state and a disabled state, wherein the enabled state of the second selectable option authorizes the second application to display one or more low power user interfaces corresponding to (e.g., generated by) the second application when the computer system is in the second mode, and the disabled state of the second selectable option prohibits the second application from displaying one or more low power user interfaces corresponding to (e.g., generated by) the second application when the computer system is in the second mode.
In some embodiments, the determination that the first application is authorized to display the first set of information while the computer system is in the second mode comprises a determination that the first selectable option is enabled. In some embodiments, the determination that the first application is not authorized to display the first set of information while the computer system is in the second mode comprises a determination that the first selectable option is disabled (e.g., is not enabled). Providing options that enable a user to identify specific applications that are authorized to display low power user interfaces when the computer system is in the second mode enhances security and can prevent unauthorized users from viewing sensitive information (e.g., by allowing a user to select certain applications that are authorized display low power user interfaces, and allowing a user to specify certain applications that are not authorized to display low power user interface). Providing options that enable a user to identify specific applications that are authorized to display low power user interfaces when the computer system is in the second mode also enhances the operability of the device and makes the user-device interface more efficient (e.g., by restricting unauthorized access) which, additionally, reduces power usage and improves battery life of the device by limiting the performance of restricted operations.
In some embodiments, while the computer system is in the first mode, the computer system displays a second settings user interface (e.g., 872) (e.g., the settings user interface, a second settings user interface different from the settings user interface) (e.g., different from the first user interface, the second user interface, and/or the third user interface) comprising a third selectable option (e.g., 874A) that has a state selected from a plurality of states including an enabled state and a disabled state, wherein: the enabled state of the third selectable option enables the computer system to display content via the display generation component when the computer system is in the second mode (e.g., display content in a low power mode, display one or more low power user interfaces) (e.g., the enabled state of the third selectable option enables an always on display setting), and the disabled state of the third selectable option prohibits the computer system from displaying content via the display generation component (e.g., turns off the display generation component) when the computer system is in the second mode (e.g., the disabled state of the third selectable option disables an always on display setting).
In some embodiments, the third selectable option corresponds to an always on display option, wherein enabling the always on display option causes the display to remain on (e.g., display content) in the second mode (e.g., remain on in a low power state), and disabling the always on display option causes the display to turn off (e.g., cease displaying content) in the second mode. In some embodiments, the method further comprises: while the computer system is in the first mode, displaying first content via the display generation component; while displaying the first content, detecting that the computer system has met one or more criteria for transitioning from the first mode to the second mode; and in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode: in accordance with a determination that the third selectable option is in the enabled state, displaying second content while the computer system is in the second mode; and in accordance with a determination that the third selectable option is in the disabled state, ceasing display of content via the display generation component (e.g., turning off the display, entering a sleep state) (not displaying content, displaying no content) while the computer system is in the second mode. Providing an option that enables a user to enable or disable an always on display enhances security and can prevent unauthorized users from viewing sensitive information e.g., by allowing a user to disable the always on display). Providing an option that enables a user to enable or disable an always on display also enhances the operability of the device and makes the user-device interface more efficient (e.g., by restricting unauthorized access) which, additionally, reduces power usage and improves battery life of the device by limiting the performance of restricted operations. Providing an option that enables a user to enable or disable an always on display reduces power usage and improves the battery life of the device.
In some embodiments, while the computer system is in the first mode, the computer system displays a third settings user interface (e.g., 884) (e.g., the settings user interface, the second settings user interface, a third settings user interface different from the settings user interface and/or the second settings user interface) (e.g., different from the first user interface, the second user interface, and/or the third user interface) comprising a fourth selectable option (e.g., 886, 887A-887G) that has a state selected from a plurality of states including an enabled state and a disabled state, wherein: the enabled state of the fourth selectable option enables the computer system to display one or more complications (e.g., a watch face complication; an element of the watch face that is not associated with providing an indication of time)(e.g., one or more complications corresponding to one or more applications) when the computer system is in the second mode, and the disabled state of the fourth selectable option prohibits the computer system from displaying the one or more complications when the computer system is in the second mode.
In some embodiments, the method further comprises: while the computer system is in the first mode, displaying a first complication via the display generation component; while displaying the first complication, detecting that the computer system has met one or more criteria for transitioning from the first mode to the second mode; and in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode: in accordance with a determination that the fourth selectable option is in the enabled state, displaying a second complication (e.g., a second complication corresponding to the first complication (e.g., a lower power version of the first complication)) while the computer system is in the second mode; and in accordance with a determination that the fourth selectable option is in the disabled state, ceasing display of the first complication (e.g., without displaying the second complication) while the computer system is in the second mode. Providing an option that enables a user to enable or disable complications when the computer system is in the second mode enhances security and can prevent unauthorized users from viewing sensitive information (e.g., by allowing a user to disable display of complications in the second mode). Providing an option that enables a user to enable or disable complications when the computer system is in the second mode also enhances the operability of the device and makes the user-device interface more efficient (e.g., by restricting unauthorized access) which, additionally, reduces power usage and improves battery life of the device by limiting the performance of restricted operations. Providing an option that enables a user to enable or disable complications when the computer system is in the second mode also reduces power usage and improves the battery life of the device (e.g., by allowing a user to disable display of complications in the second mode, which conserves energy by conserving computing resources required to compute and/or display the complications).
In some embodiments, the enabled state of the fourth selectable option (e.g., 886) enables the computer system to display a plurality of complications corresponding to a plurality of applications (e.g., a plurality of applications installed on the computer system, and/or a plurality of applications installed on the computer system configured to generate complications) when the computer system is in the second mode, and the disabled state of the fourth selectable option prohibits the computer system from displaying the plurality of complications corresponding to the plurality of applications when the computer system is in the second mode (e.g., the fourth selectable option controls display of complications in the second mode for a plurality of applications (e.g., but does not control display of complications for the plurality of applications when the computer system is in the first mode)).
In some embodiments, the method further comprises: while the computer system is in the first mode, displaying a first plurality of complications corresponding to a plurality of applications via the display generation component; while displaying the first plurality of complications, detecting that the computer system has met one or more criteria for transitioning from the first mode to the second mode; and in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode: in accordance with a determination that the fourth selectable option is in the enabled state, displaying a second plurality of complications corresponding to the plurality of applications (e.g., a second plurality of complications corresponding to the first plurality of complications (e.g., lower power versions of the first plurality of complications)) while the computer system is in the second mode; and in accordance with a determination that the fourth selectable option is in the disabled state, ceasing display of the first plurality of complications (e.g., without displaying the second plurality of complications) while the computer system is in the second mode.
Providing an option that enables a user to enable or disable complications when the computer system is in the second mode enhances security and can prevent unauthorized users from viewing sensitive information (e.g., by allowing a user to disable display of complications in the second mode). Providing an option that enables a user to enable or disable complications when the computer system is in the second mode also enhances the operability of the device and makes the user-device interface more efficient (e.g., by restricting unauthorized access) which, additionally, reduces power usage and improves battery life of the device by limiting the performance of restricted operations. Providing an option that enables a user to enable or disable complications when the computer system is in the second mode also reduces power usage and improves the battery life of the device (e.g., by allowing a user to disable display of complications in the second mode, which conserves energy by conserving computing resources required to compute and/or display the complications).
In some embodiments, the third settings user interface (e.g., 884) further comprises a plurality of selectable options (e.g., 887A-887G) including a fifth selectable option (e.g., 887A-887G) and a sixth selectable option (e.g., 887A-887G) (e.g., different from the fourth selectable option); the fifth selectable option corresponds to (e.g., corresponds uniquely to) the first application and has a state selected from a plurality of states including an enabled state and a disabled state; the enabled state of the fifth selectable option enables the computer system to display one or more complications corresponding to the first application when the computer system is in the second mode; the disabled state of the fifth selectable option prohibits the computer system from displaying the one or more complications corresponding to the first application when the computer system is in the second mode; the sixth selectable option corresponds to (e.g., corresponds uniquely to) a second application different from the first application and has a state selected from a plurality of states including an enabled state and a disabled state; the enabled state of the sixth selectable option enables the computer system to display one or more complications corresponding to the second application when the computer system is in the second mode; and the disabled state of the sixth selectable option prohibits the computer system from displaying the one or more complications corresponding to the second application when the computer system is in the second mode.
In some embodiments, the third settings user interface comprises a respective selectable option for each application of a plurality of applications (e.g., a plurality of applications installed on the computer system, and/or a plurality of applications installed on the computer system and configured to generate watch face complications), wherein an enabled state of a respective selectable option corresponding to (e.g., corresponding uniquely to) a respective application enables the computer system to display one or more complications corresponding to the respective application when the computer system is in the second mode, and a disabled state of the respective selectable option prohibits the computer system from displaying the one or more complications corresponding to the respective application when the computer system is in the second mode.
In some embodiments, the method further comprises: while the computer system is in the first mode, displaying a first complication associated with (e.g., corresponding uniquely to) the first application via the display generation component; while displaying the first complication, detecting that the computer system has met one or more criteria for transitioning from the first mode to the second mode; and in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode: in accordance with a determination that the fifth selectable option is in the enabled state, displaying a second complication associated with (e.g., corresponding uniquely to) the first application while the computer system is in the second mode (e.g., a second complication corresponding to the first complication (e.g., a lower power version of the first complication)); and in accordance with a determination that the fifth selectable option is in the disabled state, ceasing display of the first complication (e.g., without displaying the second complication) while the computer system is in the second mode.
In some embodiments, the method further comprises: while the computer system is in the first mode, displaying a third complication associated with (e.g., corresponding uniquely to) the second application via the display generation component; while displaying the third complication, detecting that the computer system has met one or more criteria for transitioning from the first mode to the second mode; and in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode: in accordance with a determination that, the sixth selectable option is in the enabled state, displaying a fourth complication associated with (e.g., corresponding uniquely to) the second application while the computer system is in the second mode (e.g., a fourth complication corresponding to the third complication (e.g., a lower power version of the third complication)); and in accordance with a determination that the sixth selectable option is in the disabled state, ceasing display of the third complication (e.g., without displaying the fourth complication) while the computer system is in the second mode.
Providing options that enable a user to enable or disable complications for individual applications when the computer system is in the second mode enhances security and can prevent unauthorized users from viewing sensitive information (e.g., by allowing a user to disable display of complications for certain applications in the second mode). Providing an option that enables a user to enable or disable complications for individual applications when the computer system is in the second mode also enhances the operability of the device and makes the user-device interface more efficient (e.g., by restricting unauthorized access) which, additionally, reduces power usage and improves battery life of the device by limiting the performance of restricted operations.
Providing options that enable a user to enable or disable complications for individual applications when the computer system is in the second mode also reduces power usage and improves the battery life of the device (e.g., by allowing a user to disable display of complications for one or more applications in the second mode, which conserves energy by conserving computing resources required to compute and/or display the complications).
In some embodiments, while the computer system is in the first mode, the computer system displays a fourth settings user interface (e.g., 888) (e.g., the settings user interface, the second settings user interface, the third settings user interface, and/or a fourth settings user interface different from the settings user interface, the second settings user interface, and/or the third settings user interface) (e.g., different from the first user interface, the second user interface, and/or the third user interface) comprising a seventh selectable option (e.g., 890) that has a state selected from a plurality of states including an enabled state and a disabled state, wherein: the enabled state of the seventh selectable option enables the computer system to display notifications (e.g., one or more notifications corresponding to one or more applications) when the computer system is in the second mode, and the disabled state of the seventh selectable option prohibits the computer system from displaying notifications when the computer system is in the second mode.
In some embodiments, the method further comprises: while the computer system is in the second mode, receiving notification information; and in response to receiving the notification information: in accordance with a determination that the seventh selectable option is in the enabled state, displaying a notification corresponding to the notification information while the computer system is in the second mode; and in accordance with a determination that the seventh selectable option is in the disabled state, forgoing displaying the notification corresponding to the notification while the computer system is in the second mode.
Providing an option that enables a user to enable or disable notifications when the computer system is in the second mode enhances security and can prevent unauthorized users from viewing sensitive information (e.g., by allowing a user to disable display of notifications in the second mode). Providing an option that enables a user to enable or disable notifications when the computer system is in the second mode also enhances the operability of the device and makes the user-device interface more efficient (e.g., by restricting unauthorized access) which, additionally, reduces power usage and improves battery life of the device by limiting the performance of restricted operations.
Providing an option that enables a user to enable or disable notifications when the computer system is in the second mode also reduces power usage and improves the battery life of the device (e.g., by allowing a user to disable display of notifications in the second mode, which conserves energy by conserving computing resources required to compute and/or display the notifications).
In some embodiments, the enabled state of the seventh selectable option (e.g., 890) enables the computer system to display notifications corresponding to a plurality of applications (e.g., a plurality of applications installed on the computer system, and/or a plurality of applications installed on the computer system configured to generate notifications) when the computer system is in the second mode, and the disabled state of the seventh selectable option prohibits the computer system from displaying notifications corresponding to the plurality of applications when the computer system is in the second mode (e.g., the seventh selectable option controls display of notifications for a plurality of applications while the computer system is in the second mode (e.g., but does not control display of notifications for the plurality of applications while the computer system is in the first mode)).
In some embodiments, the method further comprises: while the computer system is in the second mode, receiving notification information corresponding to a respective application of the plurality of applications; and in response to receiving the notification information corresponding to the respective application: in accordance with a determination that the seventh selectable option is in the enabled state, displaying a notification corresponding to the notification information while the computer system is in the second mode; and in accordance with a determination that the seventh selectable option is in the disabled state, forgoing displaying the notification corresponding to the notification information while the computer system is in the second mode.
Providing an option that enables a user to enable or disable notifications when the computer system is in the second mode enhances security and can prevent unauthorized users from viewing sensitive information (e.g., by allowing a user to disable display of notifications in the second mode), Providing an option that enables a user to enable or disable notifications when the computer system is in the second mode also enhances the operability of the device and makes the user-device interface more efficient (e.g., by restricting unauthorized access) which, additionally, reduces power usage and improves battery life of the device by limiting the performance of restricted operations.
Providing an option that enables a user to enable or disable notifications when the computer system is in the second mode also reduces power usage and improves the battery life of the device (e.g., by allowing a user to disable display of notifications in the second mode, which conserves energy by conserving computing resources required to compute and/or display the notifications).
In some embodiments, the fourth settings user interface (e.g., 888) further comprises a plurality of selectable options (e.g., 891A-891G), including an eighth selectable option (e.g., 891A-891G) and a ninth selectable option (e.g., 891A-891G) (e.g., different from the seventh selectable option); the eighth selectable option corresponds to (e.g., corresponds uniquely to) the first application and has a state selected from a plurality of states including an enabled state and a disabled state; the enabled state of the eighth selectable option enables the computer system to display notifications corresponding to the first application when the computer system is in the second mode; the disabled state of the eighth selectable option prohibits the computer system from displaying notifications corresponding to the first application when the computer system is in the second mode; the ninth selectable option corresponds to (e.g., corresponds uniquely to) a second application different from the first application and has a state selected from a plurality of states including an enabled state and a disabled state; the enabled state of the ninth selectable option enables the computer system to display notifications corresponding to the second application when the computer system is in the second mode; and the disabled state of the ninth selectable option prohibits the computer system from displaying notifications corresponding to the second application when the computer system is in the second mode.
In some embodiments, the fourth settings user interface comprises a respective selectable option for each application of a plurality of applications (e.g., a plurality of applications installed on the computer system, and/or a plurality of applications installed on the computer system configured to generate notifications), wherein an enabled state of a respective selectable option corresponding to (e.g., corresponding uniquely to) a respective application enables the computer system to display notifications corresponding to the respective application when the computer system is in the second mode, and a disabled state of the respective selectable option prohibits the computer system from displaying notifications corresponding to the respective application when the computer system is in the second mode.
In some embodiments, the method further comprises: while the computer system is in the second mode, receiving notification information corresponding to the first application; and in response to receiving the notification information: in accordance with a determination that the eighth selectable option is in the enabled state (e.g., regardless of the state of the ninth selectable option), displaying a notification corresponding to the notification information while the computer system is in the second mode; and in accordance with a determination that the eighth selectable option is in the disabled state (e.g., regardless of the state of the ninth selectable option), forgoing displaying the notification corresponding to the notification information while the computer system is in the second mode.
In some embodiments, the method further comprises: while the computer system is in the second mode, receiving notification information corresponding to the second application; and in response to receiving the notification information: in accordance with a determination that the ninth selectable option is in the enabled state (e.g., regardless of the state of the eighth selectable option), displaying a notification corresponding to the notification information while the computer system is in the second mode; and in accordance with a determination that the ninth selectable option is in the disabled state (e.g., regardless of the state of the eighth selectable option), forgoing displaying the notification corresponding to the notification information while the computer system is in the second mode.
Providing an option that enables a user to enable or disable notifications for individual applications when the computer system is in the second mode enhances security and can prevent unauthorized users from viewing sensitive information (e.g., by allowing a user to disable display of notifications for one or more applications in the second mode). Providing an option that enables a user to enable or disable notifications for individual applications when the computer system is in the second mode also enhances the operability of the device and makes the user-device interface more efficient (e.g., by restricting unauthorized access) which, additionally, reduces power usage and improves battery life of the device by limiting the performance of restricted operations.
Providing an option that enables a user to enable or disable notifications for individual applications when the computer system is in the second mode also reduces power usage and improves the battery life of the device (e.g., by allowing a user to disable display of notifications for one or more applications in the second mode, which conserves energy by conserving computing resources required to compute and/or display the notifications).
In some embodiments, while the computer system is in the first mode, the computer system displays a fifth settings user interface (e.g., 892) (e.g., the settings user interface, the second settings user interface, the third settings user interface, the fourth settings user interface, and/or a fifth settings user interface different from the settings user interface, the second settings user interface, the third settings user interface, and/or the fourth settings user interface) (e.g., different from the first user interface, the second user interface, and/or the third user interface) comprising a tenth selectable option (e.g., 894) that has a state selected from a plurality of states including an enabled state and a disabled state, wherein: the enabled state of the tenth selectable option enables the computer system to display application user interfaces (e.g., one or more application user interfaces corresponding to (e.g., generated by) one or more applications) (e.g., one or more low power application user interfaces) when the computer system is in the second mode, and the disabled state of the tenth selectable option prohibits the computer system from displaying application user interfaces when the computer system is in the second mode.
In some embodiments, the method further comprises: while the computer system is in the first mode, displaying a first application user interface corresponding to (e.g., generated by) a respective application via the display generation component; while displaying the first application user interface, detecting that the computer system has met one or more criteria for transitioning from the first mode to the second mode; and in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode: in accordance with a determination that the tenth selectable option is in the enabled state, displaying a second application user interface corresponding to (e.g., generated by) the respective application (e.g., a second application user interface corresponding to the first application user interface (e.g., a low power version of the first application user interface)) while the computer system is in the second mode; and in accordance with a determination that the tenth selectable option is in the disabled state, forgoing display of the second application user interface while the computer system is in the second mode (e.g., displaying a user interface that does not correspond to (e.g., is not generated by) the respective application, and/or forgoing displaying any content).
In some embodiments, the determination that the first application is authorized to display the first set of information while the computer system is in the second mode comprises a determination that the tenth selectable option is in the enabled state. In some embodiments, the determination that the first application is not authorized to display the first set of information while the computer system is in the second mode comprises a determination that the tenth selectable option is in the disabled state.
Providing an option that enables a user to enable or disable display of application user interfaces when the computer system is in the second mode enhances security and can prevent unauthorized users from viewing sensitive information (e.g., by allowing a user to disable display of application user interfaces in the second mode). Providing an option that enables a user to enable or disable display of application user interfaces when the computer system is in the second mode also enhances the operability of the device and makes the user-device interface more efficient (e.g., by restricting unauthorized access) which, additionally, reduces power usage and improves battery life of the device by limiting the performance of restricted operations. Providing an option that enables a user to enable or disable display of application user interfaces when the computer system is in the second mode also reduces power usage and improves the battery life of the device (e.g., by allowing a user to disable display of application user interfaces in the second mode, which conserves energy by conserving computing resources required to compute and/or display the application user interfaces).
In some embodiments, the enabled state of the tenth selectable option (e.g., 894) enables the computer system to display application user interfaces (e.g., one or more low power application user interfaces) corresponding to a plurality of applications (e.g., a plurality of applications installed on the computer system, and/or a plurality of applications installed on the computer system configured to generate low power user interfaces) when the computer system is in the second mode, and the disabled state of the tenth selectable option prohibits the computer system from displaying application user interfaces corresponding to the plurality of applications when the computer system is in the second mode (e.g., the tenth selectable option controls display of application user interfaces for a plurality of applications while the computer system is in the second mode (e.g., but does not control display of application user interfaces for the plurality of applications while the computer system is in the first mode)).
In some embodiments, the method further comprises: while the computer system is in the first mode, displaying a first application user interface corresponding to (e.g., generated by) a respective application of the plurality of applications via the display generation component; while displaying the first application user interface, detecting that the computer system has met one or more criteria for transitioning from the first mode to the second mode; and in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode: in accordance with a determination that the tenth selectable option is in the enabled state, displaying a second application user interface corresponding to (e.g., generated by) the respective application (e.g., a second application user interface corresponding to the first application user interface (e.g., a low power version of the first application user interface)) while the computer system is in the second mode; and in accordance with a determination that the tenth selectable option is in the disabled state, forgoing display of the second application user interface while the computer system is in the second mode (e.g., displaying a user interface that does not correspond to (e.g., is not generated by) the respective application, and/or forgoing displaying any content).
In some embodiments, the determination that the first application is authorized to display the first set of information while the computer system is in the second mode comprises a determination that the tenth selectable option is in the enabled state. In some embodiments, the determination that the first application is not authorized to display the first set of information while the computer system is in the second mode comprises a determination that the tenth selectable option is in the disabled state.
Providing an option that enables a user to enable or disable display of application user interfaces when the computer system is in the second mode enhances security and can prevent unauthorized users from viewing sensitive information (e.g., by allowing a user to disable display of application user interfaces in the second mode), Providing an option that enables a user to enable or disable display of application user interfaces when the computer system is in the second mode also enhances the operability of the device and makes the user-device interface more efficient (e.g., by restricting unauthorized access) which, additionally, reduces power usage and improves battery life of the device by limiting the performance of restricted operations.
Providing an option that enables a user to enable or disable display of application user interfaces when the computer system is in the second mode also reduces power usage and improves the battery life of the device (e.g., by allowing a user to disable display of application user interfaces in the second mode, which conserves energy by conserving computing resources required to compute and/or display the application user interfaces).
In some embodiments, the fifth settings user interface (e.g., 892) further comprises a plurality of selectable options (e.g., 895A-895G), including an eleventh selectable option (e.g., 895A-895G) and a twelfth selectable option (e.g., 895A-895G) (e.g., different from the tenth selectable option); the eleventh selectable option corresponds to (e.g., corresponds uniquely to) the first application and has a state selected from a plurality of states including an enabled state and a disabled state; the enabled state of the eleventh selectable option enables the computer system to display application user interfaces (e.g., one or more low power application user interfaces) corresponding to (e.g., generated by) the first application when the computer system is in the second mode; the disabled state of the eleventh selectable option prohibits the computer system from displaying application user interfaces corresponding to the first application when the computer system is in the second mode; the twelfth selectable option corresponds to (e.g., corresponds uniquely to) a second application different from the first application and has a state selected from a plurality of states including an enabled state and a disabled state; the enabled state of the twelfth selectable option enables the computer system to display application user interfaces (e.g., one or more low power application user interfaces) corresponding to (e.g., generated by) the second application when the computer system is in the second mode; and the disabled state of the twelfth selectable option prohibits the computer system from displaying application user interfaces corresponding to the second application when the computer system is in the second mode.
In some embodiments, the fifth settings user interface comprises a respective selectable option for each application of a plurality of applications (e.g., a plurality of applications installed on the computer system, and/or a plurality of applications installed on the computer system configured to generate low power state application user interfaces), wherein an enabled state of a respective selectable option corresponding to (e.g., corresponding uniquely to) a respective application enables the computer system to display application user interfaces (e.g., one or more low power application user interfaces) corresponding to the respective application when the computer system is in the second mode, and a disabled state of the respective selectable option prohibits the computer system from displaying application user interfaces corresponding to the respective application when the computer system is in the second mode.
In some embodiments, the method further comprises: while the computer system is in the first mode, displaying a first application user interface corresponding to (e.g., generated by) the first application via the display generation component; while displaying the first application user interface, detecting that the computer system has met one or more criteria for transitioning from the first mode to the second mode; and in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode: in accordance with a determination that the eleventh selectable option is in the enabled state (e.g., regardless of the state of the twelfth selectable option), displaying a second application user interface corresponding to (e.g., generated by) the first application while the computer system is in the second mode (e.g., a second application user interface corresponding to the first application user interface (e.g., a low power version of the first application user interface)); and in accordance with a determination that the eleventh selectable option is in the disabled state (e.g., regardless of the state of the twelfth selectable option), forgoing display of the second application user interface while the computer system is in the second mode (e.g., displaying a user interface that does not correspond to (e.g., is not generated by) the first application, and/or forgoing displaying any content).
In some embodiments, the method further comprises: while the computer system is in the first mode, displaying a third application user interface corresponding to (e.g., generated by) the second application via the display generation component; while displaying the third application user interface, detecting that the computer system has met one or more criteria, for transitioning from the first mode to the second mode; and in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode: in accordance with a determination that the twelfth selectable option is in the enabled state (e.g., regardless of the state of the eleventh selectable option), displaying a fourth application user interface corresponding to (e.g., generated by) the second application while the computer system is in the second mode (e.g., a fourth application user interface corresponding to the third application user interface (e.g., a low power version of the third application user interface)); and in accordance with a determination that the twelfth selectable option is in the disabled state (e.g., regardless of the state of the eleventh selectable option), forgoing display of the fourth application user interface while the computer system is in the second mode (e.g., displaying a user interface that does not correspond to (e.g., is not generated by) the second application, and/or forgoing displaying any content).
Providing options that enable a user to enable or disable display of application user interfaces for individual applications when the computer system is in the second mode enhances security and can prevent unauthorized users from viewing sensitive information by allowing a user to disable display of application user interfaces for one or more applications in the second mode). Providing options that enable a user to enable or disable display of application user interfaces for individual applications when the computer system is in the second mode also enhances the operability of the device and makes the user-device interface more efficient (e.g., by restricting unauthorized access) which, additionally, reduces power usage and improves battery life of the device by limiting the performance of restricted operations.
Providing options that enable a user to enable or disable display of application user interfaces for individual applications when the computer system is in the second mode also reduces power usage and improves the battery life of the device (e.g., by allowing a user to disable display of application user interfaces for one or more applications in the second mode, which conserves energy by conserving computing resources required to compute and/or display the application user interfaces).
Note that details of the processes described above with respect to method 900 (e.g.,
In particular,
At
In
At
Corresponding elements in map user interface 1002-2 are displayed by device 600 differently than they were previously displayed in map user interface 1002-1. For example, in
In some embodiments, the change in brightness levels between corresponding user interface elements in map user interface 1002-1 and 1002-2 are not uniform. In some embodiments, device 600 displays one or more elements in map user interface 1002-2 at a reduced size compared to their corresponding elements in map user interface 1002-1.
Furthermore, as discussed above, while device 600 was operating in the standard display mode, device 600 periodically updated one or more elements of map user interface 1002-1, including geographic map 1003-1, at a first update frequency. In
In addition to displaying geographic map 1003-2 at a lower brightness level than geographic map 1003-1, device 600 also displays geographic map 1003-2 at a different zoom level than geographic map 1003-1 was displayed. In
At 1013, while operating in the low power display mode and displaying map user interface 1002-2, device 600 detects input 1012 (e.g., a tap input and/or a non-tap input). At
At
At
In
At
As discussed above, while device 600 was operating in the standard display mode, device 600 periodically updated the appearance of one or more elements of navigation user interface 1016-1, including geographic map 1018-1, at a first update frequency. In
Corresponding elements in navigation user interface 1016-2 are displayed by device 600 differently than they were previously displayed in navigation user interface 1016-1. For example, in
As discussed above with reference to map user interface 1002-1 and map user interface 1002-2 in
At
As discussed above, in some embodiments, when device 600 is operating in the standard display mode, device 600 periodically updates the appearance of navigation user interface 1016-1 at a first update frequency, and when device 600 is operating in the low power display mode, device 600 periodically updates the appearance of navigation user interface 1016-2 at a second update frequency that is lower than the first update frequency. In some embodiments, if device 600 is receiving navigation information from the other device (e.g., device 1030) and displaying navigation user interface 1016-2 based on the received navigation information, device 600, while in the low power display mode, periodically updates the appearance of navigation user interface 1016-2 at a third update frequency that is greater than the second update frequency. This may be implemented, for example, to take advantage of the decreased power consumption that is achieved by receiving navigation information from device 1030. In
In other embodiments, if device 600 is tethered and/or connected to another device, and is receiving navigation information from the other device (e.g., device 1030), device 600, while in the low power display mode, periodically updates the appearance of navigation user interface 1016-2 at a fourth update frequency that is less than the second update frequency.
As described below, method 1100 provides an intuitive way for managing display usage. The method reduces power usage and the likelihood of screen burn-in. The method also reduces the cognitive burden on a user for managing display usage, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a device to automatically manage display usage faster and more efficiently conserves power and increases the time between battery charges.
In some embodiments, a computer system (e.g., a smart phone, a smart watch, and/or a tablet) that is in communication with a display generation component (e.g., a display controller; a touch-sensitive display system; and/or a display (e.g., integrated and/or connected)), while the computer system is in a first mode (1102) (e.g., a higher power consumption mode (e.g., a mode that corresponds to higher power consumption than a lower power consumption mode) (e.g., a mode that corresponds to a brighter display, increased performance, and/or more frequent display updates)), displays (1104), via the display generation component, a first user interface (e.g., 1002-1) that is associated with (e.g., generated by) a first application and that includes a first set of one or more user interface elements (e.g., 1004-1, 1006-1, 1010-1, 1003-1, 1008) including a first user interface element, wherein: the appearance of the first user interface element (e.g., 1003-1) is periodically updated at a first update frequency (in some embodiments, the appearance of the first set of one or more user interface elements is updated according to the first update frequency; in some embodiments, the appearance of a subset of the first set of one or more user interface elements is updated according to the first update frequency), and the first user interface is displayed at a first zoom level (e.g.,
While displaying the first user interface (1106) (e.g., 1002-1), the computer system detects (1108) that the computer system has met one or more criteria for transitioning from the first mode to a second mode (e.g., a lower power consumption mode (e.g., lower power consumption in the second mode than in the first mode)) (e.g., reaching a duration of time since a last input, a wrist down gesture, and/or a hand cover gesture).
In response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode (1110), the computer system displays (1112) a second user interface (e.g., 1002-2) that is different from the first user interface and is associated with (e.g., generated by) the first application, wherein: the second user interface corresponds to the first user interface and is displayed at a location that occupies at least a portion of a display region that was occupied by the first user interface, the second user interface includes a second set of one or more user interface elements (e.g., 1004-2, 1006-2, 1003-2, 1010-2) including a second user interface element (e.g., 1003-2) (in some embodiments, at least some of the second set of one or more user interface elements correspond to at least some of the first set of one or more user interface elements) (in some embodiments, the second user interface element corresponds to the first user interface element (e.g., is a low power version of the first user interface element)), the appearance of the second user interface element is periodically updated at a second update frequency that is different from the first update frequency and corresponds to a lower update frequency than the first update frequency, and the second user interface is displayed at a second zoom level different from the first zoom level. In some embodiments, the second user interface represents a zoomed out view of the first user interface.
In some embodiments, the second user interface is a lower power user interface and the first user interface is a higher power user interface (in some embodiments, the lower power user interface differs from the higher power interface in one or more visual characteristics (e.g., size of elements, color, hue, saturation, opacity, shape, and/or frequency of updates))). In some embodiments, displaying the second user interface includes replacing display of the first user interface with the second user interface.
In some embodiments, the method further comprises: after displaying the second user interface at the second zoom level, detecting that the computer system has met one or more criteria for transitioning from the second mode to the first mode (e.g., a wrist up gesture, a tap input, a button input, a rotatable and/or depressible input mechanism input); and in response to detecting that the computer system has met the one or more criteria for transitioning from the second mode to the first mode, displaying the first user interface (e.g., replacing display of the second user interface with the first user interface), wherein the first user interface corresponds to the second user interface and is displayed at a location that occupies at least a portion of a display region that was occupied by the second user interface; the first user interface includes the first set of one or more user interface elements including the first user interface element, the first user interface element is periodically updated at the first update frequency; and the first user interface is displayed at the first zoom level.
Updating the second user interface element at a reduced update frequency when the computer system is in the second mode reduces power usage and improves the battery life of the device, while still providing periodic updates to the second user interface element.
Changing a zoom level of the user interface when the computer system is in the second mode and when the second user interface element is updated at a reduced update frequency provides the user with more visual context when additional context may be needed (e.g., when updates are provided less frequency, additional context provides the user with more information that may be required between update intervals), thereby providing the user with improved visual feedback. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the second zoom level represents a zoomed out zoom level relative to the first zoom level (e.g., map 1003-2 in
In some embodiments, the first user interface (e.g., 1002-1) comprises a first geographic map (e.g., 1003-1), Updating a geographic map at a reduced update frequency when the computer system is in the second mode reduces power usage and improves the battery life of the device, while still providing periodic updates to the geographic map.
In some embodiments, the second user interface (e.g., 1002-2) comprises a second geographic map (e.g., 1003-2) that uses a different color scheme than the first geographic map (e.g., 1003-1) (e.g., a second geographic map different from the first geographic map) (e.g., a second geographic map that corresponds to the first geographic map) (in some embodiments, the second geographic map is a zoomed out version of the first geographic map (e.g., the first geographic map depicts a first geographic region, and the second geographic map includes the first geographic region, and also includes an additional region adjacent to and/or surrounding the first geographic region). Updating a geographic map at a reduced update frequency when the computer system is in the second mode reduces power usage and improves the battery life of the device, while still providing periodic updates to the geographic map.
In some embodiments, the first geographic map (e.g., 1003-1) comprises a location indicator user interface element (e.g., 1008) indicative of a current location of the computer system within the first geographic map; and the second geographic map (e.g., 1003-2) does not include the location indicator user interface element (e.g.,
In some embodiments, the first user interface comprises one or more geographic navigation directions (e.g., 1010-1, 1028-1) (e.g., route directions from a starting destination to a final destination, and/or turn-by-turn directions). Updating a user interface with one or more geographic navigation directions at a reduced update frequency when the computer system is in the second mode reduces power usage and improves the battery life of the device.
In some embodiments, while the computer system is in the first mode, the computer system displays, via the display generation component, a third user interface (e.g., 1016-1) that is associated with a second application, wherein: the third user interface includes turn by turn navigation directions (e.g., 1028-1) (e.g., navigation directions that are periodically and/or automatically updated based on a current position of the computer system), and the third user interface is displayed at a third zoom level (e.g.,
In some embodiments, displaying the first user interface (e.g., 1016-1) includes displaying turn by turn navigation directions (e.g., 1028-1) (e.g., navigation directions that are periodically and/or automatically updated based on a current position of the computer system), including concurrently displaying: a direction corresponding to a next upcoming navigation instruction (e.g., a left turn indication in 1028-1 in
In some embodiments, while the second user interface is displayed at the second zoom level (e.g.,
In some embodiments, the first user interface, when displayed prior to displaying the second user interface, includes (e.g., displays) a first set of information, and the first user interface, when displayed after displaying the second user interface, includes (e.g., displays) a second set of information. In some embodiments, the second set of information is different from the first set of information (e.g., the first user interface at the later point in time after displaying the second user interface displays different information from what was displayed at the earlier point in time when the first user interface was displayed prior to displaying the second user interface). For example, the first user interface prior to displaying the second set of information may display a first map portion based on the device's geographic position at that time, and the first user interface after displaying the second user interface may display a second, different map portion based on the device's new and/or updated geographic position at that later time. Zooming in the user interface when the computer system is in the first mode provides the user with more visual precision and detail when appropriate (e.g., providing a greater level of precision and detail when the computer system is in the first mode and the user interface is being updated at a greater frequency), thereby providing the user with improved visual feedback. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting, with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the first user interface is displayed (e.g., while the computer system is in the first mode) at a first brightness level (e.g., 1002-1 in
In some embodiments, the first user interface is displayed at a brighter brightness level than the second user interface by increasing a brightness (e.g., a brightness setting) of the display generation component when transitioning from the second mode to the first mode. In some embodiments, the first user interface is displayed at a brighter brightness level than the second user interface by replacing one or more user interface elements of the second user interface with brighter versions of those user interface elements (e.g., user interface elements having a different (e.g., brighter) set of colors). In some embodiments, the first user interface is displayed at a brighter brightness level than the second user interface by both increasing a brightness of the display generation component and replacing one or more user interface elements of the second user interface with brighter versions of those user interface elements.
In some embodiments, when the computer system is in the first mode, the display generation is component is set to a first brightness level, and when the computer system is in the second mode, the display generation component is set to a second brightness level that is dimmer (e.g., less bright) than the first brightness level. In some embodiments, the first user interface is displayed at the first brightness level prior to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode, the second user interface is displayed at the second brightness level after detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode and prior to detecting that the computer system has met the one or more criteria for transitioning from the second mode to the first mode, and the first user interface is displayed at the first brightness level after detecting that the computer system has met the one or more criteria for transitioning from the second mode to the first mode.
Dimming the display when the computer system is in the second mode reduces power usage and improves the battery life of the device, while still providing periodic updates to the second user interface element.
In some embodiments, the second user interface element (e.g., 1003-2) corresponds to the first user interface element (e.g., 1003-1) (e.g., is displayed at roughly the same position as the first user interface element; the first user interface element displays a first set of information and the second user interface element displays a second set of information that corresponds to the first set of information; and/or when transitioning from the first user interface to the second user interface, the second user interface element replaces display of the first user interface element). While the computer system is in the first mode, the first user interface element is displayed with a first color (e.g., a first set of colors) (e.g., 1003-1 in
In some embodiments, the second update frequency is an update frequency of one update per minute. Updating the second user interface element at a reduced update frequency of one update per minute when the computer system is in the second mode reduces power usage and improves the battery life of the device, while still providing periodic updates to the second user interface element.
In some embodiments, in accordance with a determination that the computer system (e.g., 600) is receiving update information for updating the second user interface element (e.g., 1018-2) from an external computer system (e.g., 1030) (e.g., an external computer system that is in communication with (e.g., wirelessly connected to) the computer system), the second update frequency is a third update frequency (e.g., a third update frequency that is different from the first update frequency, and corresponds to a lower update frequency than the first update frequency), and in accordance with a determination that the computer system is not receiving update information for updating the second user interface element from an external computer system (e.g., in accordance with a determination that the computer system is generating update information for updating the second user interface element), the second update frequency is a fourth update frequency different from the third update frequency (e.g., a fourth update frequency that is different from the first update frequency, and corresponds to a lower update frequency than the first update frequency). Modifying an update frequency for the second user interface element based on whether the computer system is receiving update information from an external computer system reduces power usage and improves the battery life of the device, while still providing periodic updates to the second user interface element.
In some embodiments, the third update frequency corresponds to a greater update frequency than the fourth update frequency (e.g., when the computer system is receiving update information from an external computer system, the second user interface element is updated with greater frequency). Increasing an update frequency when the computer system is receiving update information from an external computer system provides the user with more visual precision and detail when appropriate (e.g., providing greater update frequency when other computing resources are being conserved by the computer system because the external computer system is expending its own computing resources to generate and provide update information). Accordingly, the user is provided with improved visual feedback while also optimizing power usage and battery life. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the third update frequency corresponds to a lower update frequency than the fourth update frequency (e.g., when the computer system is receiving update information from an external computer system, the second user interface element is updated with lesser frequency). Decreasing an update frequency for the second user interface element when the computer system is receiving update information from an external computer system reduces power usage and improves the battery life of the device, while still providing periodic updates to the second user interface element.
Note that details of the processes described above with respect to method 1100 (e.g.,
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.
Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.
As described above, one aspect of the present technology is the gathering and use of data available from various sources to manage display usage. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, twitter IDs, home addresses, data or records relating to a user's health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information.
The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to present user interfaces that provide users with relevant information. Accordingly, use of such personal information data enables users to have calculated control of the delivered information. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. For instance, health and fitness data may be used to provide insights into a user's general wellness, or may be used as positive feedback to individuals using technology to pursue wellness goals.
The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the U.S., collection of or access to certain health data may be governed by federal and/or state laws, such as the Health. Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country.
Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of display user interfaces with managed display usage, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter. In another example, users can select certain types of information that is permissible to be displayed (e.g., permissible to be displayed in a low power mode) and can identify other types of information that are not permitted to be displayed (e.g., that are not permitted to be displayed in a low power mode). In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.
Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user's privacy. De-identification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods.
Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, content can be selected and delivered to users by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the computer system, or publicly available information.
This application claims priority to U.S. Provisional Patent Application Ser. No. 63/180,568, entitled “TECHNIQUES FOR MANAGING DISPLAY USAGE,” filed on Apr. 27, 2021, the contents of which are hereby incorporated by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 872200 | Rowe | Nov 1907 | A |
| 3148500 | Thomas | Sep 1964 | A |
| 4205628 | Null | Jun 1980 | A |
| 4355380 | Huguenin et al. | Oct 1982 | A |
| 4597674 | Thompson, III | Jul 1986 | A |
| 4847819 | Hong | Jul 1989 | A |
| 4945521 | Klaus | Jul 1990 | A |
| 5124959 | Yamazaki et al. | Jun 1992 | A |
| 5208790 | Sato et al. | May 1993 | A |
| 5220541 | Vuilleumier | Jun 1993 | A |
| 5408275 | Song et al. | Apr 1995 | A |
| 5455808 | Grupp et al. | Oct 1995 | A |
| 5500835 | Born | Mar 1996 | A |
| 5508979 | Eisenegger | Apr 1996 | A |
| 5659693 | Hansen et al. | Aug 1997 | A |
| 5825353 | Will | Oct 1998 | A |
| 5845257 | Fu et al. | Dec 1998 | A |
| 5892519 | Hirai et al. | Apr 1999 | A |
| 5986655 | Chiu et al. | Nov 1999 | A |
| 5999195 | Santangeli | Dec 1999 | A |
| 6043818 | Nakano et al. | Mar 2000 | A |
| 6084598 | Chekerylla | Jul 2000 | A |
| 6128012 | Seidensticker et al. | Oct 2000 | A |
| 6160767 | Ho | Dec 2000 | A |
| 6279018 | Kudrolli et al. | Aug 2001 | B1 |
| 6297795 | Kato et al. | Oct 2001 | B1 |
| 6353449 | Gregg et al. | Mar 2002 | B1 |
| 6359839 | Schenk et al. | Mar 2002 | B1 |
| 6441824 | Hertzfeld et al. | Aug 2002 | B2 |
| 6449219 | Hepp et al. | Sep 2002 | B1 |
| 6452597 | Goldberg et al. | Sep 2002 | B1 |
| 6477117 | Narayanaswami et al. | Nov 2002 | B1 |
| 6496780 | Harris et al. | Dec 2002 | B1 |
| 6525997 | Narayanaswami et al. | Feb 2003 | B1 |
| 6539243 | Kimura et al. | Mar 2003 | B1 |
| 6539343 | Zhao et al. | Mar 2003 | B2 |
| 6549218 | Gershony et al. | Apr 2003 | B1 |
| 6556222 | Narayanaswami | Apr 2003 | B1 |
| 6683653 | Miyake et al. | Jan 2004 | B1 |
| 6690623 | Maano | Feb 2004 | B1 |
| 6728533 | Ishii et al. | Apr 2004 | B2 |
| 6806893 | Kolawa et al. | Oct 2004 | B1 |
| 6809724 | Shiraishi et al. | Oct 2004 | B1 |
| 6871076 | Samn et al. | Mar 2005 | B2 |
| 6982695 | Canova et al. | Jan 2006 | B1 |
| 7036025 | Hunter | Apr 2006 | B2 |
| 7113809 | Noesgaard et al. | Sep 2006 | B2 |
| 7203380 | Chiu et al. | Apr 2007 | B2 |
| 7257254 | Tunney et al. | Aug 2007 | B2 |
| 7302650 | Allyn et al. | Nov 2007 | B1 |
| 7378954 | Wendt et al. | May 2008 | B2 |
| 7479949 | Jobs et al. | Jan 2009 | B2 |
| 7515509 | Klein et al. | Apr 2009 | B2 |
| 7515903 | Cast | Apr 2009 | B1 |
| 7619615 | Donoghue et al. | Nov 2009 | B1 |
| 7637204 | Sumser et al. | Dec 2009 | B2 |
| 7716057 | Horvitz | May 2010 | B2 |
| 7751285 | Cain et al. | Jul 2010 | B1 |
| 7773460 | Holt | Aug 2010 | B2 |
| 7843769 | Ishida et al. | Nov 2010 | B2 |
| 7898542 | Yu et al. | Mar 2011 | B1 |
| 7907476 | Lee | Mar 2011 | B2 |
| 8041968 | Tupman | Oct 2011 | B2 |
| 8046617 | Fleck et al. | Oct 2011 | B2 |
| 8238876 | Teng et al. | Aug 2012 | B2 |
| 8245143 | Yach et al. | Aug 2012 | B2 |
| 8364855 | James et al. | Jan 2013 | B2 |
| 8405663 | Wikkerink et al. | Mar 2013 | B2 |
| 8462997 | Soldan et al. | Jun 2013 | B2 |
| 8595649 | Sherrard et al. | Nov 2013 | B2 |
| 8635475 | Lin et al. | Jan 2014 | B2 |
| 8725842 | Al-Nasser | May 2014 | B1 |
| 8768648 | Panther et al. | Jul 2014 | B2 |
| 8775844 | Peterson | Jul 2014 | B1 |
| 8847903 | Stokes et al. | Sep 2014 | B2 |
| 8854925 | Lee et al. | Oct 2014 | B1 |
| 8924894 | Yaksick et al. | Dec 2014 | B1 |
| 8938394 | Faaborg et al. | Jan 2015 | B1 |
| 8948819 | Yun et al. | Feb 2015 | B2 |
| 8963894 | Klassen et al. | Feb 2015 | B2 |
| 9070092 | Shieh et al. | Jun 2015 | B2 |
| 9082314 | Tsai | Jul 2015 | B2 |
| 9141270 | Stuart et al. | Sep 2015 | B1 |
| 9152211 | Gunn et al. | Oct 2015 | B2 |
| 9152212 | Gunn | Oct 2015 | B2 |
| 9171268 | Penilla et al. | Oct 2015 | B1 |
| 9173052 | Hauser et al. | Oct 2015 | B2 |
| 9197738 | Peev et al. | Nov 2015 | B2 |
| 9237855 | Hong et al. | Jan 2016 | B2 |
| 9239605 | Nanda et al. | Jan 2016 | B1 |
| 9259615 | Weast et al. | Feb 2016 | B2 |
| 9292310 | Chaudhri et al. | Mar 2016 | B2 |
| 9369537 | Mathew et al. | Jun 2016 | B1 |
| 9377762 | Hoobler et al. | Jun 2016 | B2 |
| 9436269 | Yang | Sep 2016 | B2 |
| 9448685 | Somin et al. | Sep 2016 | B1 |
| 9459781 | Kocienda et al. | Oct 2016 | B2 |
| 9542070 | Xu et al. | Jan 2017 | B2 |
| 9547425 | Kocienda et al. | Jan 2017 | B2 |
| 9557806 | Väyrynen | Jan 2017 | B2 |
| 9568891 | Adams et al. | Feb 2017 | B2 |
| 9582165 | Wilson et al. | Feb 2017 | B2 |
| 9594354 | Kahn et al. | Mar 2017 | B1 |
| 9600178 | Yun et al. | Mar 2017 | B2 |
| 9606695 | Matas | Mar 2017 | B2 |
| 9609230 | Bakshi et al. | Mar 2017 | B1 |
| 9625987 | LaPenna | Apr 2017 | B1 |
| 9635255 | Baldwin | Apr 2017 | B1 |
| 9651922 | Hysek et al. | May 2017 | B2 |
| 9753436 | Ely et al. | Sep 2017 | B2 |
| 9756172 | Piemonte | Sep 2017 | B2 |
| 9794397 | Min et al. | Oct 2017 | B2 |
| 9939872 | Graham | Apr 2018 | B2 |
| 10019599 | Moran et al. | Jul 2018 | B1 |
| 10062133 | Mishra et al. | Aug 2018 | B1 |
| 10183622 | Taguchi et al. | Jan 2019 | B2 |
| 10268432 | Kyung | Apr 2019 | B2 |
| 10275148 | Matas et al. | Apr 2019 | B2 |
| 10282078 | Choi | May 2019 | B2 |
| 10303289 | Sepulveda et al. | May 2019 | B2 |
| 10304347 | Wilson et al. | May 2019 | B2 |
| 10317977 | Yang | Jun 2019 | B2 |
| 10356070 | Cha et al. | Jul 2019 | B2 |
| 10459887 | Dvortsov | Oct 2019 | B1 |
| 10489508 | Zhai et al. | Nov 2019 | B2 |
| 10620590 | Guzman et al. | Apr 2020 | B1 |
| 10643246 | Suprasadachandran Pillai | May 2020 | B1 |
| 10649644 | Ma | May 2020 | B2 |
| 10684592 | Chang et al. | Jun 2020 | B2 |
| 10721711 | Kirov et al. | Jul 2020 | B2 |
| 10761702 | Block et al. | Sep 2020 | B2 |
| 10788797 | Guzman et al. | Sep 2020 | B1 |
| 10807005 | Dugan et al. | Oct 2020 | B2 |
| 10817981 | Belkin | Oct 2020 | B1 |
| 10852905 | Guzman et al. | Dec 2020 | B1 |
| 10878782 | Guzman et al. | Dec 2020 | B1 |
| 10908559 | Guzman et al. | Feb 2021 | B1 |
| 10936345 | Guzman et al. | Mar 2021 | B1 |
| 11009833 | Essery | May 2021 | B2 |
| 11023090 | Xu et al. | Jun 2021 | B2 |
| 11050873 | Kim et al. | Jun 2021 | B2 |
| 11061372 | Chen et al. | Jul 2021 | B1 |
| 11435887 | Mirho et al. | Sep 2022 | B1 |
| 20020054066 | Kikinis et al. | May 2002 | A1 |
| 20020054157 | Hayashi et al. | May 2002 | A1 |
| 20020054541 | Hall et al. | May 2002 | A1 |
| 20020059623 | Rodriguez et al. | May 2002 | A1 |
| 20020081976 | Fujisawa et al. | Jun 2002 | A1 |
| 20020098857 | Ishii | Jul 2002 | A1 |
| 20020099452 | Kawai | Jul 2002 | A1 |
| 20020131331 | Molander et al. | Sep 2002 | A1 |
| 20030002391 | Biggs et al. | Jan 2003 | A1 |
| 20030027621 | Libby et al. | Feb 2003 | A1 |
| 20030052928 | Williams | Mar 2003 | A1 |
| 20030067497 | Pichon et al. | Apr 2003 | A1 |
| 20030107603 | Clapper | Jun 2003 | A1 |
| 20030135769 | Loughran | Jul 2003 | A1 |
| 20030140309 | Saito et al. | Jul 2003 | A1 |
| 20030164847 | Zaima et al. | Sep 2003 | A1 |
| 20030169306 | Makipaa et al. | Sep 2003 | A1 |
| 20030214885 | Powell et al. | Nov 2003 | A1 |
| 20030229900 | Reisman | Dec 2003 | A1 |
| 20040001105 | Chew et al. | Jan 2004 | A1 |
| 20040017733 | Sullivan | Jan 2004 | A1 |
| 20040021699 | Fildebrandt et al. | Feb 2004 | A1 |
| 20040047244 | Iino et al. | Mar 2004 | A1 |
| 20040066710 | Yuen et al. | Apr 2004 | A1 |
| 20040075699 | Franchi et al. | Apr 2004 | A1 |
| 20040075700 | Liu et al. | Apr 2004 | A1 |
| 20040083474 | Mckinlay et al. | Apr 2004 | A1 |
| 20040168107 | Sharp et al. | Aug 2004 | A1 |
| 20040181771 | Anonsen et al. | Sep 2004 | A1 |
| 20040192332 | Samn | Sep 2004 | A1 |
| 20040203342 | Sibecas et al. | Oct 2004 | A1 |
| 20040218472 | Narayanaswami et al. | Nov 2004 | A1 |
| 20040225966 | Besharat et al. | Nov 2004 | A1 |
| 20040243547 | Chhatrapati et al. | Dec 2004 | A1 |
| 20040266491 | Howard et al. | Dec 2004 | A1 |
| 20050041667 | Miller et al. | Feb 2005 | A1 |
| 20050052446 | Plut | Mar 2005 | A1 |
| 20050094492 | Rosevear et al. | May 2005 | A1 |
| 20050124389 | Yang | Jun 2005 | A1 |
| 20050139852 | Chen et al. | Jun 2005 | A1 |
| 20050156873 | Walter et al. | Jul 2005 | A1 |
| 20050168566 | Tada et al. | Aug 2005 | A1 |
| 20050188856 | Sumser et al. | Sep 2005 | A1 |
| 20050190653 | Chen | Sep 2005 | A1 |
| 20050195173 | Mckay | Sep 2005 | A1 |
| 20050198319 | Chan et al. | Sep 2005 | A1 |
| 20050200611 | Goto et al. | Sep 2005 | A1 |
| 20050261031 | Seo et al. | Nov 2005 | A1 |
| 20050272462 | Okamoto | Dec 2005 | A1 |
| 20050278757 | Grossman et al. | Dec 2005 | A1 |
| 20060007785 | Fernandez et al. | Jan 2006 | A1 |
| 20060020904 | Aaltonen et al. | Jan 2006 | A1 |
| 20060035628 | Miller et al. | Feb 2006 | A1 |
| 20060085765 | Peterson et al. | Apr 2006 | A1 |
| 20060087502 | Karidis | Apr 2006 | A1 |
| 20060092770 | Demas | May 2006 | A1 |
| 20060123362 | Keely | Jun 2006 | A1 |
| 20060128419 | Shimizu et al. | Jun 2006 | A1 |
| 20060129948 | Hamzy et al. | Jun 2006 | A1 |
| 20060166708 | Kim et al. | Jul 2006 | A1 |
| 20060214935 | Boyd et al. | Sep 2006 | A1 |
| 20060277469 | Chaudhri et al. | Dec 2006 | A1 |
| 20070004451 | C. Anderson | Jan 2007 | A1 |
| 20070006096 | Kim et al. | Jan 2007 | A1 |
| 20070021153 | Novak | Jan 2007 | A1 |
| 20070052851 | Ochs et al. | Mar 2007 | A1 |
| 20070055947 | Ostojic et al. | Mar 2007 | A1 |
| 20070057775 | O'Reilly et al. | Mar 2007 | A1 |
| 20070094330 | Russell et al. | Apr 2007 | A1 |
| 20070101279 | Chaudhri et al. | May 2007 | A1 |
| 20070113181 | Blattner et al. | May 2007 | A1 |
| 20070146344 | Martin et al. | Jun 2007 | A1 |
| 20070192718 | Voorhees et al. | Aug 2007 | A1 |
| 20070211042 | Kim et al. | Sep 2007 | A1 |
| 20070213955 | Ishida et al. | Sep 2007 | A1 |
| 20070226653 | Moore et al. | Sep 2007 | A1 |
| 20070236475 | Wherry | Oct 2007 | A1 |
| 20070239754 | Schnitman et al. | Oct 2007 | A1 |
| 20070250772 | Milosevski | Oct 2007 | A1 |
| 20070261537 | Eronen et al. | Nov 2007 | A1 |
| 20070277127 | Carlson et al. | Nov 2007 | A1 |
| 20070279190 | Lugt et al. | Dec 2007 | A1 |
| 20070287140 | Liebowitz | Dec 2007 | A1 |
| 20080005599 | Theocharous | Jan 2008 | A1 |
| 20080071885 | Hardy et al. | Mar 2008 | A1 |
| 20080082930 | Omernick et al. | Apr 2008 | A1 |
| 20080095470 | Chao et al. | Apr 2008 | A1 |
| 20080098031 | Ducharme | Apr 2008 | A1 |
| 20080127268 | Bergeron et al. | May 2008 | A1 |
| 20080130421 | Akaiwa et al. | Jun 2008 | A1 |
| 20080143729 | Wyatt | Jun 2008 | A1 |
| 20080150959 | Marui et al. | Jun 2008 | A1 |
| 20080151700 | Inoue et al. | Jun 2008 | A1 |
| 20080167834 | Herz et al. | Jul 2008 | A1 |
| 20080168396 | Matas et al. | Jul 2008 | A1 |
| 20080168402 | Blumenberg | Jul 2008 | A1 |
| 20080170058 | Ahn et al. | Jul 2008 | A1 |
| 20080174606 | Rengarajan | Jul 2008 | A1 |
| 20080186808 | Lee | Aug 2008 | A1 |
| 20080192021 | Lim et al. | Aug 2008 | A1 |
| 20080195961 | Bae et al. | Aug 2008 | A1 |
| 20080201438 | Mandre et al. | Aug 2008 | A1 |
| 20080201647 | Lagerstedt et al. | Aug 2008 | A1 |
| 20080215240 | Howard et al. | Sep 2008 | A1 |
| 20080224988 | Whang | Sep 2008 | A1 |
| 20080246778 | Ham et al. | Oct 2008 | A1 |
| 20080247519 | Abella et al. | Oct 2008 | A1 |
| 20080270934 | Firebaugh et al. | Oct 2008 | A1 |
| 20090005882 | Boyer et al. | Jan 2009 | A1 |
| 20090012988 | Brown | Jan 2009 | A1 |
| 20090016168 | Smith | Jan 2009 | A1 |
| 20090016492 | Tsuchiya | Jan 2009 | A1 |
| 20090017800 | Middleton | Jan 2009 | A1 |
| 20090051327 | Bohne | Feb 2009 | A1 |
| 20090058821 | Chaudhri et al. | Mar 2009 | A1 |
| 20090059730 | Lyons et al. | Mar 2009 | A1 |
| 20090066533 | Park et al. | Mar 2009 | A1 |
| 20090068984 | Burnett | Mar 2009 | A1 |
| 20090070675 | Li | Mar 2009 | A1 |
| 20090077497 | Cho et al. | Mar 2009 | A1 |
| 20090143114 | Vargas et al. | Jun 2009 | A1 |
| 20090146962 | Ahonen et al. | Jun 2009 | A1 |
| 20090158173 | Palahnuk et al. | Jun 2009 | A1 |
| 20090164923 | Ovi et al. | Jun 2009 | A1 |
| 20090178007 | Matas et al. | Jul 2009 | A1 |
| 20090178008 | Herz et al. | Jul 2009 | A1 |
| 20090183080 | Thakkar et al. | Jul 2009 | A1 |
| 20090195497 | Fitzgerald et al. | Aug 2009 | A1 |
| 20090199130 | Tsern et al. | Aug 2009 | A1 |
| 20090249247 | Tseng et al. | Oct 2009 | A1 |
| 20090259958 | Ban | Oct 2009 | A1 |
| 20090262088 | Moll-Carrillo et al. | Oct 2009 | A1 |
| 20090264116 | Thompson et al. | Oct 2009 | A1 |
| 20090279392 | Scott et al. | Nov 2009 | A1 |
| 20090284389 | Klassen et al. | Nov 2009 | A1 |
| 20090287470 | Farnsworth et al. | Nov 2009 | A1 |
| 20090300146 | Park et al. | Dec 2009 | A1 |
| 20090300598 | Choi | Dec 2009 | A1 |
| 20090305732 | Marcellino et al. | Dec 2009 | A1 |
| 20090312059 | Pratt et al. | Dec 2009 | A1 |
| 20090315834 | Nurmi et al. | Dec 2009 | A1 |
| 20090319467 | Berg et al. | Dec 2009 | A1 |
| 20090327886 | Whytock et al. | Dec 2009 | A1 |
| 20100015774 | Shimamune et al. | Jan 2010 | A1 |
| 20100016771 | Jardine et al. | Jan 2010 | A1 |
| 20100026640 | Kim et al. | Feb 2010 | A1 |
| 20100060586 | Pisula et al. | Mar 2010 | A1 |
| 20100062905 | Rottler et al. | Mar 2010 | A1 |
| 20100064255 | Rottler et al. | Mar 2010 | A1 |
| 20100069035 | Johnson | Mar 2010 | A1 |
| 20100081473 | Chatterjee et al. | Apr 2010 | A1 |
| 20100085203 | Kahn et al. | Apr 2010 | A1 |
| 20100088597 | Shin et al. | Apr 2010 | A1 |
| 20100100841 | Shin et al. | Apr 2010 | A1 |
| 20100110082 | Myrick et al. | May 2010 | A1 |
| 20100124152 | Lee | May 2010 | A1 |
| 20100146437 | Woodcock et al. | Jun 2010 | A1 |
| 20100146463 | Cho et al. | Jun 2010 | A1 |
| 20100149573 | Pat et al. | Jun 2010 | A1 |
| 20100156833 | Kim et al. | Jun 2010 | A1 |
| 20100157742 | Relyea et al. | Jun 2010 | A1 |
| 20100167712 | Stallings et al. | Jul 2010 | A1 |
| 20100205563 | Haapsaari et al. | Aug 2010 | A1 |
| 20100217657 | Gazdzinski et al. | Aug 2010 | A1 |
| 20100218089 | Chao et al. | Aug 2010 | A1 |
| 20100223563 | Green | Sep 2010 | A1 |
| 20100225495 | Marui | Sep 2010 | A1 |
| 20100226213 | Drugge | Sep 2010 | A1 |
| 20100235726 | Ording et al. | Sep 2010 | A1 |
| 20100243516 | Martin et al. | Sep 2010 | A1 |
| 20100248688 | Teng et al. | Sep 2010 | A1 |
| 20100257469 | Kim et al. | Oct 2010 | A1 |
| 20100281374 | Schulz et al. | Nov 2010 | A1 |
| 20100289723 | London | Nov 2010 | A1 |
| 20100309149 | Blumenberg et al. | Dec 2010 | A1 |
| 20110000968 | Phillips et al. | Jan 2011 | A1 |
| 20110003616 | Gorsica et al. | Jan 2011 | A1 |
| 20110003621 | Atsumi | Jan 2011 | A1 |
| 20110003665 | Burton | Jan 2011 | A1 |
| 20110004835 | Yanchar et al. | Jan 2011 | A1 |
| 20110022294 | Apley | Jan 2011 | A1 |
| 20110023415 | Davlin et al. | Feb 2011 | A1 |
| 20110025719 | Yanase et al. | Feb 2011 | A1 |
| 20110029870 | May et al. | Feb 2011 | A1 |
| 20110047014 | De Angelo | Feb 2011 | A1 |
| 20110061010 | Wasko | Mar 2011 | A1 |
| 20110070924 | Kim et al. | Mar 2011 | A1 |
| 20110071818 | Jiang | Mar 2011 | A1 |
| 20110076992 | Chou et al. | Mar 2011 | A1 |
| 20110078624 | Missig et al. | Mar 2011 | A1 |
| 20110080411 | Wikkerink et al. | Apr 2011 | A1 |
| 20110083111 | Forutanpour et al. | Apr 2011 | A1 |
| 20110098928 | Hoffman et al. | Apr 2011 | A1 |
| 20110109540 | Milne et al. | May 2011 | A1 |
| 20110115721 | Li et al. | May 2011 | A1 |
| 20110117902 | Chang et al. | May 2011 | A1 |
| 20110119610 | Hackborn et al. | May 2011 | A1 |
| 20110128311 | Wakatsuki et al. | Jun 2011 | A1 |
| 20110129311 | Itoh | Jun 2011 | A1 |
| 20110138329 | Wells et al. | Jun 2011 | A1 |
| 20110151415 | Darling et al. | Jun 2011 | A1 |
| 20110157046 | Lee et al. | Jun 2011 | A1 |
| 20110166777 | Chavakula | Jul 2011 | A1 |
| 20110173221 | Ahiakpor et al. | Jul 2011 | A1 |
| 20110179372 | Moore et al. | Jul 2011 | A1 |
| 20110181521 | Reid et al. | Jul 2011 | A1 |
| 20110182151 | Geyer et al. | Jul 2011 | A1 |
| 20110191661 | Phillips et al. | Aug 2011 | A1 |
| 20110193878 | Seo et al. | Aug 2011 | A1 |
| 20110197165 | Filippov et al. | Aug 2011 | A1 |
| 20110202834 | Mandryk et al. | Aug 2011 | A1 |
| 20110202883 | Oh et al. | Aug 2011 | A1 |
| 20110205851 | Harris | Aug 2011 | A1 |
| 20110218765 | Rogers et al. | Sep 2011 | A1 |
| 20110230986 | Lafortune et al. | Sep 2011 | A1 |
| 20110234152 | Frossen et al. | Sep 2011 | A1 |
| 20110237221 | Prakash et al. | Sep 2011 | A1 |
| 20110248992 | Van et al. | Oct 2011 | A1 |
| 20110256848 | Bok et al. | Oct 2011 | A1 |
| 20110261079 | Ingrassia et al. | Oct 2011 | A1 |
| 20110281342 | Porsch et al. | Nov 2011 | A1 |
| 20110296324 | Goossens et al. | Dec 2011 | A1 |
| 20110306421 | Nishimoto et al. | Dec 2011 | A1 |
| 20110316858 | Shen et al. | Dec 2011 | A1 |
| 20110320938 | Schorsch et al. | Dec 2011 | A1 |
| 20120001922 | Escher et al. | Jan 2012 | A1 |
| 20120013552 | Ahn | Jan 2012 | A1 |
| 20120017180 | Flik et al. | Jan 2012 | A1 |
| 20120019152 | Bamhoefer et al. | Jan 2012 | A1 |
| 20120028707 | Raitt et al. | Feb 2012 | A1 |
| 20120036220 | Dare et al. | Feb 2012 | A1 |
| 20120047447 | Haq | Feb 2012 | A1 |
| 20120059787 | Brown et al. | Mar 2012 | A1 |
| 20120062470 | Chang et al. | Mar 2012 | A1 |
| 20120077554 | Ahn et al. | Mar 2012 | A1 |
| 20120079375 | Ogino et al. | Mar 2012 | A1 |
| 20120084729 | Lin et al. | Apr 2012 | A1 |
| 20120092383 | Hysek et al. | Apr 2012 | A1 |
| 20120098639 | Ijäs | Apr 2012 | A1 |
| 20120110438 | Peraza et al. | May 2012 | A1 |
| 20120113762 | Frost | May 2012 | A1 |
| 20120116550 | Hoffman et al. | May 2012 | A1 |
| 20120117507 | Tseng et al. | May 2012 | A1 |
| 20120124499 | Tsai et al. | May 2012 | A1 |
| 20120127198 | Gundavarapu | May 2012 | A1 |
| 20120150327 | Altman et al. | Jun 2012 | A1 |
| 20120151341 | Ko et al. | Jun 2012 | A1 |
| 20120154156 | Kuntzel | Jun 2012 | A1 |
| 20120176413 | Kulik et al. | Jul 2012 | A1 |
| 20120182226 | Tuli | Jul 2012 | A1 |
| 20120197523 | Kirsch | Aug 2012 | A1 |
| 20120210263 | Perry et al. | Aug 2012 | A1 |
| 20120212495 | Butcher et al. | Aug 2012 | A1 |
| 20120218201 | Tamas et al. | Aug 2012 | A1 |
| 20120231849 | Yamashita et al. | Sep 2012 | A1 |
| 20120243735 | Wu et al. | Sep 2012 | A1 |
| 20120254804 | Sheha et al. | Oct 2012 | A1 |
| 20120254810 | Heck et al. | Oct 2012 | A1 |
| 20120288139 | Singhar | Nov 2012 | A1 |
| 20120297346 | Hoffknecht et al. | Nov 2012 | A1 |
| 20120304084 | Kim et al. | Nov 2012 | A1 |
| 20120319984 | Borovsky et al. | Dec 2012 | A1 |
| 20120320081 | Kim et al. | Dec 2012 | A1 |
| 20120323933 | He et al. | Dec 2012 | A1 |
| 20120324390 | Tao et al. | Dec 2012 | A1 |
| 20130007665 | Chaudhri et al. | Jan 2013 | A1 |
| 20130019175 | Kotler et al. | Jan 2013 | A1 |
| 20130021236 | Bender et al. | Jan 2013 | A1 |
| 20130030892 | Liu et al. | Jan 2013 | A1 |
| 20130036377 | Colley | Feb 2013 | A1 |
| 20130044072 | Kobayashi et al. | Feb 2013 | A1 |
| 20130044080 | Chiang | Feb 2013 | A1 |
| 20130050263 | Khoe et al. | Feb 2013 | A1 |
| 20130055147 | Vasudev et al. | Feb 2013 | A1 |
| 20130057566 | Kriese et al. | Mar 2013 | A1 |
| 20130063084 | Tilvis et al. | Mar 2013 | A1 |
| 20130063383 | Anderssonreimer et al. | Mar 2013 | A1 |
| 20130069893 | Brinda et al. | Mar 2013 | A1 |
| 20130076757 | Pritting | Mar 2013 | A1 |
| 20130082965 | Wada et al. | Apr 2013 | A1 |
| 20130107674 | Gossweiler et al. | May 2013 | A1 |
| 20130111550 | Naveh et al. | May 2013 | A1 |
| 20130111579 | Newman et al. | May 2013 | A1 |
| 20130116967 | Akcasu et al. | May 2013 | A1 |
| 20130121119 | Umamoto | May 2013 | A1 |
| 20130132888 | Tijssen | May 2013 | A1 |
| 20130141371 | Hallford et al. | Jun 2013 | A1 |
| 20130143512 | Hernandez et al. | Jun 2013 | A1 |
| 20130147825 | Martin et al. | Jun 2013 | A1 |
| 20130157646 | Ferren et al. | Jun 2013 | A1 |
| 20130162611 | Lim et al. | Jun 2013 | A1 |
| 20130176293 | Pantfoerder | Jul 2013 | A1 |
| 20130185813 | Shim et al. | Jul 2013 | A1 |
| 20130191785 | Wu et al. | Jul 2013 | A1 |
| 20130205194 | Decker et al. | Aug 2013 | A1 |
| 20130212487 | Cote et al. | Aug 2013 | A1 |
| 20130215044 | Ahn et al. | Aug 2013 | A1 |
| 20130222271 | Alberth et al. | Aug 2013 | A1 |
| 20130225152 | Matthews et al. | Aug 2013 | A1 |
| 20130232443 | Ryu et al. | Sep 2013 | A1 |
| 20130234964 | Kim et al. | Sep 2013 | A1 |
| 20130239060 | Kang et al. | Sep 2013 | A1 |
| 20130239063 | Ubillos et al. | Sep 2013 | A1 |
| 20130254705 | Mooring et al. | Sep 2013 | A1 |
| 20130305189 | Kim | Nov 2013 | A1 |
| 20130314204 | Ho et al. | Nov 2013 | A1 |
| 20130316763 | Kader | Nov 2013 | A1 |
| 20130318437 | Jung et al. | Nov 2013 | A1 |
| 20130318466 | Estrada et al. | Nov 2013 | A1 |
| 20130322218 | Burkhardt et al. | Dec 2013 | A1 |
| 20130326418 | Utsuki et al. | Dec 2013 | A1 |
| 20130332721 | Chaudhri et al. | Dec 2013 | A1 |
| 20130332856 | Sanders et al. | Dec 2013 | A1 |
| 20130345978 | Lush et al. | Dec 2013 | A1 |
| 20130345980 | Van Os et al. | Dec 2013 | A1 |
| 20140013414 | Bruck et al. | Jan 2014 | A1 |
| 20140013945 | Tanaka et al. | Jan 2014 | A1 |
| 20140022183 | Ayoub et al. | Jan 2014 | A1 |
| 20140037109 | Ban | Feb 2014 | A1 |
| 20140043367 | Sakaino et al. | Feb 2014 | A1 |
| 20140047525 | Bonhoff | Feb 2014 | A1 |
| 20140055495 | Kim et al. | Feb 2014 | A1 |
| 20140059493 | Kim | Feb 2014 | A1 |
| 20140063049 | Armstrong-Muntner | Mar 2014 | A1 |
| 20140068755 | King et al. | Mar 2014 | A1 |
| 20140074570 | Hope et al. | Mar 2014 | A1 |
| 20140080465 | Cho | Mar 2014 | A1 |
| 20140082533 | Kelley et al. | Mar 2014 | A1 |
| 20140086123 | Deivasigamani | Mar 2014 | A1 |
| 20140094224 | Lozovoy et al. | Apr 2014 | A1 |
| 20140101169 | Kurata et al. | Apr 2014 | A1 |
| 20140120988 | Gunn et al. | May 2014 | A1 |
| 20140125620 | Panther et al. | May 2014 | A1 |
| 20140126336 | Goeller et al. | May 2014 | A1 |
| 20140129959 | Battles et al. | May 2014 | A1 |
| 20140135631 | Brumback et al. | May 2014 | A1 |
| 20140139454 | Mistry et al. | May 2014 | A1 |
| 20140139637 | Mistry et al. | May 2014 | A1 |
| 20140143678 | Mistry et al. | May 2014 | A1 |
| 20140143737 | Mistry et al. | May 2014 | A1 |
| 20140155031 | Lee et al. | Jun 2014 | A1 |
| 20140157189 | Morita | Jun 2014 | A1 |
| 20140157321 | Kurita et al. | Jun 2014 | A1 |
| 20140164907 | Jung et al. | Jun 2014 | A1 |
| 20140171132 | Ziemianska et al. | Jun 2014 | A1 |
| 20140173439 | Gutierrez et al. | Jun 2014 | A1 |
| 20140179272 | Zhang et al. | Jun 2014 | A1 |
| 20140189056 | St. Clair et al. | Jul 2014 | A1 |
| 20140189578 | Shuttleworth et al. | Jul 2014 | A1 |
| 20140189584 | Weng et al. | Jul 2014 | A1 |
| 20140192244 | Ishihara et al. | Jul 2014 | A1 |
| 20140195476 | Sxhmidt | Jul 2014 | A1 |
| 20140200691 | Lee et al. | Jul 2014 | A1 |
| 20140201655 | Mahaffey et al. | Jul 2014 | A1 |
| 20140210708 | Simmons et al. | Jul 2014 | A1 |
| 20140210801 | Li | Jul 2014 | A1 |
| 20140229752 | Lee et al. | Aug 2014 | A1 |
| 20140244009 | Mestas | Aug 2014 | A1 |
| 20140244165 | Bells et al. | Aug 2014 | A1 |
| 20140245161 | Yuen et al. | Aug 2014 | A1 |
| 20140245177 | Maklouf et al. | Aug 2014 | A1 |
| 20140250374 | Ohki et al. | Sep 2014 | A1 |
| 20140250391 | Jong et al. | Sep 2014 | A1 |
| 20140253487 | Bezinge et al. | Sep 2014 | A1 |
| 20140256298 | Moss et al. | Sep 2014 | A1 |
| 20140258935 | Nishida et al. | Sep 2014 | A1 |
| 20140267103 | Chaudhri | Sep 2014 | A1 |
| 20140267303 | Larkin et al. | Sep 2014 | A1 |
| 20140276244 | Kamyar | Sep 2014 | A1 |
| 20140282103 | Jerry | Sep 2014 | A1 |
| 20140282153 | Christiansen et al. | Sep 2014 | A1 |
| 20140282207 | Wouhaybi et al. | Sep 2014 | A1 |
| 20140282254 | Feiereisen et al. | Sep 2014 | A1 |
| 20140285699 | Kato et al. | Sep 2014 | A1 |
| 20140289660 | Min | Sep 2014 | A1 |
| 20140293755 | Geiser et al. | Oct 2014 | A1 |
| 20140302834 | Jones | Oct 2014 | A1 |
| 20140304664 | Lee et al. | Oct 2014 | A1 |
| 20140310350 | Borggaard et al. | Oct 2014 | A1 |
| 20140310618 | Venkatesh | Oct 2014 | A1 |
| 20140310643 | Karmanenko | Oct 2014 | A1 |
| 20140317543 | Kim | Oct 2014 | A1 |
| 20140320434 | Pantel | Oct 2014 | A1 |
| 20140325384 | Kobayashi | Oct 2014 | A1 |
| 20140325408 | Leppanen et al. | Oct 2014 | A1 |
| 20140328151 | Serber | Nov 2014 | A1 |
| 20140331314 | Fujioka | Nov 2014 | A1 |
| 20140342792 | Markus | Nov 2014 | A1 |
| 20140344723 | Malik et al. | Nov 2014 | A1 |
| 20140344820 | Kumar | Nov 2014 | A1 |
| 20140344951 | Brewer | Nov 2014 | A1 |
| 20140347275 | Jung et al. | Nov 2014 | A1 |
| 20140359124 | Adimatyam et al. | Dec 2014 | A1 |
| 20140359477 | Chen | Dec 2014 | A1 |
| 20140361955 | Goncalves | Dec 2014 | A1 |
| 20140362105 | Kocienda et al. | Dec 2014 | A1 |
| 20140371887 | Hoffman et al. | Dec 2014 | A1 |
| 20140380229 | Volodin et al. | Dec 2014 | A1 |
| 20150002735 | Moskovchenko | Jan 2015 | A1 |
| 20150011204 | Seo et al. | Jan 2015 | A1 |
| 20150015500 | Lee et al. | Jan 2015 | A1 |
| 20150019981 | Petitt et al. | Jan 2015 | A1 |
| 20150019982 | Petitt et al. | Jan 2015 | A1 |
| 20150022438 | Hong | Jan 2015 | A1 |
| 20150026615 | Choi et al. | Jan 2015 | A1 |
| 20150037545 | Sun | Feb 2015 | A1 |
| 20150042571 | Lombardi et al. | Feb 2015 | A1 |
| 20150043046 | Iwamoto | Feb 2015 | A1 |
| 20150049033 | Kim et al. | Feb 2015 | A1 |
| 20150052461 | Sullivan et al. | Feb 2015 | A1 |
| 20150055197 | Romanoff et al. | Feb 2015 | A1 |
| 20150058651 | Choi et al. | Feb 2015 | A1 |
| 20150061988 | Galu, Jr. | Mar 2015 | A1 |
| 20150062052 | Bernstein et al. | Mar 2015 | A1 |
| 20150062130 | Ho | Mar 2015 | A1 |
| 20150067596 | Brown et al. | Mar 2015 | A1 |
| 20150071043 | Kubota | Mar 2015 | A1 |
| 20150081474 | Kostka et al. | Mar 2015 | A1 |
| 20150082193 | Wallace et al. | Mar 2015 | A1 |
| 20150082446 | Flowers et al. | Mar 2015 | A1 |
| 20150083970 | Koh et al. | Mar 2015 | A1 |
| 20150100621 | Pan | Apr 2015 | A1 |
| 20150105125 | Min et al. | Apr 2015 | A1 |
| 20150106221 | Tapley | Apr 2015 | A1 |
| 20150106752 | Yang | Apr 2015 | A1 |
| 20150111558 | Yang | Apr 2015 | A1 |
| 20150112700 | Sublett et al. | Apr 2015 | A1 |
| 20150113468 | Clark | Apr 2015 | A1 |
| 20150117162 | Tsai et al. | Apr 2015 | A1 |
| 20150118657 | Shrake et al. | Apr 2015 | A1 |
| 20150128042 | Churchill et al. | May 2015 | A1 |
| 20150128078 | Oh et al. | May 2015 | A1 |
| 20150143234 | Norris, III | May 2015 | A1 |
| 20150160806 | Fey et al. | Jun 2015 | A1 |
| 20150160812 | Yuan et al. | Jun 2015 | A1 |
| 20150160856 | Jang et al. | Jun 2015 | A1 |
| 20150163210 | Meyers et al. | Jun 2015 | A1 |
| 20150172438 | Yang | Jun 2015 | A1 |
| 20150185703 | Tanaka | Jul 2015 | A1 |
| 20150185995 | Shoemaker et al. | Jul 2015 | A1 |
| 20150194137 | Wyatt | Jul 2015 | A1 |
| 20150205509 | Scriven et al. | Jul 2015 | A1 |
| 20150207922 | Kobayashi et al. | Jul 2015 | A1 |
| 20150217163 | Amis et al. | Aug 2015 | A1 |
| 20150220265 | Takahashi | Aug 2015 | A1 |
| 20150220299 | Kim et al. | Aug 2015 | A1 |
| 20150228048 | Heo | Aug 2015 | A1 |
| 20150241939 | Im et al. | Aug 2015 | A1 |
| 20150248235 | Offenberg et al. | Sep 2015 | A1 |
| 20150253736 | Watterson | Sep 2015 | A1 |
| 20150253740 | Nishijima et al. | Sep 2015 | A1 |
| 20150254875 | Zhang | Sep 2015 | A1 |
| 20150261284 | Lee | Sep 2015 | A1 |
| 20150262548 | Lin | Sep 2015 | A1 |
| 20150277545 | Flowers et al. | Oct 2015 | A1 |
| 20150277996 | Bank et al. | Oct 2015 | A1 |
| 20150286285 | Pantelopoulos et al. | Oct 2015 | A1 |
| 20150286372 | Swindell et al. | Oct 2015 | A1 |
| 20150286391 | Jacobs et al. | Oct 2015 | A1 |
| 20150301506 | Koumaiha | Oct 2015 | A1 |
| 20150301608 | Nagaraju et al. | Oct 2015 | A1 |
| 20150302624 | Burke | Oct 2015 | A1 |
| 20150309535 | Connor | Oct 2015 | A1 |
| 20150317945 | Andress et al. | Nov 2015 | A1 |
| 20150339261 | Jha et al. | Nov 2015 | A1 |
| 20150346694 | Hoobler et al. | Dec 2015 | A1 |
| 20150346824 | Chen | Dec 2015 | A1 |
| 20150355830 | Chaudhri et al. | Dec 2015 | A1 |
| 20150365892 | Ma et al. | Dec 2015 | A1 |
| 20150366518 | Sampson | Dec 2015 | A1 |
| 20150370469 | Leong et al. | Dec 2015 | A1 |
| 20150378592 | Kim | Dec 2015 | A1 |
| 20150379476 | Chaudhri et al. | Dec 2015 | A1 |
| 20160004345 | Imana | Jan 2016 | A1 |
| 20160004393 | Faaborg et al. | Jan 2016 | A1 |
| 20160018872 | Tu et al. | Jan 2016 | A1 |
| 20160022202 | Peterson et al. | Jan 2016 | A1 |
| 20160027420 | Eronen | Jan 2016 | A1 |
| 20160034133 | Wilson et al. | Feb 2016 | A1 |
| 20160034148 | Wilson et al. | Feb 2016 | A1 |
| 20160034152 | Wilson et al. | Feb 2016 | A1 |
| 20160034166 | Wilson et al. | Feb 2016 | A1 |
| 20160034167 | Wilson et al. | Feb 2016 | A1 |
| 20160041597 | Graham et al. | Feb 2016 | A1 |
| 20160044091 | Doumet | Feb 2016 | A1 |
| 20160044442 | Pacelli et al. | Feb 2016 | A1 |
| 20160048161 | Carceroni et al. | Feb 2016 | A1 |
| 20160048283 | Yang et al. | Feb 2016 | A1 |
| 20160049106 | Connell | Feb 2016 | A1 |
| 20160054710 | Jo et al. | Feb 2016 | A1 |
| 20160054892 | Kim et al. | Feb 2016 | A1 |
| 20160058336 | Blahnik et al. | Mar 2016 | A1 |
| 20160058337 | Blahnik et al. | Mar 2016 | A1 |
| 20160058375 | Rothkopf | Mar 2016 | A1 |
| 20160062450 | Han et al. | Mar 2016 | A1 |
| 20160062540 | Yang et al. | Mar 2016 | A1 |
| 20160062570 | Dascola et al. | Mar 2016 | A1 |
| 20160062572 | Yang et al. | Mar 2016 | A1 |
| 20160062589 | Wan et al. | Mar 2016 | A1 |
| 20160062630 | Anzures et al. | Mar 2016 | A1 |
| 20160073034 | Mukherjee et al. | Mar 2016 | A1 |
| 20160077718 | Kwon et al. | Mar 2016 | A1 |
| 20160085397 | Jain | Mar 2016 | A1 |
| 20160091867 | Mansour et al. | Mar 2016 | A1 |
| 20160098137 | Kim et al. | Apr 2016 | A1 |
| 20160134737 | Pulletikurty | May 2016 | A1 |
| 20160134840 | Mcculloch | May 2016 | A1 |
| 20160142763 | Kim et al. | May 2016 | A1 |
| 20160162112 | Lee et al. | Jun 2016 | A1 |
| 20160165037 | Youn et al. | Jun 2016 | A1 |
| 20160165038 | Lim et al. | Jun 2016 | A1 |
| 20160170731 | Maddern et al. | Jun 2016 | A1 |
| 20160179353 | Iskander | Jun 2016 | A1 |
| 20160180568 | Bullivant et al. | Jun 2016 | A1 |
| 20160180780 | Chen et al. | Jun 2016 | A1 |
| 20160187995 | Rosewall | Jun 2016 | A1 |
| 20160188179 | Roh | Jun 2016 | A1 |
| 20160188181 | Smith | Jun 2016 | A1 |
| 20160189328 | Vranjes et al. | Jun 2016 | A1 |
| 20160191511 | Tijerina et al. | Jun 2016 | A1 |
| 20160192324 | Zhang et al. | Jun 2016 | A1 |
| 20160205167 | Kolam et al. | Jul 2016 | A1 |
| 20160205241 | Atsumi | Jul 2016 | A1 |
| 20160205244 | Dvortsov | Jul 2016 | A1 |
| 20160205267 | Vaughn et al. | Jul 2016 | A1 |
| 20160217601 | Tsuda et al. | Jul 2016 | A1 |
| 20160252978 | Yoo et al. | Sep 2016 | A1 |
| 20160259518 | King et al. | Sep 2016 | A1 |
| 20160259535 | Fleizach et al. | Sep 2016 | A1 |
| 20160261675 | Block et al. | Sep 2016 | A1 |
| 20160266548 | Akiyama | Sep 2016 | A1 |
| 20160283094 | Choi | Sep 2016 | A1 |
| 20160313908 | Matas et al. | Oct 2016 | A1 |
| 20160320756 | Lee et al. | Nov 2016 | A1 |
| 20160327911 | Eim et al. | Nov 2016 | A1 |
| 20160327915 | Katzer et al. | Nov 2016 | A1 |
| 20160332025 | Repka | Nov 2016 | A1 |
| 20160342327 | Chi et al. | Nov 2016 | A1 |
| 20160357151 | Block | Dec 2016 | A1 |
| 20160357282 | Block | Dec 2016 | A1 |
| 20160357354 | Chen et al. | Dec 2016 | A1 |
| 20160357386 | Choi | Dec 2016 | A1 |
| 20160357394 | Tae et al. | Dec 2016 | A1 |
| 20160357413 | Block | Dec 2016 | A1 |
| 20160358311 | Chen et al. | Dec 2016 | A1 |
| 20170004798 | Park | Jan 2017 | A1 |
| 20170011210 | Cheong et al. | Jan 2017 | A1 |
| 20170039535 | Park et al. | Feb 2017 | A1 |
| 20170040001 | Zhang | Feb 2017 | A1 |
| 20170045993 | Oh et al. | Feb 2017 | A1 |
| 20170046024 | Dascola et al. | Feb 2017 | A1 |
| 20170046052 | Lee et al. | Feb 2017 | A1 |
| 20170053542 | Wilson et al. | Feb 2017 | A1 |
| 20170061934 | Shin | Mar 2017 | A1 |
| 20170068407 | Wilson et al. | Mar 2017 | A1 |
| 20170070716 | Kim et al. | Mar 2017 | A1 |
| 20170075305 | Ryu et al. | Mar 2017 | A1 |
| 20170075316 | Berdinis et al. | Mar 2017 | A1 |
| 20170075563 | Bauer et al. | Mar 2017 | A1 |
| 20170082983 | Katzer et al. | Mar 2017 | A1 |
| 20170109011 | Jiang | Apr 2017 | A1 |
| 20170123571 | Huang et al. | May 2017 | A1 |
| 20170123603 | Chang | May 2017 | A1 |
| 20170123640 | Wilson et al. | May 2017 | A1 |
| 20170127354 | Garland et al. | May 2017 | A1 |
| 20170134321 | Ushio et al. | May 2017 | A1 |
| 20170149795 | Day, II | May 2017 | A1 |
| 20170160898 | Lee | Jun 2017 | A1 |
| 20170164292 | Santamaria | Jun 2017 | A1 |
| 20170176950 | Jung et al. | Jun 2017 | A1 |
| 20170186399 | Moritani et al. | Jun 2017 | A1 |
| 20170209766 | Riley et al. | Jul 2017 | A1 |
| 20170212648 | Choi et al. | Jul 2017 | A1 |
| 20170230236 | Kim et al. | Aug 2017 | A1 |
| 20170236497 | Huitema | Aug 2017 | A1 |
| 20170255169 | Lee et al. | Sep 2017 | A1 |
| 20170257426 | Wilbur et al. | Sep 2017 | A1 |
| 20170266494 | Crankson et al. | Sep 2017 | A1 |
| 20170269715 | Kim et al. | Sep 2017 | A1 |
| 20170269792 | Xu et al. | Sep 2017 | A1 |
| 20170277136 | Minami | Sep 2017 | A1 |
| 20170286913 | Liu et al. | Oct 2017 | A1 |
| 20170287312 | Schofield et al. | Oct 2017 | A1 |
| 20170294174 | Albadawi et al. | Oct 2017 | A1 |
| 20170300013 | Satou et al. | Oct 2017 | A1 |
| 20170322658 | Lee et al. | Nov 2017 | A1 |
| 20170322711 | Robinson et al. | Nov 2017 | A1 |
| 20170325196 | Cho et al. | Nov 2017 | A1 |
| 20170329477 | Sachidanandam et al. | Nov 2017 | A1 |
| 20170337554 | Mokhasi et al. | Nov 2017 | A1 |
| 20170354845 | Williams et al. | Dec 2017 | A1 |
| 20170357329 | Park et al. | Dec 2017 | A1 |
| 20170357358 | Teutschler et al. | Dec 2017 | A1 |
| 20170357413 | Green | Dec 2017 | A1 |
| 20170357426 | Wilson et al. | Dec 2017 | A1 |
| 20170357427 | Wilson et al. | Dec 2017 | A1 |
| 20170357495 | Crane | Dec 2017 | A1 |
| 20170358276 | Mese et al. | Dec 2017 | A1 |
| 20170371394 | Chan | Dec 2017 | A1 |
| 20180011450 | Stackowski | Jan 2018 | A1 |
| 20180024619 | Kasuo et al. | Jan 2018 | A1 |
| 20180033311 | Berggren | Feb 2018 | A1 |
| 20180052428 | Abramov | Feb 2018 | A1 |
| 20180059903 | Lim et al. | Mar 2018 | A1 |
| 20180061308 | Bae et al. | Mar 2018 | A1 |
| 20180067633 | Wilson et al. | Mar 2018 | A1 |
| 20180074462 | Helder et al. | Mar 2018 | A1 |
| 20180081515 | Block et al. | Mar 2018 | A1 |
| 20180088537 | Murai | Mar 2018 | A1 |
| 20180088733 | Syed | Mar 2018 | A1 |
| 20180088797 | Mcatee et al. | Mar 2018 | A1 |
| 20180097925 | Ryu et al. | Apr 2018 | A1 |
| 20180120927 | Ma et al. | May 2018 | A1 |
| 20180121060 | Jeong | May 2018 | A1 |
| 20180136810 | Martin et al. | May 2018 | A1 |
| 20180150212 | Chen et al. | May 2018 | A1 |
| 20180150443 | Singleton | May 2018 | A1 |
| 20180157452 | Nelson et al. | Jun 2018 | A1 |
| 20180174550 | Zhang | Jun 2018 | A1 |
| 20180181078 | Imamura | Jun 2018 | A1 |
| 20180181381 | Michaely et al. | Jun 2018 | A1 |
| 20180188925 | Na et al. | Jul 2018 | A1 |
| 20180246635 | Baer et al. | Aug 2018 | A1 |
| 20180246639 | Han et al. | Aug 2018 | A1 |
| 20180260080 | Cho | Sep 2018 | A1 |
| 20180261183 | Gou et al. | Sep 2018 | A1 |
| 20180275739 | Minami et al. | Sep 2018 | A1 |
| 20180288560 | Naik et al. | Oct 2018 | A1 |
| 20180316783 | Ye et al. | Nov 2018 | A1 |
| 20180321842 | Lee et al. | Nov 2018 | A1 |
| 20180329587 | Ko et al. | Nov 2018 | A1 |
| 20180335927 | Anzures et al. | Nov 2018 | A1 |
| 20180336866 | Triverio et al. | Nov 2018 | A1 |
| 20180341389 | Kim | Nov 2018 | A1 |
| 20180343023 | Park et al. | Nov 2018 | A1 |
| 20180348844 | Lingutla | Dec 2018 | A1 |
| 20180352435 | Donley et al. | Dec 2018 | A1 |
| 20180366068 | Liu | Dec 2018 | A1 |
| 20180374429 | Nakamura | Dec 2018 | A1 |
| 20190018445 | Watanabe | Jan 2019 | A1 |
| 20190050045 | Jha et al. | Feb 2019 | A1 |
| 20190069244 | Jeon et al. | Feb 2019 | A1 |
| 20190079576 | Liu | Mar 2019 | A1 |
| 20190121300 | Peterson et al. | Apr 2019 | A1 |
| 20190121523 | Block et al. | Apr 2019 | A1 |
| 20190139207 | Jeong et al. | May 2019 | A1 |
| 20190163142 | Chang et al. | May 2019 | A1 |
| 20190180221 | Greenberger et al. | Jun 2019 | A1 |
| 20190182749 | Breaux et al. | Jun 2019 | A1 |
| 20190212707 | Minami et al. | Jul 2019 | A1 |
| 20190213037 | Kim et al. | Jul 2019 | A1 |
| 20190235748 | Seol et al. | Aug 2019 | A1 |
| 20190237003 | Cao et al. | Aug 2019 | A1 |
| 20190250813 | Block et al. | Aug 2019 | A1 |
| 20190268771 | Seo et al. | Aug 2019 | A1 |
| 20190279520 | Wilson et al. | Sep 2019 | A1 |
| 20190281154 | Choi et al. | Sep 2019 | A1 |
| 20190302972 | Kline et al. | Oct 2019 | A1 |
| 20190324620 | Gu et al. | Oct 2019 | A1 |
| 20190339860 | Chen et al. | Nov 2019 | A1 |
| 20190340348 | Yu et al. | Nov 2019 | A1 |
| 20190349469 | Skogen et al. | Nov 2019 | A1 |
| 20200042311 | Shin | Feb 2020 | A1 |
| 20200050332 | Yang et al. | Feb 2020 | A1 |
| 20200068095 | Nabetani | Feb 2020 | A1 |
| 20200073122 | Rothkopf | Mar 2020 | A1 |
| 20200089302 | Kim | Mar 2020 | A1 |
| 20200110946 | Kline et al. | Apr 2020 | A1 |
| 20200125037 | Jo et al. | Apr 2020 | A1 |
| 20200133206 | Jo et al. | Apr 2020 | A1 |
| 20200228646 | Hotes et al. | Jul 2020 | A1 |
| 20200242228 | Farraro et al. | Jul 2020 | A1 |
| 20200249632 | Olwal et al. | Aug 2020 | A1 |
| 20200264567 | Ok et al. | Aug 2020 | A1 |
| 20200279539 | Triverio et al. | Sep 2020 | A1 |
| 20200319348 | Oshita | Oct 2020 | A1 |
| 20200327862 | Sinha | Oct 2020 | A1 |
| 20200342144 | Alameh et al. | Oct 2020 | A1 |
| 20200348827 | Wilson et al. | Nov 2020 | A1 |
| 20200356063 | Guzman et al. | Nov 2020 | A1 |
| 20200356224 | Wilson | Nov 2020 | A1 |
| 20200356242 | Wilson et al. | Nov 2020 | A1 |
| 20200356252 | Ko et al. | Nov 2020 | A1 |
| 20200356687 | Salzman et al. | Nov 2020 | A1 |
| 20200359204 | Hawkins et al. | Nov 2020 | A1 |
| 20200379413 | Chen et al. | Dec 2020 | A1 |
| 20200408521 | Lyons et al. | Dec 2020 | A1 |
| 20210042028 | Block et al. | Feb 2021 | A1 |
| 20210048929 | Agnoli et al. | Feb 2021 | A1 |
| 20210132780 | Kyung | May 2021 | A1 |
| 20210149694 | Guzman et al. | May 2021 | A1 |
| 20210201732 | Ranjan | Jul 2021 | A1 |
| 20210208903 | Zhang et al. | Jul 2021 | A1 |
| 20210216654 | Ko et al. | Jul 2021 | A1 |
| 20210294438 | Yang et al. | Sep 2021 | A1 |
| 20210349426 | Chen et al. | Nov 2021 | A1 |
| 20210349427 | Chen et al. | Nov 2021 | A1 |
| 20210349583 | Guzman et al. | Nov 2021 | A1 |
| 20210349611 | Chen et al. | Nov 2021 | A1 |
| 20210349741 | Guzman et al. | Nov 2021 | A1 |
| 20220157184 | Wilson et al. | May 2022 | A1 |
| 20220184309 | Rosinko | Jun 2022 | A1 |
| 20220198984 | Connor et al. | Jun 2022 | A1 |
| 20220206681 | Mcatee et al. | Jun 2022 | A1 |
| 20220214785 | Giv | Jul 2022 | A1 |
| 20220221964 | Ko et al. | Jul 2022 | A1 |
| 20220229537 | Chen et al. | Jul 2022 | A1 |
| 20220236867 | Chen et al. | Jul 2022 | A1 |
| 20220276780 | Ko et al. | Sep 2022 | A1 |
| 20220351702 | Triverio et al. | Nov 2022 | A1 |
| 20230004270 | Chen et al. | Jan 2023 | A1 |
| 20230008229 | Chen et al. | Jan 2023 | A1 |
| 20230035532 | Chen et al. | Feb 2023 | A1 |
| 20230071987 | Zeng | Mar 2023 | A1 |
| 20230078153 | Yang et al. | Mar 2023 | A1 |
| 20230082876 | Guzman et al. | Mar 2023 | A1 |
| 20230368750 | Stack et al. | Nov 2023 | A1 |
| 20240118783 | Chen et al. | Apr 2024 | A1 |
| 20240257786 | Triverio et al. | Aug 2024 | A1 |
| Number | Date | Country |
|---|---|---|
| 2010249319 | Jun 2012 | AU |
| 2015101019 | Sep 2015 | AU |
| 2015101639 | Dec 2015 | AU |
| 2356232 | Mar 2002 | CA |
| 2781636 | Jul 2010 | CA |
| 2800123 | Jul 2016 | CA |
| 2986980 | May 2019 | CA |
| 707412 | Jun 2014 | CH |
| 1337638 | Feb 2002 | CN |
| 1397904 | Feb 2003 | CN |
| 1536511 | Oct 2004 | CN |
| 1610866 | Apr 2005 | CN |
| 1870796 | Nov 2006 | CN |
| 1932590 | Mar 2007 | CN |
| 1997957 | Jul 2007 | CN |
| 101273324 | Sep 2008 | CN |
| 101382438 | Mar 2009 | CN |
| 100492288 | May 2009 | CN |
| 101432722 | May 2009 | CN |
| 101505320 | Aug 2009 | CN |
| 101584124 | Nov 2009 | CN |
| 101627349 | Jan 2010 | CN |
| 101702112 | May 2010 | CN |
| 101819486 | Sep 2010 | CN |
| 101939740 | Jan 2011 | CN |
| 101981987 | Feb 2011 | CN |
| 102067070 | May 2011 | CN |
| 102376265 | Mar 2012 | CN |
| 102681648 | Sep 2012 | CN |
| 102687176 | Sep 2012 | CN |
| 102750070 | Oct 2012 | CN |
| 102831404 | Dec 2012 | CN |
| 103019567 | Apr 2013 | CN |
| 103154954 | Jun 2013 | CN |
| 103281419 | Sep 2013 | CN |
| 103294197 | Sep 2013 | CN |
| 103399480 | Nov 2013 | CN |
| 103399661 | Nov 2013 | CN |
| 103544920 | Jan 2014 | CN |
| 103562832 | Feb 2014 | CN |
| 103607660 | Feb 2014 | CN |
| 103631496 | Mar 2014 | CN |
| 103649897 | Mar 2014 | CN |
| 103853328 | Jun 2014 | CN |
| 103902165 | Jul 2014 | CN |
| 103914238 | Jul 2014 | CN |
| 103929662 | Jul 2014 | CN |
| 103973899 | Aug 2014 | CN |
| 203773233 | Aug 2014 | CN |
| 104281405 | Jan 2015 | CN |
| 104487929 | Apr 2015 | CN |
| 104501043 | Apr 2015 | CN |
| 104580576 | Apr 2015 | CN |
| 104978904 | Oct 2015 | CN |
| 105045079 | Nov 2015 | CN |
| 105204620 | Dec 2015 | CN |
| 105204931 | Dec 2015 | CN |
| 105260049 | Jan 2016 | CN |
| 105264479 | Jan 2016 | CN |
| 105335087 | Feb 2016 | CN |
| 105388966 | Mar 2016 | CN |
| 105389078 | Mar 2016 | CN |
| 105389107 | Mar 2016 | CN |
| 105430154 | Mar 2016 | CN |
| 105453016 | Mar 2016 | CN |
| 105516824 | Apr 2016 | CN |
| 105677179 | Jun 2016 | CN |
| 205608658 | Sep 2016 | CN |
| 106056848 | Oct 2016 | CN |
| 106486044 | Mar 2017 | CN |
| 106598201 | Apr 2017 | CN |
| 106605201 | Apr 2017 | CN |
| 107239101 | Oct 2017 | CN |
| 107430489 | Dec 2017 | CN |
| 107643677 | Jan 2018 | CN |
| 107870560 | Apr 2018 | CN |
| 108255049 | Jul 2018 | CN |
| 109196469 | Jan 2019 | CN |
| 109313655 | Feb 2019 | CN |
| 109690445 | Apr 2019 | CN |
| 110708581 | Jan 2020 | CN |
| 110471582 | Oct 2021 | CN |
| 202017105858 | Mar 2018 | DE |
| 0579093 | Jan 1994 | EP |
| 0831629 | Mar 1998 | EP |
| 1659504 | May 2006 | EP |
| 1674889 | Jun 2006 | EP |
| 1674977 | Jun 2006 | EP |
| 1750242 | Feb 2007 | EP |
| 1832969 | Sep 2007 | EP |
| 1855170 | Nov 2007 | EP |
| 1988432 | Nov 2008 | EP |
| 2120115 | Nov 2009 | EP |
| 2175367 | Apr 2010 | EP |
| 2194508 | Jun 2010 | EP |
| 2204702 | Jul 2010 | EP |
| 2290922 | Mar 2011 | EP |
| 2312512 | Apr 2011 | EP |
| 2360902 | Aug 2011 | EP |
| 2413577 | Feb 2012 | EP |
| 2423810 | Feb 2012 | EP |
| 2426902 | Mar 2012 | EP |
| 2565602 | Mar 2013 | EP |
| 2600215 | Jun 2013 | EP |
| 2629483 | Aug 2013 | EP |
| 2449434 | Mar 2014 | EP |
| 2738640 | Jun 2014 | EP |
| 2869292 | May 2015 | EP |
| 2942932 | Nov 2015 | EP |
| 2990887 | Mar 2016 | EP |
| 2993602 | Mar 2016 | EP |
| 3056949 | Aug 2016 | EP |
| 3101958 | Dec 2016 | EP |
| 3376342 | Sep 2018 | EP |
| 3401770 | Nov 2018 | EP |
| 3465408 | Aug 2020 | EP |
| 3896560 | Oct 2021 | EP |
| 2475669 | Jun 2011 | GB |
| 49-134364 | Dec 1974 | JP |
| 53-31170 | Mar 1978 | JP |
| 54-92359 | Jul 1979 | JP |
| 56-621 | Jan 1981 | JP |
| 3007616 | Feb 1995 | JP |
| 8-110955 | Apr 1996 | JP |
| 9-251084 | Sep 1997 | JP |
| 10-143636 | May 1998 | JP |
| 10-506472 | Jun 1998 | JP |
| 11-109066 | Apr 1999 | JP |
| 11-160470 | Jun 1999 | JP |
| 11-232013 | Aug 1999 | JP |
| 2000-162349 | Jun 2000 | JP |
| 3062531 | Jul 2000 | JP |
| 2001-144884 | May 2001 | JP |
| 2001-147282 | May 2001 | JP |
| 2001-273064 | Oct 2001 | JP |
| 2001-313886 | Nov 2001 | JP |
| 2001-318852 | Nov 2001 | JP |
| 2002-73486 | Mar 2002 | JP |
| 2002-507718 | Mar 2002 | JP |
| 2002-251238 | Sep 2002 | JP |
| 2002-259046 | Sep 2002 | JP |
| 2002-271451 | Sep 2002 | JP |
| 2003-9404 | Jan 2003 | JP |
| 2003-196593 | Jul 2003 | JP |
| 2003-233616 | Aug 2003 | JP |
| 2003-296246 | Oct 2003 | JP |
| 2004-28918 | Jan 2004 | JP |
| 2004-184396 | Jul 2004 | JP |
| 2004-251719 | Sep 2004 | JP |
| 2005-016962 | Jan 2005 | JP |
| 2005-521890 | Jul 2005 | JP |
| 2005-339017 | Dec 2005 | JP |
| 2006-101505 | Apr 2006 | JP |
| 2006-287949 | Oct 2006 | JP |
| 2006-293340 | Oct 2006 | JP |
| 2007-150831 | Jun 2007 | JP |
| 2008-175800 | Jul 2008 | JP |
| 2009-147889 | Jul 2009 | JP |
| 2009-293960 | Dec 2009 | JP |
| 2010-124181 | Jun 2010 | JP |
| 2010-257051 | Nov 2010 | JP |
| 3168099 | Jun 2011 | JP |
| 2011-159172 | Aug 2011 | JP |
| 2011-166679 | Aug 2011 | JP |
| 2011-203707 | Oct 2011 | JP |
| 2011-217000 | Oct 2011 | JP |
| 2012-32306 | Feb 2012 | JP |
| 2012-53642 | Mar 2012 | JP |
| 2012-505478 | Mar 2012 | JP |
| 2012-109778 | Jun 2012 | JP |
| 2012-147432 | Aug 2012 | JP |
| 2012-517630 | Aug 2012 | JP |
| 2012-189422 | Oct 2012 | JP |
| 2012-203537 | Oct 2012 | JP |
| 2012-203832 | Oct 2012 | JP |
| 2012-531607 | Dec 2012 | JP |
| 2013-3671 | Jan 2013 | JP |
| 2013-011931 | Jan 2013 | JP |
| 2013-29925 | Feb 2013 | JP |
| 2013-92989 | May 2013 | JP |
| 2013-146557 | Aug 2013 | JP |
| 2013-232230 | Nov 2013 | JP |
| 2014-35766 | Feb 2014 | JP |
| 2014-123197 | Jul 2014 | JP |
| 2014-143575 | Aug 2014 | JP |
| 2014-519126 | Aug 2014 | JP |
| 2014-216868 | Nov 2014 | JP |
| 5630676 | Nov 2014 | JP |
| 2015-210587 | Nov 2015 | JP |
| 2016-13151 | Jan 2016 | JP |
| 2016-020931 | Feb 2016 | JP |
| 2016-085364 | May 2016 | JP |
| 2016-120890 | Jul 2016 | JP |
| 2017-527026 | Sep 2017 | JP |
| 2017-531225 | Oct 2017 | JP |
| 2017-531230 | Oct 2017 | JP |
| 2018-514838 | Jun 2018 | JP |
| 2018-113544 | Jul 2018 | JP |
| 2018-116067 | Jul 2018 | JP |
| 2020-169845 | Oct 2020 | JP |
| 10-2004-0107472 | Dec 2004 | KR |
| 10-2004-0107489 | Dec 2004 | KR |
| 20-0425314 | Sep 2006 | KR |
| 10-2007-0025292 | Mar 2007 | KR |
| 10-2008-0058246 | Jun 2008 | KR |
| 10-0864578 | Oct 2008 | KR |
| 10-2009-0112132 | Oct 2009 | KR |
| 10-2010-0025846 | Mar 2010 | KR |
| 10-2010-0025853 | Mar 2010 | KR |
| 10-2011-0093729 | Aug 2011 | KR |
| 10-2012-0132134 | Dec 2012 | KR |
| 10-2013-0109466 | Oct 2013 | KR |
| 10-2014-0025552 | Mar 2014 | KR |
| 10-2014-0064687 | May 2014 | KR |
| 10-2014-0074824 | Jun 2014 | KR |
| 10-2014-0120470 | Oct 2014 | KR |
| 10-2015-0008996 | Jan 2015 | KR |
| 10-2015-0038711 | Apr 2015 | KR |
| 10-2015-0057307 | May 2015 | KR |
| 10-2015-0081140 | Jul 2015 | KR |
| 10-2015-0093090 | Aug 2015 | KR |
| 10-2016-0026314 | Mar 2016 | KR |
| 10-2016-0030832 | Mar 2016 | KR |
| 10-2016-0066813 | Jun 2016 | KR |
| 10-2016-0076957 | Jul 2016 | KR |
| 10-2017-0032471 | Mar 2017 | KR |
| 10-2017-0076452 | Jul 2017 | KR |
| 10-2017-0081391 | Jul 2017 | KR |
| 10-2017-0082698 | Jul 2017 | KR |
| 10-2018-0011581 | Feb 2018 | KR |
| 10-2018-0078355 | Jul 2018 | KR |
| 10-1875907 | Jul 2018 | KR |
| 10-2019-0020850 | Mar 2019 | KR |
| 10-2019-0035800 | Apr 2019 | KR |
| 10-2019-0071285 | Jun 2019 | KR |
| 10-2019-0114034 | Oct 2019 | KR |
| 2269812 | Feb 2006 | RU |
| 498240 | Aug 2002 | TW |
| 546942 | Aug 2003 | TW |
| 200512616 | Apr 2005 | TW |
| 200850058 | Dec 2008 | TW |
| 200915698 | Apr 2009 | TW |
| 1348803 | Sep 2011 | TW |
| 201232486 | Aug 2012 | TW |
| 201419115 | May 2014 | TW |
| 9840795 | Sep 1998 | WO |
| 0171433 | Sep 2001 | WO |
| 02054157 | Jul 2002 | WO |
| 2003048872 | Jun 2003 | WO |
| 2003085460 | Oct 2003 | WO |
| 2006012343 | Feb 2006 | WO |
| 2006112641 | Oct 2006 | WO |
| 2006131780 | Dec 2006 | WO |
| 2007018881 | Feb 2007 | WO |
| 2007043222 | Apr 2007 | WO |
| 2007124364 | Nov 2007 | WO |
| 2008083360 | Jul 2008 | WO |
| 2008085402 | Jul 2008 | WO |
| 2008114491 | Sep 2008 | WO |
| 2009053775 | Apr 2009 | WO |
| 2009146857 | Dec 2009 | WO |
| 2010017627 | Feb 2010 | WO |
| 2011000893 | Jan 2011 | WO |
| 2011062871 | May 2011 | WO |
| 2011099819 | Aug 2011 | WO |
| 2011145256 | Nov 2011 | WO |
| 2012021507 | Feb 2012 | WO |
| 2012161434 | Nov 2012 | WO |
| 2012170446 | Dec 2012 | WO |
| 2013051048 | Apr 2013 | WO |
| 2013093558 | Jun 2013 | WO |
| 2013136548 | Sep 2013 | WO |
| 2013169842 | Nov 2013 | WO |
| 2013169846 | Nov 2013 | WO |
| 2013169849 | Nov 2013 | WO |
| 2013169875 | Nov 2013 | WO |
| 2013169882 | Nov 2013 | WO |
| 2014024366 | Feb 2014 | WO |
| 2014078114 | May 2014 | WO |
| 2014081181 | May 2014 | WO |
| 2014105274 | Jul 2014 | WO |
| 2014105278 | Jul 2014 | WO |
| 2014189197 | Nov 2014 | WO |
| 2014200730 | Dec 2014 | WO |
| 2015023419 | Feb 2015 | WO |
| 2015029313 | Mar 2015 | WO |
| 2015034960 | Mar 2015 | WO |
| 2015034965 | Mar 2015 | WO |
| 2015065402 | May 2015 | WO |
| 2015163536 | Oct 2015 | WO |
| 2016022203 | Feb 2016 | WO |
| 2016022204 | Feb 2016 | WO |
| 2016022205 | Feb 2016 | WO |
| 2016022496 | Feb 2016 | WO |
| 2016025395 | Feb 2016 | WO |
| 2016032076 | Mar 2016 | WO |
| 2016036427 | Mar 2016 | WO |
| 2016036472 | Mar 2016 | WO |
| 2016036522 | Mar 2016 | WO |
| 2016039587 | Mar 2016 | WO |
| 2016057062 | Apr 2016 | WO |
| 2016099097 | Jun 2016 | WO |
| 2016144385 | Sep 2016 | WO |
| 2016144563 | Sep 2016 | WO |
| 2016144977 | Sep 2016 | WO |
| 2017000522 | Jan 2017 | WO |
| 2017027526 | Feb 2017 | WO |
| 2017062621 | Apr 2017 | WO |
| 2017213777 | Dec 2017 | WO |
| 2017213899 | Dec 2017 | WO |
| 2017213937 | Dec 2017 | WO |
| 2018048700 | Mar 2018 | WO |
| 2018057271 | Mar 2018 | WO |
| 2018213451 | Nov 2018 | WO |
| 2019200350 | Oct 2019 | WO |
| 2019217086 | Nov 2019 | WO |
| 2019217249 | Nov 2019 | WO |
| 2020117189 | Jun 2020 | WO |
| 2020236148 | Nov 2020 | WO |
| 2021050190 | Mar 2021 | WO |
| Entry |
|---|
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/591,184, mailed on Feb. 27, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/676,034, mailed on Feb. 27, 2023, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/935,002, mailed on Mar. 2, 2023, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/556, 165, mailed on Feb. 21, 2023, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/591,184, mailed on Feb. 22, 2023, 5 pages. |
| Office Action received for Japanese Patent Application No. 2020-137007, mailed on Feb. 10, 2023, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 15/405,122, mailed on Jan. 11, 2023, 16 pages. |
| Office Action received for Chinese Patent Application No. 201910924197.0, mailed on Nov. 30, 2022, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202110783860.7, mailed on Nov. 15, 2022, 8 pages (2 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-0123857, mailed on Dec. 16, 2022, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Advisory Action received for U.S. Appl. No. 17/031,765, mailed on Dec. 12, 2022, 7 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/389,722, mailed on Nov. 4, 2022, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,671, mailed on Dec. 9, 2022, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,765, mailed on Nov. 16, 2022, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/556,165, mailed on Oct. 28, 2022, 4 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 17810723.1, mailed on Nov. 11, 2022, 11 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/341,839, mailed on Oct. 26, 2022, 2 pages. |
| Decision to Refuse received for Japanese Patent Application No. 2020-159824, mailed on Sep. 30, 2022, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 17/031,671, mailed on Nov. 15, 2022, 27 pages. |
| Intention to Grant received for European Patent Application No. 21177569.7, mailed on Oct. 27, 2022, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/031212, mailed on Nov. 24, 2022, 16 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/031669, mailed on Nov. 24, 2022, 12 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/026371, mailed on Oct. 12, 2022, 16 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/029279, mailed on Nov. 9, 2022, 16 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2022/029279, mailed on Sep. 15, 2022, 9 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 17810723.1, mailed on Dec. 9, 2022, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/158,936, mailed on Nov. 30, 2022, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/713,016, mailed on Oct. 27, 2022, 25 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021245228, mailed on Oct. 4, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022220279, mailed on Sep. 27, 2022, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202111457936.3, mailed on Nov. 7, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2020-124605, mailed on Dec. 5, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2022-512865, mailed on Oct. 3, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2020-0123852, mailed on Nov. 28, 2022, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2020-0123887, mailed on Nov. 28, 2022, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7036016, mailed on Sep. 28, 2022, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/418,786, mailed on Nov. 22, 2022, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/317,042, mailed on Nov. 9, 2022, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/341,839, mailed on Dec. 2, 2022, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/341,839, mailed on Oct. 5, 2022, 5 pages. |
| Office Action received for Australian Patent Application No. 2021250863, mailed on Oct. 6, 2022, 6 pages. |
| Office Action received for European Patent Application No. 19724997.2, mailed on Oct. 27, 2022, 5 pages. |
| Office Action received for European Patent Application No. 20730136.7, mailed on Oct. 6, 2022, 11 pages. |
| Office Action received for European Patent Application No. 21169911.1, mailed on Dec. 1, 2022, 4 pages. |
| Office Action received for Japanese Patent Application No. 2021-023661, mailed on Oct. 3, 2022, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2022-7019205, mailed on Sep. 21, 2022, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Result of Consultation received for European Patent Application No. 17810723.1, mailed on Nov. 30, 2022, 3 pages. |
| Hoffman, Chris, “5+ Cool Uses for Android's Daydream Mode”, retrieved from—https://www.howtogeek.com/170990/5-cool-uses-for-androids-daydream-mode, Jul. 12, 2017, 8 pages. |
| Spears, Ann, “dimming screen before/instead of screensaver?”, retrieved from—https://discussions.apple.com/thread/339700, Jan. 28, 2006, 1 page. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/738,940, mailed on Mar. 7, 2023, 4 pages. |
| Extended European Search Report received for European Patent Application No. 22188724.3, mailed on Mar. 2, 2023, 14 pages. |
| Intention to Grant received for European Patent Application No. 21169911.1, mailed on Mar. 6, 2023, 9 pages. |
| Lee et al., “PASS: Reducing Redundant Notifications between a Smartphone and a Smartwatch for Energy Saving”, IEEE Transactions on Mobile Computing, vol. 19, Jul. 23, 2019, pp. 2656-2669. |
| Lyons Kent, “Smartwatch Innovation: Exploring a Watch-First Model”, Pervasive Computing, Jan. 2016, pp. 10-13. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-0123857, mailed on Feb. 21, 2023, 6 pages (1 page of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 17/515,143, mailed on Mar. 13, 2023, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/941,962, mailed on Mar. 10, 2023, 11 pages. |
| Pre-Appeal Review Report received for Japanese Patent Application No. 2020-159823, mailed on Jan. 12, 2023, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Advisory Action received for U.S. Appl. No. 16/792,096, mailed on Nov. 18, 2021, 4 pages. |
| “Adyclock—Night Alarm Clock”, App for android, Google play store page: https://web.archive.org/web/20130924223153/https://play.google.com/store/apps/details?id=com.adyclock&hl=en, Sep. 24, 2013, 2 pages. |
| 2Raz Tech&Moto, “Sony Smartwatch 2 Update—New Feartures and Watchface Creator !!! New !!! ”, Online available at: https://www.youtube.com/watch?v=k3jjBv7QZSk, May 8, 2014, 3 pages. |
| Advisory Action received for U.S. Appl. No. 14/815,898, mailed on Aug. 30, 2016, 3 pages. |
| Advisory Action received for U.S. Appl. No. 14/841,606, mailed on Feb. 28, 2019, 3 pages. |
| Advisory Action received for U.S. Appl. No. 14/846,511, mailed on Oct. 22, 2019, 5 pages. |
| Advisory Action received for U.S. Appl. No. 14/846,511, mailed on Sep. 19, 2018, 8 pages. |
| Advisory Action received for U.S. Appl. No. 15/421,865, mailed on Apr. 16, 2020, 7 pages. |
| Advisory Action received for U.S. Appl. No. 15/554,204, mailed on Mar. 12, 2020, 3 pages. |
| Advisory Action received for U.S. Appl. No. 16/389,722, mailed on Mar. 9, 2021, 5 pages. |
| Advisory Action received for U.S. Appl. No. 16/582,020, mailed on Aug. 3, 2020, 4 pages. |
| Airshow, “Airshow App for Mobile Devices”, 2012, 4 pages. |
| Andro Dollar, “Huawei Watch Gt Always on Mode Update is Finally Here! ????”, Online Available at: https://www.youtube.com/watch?v=AJw_FIAf7v4, Jun. 6, 2019, 4 pages. |
| Android Central, “Beweather Weather App for Android”, Available online at: <https://www.youtube.com/watch?v=G2EY2K-XkSI>, Sep. 1, 2011, 1 page. |
| Android Central, “Changing the Watchface on Your Android Wear Device”, Retrieved from: https://www.youtube.com/watch?v=YYwFe2K_qil, Jul. 2, 2014, 4 pages. |
| Android Tips, “Create a Minimal Lock Screen with Widgetlocker”, Online Available at: http://appstap192.blogspot.com/2012/01/create-minimal-lock-screen-with.html, Jan. 18, 2012, 6 pages. |
| Androidika, “Butterfly 3d Live Wallpaper 1.0 Apk”, Available at: <http://net-suckga-ilauncher2.apk-dl.com/butterfly-3d-live-wallpaper>, Feb. 26, 2013, 7 pages. |
| Aod Too Dim. I've Answered My Own Question to Help Others, Online Available: https://forums.androidcentral.com/samsung-galaxy-s9-s9-plus/874444-aod-too-dim-ive-answered-my-own-question-help-others.html, Mar. 11, 2018, 3 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 14/846,511, mailed on Apr. 20, 2020, 4 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 15/713,544, mailed on Apr. 6, 2020, 7 pages. |
| Initiated Interview Summary received for U.S. Appl. No. 15/713,544, mailed on Oct. 24, 2019, 4 pages. |
| Initiated Interview Summary received for U.S. Appl. No. 16/389,722, mailed on Jul. 7, 2020, 5 pages. |
| Initiated Interview Summary received for U.S. Appl. No. 16/582,020, mailed on Jul. 9, 2021, 4 pages. |
| Initiated Interview Summary received for U.S. Appl. No. 16/582,020, mailed on Jul. 14, 2020, 5 pages. |
| Initiated Interview Summary received for U.S. Appl. No. 16/582,020, mailed on Mar. 25, 2020, 5 pages. |
| Initiated Interview Summary received for U.S. Appl. No. 16/584,445, mailed on Mar. 17, 2020, 5 pages. |
| Interview received for U.S. Appl. No. 16/585,399, mailed on Mar. 25, 2020, 3 pages. |
| Initiated Interview received for U.S. Appl. No. 17/031,671, mailed on Aug. 2, 2021, 5 pages. |
| Interview received for U.S. Appl. No. 17/031,671, mailed on Nov. 8, 2021, 5 pages. |
| Interview received for U.S. Appl. No. 15/405,122, mailed on Dec. 22, 2020, 5 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 15/405,122, mailed on Jul. 7, 2021, 4 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 15/405,122, mailed on May 21, 2020, 5 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 15/421,865, mailed on Dec. 15, 2020, 6 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 15/421,865, mailed on Feb. 3, 2020, 5 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 15/421,865, mailed on Jun. 30, 2021, 6 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 15/554,204, mailed on Jan. 31, 2020, 3 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 15/554,204, mailed on Oct. 11, 2019, 5 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 15/798,235, mailed on Feb. 3, 2020, 3 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 16/389,722, mailed on Feb. 11, 2021, 4 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 16/389,722, mailed on Sep. 7, 2021, 4 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 16/401,934, mailed on Feb. 23, 2021, 8 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 16/418,786, mailed on Mar. 30, 2021, 4 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 16/584,281, mailed on Mar. 9, 2020, 5 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 16/584,281, mailed on Sep. 14, 2020, 6 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 16/585,714, mailed on Jul. 20, 2020, 5 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 16/585,721, mailed on Aug. 31, 2020, 5 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 16/585,721, mailed on Mar. 13, 2020, 5 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 16/659,507, mailed on Nov. 17, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/792,096, mailed on May 17, 2021, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/792,096, mailed on Oct. 18, 2021, 6 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 16/861,651, mailed on Mar. 25, 2021, 6 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 16/861,651, mailed on Sep. 3, 2021, 5 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 16/935,002, mailed on Sep. 21, 2021, 4 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 16/943,737, mailed on Sep. 7, 2021, 4 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 16/997,588, mailed on Jan. 29, 2021, 3 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 16/997,588, mailed on May 12, 2021, 2 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 17/031,654, mailed on Feb. 1, 2021, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,765, mailed on Dec. 15, 2021, 4 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 17/031,765, mailed on Sep. 22, 2021, 5 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 17/041,350, mailed on Aug. 18, 2021, 2 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 17/068,386, mailed on Sep. 21, 2021, 2 pages. |
| Avdonin, Nikita, “Astroviewer 3d”, Available at: https: jjwww.youtube.comjwatch?v=zY0tslx3JHY/, Nov. 5, 2013, 2 pages. |
| Baar, Marius, “Fitbit Ace—Unboxing, Setup and 24-hour Test”, YouTube [online] [video], Retrieved from: https://youtu.be/ekvkfqOyrls. See especially 4:44., Oct. 24, 2018, 3 pages. |
| Barbosa, Jonathan, “Weather Clock 2.1 for Android”, APKPure, Online Available at: https://apkpure.com/weather-clock/com.urbandroid.wclock, Oct. 15, 2015, 3 pages. |
| Big Phil TV, “Gear S3 Watch Faces with Great Always on Display (a O D)”, Available online at: https://www.youtube.com/watch?v=2cxMnrMiGU8, Apr. 5, 2017, 3 pages. |
| Bogdanov, Alexei, “Skmei 1016”, XP054977588, Available online at: URL: https://www.youtube.com/watch?v=E4q4Fug05Fw, Jun. 21, 2014, 2 pages (Official Copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Bond, John-Michael, “The 4 Best Free Flashlight Apps for Android and IOS”, Online Available at: https://www.dailydot.com/debug/best-free-flashlight-apps/, 8 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 15730925.3, mailed on Feb. 18, 2020, 7 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 172061772, mailed on Nov. 21, 2019, 5 pages. |
| Brightness on Lock Screen, Online Available at: https://www.reddit.com/r/galaxys10/comments/b4d5fb/brightness_on_lock_screen/, 2019, 1 page. |
| Cancellation of Oral Proceedings received for European Patent Application No. 17206177.2, mailed on Dec. 4, 2019, 2 pages. |
| Castellini, Rick, “Google Earth”, Retrieved from: https://www.youtube.com/watch?v=bgjMSBXsFZQ, Feb. 12, 2013, 3 pages. |
| Cengic, Suad, “Samsung Gear S3—Display Always On! Cool!”, Available online at: https://www.youtube.com/watch?v=ceeDinbPwOY, Mar. 10, 2017, 3 pages. |
| Certificate of Examination received for Australian Patent Application No. 2018101947, mailed on Feb. 18, 2019, 2 pages. |
| Certificate of Examination received for Australian Patent Application No. 2020102158, mailed on Jun. 8, 2021, 2 pages. |
| Clark, Josh, “Designing Great Iphone Apps”, O'Reilly Japan Co., O'Reilly Tim, vol. 1, May 24, 2012, 5 pages (Official Copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/815,879, mailed on Jul. 13, 2017, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/815,879, mailed on Jul. 28, 2017, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/815,879, mailed on Sep. 21, 2017, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/183,663, mailed on Feb. 25, 2019, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/183,663, mailed on Mar. 27, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/355,956, mailed on Jan. 3, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/554,204, mailed on Aug. 19, 2020, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/791,829, mailed on Jan. 16, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/798,257, mailed on Aug. 26, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/798,257, mailed on Jul. 9, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/798,257, mailed on Jun. 12, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/582,020, mailed on Aug. 11, 2021, 2 pages. |
| Cyr, Jim, “Apple Watch-Customize Modular Watch Face”, Available online at: https://www.youtube.com/watch?v=02W93HbKIK8, May 13, 2015, 2 pages. |
| Dan, “Get This Look: ‘minimal’ Zooper Widget”, Online Available at: https://www.androidguys.com/featured/customize/get-look-minimal-zooper-widget/, Mar. 7, 2014, 2 pages. |
| Decision on Acceptance received for Australian Patent Application No. 2015298710, mailed on Jul. 19, 2019, 18 pages. |
| Decision on Acceptance received for Australian Patent Application No. 2018201089, mailed on Apr. 20, 2021, 28 pages. |
| Decision on Appeal received for U.S. Appl. No. 14/815,890, mailed on Nov. 24, 2020, 13 pages. |
| Decision on Appeal received for U.S. Appl. No. 15/713,544, mailed on Dec. 14, 2021, 10 pages. |
| Decision on Opposition received for Australian Patent Application No. 2015298710, mailed on Aug. 9, 2019, 4 pages. |
| Decision on Opposition received for Australian Patent Application No. 2015298710, mailed on Aug. 20, 2018, 20 pages. |
| Decision to Grant received for Danish Patent Application No. PA201770387, mailed on Aug. 30, 2018, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201770397, mailed on Feb. 6, 2018, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201770791, mailed on Jul. 7, 2020, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201970596, mailed on Feb. 26, 2021, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201970597, mailed on Aug. 19, 2021, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA202070609, mailed on May 3, 2021, 2 pages. |
| Decision to Grant received for European Patent Application No. 15730925.3, mailed on Dec. 9, 2021, 2 pages. |
| Decision to Grant received for European Patent Application No. 15747595.5, mailed on Jul. 16, 2020, 2 pages. |
| Decision to Grant received for European Patent Application No. 17206177.2, mailed on Aug. 6, 2020, 2 pages. |
| Decision to Grant received for European Patent Application No. 18172554.0, mailed on Jul. 30, 2020, 2 pages. |
| Decision to Refuse received for European Patent Application No. 15730924.6, mailed on Mar. 15, 2019, 12 pages. |
| Deluxe Moon-guide, Available online at: https://web.archive.org/web/20130520161057/http://www.lifewaresolutions.com/deluxe_moon_guide_ip.html, May 20, 2013, 5 pages. |
| Digital Alarm Clock App for Android, Goggle play store digital alarm clock description page, Mar. 25, 2015, 3 pages. |
| Disrapptive, “Flashlight for Android Wear”, Available online at: https://www.youtube.com/watch?v=HVNxxUI57BM, 6 pages. |
| Disrapptive, “Flashlight for Android Wear”, Online Available at: <https://www.youtube.corn/watch?v=HVNxxUI57BM>, 5 pages. |
| Droid Life, “How To: Use Always-on Apps with Android Wear”, Available online at: https://www.youtube.com/watch?v =_-xYB9EBTaA, Jun. 26, 2015, 3 pages. |
| Ebpman Tech Reviews, “LG G3 Tips: How to Customize the Clock Face”, Available online at: https://www.youtube.com/watch?v=evraMWFb1fY, Jul. 25, 2014, 1 page. |
| Elecont, “Weather Clock—Hourly Forecast Description”, Accurate 10-day weather. Forecast, NOAA radar and satellite, buoy, Elecont LLC Forums, Online Available at: https://www.tapatalk.com/groups/elecontfr/weather-clock-hourly-forecast-description-t427.html, Dec. 1, 2011, 5 pages. |
| European Search Report received for European Patent Application No. 17206177.2, mailed on Apr. 30, 2018, 4 pages. |
| European Search Report received for European Patent Application No. 20172197.4, mailed on Jul. 28, 2020, 4 pages. |
| Evgenyevich, Sergey, “Earth & Moon in Hd Gyro 3d”, Available at: https://www.youtube.com/watch?v=IRwNcaSYrls/, Dec. 1, 2013, 2 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/815,890, mailed on Mar. 20, 2020, 16 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/846,511, mailed on Jun. 14, 2021, 15 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 15/713,544, mailed on Apr. 5, 2021, 15 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 15/713,544, mailed on Apr. 9, 2021, 15 pages. |
| Extended European Search Report received for European Patent Application No. 16762356.0, mailed on Nov. 9, 2018, 10 pages. |
| Extended European Search Report received for European Patent Application No. 16837432.0, mailed on Mar. 11, 2019, 10 pages. |
| Extended European Search Report received for European Patent Application No. 17810723.1, mailed on Nov. 12, 2019, 9 pages. |
| Extended European Search Report received for European Patent Application No. 17853656.1, mailed on Jul. 3, 2019, 9 pages. |
| Extended European Search Report received for European Patent Application No. 18172554.0, mailed on Aug. 3, 2018, 10 pages. |
| Extended European Search Report received for European Patent Application No. 20180900.1, mailed on Sep. 18, 2020, 7 pages. |
| Extended European Search Report received for European Patent Application No. 20185974.1, mailed on Oct. 28, 2020, 7 pages. |
| Extended European Search Report received for European Patent Application No. 21169911.1, mailed on Sep. 20, 2021, 9 pages. |
| Extended European Search Report received for European Patent Application No. 21177569.7, mailed on Sep. 20, 2021, 8 pages. |
| Feist, Jonathan, “Android Customization—How to Create a Custom Clock Widget Using Zooper Widget”, Available Online at: https://www.androidauthority.com/zooper-widget-clock-366476/, May 15, 2014, 10 pages. |
| Feldman, Ari, “Excerpts From: Designing Arcade Computer Game Graphics”, Available online at: http://www.phatcode.net/res/269/files/dacgg.pdf, Jan. 1, 2001, 35 pages. |
| Final Office Action received for U.S. Appl. No. 14/815,879, mailed on Mar. 24, 2016, 46 pages. |
| Final Office Action received for U.S. Appl. No. 14/815,890, mailed on Feb. 26, 2018, 20 pages. |
| Final Office Action received for U.S. Appl. No. 14/815,890, mailed on May 14, 2019, 22 pages. |
| Final Office Action received for U.S. Appl. No. 14/815,890, mailed on Nov. 21, 2016, 18 pages. |
| Final Office Action received for U.S. Appl. No. 14/815,898, mailed on Jun. 9, 2016, 19 pages. |
| Final Office Action received for U.S. Appl. No. 14/821,667, mailed on Apr. 26, 2018, 13 pages. |
| Final Office Action received for U.S. Appl. No. 14/841,606, mailed on Sep. 7, 2018, 34 pages. |
| Final Office Action received for U.S. Appl. No. 14/846,511 mailed on May 10, 2018, 21 pages. |
| Final Office Action received for U.S. Appl. No. 14/846,511, mailed on Aug. 11, 2020, 25 pages. |
| Final Office Action received for U.S. Appl. No. 14/846,511, mailed on Jun. 5, 2019, 24 pages. |
| Final Office Action received for U.S. Appl. No. 15/405,122, mailed on Jan. 21, 2020, 36 pages. |
| Final Office Action received for U.S. Appl. No. 15/405,122, mailed on Nov. 5, 2021, 45 pages. |
| Final Office Action received for U.S. Appl. No. 15/421,865, mailed on Dec. 2, 2019, 19 pages. |
| Final Office Action received for U.S. Appl. No. 15/421,865, mailed on Mar. 19, 2021, 20 pages. |
| Final Office Action received for U.S. Appl. No. 15/554,204, mailed on Oct. 31, 2019, 22 pages. |
| Final Office Action received for U.S. Appl. No. 15/713,544, mailed on Jul. 19, 2019, 20 pages. |
| Final Office Action received for U.S. Appl. No. 15/713,544, mailed on May 20, 2020, 14 pages. |
| Final Office Action received for U.S. Appl. No. 15/791,829, mailed on Mar. 7, 2019, 23 pages. |
| Final Office Action received for U.S. Appl. No. 15/798,235, mailed on Oct. 9, 2018, 45 pages. |
| Final Office Action received for U.S. Appl. No. 15/798,235, mailed on Oct. 18, 2019, 25 pages. |
| Final Office Action received for U.S. Appl. No. 15/881,544, mailed on Jan. 29, 2019, 14 pages. |
| Final Office Action received for U.S. Appl. No. 16/389,722, mailed on Dec. 6, 2021, 19 pages. |
| Final Office Action received for U.S. Appl. No. 16/389,722, mailed on Dec. 8, 2020, 18 pages. |
| Final Office Action received for U.S. Appl. No. 16/401,934, mailed on Jun. 14, 2021, 30 pages. |
| Final Office Action received for U.S. Appl. No. 16/418,786, mailed on Jan. 13, 2021, 14 pages. |
| Final Office Action received for U.S. Appl. No. 16/582,020, mailed on Apr. 28, 2020, 31 pages. |
| Final Office Action received for U.S. Appl. No. 16/584,281, mailed on Apr. 15, 2020, 26 pages. |
| Final Office Action received for U.S. Appl. No. 16/585,721, mailed on Apr. 1, 2020, 28 pages. |
| Final Office Action received for U.S. Appl. No. 16/792,096, mailed on Aug. 9, 2021, 17 pages. |
| Final Office Action received for U.S. Appl. No. 16/861,651, mailed on Apr. 20, 2021, 14 pages. |
| Final Office Action received for U.S. Appl. No. 16/997,588, mailed on Mar. 30, 2021, 23 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,671, mailed on Sep. 7, 2021, 27 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,765, mailed on Oct. 29, 2021, 34 pages. |
| Final Office Action received for U.S. Appl. No. 17/041,350, mailed on Sep. 17, 2021, 25 pages. |
| First Action Interview received for U.S. Appl. No. 14/815,890, mailed on Aug. 12, 2016, 3 pages. |
| Fitbit Surge Fitness Watch, Manual version 1.0, May 7, 2015, 48 pages. |
| Fuchphone Extras, “Lg G Watch—Designs | Watch Faces”, Available online at: https://www.youtube.com/watch?v=yqxzqdi_MSE, Jul. 27, 2014, 1 page. |
| Fuchphone Extras, “Samsung Gear Live—Designs | Watch Faces”, Available online at: https://www.youtube.com/watch?v=fFjtVAxyimE, Jul. 26, 2014, 1 page. |
| Fukuda, Kazuhiro, “Xperia Z1 Perfect Manual”, Sotec Co., Ltd., No. 1, Nov. 15, 2013, pp. 217-218. |
| Gazer, “Iphone 4s Super Manual”, Shuwa System Co., Saito Kazukuni, vol. 1, Jun. 6, 2013, 7 pages (Official Copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Geary, David, “Programming Html5 Canvas”, O'Reilly Japan, Inc., No. 1, Jul. 23, 2014, pp. 327-330. |
| Geek, “How to Put the Day of the Week into the Windows Taskbar Clock”, available online at: https://www.howtogeek.com/194103/how-to-put-the-day-of-the-week-into-the-windows-taskbar-clock/, 2014, 3 pages. |
| Google Earth 7.0.1.8244, retrieved from the Internet: http://dl.google.com/dl/earth/client/ge7/release_7_0_1/googleearth-win-bundle-7.0.1.8244.exe, Oct. 29, 2012, 1 page. |
| Google Earth on Android—Androidcentral.com, Available online at:—https://www.youtube.com/watch?v=1WxN1RunrE4, Feb. 22, 2010, 1 page. |
| Gottabemobile, “How to Change Watch Faces on Android Wear”, available online at URL: https://www.youtube.com/watch?v=B8iRGkGq6a8, Jul. 9, 2014, 4 pages. |
| Haidar, Rawand, “How to Use Android Wear Smartwatch as a Flashlight!”, Available online at: <https://howto.highonandroid.com/android-wear-tutorials/how-to-use-android-wear-smartwatch-as-a-flashlight-flashlight-app/>, 6 pages. |
| Hollywoodfrodo, “FREE Flashlight Android App by Asus Best Flashlight App on Google Play”, Online Available at: <https://www.youtube.corn/watch?v=K_kFa7PoVsc>, 3 pages. |
| Huawei Watch FAQS-en_us-V2.8, Available Online at: Online available at: https://maplindownloads.s3-eu-west-1.amazonaws.com/A27WH-9512.pdf, 135 pages. |
| Intention to Grant received for Danish Patent Application No. PA201570496, mailed on Feb. 17, 2016, 6 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770387, mailed on Apr. 4, 2018, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770387, mailed on May 24, 2018, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770397, mailed on Aug. 18, 2017, 7 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770791, mailed on Feb. 19, 2020, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201970596, mailed on Dec. 1, 2020, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201970597, mailed on Apr. 20, 2021, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA202070609, mailed on Jan. 14, 2021, 2 pages. |
| Intentiom to Grant received for European Patent Application No. 15730925.3, mailed on Aug. 16, 2021, 10 pages. |
| Intention to Grant received for European Patent Application No. 15730925.3, mailed on May 28, 2020, 10 pages. |
| Intention to Grant received for European Patent Application No. 15747595.5, mailed on Feb. 17, 2020, 8 pages. |
| Intention to Grant received for European Patent Application No. 17206177.2, mailed on Feb. 24, 2020, 8 pages. |
| Intention to Grant received for European Patent Application No. 18172554.0, mailed on Feb. 17, 2020, 8 pages. |
| Preliminary Report on Patentability received for PCT Application No. PCT/US2016/037686, mailed on Mar. 1, 2018, 12 pages. |
| Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/034604, mailed on Feb. 16, 2017, 21 pages. |
| Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/034606, mailed on Feb. 16, 2017, 11 pages. |
| Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/034607, mailed on Feb. 16, 2017, 18 pages. |
| Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/044473, mailed on Mar. 2, 2017, 20 pages. |
| Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/044485, mailed on Mar. 2, 2017, 20 pages. |
| Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/053353, mailed on Sep. 21, 2017, 15 pages. |
| Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/054223, mailed on Dec. 14, 2017, 18 pages. |
| Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/021403, mailed on Sep. 21, 2017, 21 pages. |
| Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/035090, mailed on Dec. 14, 2017, 14 pages. |
| Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2017/034834, mailed on Dec. 20, 2018, 9 pages. |
| Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2017/049793, mailed on Apr. 4, 2019, 15 pages. |
| Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2018/032164, mailed on Nov. 21, 2019, 11 pages. |
| Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2018/032385, mailed on Nov. 28, 2019, 10 pages. |
| Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/030770, mailed on Nov. 19, 2020, 14 pages. |
| Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/030079, mailed on Nov. 18, 2021, 12 pages. |
| Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/031536, mailed on Nov. 18, 2021, 11 pages. |
| Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/031575, mailed on Nov. 18, 2021, 9 pages. |
| Search Report and Written Opinion received for PCT Application No. PCT/US2015/034604, mailed on Nov. 9, 2015, 30 pages. |
| Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/034606, mailed on Dec. 2, 2015, 17 pages. |
| Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/034607, mailed on Dec. 1, 2015, 23 pages. |
| Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/044473, mailed on Feb. 12, 2016, 24 pages. |
| Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/044485, mailed on Feb. 9, 2016, 27 pages. |
| Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/053353, mailed on May 9, 2016, 21 pages. |
| Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/054223, mailed on Jul. 6, 2016, 25 pages. |
| Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/021403, mailed on May 12, 2016, 23 pages. |
| Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/035090, mailed on Oct. 4, 2016, 17 pages. |
| Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/037686, mailed on Sep. 9, 2016, 19 pages. |
| Search Report and Written Opinion received for PCT Patent Application No. PCT/US2017/034834, mailed on Aug. 23, 2017, 10 pages. |
| Search Report and Written Opinion received for PCT Patent Application No. PCT/US2017/049793, mailed on Dec. 27, 2017, 19 pages. |
| Search Report and Written Opinion received for PCT Patent Application No. PCT/US2018/032164, mailed on Oct. 18, 2018, 16 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2018/032385 mailed on Aug. 3, 2018, 14 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/030770, mailed on Oct. 31, 2019, 23 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/030079, mailed on Sep. 4, 2020, 18 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/031536, mailed on Sep. 23, 2020, 16 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/031575, mailed on Aug. 20, 2020, 14 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/045814, mailed on Jan. 20, 2021, 16 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/031212, mailed on Sep. 21, 2021, 21 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/031669, mailed on Oct. 13, 2021, 17 pages. |
| Internet Blog Post, “[pc] Pre-customization of Black Desert's Characters”, Online Available at:—<https://blog.naver.com/hsh6051/220209813968>, Dec. 14, 2014, 41 pages (21 pages of English Translation and 20 pages of Official Copy). |
| Inventerium, “Tropical Fish 14”, Available online at: https://www.turbosquid.com/3d-models/tropical-fish-3d-model/388510, Feb. 4, 2008, 2 pages. |
| Invitation to Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2015/034604 mailed on Sep. 4, 2015, 6 pages. |
| Invitation to Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2015/034606 mailed on Sep. 9, 2015, 6 pages. |
| Invitation to Pay Additional Fee received for European Patent Application No. 15747595.5, mailed on Feb. 9, 2018, 6 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/034607, mailed on Sep. 30, 2015, 4 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/044473, mailed on Nov. 3, 2015, 5 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/044485, mailed on Nov. 3, 2015, 7 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/053353, mailed on Jan. 21, 2016, 7 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/054223, mailed on Mar. 9, 2016, 9 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2016/035090, mailed on Jul. 15, 2016, 2 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2017/049793, mailed on Nov. 3, 2017, 2 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2018/032164, mailed on Aug. 21, 2018, 10 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2019/030770, mailed on Jul. 26, 2019, 12 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/030079, mailed on Jul. 14, 2020, 12 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/031536, mailed on Jul. 31, 2020, 9 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/045814, mailed on Nov. 18, 2020, 11 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2021/031212, mailed on Jul. 28, 2021, 19 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2021/031669, mailed on Aug. 19, 2021, 9 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 20761084.1, mailed on Dec. 7, 2021, 3 pages. |
| ISO 9241-13:1998, “Ergonomic Requirements for Office Work with Visual Display Terminals (vdts)”, Part 13: User guidance, International Standard ISO, Zuerich, CH, vol. 9241-13, Jul. 15, 1998, 40 pages. |
| Jean, “Our Pact Parental Control Review”, Available online at: https://www.bewebsmart.com/parental-controls/our-pact-parental-control-review/, Jun. 25, 2016, 25 pages. |
| Kenney, Briley, “How to Customize a Smartwatch and Other Personalization Questions”, Available online at: https://smartwatches.org/learn/customize-smartwatch/, Jan. 23, 2014, 3 pages. |
| Kidizoom Smartwatch, Available online at: https://www.vtechnl.com/media/downloads/Kidizoom-Smart-Watch.pdf, Jun. 24, 2014, 23 pages. |
| Kubo, et al., “Watch Commander: A Gesture-based Invocation System for Rectangular Smartwatches using B2B-Swipe”, UIST'16 Adjunct, Available online at: https://dl.acm.org/doi/pdf/10.1145/2984751.2985697, pp. 37-39. |
| Living Earth, Available at: http;//www.livingcarthapp.com/, 2014, 6 pages. |
| Looking for a Launcher that Changes the Default Homescreen or Widgets Based on Wifi, Location, or Other Context., 2015, 2 pages. |
| Minutes of Oral Proceedings received for European Patent Application No. 15730924.6, mailed on Mar. 13, 2019, 4 pages. |
| Minutes of Oral Proceedings received for European Patent Application No. 15730925.3, mailed on May 26, 2020, 11 pages. |
| Minutes of Oral Proceedings received for European Patent Application No. 16762356.0, mailed on Dec. 17, 2021, 5 pages. |
| Ms Excel 2013, Jan. 29, 2013, 2 pages. |
| My Mate Vince, “Setting Up the Fitbit Alta Hr Activity Tracker on Apple los”, Online available at: https://youtu.be/FdwRF4IfvFc, Jun. 18, 2017, 3 pages. |
| Nerdtalk, “The Best Android Clock Widgets”, Available at: https://www.youtube.com/watch?v=E1bAprWByfU, Apr. 25, 2011, 1 page. |
| New, but Unsigned—Easy Stopwatch for Symbian, XP55393563, Available online at: http://www.allaboutsymbian.com/flow/item/19490_New_but_unsigned-Easy_StopWatc.php, Mar. 15, 2014, 15 pages. |
| Night Display (Alarm Clock) App, Google Play Store Night Display (Alarm Clock) Description page, available at: https://web.archive.org/web/20141007124222/https://play.google.com/store/apps/details?id =com.srk.nighttimedisplay&hl=en, Oct. 7, 2014, pp. 1-3. |
| Non-Final Office Action received for U.S. Appl. No. 14/815,879, mailed on Dec. 15, 2016, 33 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/815,879, mailed on Nov. 6, 2015, 35 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/815,890, mailed on Dec. 18, 2018, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/815,890, mailed on Jun. 6, 2017, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/815,890, mailed on Oct. 19, 2015, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/815,898, mailed on Dec. 1, 2015, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/815,907, mailed on Jan. 12, 2016, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/815,909, mailed on Nov. 27, 2015, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/821,667, mailed on Feb. 4, 2019, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/821,667, mailed on Jul. 14, 2017, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,889, mailed on Mar. 7, 2017, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/841,606, mailed on Dec. 7, 2017, 30 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/841,606, mailed on May 8, 2019, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/846,511 mailed on Jan. 7, 2020, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/846,511 mailed on Oct. 27, 2017, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/846,511, mailed on Nov. 30, 2018, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/183,663, mailed on Jul. 9, 2018, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/355,956, mailed on May 31, 2019, 32 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/405,122, mailed on Apr. 2, 2021, 35 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/405,122, mailed on May 31, 2019, 43 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/405,122, mailed on Sep. 24, 2020, 30 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/421,865, mailed on Mar. 21, 2019, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/421,865, mailed on Oct. 7, 2020, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/554,204, mailed on Apr. 17, 2019, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/713,544, mailed on Dec. 11, 2019, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/713,544, mailed on Jan. 24, 2019, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/791,829, mailed on Nov. 8, 2018, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/798,235, mailed on Apr. 24, 2019, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/798,235, mailed on Mar. 14, 2018, 58 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/881,544, mailed on Jun. 7, 2018, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/389,722, mailed on Apr. 3, 2020, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/389,722, mailed on Jun. 3, 2021, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/401,934, mailed on Dec. 11, 2020, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/418,786, mailed on Apr. 24, 2020, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/418,786, mailed on Oct. 4, 2021, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/582,020, mailed on Apr. 5, 2021, 29 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/582,020, mailed on Jan. 13, 2020, 39 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/584,281, mailed on Dec. 10, 2019, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/584,445, mailed on Dec. 26, 2019, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/585,399, mailed on Jan. 23, 2020, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/585,714, mailed on Apr. 16, 2020, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/585,721, mailed on Dec. 27, 2019, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/659,507, mailed on Oct. 7, 2020, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/792,096, mailed on Feb. 12, 2021, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/861,651, mailed on Nov. 27, 2020, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/861,651, mailed on Sep. 30, 2021, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/935,002, mailed on Jun. 25, 2021, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/943,737, mailed on Jun. 25, 2021, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/997,588, mailed on Dec. 14, 2020, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,654, mailed on Nov. 19, 2020, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,671, mailed on Apr. 30, 2021, 27 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,765, mailed on Jun. 28, 2021, 32 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/041,350, mailed on Jun. 10, 2021, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/068,386, mailed on Jul. 15, 2021, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/068,386, mailed on Oct. 28, 2021, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/317,042, mailed on Nov. 10, 2021, 13 pages. |
| Non-Final received for U.S. Appl. No. 17/078,896, mailed on Dec. 24, 2021, 17 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2015298710, mailed on Oct. 8, 2019, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2016229847, mailed on Sep. 12, 2018, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017277813, mailed on Jun. 16, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017330211, mailed on May 11, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018201089, mailed May 28, 2021, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018279037, mailed May 13, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019208225, mailed Jan. 21, 2021, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019267413, mailed Nov. 23, 2021, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020204506, mailed Apr. 8, 2021, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020239670, mailed Jul. 2, 2021, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020309093, mailed on Jul. 8, 2021, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021202834, mailed on Jul. 15, 2021, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021202836, mailed on Jun. 25, 2021, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201510479088.4, mailed on Jan. 21, 2021, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201510481525.6, mailed on May 27, 2019, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201510483268.X, mailed on Nov. 6,2019, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201510483305.7, mailed on Jan. 8, 2019, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201510484514.3, mailed on Jun. 6, 2019, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201520594249.X, mailed on Jul. 12, 2016, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201680013193.1, mailed on May 7, 2021, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201680047983.1, mailed on Apr. 28, 2021, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201780033973.7, mailed on Jul. 7, 2021, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201810037665.8, mailed on Jul. 9, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201910906898.1, mailed on Oct. 28, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Danish Patent Application No. PA201570495, mailed on Feb. 22, 2017, 1 page. |
| Notice of Allowance received for Danish Patent Application No. PA201570496, mailed on Apr. 18, 2016, 2 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2017-505450, mailed on Mar. 9, 2018, 10 pages (7 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2017-505842, mailed on Mar. 16, 2020, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2017-505847, mailed on May 20, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2017-545918, mailed on Jul. 22, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2018-074971, mailed on Apr. 23, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2018-537840, mailed on Mar. 19, 2020, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2019-096219, mailed on Jun. 26, 2020, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2019-151358, mailed on Jan. 22, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2019-511611, mailed on Jul. 20, 2020, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2020-074878, mailed on May 28, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2020-551465, mailed on Jun. 28, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2017-7005939, mailed on Mar. 30, 2018, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7018904, mailed on Jun. 26, 2020, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7022101, mailed on Oct. 14, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7005734, mailed on Oct. 20, 2020, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7029673, mailed on Aug. 3, 2021, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7001340, mailed on May 10, 2021, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7026036, mailed on Jul. 26, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7028759, mailed on Oct. 19, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7002083, mailed on Jun. 18, 2021, 5 pages (2 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7002597, mailed on Feb. 25, 2021, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7013453, mailed on Aug. 11, 2021, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7013454, mailed on Aug. 12, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 104124962, mailed on Jul. 27, 2017, 3 pages (Official Copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Notice of Allowance received for Taiwanese Patent Application No. 104124963, mailed on Sep. 28, 2017, 5 pages (1 page of English Translation of Search report and 4 pages of Official Copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 104124995, mailed on Jul. 27, 2017, 3 pages (Official Copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Notice of Allowance received for Taiwanese Patent Application No. 104124997, mailed on Jun. 16, 2017, 5 pages (1 page of English Translation of Search report and 4 pages of Official Copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 104124998 mailed on Mar. 31, 2017, 3 pages (Official Copy only) (See Communication Under 37 CFR § 1.98(a) (3)). |
| Notice of Allowance received for Taiwanese Patent Application No. 104134740, mailed on Dec. 8, 2016, 5 pages (1 page of English Translation of Search Report and 4 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 14/815,879, mailed on Jun. 26, 2017, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/815,890, mailed on Feb. 12, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/815,898, mailed on Dec. 5, 2016, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/815,898, mailed on Oct. 24, 2016, 14 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/815,907, mailed on Jul. 28, 2016, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/815,907, mailed on Nov. 30, 2016, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/815,909, mailed on Jun. 9, 2016, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/815,909, mailed on May 3, 2016, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/815,909, mailed on May 20, 2016, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/815,909, mailed on Sep. 6, 2016, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/821,667, mailed on Jun. 12, 2019, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/839,889, mailed on Oct. 30, 2017, 16 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/183,663, mailed on Jan. 17, 2019, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/355,956, mailed on Nov. 22, 2019, 29 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/554,204, mailed on Jul. 13, 2020, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/791,829, mailed on Oct. 4, 2019, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/798,235, mailed on Apr. 1, 2020, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/798,235, mailed on Sep. 22, 2020, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/798,257, mailed on May 22, 2019, 14 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/881,544, mailed on Jun. 26, 2019, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/881,544, mailed on Nov. 7, 2019, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/401,934, mailed on Nov. 1, 2021, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/418,786, mailed on Dec. 9, 2021, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/582,020, mailed on Jul. 27, 2021, 29 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,281, mailed on Nov. 18, 2020, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,281, mailed on Sep. 29, 2020, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,445, mailed on Apr. 17,2020, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,445, mailed on Jul. 23, 2020, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,445, mailed on Jun. 24, 2020, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,445, mailed on May 29, 2020, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,445, mailed on Oct. 21,2020, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/585,366, mailed on Jan. 2, 2020, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/585,399, mailed on Jul. 21,2020, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/585,714, mailed on Jan. 8,2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/585,714, mailed on Jan. 27, 2021, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/585,714, mailed on Sep. 25, 2020, 15 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/585,721, mailed on Oct. 30, 2020, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/585,721, mailed on Sep. 30, 2020, 15 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/659,507, mailed on Feb. 24, 2021, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/867,002, mailed on Aug. 20, 2021, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/997,588, mailed on Sep. 30, 2021, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,654, mailed on Feb. 10, 2021, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,654, mailed on May 27, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/087,845, mailed on Oct. 28, 2021, 9 pages. |
| Nova Launcher—Lock Screen Edit, Online Available at: https://forums.androidcentral.com/ask-question/835057-nova-launcher-lock-screen-edit.html, Sep. 2017, 2 pages. |
| Nova, “Tour of the Solar System”, Retrieved from: http://www.pbs.org/wgbh/nova/space/tour-solar-system.html, May 24, 2013, 14 pages. |
| Obara, Yuuta, “Iphone Application Selection for Univesity Students”, Shuwa System Co., Saito Kazukuni, vol. 1, May 16, 2013, 4 pages (Official Copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Octoba, “Just Install It—Utilizing Method for Android Application Business”, ASCII Media Works Co. Takano Kiyoshi, vol. 1, Apr. 25, 2013, 6 pages (Official Copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Office Action and Search Report received for Danish Patent Application No. PA201970598, mailed on Jan. 28, 2020, 6 pages. |
| Office Action received for Australian Patent Application No. 2015101019, issued on Oct. 14, 2015, 3 pages. |
| Office Action received for Australian Patent Application No. 2015101019, issued on Apr. 7, 2016, 4 pages. |
| Office Action received for Australian Patent Application No. 2015101019, mailed on Feb. 12, 2016, 4 pages. |
| Office Action received for Australian Patent Application No. 2015101020, mailed on Oct. 26, 2015, 8 pages. |
| Office Action received for Australian Patent Application No. 2015101021, issued on Apr. 26, 2016, 4 pages. |
| Office Action received for Australian Patent Application No. 2015101021, issued on Oct. 28, 2015, 10 pages. |
| Office Action received for Australian Patent Application No. 2015298710, mailed on Apr. 13, 2017, 3 pages. |
| Office Action received for Australian Patent Application No. 2015298710, mailed on Feb. 15, 2017, 2 pages. |
| Office Action received for Australian Patent Application No. 2015298710, mailed on Nov. 6, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2015298710, mailed on Sep. 24, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2016100411, mailed on Jun. 10, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2016100476, mailed on Jun. 9, 2016, 4 pages. |
| Office Action received for Australian Patent Application No. 2016100765, issued on Aug. 5, 2016, 2 pages. |
| Office Action received for Australian Patent Application No. 2016100765, mailed on Dec. 16, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2016229847, mailed on Jul. 3, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2017277813, mailed on Jun. 11, 2019, 3 pages. |
| Office Action received for Australian Patent Application No. 2017277813, mailed on Mar. 20, 2020, 4 pages. |
| Office Action received for Australian Patent Application No. 2017330211, mailed on Dec. 5, 2019, 3 pages. |
| Office Action received for Australian Patent Application No. 2018100179, mailed on Jun. 4, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2018100179, mailed on Nov. 20, 2018, 7 pages. |
| Office Action received for Australian Patent Application No. 2018100179, mailed on Sep. 14, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2018201089, mailed on Jul. 23, 2020, 4 pages. |
| Office Action received for Australian Patent Application No. 2018201089, mailed on Oct. 11, 2019, 4 pages. |
| Office Action received for Australian Patent Application No. 2018206770, mailed on Apr. 30, 2019, 4 pages. |
| Office Action received for Australian Patent Application No. 2018206770, mailed on Jul. 16, 2019, 5 pages. |
| Office Action received for Australian Patent Application No. 2018206770, mailed on Jul. 25, 2018, 5 pages. |
| Office Action received for Australian Patent Application No. 2018206770, mailed on Mar. 5, 2019, 3 pages. |
| Office Action received for Australian Patent Application No. 2018279037, mailed on Jan. 17, 2020, 4 pages. |
| Office Action received for Australian Patent Application No. 2018279037, mailed on Jun. 18, 2019, 5 pages. |
| Office Action received for Australian Patent Application No. 2019208225, mailed on Dec. 21, 2020, 3 pages. |
| Office Action received for Australian Patent Application No. 2019208225, mailed on Mar. 20, 2020, 3 pages. |
| Office Action received for Australian Patent Application No. 2019267413, mailed on Jun. 29, 2021, 3 pages. |
| Office Action received for Australian Patent Application No. 2020102158, mailed on Apr. 27, 2021, 5 pages. |
| Office Action received for Australian Patent Application No. 2020102158, mailed on Dec. 8, 2020, 9 pages. |
| Office Action received for Australian Patent Application No. 2020204506, mailed on Dec. 7, 2020, 6 pages. |
| Office Action received for Australian Patent Application No. 2020217354, mailed on Jul. 22, 2021, 3 pages. |
| Office Action received for Australian Patent Application No. 2020239670, mailed on Mar. 3, 2021, 4 pages. |
| Office Action received for Australian Patent Application No. 2020239749, mailed on Jul. 16, 2021, 5 pages. |
| Office Action received for Australian Patent Application No. 2020239774, mailed on Jun. 28, 2021, 8 pages. |
| Office Action received for Australian Patent Application No. 2020239774, mailed on Oct. 5, 2021, 3 pages. |
| Office Action received for Australian Patent Application No. 2020309093, mailed on Jan. 21, 2021, 3 pages. |
| Office Action received for Australian Patent Application No. 2021202834, mailed on May 28, 2021, 2 pages. |
| Office Action received for Chinese Patent Application No. 201510479088.4, mailed on Apr. 22, 2020, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201510479088.4, mailed on Mar. 12, 2018, 20 pages (6 pages of English Translation and 14 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201510479088.4, mailed on May 7, 2019, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201510481525.6, mailed on Aug. 29, 2018, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201510481525.6, mailed on Nov. 29, 2017, 9 pages (3 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201510483268.X, mailed on Apr. 16, 2019, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201510483268.X, mailed on Dec. 1, 2017, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201510483268.X, mailed on Oct. 19, 2018, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201510483305.7, mailed on Aug. 31, 2018, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201510483305.7, mailed on Dec. 1, 2017, 13 pages (5 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201510484514.3, mailed on Apr. 4, 2018, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201510484514.3, mailed on Dec. 24, 2018, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201520594249.X, mailed on Dec. 9, 2015, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201520594249.X, mailed on Mar. 25, 2016, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201520595384.6, mailed on Dec. 9, 2015, 4 pages. (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201520595384.6, mailed on Dec. 30, 2016, 2 pages (Official Copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Office Action received for Chinese Patent Application No. 201520595384.6, mailed on Jul. 22, 2016, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201520595384.6, mailed on Mar. 25, 2016, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201520595385.0, mailed on Dec. 9, 2015, 4 pages (2 pages of English Translation and 2 pages of Official Copy. |
| Office Action received for Chinese Patent Application No. 201520595385.0, mailed on Dec. 30, 2016, 2 pages (Official Copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Office Action received for Chinese Patent Application No. 201520595385.0, mailed on Jul. 22, 2016, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201520595385.0, mailed on Mar. 25, 2016, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201520595408.8, mailed on Dec. 9, 2015, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action Received for Chinese Patent Application No. 201520595408.8, mailed on Dec. 30, 2016, 2 pages (Official Copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Office Action received for Chinese Patent Application No. 201520595408.8, mailed on Jul. 25, 2016, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201520595408.8, mailed on Mar. 25, 2016, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201520595538.1, mailed on Dec. 9, 2015, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201520595538.1, mailed on Dec. 30, 2016, 2 pages (Official Copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Office Action received for Chinese Patent Application No. 201520595538.1, mailed on Jul. 22, 2016, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201520595538.1, mailed on Mar. 25, 2016, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201680013193.1, mailed on Feb. 1, 2021, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201680013193.1, mailed on Mar. 25, 2020, 21 pages (8 pages of English Translation and 13 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201680013193.1, mailed on Sep. 7, 2020, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201680047983.1, mailed on Feb. 1, 2021, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201680047983.1, mailed on Jul. 1, 2020, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201680047983.1, mailed on Mar. 18, 2019, 18 pages (6 pages of English Translation and 12 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201680047983.1, mailed on Nov. 28, 2019, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201780002643.1, mailed on Aug. 2, 2021, 20 pages (6 pages of English Translation and 14 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201780002643.1, mailed on Dec. 31, 2020, 26 pages (6 pages of English Translation and 20 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201780002643.1, mailed on Jun. 17, 2020, 30 pages (10 pages of English Translation and 20 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201780033973.7, mailed on Jan. 22, 2021, 27 pages (11 pages of English Translation and 16 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201810037665.8, mailed on Dec. 7, 2018, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201810467061.7, mailed on Aug. 15, 2019, 13 pages (7 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201810467061.7, mailed on Feb. 22, 2019, 19 pages (10 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 2018104670617, mailed on Feb. 18, 2020, 12 pages (6 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201910906898.1, mailed on Jun. 23, 2021, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201910906898.1, mailed on Sep. 9, 2020, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202110194015.6, mailed on Sep. 28, 2021, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202110453180.9, mailed on Nov. 8, 2021, 21 pages (11 pages of English Translation and 10 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202110454541.1, mailed on Oct. 20, 2021, 19 pages (10 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA201570495, mailed on Dec. 9, 2016, 2 pages. |
| Office Action received for Danish Patent Application No. PA201570495, mailed on May 4, 2016, 8 pages. |
| Office Action received for Danish Patent Application No. PA201570495, mailed on Oct. 29, 2015, 7 pages. |
| Office Action received for Danish Patent Application No. PA201570496, mailed on Oct. 29, 2015, 6 pages. |
| Office Action received for Danish Patent Application No. PA201570497, mailed on Feb. 21, 2017, 3 pages. |
| Office Action received for Danish Patent Application No. PA201570497, mailed on May 17, 2016, 6 pages. |
| Office Action received for Danish Patent Application No. PA201570497, mailed on Nov. 15, 2016, 2 pages. |
| Office Action received for Danish Patent Application No. PA201570497, mailed on Oct. 24, 2017, 2 pages. |
| Office Action received for Danish Patent Application No. PA201570497, mailed on Oct. 30, 2015, 6 pages. |
| Office Action received for Danish Patent Application No. PA201570498, mailed on Feb. 6, 2017, 2 pages. |
| Office Action received for Danish Patent Application No. PA201570498, mailed on Jun. 2, 2016, 8 pages. |
| Office Action received for Danish Patent Application No. PA201570498, mailed on Oct. 26, 2017, 5 pages. |
| Office Action received for Danish Patent Application No. PA201570498, mailed on Oct. 30, 2015, 7 pages. |
| Office Action received for Danish Patent Application No. PA201570499, mailed on Feb. 14, 2017, 2 pages. |
| Office Action received for Danish Patent Application No. PA201570499, mailed on Jun. 16, 2016, 8 pages. |
| Office Action received for Danish Patent Application No. PA201570499, mailed on Jun. 19, 2018, 4 pages. |
| Office Action received for Danish Patent Application No. PA201570499, mailed on Nov. 1, 2017, 6 pages. |
| Office Action received for Danish Patent Application No. PA201570499, mailed on Nov. 3, 2015, 7 pages. |
| Office Action received for Danish Patent Application No. PA201570768, mailed on Sep. 13, 2016, 8 pages. |
| Office Action received for Danish Patent Application No. PA201570770, mailed on Apr. 7, 2017, 7 pages. |
| Office Action received for Danish Patent Application No. PA201570770, mailed on Mar. 17, 2016, 9 pages. |
| Office Action received for Danish Patent Application No. PA201570770, mailed on Sep. 12, 2016, 6 pages. |
| Office Action received for Danish Patent Application No. PA201770387, mailed on Feb. 1, 2018., 3 Pages. |
| Office Action received for Danish Patent Application No. PA201770791, mailed on Jan. 31, 2018, 8 pages. |
| Office Action received for Danish Patent Application No. PA201770791, mailed on Jul. 13, 2018, 2 pages. |
| Office Action received for Danish Patent Application No. PA201770791, mailed on Jun. 11, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201970596, mailed on May 6, 2020, 4 pages. |
| Office Action received for Danish Patent Application No. PA201970597, mailed on Oct. 29, 2020, 4 pages. |
| Office Action received for Danish Patent Application No. PA201970598, mailed on Apr. 15, 2021, 6 pages. |
| Office Action received for Danish Patent Application No. PA201970598, mailed on Oct. 9, 2020, 4 pages. |
| Office Action received for Danish Patent Application No. PA201970599, mailed on Jan. 23, 2020, 6 pages. |
| Office Action received for Danish Patent Application No. PA201970599, mailed on Mar. 1, 2021, 4 pages. |
| Office Action received for Danish Patent Application No. PA201970599, mailed on May 27, 2020, 4 pages. |
| Office Action received for Danish Patent Application No. PA202070609, mailed on Dec. 10, 2020, 8 pages. |
| Office Action received for Danish Patent Application No. PA202070610, mailed on Jun. 18, 2021, 8 pages. |
| Office Action received for Danish Patent Application No. PA202070623, mailed on Aug. 24, 2021, 3 pages. |
| Office Action received for Danish Patent Application No. PA202070624, mailed on Jun. 16, 2021, 5 pages. |
| Office Action received for Danish Patent Application No. PA202070625, mailed on Jun. 16, 2021, 3 pages. |
| Office Action received for European Patent Application No. 15730924.6, mailed on Dec. 12, 2017, 8 pages. |
| Office Action received for European Patent Application No. 15730925.3, mailed on Apr. 12, 2018, 8 pages. |
| Office Action received for European Patent Application No. 15730925.3, mailed on Feb. 27, 2019, 5 pages. |
| Office Action received for European Patent Application No. 15747595.5, mailed on Apr. 15, 2019, 4 pages. |
| Office Action received for European Patent Application No. 15747595.5, mailed on Jun. 27, 2018, 8 pages. |
| Office Action received for European Patent Application No. 16762356.0, mailed on Dec. 11, 2020, 7 pages. |
| Office Action received for European Patent Application No. 16837432.0, mailed on Jan. 10, 2020, 7 pages. |
| Office Action received for European Patent Application No. 16837432.0, mailed on Jan. 27, 2021, 7 pages. |
| Office Action received for European Patent Application No. 17206177.2, mailed on May 15, 2018, 6 pages. |
| Office Action received for European Patent Application No. 17810723.1, mailed on Jul. 9, 2021, 8 pages. |
| Office Action received for European Patent Application No. 17853656.1, mailed on Mar. 25, 2021, 8 pages. |
| Office Action received for European Patent Application No. 18172554.0, mailed on Jul. 12, 2019, 10 Pages. |
| Office Action received for European Patent Application No. 20172197.4, mailed on Aug. 5, 2020, 6 pages. |
| Office Action received for European Patent Application No. 20172197.4, mailed on Jul. 8, 2021, 5 pages. |
| Office Action received for German Patent Application No. 112015003083.2, mailed on Mar. 9, 2018, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Indian Patent Application No. 202017041557, mailed on Dec. 8, 2021, 8 pages. |
| Office Action received for Japanese Patent Application No. 2017-505450, mailed on Jun. 20, 2017, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2017-505842, mailed on Feb. 22, 2019, 11 pages (6 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2017-505842, mailed on Sep. 9, 2019, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2017-505847, mailed on Feb. 12, 2019, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2017-545918, mailed on Sep. 14, 2018, 12 pages (7 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2018-074971, mailed on Jan. 28, 2019, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2018-537840, mailed on Jul. 8, 2019, 15 pages (8 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2019-151358, mailed on Oct. 2, 2020, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2019-511611, mailed on Feb. 28, 2020, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2020-074878, mailed on Sep. 7, 2020, 13 pages (7 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2020-124605, mailed on Sep. 3, 2021, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2020-137007, mailed on Jun. 21, 2021, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2017-7005939, mailed on Jun. 30, 2017, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2017-7024570, mailed on Jul. 10, 2019, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2017-7024570, mailed on Sep. 28, 2018, 14 pages (6 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-7018904, mailed on Aug. 20, 2019, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-7022101, mailed on Feb. 14, 2019, 15 pages (6 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-7022101, mailed on Jul. 9, 2019, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2019-7005734, mailed on Feb. 24, 2020, 13 pages (7 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2019-7005734, mailed on Jul. 14, 2020, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2019-7029673, mailed on Apr. 8, 2021, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2019-7029673, mailed on Nov. 5, 2019, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2019-7029673, mailed on Sep. 3, 2020, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-7001340, mailed on Mar. 26, 2021, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-7001340, mailed on Sep. 24, 2020, 19 pages (8 pages of English Translation and 11 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-7026036, mailed on Dec. 7, 2020, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-7028759, mailed on Jun. 29, 2021, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2021-7002083, mailed on Feb. 10, 2021, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2021-7013453, mailed on Jun. 5, 2021, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2021-7013454, mailed on Jun. 5, 2021, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2021-7025301, mailed on Oct. 15, 2021, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2021-7030552, mailed on Nov. 22, 2021, 14 pages (8 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2021-7036016, mailed on Nov. 10, 2021, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2021-7036246, mailed on Nov. 26, 2021, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Netherland Patent Application No. 2015245, mailed on Jan. 24, 2017, 11 pages (1 page of English Translation and 10 pages of Official Copy). |
| Office Action received for Netherlands Patent Application No. 2015239, mailed on Oct. 28, 2016, 13 pages (5 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104124962, issued on Nov. 29, 2016, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104124963, mailed on Jan. 5, 2017, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104124995, issued on Dec. 1, 2016, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104124997, issued on Dec. 8, 2016, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104124998, mailed on Nov. 29, 2016, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104126627, issued on Nov. 29, 2016, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104126627, mailed on Aug. 30, 2018, 22 pages (9 pages of English Translation and 13 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104126627, mailed on Dec. 20, 2018, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104126627, mailed on Oct. 16, 2017, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104132636, issued on Dec. 13, 2018, 26 pages (9 pages of English Translation and 17 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104132636, issued on Mar. 23, 2017, 25 pages (10 pages of English Translation and 15 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104132636, issued on Oct. 31, 2017, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Omar Romero, “Sony Smartwatch 2 Custom Watchfaces Tutorial”, Retrieved From: https://www.youtube.com/watch?v=8odbxqwSQR8, May 1, 2014, 2 pages. |
| Online Alarm Clock, https://web.archive.org/web/20150505081746/ http://www.online-stopwatch.com/online-alarm-clock, May 5, 2015, 2 pages. |
| Pa201570497, “Link to Wayback Machine with Link to Google Play Showing Different Layouts of Complications Associated with a Clock Face”, Available online at: https://play.google.com/store/apps/details?id=com.levelup.beautifulwidgets.free&hl=da, Sep. 9, 2013, 6 pages. |
| Pentax K20d Operating Manual, available online at: http://www.ricoh-imaging.eu/en/operating-manuals-download.html 2008, pp. 173-174. |
| Phandroid, “New Android Wear Wrist Gestures in Marshmallow”, Available online at: https://www.youtube.com/watch?v=0WhKuklpQ9A, Feb. 11, 2016, 3 pages. |
| Phlam, Dev, “Clockwork Tomato Presentation”, Retrieved from the Internet: URL: https://www.youtube.com/watch?v=2IQDx9REn0E, Apr. 29, 2016, 6 pages. |
| Phonebuff, “Hybrid Stopwatch & Timer Android App Review”, Available Online at: https://www.youtube.com/watch?v=B43oCFPiWvY, Apr. 4, 2012, 7 pages. |
| Pre-interview First Office Action received for U.S. Appl. No. 14/815,890, mailed on May 26, 2016, 4 pages. |
| Record of Oral Hearing received for U.S. Appl. No. 14/815,890, mailed on Nov. 20, 2020, 18 pages. |
| Rehman, A, “Install Android 4.2 Gesture-based Keyboard & Clock App on JellyBean 4.1 or Higher”, Excerpts From, Available online at: http://www.addictivetips.com/android/install-android-4-2-keyboard-clock-app-apk-on-jelly-bean-4-1-x/, Nov. 3, 2012, 4 pages. |
| Restriction Requirement received for U.S. Appl. No. 14/815,890, mailed on Feb. 22, 2016, 5 pages. |
| Result of Consultation received for European Patent Application No. 15730925.3, mailed on Nov. 24, 2020, 4 pages. |
| Result of Consultation received for European Patent Application No. 16762356.0, mailed on Nov. 29, 2021, 3 pages. |
| Rosa et al., “Stripe Generator—a Free Tool for the Web Design Community”, Available online at: http://www.stripegenerator.com/, Mar. 28, 2019, 10 pages. |
| Rowinski, Dan, “Why the All-in-one Smartwatch Isn't Happening Any Time Soon”, Online Available at: https://web.archive.org/web/20140123074218if_/https://readwrite.com/2014/01/20/smartwatch-wearable-fitness-remote-control/, Jan. 20, 2014, 6 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201770387, mailed on Oct. 12, 2017., 8 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201970596, mailed on Dec. 4, 2019, 11 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201970597, mailed on Dec. 18, 2019, 10 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201970598, mailed on Oct. 31, 2019, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201970599, mailed on Nov. 8, 2019, 12 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070610, mailed on Jan. 8, 2021, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070623, mailed on Dec. 21, 2020, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070624, mailed on Dec. 10, 2020, 10 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070625, mailed on Dec. 17, 2020, 9 pages. |
| Search Report and Opinion received for Netherland Patent Application No. 2015232, mailed on Jan. 25, 2017, 9 pages (1 page of English Translation and 8 pages of Official Copy). |
| Search Report and Opinion received for Netherlands Patent Application No. 2015242, issued on Jul. 4, 2017, 20 pages (10 pages of English Translation of Search Opinion and 10 pages of Official Copy). |
| Search Report and Opinion received for Netherlands Patent Application No. 2018531, Issued on Jul. 27, 2017, 14 pages (6 pages of English Translation and 8 pages of Official Copy). |
| Search Report received for Danish Patent Application No. 201570768, mailed on Mar. 17, 2016, 11 pages. |
| Search Report received for Netherlands Patent Application No. 2015236, mailed on Apr. 21, 2021, 19 pages (13 pages of English Translation and 6 pages of Official Copy). |
| Shiota, Shinji, “Windows 7 Dojo”, Weekly ASCII, Ascii Mediaworks Inc., vol. 798, Aug. 31, 2010, 3 pages. |
| Singh, Lovepreet, “Samsung Galaxy Watch: How to Change Watch Face—Tips and Tricks”, Online available at: https://www.youtube.com/watch?pp=desktop&v=IN7gPxTZ1qU, Dec. 4, 2018, 1 page. |
| Smartwatch, “App Earth Space Hd Live Wallpaper Apk for Smart Watch”, Version 1.7, Android version 2.2, Aug. 27, 2013, 1 page. |
| Solar Walk Free, Vito Technology Jun. 19, 2014, 9 pages. |
| Sony, “Live View™ Micro Display”, Extended User Guide, Aug. 2010, 27 pages. |
| Sony, “Sony Smartwatch”, User Guide, Dec. 2011, 18 pages. |
| Stateoftech, “Samsung Galaxy Gear Tips—Installing and Customizing Clock Faces”, Online available at: https://www.youtube.com/watch?v=p2GzpL3xlUo, Dec. 12, 2013, 3 pages. |
| Stateoftech, “Samsung Galaxy Gear Tips—Change the Clock Face”, Retrieved from: https://www.youtube.com/watch?v=GOom7AZUAjY, Dec. 11, 2013, 2 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 15730924.6, mailed on Jun. 13, 2018, 10 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 15730925.3, mailed on Oct. 2, 2019, 8 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 16762356.0, mailed on May 10, 2021, 10 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 17206177.2, mailed on Jun. 3, 2019, 8 pages. |
| Sun Set, “Sun Set Solar Image Clock”, Available at: https://web.archive.orgjweb/20140719005410/http://www.sunsetclock.com/, 2013, 5 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 14/815,890, mailed on Mar. 10, 2021, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/585,399, mailed on Aug. 26, 2020, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/867,002, mailed on Sep. 9, 2021, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/997,588, mailed on Oct. 22, 2021, 4 pages. |
| Talkandroid, “Android Wear Walkthrough”, Available online at: https://www.youtube.com/watch?v=4xntpZac4sw, Jun. 30, 2014, 1 page. |
| Techcloud, “How to Create Custom Watch Face for Samsung Galaxy Gear Smartwatch Just in Few Seconds”, Online available at:—https://www.youtube.com/watch?v=6rO-_SREDjQ, Oct. 9, 2013, 3 pages. |
| The Simply Alarm App for Pebble, Available online at: https://web.archive.org/web/20150517070400/http://www.rebootsramblings.ca/n/sahhelp/ https://www.youtube.com/watch?v=IVp1scQPw08, May 17, 2015, 1 page. |
| Theunlockr, “How to Change the Watch Face on the Galaxy Gear”, Online available at: https://www.youtube.com/watch?v=Z7EBG5aBiZg, Jan. 3, 2014, 3 pages. |
| Tweedie, Steven, “Create and Customize Your Own Emojis with ‘makemoji’ for Iphone”, Available online at: http://www.businessinsider.com/create-custom-emojis-with-makemoji-app-2014-8, Aug. 19, 2014, 6 pages. |
| Uikit User Interface Catalog: Page Controls, Available online at: https://web.archive.org/web/20140703123442/https://developer.apple.com/, Dec. 16, 2013, 4 pages. |
| Ultitorch For, Online Available at <https://apkgk.com/com.qasq.torchpro>, 4 pages. |
| Vidstube, “Bitmoji Clockface on Fitbit Versa Sense/versa 3/versa 2”, Available online at: https://www.youtube.com/watch?v=4V_xDnSLeHE, Jun. 30, 2019, 1 page. |
| Viticci, Frederico, “Checking Time Zones with Living Earth—Macstories”, Available at: https://www.macstories.net/reviews/checking-time-zones-with-living-earth/, Dec. 11, 2013, pp. 1-5. |
| Wade, Cliff, “Get the Most Out of Nova Launcher: Changing Icon Sizes”, Online Available at: https://www.androidguys.com/tips-tools/get-nova-launcher-changing-icon-sizes/, Nov. 16, 2015, 3 pages. |
| Wade, Cliff, “Get the Most Out of Nova Launcher: Changing Icon Sizes”, Online available at: https://www.androidguys.com/tips-tools/get-nova-launcher-changing-icon-sizes/, Nov. 16, 2015, 6 pages. |
| Wade, Cliff, “Get the Most Out of Nova Launcher: Customizing the Dock (contest Included)”, Online Available at: https://www.androidguys.com/tips-tools/get-nova-launcher-customizing-dockcontest-included/, Dec. 1, 2015, 5 pages. |
| Watchophilia, “Mickey Mouse Watches”, Online Available at: https://web.archive.org/web/20130929065422/https://www.watchophilia.com/photogallery/mickey-mouse/, Sep. 29, 2013, 16 pages. |
| Watchuseek, “The Watch Every Father Needs: M-i-c-k-e-y, M-o-u-s-e. Mickey Mouse . . .?”, Online Available at: https://forums.watchuseek.com/f2/watch-every-father-needs-m-i- c-k-e-y-m-o-u-s-e-mickey-mouse-855069.html, 2013, 3 pages. |
| Wearablezone, “How to Set Up Your Fitbit Profile”, Online available at: https://youtu.be/jsWPtcDWiJM, Jun. 6, 2016, 3 pages. |
| Whitwam, Ryan, “Facer is Fast Becoming the De Facto Custom Watch Face Maker for Android Wear”, Available online at: http://www.androidpolice.com/2014/09/19/facer-is-fast-becoming-the-de-facto-custom-watch-face-maker-for-android-wear, Sep. 19, 2014, 11 pages. |
| Wikipedia, “Emoji”, Available online at: https://en.wikipedia.org/w/index.php?title=Emoji&oldid=648831795, Feb. 25, 2015, 12 pages. |
| Wikipedia, “Emoticon”, Available online at: https://en.wikipedia.org/w/index.php?title=Emoticon&oldid=648776142, Feb. 25, 2015, 9 pages. |
| Woolsey, Amanda, “How to Customize the Clock on the Apple Watch”, Available online at: https://www.youtube.com/watch?v=t-3Bckdd9B4>, Apr. 25, 2015, 1 page. |
| Xdream, “Ticktalk Video User Manual”, YouTube [online] [video], Online available at: https://youtu.be/jYhq3DwmVzo, Mar. 17, 2017, 3 pages. |
| Xperia ZL2 SOL25, “Instruction Manual”, Detailed version, KDDI Corporation, No. 1, vol. 1, Jun. 2014, 4 pages. |
| Zelgadis, “Reuse Animations—Synfig Animation Studio”, Available online at: https://wiki.synfig.org/index.php?title=Doc: Reuse_Animations&oldid=18173, May 20, 2013, 5 pages. |
| Zephyrnix, “Steam's In-game Home Menu”, Online Available at: https://www.youtube.com/watch?v=jLoRFiPkcUw, see 0;00-1;06., Feb. 15, 2011, 3 pages. |
| Zukerman, Erez, “6 Beautiful, Interesting & Versatile Timer Apps [android]”, available at: http://www.makeuseof.com/tag/beautiful-interesting-versatile-timer-apps-android/, May 18, 2012, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/681,584, mailed on Jan. 18, 2023, 12 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021250863, mailed on Jan. 13, 2023, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2022-139320, mailed on Jan. 6, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7019205, mailed on Jan. 5, 2023, 8 pages (2 pages of English Translation and 6 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/158,936, mailed on Dec. 28, 2022, 4 pages. |
| Final Office Action received for U.S. Appl. No. 17/591,184, mailed on Dec. 23, 2022, 10 pages. |
| Intention to Grant received for European Patent Application No. 17810723.1, mailed on Dec. 16, 2022, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/738,940, mailed on Dec. 22, 2022, 31 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7014529, mailed on Dec. 13, 2022, 8 pages (2 pages of English Translation and 6 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7027441, mailed on Dec. 2, 2022, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 17/515,143, mailed on Dec. 16, 2022, 11 pages. |
| Office Action received for European Patent Application No. 20761084.1, mailed on Dec. 14, 2022, 5 pages. |
| Poppinga et al., “Sensor-Based Identification of Opportune Moments for Triggering Notifications”, IEEE CS, Mar. 14, 2014, pp. 22-29. |
| Pradhan et al., “Understanding and Managing Notifications”, IEEE Infocom 2017—IEEE Conference on Computer Communications, May 1, 2017, 9 pages. |
| Advisory Action received for U.S. Appl. No. 15/405,122, mailed on Apr. 18, 2022, 5 pages. |
| Advisory Action received for U.S. Appl. No. 16/935,002, mailed on May 6, 2022, 3 pages. |
| Advisory Action received for U.S. Appl. No. 16/943,737, mailed on Jun. 1, 2022, 6 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 17/031,671, mailed on Jun. 13, 2022, 7 pages. |
| Applicant-lnitiated Interview Summary received for U.S. Appl. No. 16/418,786, mailed on May 9, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/943,737, mailed on Apr. 29, 2022, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,765, mailed on May 23, 2022, 5 pages. |
| Applicant-lnitiated Interview Summary received for U.S. Appl. No. 17/078,896, mailed on Apr. 25, 2022, 2 pages. |
| Applicant-lnitiated Interview Summary received for U.S. Appl. No. 17/317,042, mailed on Apr. 29, 2022, 2 pages. |
| Applicant-initiated Interview Summary received for U.S. Appl. No. 17/341,839, mailed on Apr. 29, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/373,163, mailed on Apr. 11, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/418,786, mailed on Jun. 23, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/041,350, mailed on Apr. 4, 2022, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/041,350, mailed on Mar. 15, 2022, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/373,163, mailed on Jun. 27, 2022, 5 pages. |
| Decision to Grant received for European Patent Application No. 167623560, mailed on Apr. 26, 2022, 2 pages. |
| Intention to Grant received for European Patent Application No. 201859741, mailed on Apr. 28, 2022, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/045814, mailed on Mar. 17, 2022, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/418,786, mailed on Mar. 28, 2022, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,671, mailed on Apr. 1, 2022, 32 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,765, mailed on Mar. 29, 2022, 33 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/341,839, mailed on Mar. 17, 2022, 14 pages. |
| Notice of Acceptance received for Austraiian Patent Application No. 2020217354, mailed on May 31, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020239749, mailed on May 27, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020250323, mailed on Feb. 28, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021202797, mailed on May 9, 2022, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 2021101940156, mailed on Mar. 9, 2022, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 2021104545411, mailed on May 31, 2022, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2020-159825, mailed on Mar. 25, 2022, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2021-565837, mailed on May 16, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7025301, mailed on Mar. 16, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7030552, mailed on May 6, 2022, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7036246, mailed on Mar. 2, 2022, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7036678, mailed on Mar. 7, 2022, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7001721, mailed on Feb. 28, 2022, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/418,786, mailed on Jun. 14, 2022, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/997,588, mailed on Mar. 18, 2022, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/078,896, mailed on May 13, 2022, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/373,163, mailed on May 11, 2022, 8 pages. |
| Office Action received for Australian Patent Application No. 2021203216, mailed on Mar. 7, 2022, 8 pages. |
| Office Action received for Australian Patent Application No. 2022202292, mailed on May 10, 2022, 2 pages. |
| Office Action received for Chinese Patent Application No. 201810467061.7, mailed on Apr. 11, 2022, 19 pages (11 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201810467061.7, mailed on Jun. 22, 2022, 15 pages (1 page of English Translation and 14 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202110783860.7, mailed on Mar. 10, 2022, 15 pages (5 pages of English Translation and 10 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA202070610, mailed on Mar. 14, 2022, 7 pages. |
| Office Action received for Danish Patent Application No. PA202070623, mailed on May 23, 2022, 3 pages. |
| Office Action received for European Patent Application No. 17853656.1, mailed on May 3, 2022, 7 pages. |
| Office Action received for European Patent Application No. 20761084.1, mailed on May 9, 2022, 9 pages. |
| Office Action received for European Patent Application No. 21169911.1, mailed on Jun. 3, 2022, 5 pages. |
| Office Action received for European Patent Application No. 21177569.7, mailed on Jun. 9, 2022, 5 pages. |
| Office Action received for Indian Patent Application No. 202118025047, mailed on Apr. 26, 2022, 6 pages. |
| Office Action received for Japanese Patent Application No. 2020-124605, mailed on May 13, 2022, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2020-137007, mailed on May 9, 2022, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2020-159824, mailed on Dec. 17, 2021, 13 pages (7 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-0123852, mailed on Jun. 9, 2022, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-0123857, mailed on Jun. 9, 2022, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-0123887, mailed on Jun. 9, 2022, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-7032187, mailed on Jun. 10, 2022, 16 pages (7 pages of English Translation and 9 pages of Official Copy). |
| Result of Consultation received for European Patent Application No. 20185974.1, mailed on Apr. 4, 2022, 4 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/867,002, mailed on Mar. 16, 2022, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/997,588, mailed on Apr. 20, 2022, 4 pages. |
| Jurick et al., “iPhone Hacks”, Tips & Tools for Unlocking the Power of Your iPhone & iPod touch, Online:URL:https://api.pageplace.de/preview/DT0400.9780596550974_A23629666/preview-9780596550974_A23629666.pdf >, Apr. 2009, 49 pages. |
| Advisory Action received for U.S. Appl. No. 16/861,651, mailed on Jul. 29, 2022, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/418,786, mailed on Sep. 23, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/341,839, mailed on Sep. 16, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/591,184, mailed on Sep. 23, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/373,163, mailed on Jul. 15, 2022, 5 pages. |
| Decision to Grant received for European Patent Application No. 20185974.1, mailed on Aug. 19, 2022, 3 pages. |
| Extended European Search Report received for European Patent Application No. 22173249.8, mailed on Aug. 19, 2022, 15 pages. |
| Final Office Action received for U.S. Appl. No. 15/421,865, mailed on Jul. 12, 2022, 27 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,765, mailed on Sep. 12, 2022, 37 pages. |
| Final Office Action received for U.S. Appl. No. 17/341,839, mailed on Jul. 18, 2022, 15 pages. |
| Google, “Android User's Guide”, Retrieved from the Internet: https://static.googleusercontent.com/media/www.google.com/en//help/hc/pdfs/mobile/AndroidUsersGuide-30-100.pdf, Feb. 23, 2011, 140 pages. |
| Intention to Grant received for Danish Patent Application No. PA202070623, mailed on Jul. 20, 2022, 2 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 20730136.7, mailed on Jul. 1, 2022, 4 pages. |
| Lein et al., “Patternizer”, Available online at : https://patternizer.com/, Apr. 2016, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/389,722, mailed on Jul. 7, 2022, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/418,786, mailed on Aug. 1, 2022, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/556,165, mailed on Sep. 7, 2022, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/591,184, mailed on Aug. 4, 2022, 18 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021203216, mailed on Jul. 26, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022202292, mailed on Jul. 6, 2022, 3 pages. |
| Notice of Allowance received for Danish Patent Application No. PA202070623, mailed on Sep. 20, 2022, 2 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-562622, mailed on Aug. 26, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2021-105941, mailed on Jul. 4, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2021-122610, mailed on Aug. 5, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 17/317,042, mailed on Jul. 26, 2022, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/373,163, mailed on Jul. 27, 2022, 8 pages. |
| Office Action received for Australian Patent Application No. 2021245228, mailed on Aug. 31, 2022, 2 pages. |
| Office Action received for Chinese Patent Application No. 202110453180.9, mailed on Jun. 16, 2022, 14 pages (7 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202111457936.3, mailed on Jul. 5, 2022, 18 pages (9 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA202070625, mailed on Sep. 23, 2022, 4 pages. |
| Office Action received for European Patent Application No. 20729346.5, mailed on Jul. 28, 2022, 9 pages. |
| Office Action received for Indian Patent Application No. 202017048447, mailed on Sep. 5, 2022, 6 pages. |
| Office Action received for Japanese Patent Application No. 2020-159823, mailed on Aug. 15, 2022, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2022-7027441, mailed on Aug. 24, 2022, 11 pages (6 pages of English Translation and 5 pages of Official Copy). |
| Programmatically download APK from google play store, retrieved from the Internet: https://stackoverflow.com/questions/13703982/prog ram maticallydownload-apk-from-google-play-store/13704021#13704021, Dec. 10, 2012, 2 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 17810723.1, mailed on Jul. 5, 2022, 8 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2022/026371, mailed on Aug. 18, 2022, 9 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 16/861,651, mailed on Jan. 18, 2023, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/068,386, mailed on Jan. 30, 2023, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/676,034, mailed on Jan. 24, 2023, 15 pages. |
| Office Action received for Chinese Patent Application No. 202110453180.9, mailed on Dec. 26, 2022, 13 pages (8 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for European Patent Application No. 20730136.7, mailed on Jan. 19, 2023, 4 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20729346.5, mailed on Jan. 23, 2023, 11 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/405,122, mailed on Mar. 1, 2022, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/421,865, mailed on Feb. 28, 2022, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/389,722, mailed on Feb. 18, 2022, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/861,651, mailed on Dec. 29, 2021, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/041,350, mailed on Feb. 2, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/068,386, mailed on Jan. 13, 2022, 2 pages. |
| Board Decision received for Chinese Patent Application No. 201780002643.1, mailed on Dec. 15, 2021, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/713,544, mailed on Feb. 3, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/713,544, mailed on Feb. 10, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/713,544, mailed on Feb. 23, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/401,934, mailed on Dec. 23, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/401,934, mailed on Feb. 28, 2022, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/418,786, mailed on Jan. 5, 2022, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/792,096, mailed on Jan. 11, 2022, 3 pages. |
| Decision on Appeal received for U.S. Appl. No. 14/846,511, mailed on Dec. 29, 2021, 20 pages. |
| Final Office Action received for U.S. Appl. No. 16/861,651, mailed on Jan. 26, 2022, 16 pages. |
| Final Office Action received for U.S. Appl. No. 16/935,002, mailed on Jan. 5, 2022, 25 pages. |
| Final Office Action received for U.S. Appl. No. 16/943,737, mailed on Feb. 4, 2022, 24 pages. |
| Final Office Action received for U.S. Appl. No. 17/068,386, mailed on Mar. 3, 2022, 29 pages. |
| Ilovex, ““Stripe Generator”, a tool that makes it easy to create striped materials”, Online available at: https://www.ilovex.co.jp/blog/system/webconsulting/stripe-generator.html, May 2, 2012, 3 pages (Official Copy Only). {See Communication under 37 CFR § 1.98(a) (3)}. |
| Intention to Grant received for European Patent Application No. 16762356.0, mailed on Dec. 23, 2021, 8 pages. |
| Kasai, Yoshino, “Apple Watch Absolute Basics—Season 3—The key is to customize the dial”, Mynavi Corporation, Online Available at: https://news.mynavi.jp/article/20171104-apple_watch/, Nov. 4, 2017, 5 pages (Official Copy only). {See Communication under 37 CFR § 1.98(a) (3)}. |
| Non-Final Office Action received for U.S. Appl. No. 15/421,865, mailed on Dec. 29, 2021, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/373,163, maiied on Jan. 27, 2022, 14 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020239774, mailed on Jan. 5, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020269232, mailed on Dec. 16, 2021, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 2017800026431, mailed on Jan. 6, 2022, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7034748, mailed on Jan. 27, 2022, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 15/713,544, mailed on Jan. 14, 2022, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/401,934, mailed on Feb. 2, 2022, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/792,096, mailed on Dec. 29, 2021, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/867,002, mailed on Mar. 1, 2022, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/041,350, mailed on Feb. 24, 2022, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/087,845, mailed on Mar. 3, 2022, 9 pages. |
| Office Action received for Australian Patent Application No. 2020217354, mailed on Jan. 17, 2022, 5 pages. |
| Office Action received for Australian Patent Application No. 2020239749, mailed on Jan. 21, 2022, 4 pages. |
| Office Action received for Australian Patent Application No. 2020250323, mailed on Dec. 14, 2021, 2 pages. |
| Office Action received for Australian Patent Application No. 2021202797, mailed on Feb. 4, 2022, 5 pages. |
| Office Action received for Danish Patent Application No. PA202070624, mailed on Feb. 4, 2022, 4 pages. |
| Office Action received for Danish Patent Application No. PA202070625, mailed on Feb. 8, 2022, 2 pages. |
| Office Action received for European Patent Application No. 20180900.1, mailed on Feb. 14, 2022, 8 pages. |
| Office Action received for European Patent Application No. 20729346.5, mailed on Jan. 17, 2022, 8 pages. |
| Office Action received for Japanese Patent Application No. 2020-124605, mailed on Dec. 17, 2021, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Office Action received for Japanese Patent Application No. 2020-159823, mailed on Dec. 23, 2021, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2020-159825, mailed on Dec. 10, 2021, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2020-562622, mailed on Jan. 7, 2022, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2021-023661, mailed on Feb. 25, 2022, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2021-7036678, mailed on Dec. 22, 2021, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/713,016, mailed on Feb. 14, 2023, 4 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/746,807, mailed on Feb. 2, 2023, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/948,578, mailed on Feb. 2, 2023, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/935,002, mailed on Feb. 15, 2023, 15 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,765, mailed on May 3, 2023, 6 pages. |
| Final Office Action received for U.S. Appl. No. 17/068,386, mailed on May 8, 2023, 23 pages. |
| Final Office Action received for U.S. Appl. No. 17/746,807, mailed on Apr. 26, 2023, 16 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/941,962, mailed on May 3, 2023, 10 pages. |
| Office Action received for European Patent Application No. 20180900.1, mailed on May 3, 2023, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,765, mailed on Apr. 17, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/068,386, mailed on Apr. 24, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/941,962, mailed on Apr. 14, 2023, 6 pages. |
| Final Office Action received for U.S. Appl. No. 17/681,584, mailed on Apr. 20, 2023, 15 pages. |
| Intention to Grant received for European Patent Application No. 16837432.0, mailed on Apr. 14, 2023, 8 pages. |
| Non-Final Office Action received for U.S. Patent Application No. 17/591, 184, mailed on Apr. 21, 2023, 15 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201910924197.0, mailed on Apr. 5, 2023, 3 pages (2 pages of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2021-023661, mailed on Apr. 10, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 17/713,016, mailed on Apr. 18, 2023, 10 pages. |
| Office Action received for Australian Patent Application No. 2022218607, mailed on Apr. 14, 2023, 3 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20172197.4, mailed on Apr. 14, 2023, 8 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 17/681,584, mailed on Mar. 24, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/935,002, mailed on Mar. 28, 2023, 2 pages. |
| Droid Life, “20+ Galaxy S9, S9+ Tips and Tricks”, Available Online at: https://www.youtube.com/watch?v=sso0mYTfV6w, Mar. 22, 2018, pp. 1-33. |
| Final Office Action received for U.S. Appl. No. 16/389,722, mailed on Mar. 17, 2023, 14 pages. |
| Final Office Action received for U.S. Appl. No. 17/713,016, mailed on Mar. 15, 2023, 6 pages. |
| Gauging Gadgets, “How to Customize Watch Faces—Garmin Venu Tutorial”, Online Available at: https://www.youtube.com/watch?v=dxajKKulaP0, Jan. 7, 2020, 14 pages. |
| Intention to Grant received for European Patent Application No. 20761084.1, mailed on Mar. 27, 2023, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/943,737, mailed on Mar. 28, 2023, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,671, mailed on Mar. 17, 2023, 34 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,765, mailed on Mar. 28, 2023, 31 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/697,749, mailed on Mar. 27, 2023, 20 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-0123852, mailed on Mar. 9, 2023, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2022201419, mailed on Mar. 20, 2023, 3 pages. |
| Office Action received for Australian Patent Application No. 2022202583, mailed on Mar. 24, 2023, 4 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 17/746,807, mailed on Mar. 31, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/948,578, mailed on Apr. 11, 2023, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/515,143, mailed on Mar. 29, 2023, 2 pages. |
| Decision to Grant received for European Patent Application No. 21177569.7, mailed on Apr. 6, 2023, 3 pages. |
| Final Office Action received for U.S. Appl. No. 17/158,936, mailed on Apr. 7, 2023, 18 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/389,722, mailed on May 31, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,671, mailed on May 23, 2023, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/697,749, mailed on May 30, 2023, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/941,962, mailed on May 30, 2023, 2 pages. |
| Office Action received for Australian Patent Application No. 2022203957, mailed on May 12, 2023, 5 pages. |
| Office Action received for Korean Patent Application No. 10-2023-7011744, mailed on May 15, 2023, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
| Advisory Action received for U.S. Appl. No. 17/158,936, mailed on Jul. 24, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/676,034, mailed on Sep. 18, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/681,584, mailed on Jun. 6, 2023, 2 pages. |
| Decision to Grant received for European Patent Application No. 20761084.1, mailed on Jul. 27, 2023, 4 pages. |
| Decision to Grant received for European Patent Application No. 21169911.1, mailed on Jun. 29, 2023, 3 pages. |
| Extended European Search Report received for European Patent Application No. 23176305.3, mailed on Sep. 13, 2023, 8 pages. |
| Final Office Action received for U.S. Appl. No. 17/676,034, mailed on Jul. 24, 2023, 19 pages. |
| Final Office Action received for U.S. Appl. No. 17/697,749, mailed on Aug. 10, 2023, 8 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022287595, mailed on Aug. 29, 2023, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-137007, mailed on May 29, 2023, 5 pages (1 page of English Translation & 4 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2023-7011744, mailed on Sep. 4, 2023, 8 pages (2 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2022228204, mailed on Jul. 27, 2023, 5 pages. |
| Office Action received for Australian Patent Application No. 2022287595, mailed on Jul. 20, 2023, 3 pages. |
| Hoffman Chris, “5+ Cool Uses for Android's Daydream Mode”, Online Available at: https://www.howtogeek.com/170990/5-cool-uses-for-androids-daydream-mode/, Jul. 12, 2017, 8 pages. |
| Office Action received for Indian Patent Application No. 202118025048, mailed on Sep. 22, 2023, 8 pages. |
| Office Action received for Japanese Patent Application No. 2022-174879, mailed on Dec. 8, 2023, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/676,034, mailed on Oct. 31, 2023, 2 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2022/026371, mailed on Nov. 9, 2023, 11 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/697,749, mailed on Oct. 10, 2023, 5 pages. |
| Houben et al., “WatchConnect: A Toolkit for Prototyping Smartwatch-Centric Cross-Device Applications”, Proceedings of the 33rd Annual ACM Conference on Human Factors in Computing Systems, Online available at: https://dl.acm.org/doi/10.1145/2702123.2702215, 2015, pp. 1247-1256. |
| Non-Final Office Action received for U.S. Appl. No. 17/676,034, mailed on Oct. 11, 2023, 23 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/021409, mailed on Nov. 9, 2023, 23 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2023/021409, mailed on Sep. 19, 2023, 17 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/676,034, mailed on Nov. 17, 2023, 9 pages. |
| Office Action received for Chinese Patent Application No. 202210265746.X, mailed on Oct. 11, 2023, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
| Non-Final Office Action received for U.S. Appl. No. 17/681,584, mailed on Sep. 19, 2023, 16 pages. |
| Office Action received for Japanese Patent Application No. 2023-560221, mailed on Jun. 28, 2024, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| 103399661, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202210263607.3 on Oct. 23, 2023. |
| 105045079, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202210263607.3 on Oct. 23, 2023. |
| 105204620, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202210263607.3 on Oct. 23, 2023. |
| 105516824, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202210263607.3 on Oct. 23, 2023. |
| 2007-150831, JP, A, Cited by the Japanese Patent Office in an Office Action for related Patent Application No. 2024-067669 on Jul. 12, 2024. |
| 2011-166679, JP, A, Cited by the Japanese Patent Office in an Office Action for related Patent Application No. 2023-105300 on Oct. 4, 2024. |
| 2011-203707, JP, A, Cited by the Japanese Patent Office in an Office Action for related Patent Application No. 2024-067669 on Jul. 12, 2024. |
| 2016-120890, JP, A, Cited by the Japanese Patent Office in an Office Action for related Patent Application No. 2023-105300 on Oct. 4, 2024. |
| 10-2014-0120470, KR, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202210265746.X on Apr. 25, 2024. |
| 10-2015-0057307, KR, A, Cited by the Korean Patent Office in an Office Action for related Patent Application No. 10-2023-7040267 on Dec. 5, 2023. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/158,936, mailed on May 29, 2024, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/697,749, mailed on Feb. 22, 2024, 5 pages. |
| DRE SM, “Android 8 | How to use Picture in Picture (with YouTube)”, available online at: https://youtu.be/H4w4EdlzqEg?si=OZJm2exdqF27hDBC, Nov. 27, 2017, 8 pages. |
| Final Office Action received for U.S. Appl. No. 17/158,936, mailed on Aug. 19, 2024, 25 pages. |
| Gotta Be Mobile, “How to Use Picture-in-Picture Mode on Android 8.0 Oreo”, available online at: https://www.youtube.com/watch?v=305V9aP3BEs, Oct. 31, 2017, 1 page. |
| Gupta Information Systems in English, “Enable Picture in Picture Mode on Android Oreo 8.0 (See Updated Method in Description)”, available online at: https://www.youtube.com/watch?v=whcee_eSwtc, May 19, 2017, 1 page. |
| Knight, Jon, “Use the New Picture-in-Picture Mode in Android O”, Gadget Hacks, Retrieved from: https://android.gadgethacks.com/how-to/ use-new-picture-picture-mode-android-o-0178324/, Jun. 23, 2017, 6 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/158,936, mailed on Mar. 26, 2024, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/697,749, mailed on Dec. 4, 2023, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/543,837, mailed on Aug. 29, 2024, 11 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202210265746.X, mailed on Apr. 25, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2022-174879, mailed on Mar. 22, 2024, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2023-7040267, mailed on Dec. 5, 2023, 8 pages (2 pages of English Translation and 6 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 17/697,749, mailed on Apr. 10, 2024, 5 pages. |
| Notice of Hearing received for Indian Patent Application No. 202118025047, mailed on Mar. 14, 2024, 2 pages. |
| Office Action received for Australian Patent Application No. 2022228204, mailed on Feb. 15, 2024, 3 pages. |
| Office Action received for Australian Patent Application No. 2022228204, mailed on Jul. 3, 2024, 6 pages. |
| Office Action received for Chinese Patent Application No. 202210263607.3, mailed on Apr. 15, 2024, 12 pages (4 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202210263607.3, mailed on Oct. 23, 2023, 18 pages (7 pages of English Translation and 11 pages of Official Copy). |
| Office Action received for European Patent Application No. 17853656.1, mailed on Apr. 24, 2024, 7 pages. |
| Office Action received for European Patent Application No. 20180900.1, mailed on Dec. 21, 2023, 5 pages. |
| Office Action received for Indian Patent Application No. 202118025046, mailed on Mar. 18, 2024, 6 pages. |
| Office Action received for Japanese Patent Application No. 2023-105300, mailed on Oct. 4, 2024, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2024-067669, mailed on Jul. 12, 2024, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2024-7007452, mailed on Apr. 1, 2024, 17 pages (9 pages of English Translation and 8 pages of Official Copy). |
| Play video from youtube in picture-in-picture mode, available online at: https://stackoverflow.com/questions/54043791/play-video-from-youtube-in-picture-in-picture-mode, Jan. 4, 2019, 5 pages. |
| Result of Consultation received for European Patent Application No. 20180900.1, mailed on May 6, 2024, 7 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/676,034, mailed on Feb. 14, 2024, 4 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/676,034, mailed on Mar. 4, 2024, 10 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/697,749, mailed on Apr. 17, 2024, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/697,749, mailed on Jun. 14, 2024, 2 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20220342514 A1 | Oct 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 63180568 | Apr 2021 | US |
