Media control for screen saver programs on electronic devices

Abstract

Embodiments of the present disclosure relate to media control for screen savers on electronic devices. In some embodiments, an electronic device displays a screen saver on a display. In some embodiments, while displaying the screen saver, the electronic device receives input detected on a touch-sensitive surface of one or more input devices. In some embodiments, in response to the input, if the electronic device is in a music playback mode when the input is received, and if the input is a tap input at a first region of a plurality of regions of the touch-sensitive surface, the electronic device displays, on the display, a representation of music playing in response to the input overlaid on the screen saver. In some embodiments, in response to the input, if the input is a tap input at a second region of the plurality of regions of the touch-sensitive surface, the electronic device ceases to display the screen saver.

Description

[0001] This application is a divisional application of the invention patent application filed on May 3, 2019, with Chinese national application number 201980037597.8 and the invention title "Media Control for Screen Saver Programs on Electronic Devices". Technical Field

[0002] This disclosure relates in its entirety to electronic devices that allow browsing and playback of content and screensavers, and to user interaction with such devices. Background Technology

[0003] In recent years, user interaction with electronic devices has increased significantly. These devices can include computers, tablets, televisions, multimedia devices, mobile devices, and so on.

[0004] In some situations, when a device starts displaying a screensaver, or while a screensaver is being displayed, a user may be playing media such as music on the device, and the user's interaction with such a device requires controlling music playback and the display of the screensaver without exiting the screensaver. Enhancing these interactions improves the user experience and reduces user interaction time, which is especially important when the input device is battery-powered. Summary of the Invention

[0005] Some embodiments described in this disclosure relate to one or more electronic devices that facilitate music playback and screen saver control when a screen saver is displayed, and one or more operations optionally performed by the electronic device in relation to the foregoing. A full description of the embodiments is provided in the accompanying drawings and detailed description; it should be understood that the above-described summary of the invention does not limit the scope of this disclosure in any way. Attached Figure Description

[0006] To better understand the various embodiments described, reference should be made to the following detailed description in conjunction with the accompanying drawings, in which similar reference numerals indicate corresponding parts throughout the drawings.

[0007] Figure 1A This is a block diagram illustrating a multifunctional device with a touch-sensitive display according to some embodiments of the present disclosure.

[0008] Figure 1B This is a block diagram illustrating exemplary components for event handling according to some embodiments of the present disclosure.

[0009] Figure 2 A multifunctional device with a touch screen is shown according to some embodiments of the present disclosure.

[0010] Figure 3This is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface according to some embodiments of this disclosure.

[0011] Figure 4 An exemplary user interface for a multifunctional device having a touch-sensitive surface separate from the display is shown according to some embodiments of the present disclosure.

[0012] Figures 5A to 5B A block diagram of an exemplary architecture for a device according to some embodiments of the present disclosure is shown.

[0013] Figures 6A to 6DD Exemplary ways in which electronic devices facilitate music playback and screen saver control while displaying a screen saver are shown, according to some embodiments of the present disclosure.

[0014] Figures 7A to 7Q This is a flowchart illustrating a method for facilitating music playback and screen saver control when displaying a screen saver, according to some embodiments of the present disclosure. Detailed Implementation

[0015] The accompanying drawings, which form part of the following description of the embodiments and illustrate specific embodiments of alternative implementations by way of example, will be referenced in the description of the embodiments below. It should be understood that other embodiments and structural changes may be optionally used without departing from the scope of the disclosed embodiments. Furthermore, although the terms “first,” “second,” etc., are used in the following description 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 may be named a second touch and similarly, a second touch may be named a first touch, without departing from the scope of the various described embodiments. Both the first touch and the second touch are touches, but they are not the same touch.

[0016] The terminology used in the description of the various 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 embodiments and the appended claims, the singular forms “a” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and / or” as used herein refers to and covers any and all possible combinations of one or more of the associated listed items. It will also be understood that the terms “includes”, “including”, “comprises”, and / or “comprising”, when used in this specification, specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0017] Depending on the context, the term "if" may optionally be interpreted as meaning "when," "in response to," or "in response to detection." Similarly, depending on the context, the phrases "if it is determined..." or "if [the stated condition or event] is detected" may optionally be interpreted as meaning "in response to determining..." or "in response to detecting [the stated condition or event]."

[0018] Exemplary device

[0019] This document describes implementations of electronic devices, user interfaces for such devices, and related processes for using such devices. In some implementations, the device is a portable communication device, such as a mobile phone, that also includes other functions such as PDA and / or music player functionality. Exemplary implementations of portable multi-functional devices include, but are not limited to, those from Apple Inc. (Cupertino, California). equipment, Equipment, and Device. Optionally, other portable electronic devices may be used, such as laptops or tablets with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer or television with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). In some embodiments, the device does not have a touchscreen display and / or touchpad, but is capable of outputting display information (such as the user interface of this disclosure) for display on a separate display device, and is capable of receiving input information from a separate input device having one or more input mechanisms (such as one or more buttons, touchscreen displays, and / or touchpads). In some embodiments, the device has a display, but is capable of receiving input information from a separate input device having one or more input mechanisms (such as one or more buttons, touchscreen displays, and / or touchpads).

[0020] In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it should be understood that the electronic device optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse, and / or joystick. Additionally, as mentioned above, it should be understood that the described electronic device, display, and touch-sensitive surface are optionally distributed across two or more devices. Therefore, as used in this disclosure, information on or displayed by the electronic device is optionally used to describe information output by the electronic device for display on a separate display device (touch-sensitive or non-touch-sensitive). Similarly, as used in this disclosure, input received on the electronic device (e.g., touch input received on a touch-sensitive surface of the electronic device) is optionally used to describe input received on a separate input device from which the electronic device receives input information.

[0021] The device typically supports a variety of applications, such as one or more of the following: drawing applications, rendering applications, word processing applications, website creation applications, disk editing applications, spreadsheet applications, game applications, phone applications, video conferencing applications, email applications, instant messaging applications, fitness support applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music player applications, TV channel browsing applications, and / or digital video player applications.

[0022] Various applications running on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and the corresponding information displayed on the device are optionally adjusted and / or varied for different applications, and / or adjusted and / or varied within the respective applications. In this way, the device's common physical architecture (such as the touch-sensitive surface) optionally utilizes a user interface that is intuitive and clear to the user to support various applications.

[0023] Now let’s turn our attention to implementations of portable or non-portable devices with touch-sensitive displays, but the device does not necessarily include a touch-sensitive display or a general display, as described above. Figure 1A This is a block diagram illustrating a portable or non-portable multi-functional device 100 with a touch-sensitive display 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a “touchscreen” for convenience, and is sometimes referred to as a touch-sensitive display system. Device 100 includes a memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input or control devices 116, and an external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact strength sensors 165 for detecting the intensity of contact on device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more haptic output generators 167 for generating haptic output on device 100 (e.g., generating haptic output on a touch-sensitive surface such as the touch-sensitive display system 112 of device 100 or the touchpad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0024] As used in this specification and claims, the term "intensity" of contact on a tactile surface refers to the force or pressure (force per unit area) of a contact (e.g., finger contact) on a tactile surface, or to a substitute (alternative) for the force or pressure of a contact on a tactile surface. The intensity of contact has a range of values ​​that includes at least four different values ​​and more typically hundreds of different values ​​(e.g., at least 256). The intensity of contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the tactile surface are optionally used to measure the force at different points on the tactile surface. In some embodiments, force measurements from multiple force sensors are combined (e.g., weighted average) to determine the estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the tactile surface. Alternatively, the size and / or variation of the contact area detected on the touch-sensitive surface, the capacitance and / or variation of the touch-sensitive surface near the contact, and / or the resistance and / or variation of the touch-sensitive surface near the contact may optionally be used as substitutes for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether an intensity threshold (e.g., the intensity threshold is described in units corresponding to the substitute measurement) has been exceeded. In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold (e.g., the intensity threshold is a pressure threshold measured in pressure units) has been exceeded. Using the intensity of the contact as an attribute of user input allows the user to access additional device functions that would otherwise be inaccessible to the user on a smaller device with limited physical space, which is used (e.g., on a touch-sensitive display) to display an indication and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons).

[0025] As used in this specification and claims, the term "haptic output" refers to a physical displacement of the device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., the housing), or a displacement of a component relative to the center of mass of the device, which is detected by the user using the user's tactile sense. For example, when the device or a component of the device comes into contact with a touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical characteristics of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or touchpad) may optionally be interpreted by the user as a "press-click" or "release-click" on a physically actuated button. In some cases, the user will feel a tactile sensation, such as a "press-click" or "release-click," even when a physically actuated button associated with a touch-sensitive surface that has been physically pressed (e.g., displaced) by the user's movement does not move. For example, even when the smoothness of the tactile surface remains unchanged, the movement of the tactile surface can optionally be interpreted or sensed by the user as the "roughness" of the tactile surface. While such interpretations of touch by users will be limited by the individualized sensory perceptions of the user, many sensory perceptions of touch are common to most users. Therefore, when a tactile output is described as corresponding to a specific sensory perception of a user (e.g., "press click", "release click", "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or its components that will generate the sensory perception of a typical (or ordinary) user.

[0026] It should be understood that device 100 is merely an example of a portable or non-portable multifunctional device, and device 100 may optionally have more or fewer components than shown, may optionally combine two or more components, or may optionally have different configurations or arrangements of these components. Figure 1A The various components shown are implemented in hardware, software, or a combination of both, including one or more signal processing and / or application-specific integrated circuits (ASICs). Furthermore, Figure 1A The various components shown are optionally implemented on two or more devices; for example, a display and audio circuitry on a display device, a touch-sensitive surface on an input device, and other components on device 100. In such embodiments, device 100 optionally communicates with the display device and / or input device to facilitate system operation as described herein, and the various components relating to display and / or input described herein are retained in device 100 or optionally included in the display and / or input device where appropriate.

[0027] Memory 102 optionally includes high-speed random access memory and also optionally includes non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 optionally controls other components of device 100 to access memory 102.

[0028] Peripheral interface 118 can be used to couple the device's input peripherals and output peripherals to CPU 120 and memory 102. One or more processors 120 run or execute various software programs and / or instruction sets stored in memory 102 to perform various functions of device 100 and process data.

[0029] In some implementations, the peripheral interface 118, CPU 120, and memory controller 122 are optionally implemented on a single chip, such as chip 104. In other implementations, they are optionally implemented on separate chips.

[0030] RF (Radio Frequency) circuit 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuit 108 converts electrical signals into electromagnetic signals and vice versa, and communicates with communication networks and other communication devices via these electromagnetic signals. RF circuit 108 optionally includes well-known circuitry for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, Subscriber Identity Module (SIM) cards, memory, etc. RF circuit 108 optionally communicates with networks and other devices wirelessly, such as the Internet (also known as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuit 108 optionally includes well-known circuitry for detecting near-field communication (NFC) fields, such as through near-field communication radio components. Wireless communication may optionally employ any of a variety of communication 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-Unit 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), and 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, email protocols (e.g., Internet Messaging 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 Utilizing Extended Protocol (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol including those not yet developed at the date of this document submission.

[0031] Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between the user and device 100. Audio circuitry 110 receives audio data from peripheral interface 118, converts the audio data into electrical signals, and transmits the electrical signals to speaker 111. Speaker 111 converts the electrical signals into sound waves that are audible to humans. Audio circuitry 110 also receives electrical signals converted from sound waves by microphone 113. Audio circuitry 110 converts the electrical signals into audio data and transmits the audio data to peripheral interface 118 for processing. Audio data is optionally retrieved by peripheral interface 118 from and / or transmitted to memory 102 and / or RF circuitry 108. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., ...). Figure 2 (212 in the text). The headset jack provides an interface between the audio circuitry 110 and a removable audio input / output peripheral device, such as an output-only headphone or a headset with both output (e.g., a mono or binaural headphone) and input (e.g., a microphone).

[0032] I / O subsystem 106 couples input / output peripherals on device 100, such as touchscreen 112 and other input control devices 116, to peripheral interface 118. I / O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. One or more input controllers 160 receive electrical signals from / send electrical signals to other input or control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push-buttons, rocker buttons, etc.), dial pads, slide switches, joysticks, click dials, etc. In some alternative embodiments, one or more input controllers 160 are optionally coupled to (or not coupled to) any of the following: keyboard, infrared port, USB port, and pointing devices such as a mouse. One or more buttons (e.g., ... Figure 2 Optionally, 208) includes an increase / decrease button for volume control of speaker 111 and / or microphone 113. One or more buttons optionally include a push-button (e.g., Figure 2 (206 in the middle).

[0033] A quick press of the push button optionally disengages the touchscreen 112 from its lock or optionally initiates a process of unlocking the device using gestures on the touchscreen, as described in U.S. Patent Application 11 / 322,549 (i.e., U.S. Patent No. 7,657,849), filed December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," the entire contents of which are incorporated herein by reference. A long press of the push button (e.g., 206) optionally powers the device 100 on or off. The function of one or more buttons is optionally user-customizable. The touchscreen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

[0034] The touch-sensitive display 112 provides input and output interfaces between the device and the user. As described above, the touch-sensitive operation and display operation of the touch-sensitive display 112 are optionally separated from each other, such that the display device is used for display purposes, while the touch-sensitive surface (whether or not a display) is used for input detection purposes, and the described components and functions are modified accordingly. However, for the sake of brevity, the following description refers to the touch-sensitive display. The display controller 156 receives electrical signals from the touchscreen 112 and / or sends electrical signals to the touchscreen. The touchscreen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively, "graphics"). In some embodiments, some or all of the visual output corresponds to user interface objects.

[0035] Touchscreen 112 has a touch-sensitive surface, sensor, or sensor array that accepts input from a user based on tactile and / or haptic contact. Touchscreen 112 and display controller 156 (along with any associated modules and / or instruction set in memory 102) detect contact on touchscreen 112 (and any movement or interruption of that contact) and translate the detected contact into interaction with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on touchscreen 112. In an exemplary embodiment, the contact point between touchscreen 112 and the user corresponds to the user's finger.

[0036] Touchscreen 112 optionally employs LCD (Liquid Crystal Display) technology, LPD (Light Emitting Polymer Display) technology, or LED (Light Emitting Diode) technology, but other display technologies are used in other embodiments. Touchscreen 112 and display controller 156 optionally employ any of a variety of touch sensing technologies now known or to be developed hereafter, along with other proximity sensor arrays or other elements for determining one or more points of contact with touchscreen 112, to detect contact and any movement or interruption therein. These various touch sensing technologies include, but are not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies. In one exemplary embodiment, projected mutual capacitance sensing technology, such as that from Apple Inc. (Cupertino, California), is used. iPod and The technology that was discovered.

[0037] In some embodiments of the touchscreen 112, the touch-sensitive display optionally resembles the multi-touch-sensitive touchpad described in the following U.S. patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman et al.) and / or U.S. Patent Publication 2002 / 0015024A1, each of which is incorporated herein by reference in its entirety. However, the touchscreen 112 displays visual output from the device 100, while the touch-sensitive touchpad does not provide visual output.

[0038] In some embodiments, the touchscreen 112 has a touch-sensitive display as described in the following patent applications: (1) U.S. Patent Application No. 11 / 381,313, filed May 2, 2006, entitled “Multipoint Touch Surface Controller”; (2) U.S. Patent Application No. 10 / 840,862, filed May 6, 2004, entitled “Multipoint Touchscreen”; (3) U.S. Patent Application No. 10 / 903,964, filed July 30, 2004, entitled “Gestures For Touch Sensitive Input Devices”; (4) U.S. Patent Application No. 11 / 048,264, filed January 31, 2005, entitled “Gestures For Touch Sensitive Input Devices”; and (5) U.S. Patent Application No. 18, 2005, entitled “Mode-Based Graphical User Interfaces For Touch Sensitive”. (6) U.S. Patent Application No. 11 / 038,590 entitled “Input Devices”; (7) U.S. Patent Application No. 11 / 228,758 entitled “Virtual Input Device Placement On A Touch Screen User Interface”, filed September 16, 2005; (8) U.S. Patent Application No. 11 / 228,700 entitled “Operation Of A Computer With A Touch Screen Interface”, filed September 16, 2005; (9) U.S. Patent Application No. 11 / 228,737 entitled “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard”, filed September 16, 2005; and (10) U.S. Patent Application No. 11 / 367,749 entitled “Multi-Functional Hand-Held Device”, filed March 3, 2006. The full text of all these applications is incorporated herein by reference.

[0039] Touchscreen 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. Users optionally interact with touchscreen 112 using any suitable object or accessory such as a stylus, finger, etc. In some embodiments, the user interface is designed to operate primarily through finger-based touch and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​a finger on the touchscreen. In some embodiments, the device translates coarse finger-based input into precise pointer / cursor positions or commands to perform the user-desired actions.

[0040] In some embodiments, in addition to the touchscreen, device 100 optionally includes a touchpad (not shown) for activating or deactivating specific functions. In some embodiments, the touchpad is a touch-sensitive area of ​​the device that, unlike the touchscreen, does not display visual output. The touchpad is optionally a touch-sensitive surface separate from the touchscreen 112, or an extension of the touch-sensitive surface formed by the touchscreen.

[0041] The device 100 also includes a power system 162 for supplying power to various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, a power fault detection circuit, a power converter or inverter, a power status indicator (e.g., light-emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power in portable or non-portable devices.

[0042] The device 100 may optionally also include one or more optical sensors 164. Figure 1AAn optical sensor 164 is shown coupled to an optical sensor controller 158 in the I / O subsystem 106. The optical sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with an imaging module 143 (also called a camera module), the optical sensor 164 optionally captures still images or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite to a touchscreen display 112 on the front of the device, allowing the touchscreen display to be used as a viewfinder for still image and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device, allowing images of the user to be optionally acquired for video conferencing while the user views other video conferencing participants on the touchscreen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lenses and sensor within the device housing), allowing a single optical sensor 164 to be used in conjunction with the touchscreen display for both video conferencing and still image and / or video image acquisition.

[0043] The device 100 may optionally also include one or more contact strength sensors 165. Figure 1A A contact strength sensor 165 is shown coupled to a strength sensor controller 159 in the I / O subsystem 106. The contact strength sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electro-force sensors, piezoelectric sensors, optical force sensors, capacitive touch-sensitive surfaces, or other strength sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). The contact strength sensor 165 receives contact strength information (e.g., pressure information or a substitute for pressure information) from the environment. In some embodiments, at least one contact strength sensor is arranged juxtaposed with or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact strength sensor is located on the rear of device 100, opposite to the touchscreen display 112 located on the front of device 100.

[0044] The device 100 optionally also includes one or more proximity sensors 166. Figure 1AA proximity sensor 166 coupled to a peripheral device interface 118 is shown. Alternatively, the proximity sensor 166 may optionally be coupled to an input controller 160 in an I / O subsystem 106. The proximity sensor 166 may optionally perform as described in the following U.S. patent applications: No. 11 / 241,839, entitled "Proximity Detector In Handheld Device"; No. 11 / 240,788, entitled "Proximity Detector In Handheld Device"; No. 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; No. 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and No. 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", the entire contents of which are incorporated herein by reference. In some implementations, the proximity sensor is turned off and the touchscreen 112 is disabled when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

[0045] The device 100 may optionally also include one or more tactile output generators 167. Figure 1AA haptic output generator coupled to a haptic feedback controller 161 in I / O subsystem 106 is shown. The haptic output generator 167 optionally includes one or more electroacoustic devices, such as speakers or other audio components; and / or electromechanical devices that convert energy into linear motion, such as motors, solenoids, electroactive polymerizers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components that convert electrical signals into haptic outputs on the device). A contact intensity sensor 165 receives haptic feedback generation instructions from a haptic feedback module 133 and generates a haptic output on device 100 that can be felt by a user of device 100. In some embodiments, at least one haptic output generator is juxtaposed or adjacent to a haptic surface (e.g., a haptic display system 112) and optionally generates the haptic output by moving the haptic surface vertically (e.g., in / outward from the surface of device 100) or laterally (e.g., backward and forward in the same plane as the surface of device 100). In some embodiments, at least one haptic output generator sensor is located on the rear of the device 100, opposite to the touch screen display 112 located on the front of the device 100.

[0046] The device 100 may optionally also include one or more accelerometers 168. Figure 1A An accelerometer 168 is shown coupled to a peripheral device interface 118. Alternatively, the accelerometer 168 may optionally be coupled to an input controller 160 in an I / O subsystem 106. The accelerometer 168 may optionally perform as described in the following U.S. patent publications: U.S. Patent Publication No. 20050190059, entitled "Acceleration-based Theft Detection System for Portable Electronic Devices" and U.S. Patent Publication No. 20060017692, entitled "Methods and Apparatuses For Operating A Portable Device Based On An Accelerometer," both of which are incorporated herein by reference in their entirety. In some embodiments, information is displayed on a touchscreen display in portrait or landscape view based on analysis of data received from one or more accelerometers. In addition to the accelerometer 168, the device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information about the position and orientation (e.g., longitudinal or lateral) of the device 100.

[0047] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and an application program (or instruction set) 136. Furthermore, in some embodiments, memory 102 ( Figure 1A ) or 370 ( Figure 3 Storage device / global internal state 157, such as Figure 1A and Figure 3 As shown in the diagram. Device / global internal state 157 includes one or more of the following: active application state, which indicates which applications (if any) are currently active; display state, which indicates what applications, views or other information occupy various areas of the touchscreen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and positional information about the device's position and / or orientation.

[0048] The operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or embedded operating systems 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.

[0049] The communication module 128 facilitates communication with other devices via one or more external ports 124 and includes various software components for processing data received by the RF circuitry 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are adapted to be directly coupled to other devices or indirectly coupled via 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 (Apple Inc. trademark) devices.

[0050] The contact / motion module 130 optionally detects contact with the touchscreen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., touchpads or physical click-based rotary dials). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether a contact has occurred (e.g., detecting a finger press event), determining the contact intensity (e.g., the force or pressure of the contact, or an alternative to force or pressure), determining whether there is movement of the contact and tracking movement on the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger lift event or contact disconnection). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of which is represented by a series of contact data. These operations are optionally applied to single-point contact (e.g., single-finger contact) or multi-point simultaneous contact (e.g., "multi-touch" / multiple-finger contact). In some implementations, the contact / motion module 130 and the display controller 156 detect contact on the touchpad.

[0051] In some implementations, the 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., determining whether the user has “clicked” an icon). In some implementations, at least one subset of intensity thresholds is determined based on software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a specific physical actuator and can be adjusted without changing the physical hardware of device 100). For example, the mouse “click” threshold of a touchpad or touchscreen can be set to any threshold in a wide range of predefined thresholds without changing the touchpad or touchscreen display hardware. Additionally, in some implementations, the user of the device is provided with software settings for adjusting one or more intensity thresholds in a set (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once using system-level clicks on the “intensity” parameter).

[0052] The touch / motion module 130 optionally detects the user's gesture input. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timings, and / or intensities of the detected contact). Therefore, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture includes detecting a finger press event, and then detecting a finger lift-off (lift-away) event at the same (or substantially the same) location as the finger press event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on a touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and subsequently detecting a finger lift-off (lift-away) event.

[0053] The graphics module 132 includes various known software components for rendering and displaying graphics on the touchscreen 112 or other displays, including components for altering the visual impact of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual properties). As used herein, the term "graphics" includes any object that can be displayed to a user, and non-limitingly includes text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

[0054] In some implementations, the graphics module 132 stores data representing the graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes from an application or the like to specify the graphic to be displayed, and, if necessary, also receives coordinate data and other graphic attribute data, and then generates screen image data for output to the display controller 156.

[0055] The haptic feedback module 133 includes various software components for generating instructions that are used by the haptic output generator 167 to produce haptic output at one or more locations on the device 100 in response to user interaction with the device 100.

[0056] Optionally, the text input module 134, a component of the graphics module 132, provides a soft keyboard for entering text in various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other application that requires text input).

[0057] GPS module 135 determines the location of the device and provides that information for use in various applications (e.g., to phone 138 for location-based dialing; to camera 143 as image / video metadata; and to applications that provide location-based services such as weather desktop apps, local yellow pages desktop apps, and map / navigation desktop apps).

[0058] Application 136 optionally includes the following modules (or instruction sets) or subsets or supersets thereof:

[0059] • Contacts module 137 (sometimes called address book or contact list);

[0060] • Telephone module 138;

[0061] • Video conferencing module 139;

[0062] • Email client module 140;

[0063] • Instant Messaging (IM) module 141;

[0064] Fitness support module 142;

[0065] • Camera module 143 for still images and / or video images;

[0066] • Image management module 144;

[0067] • Video player module;

[0068] Music player module;

[0069] • Browser module 147;

[0070] • Calendar module 148;

[0071] • Desktop mini-program module 149, which optionally includes one or more of the following: weather desktop mini-program 149-1, stock market desktop mini-program 149-2, calculator desktop mini-program 149-3, alarm clock desktop mini-program 149-4, dictionary desktop mini-program 149-5, and other desktop mini-programs obtained by the user, and desktop mini-programs created by the user 149-6;

[0072] • Desktop app creator module 150 for creating user-created desktop apps 149-6;

[0073] • Search module 151;

[0074] • Video and music player module 152, which combines a video player module and a music player module;

[0075] • Memo module 153;

[0076] • Map module 154; and / or

[0077] • Online video module 155.

[0078] Examples of other applications 136 that may be optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, rendering applications, Java-enabled applications, encryption, digital rights management, speech recognition, and speech duplication.

[0079] In conjunction with the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the contact module 137 is optionally used to manage an address book or contact list (e.g., in the application internal state 192 of the contact module 137 stored in memory 102 or memory 370), including: adding one or more names to the address book; deleting names from the address book; associating phone numbers, email addresses, physical addresses, or other information with names; associating images with names; categorizing and classifying names; providing phone numbers or email addresses to initiate and / or facilitate communications via telephone 138, video conferencing module 139, email 140, or IM 141; and so on.

[0080] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, telephone module 138 is optionally used to input character sequences corresponding to telephone numbers, access one or more telephone numbers in contact module 137, modify entered telephone numbers, dial corresponding telephone numbers, initiate conversations, and disconnect or hang up when a conversation is completed. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

[0081] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contact module 137, and telephone module 138, video conferencing module 139 includes executable instructions to initiate, conduct, and terminate video conferences between the user and one or more other participants based on user instructions.

[0082] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to user commands. Combined with image management module 144, email client module 140 makes it very easy to create and send emails containing still images or video images captured by camera module 143.

[0083] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for: inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocols for telephone-based instant messaging or using XMPP, SIMPLE, or IMPS for internet-based instant messaging), receiving an instant message, and viewing a received instant message. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photographs, audio files, video files, and / or other attachments supported in MMS and / or Enhanced Messaging Services (EMS). As used herein, "instant message" refers to both telephone-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0084] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, fitness support module 142 includes executable instructions for creating fitness activities (e.g., with time, distance, and / or calorie burning goals); communicating with fitness sensors (executive devices); receiving fitness sensor data; calibrating sensors used to monitor fitness; selecting and playing music for fitness activities; and displaying, storing, and transmitting fitness data.

[0085] In conjunction with the touchscreen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132, and image management module 144, the camera module 143 includes executable instructions for: capturing still images or videos (including video streams) and storing them in memory 102, modifying the characteristics of still images or videos, or deleting still images or videos from memory 102.

[0086] Incorporating the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and camera module 143, the image management module 144 includes executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, tagging, deleting, presenting (e.g., in a digital slideshow or album), and storing still images and / or video images.

[0087] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions for browsing the Internet according to user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as links to attachments and other files on web pages.

[0088] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and associated data (e.g., calendar entries, to-dos, etc.) according to user instructions.

[0089] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, desktop applet module 149 is optionally a micro-application downloaded and used by a user (e.g., weather desktop applet 149-1, stock market desktop applet 149-2, calculator desktop applet 149-3, alarm clock desktop applet 149-4, and dictionary desktop applet 149-5) or a user-created micro-application (e.g., user-created desktop applet 149-6). In some embodiments, the desktop applet includes HTML (Hypertext Markup Language) files, CSS (Cascading Style Sheets) files, and JavaScript files. In some embodiments, the desktop applet includes XML (Extensible Markup Language) files and JavaScript files (e.g., Yahoo! desktop applet).

[0090] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, the desktop applet creator module 150 can optionally be used by the user to create desktop applets (e.g., converting user-specified portions of a webpage into desktop applets).

[0091] In conjunction with the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the search module 151 includes executable instructions for searching the memory 102 for text, music, sound, images, videos, and / or other files that match one or more search criteria (e.g., one or more user-specified search terms) according to user instructions.

[0092] Incorporating touchscreen 112, display controller 156, touch / 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 allowing users to download and play recorded music and other sound files stored in one or more file formats such as MP3 or AAC files, as well as executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touchscreen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player such as an iPod (a trademark of Apple Inc.).

[0093] Combining the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the memo module 153 includes executable instructions for creating and managing memos, to-do items, etc., according to user instructions.

[0094] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 is optionally used to receive, display, modify, and store maps and map-related data (e.g., driving directions, data related to shops and other points of interest at or near a specific location, and other location-based data) according to user instructions.

[0095] Incorporating touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, the online video module 155 includes instructions for performing the following actions: allowing users to access, browse, receive (e.g., via streaming and / or downloading), play back (e.g., on the touchscreen or on an external display connected via external port 124), send emails with links to specific online videos, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, an instant messaging module 141 is used instead of the email client module 140 to send links to specific online videos. Further descriptions of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are incorporated herein by reference in their entirety.

[0096] Each of the modules and applications described above corresponds to an executable instruction set for performing one or more of the functions described above and the methods described in this patent application (e.g., computer-implemented methods and other information processing methods as described herein). These modules (e.g., instruction sets) need not be implemented as separate software programs, processes, or modules; therefore, various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. For example, a video player module may optionally be combined with a music player module into a single module (e.g., Figure 1A (e.g., video and music player module 152). In some embodiments, memory 102 optionally stores a subset of the above-described modules and data structures. Additionally, memory 102 optionally stores other modules and data structures not described above.

[0097] In some implementations, device 100 is a device on which the operation of a predefined set of functions is performed solely via a touchscreen and / or touchpad. By using a touchscreen and / or touchpad as the primary input control device for operating device 100, the number of physical input control devices (e.g., push-buttons, dials, etc.) on device 100 can be optionally reduced.

[0098] A predefined set of functions, uniquely performed via a touchscreen and / or touchpad, optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 from any user interface displayed on device 100 to a main menu, home menu, or root menu. In such embodiments, a touchpad is used to implement a "menu button." In some other embodiments, the menu button is a physical push-button or other physical input control device, rather than a touchpad.

[0099] Figure 1B This is a block diagram illustrating exemplary components for event processing according to some embodiments. In some embodiments, memory 102 ( Figure 1A ) or memory 370 ( Figure 3 This includes an event classifier 170 (e.g., in operating system 126) and a corresponding application 136-1 (e.g., any one of the aforementioned applications 137-151, 155, 380-390).

[0100] Event classifier 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which the event information should be delivered. Event classifier 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates one or more current application views 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 classifier 170 to determine which application(s) is currently active, and application internal state 192 is used by event classifier 170 to determine the application view 191 to which the event information should be delivered.

[0101] In some implementations, the application internal state 192 includes additional information such as one or more of the following: recovery information to be used when the application 136-1 resumes execution, user interface state information indicating that information is being displayed or ready to be displayed by the application 136-1, a state queue for enabling the user to return to the previous state or view of the application 136-1, and a repeat / undo queue for the user's previous actions.

[0102] Event monitor 171 receives event information from peripheral device interface 118. The event information includes information about sub-events (e.g., user touches on touch-sensitive display 112 as part of a multi-touch gesture). Peripheral device interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, one or more accelerometers 168, and / or microphone 113 (via audio circuitry 110). The information received by peripheral device interface 118 from I / O subsystem 106 includes information from touch-sensitive display 112 or touch-sensitive surfaces.

[0103] In some implementations, event monitor 171 sends requests to peripheral device interface 118 at predetermined intervals. In response, peripheral device interface 118 transmits event information. In other implementations, peripheral device interface 118 transmits event information only when a significant event occurs (e.g., receiving input above a predetermined noise threshold and / or receiving input for a predetermined duration).

[0104] In some implementations, the event classifier 170 also includes a hit view determination module 172 and / or an activity event recognizer determination module 173.

[0105] When the touch-sensitive display 112 displays more than one view, the hit view determination module 172 provides a software process for determining where a sub-event has occurred within one or more views. A view consists of controls and other elements that the user can see on the display.

[0106] Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the corresponding application) in which a touch is detected optionally corresponds to a procedural level within the application's procedural or view hierarchy. For example, the lowest-level view in which a touch is detected is optionally referred to as the hit view, and the set of events identified as correct input is optionally determined at least in part based on the hit view of the initial touch that initiates a touch-based gesture.

[0107] The hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchical structure, the hit view determination module 172 identifies the hit view as the lowest-level view in the hierarchical structure from which the sub-events should be processed. In most cases, the hit view is the lowest-level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events forming an event or potential event) occurs. 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 to which it was identified as the hit view.

[0108] The activity event recognizer determination module 173 determines which views(s) within the view hierarchy should receive a specific sub-event sequence. In some embodiments, the activity event recognizer determination module 173 determines that only the hit view should receive the specific sub-event sequence. In other embodiments, the activity event recognizer determination module 173 determines that all views including the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive the specific sub-event sequence. In other embodiments, even if the touch sub-event is entirely confined to the area associated with a particular view, higher views in the hierarchy will still remain actively participating views.

[0109] Event assigner module 174 assigns event information to event identifiers (e.g., event identifier 180). In embodiments that include active event identifier determination module 173, event assigner module 174 delivers event information to the event identifier determined by active event identifier determination module 173. In some embodiments, event assigner module 174 stores event information in an event queue, which is retrieved by the corresponding event receiver 182.

[0110] In some embodiments, operating system 126 includes event classifier 170. Alternatively, application 136-1 includes event classifier 170. In yet another embodiment, event classifier 170 is a standalone module or part of another module (such as contact / motion module 130) stored in memory 102.

[0111] 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 occurring within a corresponding view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a corresponding application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of the event recognizers 180 are part of a separate module, such as a user interface toolkit (not shown) or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, a corresponding event handler 190 includes one or more of the following: a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from an event classifier 170. Event handlers 190 optionally utilize or invoke the data updater 176, the object updater 177, or the GUI updater 178 to update the application's internal state 192. Alternatively, one or more application views in application view 191 include one or more corresponding event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in the corresponding application view 191.

[0112] The corresponding event recognizer 180 receives event information (e.g., event data 179) from the event classifier 170 and identifies events from the event information. The event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, the event recognizer 180 also includes at least one subset of metadata 183 and event delivery instructions 188 (which optionally include sub-event delivery instructions).

[0113] Event receiver 182 receives event information from event classifier 170. The event information includes information about sub-events, such as touch or touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves touch movement, the event information optionally also includes the rate and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another (e.g., from a longitudinal orientation to a lateral orientation, or vice versa), and the event information includes corresponding information about the device's current orientation (also referred to as device pose).

[0114] Event comparator 184 compares event information with predefined event or sub-event definitions and determines the event or sub-event based on the comparison, or determines or updates the state of the event or sub-event. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 contains definitions of events (e.g., predefined sequences of sub-events), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in event (187) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, event 1 (187-1) is defined as a double-click on a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on the displayed object, a first lift-off of a predetermined duration (touch end), a second touch (touch start) of a predetermined duration on the displayed object, and a second lift-off of a predetermined duration (touch end). In another example, event 2 (187-2) is defined as a drag on a displayed object. For example, dragging includes a touch (or contact) on the displayed object for a predetermined duration, movement of the touch on the touch-sensitive display 112, and lifting off the touch (end of touch). In some embodiments, the event also includes information for one or more associated event handlers 190.

[0115] In some implementations, event definition 187 includes definitions of events for corresponding user interface objects. In some implementations, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, in an application view displaying three user interface objects 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 corresponding 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 the event handler associated with the sub-event and the object that triggered the hit test.

[0116] In some implementations, the definition of the corresponding event (187) also includes a delay action that delays the delivery of event information until it has been determined whether the sub-event sequence actually corresponds to or does not correspond to the event type of the event recognizer.

[0117] When the corresponding event recognizer 180 determines that the sub-event sequence does not match any event in event definition 186, the corresponding event recognizer 180 enters an event impossible, event failed, or event ended state, after which subsequent sub-events based on touch gestures are ignored. In this case, other event recognizers (if any) that remain active in the hit view continue to track and process the ongoing sub-events based on touch gestures.

[0118] In some embodiments, the corresponding event recognizer 180 includes metadata 183 having configurable attributes, flags, and / or lists instructing how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, the metadata 183 includes configurable attributes, flags, and / or lists instructing how or how event recognizers can interact with each other. In some embodiments, the metadata 183 includes configurable attributes, flags, and / or lists instructing whether sub-events are delivered to different levels in a view or programmatic hierarchy.

[0119] In some implementations, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates the event handler 190 associated with the event. In some implementations, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and delaying) the sub-event to the corresponding hit view. In some implementations, the event recognizer 180 throws a tag associated with the identified event, and the event handler 190 associated with that tag receives the tag and executes a predefined procedure.

[0120] In some implementations, event delivery instruction 188 includes a sub-event delivery instruction that delivers event information about a sub-event without activating an event handler. Instead, the sub-event delivery instruction delivers the event information to an event handler associated with the sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or the actively participating view receives the event information and performs a predetermined procedure.

[0121] In some implementations, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates phone numbers used in contact module 137 or stores video files used in video player module. In some implementations, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates new user interface objects or updates the location of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends the display information to graphics module 132 for display on touch-sensitive display.

[0122] In some implementations, event handler 190 includes, or has access to, a data updater 176, an object updater 177, and a GUI updater 178. In some implementations, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the corresponding application 136-1 or application view 191. In other implementations, they are included in two or more software modules.

[0123] It should be understood that the above discussion regarding event handling for user touch on a touch-sensitive display also applies to other forms of user input used to operate the multifunction device 100 using an input device, and not all user input is initiated on the touchscreen. For example, mouse movement and mouse button presses optionally in conjunction with single or multiple keyboard presses or holds; touch movements on the touchpad, such as taps, drags, scrolls, etc.; stylus input; device movement; verbal commands; detected eye movements; biometric input; and / or any combination thereof may optionally be used as input corresponding to sub-events that define the event to be identified.

[0124] Figure 2 A portable or non-portable multifunction device 100 with a touchscreen 112 is shown according to some embodiments. As described above, the multifunction device 100 is described as having various structures shown (such as touchscreen 112, speaker 111, accelerometer 168, microphone 113, etc.); however, it should be understood that these structures optionally reside on separate devices. For example, display-related structures (e.g., display, speaker, etc.) and / or functions optionally reside on separate display devices, input-related structures (e.g., touch-sensitive surface, microphone, accelerometer, etc.) and / or functions optionally reside on separate input devices, and other structures and / or functions optionally reside on the multifunction device 100.

[0125] Touchscreen 112 optionally displays one or more graphics within user interface (UI) 200. In this embodiment and other embodiments described below, a user can select one or more graphics by gesturing over the graphics, for example, using one or more fingers 202 (not drawn to scale in the diagram) or one or more styluses 203 (not drawn to scale in the diagram). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the graphics. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down), and / or scrolling (from right to left, from left to right, up and / or down) of a finger already in contact with device 100. In some embodiments or in some cases, unintentional contact with a graphic does not select the graphic. For example, a swipe gesture over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

[0126] Device 100 optionally also includes one or more physical buttons, such as a "home button" or menu button 204. As previously described, menu button 204 is optionally used to navigate to any application 136 of a set of applications optionally executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touchscreen 112.

[0127] In one embodiment, device 100 includes a touchscreen 112, a menu button 204, a push-button 206 for powering on / off and locking the device, one or more volume control buttons 208, a SIM card slot 210, a headset jack 212, and a docking / charging external port 124. The push-button 206 is optionally used to power on / off the device by pressing the button and holding it in the pressed state for a predefined time interval; to lock the device by pressing the button and releasing it before the predefined time interval has elapsed; and / or to unlock the device or initiate an unlocking process. In another embodiment, device 100 also accepts voice input via microphone 113 for activating or deactivating certain functions. Device 100 also optionally includes one or more contact strength sensors 165 for detecting the intensity of contact on the touchscreen 112, and / or one or more haptic output generators 167 for generating haptic outputs for a user of device 100.

[0128] Figure 3This is a block diagram of an exemplary multifunctional device with a display and a touch-sensitive surface according to some embodiments. As mentioned above, device 300 does not necessarily include a display and a touch-sensitive surface; instead, in some embodiments, it optionally communicates with displays and touch-sensitive surfaces on other devices. Additionally, device 300 does not necessarily have to be portable. In some embodiments, device 300 is a laptop computer, desktop computer, tablet computer, multimedia player device (such as a television or set-top box), navigation device, educational device (such as a children's learning toy), gaming system, or control device (e.g., a home or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects system components and controls communication between system components. Device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touchscreen display. I / O interface 330 may also optionally include keyboard and / or mouse (or other pointing device) 350 and touchpad 355, and haptic output generator 357 for generating haptic output on device 300 (e.g., similar to the above reference). Figure 1A The tactile output generator 167 and sensor 359 (e.g., optical sensor, accelerometer, proximity sensor, touch sensor and / or similar to those mentioned above) are described. Figure 1A The contact strength sensor 165 is a contact strength sensor. The memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and optionally includes non-volatile memory, such as one or more disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 370 optionally includes one or more storage devices located remotely from the CPU 310. In some embodiments, the memory 370 stores programs, modules, and data structures or subsets thereof, said programs, modules, and data structures resembling portable or non-portable multifunction device 100. Figure 1A The memory 370 stores programs, modules, and data structures in the memory 102 of the portable or non-portable multifunction device 100. Additionally, the memory 370 optionally stores additional programs, modules, and data structures not present in the memory 102 of the portable or non-portable multifunction device 100. For example, the memory 370 of the device 300 optionally stores a drawing module 380, a rendering module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while the portable or non-portable multifunction device 100 ( Figure 1A The memory 102 may optionally not store these modules.

[0129] Figure 3 Each of the aforementioned identified elements is optionally stored in one or more of the previously mentioned memory devices. Each of the aforementioned identified modules corresponds to an instruction set for performing the functions described above. The aforementioned identified modules or programs (i.e., instruction sets) need not be implemented as standalone software programs, processes, or modules; therefore, various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the aforementioned modules and data structures. Furthermore, memory 370 optionally stores additional modules and data structures not described above.

[0130] Figure 4 A touch-sensitive surface 451 (e.g., separate from the display 450 (e.g., touchscreen display 112)) is shown. Figure 3 Devices (e.g., tablets or touchpads 355) Figure 3 An exemplary user interface on the device 300. The device 300 also optionally includes one or more contact intensity sensors (e.g., one or more sensors in sensor 357) for detecting the intensity of contact on the tactile surface 451 and / or one or more tactile output generators 359 for generating tactile output for the user of the device 300.

[0131] While some examples of input on a reference touchscreen display 112 (which combines a touch-sensitive surface and a display) are given below, in some implementations the device detects input on a touch-sensitive surface separate from the display, such as... Figure 4 As shown in the diagram. In some embodiments, the touch-sensitive surface (e.g., Figure 4 451) has a main shaft (e.g., Figure 4 452), the spindle corresponds to the spindle on the display (e.g., 450), Figure 4 (453 in the example). According to these embodiments, the device detects contact with the touch-sensitive surface 451 (e.g., ...). Figure 4 (460 and 462 in the text), the position of this contact corresponds to the corresponding position on the display (e.g., in...). Figure 4 In this context, 460 corresponds to 468, and 462 corresponds to 470. Thus, when the touch-sensitive surface (e.g., Figure 4 451) and the display of the multi-functional device ( Figure 4 When 450 is separated from the touch-sensitive surface, user input detected by the device (e.g., touches on 460 and 462 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods may be optionally used for other user interfaces described herein.

[0132] Additionally, while the examples below are primarily given with reference to finger input (e.g., finger touch, single-finger tap, finger swipe), it should be understood that in some implementations, one or more of these finger inputs may be replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture may optionally be replaced by a mouse click (e.g., instead of a touch), followed by movement of the cursor along the swipe path (e.g., instead of movement of the touch). Similarly, a tap gesture may optionally be replaced by a mouse click while the cursor is over the location of the tap gesture (e.g., instead of detection of touch, followed by cessation of touch detection). Likewise, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice may optionally be used simultaneously, or mouse and finger touch may optionally be used simultaneously.

[0133] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface with which a user is interacting. In some implementations that include a cursor or other positional marker, the cursor acts as a "focus selector" such that when the cursor hovers over a particular user interface element (e.g., a button, window, slider, or other user interface element), a touch-sensitive surface (e.g., Figure 3 The touchpad 355 or Figure 4 When an input (e.g., a press input) is detected on the touch-sensitive surface 451 of the device, a specific user interface element is adjusted based on the detected input. This applies to touchscreen displays (e.g., those enabling direct interaction with user interface elements on a touchscreen display) that include... Figure 1AIn some embodiments of the touch-sensitive display system 112, a touch detected on the touchscreen acts as a "focus selector," causing the specific user interface element to be adjusted based on the detected input when input (e.g., a press input via a touch) is detected at the location of a specific user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display. In some embodiments, focus moves from one area of ​​the user interface to another without corresponding movement of the cursor or movement of a touch on the touchscreen display (e.g., moving focus from one button to another using tab keys or arrow keys); in these embodiments, the focus selector moves according to the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user-controlled element (or a touch on the touchscreen display) that transmits the user's desired interaction with the user interface (e.g., by indicating to the device the element of the user interface that the user expects to interact with). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of the focus selector (e.g., a cursor, touch, or selection box) above the corresponding button will indicate to the user that they expect to activate the corresponding button (rather than other user interface elements shown on the device's display).

[0134] 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 over a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to be lifted away, before or after contact begins to move, before contact ends, before or after contact intensity is detected to increase and / or before or after contact intensity decreases). The characteristic intensity of the contact is optionally based on one or more of the following: the maximum value of the contact intensity, the mean value of the contact intensity, the average value of the contact intensity, the value at the top 10% of the contact intensity, the half maximum value of the contact intensity, the 90% maximum value of the contact intensity, etc. In some embodiments, the duration of the contact is used when determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the contact intensity over time). In some implementations, the feature intensity is compared to a set of one or more intensity thresholds to determine whether the user has performed an action. For example, the set of one or more intensity thresholds may optionally include a first intensity threshold and a second intensity threshold. In this example, contact with a feature intensity not exceeding the first threshold results in a first action, contact with a feature intensity exceeding the first intensity threshold but not exceeding the second intensity threshold results in a second action, and contact with a feature intensity exceeding the second threshold results in a third action. In some implementations, a comparison between the feature intensity and one or more thresholds is used to determine whether to perform one or more actions (e.g., whether to perform the corresponding action or abandon performing the corresponding action) rather than to determine whether to perform the first action or the second action.

[0135] In some embodiments described herein, one or more operations are performed in response to detecting a gesture including a corresponding press input or in response to detecting a corresponding press input performed using a corresponding contact (or multiple contacts), wherein the corresponding press input is detected at least in part based on detecting that the intensity of the contact (or multiple contacts) increases to above a press input intensity threshold. In some embodiments, the corresponding operation is performed in response to detecting that the intensity of the corresponding contact increases to above a press input intensity threshold (e.g., a "downward stroke" of the corresponding press input). In some embodiments, the press input includes the intensity of the corresponding contact increasing to above a press input intensity threshold and the intensity of the contact subsequently decreasing to below the press input intensity threshold, and the corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases to below the press input threshold (e.g., an "upward stroke" of the corresponding press input).

[0136] In some embodiments, the device employs intensity hysteresis to avoid unintended inputs sometimes referred to as "jitter," wherein the device defines or selects a hysteresis intensity threshold that has a predefined relationship with a 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 percentage of the press input intensity threshold). Therefore, in some embodiments, a press input includes an increase in the intensity of the corresponding contact above the press input intensity threshold and a subsequent decrease in the intensity of that contact below the hysteresis intensity threshold corresponding to the press input intensity threshold, and a corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases below the hysteresis intensity threshold (e.g., an "upstroke" of the corresponding press input). Similarly, in some embodiments, a press input is detected only when the device detects that the contact intensity increases from an intensity equal to or below the hysteresis intensity threshold to an intensity equal to or above the press input intensity threshold and optionally the contact intensity subsequently decreases to an intensity equal to or below the hysteresis intensity threshold, and a corresponding operation is performed in response to detecting a press input (e.g., an increase or decrease in contact intensity depending on the environment).

[0137] For ease of explanation, optionally, the description of an operation triggered in response to a press input associated with a press input strength threshold or in response to a gesture including a press input is provided in response to detecting any of the following conditions: the contact strength increases to above the press input strength threshold, the contact strength increases from below a hysteresis strength threshold to above the press input strength threshold, the contact strength decreases to below the press input strength threshold, and / or the contact strength decreases to below the hysteresis strength threshold corresponding to the press input strength threshold. Additionally, in the example where the operation is described as being performed in response to detecting a decrease in contact strength below the press input strength threshold, the operation is optionally performed in response to detecting a decrease in contact strength below a hysteresis strength threshold corresponding to and less than the press input strength threshold.

[0138] Figure 5A A block diagram of an exemplary architecture for device 500 according to some embodiments of this disclosure is shown. Figure 5A In this implementation, media content or other content is optionally received by device 500 via network interface 502, which is optionally a wireless or wired connection. One or more processors 504 optionally execute any number of programs stored in memory 506 or a storage device, the programs optionally including instructions for performing one or more of the methods and / or processes described herein (e.g., method 700).

[0139] In some embodiments, the display controller 508 causes various user interfaces of this disclosure to be displayed on the display 514. Additionally, input to the device 500 is optionally provided by a remote controller 510 via a remote controller interface 512, which is optionally a wireless or wired connection. In some embodiments, input to the device 500 is provided by a multifunction device 511 (e.g., a smartphone) running a remote application that configures the multifunction device to simulate remote control functionality, as will be described in more detail below. In some embodiments, the multifunction device 511 corresponds to... Figure 1A and Figure 2 Equipment 100 and Figure 3 One or more devices in device 300. It should be understood that... Figure 5A The implementation scheme does not imply limitation on the features of the device described herein, and other components that are advantageous to other features described herein may also be optionally included. Figure 5A In the architecture. In some implementations, device 500 optionally corresponds to Figure 1A and Figure 2 Multifunctional device 100 and Figure 3 One or more of the devices in device 300; network interface 502 optionally corresponds to Figure 1A and Figure 2 The RF circuit 108, external port 124, and peripheral device interface 118 are included. Figure 3 One or more of the network communication interfaces 360; the processor 504 optionally corresponds to one or more of the following: Figure 1A One or more processors 120 and Figure 3 One or more CPUs 310; the display controller 508 optionally corresponds to one or more of the following: Figure 1A The display controller 156 and Figure 3 The I / O interface 330 and memory 506 optionally correspond to one or more of the following: Figure 1A The memory 102 and Figure 3 The memory 370 in the memory; the remote control interface 512 optionally corresponds to one or more of the following: Figure 1A The peripheral device interface 118 and I / O subsystem 106 (and / or its components) and Figure 3 The I / O interface 330; the remote control 512 optionally corresponds to and / or includes one or more of the following: Figure 1AThe system includes a speaker 111, a touch-sensitive display system 112, a microphone 113, one or more optical sensors 164, one or more contact intensity sensors 165, one or more tactile output generators 167, other input control devices 116, one or more accelerometers 168, a proximity sensor 166, and an I / O subsystem 106. Figure 3 The keyboard / mouse 350, touchpad 355, one or more haptic output generators 357, and one or more contact intensity sensors 359, and Figure 4 The touch-sensitive surface 451; and the display 514 optionally corresponds to one or more of the following: Figure 1A and 2 The touch-sensitive display system 112 in the middle, and Figure 3 The monitor in the middle is 340.

[0140] Figure 5B Exemplary structures of a remote controller 510 according to some embodiments of the present disclosure are shown. In some embodiments, the remote controller 510 optionally corresponds to Figure 1A and Figure 2 Multifunctional device 100 and Figure 3 One or more devices in device 300. Remote controller 510 optionally includes a touch-sensitive surface 451. In some embodiments, the touch-sensitive surface 451 is edge-to-edge (e.g., it extends to the edge of remote controller 510 such that there is virtually no or no surface of remote controller 510 between the touch-sensitive surface 451 and one or more edges of remote controller 510, such as...). Figure 5B(As shown). As described above in this disclosure, the touch-sensitive surface 451 is optionally capable of sensing contact and contact intensity (e.g., clicking the touch-sensitive surface 451). Furthermore, the touch-sensitive surface 451 optionally includes a mechanical actuator for providing physical button click functionality (e.g., the touch-sensitive surface 451 is "clickable" to provide a corresponding input to the device 500). The remote control 510 also optionally includes buttons 516, 518, 520, 522, 524, and 526. Buttons 516, 518, 520, 522, 524, and 526 are optionally mechanical buttons or alternative forms of mechanical buttons, which are capable of sensing contact or pressing with such buttons to initiate one or more corresponding actions, for example, on the device 500. In some implementations, a user's selection of the "Menu" button 516 navigates backward through the currently running application or the currently displayed user interface (e.g., backward to a user interface displayed before the currently displayed user interface), or navigates the device 500 to a user interface one level higher than the currently displayed user interface. In some implementations, a user's selection of the "Home" button 518 navigates the device 500 from any user interface displayed on the device 500 to the main, home, or root user interface (e.g., to the home screen of the device 500, which optionally includes one or more applications accessible on the device 500). In some implementations, a user's selection of the "Play / Pause" button 520 toggles between playing and pausing a currently playing content item on the device 500 (e.g., optionally pausing the content item if it is playing on the device 500 when the "Play / Pause" button 520 is selected, and optionally playing the content item if it is paused on the device 500 when the "Play / Pause" button 520 is selected). In some embodiments, the user's selection of the "+" 522 or "-" 524 buttons increases or decreases the volume of audio reproduced by device 500 (e.g., the volume of content currently playing on device 500). In some embodiments, the user's selection of the "Audio Input" button 526 allows the user to provide audio input (e.g., voice input) to device 500, optionally to a voice assistant on the device. In some embodiments, the remote control 510 includes a microphone via which the user provides audio input to device 500 when the user selects the "Audio Input" button 526. In some embodiments, the remote control 510 includes one or more accelerometers for detecting information about the movement of the remote control.

[0141] User interface and related processes

[0142] Music playback and screen saver control

[0143] Users interact with electronic devices in a variety of ways, including with media (e.g., music, movies, etc.) available on the device (e.g., stored or otherwise accessible). For example, a user can browse and play media accessible on an electronic device. However, in some cases, a user may be playing media such as music on an electronic device when it begins to display a screensaver, or when the device is displaying a screensaver (e.g., the device is playing music from a playlist and the user has not interacted with the device for a certain amount of time, causing the device to display a screensaver). Once the screensaver is activated, the user may want to control music playback (e.g., skip a song, replay a song, or play the previous song) without exiting the screensaver and navigating to the appropriate music control interface or application (e.g., a music application) to perform such controls. In some cases, a user may want to control the display of the screensaver without exiting it (e.g., skip to the next screensaver, display the previous screensaver, or see where the screensaver is depicted). The embodiments described below provide a way for electronic devices to enhance user interaction by facilitating music playback and screen saver control while the device is displaying a screen saver. Enhanced interaction with the device reduces the amount of time required for the user to perform actions, thereby reducing the device's power consumption and extending the battery life of battery-powered devices. It should be understood that people use devices. When a person uses a device, that person is optionally referred to as the user of the device.

[0144] Figures 6A to 6DD Exemplary ways in which electronic devices facilitate music playback and screen saver control while displaying a screen saver are illustrated according to some embodiments of the present disclosure. The embodiments in these figures are used to illustrate the processes described below, including references to... Figures 7A to 7Q The process described.

[0145] Figure 6A An exemplary display 514 is shown. Display 514 optionally displays one or more user interfaces including various content. Figure 6A In the example shown, display 514 displays an electronic device (e.g., Figure 5AThe electronic device 500 has a home screen user interface 602, and a display 514 is part of the electronic device or connected to the electronic device. User interface 602 is optionally an application browsing user interface of the electronic device's operating system, which includes icons for different applications installed on the electronic device, which can be selected to launch their corresponding applications on the electronic device. For example, user interface 602 includes icons 618-1 to 618-5, which can be selected to launch different applications on the electronic device. Icon 618-1 can be selected to launch the unified media browsing application, icon 618-2 can be selected to launch the settings application, icon 618-3 can be selected to launch the media application corresponding to media provider 1, icon 618-4 can be selected to launch the media application corresponding to media provider 2, and icon 618-5 can be selected to launch the media application corresponding to media provider 3. Figure 6A In the diagram, icon 618-3 has the current focus, as indicated by the dashed box within icon 618-3. In some embodiments, icons 618-1 to 618-5 are arranged in a scrollable grid pattern, and the user interface 602 is scrollable to display more rows of icons beyond 618-5.

[0146] User interface 602 also includes an area above icon 618 (e.g., a "top layer" area) that optionally displays one or more user interface elements corresponding to the application whose icon 618 currently has focus (in some embodiments, only the icons in the top row of icons 618 in user interface 602 have corresponding user interface elements in the "top layer" area for their current focus). For example, in Figure 6A In the interface 602, icon 618-3 corresponding to media provider 1 has the current focus. Therefore, the electronic device displays representations 623-1 to 623-4 of media items accessible from media provider 1 in the "top" area of ​​the user interface 623. Representation 623 optionally includes information identifying each media item (e.g., text information) and / or information about the content of each media item (e.g., a video preview of the media item, a still image of the media item, etc.). In some embodiments, the "top" area is a scrollable area that includes representations of suggested media items for the currently highlighted application on the home screen, and swiping up moves the current focus to a representation of one of the suggested media items. Selecting that representation (e.g., by tapping or clicking on a remote control) causes the device to begin playing the media item corresponding to the representation of the suggested media item with the current focus.

[0147] In some implementations, device 500 displays one or more screen savers on display 514. For example, in Figure 6BIn this mode, device 500 enters screen saver mode, and display 514 displays screen saver interface 603 (e.g., in response to the device being idle or not receiving user input for a certain amount of time, such as 3 minutes, 5 minutes, or 10 minutes). Figure 6B In this context, screen saver A is displayed in screen saver interface 603. Screen saver A is optionally an animated video displaying an aerial view of a landmark, city, or other geographical location (e.g., an aerial screen saver for Apple Inc. (Cupertino, California)), and in some embodiments, transitions from one to another in a continuous manner (e.g., displaying a continuous aerial view from one location to another without skipping any part of the geography between the two locations). Figure 6B In this example, screensaver A is displaying video or images from location A-1 (e.g., state or country) and sub-location A-1 (e.g., city or landmark). As screensaver A displays (e.g., video playback), screensaver A optionally displays different locations and sub-locations. For example, in some implementations, screensaver A is a continuous fly-through video from San Francisco, California to Los Angeles, California. The screensaver optionally begins by displaying an aerial view of the Golden Gate Bridge, Lombard Street, Painted Ladies, and other landmarks in San Francisco. Screensaver A then optionally “flies” over the California coast before reaching Los Angeles, California (thus displaying scenes and landmarks along the way), and displays landmarks in Los Angeles such as the Griffith Observatory, the Hollywood Sign, and Santa Monica Pier, etc. Thus, a single screensaver optionally displays multiple locations and sub-locations without changing to a different screensaver. After the display of screensaver A ends (e.g., the playback of aerial video reaches its end or the user requests a different screensaver), device 500 optionally displays another screensaver in the screensaver queue. The screensavers in the screensaver queue optionally contain similar overflight aerial videos from different geographical locations.

[0148] exist Figure 6BIn the context of screen saver A, when screen saver A is displaying position A-1 and sub-position A-1, position label 606 is displayed as an overlay on top of the screen saver in the lower left corner of the screen saver interface 603. In some embodiments, position label 606 is displayed for a predetermined time period (e.g., 3 seconds, 5 seconds, or 10 seconds) after the device 500 initially begins displaying the screen saver (e.g., screen saver A). Although position label 606 is displayed in the lower left corner of the screen saver interface 603, this is not intended to be limiting, and position label 606 may optionally be displayed anywhere on the screen saver interface 603 without departing from the scope of this disclosure. Position label 606 provides the user with information about the current position of screen saver A. In some embodiments, position label 606 includes a primary label 616-1 and a secondary label 616-2, which correspond to the primary and secondary positions depicted by the screen saver. Figure 6B In this context, location label 606 includes a primary label 616-1 and a secondary label 616-2 corresponding to location A-1 and sub-location A-1, respectively (e.g., text descriptions / names of location A-1 and sub-location A-1). In some embodiments, device 500 updates location label 606 accordingly when the screen saver changes from displaying one location to another.

[0149] exist Figure 6C In the process, screensaver A changes to display sub-location A-2 within location A-1 (e.g., the animated video has progressed to displaying an aerial view of another landmark still within location A), while location label 606 is displayed on interface 603 (e.g., changing from displaying Golden Gate Bridge in San Francisco to Lombard Street in San Francisco). Therefore, location label 606 is updated to reflect the new location. Specifically, in Figure 6C In the main label 616-1, the location A-1 is still displayed (e.g., San Francisco), but the secondary label 616-2 has been changed to display the sub-location A-2 (e.g., Lombard Street), thus reflecting the new location displayed by the screensaver A.

[0150] exist Figure 6DIn the middle, screensaver A changes to display location A-2 and sub-location A-3 (e.g., the animated video progresses to a point where the new location is no longer displayed within location A-1), while location label 606 is displayed on interface 603 (e.g., changing from displaying Lombard Street in San Francisco to Griffith Observatory in Los Angeles). Therefore, location label 606 is updated to reflect the new location. Specifically, in Figure 6D In the middle, the primary label 616-1 has been changed to display position A-2 (e.g., Los Angeles), and the secondary label 616-2 has been changed to display sub-position A-3 (e.g., GriffithObservatory), thus reflecting the new position displayed by screensaver A.

[0151] exist Figure 6D In the middle, after the location label 606 has been displayed for a certain period of time, the location label 606 will fade out, leaving only the screen saver displayed on the interface 603 (e.g., screen saver A), such as Figure 6E As shown. The amount of time before the location label 606 disappears is optionally the amount of time since the location label 606 was first displayed (e.g., the location label will only display a certain amount of time, regardless of the frequency or number of location changes that have occurred or are displayed by the location label).

[0152] In some implementations, the screensaver interface 603 transitions from one screensaver to another. The transition may optionally be an automatic transition to the next screensaver in the screensaver queue or a manual transition based on user input, as discussed later. An automatic transition occurs when the previous screensaver completes (e.g., after the screensaver has been displayed for a fixed amount of time or after the playback of aerial video reaches the end of the video). For example, as... Figures 6E to 6F As shown, device 500 automatically switches from displaying screen saver A to displaying screen saver B. Specifically, after screen saver A finishes playing, screen saver interface 603 automatically switches to displaying screen saver B, the next screen saver in the screen saver queue. The transition can optionally be a fade-in animation spanning 1 second.

[0153] In some implementations, if the display is driven by the same or similar display signals over an extended period of time, the display may exhibit temporary or permanent physical damage to the pixels or panel of the display. This effect is called screen burn-in and produces a visual discoloration of the pixels on the display (e.g., ghosting). As the name suggests, screen savers optionally prevent screen burn-in and extend the lifespan of the display. Based on the display content of the screen saver, screen savers have different levels of effectiveness in preventing screen burn-in. The effectiveness of a screen saver optionally depends on the screen saver's color palette, brightness, the movement pattern of objects on the screen, and the overall diversity of the driving signals. In some implementations, to improve the device's ability to prevent burn-in, discrete screen savers (each with its own individual screen burn-in prevention capability) can be arranged in a way that improves the overall ability of the device to prevent screen burn-in. For example, the device optionally arranges screen savers to improve its ability to prevent screen burn-in. For example, in Figure 6F In the comparison, screen saver A has a burn-in prevention score of 50, while screen saver B (the next screen saver in the queue) has a burn-in prevention score of 60. Therefore, screen saver B (which follows screen saver A in the queue) has better burn-in prevention characteristics than screen saver A. Although Figure 6F Screen savers A and B are shown with burn-in prevention scores of 50 and 60, respectively, but this is merely illustrative and not intended to be limiting. The burn-in prevention score can optionally be any number on any arbitrary scale (e.g., a scale of 0-10, 0-100, or 0-200).

[0154] In some implementations, the transition between screen savers is smooth and essentially invisible to the user. Therefore, the location label optionally appears only when the user requests to view location information (e.g., by performing a tapping gesture on a touch-sensitive surface, as described later), and screen saver transitions optionally do not trigger the display of the location label. For example, in Figure 6F During or after a screen saver transition from screen saver A to screen saver B, the location label is not displayed in interface 603 (for example, an automatic transition from screen saver A to screen saver B does not trigger the display of the location label).

[0155] As described above, in addition to automatic switching, device 500 is also capable of responding to user input to manually switch between screen savers. Device 500 can optionally manually switch to the next screen saver in the screen saver queue or the previous screen saver in the screen saver queue. For example, in Figure 6GIn the process, a right-to-left swipe of contact 608 is detected on the touch-sensitive surface 604, causing the screen saver interface 603 to switch from displaying screen saver B to displaying screen saver C, the next screen saver in the screen saver queue. The transition, as a result of user input, optionally spans 0.5 seconds (e.g., the transition is faster than an automatic transition, such as...). Figure 6F (As shown). In Figure 6G In the example, screen saver B has a burn-in prevention score of 60, and screen saver C has a burn-in prevention score of 70. Therefore, screen saver C optionally has better burn-in prevention characteristics than screen saver D because it is the next screen saver in the screen saver queue. The manual transition from screen saver B to screen saver C optionally does not display a position label to ensure a smooth visual transition between screen savers (as described above).

[0156] As described above, device 500 can optionally be manually switched to the previous screensaver in the screensaver queue. For example, in Figure 6H In the process, a left-to-right swipe of touch 608 is detected on the touch-sensitive surface 604, causing the interface 603 to switch from displaying screen saver C back to displaying screen saver B, the previous screen saver in the screen saver queue. The manual switch from screen saver C to screen saver B optionally does not display a position label to ensure a smooth visual transition between screen savers (as described above).

[0157] As described above, the user can optionally request information about the location depicted by screensaver B at any time, causing location label 606 to be displayed. For example, in Figure 6I In the event that screen saver B is displayed on interface 603 and no location label is displayed, a tap of contact 608 is detected on touch-sensitive surface 604. Therefore, the electronic device displays location label 606 on screen saver interface 603, as... Figure 6J As shown. Location labels (as previously relative to) Figures 6B to 6D The above includes a primary label 616-1 and a secondary label 616-2 corresponding to the current location B and sub-location B displayed by the screen saver B, respectively (e.g., when a tap touch 608 is received and / or when the location label 606 is displayed, the animated video screen saver is displaying location B and sub-location B).

[0158] As previously described, in some implementations, if the screen saver changes to display a different location, or if the screen saver interface 603 changes to display a different screen saver while displaying a location label, the location label is updated to display the new location depicted by the screen saver. For example, as Figures 6J to 6K As shown, when the location label 606 is displayed, a right-to-left swipe of contact 608 is detected on the touch-sensitive surface 604. Because the right-to-left swipe is detected, the electronic device replaces the display of screen saver B with the display of screen saver C (the next screen saver in the screen saver queue) on the screen saver interface 603, as... Figure 6K As shown. In Figure 6K In the process, screensaver C initially displays position C and sub-position C immediately after the transition (e.g., the first position displayed by the animated video screensaver C is sub-position C at position C). Because position label 606 is displayed when the screensaver transitions, position label 606 now displays position C and sub-position C at the main label 616-1 and secondary label 616-2, respectively. As described above, after the initial display of position label 606, the position label will optionally remain displayed for a certain amount of time, and the screensaver transition and the resulting updates to the main position 616-1 and secondary position 616-2 optionally do not affect the amount of time that position label 606 remains displayed. After displaying position label 606 for a predetermined amount of time, position label 606 optionally disappears.

[0159] In some implementations, when device 500 enters screensaver mode, device 500 is playing music (or more generally, playing music while the device is in screensaver mode, regardless of whether music is being played when it enters screensaver mode). For example, if device 500 is playing music and no user input is received after a certain duration, device 500 optionally enters screensaver mode and displays screensaver interface 603. The screensaver trigger duration can be set by the device or by the user, and can be any suitable duration, such as 3 minutes, 5 minutes, or 10 minutes. In some implementations, when device 500 is in screensaver mode while playing music (e.g., when device 500 enters screensaver mode or when device 500 is in screensaver mode and the user starts playing music without exiting screensaver mode (e.g., by providing a voice command on a remote control device), device 500 is able to provide music control functionality without exiting the screensaver. For example... Figures 6L to 6Q The illustration shows music control functionality when the device 500 displays a screen saver. Specifically, when the device is displaying a screen saver while playing music, the touch-sensitive surface 604 is optionally divided into three areas (e.g., left area 614-1, middle area 614-2, and right area 614-3). In some embodiments, input detected in each of the three areas performs different music control and / or screen saver functions.

[0160] exist Figure 6L In this scenario, when device 500 is playing Michael Jackson's "Thriller," screen saver C is displayed on display 514. The song is optionally one of many songs on the playlist currently being played by the device. Because the screen saver is displayed while the song is playing, the touch-sensitive surface 604 is divided into three areas 614-1 to 614-3, indicated by dashed lines. Figure 6L A click on the right area 614-3 of the touch-sensitive surface 604 was detected. Therefore, the electronic device plays the next song in the playlist, Longview by Green Day, while continuing to display the screen saver C, such as... Figure 6M As shown.

[0161] In some implementations, the music playing while device 500 is displaying a screensaver changes automatically (e.g., when the song ends) or manually (in response to a user request). In some implementations, when the song playing on device 500 changes in response to a user request, a music head-up display (HUD) 610 is displayed, such as... Figure 6M As shown, simply changing the currently playing song may not provide the user with immediate feedback on that change. Therefore, the music HUD provides the user with visual feedback and confirmation that the song has changed, displaying information about the new song. In some implementations, the music HUD 610 is not displayed when the song changes automatically, and is only displayed when the song changes in response to user input.

[0162] For example, in Figure 6M In this context, as a result of a user request to play the next song (e.g., a click on the right area 614-1 of the touch-sensitive surface 604), the music HUD 610 is displayed as an overlay on top of the screen saver interface 603 at the upper right corner. Although the music HUD 610 is displayed at the upper right corner of the screen saver interface 603, this is not intended to be limiting, and the music HUD 610 may optionally be displayed anywhere on the screen saver interface 603 without departing from the scope of this disclosure. The music HUD 610 may optionally display the artist's name and the name of the song that started playing due to the detected click input (as further described with reference to method 700). In some embodiments, the music HUD 610 includes illustrations corresponding to the song being played (e.g., album art, cover art, artist's picture). For example, in Figure 6MIn this implementation, the music HUD 610 displays Green Day as the artist's name and Longview as the song title (e.g., the song that starts playing in response to a request to skip to the next song). In some implementations, the music HUD 610 uses two lines of text. The top line displays the artist, and the bottom line indicates the song title. In some implementations, the top line is in a larger font and / or bold than the bottom line (e.g., for visual emphasis relative to the bottom line).

[0163] After the music HUD 610 has been displayed on interface 603 for a certain period of time, the music HUD 610 may optionally disappear and no longer be displayed on interface 603, such as Figure 6N As shown. Green Day's song Longview will continue to play on the electronic device, and screen saver C will continue to be displayed on the electronic device.

[0164] exist Figure 6N In the event that a tap on the central area 614-2 of the touch-sensitive surface 604 is detected while the electronic device is playing a Longview of Green Day, the electronic device will exit its screen saver and the display 514 will show the home screen interface 602, as shown in the image. Figure 6O As shown. Green Day's song Longview will continue to be played by electronic devices.

[0165] exist Figure 6P In the middle, electronic devices are in a similar state to Figure 6M Status: The electronic device is displaying screen saver interface 603, where screen saver C is the currently displayed screen saver, and playing Green Day's Longview. Figure 6P A click on the left region 614-1 of the touch-sensitive surface 604 has been detected.

[0166] As a result of clicking on the left area 614-1 of the touch-sensitive surface 604, the electronic device optionally plays the previous song in the playlist, namely Michael Jackson's Thriller, while continuing to display the screen saver C, such as Figure 6QAs shown. In some embodiments, if the playback progress of the song being played at the time of the click is below a certain threshold (e.g., the song has been played for less than 3 seconds, 5 seconds, or 10 seconds), the electronic device will play the previous song. In some embodiments, if the playback progress of the song is above a threshold (e.g., the song has been played for more than 3 seconds, 5 seconds, or 10 seconds), the electronic device will replay the song being played at the time of the click. For example, if the playback progress of Green Day's Longview is more than 3 seconds, the result of a click on the left area 614-1 of the touch-sensitive surface 604 may optionally replay Green Day's Longview from the beginning of the song. If the playback progress of Green Day's Longview is less than 3 seconds, the result of a click on the left area 614-1 of the touch-sensitive surface 604 may optionally play the previous song, namely Michael Jackson's Thriller, as shown. Figure 6Q As shown. The 3-second playback threshold in this example is intended to be illustrative only, and any suitable playback threshold may be used without departing from the scope of this disclosure.

[0167] Return to reference Figure 6Q If a click on the left area 614-1 of the touch-sensitive surface 604 results in the playback of the previous song (e.g., if the playback progress is below a playback threshold), the music HUD 610 is displayed, indicating that the currently playing song has changed and showing information about the new song. Figure 6Q In the current context, as a result of user input, device 500 is playing Michael Jackson's "Thriller," so the music HUD 610 displays the artist as Michael Jackson and the song title as "Thriller." However, if a tap on the left area 614-1 of the touch-sensitive surface 604 causes the current song to restart from the beginning, and if the music HUD 610 is not displayed when the tap is detected, it may optionally not be displayed when the playback of the current song resumes.

[0168] exist Figure 6R In the present invention, the electronic device is displaying a screen saver interface 603, in which screen saver C is currently displayed. The screen saver interface 603 includes a music HUD 610 (e.g., the music HUD 610 has not yet disappeared), indicating that the electronic device is playing Michael Jackson's "Thriller". While the music HUD 610 is displayed, a tap of contact 608 corresponding to a request to view location information is detected on the touch-sensitive surface 604. Figure 6SAs shown, due to the detection of a tap input, device 500 displays location labels 606. As previously described, location labels 606 are displayed as an overlay on top of the screen saver and include a primary label 616-1 and a secondary label 616-2 corresponding to the primary and secondary locations depicted by the screen saver. Figure 6S In the display, position label 606 shows position C and sub-position C, thus reflecting the position displayed by screen saver C when the position label is displayed. Therefore, both the music HUD 610 and position label 606 are displayed simultaneously on screen saver interface 603. Although both the music HUD 610 and position label 606 are displayed simultaneously, each overlay optionally maintains its own fade-out timer. In other words, the duration of display of music HUD 610 is optionally unaffected by the display of position label 606, and vice versa (e.g., the display duration and / or fade-out time of music HUD 610 and position label 606 are optionally independent of each other).

[0169] exist Figure 6T In the example where device 500 is displaying screensaver C and playing Michael Jackson's "Thriller," a click input is detected on the play / pause button 520 of remote control 510. As a result of detecting the click input, device 500 pauses the playback of the song, as shown in 6U. In some embodiments, if a click input is detected on the play / pause button 520 of remote control 510 within a threshold time (e.g., 3 seconds, 5 seconds, or 10 seconds) of pausing "Thriller," the playback of "Thriller" is resumable. For example, Figure 6V This illustrates that while playback of Michael Jackson's "Thriller" is currently paused, device 500 detects another tap input on the play / pause button 520 of remote control 510. In some implementations, if the song playback has not been paused for a certain threshold amount of time, device 500 will resume the song playback, such as... Figure 6W As shown. In some implementations, if song playback has been paused for longer than a threshold time, device 500 will exit music playback mode. In other words, device 500 has disabled music playback and no longer responds to music control commands. Figures 6X to 6Z As shown, when device 500 exits music playback mode, the touch-sensitive surface 604 is no longer divided into three areas 614-1 to 614-3. Therefore, any tap input detected on the touch-sensitive surface 604 will optionally no longer control music playback, but will instead optionally exit the screen saver and display the home screen.

[0170] For example, in Figure 6YIn the current state, the playback of Michael Jackson's Thriller has been paused for longer than a threshold duration, and device 500 has exited music playback mode and touch-sensitive surface 604 is no longer segmented. Then, device 500 detects a tap input on the right area of ​​touch-sensitive surface 604 (e.g., the location of area 614-3 when the device is in music playback mode). However, because device 500 is no longer in music playback mode and touch-sensitive surface 604 is no longer segmented, the tap input no longer performs any music playback functions (e.g., device 500 does not play the next song in the playlist). Instead, the device will exit the screensaver and display the home screen interface 602 due to the tap input. Figure 6Z As shown.

[0171] In some implementations, the music HUD and location tags reside on the same display layer. Therefore, the display 514 optionally always displays both the music HUD and the location tags simultaneously. In other words, in some implementations, detected input for displaying the location tags (e.g., in any of the aforementioned ways) causes both the location tags and the music HUD to be displayed, and detected input for displaying the music HUD (e.g., in any of the aforementioned ways) also causes both the location tags and the music HUD to be displayed. Similarly, the fade-out times of the music HUD and the location tags are optionally the same, causing both layers to fade out simultaneously.

[0172] For example, in Figure 6AA In the middle, device 500 is displaying screen saver C while playing Michael Jackson's Thriller, and the touch-sensitive surface 604 is divided into three areas 614-1 to 614-3. Figure 6AA In the middle, a tap of contact 608 is detected in the left region 614-1 of the touch-sensitive surface 604, thereby instructing the user to view the location label (as previously requested relative to...). Figures 6I to 6J (as described above). Therefore, device 500 simultaneously displays location tag 606 and music HUD 610, both overlaid on a screen saver, as... Figure 6BB As shown. After displaying the location label 606 and the music HUD 610 for a certain period of time, both overlays simultaneously disappear and are no longer displayed, such as... Figure 6CC As shown.

[0173] Figures 6CC to 6DD Another exemplary implementation showing a music HUD 610 and location labels 606 on the same layer is illustrated. Figure 6CCIn the event that screen saver C is displayed on display 514 and device 500 is playing Michael Jackson's Thriller, a click on the right area 614-3 of touch-sensitive surface 604 is detected. As a result of detecting the click (e.g., instructing the user to play the next song, as previously indicated relative to...),... Figures 6L to 6M The device 500 plays the next song in the playlist, namely Green Day's Longview, and displays the music HUD 610, as described above. Figure 6DD As shown. In Figure 6DD In the above context, because the music HUD 610 and the location label are on the same layer, the location label 606 and the music HUD 610 are displayed simultaneously. After displaying the location label 606 and the music HUD 610 for a certain period of time, both layers disappear simultaneously and are no longer displayed.

[0174] Figures 7A to 7Q This is a flowchart illustrating a method 700 for facilitating music playback and screen saver control when displaying a screen saver, according to some embodiments of the present disclosure. Method 700 is optionally performed on an electronic device (such as device 100, device 300, or device 500), as described above. Figures 1A to 1B , Figures 2 to 3 and Figures 5A to 5B The operations in method 700 may be optionally combined, and / or the order of some operations may be optionally changed.

[0175] As described below, method 700 provides a way to facilitate music playback and screen saver control while displaying a screen saver. This method reduces the cognitive burden on the user when interacting with the device user interface of this disclosure, thereby creating a more efficient human-computer interface. For battery-powered electronic devices, improving the efficiency of user interaction with the user interface saves power and increases the time between battery charging cycles.

[0176] In some implementations, an electronic device (e.g., a set-top box, such as device 100, device 300, or device 500) communicating with a display (e.g., a television, such as display 514) and one or more input devices (e.g., a remote control device separate from the electronic device, such as remote control 510, or a smartphone separate from the electronic device, such as device 511)) displays a first screen saver (702) on the display. Figure 6BAs shown in the diagram. In some embodiments, the electronic device is a tablet computer, smartphone, wearable device, etc., and the display and / or input device is a touchscreen included in those devices. In some embodiments, when displaying a first screen saver, the electronic device receives an indication (704) of input detected on the touch-sensitive surface of one or more input devices, such as... Figure 6G As shown in the image (e.g., taps, swipes, clicks, multi-touch inputs, or any other suitable input or gesture on a touch-sensitive surface).

[0177] In some implementations, in response to receiving an instruction (706), based on determining that the electronic device is in music playback mode (708) when the instruction is received (e.g., when the device is playing music and displaying a screen saver, or when the device is displaying a screen saver and pausing music but before a threshold time has elapsed to cause the device to exit music playback mode), and based on determining that the input is a click input detected in a first area of ​​a plurality of areas of the touch-sensitive surface, the electronic device displays on the display a representation (710) of music played in response to the input overlaid on the first screen saver, such as... Figures 6L to 6M As shown in the example (e.g., displaying a music HUD). In some embodiments, the music HUD includes artist names, song titles, album titles, artist portraits, album art, hidden artwork, any other suitable images, or any combination thereof. In some embodiments, the currently playing music is the song that was playing when the click input was received. In some embodiments, the currently playing music is a different song from the song that was playing when the click input was received. For example, after receiving a right click, the device optionally begins playing the next song as the song that was playing when the click input was received, and the music HUD displays information about the next song. After receiving a left click, if the playback progress of the song that was playing when the click was received is below a threshold, the device optionally begins playing the previous song as the song that was playing when the click was received, and the music HUD displays information about the previous song. If the playback progress of the song that was playing when the left click was received is above a threshold, in some embodiments, the device optionally replays the song that was playing when the click was received without displaying the music HUD.

[0178] In some implementations, in response to receiving an instruction (706), based on determining that the electronic device is in music playback mode (708) when the instruction is received (e.g., when the device is playing music and displaying a screen saver, or when the device is displaying a screen saver and pausing music but before a threshold time has elapsed to cause the device to exit music playback mode), based on determining that the input is a click input detected in a second area of ​​a plurality of areas of the touch-sensitive surface, different from the first area (e.g., a click in the middle area of ​​the touch-sensitive surface), the electronic device stops displaying the first screen saver (712), such as Figures 6N to 6O As shown in the image (e.g., exiting the screen saver and displaying the home screen of the electronic device).

[0179] The aforementioned method of performing different actions based on the area of ​​the touch-sensitive surface in which input is received (e.g., displaying information about the currently playing song when tapped on a first area, or stopping the screensaver when tapped on a second area) allows electronic devices to provide users with the ability to elicit different actions based on the location of input using a single touch surface (e.g., without exiting the screensaver and navigating to a separate application or interface to perform the same action). This simplifies user interaction with the device and enhances device operability, and makes the user device interface more efficient (e.g., by performing different actions with less input without exiting the screensaver). This, in turn, reduces power consumption and improves device battery life by enabling users to use the device more quickly and efficiently.

[0180] In some implementations, based on determining that the electronic device is in music playback mode (e.g., when the device is displaying a screensaver and playing music, or when the music is paused but a threshold time has not yet elapsed for the device to exit music playback mode), the touch-sensitive surface includes multiple regions, including a first region and a second region, each of the multiple regions being associated with a corresponding function (714), such as... Figure 6L As shown (for example, when in music playback mode, the touch-sensitive surface is optionally divided into three areas). For example, the touch-sensitive surface is optionally divided into a left area, a right area, and a middle area, and a click in the right area will initiate playback of the next song, a click in the left area will initiate playback of the previous song or replay the current song, and a click in the middle area will exit the screen saver.

[0181] In some implementations, based on the determination that the electronic device is not in music playback mode, the touch-sensitive surface does not include multiple areas (716), such as Figure 6BAs shown (for example, when the device is not in music playback mode, the touch-sensitive surface is optionally not divided into multiple areas, such that a click detected on the touch-sensitive surface will cause the electronic device to perform the same action, regardless of where the click is detected on the touch-sensitive surface).

[0182] The aforementioned method of dividing a touch-sensitive surface into multiple regions (each associated with a corresponding function) (e.g., dividing the touch-sensitive surface into a left, right, and center region, where a tap in the right region initiates playback of the next song, a tap in the left region initiates playback of the previous song or replays the current song, and a tap in the center region exits the screensaver) allows electronic devices to provide users with the ability to trigger different actions based on the location of input on a single touch surface (e.g., without exiting the screensaver and navigating to a separate application or interface to perform the same action). This simplifies user interaction with the device and enhances device operability, making the user interface more efficient (e.g., by performing different actions with less input without exiting the screensaver). This, in turn, reduces power consumption and improves device battery life by enabling users to use the device more quickly and efficiently.

[0183] In some implementations, in response to receiving an instruction (717), based on determining that the input is a click input detected in a first area of ​​a plurality of areas of the touch-sensitive surface (e.g., a click in the right area of ​​the touch-sensitive surface), the electronic device initiates playback of the next song in the music playback queue after the currently playing song at the time the input is received (e.g., skips to the next song), wherein the representation of the music played in response to the input includes a representation of the next song (718), such as... Figures 6L to 6M As shown in the image (for example, a music HUD will display information related to the next song).

[0184] In some implementations, in response to receiving an instruction (717), based on determining that the input is a click input detected in a third region of a plurality of regions of the touch-sensitive surface, different from the first and second regions (720) (e.g., a click in the left region of the touch-sensitive surface), and based on determining that the playback progress of the currently playing song is below a predetermined progress threshold (e.g., the currently playing song has been played for less than 0.5 seconds, 1 second, 3 seconds, or 5 seconds), the electronic device initiates playback of the previous song in the music playback queue before the currently playing song (e.g., skips back to the previous song), and displays a representation of the previous song overlaid on the first screensaver on the display (722), such as... Figures 6P to 6Q As shown in the image (for example, a music HUD will display information related to the previous song).

[0185] In some implementations, in response to receiving an instruction (717), based on determining that the input is a click input detected in a third region of the multiple regions of the touch-sensitive surface, different from the first and second regions (720) (e.g., a click in the left region of the touch-sensitive surface), and based on determining that the playback progress of the currently playing song is higher than a predetermined threshold (e.g., the currently playing song has been playing for more than 0.5 seconds, 1 second, 3 seconds, or 5 seconds), the electronic device initiates replay of the currently playing song (e.g., jumps back to the beginning of the current song) without displaying a representation of the currently playing song overlaid on the first screensaver (724), such as... Figures 6P to 6Q As shown in the image (in other words, if the music playback does not change to a different song in response to user input, the music HUD may optionally not be displayed).

[0186] The aforementioned method of selectively displaying music HUD information when different songs begin playing allows electronic devices to effectively convey song information. This simplifies the interaction between the user and the device, enhances the device's operability, and makes the user device interface more efficient (e.g., displaying song information only when the song has changed). This also reduces power consumption and improves the device's battery life by enabling users to use the device more quickly and efficiently.

[0187] In some implementations, in response to receiving an instruction (726) (e.g., a tap, swipe, click, multi-touch input, or any other suitable input or gesture on a touch-sensitive surface), based on determining that the electronic device is not in music playback mode when the instruction is received (e.g., the device is not currently playing music when it enters screen saver mode, or the music has been paused for more than a threshold amount of time, causing the device to exit music playback mode), based on determining that the input is a click input detected on the touch-sensitive surface, the electronic device stops displaying the first screen saver (728), such as... Figures 6Y to 6Z As shown (for example, when the device is not in music playback mode, the touch-sensitive surface is optionally not divided into multiple areas, and any tap input on the touch-sensitive surface optionally exits the screen saver and displays, for example, the user interface that the electronic device is displaying when the screen saver mode is first triggered).

[0188] The aforementioned method of not dividing the touch-sensitive surface when not in playback mode (e.g., allowing a tap to exit the screen saver) allows electronic devices to simplify the operation of the touch-sensitive surface when more complex functions are not required (e.g., music control is not needed). This reduces the device's processing requirements and simplifies the interaction between the user and the device, thereby enhancing the device's operability and making the user interface more efficient. This, in turn, reduces power consumption and improves the device's battery life by enabling users to use the device more quickly, effectively, and intuitively.

[0189] In some implementations, in response to receiving an instruction (730) (e.g., a tap, swipe, click, multi-touch input, or any other suitable input or gesture on a touch-sensitive surface), based on determining that the input is a swipe input detected on the touch-sensitive surface, the electronic device stops displaying a first screen saver (732) and displays a second screen saver (734) different from the first screen saver on the display, such as... Figure 6G As shown (for example, if the input is a swipe to the left, the transition moves to the next screensaver, and if the input is a swipe to the right, the transition moves to the previous screensaver). The transition can optionally be a fade-in / fade-out, slide-out / slide-in, or any other suitable transition animation.

[0190] The manner described above in controlling the displayed screen saver (e.g., displaying a second screen saver after receiving a swipe input on a touch-sensitive surface) allows electronic devices to provide users with the ability to change the displayed screen saver while retaining the screen saver's functionality (e.g., not exiting the screen saver). This enhances the interaction between the user and the device (e.g., by displaying different screen savers for the user's enjoyment), which in turn reduces power consumption and improves the device's battery life (e.g., by optionally minimizing the device's processing requirements and keeping it in a low-power mode).

[0191] In some implementations, based on the determined swipe input in the first direction, the second screensaver is the next screensaver in a screensaver queue that includes the first and second screensavers (736), such as Figure 6G As shown (e.g., transitioning to the next screensaver after receiving a leftward swipe). In some implementations, depending on whether the swipe input is in a second direction different from the first direction, the second screensaver is the previous screensaver in the screensaver queue (738) (e.g., transitioning to the previous screensaver after receiving a rightward swipe).

[0192] The aforementioned method of directional control based on swipe input to display a screensaver allows electronic devices to provide users with the ability to control which screensaver is displayed while retaining the screensaver's functionality (e.g., not exiting the screensaver). This enhances the interaction between the user and the device (e.g., by displaying different screensavers for the user's enjoyment), which in turn reduces power consumption and improves the device's battery life (e.g., by optionally minimizing the device's processing requirements and keeping it in a low-power mode).

[0193] In some implementations, when the first screensaver is displayed and in response to determining that the first screensaver has been displayed for a predetermined display threshold time (740) (e.g., 30 seconds, 1 minute, 2 minutes, 5 minutes, or any other suitable amount of time), the electronic device stops displaying the first screensaver (742) and displays a second screensaver (744) different from the first screensaver on the display, such as... Figure 6F As shown (e.g., automatically transitioning to the next screensaver in the absence of user input). In some embodiments, the predetermined display threshold time is the total duration of the first screensaver (e.g., playback has reached the end of the first screensaver). In some embodiments, the transition from the first screensaver to the second screensaver in response to a swipe input occurs during a first time period (746), such as... Figure 6G As shown (e.g., a swipe input results in a rapid transition to another screensaver). In some embodiments, the transition may optionally be 0.1 seconds, 0.2 seconds, 0.5 seconds, or any other suitable rapid transition time. In some embodiments, in response to determining that the first screensaver has been displayed for a predetermined display threshold time, the transition from the first screensaver to the second screensaver occurs in a second time period (748) that is longer than the first time period, such as... Figure 6F As shown (e.g., an automatic transition not caused by user input results in a slower transition of the screen saver). In some implementations, the transition may optionally be 0.5 seconds, 1 second, 2 seconds, or any other suitable slow transition time.

[0194] The aforementioned methods of switching between screen savers (e.g., automatically switching at a slow rate after a threshold amount of time, and switching at a faster rate in response to a user request to change the screen saver) provide an efficient way to switch screen savers based on triggers that cause the screen saver to change (e.g., automatically or as a result of user input). This enhances the interaction between the user and the device (e.g., by switching quickly upon user request, but slowly to enhance the aesthetics of the screen saver and avoid abrupt changes), which in turn reduces power consumption and improves the device's battery life.

[0195] In some implementations, displaying a second screensaver includes (750) displaying (752) on a display a representation of the current location depicted by the second screensaver overlaid on the first screensaver, based on determining that a representation of the current location depicted by the first screensaver when an instruction is received is displayed overlaid on the first screensaver (e.g., a location label is currently displayed on the screen when the user performs a swipe input to change the displayed screensaver). Figures 6J to 6KAs shown (e.g., removing the location label that shows the location of the first screensaver and replacing it with a location label that shows information about the second screensaver, or keeping the same location label and updating the content to show the location depicted in the second screensaver, or any other suitable switching mechanism).

[0196] In some implementations, displaying a second screensaver includes (750) displaying the second screensaver without displaying the representation of the current location depicted by the first screensaver (754) based on determining that a representation of the current location depicted by the first screensaver is not displayed as an overlay on the first screensaver when an instruction is received (e.g., the location label is not displayed or is hidden when the user performs a swipe input to change the displayed screensaver), such as... Figure 6G As shown in the example (e.g., displaying a new screensaver, but without displaying the location label). In some implementations, the location label is updated to reflect the location depicted in the second screensaver without displaying the location label.

[0197] The aforementioned method of updating the location label (e.g., updating the location label to reflect the location displayed by the new screensaver if it is displayed when the screensaver changes, but not displaying the location label if it is not displayed) allows electronic devices to provide users with updated information about the displayed location depicted by the screensaver. This simplifies the interaction between the user and the device, enhances the operability of the device, and makes the user device more efficient (e.g., by updating the displayed information without requiring further input and without having to exit the screensaver). This also reduces power consumption and improves the device's battery life by enabling users to use the device more quickly and efficiently.

[0198] In some implementations, the burn-in prevention parameter of the next screen saver is greater than the burn-in prevention parameter (756) of the first screen saver, such as... Figure 6F As shown (for example, the screen saver playback queue is optionally arranged so that subsequent screen savers have a better ability to prevent or avoid screen burn-in than previous screen savers). Screen burn-in optionally refers to permanent or temporary discoloration of a display area, typically caused by the cumulative uneven use of display pixels. For example, a screen saver with a higher screen burn-in prevention score optionally changes color or intensity more frequently, changes shape more frequently, or moves objects around the screen, or otherwise avoids driving display pixels with the same signal over an extended period of time. Therefore, when a device displays more screen savers during its current screen saver session, it displays screen savers that are less likely to cause burn-in on the display.

[0199] The aforementioned method of arranging screen savers in a screen saver queue (e.g., making the next screen saver have a larger burn-in prevention parameter than the previous one) allows electronic devices to display different screen savers while increasingly avoiding screen burn-in. This protects the user's display (e.g., by avoiding or preventing burn-in damage to the display), which in turn reduces waste and improves the lifespan of the display, and further enhances the interaction between the user and the device (e.g., by allowing the user to keep the device powered on without the risk of damaging the display, thus allowing the user to interact with the device more quickly without waiting for the device to power on).

[0200] In some implementations, in response to receiving an instruction, based on determining that the input is a tap input detected on a touch-sensitive surface, the electronic device displays on a display a representation (758) of the current location depicted by the first screen saver, overlaid on the first screen saver, such as... Figures 6I to 6J As shown in the example (e.g., displaying a location label on the display after receiving a tap input). In some implementations, the location label describes the location the screensaver is currently depicting. The location label optionally includes primary location text and secondary location text. For example, if the screensaver is displaying a landmark, the primary location is optionally the country where the landmark is located, and the secondary location is the name of the landmark or the city where the landmark is located. The primary location is optionally a continent, country, state, city, or any other suitable primary location. The secondary location is optionally a state, city, landmark, or any other suitable specific location.

[0201] The aforementioned method of displaying the location depicted by the screen saver (e.g., displaying a representation of the location in response to a tap input) allows electronic devices to provide the user with information about the display location depicted by the screen saver only when requested (e.g., not displaying the location when not requested, thus improving the immersive experience of the screen saver. When requested, the user receives the location information without having to exit the screen saver and navigate to a separate interface to receive the same information). This simplifies the interaction between the user and the device and enhances the operability of the device, and makes the user device more efficient (e.g., by providing information only when requested, but hiding the information via less input when not requested, without having to exit the screen saver). This also reduces power consumption and improves the device's battery life by enabling users to use the device more quickly and efficiently.

[0202] In some implementations, when displaying a representation of the current location (e.g., displaying a location label describing the location currently being depicted by the screen saver), and in response to determining that the representation of the current location has been displayed for a predetermined display threshold time (e.g., 1 second, 2 seconds, 5 seconds, 10 seconds, or any other suitable amount of time), the electronic device stops displaying the representation of the current location while continuing to display the first screen saver (760), such as... Figures 6D to 6E As shown in the image (e.g., automatically stopping the display of the location label after a certain amount of time has elapsed since it was first displayed). The animation may optionally be a fade-out, dissolve, or any other suitable animation.

[0203] The aforementioned method of displaying location labels (e.g., displaying location labels for a predetermined threshold time and stopping displaying them after the threshold time) allows electronic devices to provide users with information related to the location being displayed by the screensaver and remove that information after the user has had the opportunity to view it (e.g., by stopping the display of location labels after the threshold time). This simplifies the interaction between the user and the device and enhances the operability of the device, and makes the user device interface more efficient (e.g., by automatically stopping the display of location labels without further user input and without exiting the screensaver). This also reduces power consumption and improves the battery life of the device by enabling users to use the device more quickly and efficiently.

[0204] In some implementations, based on determining that a representation of music played in response to a tap input is displayed when such input is received (e.g., if a music HUD is displayed when the device receives a tap input from the touchpad), the representation of the current location includes simultaneously displaying (762) a representation of the current location overlaid on the first screen saver and a representation of music played in response to the input, such as... Figures 6R to 6S As shown in the diagram (e.g., both the music HUD and the location label are displayed simultaneously). In some embodiments, the music HUD and the location label are displayed in the same area of ​​the display. In some embodiments, the music HUD and the location label are visually separated and displayed in different areas of the display (e.g., the music HUD is displayed in the upper right portion of the display, and the location label is displayed in the lower left portion of the display).

[0205] The aforementioned methods of displaying location labels and music HUD (e.g., displaying location labels and music HUD simultaneously) allow electronic devices to provide users with the ability to simultaneously view information related to the location depicted by the device's music playback and screen saver (e.g., without exiting the screen saver or waiting for the music HUD to fade out before requesting the display of location labels). This simplifies user interaction with the device, enhances device operability, and makes the user device interface more efficient (e.g., by allowing both the music HUD and location labels to be displayed simultaneously without waiting for the music HUD to fade out before displaying the location labels). This also reduces power consumption and improves device battery life by enabling users to use the device more quickly and efficiently.

[0206] In some implementations, when the first screensaver is displayed and the device is in music playback mode (e.g., when the device is playing music), the electronic device receives, via one or more input devices, an indication (764) of an input corresponding to a request to pause playback of the currently playing song when an input corresponding to a request to pause playback is received, such as... Figure 6T As shown in the diagram (e.g., clicking the play / pause button on a remote control while playing music). In some implementations, in response to receiving an input corresponding to a request to pause playback, the electronic device pauses playback of the currently playing song (766), such as... Figure 6U As shown in the diagram. In some embodiments, when pausing playback of the currently playing song, the electronic device receives an indication (768) via one or more input devices of a click input detected on the touch-sensitive surface of one or more input devices, such as... Figure 6Y As shown (e.g., receiving a click on a touch-sensitive surface of a remote control). In some embodiments, in response to receiving a click input, the electronic device stops displaying a first screen saver (770), such as Figure 6Z As shown (for example, when music is not playing, the touch-sensitive surface is no longer segmented, there are no more music controls, and any click input detected on the touch-sensitive surface exits the screen saver).

[0207] The aforementioned method of detecting when music is not playing and exiting the screen saver upon clicking allows electronic devices to provide users with the ability to easily exit the screen saver when music control is not needed. This simplifies the interaction between the user and the device, enhances the operability of the device, and makes the user device interface more efficient. In addition, this reduces power consumption and improves the device's battery life by enabling users to use the device more quickly and effectively.

[0208] In some implementations, when the first screensaver is displayed and the device is in music playback mode (e.g., when the device is playing music), the electronic device receives, via one or more input devices, an indication (772) of an input corresponding to a request to pause playback of the currently playing song when an input corresponding to a request to pause playback is received, such as... Figure 6T As shown in the diagram (e.g., clicking the play / pause button on a remote control while playing music). In some implementations, in response to receiving an input corresponding to a request to pause playback, the electronic device pauses (774) playback of the currently playing song, such as... Figure 6U As shown in the diagram. In some embodiments, when pausing playback of the currently playing song, the electronic device receives, via one or more input devices, an indication (776) corresponding to an input that corresponds to a request to resume playback of the paused song when an input corresponding to a request to resume playback is received, such as... Figure 6V As shown in the image (for example, pressing the play / pause button on the remote control to pause the music).

[0209] In some implementations, in response to receiving an input (778) corresponding to a request to resume playback, the electronic device resumes playback of the song that was paused when the input corresponding to the request to resume playback was received, based on determining that the song has been paused for less than a threshold time (780). Figure 6W As shown (e.g., if the music is paused for only 1 second, 2 seconds, 5 seconds, 10 seconds, 30 seconds, 1 minute, or any other suitable threshold time, the device will resume playback of the paused music upon request). In some embodiments, in response to receiving an input (778) corresponding to a request to resume playback, the electronic device abandons resuming playback of the paused song (782) based on determining that the song has been paused for more than a threshold time, such as... Figures 6X to 6Y As shown (for example, if the music has been paused for too long, the music playback mode will time out and the device will exit music playback mode). In some implementations, a further request to resume playback will not result in music playback because the device is no longer in music playback mode. Users may optionally be able to re-enter music playback mode using other methods, such as via voice command or by exiting the screensaver and restarting music playback mode.

[0210] The aforementioned methods of music control (e.g., pausing music playback when requested to pause and resuming it when requested to resume, or exiting playback mode without resuming it when playback times out) allow electronic devices to provide users with the ability to control music playback, while canceling playback control (e.g., by not resuming music for a threshold time and allowing the playback mode to time out) if the user indicates that he / she no longer wants to play music. This simplifies user-device interaction and reduces power consumption and improves device battery life by enabling the device to shut down processing functions that are no longer needed.

[0211] In some implementations, before displaying the first screensaver and when the screensaver is not displayed on the display (e.g., when the device is not displaying a screensaver but is displaying another user interface, such as the home screen or user interface of an application on an electronic device), in response to determining that the first screensaver should be displayed (784), such as Figure 6A As shown (e.g., in response to user input requesting the display of a screen saver, in response to a period of inactivity at the device causing the screen saver to be displayed (e.g., 3 minutes, 5 minutes, or 10 minutes), or any other trigger for displaying the screen saver), the electronic device displays a first screen saver (786) on the display, such as Figure 6B As shown (e.g., the first screen saver when the device first enters screen saver mode).

[0212] In some implementations, before displaying the first screensaver and when the screensaver is not displayed on the display (e.g., when the device is not displaying a screensaver but is displaying another user interface, such as the home screen or user interface of an application on an electronic device), in response to determining that the first screensaver should be displayed (784), such as Figure 6A As shown (e.g., in response to user input requesting the display of a screen saver, in response to a period of inactivity at the device causing the screen saver to be displayed (e.g., 3 minutes, 5 minutes, or 10 minutes), or any other trigger used to display the screen saver), the electronic device displays a representation (788) of the current location depicted by the first screen saver, overlaid on the first screen saver, such as Figure 6BAs shown (e.g., when the device first enters screen saver mode and displays a first screen saver, a location label will be displayed). The location label optionally has a background color that contrasts with the screen saver color to improve the visibility of the location label. In some embodiments, the background color of the location label is based on a gradient of distance from the label itself. For example, the background color of the location label optionally fades out from the label to create a smooth transition using the screen saver while preserving the visibility of the label's content area.

[0213] In some implementations, while displaying a first screen saver and a representation of the current location depicted by the first screen saver, in response to determining that the representation of the current location depicted by the first screen saver has been displayed for a threshold time, the electronic device stops displaying the representation of the current location while continuing to display the first screen saver (790), such as... Figures 6D to 6E As shown in the diagram (e.g., after the location label has been displayed for a threshold amount of time, the location label disappears or stops displaying). The threshold amount of time is optionally 5 seconds, 10 seconds, 30 seconds, 1 minute, or any other suitable amount of time. Thus, as described above, when the device first displays the screen saver, the location label is optionally displayed, and the label optionally stops displaying after a certain period of time.

[0214] The aforementioned method of temporarily displaying a location label when the screensaver is first displayed (e.g., displaying a location label for the initial screensaver display and removing the location label after a threshold amount of time) allows electronic devices to provide location information to the user when the device first enters screensaver mode (e.g., the user is most likely still near the device and able to receive the displayed information without having to exit the screensaver and navigate to a separate application or interface to receive the location information). This simplifies the interaction between the user and the device and enhances the operability of the device, and makes the user device interface more efficient (e.g., by displaying the location label when the user has the highest probability of seeing it and removing it after the user has had the opportunity to read it, thus avoiding distracting the user from the image on the screensaver). This also reduces power consumption and improves the device's battery life by enabling the user to use the device more quickly and efficiently.

[0215] In some implementations, after stopping the display of a representation of the current location depicted by the first screensaver and while displaying the first screensaver, the electronic device determines to display a second screensaver (792) on the display that is different from the first screensaver, such as... Figures 6E to 6F As shown (e.g., automatically or due to a user request to switch to another screensaver after the location label has disappeared or is no longer displayed in other ways).

[0216] In some implementations, in response to determining that a second screensaver (794) is to be displayed, such as Figures 6E to 6F As shown, the determination to display a second screen saver is in response to user input (796), such as... Figure 6G As shown (for example, if the user requests to switch to the next screen saver by swiping left or right on the touch-sensitive surface of the remote control), the electronic device stops displaying the first screen saver (798), such as Figure 6G As shown in the diagram. In some embodiments, in response to determining that a second screen saver should be displayed (794), and depending on whether the determination to display the second screen saver is in response to user input (796) (e.g., if the user requests to switch to the next screen saver by either swiping left or right on a touch-sensitive surface of a remote control), the electronic device displays on the display a representation of the current location depicted by the second screen saver overlaid on the second screen saver (799) (e.g., optionally when displaying the screen saver without displaying a location label, such as...). Figure 6G As shown, if the transition to the next screensaver is the result of a user request to transition to the next screensaver, then the user transitions to the next screensaver and simultaneously displays the location label associated with the second screensaver, such as... Figure 6K (as shown in the image).

[0217] In some implementations, in response to determining to display a second screen saver (794), the determination to display the second screen saver is not in response to user input (797), such as... Figure 6F As shown (e.g., an automatic transition after displaying the first screensaver for a threshold amount of time), the electronic device stops displaying the first screensaver (795), such as... Figure 6F As shown in the diagram. In some implementations, in response to determining that a second screensaver (794) is to be displayed, such as Figure 6F As shown, the determination that the display of the second screen saver is not in response to user input (797), such as Figure 6F As shown (e.g., an automatic transition after a threshold amount of time has elapsed since the first screensaver was displayed), the electronic device displays (793) a second screensaver on the display, without displaying a representation of the current location depicted by the second screensaver, such as... Figure 6F As shown (for example, if the transition is not the result of user input, such as through automatic transition, then the location label is not displayed when the second screensaver is displayed).

[0218] The aforementioned method of displaying or not displaying a location label when a screensaver changes (e.g., displaying the location label when switching to another screensaver due to a user's request, and not displaying the location label when switching to another screensaver not due to a user's request) allows electronic devices to provide location information to the user when the user is likely viewing the screen (e.g., the user has requested to switch to the next screensaver) and not to provide location information to the user when the user is likely not viewing the screen (e.g., when the screensaver is changing automatically rather than due to user input). This simplifies the interaction between the user and the device and enhances the operability of the device, and makes the user device interface more efficient (e.g., by displaying the location label only when the user has the highest probability of seeing it). This, in turn, reduces power consumption and improves the device's battery life by enabling users to use the device more quickly and efficiently.

[0219] In some implementations, while displaying a first screensaver and a representation of the current location depicted by the first screensaver, the electronic device determines to display a second screensaver (791) on the display that is different from the first screensaver, such as... Figures 6J to 6K As shown (for example, when the system changes the screen saver being displayed in response to user input to display another screen saver or without responding to user input), the location label is currently displayed on the screen (e.g., automatically changes to another screen saver).

[0220] In some implementations, in response to determining that a second screensaver (789) is to be displayed, such as Figures 6J to 6K As shown, the electronic device stops (787) displaying the first screen saver, such as Figure 6K As shown in the diagram. In some implementations, in response to determining that a second screensaver (789) is to be displayed, such as Figures 6I to 6J As shown, the electronic device displays a representation (785) on the display of a second screensaver, depicting the current position overlaid on the second screensaver, such as... Figure 6KThe transition may be shown as illustrated (e.g., automatically or in response to user input requesting a transition to the next screensaver). The transition may optionally be a fade-in / fade-out, slide-out / slide-in, or any other suitable transition animation. Therefore, in some embodiments, if a location label is displayed when a transition from the first screensaver to the second screensaver occurs, the location label is displayed along with the location information of the second screensaver. The transition may optionally be performed by removing the location label displaying the location of the first screensaver and replacing it with a location label displaying information about the second screensaver, or optionally by retaining the location label and updating the content to display the location depicted in the second screensaver, or any other suitable transition mechanism.

[0221] The aforementioned method of updating the location label (e.g., updating the location label to reflect the location displayed by the new screen saver if the location label is displayed when the screen saver changes) allows electronic devices to provide users with updated information about the displayed location depicted by the screen saver. This simplifies the interaction between the user and the device, enhances the operability of the device, and makes the user device more efficient (e.g., by updating the displayed information without requiring further input and without having to exit the screen saver). This also reduces power consumption and improves the device's battery life by enabling users to use the device more quickly and efficiently.

[0222] In some implementations, when displaying a portion of a first screensaver depicting a first location (e.g., when the screensaver includes depictions of multiple locations (e.g., as a screensaver for a continuous aerial recording from Los Angeles to New York) and a portion of the screensaver depicting a specific location is currently being displayed), the electronic device changes the first screensaver from a portion depicting the first location to a portion depicting a second location different from the first location (783), such as... Figures 6B to 6C As shown in the image (e.g., when the screen saver moves to a different display location, such as when consecutive screen savers cross a boundary from location A to location B).

[0223] In some implementations, in response to a change (781), such as Figures 6B to 6C As shown, based on the determination that the representation of the first position is displayed over the first screensaver when a change occurs (e.g., when the screensaver displays a different position, the position label is currently displayed on the screen), the electronic device updates the representation of the first position to become a representation of the second position over the first screensaver (779), such as... Figures 6B to 6CAs shown (e.g., removing the location label displaying the first location of the first screensaver and replacing it with a location label displaying the new location of the first screensaver, or retaining the same location label and updating the content to display the new location, or any other suitable switching mechanism). In some embodiments, in response to the switch (781), such as Figures 6B to 6C As shown, based on the determination that the representation of the first position is not displayed as an overlay on the first screensaver when a change occurs (e.g., when the screensaver displays a different position, the position label is not displayed or is hidden), the electronic device displays the portion of the first screensaver depicting the second position, but does not display the representation of the second position (777) (e.g., if the screensaver changes from displaying one position to displaying a new position, such as...). Figure 6C As shown in the image, but without displaying the location label during the transition, the new location is displayed within the same screensaver, but without the location label, as shown. Figure 6E (As shown in the diagram). In some implementations, the location label is updated to reflect the new location without displaying the location label.

[0224] The aforementioned method of updating the location label (e.g., updating the location label to reflect the new location displayed by the screen saver if the location label is displayed when the screen saver displays a new location, but not displaying the location label if the location label is not displayed) allows electronic devices to provide users with updated information about the displayed location depicted by the screen saver. This simplifies the interaction between the user and the device, enhances the operability of the device, and makes the user device more efficient (e.g., by updating the displayed information without requiring further input and without having to exit the screen saver). This also reduces power consumption and improves the device's battery life by enabling users to use the device more quickly and efficiently.

[0225] In some implementations, when a portion of the first screensaver depicting a second location is displayed without an indication of the second location (e.g., the location label is not displayed, and the screensaver is displaying a new location), the electronic device receives, via one or more input devices, an indication (775) of a tap input detected on the touch-sensitive surface of one or more input devices, such as... Figure 6I As shown (e.g., the user has tapped a touch-sensitive surface, thus requesting the display of a location label). In some embodiments, in response to receiving a tap input indication, the electronic device displays on the display a representation (773) of a second location depicted by the first screensaver, overlaid on the first screensaver, such as... Figure 6J As shown (e.g., displaying a location label that includes information about the new location depicted by the screen saver). The information is optionally updated when the user requests it to be displayed, or optionally updated when the screen saver switches to displaying the new location, even if the location label is not displayed at that time.

[0226] The aforementioned method of displaying a new location depicted by the screensaver (e.g., displaying a representation of the new location in response to a tap input) allows electronic devices to provide the user with information about a new location depicted by the screensaver only when requested (e.g., not displaying the location when not requested, thus improving the immersive experience of the screensaver. When requested, the user receives the location information without having to exit the screensaver and navigate to a separate interface to receive the same information). This simplifies the interaction between the user and the device and enhances the operability of the device, and makes the user device more efficient (e.g., by providing information only when requested, but hiding the information via less input when not requested, without having to exit the screensaver). This also reduces power consumption and improves the device's battery life by enabling users to use the device more quickly and efficiently.

[0227] In some implementations, the representation of the first position includes a representation of the primary position of the first position and a representation of the secondary position of the first position (771), such as Figure 6B As shown (for example, location labels optionally include two labels: primary location and secondary location). The primary location is optionally a general name or identifier for the location, and the secondary location is optionally a specific name or identifier for the location (for example, the secondary location is optionally a more specific location descriptor than the primary location). For example, if a screensaver is displaying a landmark, the primary location is optionally the country where the landmark is located, and the secondary location is the name of the landmark or the city where the landmark is located. The primary location is optionally a continent, country, state, city, or any other suitable primary location. The secondary location is optionally a state, city, landmark, or any other suitable specific location.

[0228] In some implementations, updating the representation of the first position to become the representation of the second position includes (769) updating the secondary position to the secondary secondary position based on determining that the second position is associated with the primary position of the first position and the secondary secondary position of the first position, while maintaining the primary position (767), such as Figures 6B to 6C As shown (for example, the screensaver displays different locations within the same primary location; in this case, the secondary location is optionally updated to display the updated secondary location, without changing the primary location). For example, if the screensaver displays San Francisco, California, the primary location is optionally California, and the secondary location is optionally San Francisco. Then, if the screensaver moves to display Los Angeles, California, the primary location is optionally not changed and California remains displayed, and the secondary location is optionally updated to display Los Angeles.

[0229] In some implementations, updating the representation of the first position to become the representation of the second position includes (769) based on determining that the second position is associated with a second primary position and a secondary position of the first position, the electronic device updates the primary position to the second primary position while maintaining the secondary position (765). (For example, if the screen saver changes from displaying a primary position to displaying a different primary position, such as...) Figure 6D As shown, however, the new position displayed is the same minor position as the old position, and then the primary position is optionally updated to display the updated primary position, without changing the minor positions, such as... Figure 6D As shown, the difference is that the secondary position label 616-2 maintains the display sub-position A-2. For example, if the screensaver displays French Alps, the primary position is optionally France, and the secondary position is optionally Alps. Then, if the screensaver moves to display Swiss Alps, the primary position is optionally updated to display Switzerland, and the secondary position is optionally left unchanged and the display of Alps is maintained.

[0230] In some implementations, updating the representation of the first position to become the representation of the second position includes (769) based on determining that the second position is associated with a second primary position and a secondary secondary position, the electronic device updates the primary position to the second primary position and the secondary position to the secondary secondary position (763), such as Figures 6C to 6D As shown (for example, the screensaver displays different primary and secondary positions, in which case both the primary and secondary positions are optionally updated to display the updated primary and secondary positions). For example, if the screensaver displays San Francisco, California, the primary position is optionally California, and the secondary position is optionally San Francisco. Then, if the screensaver moves to display New York City, New York, the primary position is optionally updated to display New York, and the secondary position is optionally updated to display New York City.

[0231] The aforementioned method of displaying the location depicted by the screen saver (e.g., displaying a general location and a secondary location and updating information for either location independently) allows electronic devices to provide users with more detailed information about the display location depicted by the screen saver (e.g., updating the general location without updating the secondary location, updating the secondary location without updating the general location, or updating both locations simultaneously). This simplifies the interaction between the user and the device and enhances the operability of the device, and makes the user device more efficient (e.g., by providing more information without having to exit the screen saver). This, in turn, reduces power consumption and improves the device's battery life by enabling users to use the device more quickly and efficiently.

[0232] In some implementations, in response to determining the display of a representation of music played in response to input, the electronic device simultaneously displays on the display a representation of the current position depicted by the currently displayed screensaver and a representation of the music played in response to input, both representations overlaying the currently displayed screensaver (761), such as... Figures 6CC to 6DD As shown (e.g., when the device determines to display a music HUD, it also displays a location label simultaneously). The music HUD and location label may optionally stop displaying or fade out simultaneously. In some embodiments, in response to determining to display a representation of the current location depicted by the currently displayed screensaver, the electronic device simultaneously displays on the display a representation of music played in response to input and a representation of the current location depicted by the currently displayed screensaver, both of which overlay the currently displayed screensaver (759), such as... Figures 6AA to 6BB As shown in the image (for example, when the device determines to display a location label, the music HUD is also displayed at the same time).

[0233] The aforementioned method of displaying information (e.g., both the music HUD and the location label when either is triggered) allows electronic devices to provide users with more detailed information about the music playback status and the display location depicted by the screensaver (e.g., displaying both without having to exit the screensaver and navigate to a separate interface to receive the same information). This simplifies user interaction and enhances device operability, and makes the user device more efficient (e.g., by providing more information without having to exit the screensaver). This, in turn, reduces power consumption and improves device battery life by enabling users to use the device more quickly and efficiently.

[0234] It should be understood that, Figures 7A to 7QThe specific order in which the operations are described herein is merely exemplary and not intended to indicate that the order is the only order in which the operations can be performed. Those skilled in the art will conceive of various ways to reorder the operations described herein. The operations in the above-described information processing method are optionally implemented by running one or more functional modules in an information processing apparatus, such as a general-purpose processor (e.g., as opposed to...). Figure 1A , Figure 3 , Figure 5A (As described) or a dedicated chip. Additionally, the above references... Figures 7A to 7Q The described operation is optionally determined by Figures 1A to 1B The components depicted are used to implement this. For example, display operations 702 and 710, receive operation 704, and stop operation 712 are optionally implemented by event classifier 170, event recognizer 180, and event handler 190. Event monitor 171 in event classifier 170 detects contact on touch-sensitive surface 604, and event dispatcher module 174 delivers event information to application 136-1. The corresponding event recognizer 180 of application 136-1 compares the event information with the corresponding event definition 186 and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub-event, such as a selection of an object on the user interface. When a corresponding predefined event or sub-event is detected, event recognizer 180 activates the event handler 190 associated with the detection of that event or sub-event. Event handler 190 optionally utilizes or invokes data updater 176 or object updater 177 to update the application's internal state 192. In some implementations, event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application. Similarly, those skilled in the art will readily understand how this can be done based on... Figures 1A to 1B The components depicted in the diagram are used to perform other processes.

[0235] As described above, one aspect of the present invention involves collecting and using data from various sources to improve the delivery of content that users may be interested in. This disclosure contemplates that, in some instances, such collected data may include personal information that uniquely identifies or can be used to contact or locate specific individuals. Such personal information may include demographic data, location-based data, telephone numbers, email addresses, Twitter accounts, home addresses, data or records related to a user's health or health level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying or personal information.

[0236] This disclosure recognizes that the use of such personal information data in the techniques of this invention can benefit users. For example, personal information data can be used to deliver targeted content that a user is interested in (e.g., preferred screensavers, disliked screensavers). Therefore, the use of such personal information data enables users to have planned control over the content delivered. Furthermore, this disclosure also anticipates other uses of personal information data that benefit users. For example, health and fitness data can be used to provide insights into a user's overall health status or as positive feedback for individuals using technology to pursue health goals.

[0237] This disclosure assumes that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as data collection and / or use change. Personal information from users should be collected for the entity's lawful and reasonable purposes and not shared or sold outside of these lawful uses. Furthermore, such collection / sharing should be conducted only after obtaining informed consent from users. In addition, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data and ensure that others with access to such personal information data comply with their privacy policies and processes. Additionally, such entities may be subject to third-party evaluations to demonstrate their compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be adapted to the specific types of personal information data collected and / or accessed, and to applicable laws and standards, including specific considerations regarding jurisdiction. For example, in the United States, the collection or acquisition of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while in other countries, health data may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained for different types of personal data in each country.

[0238] Regardless of the foregoing, this disclosure also contemplates implementation schemes for users to selectively block the use or access to personal information data. That is, this disclosure contemplates providing hardware and / or software components to prevent or block access to such personal information data. For example, with respect to content delivery services, the inventive technology can be configured to allow users to opt-in or opt-out at any time during or after service registration to participate in the collection of personal information data. In another example, users can choose not to provide content preference data for a target content delivery service. In addition to providing opt-in and opt-out options, this disclosure envisions providing notifications related to access to or use of personal information. For example, users can be notified when downloading an application that their personal information data will be accessed, and then reminded again just before the application accesses the personal information data.

[0239] Furthermore, the purpose of this disclosure is to manage and process personal information data to minimize the risk of unintentional or unauthorized access or use. Once data is no longer needed, this risk can be minimized by limiting data collection and deleting data. Additionally, and where applicable, including in certain health-related applications, data deidentification can be used to protect user privacy. Deidentification can be facilitated, where appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than the address level), controlling how data is stored (e.g., aggregating data among users), and / or other methods.

[0240] Therefore, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, it is also contemplated that various embodiments can be implemented without access to such personal information data. That is, various embodiments of the present invention will not be rendered inoperable due to the absence of all or part of such personal information data. For example, preferences can be inferred based on non-personal information data or a minimal amount of personal information, such as content requested by a device associated with a user, other non-personal information available to the content delivery service, or publicly available information, thereby selecting content and delivering it to the user.

[0241] For purposes of explanation, the foregoing description has been given by reference to specific embodiments. However, the illustrative discussion above is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible based on the teachings above. The embodiments were chosen and described to best elucidate the principles of the invention and its practical application, thereby enabling others skilled in the art to best utilize the invention with various modifications suitable for the contemplated particular purpose, as well as the various described embodiments.

Claims

1. A control method implemented at an electronic device, the method comprising: At the electronic device that communicates with a display and one or more input devices: Displaying a screen saver via the display includes displaying one or more images via the display while the electronic device is playing music; When the screen saver is displayed and when the music is played, a first input corresponding to a request to pause the playback of the music is received via the one or more input devices; In response to receiving the first input, the playback of the music is paused. At the same time, the display of the screen saver is maintained; While maintaining the display of the screen saver and when the playback of the music is paused, a second input corresponding to a request to resume the playback of the music is received via the one or more input devices; and In response to receiving the second input: Based on the determination that the second input was received within a threshold time of the first input, the playback of the music is resumed while the display of the screen saver is maintained; as well as If it is determined that the second input is received after the threshold time amount of the first input, the resumption of the paused music playback is abandoned.

2. The method according to claim 1, further comprising: In response to receiving the second input, based on the determination that the second input was received after the threshold time amount of the first input: Stop displaying the screen saver; as well as The home screen user interface of the electronic device is displayed via the display, and the home screen user interface is different from the screen saver.

3. The method of claim 1, wherein the first input and the second input are detected in a first region of a plurality of regions of the touch-sensitive surface of the one or more input devices.

4. The method of claim 1, wherein the first input is detected in a first region of a plurality of regions of the touch-sensitive surface of the one or more input devices, and the second input is detected in a second region of the plurality of regions of the touch-sensitive surface, the second region being different from the first region.

5. The method of claim 1, wherein when the second input is detected: Based on the determination that the second input is received within a threshold time period of the first input, the touch-sensitive surface of the one or more input devices includes a plurality of regions, the plurality of regions including a first region that detected the first input, each of the plurality of regions being selectable to perform a different function to control the playback of the music, and based on the determination that the second input is received after the threshold time period of the first input, the touch-sensitive surface does not include the plurality of regions.

6. The method of claim 1, wherein the first input and the second input are detected at the same button on the one or more input devices.

7. An electronic device, the electronic device comprising: One or more processors; Memory; as well as One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors to cause the electronic device to perform the method according to any one of claims 1 to 6.

8. A non-transitory computer-readable storage medium storing one or more programs, said one or more programs comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform the method according to any one of claims 1 to 6.

9. A control method implemented at an electronic device, the control method comprising: At the electronic device that communicates with a display and one or more input devices: Displaying a first screen saver on the display includes displaying one or more images on the display; When the first screen saver is displayed, an indication of input detected on the touch-sensitive surface of the one or more input devices is received via the one or more input devices; In response to receiving the instruction: Based on the determination that the electronic device was playing music when the instruction was received: Based on the determination that the input is a click input detected in a first area of ​​a plurality of areas on the touch-sensitive surface, in response to the input, an indication of music being played by the electronic device is overlaid on the first screen saver, wherein the indication of music being played by the electronic device is not displayed before the indication of the input is received; as well as The first screen saver is stopped from being displayed if the input is determined to be a click input detected in a second region of the plurality of regions of the touch-sensitive surface that is different from the first region.

Images