User interface for managing audio exposure

Abstract

To provide a user interface and technology for using a computer system (for example, an electronic device) to manage audio exposure.SOLUTION: An electronic device displays a graphical display having a noise exposure level over a first period, having a graphical display region colored so as to represent the noise exposure level. The color of the region transits from a first color to a second color when the noise exposure level exceeds a first threshold value. The electronic device displays the noise exposure level resulting from a first output device type and a second output device type, and visually distinguishes a set of the noise exposure levels resulting from the second output device type in response to selection of a filtering affordance.SELECTED DRAWING: Figure 6A

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is related to U.S. patent application Ser. No. 16 / 880,552, filed May 21, 2020, entitled "USER INTERFACES FOR MANAGING AUDIO EXPOSURE," U.S. patent application Ser. No. 16 / 584,186, filed September 26, 2019, entitled "USER INTERFACES FOR MONITORING NOISE EXPOSURE LEVELS," Danish patent application Ser. No. PA 2020 70335, filed May 25, 2020, entitled "USER INTERFACES FOR MANAGING AUDIO EXPOSURE," Danish patent application Ser. No. PA 2019 70534, filed August 27, 2019, entitled "USER INTERFACES FOR MONITORING NOISE EXPOSURE LEVELS," and Danish patent application Ser. No. PA 2019 70534, filed May 11, 2020, entitled "USER INTERFACES FOR MANAGING AUDIO EXPOSURE." This application claims priority to U.S. Provisional Patent Application No. 63 / 023,023, entitled "USER INTERFACES FOR MONITORING NOISE EXPOSURE," filed June 1, 2019, and U.S. Provisional Patent Application No. 62 / 856,016, entitled "USER INTERFACES FOR MONITORING NOISE EXPOSURE LEVELS," filed June 1, 2019, the contents of each of which are incorporated herein by reference in their entirety. [Technical Field]

[0002] The present disclosure relates generally to computer user interfaces, and more particularly to user interfaces and techniques for managing audio exposure. [Background technology]

[0003] The electronic device can be used to manage the amount of audio that is exposed to a user of the electronic device. Information about the audio exposure can be presented to the user on the electronic device. Summary of the Invention

[0004] However, some techniques for managing audio exposure using electronic devices are generally cumbersome and inefficient. For example, some existing techniques use complex and time-consuming user interfaces that may involve multiple key presses or strokes. Existing techniques take more time than necessary, wasting the user's time and the device's energy. The latter problem is particularly acute in battery-operated devices.

[0005] Thus, the present technology provides electronic devices with faster, more efficient methods and interfaces for managing audio exposure. Such methods and interfaces optionally complement or replace other methods for managing audio exposure. Such methods and interfaces reduce the cognitive burden on users and create more efficient human-machine interfaces. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.

[0006] According to some embodiments, a method is described that is executed on an electronic device including a display device, the method including: displaying via the display device a first user interface including a graphical object that changes appearance based on a noise level; receiving first noise level data corresponding to a first noise level below a threshold noise level; displaying the graphical object in a first color having an active portion of a first size based on the first noise data in response to receiving the first noise level data; receiving second noise level data corresponding to a second noise level different from the first noise level while maintaining display of the first user interface; displaying the active portion in a second size based on the second noise level different from the first size in response to receiving the second noise level data; displaying the active portion in a second color different from the first color in response to determining that the second noise level exceeds the threshold noise level; and maintaining display of the graphical object in the first color in response to determining that the second noise level does not exceed the threshold noise level.

[0007] In some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device including a display device is described, wherein the one or more programs include instructions for displaying, via the display device, a first user interface including a graphical object whose appearance changes based on a noise level, receiving first noise level data corresponding to a first noise level below a threshold noise level, displaying the graphical object in a first color having an active portion of a first size based on the first noise data in response to receiving the first noise level data, receiving second noise level data corresponding to a second noise level different from the first noise level while maintaining display of the first user interface, and displaying the active portion in a second size based on the second noise level different from the first size in response to receiving the second noise level data, displaying the active portion in a second color different from the first color in response to determining that the second noise level exceeds the threshold noise level, and maintaining display of the graphical object in the first color in response to determining that the second noise level does not exceed the threshold noise level.

[0008] In some embodiments, a transient computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device including a display device is described, wherein the one or more programs include instructions for displaying, via the display device, a first user interface including a graphical object whose appearance changes based on a noise level, receiving first noise level data corresponding to a first noise level below a threshold noise level, displaying the graphical object in a first color having an active portion of a first size based on the first noise data in response to receiving the first noise level data, receiving, while maintaining display of the first user interface, second noise level data corresponding to a second noise level different from the first noise level, displaying the active portion in a second size based on the second noise level different from the first size in response to receiving the second noise level data, displaying the active portion in a second color different from the first color in response to determining that the second noise level exceeds the threshold noise level, and maintaining display of the graphical object in the first color in response to determining that the second noise level does not exceed the threshold noise level.

[0009] According to some embodiments, an electronic device is described comprising: a display device; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for displaying, via the display device, a first user interface including a graphical object whose appearance changes based on a noise level, receiving first noise level data corresponding to a first noise level below a threshold noise level, displaying the graphical object in a first color having an active portion of a first size based on the first noise data in response to receiving the first noise level data, receiving, while maintaining display of the first user interface, second noise level data corresponding to a second noise level different from the first noise level, displaying the active portion in a second size based on the second noise level different from the first size in response to receiving the second noise level data, displaying the active portion in a second color different from the first color in response to determining that the second noise level exceeds the threshold noise level, and maintaining display of the graphical object in the first color in response to determining that the second noise level does not exceed the threshold noise level.

[0010] According to some embodiments, an electronic device is described that includes a display device, means for displaying via the display device a first user interface including a graphical object that changes appearance based on a noise level, means for receiving first noise level data corresponding to a first noise level below a threshold noise level, means for displaying the graphical object in a first color having an active portion of a first size based on the first noise data in response to receiving the first noise level data, means for receiving second noise level data corresponding to a second noise level different from the first noise level while maintaining display of the first user interface, and means for displaying the active portion in a second size based on the second noise level different from the first size in response to receiving the second noise level data, and in response to determining that the second noise level exceeds the threshold noise level, displaying the active portion in a second color different from the first color, and in response to determining that the second noise level does not exceed the threshold noise level, maintaining display of the graphical object in the first color.

[0011] According to some embodiments, a method is described that is performed in an electronic device that includes a display device and a touch-sensitive surface. The method includes receiving first noise level data attributable to a first device type and second noise level data attributable to a second device type different from the first device type, displaying, via the display device, a first user interface that includes a first representation of the received noise level data based on the first noise level data and the second noise level data and a first device type data filtering affordance, detecting, while displaying the first user interface, a first user input that corresponds to a selection of the first device type data filtering affordance, and, in response to detecting the first user input, displaying a second representation of the received noise level data that is based on the second noise level data and not based on the first noise level data.

[0012] According to some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device including a display device and a touch-sensitive surface is described. The one or more programs include instructions for receiving first noise level data attributable to a first device type and second noise level data attributable to a second device type different from the first device type, displaying a first user interface via the display device, the first user interface including a first representation of the received noise level data based on the first noise level data and the second noise level data and a first device type data filtering affordance, detecting a first user input while displaying the first user interface corresponding to a selection of the first device type data filtering affordance, and displaying a second representation of the received noise level data based on the second noise level data and not based on the first noise level data in response to detecting the first user input.

[0013] According to some embodiments, a transient computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device including a display device and a touch-sensitive surface is described. The one or more programs include instructions for receiving first noise level data attributable to a first device type and second noise level data attributable to a second device type different from the first device type, displaying a first user interface via the display device, the first user interface including a first representation of the received noise level data based on the first noise level data and the second noise level data and a first device type data filtering affordance, detecting a first user input while displaying the first user interface corresponding to a selection of the first device type data filtering affordance, and displaying a second representation of the received noise level data based on the second noise level data and not based on the first noise level data in response to detecting the first user input.

[0014] According to some embodiments, an electronic device is described comprising: a display device, a touch-sensitive surface, one or more processors, and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving first noise level data attributable to a first device type and second noise level data attributable to a second device type different from the first device type; displaying, via the display device, a first user interface, the first user interface including a first representation of the received noise level data based on the first noise level data and the second noise level data and a first device type data filtering affordance; detecting, while displaying the first user interface, a first user input corresponding to a selection of the first device type data filtering affordance; and displaying, in response to detecting the first user input, a second representation of the received noise level data based on the second noise level data and not based on the first noise level data.

[0015] According to some embodiments, an electronic device is described that includes a display device, a touch-sensitive surface, means for receiving first noise level data attributable to a first device type and second noise level data attributable to a second device type different from the first device type, means for displaying a first user interface via the display device, the first user interface including a first representation of the received noise level data based on the first noise level data and the second noise level data and a first device type data filtering affordance, means for detecting, while displaying the first user interface, a first user input corresponding to selection of the first device type data filtering affordance, and means for displaying, in response to detecting the first user input, a second representation of the received noise level data based on the second noise level data and not based on the first noise level data.

[0016] According to some embodiments, a method is described that is executed on a computer system in communication with a display generation component, an audio generation component, and one or more input devices. The method includes displaying, via a display generation component, an audio preference interface including simultaneously displaying a representation of a first audio sample, the first audio sample having a first set of audio characteristics, and a representation of a second audio sample, the second audio sample having a second set of audio characteristics different from the first set of audio characteristics; outputting, while displaying the audio preference interface, at least a portion of the first audio sample via the audio generation component; receiving, via one or more input devices, a set of one or more user inputs; recording a selection of the first audio sample as a preferred sample or selecting the second audio sample as a preferred sample after receiving the set of one or more inputs; and outputting, via the audio generation component, the first audio data, wherein the output of the first audio data is based on at least one audio characteristic of the first set of audio characteristics in accordance with the first audio sample being recorded as the preferred sample, and the output of the first audio data is based on at least one audio characteristic of the second set of audio characteristics in accordance with the second audio sample being recorded as the preferred sample.

[0017] According to some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component, an audio generating component, and one or more input devices is described. The one or more programs include instructions for displaying, via a display generation component, an audio preference interface including simultaneously displaying a representation of a first audio sample, the first audio sample having a first set of audio characteristics, and a representation of a second audio sample, the second audio sample having a second set of audio characteristics different from the first set of audio characteristics; outputting, while displaying the audio preference interface, at least a portion of the first audio sample via the audio generation component; receiving, via one or more input devices, a set of one or more user inputs; recording a selection of the first audio sample as a preferred sample or selecting the second audio sample as a preferred sample after receiving the set of one or more inputs; and outputting, via the audio generation component, the first audio data, wherein the output of the first audio data is based on at least one audio characteristic of the first set of audio characteristics in accordance with the first audio sample being recorded as the preferred sample, and the output of the first audio data is based on at least one audio characteristic of the second set of audio characteristics in accordance with the second audio sample being recorded as the preferred sample.

[0018] According to some embodiments, a transient computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component, an audio generation component, and one or more input devices. The one or more programs include instructions for displaying, via a display generation component, an audio preference interface including simultaneously displaying a representation of a first audio sample, the first audio sample having a first set of audio characteristics, and a representation of a second audio sample, the second audio sample having a second set of audio characteristics different from the first set of audio characteristics; outputting, while displaying the audio preference interface, at least a portion of the first audio sample via the audio generation component; receiving, via one or more input devices, a set of one or more user inputs; recording a selection of the first audio sample as a preferred sample or selecting the second audio sample as a preferred sample after receiving the set of one or more inputs; and outputting, via the audio generation component, the first audio data, wherein the output of the first audio data is based on at least one audio characteristic of the first set of audio characteristics in accordance with the first audio sample being recorded as the preferred sample, and the output of the first audio data is based on at least one audio characteristic of the second set of audio characteristics in accordance with the second audio sample being recorded as the preferred sample.

[0019] According to some embodiments, a computer system in communication with a display generation component, an audio generation component, and one or more input devices is described. The computer system in communication with the display generation component, the audio generation component, and one or more input devices includes means for displaying, via the display generation component, an audio preference interface including simultaneously displaying a representation of a first audio sample, the first audio sample having a first set of audio characteristics, and a representation of a second audio sample, the second audio sample having a second set of audio characteristics different from the first set of audio characteristics; and means for outputting, via the audio generation component, at least a portion of the first audio sample while displaying the audio preference interface, and outputting, via the one or more input devices, a representation of a first audio sample to one or more users. and means for receiving a set of audio inputs; and means for, after receiving the set of one or more inputs, recording a selection of a first audio sample as a preferred sample or selecting a second audio sample as a preferred sample, and outputting the first audio data via the audio generation component, wherein the output of the first audio data is based on at least one audio characteristic of the first set of audio characteristics in accordance with the first audio sample being recorded as a preferred sample, and the output of the first audio data is based on at least one audio characteristic of the second set of audio characteristics in accordance with the second audio sample being recorded as a preferred sample.

[0020] According to some embodiments, a method executed on a computer system in communication with an audio generation component is described, the method including detecting that an audio exposure threshold criterion has been met while causing output of audio data at a first volume via the audio generation component, and, in response to detecting that the audio exposure threshold criterion has been met, reducing the volume of the output of the audio data to a second volume lower than the first volume while continuing to cause output of the audio data.

[0021] According to some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with an audio generation component is described, wherein the one or more programs include instructions for: detecting that an audio exposure threshold criterion has been met while causing output of audio data at a first volume via the audio generation component; and, in response to detecting that the audio exposure threshold criterion has been met, reducing the volume of the output of the audio data to a second volume lower than the first volume while continuing to cause output of the audio data.

[0022] According to some embodiments, a temporary computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of a computer system in communication with an audio generation component, the one or more programs including instructions for: detecting that an audio exposure threshold criterion has been met while causing output of audio data at a first volume via the audio generation component; and, in response to detecting that the audio exposure threshold criterion has been met, reducing the volume of the output of the audio data to a second volume that is lower than the first volume while continuing to cause output of the audio data.

[0023] According to some embodiments, a computer system in communication with an audio generation component is described. The computer system in communication with the audio generation component includes one or more processors and a memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for detecting that an audio exposure threshold criterion has been met while causing output of audio data at a first volume via the audio generation component, and in response to detecting that the audio exposure threshold criterion has been met, reducing the volume of the output of the audio data to a second volume lower than the first volume while continuing to cause output of the audio data.

[0024] According to some embodiments, a computer system is described that includes a display generation component, an audio generation component, one or more input devices, means for detecting that an audio exposure threshold criterion has been met while causing output of audio data at a first volume via the audio generation component, and means for reducing the volume of the output of the audio data to a second volume lower than the first volume in response to detecting that the audio exposure threshold criterion has been met while continuing to cause output of the audio data.

[0025] According to some embodiments, a method executed on a computer system in communication with a display generation component and one or more input devices is described, the method including receiving, via the one or more input devices, input corresponding to a request to display audio exposure data, and, in response to receiving the input corresponding to the request to display the audio exposure data, displaying, via the display generation component, an audio exposure interface that includes simultaneously displaying an indication of the audio exposure data over a first time period and a first visual representation of a first alert provided as a result of a first audio exposure value exceeding an audio exposure threshold, the first visual representation of the first alert including an indication of a time when the first alert was provided.

[0026] According to some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices is described, the one or more programs including instructions for: receiving, via the one or more input devices, input corresponding to a request to display audio exposure data; and, in response to receiving the input corresponding to the request to display the audio exposure data, displaying, via the display generation component, an audio exposure interface including simultaneously displaying an indication of the audio exposure data over a first time period and a first visual indication of a first alert provided as a result of a first audio exposure value exceeding an audio exposure threshold, the first visual indication of the first alert including an indication of a time when the first alert was provided.

[0027] According to some embodiments, a transient computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices is described, the one or more programs including instructions for: receiving, via the one or more input devices, input corresponding to a request to display audio exposure data; and, in response to receiving the input corresponding to the request to display the audio exposure data, displaying, via the display generation component, an audio exposure interface including simultaneously displaying an indication of the audio exposure data over a first time period and a first visual indication of a first alert provided as a result of a first audio exposure value exceeding an audio exposure threshold, the first visual indication of the first alert including an indication of a time when the first alert was provided.

[0028] According to some embodiments, a computer system in communication with a display generation component and one or more input devices is described. The computer system in communication with the display generation component and one or more input devices comprises one or more processors and a memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for: receiving, via the one or more input devices, input corresponding to a request to display audio exposure data; and, in response to receiving the input corresponding to the request to display the audio exposure data, displaying, via the display generation component, an audio exposure interface including simultaneously displaying an indication of the audio exposure data over a first time period and a first visual indication of a first alert provided as a result of a first audio exposure value exceeding an audio exposure threshold, the first visual indication of the first alert including an indication of a time when the first alert was provided.

[0029] According to some embodiments, a computer system in communication with a display generation component and one or more input devices is described, the computer system comprising: means for receiving, via the one or more input devices, input corresponding to a request to display audio exposure data; and means for displaying, via the display generation component, an audio exposure interface in response to receiving the input corresponding to the request to display the audio exposure data, the audio exposure interface including simultaneously displaying, via the display generation component, an indication of the audio exposure data over a first time period and a first visual indication of a first alert provided as a result of a first audio exposure value exceeding an audio exposure threshold, the first visual indication of the first alert including an indication of a time when the first alert was provided.

[0030] According to some embodiments, a method executed on a computer system in communication with an audio generation component is described. The method includes receiving output audio data associated with output audio generated using the audio generation component, the output audio including a first audio signal and a second audio signal, the output audio data including a first predicted output audio volume of the first audio signal and a second predicted output audio volume of the second audio signal; in accordance with a determination that the output audio data satisfies a first set of criteria, the first set of criteria is met when the first predicted output audio volume of the first audio signal exceeds an output audio volume threshold, causing output of the first audio signal at a reduced output audio volume lower than the first predicted output audio volume and causing output of the second audio signal at the second predicted output audio volume; and in accordance with a determination that the output audio data does not satisfy the first set of criteria, causing output of the first audio signal at the first predicted output audio volume and causing output of the second audio signal at the second predicted output audio volume.

[0031] According to some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with an audio generation component is described. The one or more programs include instructions for receiving output audio data associated with output audio generated using the audio generation component, the output audio including a first audio signal and a second audio signal, the output audio data including a first predicted output audio volume of the first audio signal and a second predicted output audio volume of the second audio signal; in accordance with a determination that the output audio data satisfies a first set of criteria, the set of first criteria is met when the first predicted output audio volume of the first audio signal exceeds an output audio volume threshold, causing output of the first audio signal at a reduced output audio volume lower than the first predicted output audio volume and causing output of the second audio signal at the second predicted output audio volume; and in accordance with a determination that the output audio data does not satisfy the set of first criteria, causing output of the first audio signal at the first predicted output audio volume and causing output of the second audio signal at the second predicted output audio volume.

[0032] According to some embodiments, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with an audio generation component is described. The one or more programs include instructions for receiving output audio data associated with output audio generated using the audio generation component, the output audio including a first audio signal and a second audio signal, the output audio data including a first predicted output audio volume of the first audio signal and a second predicted output audio volume of the second audio signal; in accordance with a determination that the output audio data satisfies a first set of criteria, the set of first criteria is met when the first predicted output audio volume of the first audio signal exceeds an output audio volume threshold, causing output of the first audio signal at a reduced output audio volume lower than the first predicted output audio volume and causing output of the second audio signal at the second predicted output audio volume; and in accordance with a determination that the output audio data does not satisfy the set of first criteria, causing output of the first audio signal at the first predicted output audio volume and causing output of the second audio signal at the second predicted output audio volume.

[0033] According to some embodiments, a computer system in communication with an audio generation component is described, the computer system comprising one or more processors and a memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for receiving output audio data associated with output audio generated using the audio generation component, the output audio including a first audio signal and a second audio signal, the output audio data including a first predicted output audio volume of the first audio signal and a second predicted output audio volume of the second audio signal; in accordance with a determination that the output audio data satisfies a first set of criteria, the set of first criteria is met when the first predicted output audio volume of the first audio signal exceeds an output audio volume threshold, causing output of the first audio signal at a reduced output audio volume lower than the first predicted output audio volume and causing output of the second audio signal at the second predicted output audio volume; and in accordance with a determination that the output audio data does not satisfy the set of first criteria, causing output of the first audio signal at the first predicted output audio volume and causing output of the second audio signal at the second predicted output audio volume.

[0034] According to some embodiments, a computer system in communication with an audio generation component is described, the computer system comprising: means for receiving output audio data associated with output audio generated using the audio generation component, the output audio including a first audio signal and a second audio signal, the output audio data including a first predicted output audio volume of the first audio signal and a second predicted output audio volume of the second audio signal; means for, in accordance with a determination that the output audio data satisfies a first set of criteria, causing output of the first audio signal at a reduced output audio volume lower than the first predicted output audio volume and causing output of the second audio signal at the second predicted output audio volume, where the first set of criteria is met when the first predicted output audio volume of the first audio signal exceeds an output audio volume threshold; and means for, in accordance with a determination that the output audio data does not satisfy the first set of criteria, causing output of the first audio signal at the first predicted output audio volume and causing output of the second audio signal at the second predicted output audio volume.

[0035] Executable instructions to perform these functions are optionally contained in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions to perform these functions are optionally contained in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

[0036] This provides devices with faster, more efficient methods and interfaces for managing audio exposure, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may complement or replace other methods for managing audio exposure. [Brief explanation of the drawings]

[0037] For a better understanding of the various described embodiments, reference should be made to the following Detailed Description of the Invention in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout:

[0038] [Figure 1A] 1 is a block diagram illustrating a portable multifunction device having a touch-sensitive display in accordance with some embodiments.

[0039] [Figure 1B] FIG. 2 is a block diagram illustrating exemplary components for event processing according to some embodiments.

[0040] [Figure 2] FIG. 1 illustrates a portable multifunction device with a touch screen in accordance with some embodiments.

[0041] [Figure 3] FIG. 1 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface in accordance with some embodiments.

[0042] [Figure 4A] 1 illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.

[0043] [Figure 4B] 1A-1C illustrate exemplary user interfaces for a multifunction device having a touch-sensitive surface separate from a display in accordance with some embodiments.

[0044] [Figure 5A] FIG. 1 illustrates a personal electronic device according to some embodiments.

[0045] [Figure 5B]FIG. 1 is a block diagram illustrating a personal electronic device according to some embodiments.

[0046] [Figure 5C] 1 illustrates exemplary components of a personal electronic device having a touch-sensitive display and intensity sensor in accordance with some embodiments. [Figure 5D] 1 illustrates exemplary components of a personal electronic device having a touch-sensitive display and intensity sensor in accordance with some embodiments.

[0047] [Figure 5E] 1 illustrates exemplary components and a user interface of a personal electronic device according to some embodiments. [Figure 5F] 1 illustrates exemplary components and a user interface of a personal electronic device according to some embodiments. [Figure 5G] 1 illustrates exemplary components and a user interface of a personal electronic device according to some embodiments. [Figure 5H] 1 illustrates exemplary components and a user interface of a personal electronic device according to some embodiments.

[0048] [Figure 6A] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6B] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6C] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6D] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6E] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6F]1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6G] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6H] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6I] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6J] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6K] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6L] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6M] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6N] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6O] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6P] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6Q] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6R] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6S] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6T]1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6U] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6V] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6W] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6X] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6Y] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6Z] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6AA] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6AB] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6AC] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6AD] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6AE] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6AF] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6AG] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6AH]1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6AI] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6AJ] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6AK] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 6AL] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments.

[0049] [Figure 7A] FIG. 1 is a flow diagram illustrating a method for monitoring noise exposure levels using an electronic device, according to some embodiments. [Figure 7B] FIG. 1 is a flow diagram illustrating a method for monitoring noise exposure levels using an electronic device, according to some embodiments.

[0050] [Figure 8A] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 8B] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 8C] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 8D] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 8E] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 8F] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 8G]1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 8H] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 8I] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 8J] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 8K] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments. [Figure 8L] 1 illustrates a user interface for monitoring noise exposure levels, according to some embodiments.

[0051] [Figure 9A] 1 illustrates a user interface for monitoring audio exposure levels, according to some embodiments. [Figure 9B] 1 illustrates a user interface for monitoring audio exposure levels, according to some embodiments. [Figure 9C] 1 illustrates a user interface for monitoring audio exposure levels, according to some embodiments. [Figure 9D] 1 illustrates a user interface for monitoring audio exposure levels, according to some embodiments. [Figure 9E] 1 illustrates a user interface for monitoring audio exposure levels, according to some embodiments. [Figure 9F] 1 illustrates a user interface for monitoring audio exposure levels, according to some embodiments. [Figure 9G] 1 illustrates a user interface for monitoring audio exposure levels, according to some embodiments.

[0052] [Figure 10]FIG. 1 is a flow diagram illustrating a method for monitoring audio exposure levels using an electronic device, according to some embodiments.

[0053] [Figure 11A] 1 illustrates a user interface according to some embodiments. [Figure 11B] 1 illustrates a user interface according to some embodiments. [Figure 11C] 1 illustrates a user interface according to some embodiments. [Figure 11D] 1 illustrates a user interface according to some embodiments. [Figure 11E] 1 illustrates a user interface according to some embodiments. [Figure 11F] 1 illustrates a user interface according to some embodiments. [Figure 11G] 1 illustrates a user interface according to some embodiments. [Figure 11H] 1 illustrates a user interface according to some embodiments. [Figure 11I] 1 illustrates a user interface according to some embodiments. [Figure 11J] 1 illustrates a user interface according to some embodiments. [Figure 11K] 1 illustrates a user interface according to some embodiments. [Figure 11L] 1 illustrates a user interface according to some embodiments.

[0054] [Figure 12A] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12B] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12C]1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12D] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12E] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12F] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12G] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12H] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12I] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12J] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12K] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12L] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12M] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12N]1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12O] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12P] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12Q] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12R] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12S] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12T] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12U] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12V] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12W] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12X] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12Y]1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12Z] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12AA] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12AB] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12AC] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12AD] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12AE] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12AF] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12AG] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12AH] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12AI] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12AJ]1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12AK] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12AL] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12AM] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments. [Figure 12AN] 1 illustrates a user interface for customizing audio settings based on user preferences, according to some embodiments.

[0055] [Figure 13] FIG. 1 is a flow diagram illustrating a method for customizing audio settings using a computer system, according to some embodiments.

[0056] [Figure 14A] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14B] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14C] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14D] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14E] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14F]1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14G] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14H] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14I] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14J] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14K] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14L] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14M] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14N] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14O] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14P] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14Q] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14R] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14S] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14T] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14U] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14V] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14W] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14X] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14Y] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14Z] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14AA] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14AB] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14AC] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14AD] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14AE] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14AF] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14AG] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14AH] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14AI] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14AJ] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments. [Figure 14AK] 1 illustrates an exemplary user interface for managing audio exposure, according to some embodiments.

[0057] [Figure 15] FIG. 1 is a flow diagram illustrating a method for displaying an audio exposure limit alert using a computer system, according to some embodiments.

[0058] [Figure 16] FIG. 1 is a flow diagram illustrating a method for managing audio exposure using a computer system, according to some embodiments.

[0059] [Figure 17A] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17B] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17C] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17D] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17E] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17F]1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17G] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17H] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17I] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17J] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17K] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17L] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17M] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17N] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17O] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17P] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17Q] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17R] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17S]1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17T] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17U] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments. [Figure 17V] 1 illustrates an exemplary user interface for managing audio exposure data, according to some embodiments.

[0060] [Figure 18] FIG. 1 is a flow diagram illustrating a method for managing audio exposure data using a computer system, according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0061] The following description sets forth example methods, parameters, etc. However, it should be recognized that such description is not intended as a limitation on the scope of the present disclosure, but rather is provided as a description of example embodiments.

[0062] In some implementations, an exemplary electronic device provides an efficient method and interface for managing audio exposure. For example, the exemplary electronic device may provide a user with information regarding the level of noise to which the user is exposed in a manner that is easily understandable and convenient for the user. In another example, the exemplary electronic device may effectively alert a user of the electronic device when the noise level to which the user is exposed exceeds a certain threshold level. In another example, the exemplary electronic device may customize audio settings based on user preferences. In another example, the exemplary electronic device may provide a user with information regarding the amount of audio to which the user is exposed in a manner that is easily understandable and convenient for the user. In another example, the exemplary electronic device may effectively alert a user of the electronic device when the amount of audio to which the user is exposed exceeds a certain threshold level. In another example, the exemplary electronic device may effectively adjust the amount of audio to which the user is exposed to protect the health of the user's auditory system. Such techniques in the exemplary electronic device may reduce the cognitive burden on users of monitoring noise exposure levels, thereby increasing productivity. Furthermore, such techniques may reduce processor and battery power that would otherwise be wasted on redundant user input.

[0063] In the following description, terms such as "first" and "second" are used to describe various elements, but these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first touch can be referred to as a second touch, and similarly, a second touch can be referred to as a first touch, without departing from the scope of the various embodiments described. Although a first touch and a second touch are both touches, they are not the same touch.

[0064] The terminology used in the description of various embodiments set forth herein is for the purpose of describing particular embodiments only and is not intended to be limiting. In the description of the various embodiments set forth and in the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. Also, as used herein, the term "and / or" should be understood to refer to and include any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "includes," "including," "comprises," and / or "comprising," as used herein, specify the presence of 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.

[0065] The term "if" is interpreted, optionally, depending on the context, to mean "when" or "upon," or "in response to determining" or "in response to detecting." Similarly, the phrase "if it is determined" or "if [a stated condition or event] is detected" is interpreted, optionally, depending on the context, to mean "upon determining" or "in response to determining," or "upon detecting [the stated condition or event]" or "in response to detecting [the stated condition or event]."

[0066] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Optionally, other portable electronic devices, such as laptops or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad), are also used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad). In some embodiments, the electronic device is a computer system that communicates (e.g., via wireless communication over wired communication) with a display generation component. The display generation component is configured to provide a visual output, such as a display via a CRT display, a display via an LED display, or a display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. As used herein, "displaying" content includes displaying content (e.g., video data rendered or decoded by display controller 156) by transmitting data (e.g., image data or video data) over a wired or wireless connection to an integrated or external display generation component to visually generate the content.

[0067] In the following discussion, electronic devices are described that include a display and a touch-sensitive surface. However, it should be understood that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and / or a joystick.

[0068] The device typically supports a variety of applications such as one or more of a drawing application, a presentation application, a word processing application, a website creation application, a disc authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an email application, an instant messaging application, a training support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and / or a digital video player application.

[0069] 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 features of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or changed for each application and / or within each application. In this way, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports various applications with user interfaces that are intuitive and transparent to the user.

[0070] Attention now turns to embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable multifunction device 100 having touch-sensitive display system 112, according to some embodiments. Touch-sensitive display 112 may conveniently be referred to as a "touch screen" and may also be known or referred to as a "touch-sensitive display system." Device 100 includes memory 102 (optionally including one or more computer-readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input / output (I / O) subsystem 106, other input control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 that detect the intensity of a contact on device 100 (e.g., a touch-sensitive surface, such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 that generate tactile output on device 100 (e.g., generate tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0071] As used herein and in the claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or a proxy for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four distinct values ​​and more typically includes hundreds (e.g., at least 256) distinct values. The intensity of a contact is optionally determined (or measured) using various techniques and various sensors or combinations of sensors. For example, one or more force sensors under or adjacent to the touch-sensitive surface are optionally used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted averaged) to determine an estimated force of the contact. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in the contact area detected on the touch-sensitive surface, the capacitance and / or change in the capacitance of the touch-sensitive surface proximate the contact, and / or the resistance and / or change in the capacitance of the touch-sensitive surface proximate the contact are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measure of the force or pressure of the contact is used directly to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measure). In some implementations, the surrogate measure of the contact force or pressure is converted to an estimate of the force or pressure, and the estimate of the force or pressure is used to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using contact intensity as an attribute of user input allows users to access additional device functionality (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons) that may not otherwise be accessible to users on devices of reduced size that have limited footprint for displaying affordances.

[0072] As used herein and in the claims, the term “tactile output” refers to a physical displacement of a 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., a housing), or a displacement of a component relative to the center of mass of the device, that will be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of a device is in contact with a touch-sensitive surface of a user (e.g., the fingers, palm, or other part of the user's hand), the tactile output produced by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical property of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a “downclick” or “upclick” of a physical actuator button. In some cases, a user feels a tactile sensation such as a “downclick” or “upclick” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's action. As another example, movement of a touch-sensitive surface is optionally interpreted or perceived by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. While such user interpretation of touch depends on the user's personal sensory perception, there are many sensory perceptions of touch that are common to the majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "upclick," "downclick," "roughness"), unless otherwise specified, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that produces the described sensory perception for a typical (or average) user.

[0073] It should be understood that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than those shown, optionally combines two or more components, or optionally has a different configuration or arrangement of its components. The various components shown in Figure 1A are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing circuits and / or application specific integrated circuits.

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

[0075] Peripheral interface 118 may be used to couple input and output peripherals of the device to CPU 120 and memory 102. One or more processors 120 operate or execute various software programs and / or instruction sets stored in memory 102 to perform various functions and process data for device 100. In some embodiments, peripheral interface 118, CPU 120, and memory controller 122 are optionally implemented on a single chip, such as chip 104. In some other embodiments, they are optionally implemented on separate chips.

[0076] RF (radio frequency) circuitry 108 transmits and receives RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to electromagnetic signals and electromagnetic signals to communicate with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, etc. RF circuitry 108 optionally communicates via wireless communication with networks, such as the Internet, also known as the World Wide Web (WWW), an intranet, and / or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and with other devices. RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by short-range radios. Wireless communication optionally includes, but is not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), Long Term Evolution (LTE), and other standards.evolution (LTE), near field communications (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and / or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, protocols for email (e.g., Internet message access protocol (IMAP) and / or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol), The present invention may use any of a number of communication standards, protocols, and technologies, including the Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (XMPP), the Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), the Instant Messaging and Presence Service (IMPS), and / or the Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this application.

[0077] Audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuit 110 receives audio data from peripherals 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 audible to humans. Audio circuit 110 also receives electrical signals converted from sound waves by microphone 113. Audio circuit 110 converts the electrical signals into audio data and transmits the audio data to peripherals interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to memory 102 and / or RF circuit 108 by peripherals interface 118. In some embodiments, audio circuit 110 also includes a headset jack (e.g., 212 in FIG. 2 ). The headset jack provides an interface between audio circuitry 110 and a detachable audio input / output peripheral, such as an output-only headphone or a headset with both an output (e.g., single or double ear headphones) and an input (e.g., a microphone).

[0078] 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, light sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. One or more input controllers 160 receive / send electrical signals from / to other input control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons), dials, slider switches, joysticks, click wheels, etc. In some embodiments, input controller(s) 160 are optionally coupled to any (or none) of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208 in FIG. 2 ) optionally include up / down buttons for volume control of speaker 111 and / or microphone 113. The one or more buttons optionally include push buttons (e.g., 206 in FIG. 2 ). In some embodiments, the electronic device is a computer system in communication with one or more input devices (e.g., via wireless communication over wired communication). In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a trackpad as part of a touch-sensitive display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more light sensors 164 and / or one or more depth camera sensors 175), such as for tracking user gestures (e.g., hand gestures) as input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system.

[0079] As described in U.S. Patent Application No. 11 / 322,549, filed December 23, 2005, "Unlocking a Device by Performing Gestures on an Unlock Image," U.S. Patent No. 7,657,849, which is incorporated herein by reference in its entirety, a quick press of a push button optionally unlocks touchscreen 112 or, optionally, initiates the process of unlocking the device using gestures on the touchscreen. A longer press of a push button (e.g., 206) optionally turns power on or off to device 100. The functionality of one or more of the buttons is optionally customizable by the user. Touchscreen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

[0080] Touch-sensitive display 112 provides an input and output interface between the device and a user. Display controller 156 receives and / or sends electrical signals to touchscreen 112. Touchscreen 112 displays visual output to the user. This visual output optionally includes graphics, text, icons, animation, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.

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

[0082] Touchscreen 112 optionally uses LCD (liquid crystal display), LPD (light emitting polymer display), or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touchscreen 112 and display controller 156 optionally use any of a number of now known or later developed touch sensing technologies to detect contact and any movement or disruption thereof, including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements that determine one or more points of contact with touchscreen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.

[0083] The touch-sensitive display in some embodiments of touchscreen 112 is optionally similar to the multi-touch-sensing touchpad described in U.S. Patent Nos. 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman), and / or U.S. Patent Application Publication No. 2002 / 0015024 A1, each of which is incorporated by reference herein in its entirety. However, touchscreen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.

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

[0085] Touchscreen 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. A user optionally contacts touchscreen 112 using any suitable object or accessory, such as a stylus, a finger, or the like. In some embodiments, the user interface is designed to operate primarily using finger-based contact and gestures, which may not be as precise as stylus-based input due to the larger contact area of ​​a finger on the touchscreen. In some embodiments, the device translates the coarse finger input into precise pointer / cursor positions or commands to perform the action desired by the user.

[0086] In some embodiments, in addition to the touchscreen, device 100 optionally includes a touchpad for activating or deactivating certain 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 touchscreen 112 or an extension of the touch-sensitive surface formed by the touchscreen.

[0087] Device 100 also includes a power system 162 that provides power to the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, power failure detection circuitry, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of electrical power within a portable device.

[0088] Device 100 also optionally includes one or more light sensors 164. FIG. 1A shows a light sensor coupled to light sensor controller 158 in I / O subsystem 106. Light sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Light sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. Light sensor 164 optionally works in conjunction with imaging module 143 (also called a camera module) to capture still images or video. In some embodiments, the light sensor is located on the back side of device 100 opposite touchscreen display 112 on the front of the device, so that the touchscreen display can be used as a viewfinder for capturing still images and / or video. In some embodiments, the light sensor is located on the front of the device so that an image of a user is optionally acquired for a videoconference while the user views other videoconference participants on the touchscreen display. In some embodiments, the position of the light sensor 164 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), so that a single light sensor 164 is used for both video conferencing and capturing still images and / or video, along with a touchscreen display.

[0089] Device 100 also optionally includes one or more depth camera sensors 175. FIG. 1A shows a depth camera sensor coupled to depth camera controller 169 in I / O subsystem 106. Depth camera sensor 175 receives data from the environment and creates a three-dimensional model of an object (e.g., a face) in a scene from a viewpoint (e.g., the depth camera sensor). In some embodiments, in conjunction with imaging module 143 (also referred to as a camera module), depth camera sensor 175 is optionally used to determine a depth map of different portions of an image captured by imaging module 143. In some embodiments, a depth camera sensor is located on the front of device 100 to obtain images of the user with depth information for videoconferences and to capture selfie images with depth map data while the user views other videoconference participants on a touchscreen display. In some embodiments, depth camera sensor 175 is located on the back of the device or on both the back and front of device 100. In some embodiments, the position of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), so that the depth camera sensor 175 is used for both video conferencing and capturing still images and / or video, in conjunction with a touchscreen display.

[0090] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I / O subsystem 106. Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor 165 receives contact intensity information (e.g., pressure information, or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is juxtaposed with or proximate to the touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touchscreen display 112, which is located on the front of device 100.

[0091] Device 100 also optionally includes one or more proximity sensors 166. Figure 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternatively, proximity sensor 166 is optionally coupled to input controller 160 within I / O subsystem 106. Proximity sensor 166 optionally functions as described in U.S. patent application Ser. Nos. 11 / 241,839, "Proximity Detector In Handheld Device," 11 / 240,788, "Proximity Detector In Handheld Device," 11 / 620,702, "Using Ambient Light Sensor To Augment Proximity Sensor Output," 11 / 586,862, "Automated Response To And Sensing Of User Activity In Portable Devices," and 11 / 638,251, "Methods And Systems For Automatic Configuration Of Peripherals," which are incorporated herein by reference in their entireties. In some embodiments, the proximity sensor turns off and disables touchscreen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

[0092] Device 100 also optionally includes one or more tactile output generators 167. FIG. 1A shows tactile output generators coupled to haptic feedback controller 161 in I / O subsystem 106. Tactile 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 polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates a tactile output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is juxtaposed with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112) and generates a tactile output, optionally by moving the touch-sensitive surface vertically (e.g., in / out of the surface of device 100) or horizontally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touchscreen display 112, which is located on the front of device 100.

[0093] Device 100 also optionally includes one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternatively, accelerometer 168 is optionally coupled to input controller 160 in I / O subsystem 106. Accelerometer 168 optionally functions as described in U.S. Patent Application Publication No. 20050190059, "Acceleration-based Theft Detection System for Portable Electronic Devices," and U.S. Patent Application Publication No. 20060017692, "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer," both of which are incorporated herein by reference in their entireties. In some embodiments, information is displayed on the touchscreen display in portrait or landscape orientation based on an analysis of data received from the one or more accelerometers. In addition to accelerometer(s) 168, device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information about the position and orientation (e.g., vertical or horizontal) of device 100.

[0094] In some embodiments, software components stored in memory 102 include operating system 126, communications module (or instruction set) 128, touch / motion module (or instruction set) 130, graphics module (or instruction set) 132, text input module (or instruction set) 134, Global Positioning System (GPS) module (or instruction set) 135, and applications (or instruction sets) 136. Additionally, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) stores device / global internal state 157, as shown in FIGS. 1A and 3. Device / global internal state 157 includes one or more of: active application state indicating which applications, if any, are currently active; display state indicating which applications, views, or other information occupy various regions of touchscreen display 112; sensor state including information obtained from the device's various sensors and input control devices 116; and location information regarding the device's position and / or orientation.

[0095] Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and / or drivers that control and manage general system tasks (e.g., memory management, storage control, power management, etc.) and facilitate communication between various hardware and software components.

[0096] Communications module 128 facilitates communication with other devices via one or more external ports 124 and also includes various software components for processing data received by RF circuitry 108 and / or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted to couple to other devices directly or indirectly 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, similar to, and / or compatible with the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.

[0097] Contact / motion module 130, optionally in cooperation with display controller 156, detects contact with touchscreen 112 and other touch-sensing devices (e.g., a touchpad or physical click wheel). Contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact occurs (e.g., detecting a finger-down event), determining the intensity of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there is contact movement and tracking the movement across 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-up event or an interruption of the contact). Contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point, as represented by the series of contact data, optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point. These actions are optionally applied to a single contact (e.g., a single finger contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, contact / motion module 130 and display controller 156 detect contacts on the touchpad.

[0098] In some embodiments, contact / motion module 130 uses one or more sets of intensity thresholds to determine whether an action has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a particular physical actuator, but can be adjusted without modifying the physical hardware of device 100). For example, the mouse “click” threshold of a trackpad or touchscreen display can be set to any of a wide range of pre-defined thresholds without modifying the trackpad or touchscreen display hardware. Additionally, in some implementations, a user of the device is provided with a software setting to adjust one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once via a system-level click “intensity” parameter).

[0099] Contact / motion module 130 optionally detects gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or intensities of detected contacts). Thus, gestures are optionally detected by detecting particular contact patterns. For example, detecting a finger tap gesture includes detecting a finger down event, followed by detecting a finger up (lift off) event at the same location (or substantially the same location) as the finger down event (e.g., the location of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger down event, followed by one or more finger drag events, followed by detecting a finger up (lift off) event.

[0100] Graphics module 132 includes various known software components that render and display graphics on touchscreen 112 or other display, including components that vary the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics. As used herein, the term "graphic" includes any object that can be displayed to a user, including, but not limited to, text, web pages, icons (such as user interface objects including soft keys), digital images, video, animation, etc.

[0101] In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. Graphics module 132 receives one or more codes specifying the graphics to be displayed, including coordinate data and other graphic characteristic data, as needed, from an application or the like, and then generates screen image data to output to display controller 156.

[0102] The tactile feedback module 133 includes various software components for generating instructions used by the tactile output generator 167, which generates tactile outputs at one or more locations on the device 100 in response to a user's interaction with the device 100.

[0103] Text input module 134 is optionally a component of graphics module 132 and provides a soft keyboard for entering text in various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other application requiring text input).

[0104] The GPS module 135 determines the location of the device and provides this information for use within various applications (e.g., to the phone 138 for use in location-based dialing, to the camera 143 as picture / video metadata, and to applications that provide location-based services such as a weather widget, a local yellow pages widget, and a maps / navigation widget).

[0105] Application 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: ● a contacts module 137 (sometimes called an address book or contact list); ● Telephone module 138, ● Videoconferencing module 139; ● an email client module 140; ● Instant messaging (IM) module 141; ● Training support module 142, ● a camera module 143 for still images and / or video; ● Image management module 144; ● Video player module, ● Music player module, ● Browser module 147, ● Calendar module 148, • a widget module 149 optionally including one or more of a weather widget 149-1, a stocks widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets obtained by the user, and a user-created widget 149-6; ● a widget creator module 150 for creating user-created widgets 149-6; ● Search module 151, a video and music player module 152 that integrates a video player module and a music player module; ● Memo module 153, Map module 154, and / or ● Online video module 155.

[0106] Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice duplication.

[0107] Contacts module 137, in conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, is optionally used to manage an address book or contact list (e.g., stored in memory 102 or in the application internal state 192 of contacts module 137 in memory 370), which may include adding names to the address book, removing names from the address book, associating phone numbers, email addresses, physical addresses, or other information with names, associating images with names, categorizing and sorting names, providing phone numbers or email addresses to initiate and / or facilitate communication by telephone 138, videoconferencing module 139, email 140, or IM 141, etc.

[0108] Telephone module 138, in conjunction with 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, is optionally used to enter character sequences corresponding to telephone numbers, access one or more telephone numbers in contacts module 137, modify entered telephone numbers, dial respective telephone numbers, place calls, and disconnect and hang up when the call is completed. As previously mentioned, wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

[0109] Videoconferencing module 139 includes executable instructions to cooperate with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, light sensor 164, light sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contact module 137, and telephone module 138 to initiate, conduct, and end a videoconference between a user and one or more other participants according to the user's commands.

[0110] Email client module 140, in conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, contains executable instructions for composing, sending, receiving, and managing emails in response to user commands. In conjunction with image management module 144, email client module 140 greatly facilitates the creation and sending of emails with still or video images captured by camera module 143.

[0111] Instant messaging module 141 includes executable instructions, in cooperation with RF circuitry 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, for entering character sequences corresponding to instant messages, modifying previously entered characters, sending respective instant messages (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephony-based instant messaging, or XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, sent and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments, such as those supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0112] The training support module 142 includes executable instructions to cooperate with the RF circuitry 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module to create workouts (e.g., with time, distance, and / or calorie burn goals), communicate with training sensors (sports devices), receive training sensor data, calibrate sensors used to monitor workouts, select and play music for workouts, and display, store, and transmit workout data.

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

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

[0115] Browser module 147, in conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, contains executable instructions for browsing the Internet according to user commands, including retrieving, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0116] The calendar module 148 includes executable instructions to cooperate with the RF circuitry 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, the email client module 140, and the browser module 147 to create, display, modify, and store calendars and data associated with the calendars (e.g., calendar items, to-do lists, etc.) according to user instructions.

[0117] Widget module 149, 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, optionally provides mini-applications (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) downloaded and used by a user, or mini-applications created by a user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).

[0118] The widget creator module 150, in conjunction with the RF circuitry 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, and the browser module 147, is optionally used by a user to create a widget (e.g., turn a user-specified portion of a web page into a widget).

[0119] The search module 151 includes executable instructions for working in conjunction with the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134 to search for text, music, sound, images, video, and / or other files in the memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with a user's commands.

[0120] Video and music player module 152 includes executable instructions that, in conjunction with touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, enable a user to download and play pre-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 videos (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.).

[0121] The notes module 153 includes executable instructions for working with the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134 to create and manage notes, to-do lists, and the like according to user commands.

[0122] Map module 154, in conjunction with 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, is used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data regarding businesses and other points of interest at or near a particular location, and other location-based data), optionally in accordance with user instructions.

[0123] Online video module 155, in conjunction with touchscreen 112, display controller 156, contact / 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, contains instructions that enable a user to access, browse for, receive (e.g., by streaming and / or downloading), and play (e.g., on the touchscreen or on an external display connected via external port 124) particular online videos, send emails with links to particular online videos, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141 is used to send links to particular online videos, rather than email client module 140. For additional description of online video applications, see 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 entireties.

[0124] The above-identified modules and applications each correspond to sets of executable instructions that perform one or more of the functions previously described and methods described herein (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules; thus, in various embodiments, various subsets of these modules are optionally combined or otherwise reconfigured. For example, a video player module is optionally combined with a music player module into a single module (e.g., video and music player module 152 of FIG. 1A). In some embodiments, memory 102 optionally stores a subset of the above-identified modules and data structures. Furthermore, memory 102 optionally stores additional modules and data structures not described above.

[0125] In some embodiments, device 100 is a device in which operation of a predetermined set of functions on the device is performed solely via a touchscreen and / or touchpad. Using the touchscreen and / or touchpad as the primary input control device for operation of device 100 optionally reduces the number of physical input control devices (push buttons, dials, etc.) on device 100.

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

[0127] 1B is a block diagram illustrating exemplary components for event processing, according to some embodiments. In some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., within operating system 126) and a respective application 136-1 (e.g., any of applications 137-151, 155, 380-390 described above).

[0128] Event sorter 170 receives the event information and determines which application 136-1 to deliver the event information to and application view 191 for application 136-1. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192 that indicates the current application view that is displayed on touch-sensitive display 112 when the application is active or running. In some embodiments, device / global internal state 157 is used by event sorter 170 to determine which application(s) is currently active, and application internal state 192 is used by event sorter 170 to determine which application(s) is / are currently active, and application internal state 192 is used by event sorter 170 to determine which application view 191 to deliver the event information to.

[0129] In some embodiments, application internal state 192 includes additional information such as one or more of resume information to be used when application 136-1 resumes execution, user interface state information indicating or ready to display information being displayed by application 136-1, state cues that allow the user to return to a previous state or view of application 136-1, and redo / undo cues of previous actions taken by the user.

[0130] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about sub-events (e.g., a user touch as part of a multi-touch gesture on touch-sensitive display 112). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, accelerometer(s) 168, and / or microphone 113 (via audio circuitry 110). Information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

[0131] In some embodiments, event monitor 171 sends requests to peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receipt of an input that exceeds a predetermined noise threshold and / or exceeds a predetermined duration).

[0132] In some embodiments, event sorter 170 also includes a hit view determination module 172 and / or an active event recognizer determination module 173 .

[0133] Hit view determination module 172 provides software procedures that determine where a sub-event occurred within one or more views when touch-sensitive display 112 displays more than one view. A view consists of the controls and other elements that a user can see on the display.

[0134] Another aspect of a user interface associated with an application is the 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 respective application) in which the touch is detected optionally corresponds to a programmatic level within the application's programmatic or view hierarchy. For example, the lowest-level view in which the touch is detected is optionally referred to as the hit view, and the set of events that are recognized as appropriate inputs is optionally determined based at least in part on the hit view of the initial touch that initiates the touch gesture.

[0135] Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized hierarchically, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should process the sub-events. In most situations, the hit view is the lowest-level view in which an initiating sub-event occurs (e.g., the first sub-event in a sequence of sub-events that form an event or potential event). Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source as the touch or input source identified as the hit view.

[0136] Active event recognizer determination module 173 determines which view(s) in the view hierarchy should receive the particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive the particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that contain the physical location of the sub-event are actively participating views, and therefore all actively participating views should receive the particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely confined to the area associated with one particular view, views higher in the hierarchy still remain actively participating views.

[0137] Event dispatcher module 174 dispatches event information to event recognizers (e.g., event recognizer 180). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores event information obtained by each event receiver 182 in an event queue.

[0138] In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In still other embodiments, event sorter 170 is a stand-alone module or is part of another module stored in memory 102, such as contact / motion module 130.

[0139] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each containing instructions for processing touch events that occur within a respective view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, each application view 191 includes multiple event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, each event handler 190 includes one or more of data updater 176, object updater 177, GUI updater 178, and / or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or invokes data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in each application view 191.

[0140] Each event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes metadata 183 and at least a subset of event delivery instructions 188 (optionally including sub-event delivery instructions).

[0141] Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, e.g., a touch or a movement of a touch. Depending on the sub-event, the event information also includes additional information, such as the position of the sub-event. When the sub-event involves a movement of a touch, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape or vice versa), and the event information includes corresponding information about the current orientation of the device (also called the device's attitude).

[0142] The event comparator 184 compares the event information with predefined event or sub-event definitions and determines the event or sub-event, or determines or updates the state of the event or sub-event, based on the comparison. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 includes definitions of events (e.g., a predefined sequence of sub-events), such as Event 1 (187-1) and Event 2 (187-2). In some embodiments, sub-events within Event 1 (187) include, for example, touch start, touch end, touch movement, touch cancellation, and multiple touches. In one example, the definition for Event 1 (187-1) is a double tap on a displayed object. The double tap includes, for example, a first touch on a displayed object relative to a predetermined stage (touch start), a first lift-off (touch end) relative to the predetermined stage, a second touch on a displayed object relative to the predetermined stage (touch start), and a second lift-off (touch end) relative to the predetermined stage. In another example, a definition of event 2 (187-2) is a drag on a displayed object. Drag includes, for example, a touch (or contact) on the displayed object to a predetermined stage, a movement of the touch across the touch-sensitive display 112, and a lift-off of the touch (touch end). In some embodiments, the event also includes information about one or more associated event handlers 190.

[0143] In some embodiments, event definition 187 includes a definition of the event for each user interface object. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, if a touch is detected on touch-sensitive display 112 in an application view in which three user interface objects are displayed on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, event comparator 184 uses the results of the hit test to determine which event handler 190 to activate. For example, event comparator 184 selects the event handler associated with the sub-event and object that triggers the hit test.

[0144] In some embodiments, each event 187 definition also includes a delay action that delays transmission of the event information until it is determined whether the sequence of sub-events corresponds to the event type of the event recognizer.

[0145] If the respective event recognizer 180 determines that the sequence of sub-events does not match any of the events in the event definition 186, the respective event recognizer 180 enters an event-disabled, event-failed, or event-ended state and thereafter ignores the next sub-event of the touch-based gesture. In this situation, any other event recognizers that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

[0146] In some embodiments, each event recognizer 180 includes metadata 183 with configurable properties, flags, and / or lists that indicate to actively participating event recognizers how the event delivery system should perform sub-event delivery. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers interact with each other or how event recognizers are allowed to interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how sub-events are delivered to various levels in the view or programmatic hierarchy.

[0147] In some embodiments, each event recognizer 180 activates an event handler 190 associated with an event when one or more specific sub-events of the event are recognized. In some embodiments, each event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is separate from sending (and postponing sending) sub-events to the respective hit view. In some embodiments, the event recognizer 180 pops a flag associated with the recognized event, and the event handler 190 associated with the flag captures the flag and performs a predetermined process.

[0148] In some embodiments, the event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with a set of sub-events or to an actively participating view. The event handler associated with the set of sub-events or the actively participating view receives the event information and performs a predetermined process.

[0149] In some embodiments, data updater 176 creates and updates data used by application 136-1. For example, data updater 176 updates phone numbers used by contacts module 137 or stores video files used by a video player module. In some embodiments, object updater 177 creates and updates objects used by application 136-1. For example, object updater 177 creates new user interface objects or updates the positions 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 the touch-sensitive display.

[0150] In some embodiments, event handler(s) 190 include or have access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0151] It should be understood that the foregoing description of event processing of a user's touch on a touch-sensitive display also applies to other forms of user input for operating multifunction device 100 using input devices, although not all of them are initiated on a touchscreen. For example, mouse movements and mouse button presses, contact movements such as tapping, dragging, scrolling on a touchpad, optionally coordinated with single or multiple keyboard presses or holds, pen stylus input, device movement, verbal commands, detected eye movement, biometric input, and / or any combination thereof, are optionally utilized as inputs corresponding to sub-events that define the recognized event.

[0152] FIG. 2 illustrates portable multifunction device 100 having touchscreen 112, according to some embodiments. The touchscreen optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as other embodiments described below, a user may select one or more of the graphics by performing a gesture on the graphics, for example, using one or more fingers 202 (not drawn to scale) or one or more styluses 203 (not drawn to scale). In some embodiments, selection of one or more graphics is performed when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, upward and / or downward), and / or rolling (right to left, left to right, upward and / or downward) of a finger in contact with device 100. In some implementations or situations, accidental contact with a graphic does not select the graphic, for example, if the gesture corresponding to selection is a tap, a swipe gesture sweeping over an application icon optionally does not select the corresponding application.

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

[0154] In some embodiments, device 100 includes touchscreen 112, menu button 204, pushbuttons 206 for powering the device on / off and locking the device, volume adjustment buttons 208, subscriber identity module (SIM) card slot 210, headset jack 212, and external docking / charging port 124. Pushbutton 206 is optionally used to power the device on / off by pressing and holding the button down for a predetermined period of time, to lock the device by pressing and releasing the button before the predetermined time has elapsed, and / or to unlock the device or initiate the unlocking process. In alternative embodiments, device 100 also accepts verbal input via microphone 113 for activating or deactivating certain functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on touchscreen 112 and / or one or more tactile output generators 167 for generating a tactile output for a user of device 100.

[0155] FIG. 3 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface, according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or commercial 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 interconnecting these components. Communication bus 320 optionally includes circuitry (sometimes called a chipset) that interconnects and controls communication between system components. Device 300 includes input / output (I / O) interface 330, including display 340, which is typically a touchscreen display. I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 that generates tactile output on device 300 (e.g., similar to tactile output generator 167 described above with reference to FIG. 1A ), and sensors 359 (e.g., light, acceleration, proximity, touch-sensing, and / or contact intensity sensors similar to contact intensity sensor 165 described above with reference to FIG. 1A ). 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 magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU(s) 310.In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A). Additionally, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, ​​word processing module 384, website creation module 386, disk authoring module 388, and / or spreadsheet module 390, whereas memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

[0156] Each of the above-identified elements of FIG. 3 is optionally stored in one or more of the memory devices mentioned above. Each of the above-identified modules corresponds to an instruction set that performs the function described above. The above-identified modules or programs (e.g., instruction sets) need not be implemented as separate software programs, procedures, or modules; thus, in various embodiments, various subsets of these modules are optionally combined or otherwise reconfigured. In some embodiments, memory 370 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 370 optionally stores additional modules and data structures not described above.

[0157] Attention is now optionally directed to user interface embodiments, for example, as implemented on portable multifunction device 100.

[0158] 4A shows an exemplary user interface for a menu of applications on portable multifunction device 100, according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof: ● signal strength indicator(s) 402 for wireless communication(s), such as cellular and Wi-Fi signals; ● Time 404, ● Bluetooth indicator 405, ● Battery status indicator 406; A tray 408 with icons of frequently used applications, such as: o An icon 416 for the phone module 138, labeled "Phone", which optionally includes an indicator 414 of the number of missed calls or voicemail messages; an icon 418 for the email client module 140, labeled "Mail," which optionally includes an indicator 410 of the number of unread emails; ○ An icon 420 for the browser module 147, labeled "Browser"; and o An icon 422 for the video and music player module 152, also called the iPod (trademark of Apple Inc.) module 152, labeled "iPod"; and ● Icons of other applications, such as: ○ Icon 424 of IM module 141, labeled "Messages" ○ Icon 426 of the calendar module 148, labeled "Calendar" ○ Icon 428 in the image management module 144, labeled "Photos" ○ An icon 430 of the camera module 143, labeled "camera"; ○ Icon 432 of the online video module 155, labeled "Online Video"; Icon 434 of Stocks widget 149-2, labeled "Stock Prices" ○ Icon 436 of map module 154, labeled "Map" ○ Icon 438 of weather widget 149-1, labeled "Weather" ○ Icon 440 of alarm clock widget 149-4, labeled "Clock" ○ Icon 442 of Training Support module 142, labeled "Training Support"; icon 444 of the Notes module 153, labeled "Notes"; and o A settings application or module icon 446 labeled "Settings" that provides access to settings for the device 100 and its various applications 136.

[0159] 4A are merely exemplary. For example, icon 422 of video and music player module 152 is labeled "music" or "music player," although other labels are optionally used for various application icons. In some embodiments, the label for each application icon includes the name of the application corresponding to the respective application icon. In some embodiments, the label for a particular application icon is different from the name of the application corresponding to that particular application icon.

[0160] 4B shows an example user interface on a device (e.g., device 300 of FIG. 3 ) that has touch-sensitive surface 451 (e.g., tablet or touchpad 355 of FIG. 3 ) that is separate from display 450 (e.g., touchscreen display 112). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) that detect the intensity of a contact on touch-sensitive surface 451, and / or one or more tactile output generators 357 that generate a tactile output for a user of device 300.

[0161] Although some of the following examples are given with reference to input on touchscreen display 112 (which combines a touch-sensitive surface and a display), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, as shown in FIG. 4B . In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B ) has a primary axis (e.g., 452 in FIG. 4B ) that corresponds to a primary axis (e.g., 453 in FIG. 4B ) on the display (e.g., 450). According to these embodiments, the device detects contact with touch-sensitive surface 451 (e.g., 460 and 462 in FIG. 4B ) at locations that correspond to respective locations on the display (e.g., in FIG. 4B , 460 corresponds to 468 and 462 corresponds to 470). In this way, user input (e.g., contacts 460 and 462 and their movement) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B ) is used by the device to operate a user interface on the display (e.g., 450 in FIG. 4B ) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are optionally used for the other user interfaces described herein.

[0162] Additionally, while the following examples are given primarily with reference to finger input (e.g., finger contact, finger tap gesture, finger swipe gesture), it should be understood that in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (e.g., instead of a contact) followed by movement of a cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is optionally replaced by a mouse click (e.g., instead of detecting a contact and then ceasing contact detection) while the cursor is located over the location of the tap gesture. Similarly, it should be understood that when multiple user inputs are detected simultaneously, multiple computer mice are optionally used simultaneously, or a mouse and finger contacts are optionally used simultaneously.

[0163] FIG. 5A shows an exemplary personal electronic device 500. Device 500 includes a main body 502. In some embodiments, device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B ). In some embodiments, device 500 has a touch-sensitive display screen 504, hereafter touch screen 504. Alternatively, or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, touch screen 504 (or the touch-sensitive surface) optionally includes one or more intensity sensors that detect the intensity of contact (e.g., touches) being applied. The one or more intensity sensors of touch screen 504 (or the touch-sensitive surface) can provide output data representing the intensity of the touch. The user interface of device 500 can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface actions on device 500.

[0164] For exemplary techniques for detecting and processing touch intensity, see, for example, related applications International Patent Application No. PCT / US2013 / 040061, filed May 8, 2013, entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application," published as International Publication No. WO / 2013 / 169849, and International Patent Application No. PCT / US2013 / 069483, filed November 11, 2013, entitled "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships," published as International Publication No. WO / 2014 / 105276, each of which is incorporated herein by reference in its entirety.

[0165] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, may be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, may allow device 500 to be attached to, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch bands, chains, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow device 500 to be worn by a user.

[0166] FIG. 5B illustrates an exemplary personal electronic device 500. In some embodiments, device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, and 3. Device 500 has a bus 512 that operably couples an I / O section 514 to one or more computer processors 516 and a memory 518. I / O section 514 can be connected to a display 504, which can have touch-sensing components 522 and, optionally, an intensity sensor 524 (e.g., a contact intensity sensor). Additionally, I / O section 514 can be connected to a communication unit 530 that receives application and operating system data using Wi-Fi, Bluetooth, near-field communication (NFC), cellular, and / or other wireless communication technologies. Device 500 can include input mechanisms 506 and / or 508. Input mechanism 506 is optionally a rotatable input device or a depressible and rotatable input device, for example. In some examples, input mechanism 508 is optionally a button.

[0167] In some embodiments, input mechanism 508 is optionally a microphone. Personal electronic device 500 optionally includes various sensors, such as a GPS sensor 532, an accelerometer 534, an orientation sensor 540 (e.g., a compass), a gyroscope 536, a motion sensor 538, and / or combinations thereof, all of which may be operably connected to I / O section 514.

[0168] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, cause the computer processors to perform the techniques described below, including processes 700, 1000, 1300, 1500, 1600, and 1800 (FIGS. 7A-7B, 10, 13, 15, 16, and 18). A computer-readable storage medium may be any medium that can tangibly contain or store computer-executable instructions used by or in connection with an instruction execution system, apparatus, or device. In some embodiments, the storage medium is a transient computer-readable storage medium. In some embodiments, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic, optical, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and resident solid-state memory such as flash, solid-state drives, etc. Personal electronic device 500 is not limited to the components and configuration of Figure 5B and may include other or additional components in multiple configurations.

[0169] As used herein, the term "affordance" optionally refers to a user-interactive graphical user interface object displayed on a display screen of device 100, 300, and / or 500 (FIGS. 1A, 3, and 5A-5B). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) each, optionally, constitute an affordance.

[0170] As used herein, the term “focus selector” refers to an input element that indicates the current portion of the user interface with which the user is interacting. In some implementations involving a cursor or other position marker, the cursor acts as the “focus selector,” such that when input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 of FIG. 3 or touch-sensitive surface 451 of FIG. 4B) while the cursor is positioned over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations involving a touchscreen display (e.g., touch-sensitive display system 112 of FIG. 1A or touchscreen 112 of FIG. 4A) that allows direct interaction with user interface elements on the touchscreen display, a detected contact on the touchscreen acts as the “focus selector,” such that when input (e.g., a press input by contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, the particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one region of the user interface to another region of the user interface without a corresponding cursor movement or contact movement on the touchscreen display (e.g., by using the tab key or arrow keys to move focus from one button to another), and in these implementations, the focus selector moves to follow the movement of focus between various regions of the user interface. Regardless of the specific form the focus selector takes, the focus selector is generally a user interface element (or contact on a touchscreen display) that is controlled by the user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface through which the user intends to interact).For example, while a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of a focus selector (e.g., a cursor, touch, or selection box) over a corresponding button indicates that the user intends to activate that corresponding button (and not other user interface elements shown on the device's display).

[0171] As used herein and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of that contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predetermined number of intensity samples, i.e., a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a predetermined event (e.g., after detecting the contact, before detecting lift-off of the contact, before or after detecting the start of contact movement, before detecting the end of the contact, before or after detecting an increase in the intensity of the contact, and / or before or after detecting a decrease in the intensity of the contact). The characteristic intensity of the contact is optionally based on one or more of the maximum intensity of the contact, the mean intensity of the contact, the average intensity of the contact, the top 10 percentile intensity of the contact, half the maximum intensity of the contact, 90 percent of the maximum intensity of the contact, etc. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action is performed by the user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact having a characteristic intensity that does not exceed the first threshold results in a first action, a contact having a characteristic intensity that exceeds the first intensity threshold but not the second intensity threshold results in a second action, and a contact having a characteristic intensity that exceeds the second threshold results in a third action. In some embodiments, the comparison between the characteristic intensity and the one or more thresholds is not used to determine whether the first action or the second action should be performed, but rather is used to determine whether one or more actions should be performed (e.g., whether to perform the respective action or to forgo performing the respective action).

[0172] FIG. 5C illustrates detecting multiple contacts 552A-552E on the touch-sensitive display screen 504 by multiple intensity sensors 524A-524D. FIG. 5C additionally includes an intensity diagram illustrating the current intensity measurements of intensity sensors 524A-524D relative to intensity units. In this example, intensity sensors 524A and 524D each measure 9 intensity units, and intensity sensors 524B and 524C each measure 7 intensity units. In some implementations, the aggregate intensity is the sum of the intensity measurements of multiple intensity sensors 524A-524D, which in this example is 32 intensity units. In some embodiments, each contact is assigned a respective intensity that is a fraction of the aggregate intensity. FIG. 5D illustrates assigning aggregate intensities to contacts 552A-552E based on their distance from the center of force 554. In this example, contacts 552A, 552B, and 552E are each assigned a contact intensity of 8 intensity units of aggregate intensity, and contacts 552C and 552D are each assigned a contact intensity of 4 intensity units of aggregate intensity. More generally, in some implementations, each contact j is assigned a respective intensity Ij, which is a fraction of aggregate intensity A, according to a predetermined mathematical function Ij=A·(Dj / ΣDi), where Dj is the distance from the center of force to the respective contact j, and ΣDi is the sum of the distances from the center of force to all respective contacts (e.g., from i=1 to the end). The operations described with reference to FIGS. 5C-5D can be performed using electronic devices similar to or identical to device 100, 300, or 500. In some embodiments, the characteristic intensity of a contact is based on one or more intensities of the contact. In some embodiments, an intensity sensor is used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). Note that the intensity diagrams are not part of the displayed user interface, but are included in FIGS. 5C-5D as an aid to the reader.

[0173] In some embodiments, a portion of the gesture is identified for purposes of determining the characteristic intensity. For example, the touch-sensitive surface optionally receives successive swipe contacts that transition from a start position to an end position, where the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end position is optionally based on only a portion of the successive swipe contacts (e.g., only the portion of the swipe contact at the end position), rather than the entire swipe contact. In some embodiments, a smoothing algorithm is optionally applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of an unweighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some situations, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact for purposes of determining the characteristic intensity.

[0174] The intensity of a contact on the touch-sensitive surface is optionally characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device performs an action normally associated with clicking a physical mouse button or trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device performs an action different from an action normally associated with clicking a physical mouse button or trackpad. In some embodiments, when a contact is detected having a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is not detected), the device follows the movement of the contact on the touch-sensitive surface and moves the focus selector without performing an action associated with the light press intensity threshold or the deep press intensity threshold. In general, unless otherwise specified, these intensity thresholds are consistent across various sets of values ​​for a user interface.

[0175] An increase in the characteristic intensity of a contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold may be referred to as inputting a "light press." An increase in the characteristic intensity of a contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold may be referred to as inputting a "deep press." An increase in the characteristic intensity of a contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold may be referred to as detecting a contact on the touch surface. A decrease in the characteristic intensity of a contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold may be referred to as detecting a lift-off of the contact from the touch surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.

[0176] In some embodiments described herein, one or more actions are performed in response to detecting a gesture including a respective press input or in response to detecting a respective press input performed by a respective contact (or multiple contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or multiple contacts) above a press input intensity threshold. In some embodiments, the respective actions are performed in response to detecting an increase in intensity of the respective contact above a press input intensity threshold (e.g., a “downstroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above a press input intensity threshold followed by a decrease in intensity of the contact below the press input intensity threshold, and the respective actions are performed in response to detecting a subsequent decrease in intensity of the respective contact below the press input threshold (e.g., an “upstroke” of the respective press input).

[0177] 5E-5H illustrate the detection of a gesture including a press input corresponding to an increase in the intensity of contact 562 from an intensity below a light press intensity threshold (e.g., "ITL") in FIG. 5E to an intensity above a deep press intensity threshold (e.g., "ITD") in FIG. 5H. The gesture performed by contact 562 is detected on touch-sensitive surface 560, whereupon cursor 576 is displayed over application icon 572B corresponding to app2 on display user interface 570, which includes application icons 572A-572D displayed within predefined region 574. In some embodiments, the gesture is detected on touch-sensitive display 504. An intensity sensor detects the intensity of the contact on touch-sensitive surface 560. The device determines that the intensity of contact 562 peaks above the deep press intensity threshold (e.g., "ITD"). Contact 562 is maintained on touch-sensitive surface 560. In response to detecting the gesture, contact 562 having an intensity that exceeds a deep press intensity threshold (e.g., "ITD") during the gesture causes reduced-scale representations 578A-578C (e.g., thumbnails) of recently opened documents to App 2, as shown in FIGS. 5F-5H. In some embodiments, this intensity that is compared to one or more intensity thresholds is a characteristic intensity of the contact. Note that the intensity diagrams for contact 562 are not part of the displayed user interface, but are included in FIGS. 5E-5H as an aid to the reader.

[0178] In some embodiments, the display of representations 578A-578C includes animation. For example, as shown in FIG. 5F, representation 578A is first displayed adjacent to application icon 572B. As the animation progresses, representation 578A moves upward and representation 578B is displayed adjacent to application icon 572B, as shown in FIG. 5G. Then, as shown in FIG. 5H, representation 578A moves upward, representation 578B moves upward toward representation 578A, and representation 578C is displayed adjacent to application icon 572B. Representations 578A-578C form an array above icon 572B. In some embodiments, the animation progresses according to the intensity of contact 562, as shown in FIGS. 5F-5G, with representations 578A-578C appearing and moving upward as the intensity of contact 562 increases toward a deep press intensity threshold (e.g., "ITD"). In some embodiments, the intensity on which the animation progression is based is a characteristic intensity of the contact. The operations described with reference to FIGS. 5E-5H can be performed using an electronic device similar to or identical to device 100, 300, or 500.

[0179] In some embodiments, the device employs intensity hysteresis to avoid accidental input, sometimes referred to as “jitter,” and the device defines or selects a hysteresis intensity threshold that has a predetermined relationship to the press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units below the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the press input intensity threshold). Thus, in some embodiments, the press input includes an increase in the intensity of each contact above the press input intensity threshold followed by a decrease in the intensity of the contact below the hysteresis intensity threshold corresponding to the press input intensity threshold, and a respective action is performed in response to detecting a subsequent decrease in the intensity of each contact below the hysteresis intensity threshold (e.g., an “upstroke” of each press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the press input intensity threshold, and optionally a subsequent decrease in the intensity of the contact to an intensity below the hysteresis intensity, and a respective action is performed in response to detecting the press input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, as the case may be).

[0180] For ease of explanation, descriptions of operations performed in response to a press input associated with a press input intensity threshold, or a gesture including a press input, are optionally triggered in response to detecting any of: an increase in the intensity of the contact above the press input intensity threshold; an increase in the intensity of the contact from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold; a decrease in the intensity of the contact below the press input intensity threshold; and / or a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold. Further, in examples where an operation is described as being performed in response to detecting a decrease in the intensity of the contact below a press input intensity threshold, the operation is optionally performed in response to detecting a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to and lower than the press input intensity threshold.

[0181] As used herein, an "installed application" refers to a software application that has been downloaded onto an electronic device (e.g., device 100, 300, and / or 500) and is ready to run (e.g., opened) on the device. In some embodiments, a downloaded application becomes an installed application by an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the computer system's operating system.

[0182] As used herein, the terms "open application" or "running application" refer to a software application that has retained state information (e.g., as part of device / global internal state 157 and / or application internal state 192). An open or running application is, optionally, any one of the following types of application: ● the active application currently displayed on the display screen of the device on which the application is being used; Background applications (or background processes) that are not currently displayed, but for which one or more processes are being processed by one or more processors; and A suspended or hibernated application that is not running but has state information stored in memory (volatile and non-volatile, respectively) and that can be used to resume execution of the application.

[0183] As used herein, the term "closed application" refers to a software application that does not have retained state information (e.g., state information for a closed application is not stored in the device's memory). Thus, closing an application includes stopping and / or removing the application process for the application and removing state information for the application from the device's memory. Generally, opening a second application during a first application does not close the first application. When the second application is displayed and the first application is terminated, the first application becomes a background application.

[0184] Attention is now directed to embodiments of user interfaces (“UIs”) and related processes implemented on an electronic device such as portable multifunction device 100, device 300, or device 500.

[0185] 6A-6AL show exemplary user interfaces for monitoring audio exposure levels, according to some embodiments. The user interfaces in these figures are used to explain processes described below, including the processes in FIGS. 7A-7B.

[0186] 6A , device 600 includes a display 602 (e.g., a display device), a rotatable and depressible input mechanism 604 (e.g., rotatable and depressible relative to a housing or frame of the device), and a microphone 606. In some embodiments, device 600 is a wearable electronic device such as a smart watch. In some embodiments, device 600 includes one or more features of devices 100, 300, or 500.

[0187] 6A , clock user interface 608A includes a digital display of time 610 (e.g., a representation of a digital clock displaying the current hour and minute values) and a digital display of multiple affordances, each associated with an application stored on device 600. Date affordance 612 indicates the current date and launches a calendar application when selected. Remote affordance 614 launches a remote control application (e.g., an application to a control device external to device 600) when selected. Heart rate affordance 616 launches a heart rate monitoring application when selected.

[0188] 6A , watch user interface 608A (e.g., a watch face interface) also includes multiple noise application affordances that, when selected, launch a noise monitoring application (e.g., a noise icon 618, a noise state affordance 620, a noise meter affordance 622, and a compact noise affordance 624). As shown in FIG. 6A , the noise application on device 600 is not installed or initialized (e.g., not enabled), and as a result, noise state affordance 620, noise meter affordance 622, and compact noise affordance 624 do not indicate (e.g., display) any noise data from the noise application. Instead, for example, device 600 displays noise state affordance 620 as a setup prompt (e.g., “tap to setup”) indicating that the noise application needs to be initialized.

[0189] FIG. 6A shows device 600 receiving user input 628A (e.g., a tap) on noise state affordance 620. In response to detecting user input 628A, device 600 displays user interface 608B, as shown in FIG. 6B. User interface 608B includes a description of the functionality of the noise application, an enable affordance 630 for enablement (e.g., initializing the noise application), and a disable affordance 632 for disablement (e.g., maintaining the noise application in an uninitialized state). FIG. 6B shows device 600 receiving user input 628B (e.g., a tap) on enable affordance 630. In response to receiving user input 628B, device 600 displays user interface 608C (e.g., an interface associated with the noise application), as shown in FIG. 6C.

[0190] As shown in FIGS. 6C (and 6D-6G), user interface 608C includes a display of time 634 (e.g., showing the current time of 10:09), a noise level indicator 636, a noise meter indicator 638, and a noise status indicator 640. Noise level indicator 636 provides a numerical representation of a first noise level value (e.g., 34 DB) (e.g., measured or determined by device 600 from noise data derived from microphone 606). Noise status indicator 640 provides a non-numeric representation (e.g., an indicator including graphics and / or text) of the first noise level value (e.g., measured or determined by device 600 from noise data derived from microphone 606) relative to a first level threshold (e.g., a predetermined 80 DB threshold). In some embodiments, the first noise level threshold is user-configurable. In some embodiments, the device identifies a noise level based on noise data detected by a sensor (e.g., microphone) of the electronic device (e.g., the first noise level represents the noise level of the physical environment in which the device is located).

[0191] The noise meter indicator 636 provides a graphical display of the second noise level (e.g., measured by the device 600 via the microphone 606). In some embodiments, the second noise level and the first noise are the same noise level. In some embodiments, the first noise level and the second noise level are determined based on common noise data sampled at different periods and / or rates (e.g., 1 second and 0.1 seconds, respectively). The noise meter indicator 638 includes an active portion 638A (e.g., a visually highlighted portion) whose size and / or color change according to the second noise level. As shown in the following figures, the size of the active portion 638A increases as the noise level increases, and the color of the active portion 638A changes relative to the second threshold level. In some embodiments, the size includes the number of visually highlighted segments, the relative area occupied by the set of visually highlighted segments, or the position of the rightmost edge of the set of visually highlighted segments relative to the scale. In some embodiments, each highlighted segment in the active portion 638A represents a predetermined number of decibels (e.g., 10 dB), and in some embodiments, the first threshold level and the second threshold level are the same level (e.g., 80 dB).

[0192] The noise level (e.g., value, amplitude) indicated by the appearance of noise level indicator 636, noise meter indicator 638, and noise status indicator 640 (e.g., as described below) is updated in response to device 600 determining one or more noise levels based on received noise data (e.g., the indication updates as the ambient noise level is continuously determined or measured by device 600). In some embodiments, the noise level is measured or detected by a device external to device 600 (e.g., device 600 receives data representing the current noise level from a remote device communicatively coupled to device 600).

[0193] FIG. 6C illustrates the state of user interface 608C while device 600 is in an environment with a consistent noise level of 34 dB at the time of 10:09 (e.g., device 600 is located in a low-noise environment, such as a computer lab). Accordingly, as shown in FIG. 6C, noise level indicator 636 includes a “34 dB” value, and noise status indicator 640 includes a non-cautionary prompt (e.g., a checkmark graphic, “OK,” and an explanatory prompt indicating the relatively low risk associated with exposure at the level indicated by noise level indicator 636) indicating that the noise level is below a threshold level (e.g., 80 dB). Similarly, as shown in FIG. 6C, noise meter indicator 638 provides a graphical indication of a low, consistent noise level by displaying active portion 638A at a size corresponding to two green segments (e.g., green represented by diagonal hatching). In some implementations, the two segments may be distinguished differently to indicate that a low, consistent noise level is acceptable.

[0194] FIG. 6D illustrates the state of user interface 608C in response to a sudden increase (e.g., within 200 milliseconds of a spike) in ambient noise (e.g., a firing alarm sounds inside the computer lab). As shown in FIG. 6D, the size of the active portion 638A of noise meter indicator 638 has increased from 2 segments to 10 segments, and the color has transitioned from green to yellow (e.g., yellow represented by horizontal hatching). In some implementations, instead of a color transition from green to yellow, the segments may be differentiated in a different manner to indicate that the noise level has transitioned to a level requiring user attention. As illustrated, noise level indicator 636 and noise status indicator 640 maintain their previous appearance (e.g., as shown in FIG. 6C).

[0195] As described above, the appearance of noise level indicator 636 and noise status indicator 640 changes based on a first noise level (e.g., a noise level based on a longer 1-second period of noise level data), and the appearance of noise meter indicator 638 changes based on a second noise level (e.g., a noise level based on a shorter 0.1-second period of noise level data). As a result, the graphical meter changes more quickly (e.g., instantly) in response to sudden changes in the ambient noise level than noise level indicator 636 (and noise status indicator 640). This lag effect is indicated by the difference in the noise levels represented by noise level indicator 636, noise status indicator 640, and noise meter 638. In some embodiments, slower updates make it easier for a user to interpret (e.g., read) the displayed noise level, while the faster update behavior of graphical meter 638 provides more timely (e.g., responsive) visual feedback to the user.

[0196] 6E illustrates the state of user interface 608C after a sustained high noise level (e.g., a firing alarm continues to sound for one minute). As shown in FIG. 6E, the size and color of the active portion 638A of noise meter indicator 638 remain unchanged (e.g., compared to the depiction in FIG. 6D). However, noise level indicator 636 and noise status indicator 640 have been updated to reflect the sustained elevated ambient noise level (e.g., noise level indicator 636 indicates a 113 dB level, and noise status indicator 640 includes an advisory (e.g., "loud") prompt indicating a noise level above the 80 dB threshold).

[0197] FIG. 6F illustrates the state of the user interface 608C in response to a sudden drop in the ambient noise level (e.g., a blaring alarm suddenly stops). As shown in FIG. 6F, the size of the active portion 638A of the noise meter indicator 638 is reduced from 10 segments to 6 segments, and the color is changed from yellow to green (e.g., green represented by diagonal hatching). In some implementations, instead of a color transition from yellow to green, the segments may be differentiated in a different manner to indicate that the noise level has transitioned from a level requiring the user's attention to a normal level that poses less risk to the user's hearing. As illustrated, the noise level indicator 636 and the noise status indicator 640 maintain their previous appearance (e.g., as shown in FIG. 6E).

[0198] 6G shows the state of user interface 608C after the reduced noise level has been sustained (e.g., for a period of more than 1 second). As shown in FIG. 6G, the size and color of the active portion 638A of noise meter indicator 638 remain unchanged (e.g., compared to the depiction in FIG. 6F). However, noise level indicator 636 and noise status indicator 640 have been updated to reflect the reduced ambient noise level (e.g., noise level indicator 636 indicates a 78 DB level, and noise status indicator 640 includes a non-attentional prompt (e.g., "OK") indicating a noise level below the 80 DB threshold).

[0199] In response to determining that the noise level exceeds a notification level threshold (e.g., 80 dB, 85 dB, 90 dB) for a period of time (e.g., 3 minutes), device 600 emits a haptic alert 642, as shown in Figure 6H. In some embodiments, the noise data used to determine the noise level value is sampled at a first rate while device 600 displays graphical noise meter indicator 620 (e.g., Figures 6C-6E) and noise meter affordance 622 (e.g., Figures 6K-6N) is sampled at a second rate (e.g., a lower sampling rate, 20% lower), while device 600 does not display graphical noise meter indicator 638 or noise meter affordance 622 (e.g., Figure 6H).

[0200] Following outputting the haptic alert 642, the device 600 displays the noise notification user interface 608D of FIG. 6I (e.g., a warning notification). As shown in FIG. 6I, the noise notification user interface 608D includes a description of the notification trigger condition (e.g., "approximately 1 / 3 of 110 DB") and the associated risk of hearing loss. FIGS. 6I and 6J show the device 600 receiving user inputs 628C and 628D (e.g., scroll inputs) at the rotatable and depressible mechanism 604. In response to receiving the user inputs, the device 600 displays additional portions of the noise notification user interface 608D.

[0201] 6K, noise notification user interface 608D includes a noise app affordance 644 for launching a noise application, multiple mute affordances 646 for suppressing the display of subsequent noise notifications (e.g., display of user interface 608D) for a specific period of time (e.g., an hour and the remainder of the day), and a dismiss affordance 648. FIG. 6K shows device 600 receiving user input 628E (e.g., a tap) corresponding to dismiss affordance 648. In response to receiving user input 628E, device 600 displays (e.g., redisplays) clock user interface 608A. In some embodiments, selection of dismiss affordance 648 causes device 600 to suppress subsequent notifications for a predetermined automatic suppression period (e.g., 30 minutes) (e.g., refrain from displaying notification user interface 608D despite a notification trigger condition being detected by device 600). In some embodiments, the notification user interface 608D includes a graphical display of the noise exposure level (eg, a noise meter indicator 638).

[0202] 6L, noise state affordance 620, noise meter affordance 622, and compact noise affordance 624 now display noise level data associated with the noise application (e.g., because the noise application was initialized via user input 628B). The appearance of noise state affordance 620, noise meter affordance 622, and compact noise affordance 624 mirrors the functionality provided by noise level indicator 636, noise meter indicator 638, and noise state indicator 640 (e.g., described below with reference to FIGS. 6C-6G).

[0203] FIG. 6L illustrates the state of the clock user interface 608A while the device 600 is in an environment with a consistent noise level of 34 dB at 10:18 (e.g., the device 600 is located in a low-noise environment, such as a library). Accordingly, as shown in FIG. 6L, the noise state affordance 620 includes a “34 dB” value and a non-attentional prompt (e.g., a checkmark graphic and “OK”) indicating that the noise level is below a threshold level (e.g., 80 dB). As shown in FIG. 6L, the noise meter affordance 622 provides a graphical indication of the low noise level by displaying the active portion 622A in a size corresponding to four segments (outside of the 23 segments) of green (e.g., green represented by diagonal hatching). Similar to the active portion 638A of the noise meter indicator 638, the size of the active portion 622A is proportional to the noise level, and the color (e.g., green) indicates the noise level relative to a threshold level (e.g., green and yellow). In some implementations, the indication of noise level relative to the threshold level may be a different color or other non-color distinguishing indication.

[0204] 6L, compact noise affordance 624 displays a combination of the information represented by noise meter affordance 622 and noise state affordance 620. Specifically, as shown in FIG. 6L, compact noise affordance includes a graphical representation of a low noise level by displaying active portion 624A at a size corresponding to 2 segments (out of 11 segments) in green (e.g., green represented by diagonal hatching, representing a noise level below a threshold), numeric portion 624B includes a value (e.g., 34 DB), and graphic portion 624C includes an inattentional graphic (e.g., a checkmark graphic) corresponding to the value indicated by noise state affordance 620.

[0205] FIG. 6M illustrates the state of user interface 608A in response to a sudden increase (e.g., a spike) in ambient noise at time 10:19. As shown in FIG. 6M, the size of active portion 622A of noise meter affordance 622 increases from 4 segments to 17 segments, and the color of active portion 622A transitions from green to yellow (e.g., yellow, represented by horizontal hatching, transitions from a noise level below the threshold to a noise level at which the user should exercise listening attention). Similarly, as shown in FIG. 6M, the size of active portion 624A of compact noise affordance 624 increases from 2 segments to 8 segments, and the color changes from green to yellow. In contrast, noise level state affordance 620, numeric portion 624B, and graphical portion 624C maintain their previous appearance (e.g., as shown in FIG. 6L).

[0206] FIG. 6N illustrates the state of user interface 608A after sustained high noise levels (e.g., for three minutes). As shown in FIG. 6N, the size and color of active portion 622A of noise meter affordance 622 remain unchanged (e.g., compared to the depiction in FIG. 6M). However, noise state affordance 620, numerical portion 624B, and graphical portion 624C have been updated to reflect the sustained elevated ambient noise level. Notably, immediately after displaying user interface 608A as shown in FIG. 6N (e.g., after device 600 detects and displays a sustained noise level of 110 dB for three minutes and then detects and displays the aforementioned notification trigger condition), device 600 does not output a haptic alert (e.g., FIG. 6H) or a displayed noise notification user interface 608D (e.g., FIG. 6I) because the previous notification was dismissed within the automatic suppression period (e.g., 30 minutes).

[0207] FIG. 6O illustrates user interface 608A while device 600 is operating in a paused state (e.g., not currently measuring or detecting noise levels). As shown in FIG. 6O, while in the paused state, user interface 608A does not show noise level values, and noise state affordance 620 and graphical portion 624C appear in an alternate form to indicate the paused state of device 600. In some embodiments, noise measurement is paused upon detection of various operating conditions (e.g., water lock mode on, active phone call, speaker in use, or the watch being removed from the wrist (unless the watch is manually unlocked)). In some embodiments, notifications (e.g., display of user interface 608D) may be disabled without pausing noise measurement. In some embodiments, noise measurement is disabled when the noise application feature is disabled (e.g., via device privacy settings or noise app settings).

[0208] 6P-6U illustrate a device 600 displaying an exemplary clock user interface, including noise application affordances and elements corresponding to those described above in connection with FIGS. 6A-6O.

[0209] 6V-6Y show device 600 displaying an exemplary user interface reflecting device 600 in a paused state.

[0210] 6Z-6AC show a series of user interfaces associated with configuring a noise level threshold (e.g., a noise level threshold corresponding to the thresholds described above in connection with FIGS. 6A-6O) from device 600 or from an external device 601 coupled (e.g., wirelessly) to device 600.

[0211] 6AD-6AE show user interfaces for enabling and disabling noise measurement on device 600. FIG.

[0212] 6AF-6AL illustrate various interfaces for initializing or enabling a noise monitoring application (eg, as described above with respect to FIGS. 6A-6O).

[0213] 7A-7B are flow diagrams illustrating a method for monitoring noise levels using an electronic device, according to some embodiments. Method 700 is performed on an electronic device (e.g., 100, 300, 500, 600, 601, 800, 900, 1100, 1200, 1400, 1401, and 1700) having a display device (e.g., 602). In some embodiments, the electronic device also includes a set of sensors (e.g., an accelerometer, a gyroscope, a GPS, a heart rate sensor, a barometer, a microphone, a pressure sensor, an ambient light sensor, an ECG sensor). In some embodiments, the electronic device is a wearable device having an attachment mechanism such as a band. Some operations of method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0214] In some embodiments, the electronic device (e.g., 100, 300, 500, 600, 601, 800, 900, 1100, 1200, 1400, 1401, and 1700) is a computer system. The computer system is optionally in communication (e.g., wired communication, wireless communication) with a display generation component and one or more input devices. The display generation component is configured to provide a visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. The one or more input devices are configured to receive input, such as a touch-sensitive surface that receives user input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system. Thus, the computer system can transmit data (e.g., image data or video data) via wired or wireless connections to an integrated or external display generation component to visually generate content (e.g., using a display device), and can receive input from one or more input devices via wired or wireless connections.

[0215] As described below, method 700 provides an intuitive way to manage noise exposure levels. This method reduces the cognitive burden on a user attempting to monitor the noise levels (e.g., environmental noise levels) to which the user is exposed throughout the day, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling users to monitor noise exposure levels more quickly and efficiently conserves power and extends the time between battery charges.

[0216] The electronic device (e.g., 600) displays (712) via a display device a first user interface (e.g., a clock face user interface or an application user interface) that includes a graphical object (e.g., a meter) that changes appearance based on the noise level.

[0217] In some embodiments, pursuant to determining that a set of noise notification criteria has been met at a first time point prior to displaying the first user interface (e.g., 608A, 608C), the criteria being met when the current noise level over a third time period (e.g., an average value of the current noise level over the third time period) exceeds a third threshold noise level (e.g., 80 dB, 85 dB, 90 dB) (e.g., the average noise level exceeds the threshold for at least 3 minutes), the electronic device displays (702) a noise level notification (608D) that includes: an indication of the current noise level over the third time period (e.g., text indicating that the current noise level over the third time period exceeded the third threshold noise level; text indicating the amount of time the current noise level exceeded the third threshold noise level) (704), and a third affordance (e.g., “open noise”) (e.g., 644) (706). In some embodiments, the third threshold level is the same as the first or second threshold level. In some embodiments, the set of noise notification criteria includes a second criterion that is met when the current noise level exceeds a third threshold noise level for at least a third time period. In some embodiments, while displaying a third affordance (e.g., 644), the electronic device receives user input corresponding to the third affordance (708). In some embodiments, in response to receiving user input corresponding to the third affordance, the electronic device displays a first user interface (e.g., 608C) (710) (e.g., opening a Noise app). Displaying a noise level notification (e.g., automatically) pursuant to determining that the set of noise notification criteria is met provides the user with quick and easy access to information regarding the current noise exposure level. Taking action when a set of conditions is met without requiring further user input enhances device usability and makes the user device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

[0218] In some embodiments, the set of noise notification criteria is not met when a second noise notification level is displayed within a predetermined time (e.g., 30 minutes) before the first time point (e.g., 10:17 as shown in FIG. 6I). In some embodiments, subsequent noise level notifications are suppressed for a period of time after issuing the previous noise level notification. Suppressing subsequent noise level notifications for a period of time after issuing the previous noise level notification prevents the electronic device from providing unnecessarily redundant notifications, thereby improving device usability and making the user device interface more efficient, as well as allowing the user to use the device more quickly and efficiently, thereby reducing device power usage and improving battery life. In some embodiments, notifications displayed within a predetermined period of time after the first time point are not suppressed if the noise level remains below a threshold for a period of time (e.g., 15 minutes) after the first time point.

[0219] In some embodiments, the noise level notification (e.g., 608D) further includes a fourth affordance (e.g., 646) associated with a second predetermined time period, wherein the electronic device receives an input corresponding to the fourth affordance, and in response to receiving the input corresponding to the fourth affordance, the electronic device refrains from displaying (e.g., suppresses display of) further instances of the noise level notification for the second predetermined time period (e.g., 1 hour, 1 / 2 hour, remainder of the day). Providing a fourth affordance within the noise level notification that allows a user to cause the electronic device to refrain from displaying further instances of the noise level notification allows the user to quickly and easily suppress further noise level notifications on the electronic device. Providing additional control options without cluttering the UI with additional displayed controllers enhances device usability and makes the user device interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the device), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

[0220] The electronic device receives (714) first noise level data (e.g., noise level data corresponding to a noise level over a first time period, an average value over the first time period, or multiple data points representing a noise level over the first time period) (e.g., noise level "34 DB" in FIG. 6C ) corresponding to a first noise level (e.g., data from a sensor of the electronic device, data from an external electronic device) below a threshold noise level (e.g., 80 dB). In some embodiments, the first noise level data over the first time period represents an instantaneous noise level.

[0221] In response to receiving the first noise level data, the electronic device displays (716) a graphical object (e.g., 622, 638) having an active portion (e.g., an emphasized or visually distinguishable portion based on appearance) (e.g., 622A, 638A) of a first size (e.g., the number, length, or area of ​​segments relative to the overall size of the object proportional to the noise level) based on the first noise data and a first color (e.g., green). In some embodiments, the active portion extends from a left edge of the graphical object to a position between the left and right edges of the graphical object. In some embodiments, the graphical object includes an indication of the first noise level data other than the size of the active portion (e.g., a numerical value, the position of a point or line along an axis of a graph). Displaying a graphical object having an active portion of a first size based on the first noise data and a first color provides a user with easily recognizable and understandable noise exposure level information. Providing improved visual feedback to the user improves usability of the device, makes the user device interface more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the device and reducing user errors), and also reduces power usage and improves battery life of the device by allowing the user to use the device more quickly and efficiently.

[0222] While maintaining the display of the first user interface, the electronic device receives (718) second noise level data corresponding to a second noise level that is different from the first noise level (e.g., the second noise level is either lower than the first noise level or higher than the first noise level) (e.g., noise level “113 DB” in FIG. 6E).

[0223] In response to receiving the second noise level data (720), the electronic device displays the active portion (722) at a second size based on a second noise level that is different from the first size (e.g., the active portion grows or shrinks corresponding to the difference between the first and second noise levels) (e.g., 638A in FIG. 6D ). Displaying the active portion at a second size based on the second noise level in response to receiving the second noise level data allows a user to quickly and easily visually distinguish between the noise exposure level information corresponding to the first and second noise level data. Providing the user with improved visual feedback improves device usability, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and additionally reduces power usage and improves the device's battery life by allowing the user to use the device more quickly and efficiently.

[0224] In response to receiving the second noise level data (720), in accordance with a determination that the second noise level exceeds a threshold noise level (e.g., the noise level has increased beyond an 80 dB threshold), the electronic device displays (724) the active portion (e.g., 638A in FIG. 6D ) in a second color different from the first color (e.g., a change from green to yellow) in accordance with a determination that the second noise level exceeds the threshold noise level. Displaying the active portion in a second color different from the first color in accordance with a determination that the second noise level exceeds the threshold noise level provides visual feedback to the user that the noise exposure level has exceeded a particular threshold. Providing improved visual feedback to the user improves device usability, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and additionally reduces power usage and improves device battery life by allowing the user to use the device more quickly and efficiently.

[0225] In response to receiving (720) the second noise level data, in accordance with a determination that the second noise level does not exceed the threshold noise level (e.g., the noise level remains below the 80 dB threshold), the electronic device maintains (726) the display of the graphical object in the first color (e.g., as green).

[0226] In some embodiments, while displaying the graphical object having the active portion at a second size and a second color (e.g., yellow), the electronic device receives third noise level data (728) corresponding to a third noise level below a threshold noise level (e.g., the noise level has decreased to below an 80 dB threshold). In some embodiments, in response to receiving the third noise level data, the electronic device displays the active portion at a third size based on the third noise level data that is less than the second size and in a first color (730) (e.g., the active portion shrinks and changes from yellow to green corresponding to the difference between the second noise level and the third noise level) (e.g., 638A in FIG. 6F ). Displaying the active portion at a third second size based on the third noise level in response to receiving the third noise level data allows a user to quickly and easily visually distinguish between noise exposure level information corresponding to the first noise level data and the second noise level data and noise exposure level information corresponding to the third noise level data. Providing improved visual feedback to the user improves usability of the device, makes the user device interface more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the device and reducing user errors), and also reduces power usage and improves battery life of the device by allowing the user to use the device more quickly and efficiently.

[0227] In some embodiments, the graphical object changes based on the noise level over a first period of time (e.g., an average of the noise level over a 0.1 second window), and the first user interface further includes a second graphical object (e.g., a text display, a graphical display) (e.g., 620, 624, 636, 640) that changes appearance based on the noise level over a second period of time that is different from the first period of time (e.g., averaged over a 1 second window).

[0228] In some embodiments, displaying the first user interface includes displaying a first affordance that, when selected, displays a second user interface (e.g., an interface having information about the threshold noise level) (e.g., 640) pursuant to a determination that the current noise level (e.g., based on the noise data for the first time period or the noise data for the second time period) is below a second threshold noise level (e.g., a user-selected threshold). In some embodiments, the first affordance includes "OK" or a graphical element (e.g., a check mark) when the noise level is below the threshold (e.g., 640 in FIGS. 6C, 6D, 6G; 620 in FIGS. 6L-6M). In some embodiments, the first threshold and the second threshold are the same.

[0229] In some embodiments, displaying the first user interface includes displaying a second affordance different from the first affordance (e.g., without displaying the first affordance) that, when selected, displays a third user interface (e.g., the same as the second user interface; different from the first user interface, having information regarding the threshold noise level) pursuant to a determination that the current noise level exceeds the second threshold noise level. In some embodiments, the first affordance includes "large" or a graphical element (e.g., an exclamation point) when the noise level is at or above the threshold.

[0230] In some embodiments, the electronic device includes one or more noise sensors (e.g., one or more pressure-sensing devices such as a microphone or microphone array) (e.g., 606), and the first noise level data and the second noise level data are received from the one or more noise sensors. In some embodiments, the display device and the one or more noise sensors are located within a common housing or body of the electronic device, and the first noise level data and the second noise level data represent the noise level of a physical environment in which the electronic device is located.

[0231] In some embodiments, the first noise level data and the second noise level data are received from a second electronic device different from the first electronic device (e.g., the noise level data is received at the electronic device displaying the UI from a device external to the electronic device displaying the UI).

[0232] In some embodiments, while the first user interface is displayed (e.g., 608A, 608C), the electronic device samples noise level data at a first sampling rate (e.g., receives new noise level data at a first rate). In some embodiments, while the first user interface is not displayed (e.g., as shown in 608B, 608D and generally by FIGS. 6H, 6P-6S, 6AA-6AI), the electronic device samples noise level data at a second sampling rate that is different from the first sampling rate. In some embodiments, the first noise level data and the second noise level data are separated by a first time interval. While the first user interface is not displayed, noise level data is received at a second time interval that is longer than the first time interval. In some embodiments, the second sampling rate is 20% of the first sampling rate. By automatically sampling the noise level data at a second sampling rate different from the first sampling rate when the first user interface is not displayed as opposed to when the first user interface is displayed, the electronic device reduces power usage and thus improves battery life of the device.

[0233] It should be noted that the details of the processes described above with respect to method 700 (e.g., FIGS. 7A-7B) are also applicable in an analogous manner to the methods described below. For example, method 1000 optionally includes one or more of the features of the various methods described above with reference to method 700. For example, information regarding noise exposure levels corresponding to one or more of the output devices described in method 1000 can be presented or provided to a user using the above-described graphical displays (e.g., graphical objects) that change appearance based on the noise exposure levels. For the sake of brevity, these details will not be repeated below.

[0234] 8A-8L show device 800 displaying user interfaces (e.g., user interfaces 808A-808F) on display 802 for accessing and displaying environmental noise exposure data (e.g., sets of data representing a device user's exposure to noise at various sound intensities). In some embodiments, the environmental noise exposure data is received at device 800 from sensors in device 800 or from an external device (e.g., device 600, described above). In some embodiments, the environmental noise exposure data is manually entered by a device user (e.g., via a series of user inputs detected by device 800).

[0235] 8A and 8B show a user interface within a wellness application for accessing environmental noise data. Figures 8A and 8B show device 800 receiving inputs (e.g., 806A and 806B) at ambient audio level affordances 804A and 804B, respectively. Upon detecting these inputs, device 800 displays data viewing interface 808C, as shown in FIG. 8C.

[0236] 8C-8I illustrate various techniques for displaying and manipulating stored environmental noise data via a user interface 808 C. As shown in FIGS. 8C-8I, the user interface 808 C includes a chart 805 that displays environmental noise exposure data (e.g., the amplitude or level of noise to which a user associated with the device 800 has been exposed) over a selectable period of time (e.g., day, week, month, year).

[0237] 8C-8D, environmental noise exposure data associated with a particular time period (e.g., a day of the week) on chart 805 is selected (e.g., via user input 806C). In response to the selection, user interface 808C displays additional information about the selected environmental noise exposure data (e.g., details affordance 812). In response to the selection, the device also displays data overlay 810 at a location on chart 805 that corresponds to the selected environmental noise exposure data to provide a visual display of the data corresponding to the information displayed by details affordance 812.

[0238] As shown in FIGS. 8C-8I, user interface 808C includes various affordances (e.g., average affordance 814, daily average affordance 820, range affordance 822, notification affordance 826) for manipulating the data displayed by chart 805. As shown in FIGS. 8D-8E, in response to receiving user input 806D at average affordance 814, device 800 displays average overlay 810B (e.g., a visual reference to the average environmental noise exposure level calculated over the displayed time period). As shown in FIGS. 8E-8F, in response to detecting selection of average overlay 810B (e.g., user input 806E), device 800 displays average detail affordance 818. As shown in FIGS. 8F-8G, in response to detecting selection of average overlay 810B (e.g., user input 806E), device 800 displays average detail affordance 818. 8F-8G, in response to receiving user input 806F at daily average affordance 820, device 800 displays daily average overlay 810C (e.g., a visual reference to the average environmental noise exposure level calculated each day). In some embodiments, device 800 displays noise classification affordance 816 (as shown in FIG. 8E) in response to determining that the average noise exposure level (e.g., as indicated by average overlay 810B) exceeds a threshold level (e.g., 80 DB). In some embodiments, in response to determining that the average noise exposure level (e.g., as indicated by average overlay 810B) falls below a threshold level (e.g., 80 DB), the device displays noise classification affordance 816 with a different appearance (e.g., the affordance behaves similarly to noise state affordance 620 or noise state indicator 640 described above with respect to FIGS. 6A-6O).

[0239] As shown by Figures 8G-8H, in response to receiving user input 806G at range affordance 822, device 800 displays maximum level indicator 824A and minimum level indicator 824B (e.g., visual references to the highest and lowest noise exposure levels within the displayed environmental noise level data on chart 805).

[0240] As shown by Figures 8H-8G, in response to receiving user input 806H at notification affordance 826, device 800 updates the environmental noise level data displayed in chart 805 by visually highlighting the environmental noise exposure level (e.g., by changing one or more visual characteristics), which causes device 800 (or a device coupled to device 800, such as device 600) to display a noise notification interface (e.g., noise notification user interface 608D of Figure 6I).

[0241] 8J-8K show user interfaces for enabling and disabling noise measurements on device 800. In some embodiments, measurements on devices external to device 800 (e.g., devices used to acquire environmental noise exposure data for display via the user interfaces described above) may be turned off or deactivated in response to disabling other features (e.g., wrist detection) on the external devices.

[0242] 9A-9G show exemplary user interfaces for monitoring noise levels (e.g., exposure to noise from a media device) according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG.

[0243] 9A shows a device 900 displaying a user interface 904A on a display 902. As shown in FIG. 9A, the user interface 904A includes a chart 906 showing a set of daily audio amplitude values ​​(e.g., corresponding to the range of sound levels experienced by a user of the device 900 due to use of a connected audio output device) over a seven-day period. In some embodiments, the audio amplitude values ​​are determined based on the output volume setting of the device 900 (e.g., the audio level is not measured via a microphone). In some embodiments, the audio amplitude values ​​(e.g., the level of sound exposure due to use of the device) are estimated or extrapolated based on a known output device response (e.g., sensitivity, frequency response). As shown in FIG. 9A, the chart 905 includes a maximum indicator 908 and a minimum indicator 910 representing the highest and lowest audio amplitude levels experienced by a user of the device 900 due to use of a connected audio output device.

[0244] 9A, average affordance 914 is displayed in a selected state (e.g., previously selected via user input or selected by default upon display of user interface 904A). Average affordance 914 includes a value indicating the average audio level across the set of displayed audio amplitude values ​​(e.g., "77 DB").

[0245] Chart 905 includes an overlay line corresponding to the average audio level indicated by average affordance 914 (e.g., overlay 912). In some embodiments, the average audio level is not an average of the displayed data, but rather a time-average of the underlying data (e.g., an average based on how long the user was exposed to each level (e.g., sound pressure level) indicated by the data in chart 905). In some embodiments, the data indicated by chart 905 represents audio amplitude levels to which the device user was exposed over a day or other period (e.g., hour, week, year, month). As shown in FIG. 9A , user interface 904A includes an audio classification indicator 922 that provides a non-numeric display (e.g., a display including a graphic and / or text) of the average audio level relative to a threshold (e.g., a predetermined 80 DB threshold). As shown in FIG. 9A , audio classification indicator 922 indicates that the average audio level (e.g., 77 DB) is below the 80 DB threshold with an "OK" and check mark graphic.

[0246] As shown in FIG. 9A , user interface 904A includes device type filtering affordances (e.g., affordances associated with particular types of devices) to highlight data in graph 905 attributable to each device type (e.g., highlight a subset of the set of daily audio amplitude values ​​included in chart 905 of FIG. 9A ). Each device type filtering affordance (e.g., earphone filtering affordance 916, headphone filtering affordance 918, uncalibrated device affordance 920) includes associated ranges representing the highest and lowest audio amplitude levels a user of device 900 will experience by using a device of the respective device type. In some embodiments, a device type corresponds to a single device. In some embodiments, a single device includes a pair of connected devices (e.g., left and right).

[0247] 9A shows device 900 receiving user input 906A (e.g., a tap) on uncalibrated device affordance 920. In response to receiving user input 906A, device 900 displays user interface 904B. As shown in FIG. 9B, uncalibrated device affordance 920 has been replaced by a Bluetooth earphone affordance 924 and a generic headphone affordance 926, which respectively correspond to audio output devices coupled (e.g., wirelessly or physically) to device 900 (e.g., audio output devices receive analog or digital audio signals generated by device 1100 and convert them to acoustic output).

[0248] 9B shows device 900 receiving user input 906B (e.g., a tap) on earphone affordance 916. In response to receiving user input 906B, device 900 displays user interface 904C (e.g., an interface highlighting audio level data associated with the earphone output device), as shown in FIG. 9C. In some embodiments, the earphone output device is a calibrated device (e.g., a device with a known frequency response).

[0249] As shown in FIG. 9C , user interface 904C highlights audio level data attributable to one or more output devices associated with earphone affordance 916. For example, a set of data points (e.g., a range of audio exposure level data) attributable to a device corresponding to a selected device type filter (e.g., an earphone-type device) is visually distinguished (e.g., by varying a visual characteristic, such as color, hue, saturation, texture, etc.) from data not attributable to a device corresponding to the selected device type filter (e.g., an earphone-type device). As shown in FIG. 9C , data attributable to an earphone-type device corresponds to black data points on chart 905. In some embodiments, visually distinguishing the data (e.g., a set of exposure levels attributable to a first device type) includes suppressing noise exposure levels attributable to a second device type by varying one or more visual characteristics (e.g., brightness, opacity, color, contrast, hue, saturation).

[0250] In addition to enhancing the audio data in response to user input 906C, device 900 updates overlay 912 to indicate an average audio level (e.g., 72 DB) based on the enhanced set of noise amplitude values ​​(e.g., the average audio level attributable to the earphone device type).

[0251] 9C shows device 900 receiving user input 906C (e.g., a tap) on headphone affordance 918. In response to receiving user input 906C, device 900 displays user interface 904D (e.g., an interface highlighting noise level data associated with the headphone-style output device), as shown in FIG. 9D. In some embodiments, the headphone-style output device is a calibrated device (e.g., a device with a known frequency response).

[0252] As shown in FIG. 9D , user interface 904D highlights audio level data attributable to one or more output devices associated with headphone affordance 918. For example, a set of data points (e.g., a range of audio exposure level data) attributable to a device corresponding to a selected device type filter (e.g., a headphone-type device) is visually distinguished (e.g., by varying visual characteristics such as color, hue, saturation, texture, etc.) from data not attributable to a device corresponding to the selected device type filter (e.g., a headphone-type device). As shown in FIG. 9D , data attributable to a headphone-type device corresponds to black data points on chart 905. In addition to highlighting the audio data in response to user input 906D, device 900 updates overlay 912 to indicate an average audio level (e.g., 90 dB) based on the highlighted set of noise amplitude values ​​(e.g., the average audio level attributable to a headphone device type). Device 900 also updated audio classification indicator 922 to indicate that the average audio level (e.g., 90 dB) exceeded the 80 dB threshold with a “loud” and cautionary graphic.

[0253] 9D shows device 900 receiving user input 906D (e.g., a tap) on a generic headphone affordance 926. In response to receiving user input 906D, device 900 displays user interface 904E (e.g., a warning prompt interface), as shown in FIG. 9E. User interface 904E informs the user that audio levels based on an uncalibrated device may not be accurate. For example, device 900 cannot accurately extrapolate audio exposure levels without data characterizing the response of a given output device (e.g., a headphone frequency response curve).

[0254] 9E shows device 900 receiving user input 906E (e.g., a tap) on an acknowledgment affordance (e.g., "OK") In response to receiving user input 906E, device 900 displays user interface 904F (e.g., an interface highlighting a typical headphone-type output device associated with noise level data), as shown in FIG.

[0255] As shown in FIG. 9F , user interface 904F highlights audio level data attributable to one or more output devices associated with generic headphone affordance 926. For example, a set of data points (e.g., a range of audio exposure level data) attributable to a device corresponding to a selected device type filter (e.g., a generic headphone-type device) is visually distinguished (e.g., by varying visual characteristics such as color, hue, saturation, texture, etc.) from data not attributable to a device corresponding to the selected device type filter (e.g., a generic headphone-type device). As shown in FIG. 9E , data attributable to generic headphone-type devices correspond to black data points on chart 905. In addition to highlighting the audio data in response to user input 906E, device 900 updates overlay 912 to indicate an average audio level (e.g., 85 dB) based on the highlighted set of noise amplitude values ​​(e.g., the average audio level attributable to generic headphone device types).

[0256] 9F shows device 900 receiving user input 906F (e.g., a tap) on time scale affordance 928. In response to receiving user input 906E, device 900 displays user interface 904G (e.g., an interface highlighting a typical headphone-style output device associated with noise level data over a period of time), as shown in FIG.

[0257] As shown in Figure 9F, in response to receiving user input 906E, the device displays audio level data corresponding to Saturday, May 22 (e.g., the middle day of the seven-day period displayed across Figures 9A-9F). In some embodiments, audio exposure levels corresponding to days other than the middle day (e.g., the current audio exposure levels) are displayed by chart 905.

[0258] As shown in FIG. 9G, user interface 904G highlights audio level data attributable to one or more output devices associated with generic headphone affordance 926 over a 24-hour period (e.g., a day). For example, a set of data points (e.g., a range of audio exposure level data) attributable to a device corresponding to a selected device type filter (e.g., generic headphone-type device) is visually distinguished (e.g., by varying visual characteristics such as color, hue, saturation, texture, etc.) from data not attributable to a device corresponding to the selected device type filter (e.g., generic headphone-type device). As shown in FIG. 9G, data attributable to generic headphone-type devices correspond to black data points on chart 905. In response to user input 906F, in addition to displaying enhanced audio data for different time periods, device 900 updates maximum display 908, minimum display 910, overlay 912, average affordance 914, earphone filtering affordance 916, headphone filtering affordance 918, general headphone filtering affordance 920, and audio level classification 922 to indicate an audio level (e.g., 85 dB) based on the enhanced set of noise amplitude values ​​(e.g., average audio levels attributable to common headphone device types) within the displayed 24-hour period. For example, average affordance 914 is updated to indicate a daily average audio level of 68 dB (e.g., compared to a weekly average audio level of 85 dB, as shown in FIGS. 9A-9F).

[0259] 10 is a flow diagram illustrating a method for monitoring noise exposure levels using an electronic device, according to some embodiments. Method 1000 is performed on an electronic device (e.g., 100, 300, 500, 600, 601, 800, 900, 1100, 1200, 1400, 1401, and 1700) having a display device and a touch-sensitive surface. Some operations of method 1000 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0260] In some embodiments, the electronic device (e.g., 100, 300, 500, 600, 601, 800, 900, 1100, 1200, 1400, 1401, and 1700) is a computer system. The computer system is optionally in communication (e.g., wired communication, wireless communication) with a display generation component and one or more input devices. The display generation component is configured to provide a visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. The one or more input devices are configured to receive input, such as a touch-sensitive surface that receives user input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system. Thus, the computer system can transmit data (e.g., image data or video data) via wired or wireless connections to an integrated or external display generation component to visually generate content (e.g., using a display device), and can receive input from one or more input devices via wired or wireless connections.

[0261] As described below, method 700 provides an intuitive way to manage noise exposure levels. This method reduces the cognitive burden on the user when monitoring noise exposure levels, thereby creating a more efficient human-machine interface. For battery-operated computing devices, allowing users to monitor noise exposure levels more quickly and efficiently conserves power and extends the time between battery charges.

[0262] The electronic device receives 1002 first noise level data due to a first device type (e.g., an uncalibrated device such as wired headphones or uncalibrated wireless headphones connected to the electronic device via a port (e.g., a headphone jack)). The electronic device receives 1002 second noise level data due to a second device type different from the first device type (e.g., a calibrated device such as calibrated wireless headphones). In some embodiments, the electronic device distinguishes between the first and second noise level data based on one or more output signals (e.g., voltage, digital audio data) transmitted by the electronic device to the first type of output device.

[0263] The electronic device displays (1004) a first user interface (e.g., 904A) via a display device (e.g., 902). In some embodiments, the first user interface is displayed in response to a user request (e.g., a request to view the UI of the noise application via a search feature in a health app or a notification discovering a tab in a health app). The first user interface includes a first representation of received noise level data based on the first noise level data and the second noise level data (e.g., a graph showing combined data or separate data simultaneously for each of the first and second noise level data) (1006) (e.g., 905 in FIG. 9A). The first user interface includes a first device type data filtering affordance (1008) (e.g., 916). Including the first representation of received noise level data based on the first noise level data and the second noise level data in the first user interface (e.g., as a graph) visually informs the user of the noise level data in an easily understandable and recognizable manner. Providing improved visual feedback to the user improves usability of the device, makes the user device interface more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the device and reducing user errors), and also reduces power usage and improves battery life of the device by allowing the user to use the device more quickly and efficiently.

[0264] While displaying the first user interface, the electronic device detects (1012) a first user input corresponding to a selection of a first device type data filtering affordance (e.g., 916, 918, 926).

[0265] In response to detecting the first user input, the electronic device displays (1014) a second representation of the received noise level data based on the second noise level data and not based on the first noise level data (e.g., a second representation that highlights the noise level data from the calibrated device compared to the depiction of the noise level data in the first representation (e.g., a separate graph, visual emphasis on the first representation)) (e.g., 905 in FIGS. 9C-9D, 9F, and 9G). Displaying the second representation of the received noise level data based on the second noise level data and not based on the first noise level data (e.g., as a separate graph) in response to detecting the first user input allows a user to more easily view information corresponding to the second noise level data. Providing improved visual feedback to the user improves usability of the device, makes the user device interface more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the device and reducing user errors), and also reduces power usage and improves battery life of the device by allowing the user to use the device more quickly and efficiently.

[0266] In some embodiments, as part of displaying the second representation of the received noise level data, the electronic device maintains (1016) the first representation of the received noise level data (e.g., 905 in FIGS. 9C and 9D-9G). In some embodiments, the second representation of the received noise level data is visually distinguished from the first representation of the received noise level data (e.g., 905 in FIGS. 9C and 9D-9G). In some embodiments, visually distinguishing the data (e.g., the set of exposure levels attributable to the second output device type) includes suppressing the noise exposure levels attributable to the first device type data by varying one or more visual characteristics (e.g., brightness, opacity, color, contrast, hue, saturation) (e.g., 905 in FIGS. 9C and 9D-9G). In some embodiments, visually distinguishing the data includes highlighting the noise exposure level due to the second device type by varying one or more visual characteristics (e.g., brightness, opacity, color, contrast, hue, saturation) (e.g., 905 in Figures 9C and 9D-9G).

[0267] In some embodiments, the second noise level data corresponds to noise level data attributable to a single device, hi some embodiments, the single device comprises a pair of linked devices (e.g., wirelessly linked left and right headphones).

[0268] In some embodiments, the first noise level data corresponds to noise level data resulting from multiple devices (e.g., a set of multiple linked devices (e.g., a pair of linked wireless headphones)).

[0269] In some embodiments, the second noise level data includes third noise level data attributable to a third device type (e.g., data from an additional calibrated device). In some embodiments, the first user interface includes a second device type filtering affordance (e.g., an additional calibrated device affordance that adds to the first calibrated device affordance) (e.g., 918) that corresponds to the third noise level data. In some embodiments, while displaying the first user interface (e.g., 904C), the electronic device detects user input corresponding to selection of the second device type filtering affordance (e.g., 906C). In some embodiments, in response to detecting user input corresponding to selection of the second device type filtering affordance, the electronic device displays a third representation of the third noise level data (e.g., 905 of FIG. 6D). Displaying the third representation of the third noise level data allows a user to more easily view and understand information corresponding to the third noise level data. Providing improved visual feedback to the user improves usability of the device, makes the user device interface more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the device and reducing user errors), and also reduces power usage and improves battery life of the device by allowing the user to use the device more quickly and efficiently.

[0270] In some embodiments, the first user interface includes (1010) an average noise exposure level indicator (e.g., 912, 914) indicating an average noise exposure level corresponding to the first noise level data and the second noise level data for a first period (e.g., day, week) prior to detecting the first user input. In some embodiments, the average noise level indicator includes a check mark or exclamation point, a “loud” or “OK” (e.g., 922). In some embodiments, the average noise level indicator is an overlay line (e.g., 912), a text description, or an icon (e.g., 922). Providing an average noise exposure level indicator indicating the average noise exposure level provides the user with a simple and easily recognizable metric for understanding the overall noise exposure level. Providing improved visual feedback to the user improves device usability and makes the user device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), as well as reducing power usage and improving device battery life by allowing the user to use the device more quickly and efficiently.

[0271] In some embodiments, in response to detecting a user input corresponding to a selection of the first device type filtering affordance (e.g., 916), the electronic device updates (1018) the average noise exposure level indicator to indicate an average noise level corresponding to the second noise level data (e.g., not corresponding to the first noise level data) (e.g., indicating an average based only on calibrated data associated with the second device type) (e.g., 912 in Figures 9B-9C).

[0272] In some embodiments, the second noise level data is based, at least in part, on one or more signals transmitted from the electronic device to one or more devices of a second type (e.g., the noise level is not based on an incoming signal or data (e.g., an audio level measured via a microphone)). In some embodiments, the noise level is estimated based on a volume setting (e.g., 100% volume) and a known output device response (e.g., headphones of a first type outputting 87 dB at 100% for a particular signal being played).

[0273] In some embodiments, the first representation of the received noise level data includes an indication (e.g., 910) of a maximum value of the noise level data (e.g., 908) and a minimum value of the noise level data (e.g., values ​​representing the highest and lowest noise levels in the combined first and second noise level data) for the second time period (e.g., day, week). In some embodiments, the first representation includes two or more pairs of maximum and minimum noise level values ​​(e.g., maximum and minimum values ​​for each day within a week).

[0274] It should be noted that the details of the process (e.g., FIG. 10 ) described above with respect to method 1000 are also applicable in an analogous manner to the above-described methods. For example, method 700 optionally includes one or more of the features of the various methods described above with reference to method 1000. For example, as described above in method 700, a graphical display (e.g., a graphical object) that changes appearance based on noise exposure level may be used to display noise exposure level information corresponding to one or more output devices. For the sake of brevity, these details will not be repeated below.

[0275] 11A-11F illustrate user interfaces (e.g., 1104A-1104F) for accessing and displaying audiogram data (e.g., sets of data representing hearing acuity at various sound frequencies). In some embodiments, the audiogram data is received at device 1100 from a third-party application. In some embodiments, the audiogram data is manually entered by a device user (e.g., via a series of user inputs detected by device 1100). For example, FIGS. 11A and 11B illustrate user interfaces within a health application for accessing audiogram noise data. FIGS. 11C-11D illustrate techniques for displaying audiogram data and selecting or visually highlighting portions of the data (e.g., portions associated with the left or right side).

[0276] 11G-11L show a series of user interfaces (e.g., 1104G-1104L) for using an audiogram to personalize the audio output of device 1100 (e.g., output through devices associated with device 1100, such as connected headphones, an integrated headset or speaker, external speakers, and other media playback devices). For example, FIG. 11H shows a technique for creating a hearing profile via an AB testing process hearing test supplemented with stored audiogram data. In some embodiments, utilizing audiogram data shortens the process of creating a hearing profile or improves the accuracy of the profile compared to a calibration process that does not utilize audiogram data.

[0277] 12A-12AN show exemplary user interfaces for customizing audio settings based on user preferences, according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG.

[0278] 12A-12AN show device 1200 displaying a user interface on display 1202 (e.g., a display device or display generating component) for customizing audio settings based on user preferences. In some embodiments, device 1200 is the same as device 800, device 900, and device 1100. In some embodiments, device 1200 includes one or more features of device 100, 300, or 500.

[0279] 12A-12C show exemplary user interfaces for accessing headphone audio settings interface 1205 of FIG. 12C in response to detecting input 1204 and input 1206 of FIGS. 12A and 12B, respectively.

[0280] 12C , device 1200 displays, via display 1202, headphone audio settings interface 1205 shown with standard audio settings option 1208 selected. Thus, device 1200 now applies standard (e.g., uncustomized) audio settings to one or more connected headphone devices. Headphone audio settings interface 1205 also includes custom audio settings option 1210 and custom audio setup option 1212. Custom audio settings option 1210 is selectable to manually set custom audio settings for a connected headphone device, and custom audio setup option 1212 is selectable to initiate a guided process for configuring customized audio settings.

[0281] 12C , device 1200 detects input 1213 (e.g., a tap gesture) on custom audio settings option 1210 via display 1202 and, in response, selects custom audio settings option 1210 and displays customization options 1214, as shown in FIG. 12D . When custom audio settings option 1210 is selected, device 1200 applies customized audio settings to one or more connected headphone devices. In some embodiments, the customized audio settings are determined based on the settings indicated in customization option 1214.

[0282] In FIG. 12D , customization options 1214 include a set 1215 of audio options that can be selected, and in some embodiments, individually adjusted (e.g., customized) using slider 1216 to select a boost level for each audio option. In some embodiments, the boost value for each selected audio option can be adjusted between slight 1216-1, moderate 1216-2, and strong 1216-3 by adjusting slider 1216. In some embodiments, audio options 1215 can include options corresponding to customized audio settings based on the results of a hearing test (e.g., an audiogram). In such embodiments, audiogram settings cannot be changed using customization options 1214, and as a result, slider 1216 is not displayed when the audiogram option is selected. Audiogram options are described in more detail below.

[0283] In FIG. 12D , the set of audio options includes balance tone option 1215-1, speech intelligibility option 1215-2, and brightness option 1215-3. In some embodiments, balance tone option 1215-1 can be selected (e.g., using slider 1216) to customize the boost level of a frequency range (e.g., the tonal balance of frequencies in the 20 Hz to 20 KHz range). In some embodiments, the custom setting (e.g., boost level) of balance tone option 1215-1 is applied across all frequencies of the connected headphone device. In some embodiments, speech intelligibility option 1215-2 can be selected to customize the boost level of frequencies used for dialogue, such as, for example, a range of 2 KHz to 8 KHz. In some embodiments, brightness option 1215-2 can be selected to customize the boost level of high frequencies, such as, for example, a range of 2 KHz to 20 KHz.

[0284] 12D-12F, each of the audio options 1215 can be selected, and in response, the device 1200 displays a slider 1216 with the current boost level for the selected option. For example, in FIG. 12D, the balance tone option 1215-1 is selected, and the slider 1216 indicates that the boost value for the balance tone is set to no more than 1216-1. The boost value for the balance tone option 1215-1 can be adjusted using the slider 1216.

[0285] In Figure 12E, device 1200 displays selected speech intelligibility option 1215-2 (in response to input 1218 in Figure 12D), and slider 1216 indicates that the current boost value for speech intelligibility is set to no more than 1216-1. The boost value for speech intelligibility option 1215-2 can be adjusted using slider 1216.

[0286] In Figure 12F, device 1200 displays selected brightness option 1215-3 (in response to input 1220 in Figure 12D), and slider 1216 indicates that the current boost value for brightness is set to only 1216-1. The boost value for brightness option 1215-3 can be adjusted using slider 1216.

[0287] In some embodiments, the slider 1216 may have a different appearance than that shown in the headphone audio settings interface 1205. For example, the slider 1216 may have additional setting positions, such as “none,” “very slight,” or “very strong,” or intermediate positions between “slight” and “medium,” and between “medium” and “strong.” In some embodiments, the slider 1216 may be modified to include the ability to set a range of values. For example, the slider 1216 may have two notches for setting the high end of the range and the low end of the range. Additionally, in some embodiments, the slider 1216 may be replaced or supplemented with other user interface objects to indicate the boost setting, such as, for example, a range of values ​​(e.g., a numeric range) or a field for entering a value (e.g., a numeric value) within a range.

[0288] As shown in FIG. 12F , customization options 1214 further include sample option 1222, application option 1224, and transparency mode settings 1226. Sample option 1222 is selectable to play an audio sample with customized audio settings. In some embodiments, while the audio sample is playing, a user can select a different audio option 1215 and adjust slider 1216 to adjust the audio sample as it plays. Application options 1224 include phone call toggle 1224-1 and media toggle 1224-2. Phone call toggle 1224-1 is selectable to enable or disable customized audio settings for calls. Media toggle 1224-2 is selectable to enable or disable customized audio settings for media (e.g., music, videos, movies, games). In some embodiments, when the respective application option 1224 is disabled, standard audio settings are used for the disabled option. 12F, both application options 1224 are enabled, and therefore customized audio settings are used for each option. Phone call toggle 1224-1 and media toggle 1224-2 are non-limiting examples of application options 1224. In some embodiments, application options 1224 may include different application options (e.g., different types of media) that can be selected to enable or disable audio settings for the application associated with each option. Transparency mode setting 1226 is selectable to customize audio settings for ambient sound, as described in more detail below.

[0289] 12F, device 1200 detects input 1228 on custom audio setup option 1212 and, in response, initiates a process for setting customized audio settings based on the user's preferences for various audio samples with different audio characteristics. User interfaces for various embodiments of this custom audio setup process are shown in FIGS. 12G-12AE.

[0290] 12G, device 1200 displays introductory interface 1229 in response to input 1228. Introductory interface 1229 indicates that a customization process can be used to customize headphone audio settings for calls, media, and ambient audio, and that the customization process can incorporate audiogram results. In some embodiments, introductory interface 1229 is not displayed in response to input 1228. For example, in some embodiments, device 1200 displays introductory interface 1229 only the first time a user selects custom audio setup option 1212. In such embodiments, device 1200 instead displays the interface shown in FIG. 12H or 12K in response to selection of custom audio setup option 1212.

[0291] In FIG. 12G, device 1200 detects input 1230 and, in response, displays audiogram interface 1232. Audiogram interface 1232 includes a list of various audiograms 1233 available to the user account associated with device 1200. For example, in FIG. 12G, the user's account includes audiogram 1233-1 from a hearing test conducted on February 19, 2019, and audiogram 1233-2 from a hearing test conducted on March 23, 2020. The user can select the audiogram they want to use to customize their audio settings. The most recent audiogram is selected by default, as shown in FIG. 12H. In some embodiments, the audiogram is provided to the user account by a medical professional or provider. In some embodiments, if the user account does not include any audiograms, audiogram interface 1232 is not displayed. In such an embodiment, device 1200 instead displays the interface shown in FIG. 12K (eg, in response to input 1228 or input 1230).

[0292] Audiogram interface 1232 includes option 1234 for selecting to use the selected audiogram to customize audio settings and option 1236 for selecting not to use the audiogram to customize audio settings. In FIG. 12H, device 1200 detects input 1238 on option 1234 to use the selected audiogram 1233-2 to customize audio settings. In response to detecting input 1238, device 1200 completes the custom audio setup process, applies the custom audio settings based on the selected audiogram, and displays headphone audio settings interface 1205, as shown in FIG. 12I. In some embodiments, before displaying the interface of FIG. 12I, device 1200 displays the user interface shown in FIG. 12AE to allow the user to customize ambient audio settings. In some embodiments, before displaying the interface of FIG. 12I, device 1200 instead displays an interface similar to recommendation interface 1280, described in more detail below in connection with FIGS. 12AC and 12AD, which includes an option to compare standard audio settings with audio settings based on an audiogram, and includes an option to select standard audio settings or a customized setting based on an audiogram.

[0293] 12I, audio options 1215 are shown updated with selected audiogram list option 1215-4. Because audiogram option 1215-4 is selected, device 1200 customizes audio settings that are not configurable by the user (e.g., using headphone audio settings interface 1205). Therefore, slider 1216 is not displayed. In some embodiments, audio options 1215 include audiogram option 1215-4 when an audiogram is available to customize audio settings; otherwise, audiogram option 1215-4 is not displayed.

[0294] In FIG. 12J, device 1200 illustrates an embodiment in which an audiogram is not used to customize audio settings; instead, the device continues with a custom audio setup process in response to input 1240 on option 1236.

[0295] In FIG. 12K, device 1200 displays command interface 1242, including continuation affordance 1242-1, which is currently shown as unavailable for selection because a headphone device is not currently connected to device 1200.

[0296] 12L, device 1200 is coupled (e.g., paired, connected, communicating, or actively exchanging data) with headphone device 1245 (e.g., via a wireless connection), and continuation affordance 1242-1 is shown available for selection. Device 1200 detects input 1244 on continuation affordance 1242-1 and, in response, initiates a custom audio setup process.

[0297] In some embodiments, the custom audio setup process includes two stages: 1) an amplification stage and 2) a tone adjustment stage. In some embodiments, device 1200 uses the amplification stage to determine what volume the user is comfortable listening to. In some embodiments, device 1200 uses the tone adjustment stage to determine what audio tones are preferred by the user. In some embodiments, device 1200 recommends one or more adjustments to audio settings (e.g., tone balance, speech clarity, brightness) based on the results of the two stages of the custom audio setup process. For example, device 1200 may recommend a slight, moderate, or strong improvement in tone balance. As another example, device 1200 may recommend a slight, moderate, or strong increase in speech clarity. As yet another example, device 1200 may recommend a slight, moderate, or strong boost in brightness. In some embodiments, device 1200 may recommend adjustments to any combination of tone balance, speech clarity, and brightness. In some embodiments, the tone adjustment stage determines whether adjustments are recommended to tone balance, speech intelligibility, and / or brightness based on user preferences. In some embodiments, the results of the amplification stage influence the tone adjustment stage. For example, in some embodiments, the results of the amplification stage determine whether the recommended tone adjustment is slight, moderate, or strong.

[0298] In Figures 12M and 12N, device 1200 shows an interface for the amplification stage of the custom audio setup process. During the amplification stage, device 1200 generates audio output at different volumes to determine which volumes can be heard by the user. In some embodiments, the audio is a looped playback of an audio read "Hello." In the embodiment shown in Figures 12M-12AN, sound graphic 1245-1 is used to indicate that audio is generated by headphone device 1245. In some embodiments, device 1200 displays a waveform with movement (e.g., waveform 1248-1 in Figure 12M) to indicate to the user that audio is being played, even if the user cannot hear it.

[0299] 12M, device 1200 displays a first amplification comparison interface 1247, producing audio at a low volume level. Interface 1247 prompts the user to indicate whether they can hear the audio produced by headphone device 1245 and visually represented by waveform 1248-1. Device 1200 also displays a toggle selector 1246 with a yes toggle 1246-1 and a no toggle 1246-2 to indicate whether the user can hear the audio in combination with a continuation affordance 1249.

[0300] 12M, if the user indicates that they can hear the audio (e.g., by selecting continue affordance 1249 when yes toggle 1246-1 is selected), device 1200 ends (e.g., completes) the amplification phase and proceeds to the tone adjustment phase. In this scenario, the amplification setting is low because the user indicated that they can hear the bass level.

[0301] In Figure 12M, device 1200 detects input 1250-1 (e.g., a tap gesture) on toggle 1246-2, followed by input 1250-2 (e.g., a tap gesture) on continuation affordance 1249. In this scenario, the user indicates that they cannot hear the bass level, and the amplification stage continues in Figure 12N.

[0302] 12N, device 1200 displays a second amplification comparison interface 1252 and produces audio (on headphone device 1245) at a media sound level. Interface 1252 prompts the user whether they can hear the audio, which is visually represented by waveform 1248-2, which has a greater amplitude than waveform 1248-1. If the user indicates that they can hear the audio, the amplification setting is medium because they indicated they can hear the media sound level. If the user indicates that they cannot hear the audio, the amplification setting is strong.

[0303] 12N, device 1200 detects input 1253-1 (e.g., a tap gesture) on yes toggle 1246-1, followed by input 1253-2 (e.g., a tap gesture) on continue affordance 1249. In this scenario, the user indicates that they can hear the sound level of the media.

[0304] In some embodiments, the setting of the toggle selector 1246 persists until it is changed by selecting an unselected toggle. For example, in FIG. 12M, toggle 1246-2 is not selected and remains selected when the second amplification comparison interface 1252 is displayed in FIG. 12N. However, in some embodiments, the setting of the toggle selector 1246 is reset for each comparison. For example, the toggle resets to have the Yes toggle 1246-1 selected when the second amplification comparison interface is displayed.

[0305] In FIGS. 12O-12AD, device 1200 illustrates an interface for the tone adjustment phase of the custom audio setup process. During the tone adjustment phase, device 1200 generates a set of audio comparisons. Each comparison features two audio samples of the same sound (e.g., looped music playback), with each sample having audio characteristics that differ from the other samples. For each comparison, device 1200 prompts the user to select which audio sample they prefer and, based on those selections, recommends customized audio settings (e.g., adjustments to one or more of balance tone, speech clarity, or brightness) to optimize the user's preferences. In some embodiments, device 1200 recommends standard audio settings based on the user's selection, thereby terminating the tone adjustment phase after two comparisons. Such embodiments are illustrated in FIGS. 12P-12T.

[0306] In response to detecting input 1254 of FIG. 12O, device 1200 displays first comparison interface 1255-1 and generates music on headphone device 1245, as shown in FIG. 12P. Interface 1255-1 prompts the user to indicate whether they prefer the first version of the audio or the second version of the audio. Interface 1255-1 includes toggle selector 1257 having a version 1 toggle 1257-1 for selecting the first version of the audio in the comparison and a version 2 toggle 1257-2 for selecting the second version of the audio in the comparison. When the first version of the audio is selected, music is played on headphone device 1245 with audio characteristics corresponding to the first version of the audio. Similarly, when the second version of the audio is selected, music is played on headphone device 1245 with audio characteristics corresponding to the second version of the audio. While the music continues to play, the user can toggle between the first version and the second version and can change the audio characteristics of the music based on the selection. For example, the pitch changes when the second version is selected and then changes back when the first version is selected. By toggling between the two versions of the audio in the comparison, the user can compare the different versions and select between them. In some embodiments, device 1200 prompts the user to select the first version if both versions sound the same to the user.

[0307] Interface 1255-1 also includes a volume slider 1258 for adjusting the volume of audio being played through headphone device 1245. In some embodiments, the volume setting in interface 1255-1 is determined based on the results of the amplification stage. For example, if the amplification is medium, the tab for volume slider 1258 is centered, as shown in FIG. 12P. In some embodiments, the results of the amplification stage determine a baseline volume, and volume slider 1258 makes adjustments to the baseline volume. In some embodiments, changes to volume slider 1258 change (e.g., redefine) the results of the amplification stage. In some embodiments, the amplification stage shown in FIGS. 12M and 12N is optional. In such embodiments, the amplification can instead be determined based on the setting of volume slider 1258.

[0308] Each comparison interface includes a waveform that provides a visual representation of the audio sample being generated by headphone device 1245. For example, in the first comparison interface 1255-1, waveform 1260-1 represents a first version of the audio sample in the first comparison, and waveform 1260-2 (shown in FIG. 12V) represents a second version of the audio sample in the first comparison.

[0309] In Figure 12P, device 1200 detects input 1262 selecting an option to cancel the custom audio setup process and, in response, displays confirmation interface 1263 prompting the user to complete the custom audio setup process. In response to detecting input 1264, device 1200 returns to first comparison interface 1255-1 in Figure 12R.

[0310] In FIG. 12R, device 1200 detects a user's preference for a first version of the audio signal characterized in first comparison interface 1255-1 (e.g., by detecting input 1266 on the continuation affordance when one toggle 1257-1 is selected) and, in response, displays second comparison interface 1255-2 of FIG. 12S.

[0311] Device 1200 continues to generate music in headphones 1245 when displaying second comparison interface 1255-2. Second comparison interface 1255-2 is similar to first comparison interface 1255-1 but features at least one different audio sample. In FIG. 12S, the first version of the audio is the same as the first version of the audio in first comparison interface 1255-1, as shown by waveform 1260-1. Thus, the music generated in the headphones remains unchanged when transitioning from first comparison interface 1255-1 to second comparison interface 1255-2.

[0312] In some embodiments, the version of audio selected in the previous comparison interface becomes one of the versions of audio in the current comparison interface. For example, in the second comparison interface 1255-2, the first version of audio is the same as the first version of audio selected in the first comparison interface 1255-1. Alternatively, if a second version was selected in the first comparison interface 1255-1, the selected version is one of the options (e.g., the second version) in the second comparison interface 1255-2.

[0313] In FIG. 12S, device 1200 detects a user's preference for a first version of the audio signal characterized in second comparison interface 1255-2 (e.g., by detecting input 1268 on the continuation affordance when one toggle 1257-1 is selected) and, in response, displays standard recommendation interface 1270 of FIG. 12T.

[0314] In the embodiment shown in FIG. 12T, device 1200 recommends standard audio settings based on the user's preferences for the first version of the audio signal in both first comparison interface 1255-1 and second comparison interface 1255-1. As a result, device 1200 terminates the custom audio setup process and recommends standard settings that are optionally applied when the user selects execute affordance 1270-1. In some embodiments, the amplification settings are retained when the standard settings are applied, but tone adjustments are not performed. In some embodiments, the amplification settings are not retained, and tone adjustments are not performed when the standard settings are applied. In some embodiments, device 1200 optionally displays the user interface in FIG. 12AE in response to detecting selection of execute affordance 1270-1. In some embodiments, the device displays the user interface of FIG. 12C in response to detecting selection of completion affordance 1270-1.

[0315] 12U-12AD illustrate an exemplary embodiment in which the tone adjustment stage is complete and custom audio settings are recommended based on the user's selected preferences.

[0316] Referring to FIG. 12U, device 1200 displays first comparison interface 1255-1 and detects input 1272 on version 2 toggle 1257-2. While continuing to play music on headphone device 1245, device 1200 changes the audio characteristics from the first version of audio to that of the second version of audio in response to input 1272. In FIG. 12V, waveform 1260-2 visually represents the second version of audio in the first comparison, with version 2 toggle 1257-2 highlighted to indicate that the second version of audio is currently selected.

[0317] In Figure 12V, device 1200 detects input 1273 on the continuation affordance indicating a user preference for the second version of the audio—i.e., the second audio sample in the first comparison. In response to detecting input 1273, device 1200 displays second comparison interface 1255-2, shown in Figure 12W.

[0318] 12W , device 1200 continues to play music through headphone device 1245. The music played through headphone device 1245 now has audio characteristics associated with the second version of the audio selected in first comparison interface 1255-1, as shown by waveform 1260-2. In other words, second comparison interface 1255-2 features a comparison of audio samples that are different from those provided in first comparison interface 1255-1, but one of the feature audio samples in the second comparison (second version) is the audio sample selected from first comparison interface 1255-1. In some embodiments, the first and second versions of the audio in the second comparison interface are different from both the first and second versions of the audio in the first comparison interface, but at least one of the first or second versions of the audio in the second comparison is affected by the version of the audio selected in the first comparison interface.

[0319] In some embodiments, the setting of toggle selector 1257 persists across different comparison interfaces. For example, in the embodiment shown in FIG. 12W , VERSION 2 toggle 1257-2 remains selected (after input 1273), and the set of audio features selected from the first comparison interface 1255-1 (the second version of the audio in the first comparison) remains associated with VERSION 2 toggle 1257-2. However, in some embodiments, the setting of toggle selector 1257 resets to have VERSION 1 toggle 1257-2 selected when a new comparison interface is displayed. According to such an embodiment, the second comparison interface of FIG. 12W is shown with VERSION 1 toggle 1257-1 selected, and the audio features associated with the second version of the audio in the first comparison interface 1255-1 are instead associated with the first version of the audio in the second comparison interface 1255-2.

[0320] Referring again to FIG. 12W, device 1200 detects input 1274 on VERSION 1 toggle 1257-1 and, in response, modifies the music on headphone device 1245 based on audio characteristics associated with the first version of the audio sample in second comparison interface 1255-2. The first version of the audio in second comparison interface 1255-2 differs from both the first and second versions of the audio in the first comparison interface (and the second version of the audio in the second comparison), as shown by waveform 1260-3 in FIG. 12X. Furthermore, in the embodiment shown in FIG. 12X, the first version of the audio signal characterized in second comparison interface 1255-2 (e.g., waveform 1260-3) differs from the audio signal characterized in second comparison interface 1255-2 in FIG. 12S (e.g., waveform 1260-1). This is because the selection of a preferred audio sample affects the audio sample used in subsequent comparisons, and the selection in the embodiment illustrated in FIG. 12S differs from the selection in the embodiment illustrated in FIG. 12X.

[0321] In FIG. 12X, device 1200 detects input 1275-1 (e.g., a slide gesture) on volume slider 1258 and, in response, increases the amplitude of the audio generated by headphone device 1245, as shown by amplified waveform 1260-3a in FIG. 12Y.

[0322] In FIG. 12Y, device 1200 detects input 1275-2 (e.g., a slide gesture) on volume slider 1258 and, in response, restores the amplitude of the audio being generated by headphone device 1245 to its previous amplitude, as shown by waveform 1260-3 in FIG. 12Z.

[0323] In FIG. 12Z, device 1200 detects a user's preference for the first version of the audio signal characterized in second comparison interface 1255-2 (e.g., by detecting input 1276 on the continuation affordance when version 1 toggle 1257-1 is selected) and, in response, displays third comparison interface 1255-3 in FIG. 12AA.

[0324] In Figure 12AA, device 1200 continues to play music on headphone device 1245 with audio characteristics associated with the first version of the audio selected in second comparison interface 1255-2, as shown by waveform 1260-3. Device 1200 detects input 1277 on version 2 toggle 1257-2 and, in response, changes the music on headphone device 1245 based on audio characteristics associated with the second version of the audio sample in third comparison interface 1255-3. The second version of the audio in third comparison interface 1255-3 differs from the versions of audio in first comparison interface 1255-1 and second comparison interface 1255-2, as shown by waveform 1260-4 in Figure AB.

[0325] In FIG. 12AB, device 1200 detects a user preference for the second version of the audio signal characterized in third comparison interface 1255-3 (e.g., by detecting input 1278 on the continuation affordance when version 2 toggle 1257-2 is selected) and, in response, displays recommendation interface 1280 in FIG. 12AC.

[0326] 12AC, recommendation interface 1280 shows customized settings or audio adjustments recommended by device 1200 based on selections made in the custom audio setup process. In the embodiment shown in FIG. 12AC, device 1200 recommends a moderate boost to brightness. In some embodiments, recommendation interface 1280 can recommend other audio adjustments based on different preferences selected by the user in the custom audio setup process.

[0327] Recommendation interface 1280 includes a recommendation toggle selector 1282, which includes a custom toggle 1282-1 and a standard toggle 1282-2. When custom toggle 1282-1 is selected, device 1200 produces audio at headphone device 1245 with the recommended audio adjustments, as shown in FIG. 12AC. In the embodiment of FIG. 12AC, waveform 1260-5 represents audio at headphone device 1245 with the customized audio settings. In some embodiments, waveform 1260-5 corresponds to a preferred audio sample (e.g., waveform 1260-4) selected in third comparison interface 1255-3. In some embodiments, waveform 1260-5 differs from the preferred audio sample selected in the third comparison but is still influenced based on the selection of the preferred audio sample in the third comparison.

[0328] In FIG. 12AC, device 1200 detects input 1283 on standard toggle 1282-2 and, in response, selects standard toggle 1282-2 as shown in FIG. 12AD. When standard toggle 1282-2 is selected, device 1200 generates audio at headphone device 1245 with standard audio settings. In the embodiment of FIG. 12AD, waveform 1260-6 represents audio at headphone device 1245 with standard audio settings. In some embodiments, waveform 1260-6 corresponds to waveform 1260-1 of first comparison interface 1255-1. In some embodiments, waveform 1260-6 incorporates amplification settings determined from the amplification phase of the custom audio setup process. In some embodiments, waveform 1260-6 does not incorporate amplification settings determined from the amplification phase of the custom audio setup process.

[0329] The recommended toggle selector 1282 allows the user to toggle between custom and standard audio settings and hear a preview of the audio featuring the custom or standard settings, allowing the user to more efficiently decide whether to apply the recommended customized audio settings or to assist the user in using the standard audio settings instead.

[0330] Recommendation interface 1280 further includes custom settings affordance 1284-1 and standard settings affordance 1284-2. Custom settings affordance 1284-1 is selectable to apply recommended custom audio settings, and in some embodiments, creates a custom audio settings profile that can be used to apply the custom audio settings to other connected headphone devices. Standard settings affordance 1284-2 is selectable to apply standard audio settings. In FIG. 12AD, device 1200 detects input 1285 on custom settings affordance 1284-1 and, in response, applies the custom audio settings and, optionally, displays transparent mode interface 1286 as shown in FIG. 12AE.

[0331] 12AE, in some embodiments, device 1200 optionally displays a transparency mode interface 1286 if ambient audio settings are supported by headphone device 1245. Otherwise, device 1200 displays headphone audio settings interface 1205, as shown in FIG. 12AF. Transparency mode interface 1286 includes an amplification slider 1286-1, a balance slider 1286-2, and a tone slider 1286-3. These sliders are selectable to adjust audio settings for headphones 1245 that feature amplifying ambient sound, as described in more detail below with respect to FIG. 12AH. In some embodiments, headphone device 1245 generates ambient audio, as indicated by sound graphic 1245-1, when displaying transparency mode interface 1286. For example, headphone device 1245 detects ambient audio (e.g., using a microphone) and generates an amplified version of the ambient audio so that the user can more easily hear their physical environment while wearing the headphones.

[0332] Transparent mode interface 1286 also includes option 1286-4 for applying any setting changes made using sliders 1286-1, 1286-2, and 1286-3. In Figure 12AE, device 1200 detects input 1287 on option 1286-5 and, in response, does not apply any transparent mode setting changes and displays headphone audio settings interface 1205, as shown in Figure 12AF.

[0333] 12AF, device 1200 displays audio settings interface 1205 with updated audio settings based on the results of the custom audio setup process. For example, brightness option 1215-3 is selected and is now shown with a moderate boost 1216-2 (based on the results of the custom audio setup process) as indicated by slider 1216. In some embodiments, the user can further adjust any of the audio options 1215 (other than audiogram option 1215-4) by selecting the respective audio option and adjustment slider 1216. In some embodiments, if the custom audio settings have not been set or changed from the results of a previous custom audio setup process, the user can manually adjust the custom audio settings to match the results of the previous custom audio setup process. This allows the user to set custom results without having to complete the custom audio setup process. In some embodiments, the process of manually selecting custom audio settings can be initiated when a new set of headphones is connected to device 1200, as described in more detail below.

[0334] In Figure 12AF, transparent mode settings 1226 are shown with standard settings because no changes were made to the transparent mode settings in Figure 12AE. In some embodiments, if changes are made to these settings and option 1286-4 is selected, transparent mode settings 1226 displays "Custom" in Figure 12AF. Device 1200 detects input 1288 on transparent mode settings 1226 and, in response, displays transparent mode settings interface 1289, similar to transparent mode interface 1286 in Figure 12AE.

[0335] 12AG shows a transparent mode settings interface 1289 with standard settings selected. The device 1200 detects input 1289-1 and, in response, applies custom settings indicated by displayed transparent mode customization options 1290 similar to those displayed in FIG. 12AE.

[0336] 12AH shows transparency mode customization options 1290 and various inputs 1291 for adjusting the customization options. For example, device 1200 detects input 1291-1 (a slide gesture) on amplification slider 1290-1 to increase the amplification of ambient audio, detects input 1291-2 on balance slider 1290-1 to focus ambient audio to the left, and detects input 1291-3 on tone slider 1290-3 to increase brightness. Device 1200 updates each setting, as shown in FIG. 12AI.

[0337] In FIG. 12AI, device 1200 detects input 1292 and, in response, disables the transparent mode setting, as shown in FIG. 12AJ.

[0338] In FIG. 12AJ, device 1200 detects input 1293 and, in response, re-enables the transparent mode setting, retaining the previous setting adjustments, as shown in FIG. 12AK.

[0339] 12AL-12AN, device 1200 shows exemplary user interfaces that are displayed when connecting a new headphone device 1297 to device 1200. In some embodiments, new headphone device 1297 is a different set of headphones than headphone device 1245. In FIG. 12AM, device 1200 shows option 1294 for accessing transparency mode settings interface 1289 or transparency mode interface 1286 to customize transparency mode settings for new headphone device 1297. In FIG. 12AN, device 1200 displays option 1295 for initiating the custom audio setup process described above and option 1296 for displaying headphone audio settings interface 1205 to allow a user to manually configure custom headphone audio settings that can be applied to new headphone device 1297.

[0340] 13 is a flow diagram illustrating a method for customizing audio settings based on user preferences using a computer system, according to some embodiments. Method 1300 is performed on a computer system (e.g., a smartphone, a smartwatch) (e.g., device 100, 300, 500, 600, 601, 800, 900, 1100, 1200, 1400, 1401, 1700) in communication with a display generation component (e.g., display 1202) (e.g., a display controller, a touch-sensitive display system), an audio generation component (e.g., headphone device 1245) (e.g., audio circuitry, a speaker), and one or more input devices (e.g., a touch-sensitive surface of display 1202). In some embodiments, the computer system includes the display generation component and one or more input devices. Some operations of method 1300 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0341] In some embodiments, the electronic device (e.g., 100, 300, 500, 600, 601, 800, 900, 1100, 1200, 1400, 1401, and 1700) is a computer system. The computer system is optionally in communication (e.g., wired communication, wireless communication) with a display generation component and one or more input devices. The display generation component is configured to provide a visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. The one or more input devices are configured to receive input, such as a touch-sensitive surface that receives user input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system. Thus, the computer system can transmit data (e.g., image data or video data) via wired or wireless connections to an integrated or external display generation component to visually generate content (e.g., using a display device), and can receive input from one or more input devices via wired or wireless connections.

[0342] Method 1300 provides an intuitive way to customize audio settings based on user preferences. This method reduces the cognitive burden on the user to customize audio settings based on the user's preferences, thereby creating a more efficient human-machine interface. For battery-operated computing devices, allowing users to customize audio settings faster and more efficiently conserves power and extends the time between battery charges.

[0343] In method 1300, a computer system (e.g., 1200) displays, via a display generation component (e.g., 1202), a representation (e.g., 1257-1) of a first audio sample (e.g., interface object (e.g., selectable user interface object (e.g., affordance)) (e.g., 1260-1 in interface 1255-1 (e.g., FIG. 12U)), (e.g., 1260-3 in interface 1255-2 (e.g., FIG. 12X)), (e.g., 1260-4 in interface 1255-3 (e.g., FIG. 12X)), (e.g., 1260-5 in interface 1255-4 (e.g., FIG. 12X)), (e.g., 1260-6 in interface 1255-5 (e.g., FIG. 12X)), (e.g., 1260-7 in interface 1255-6 (e.g., FIG. 12X)), (e.g., 1260-8 in interface 1255-9 (e.g., FIG. 12X)), (e.g., 1260-9 in interface 1255-1 (e.g., FIG. 12X)), (e.g., 1260-10 in interface 1255-1 (e.g., FIG. 12X)), (e.g., 1260-11 in interface 1255-1 (e.g., FIG. 12X)), (e.g., 1260-12 in interface 1255-2 (e.g., FIG. 12X)), (e.g., 1260-11 in interface 125 12AA)), where a first audio sample has a first set of audio characteristics (e.g., a first value for one or more of amplification, balance, clarity, and brightness) (e.g., a first affordance is selectable to change the audio characteristics of the audio sample to the first set of audio characteristics), and simultaneously displaying (1304) a representation (e.g., 1257-1) of a second audio sample (e.g., 1257-2) (e.g., a second affordance) (e.g., an and simultaneously displaying (1306) a representation in an audio preference interface (e.g., 1255 (e.g., 1255-1, 1255-2, 1255-3) in an interface 1255-1 (e.g., FIG. 12V)) (e.g., 1260-2 in interface 1255-2 (e.g., FIG. 12W)) (e.g., 1260-4 in interface 1255-3 (e.g., FIG. 12AB)), wherein the second audio sample has a second set of audio characteristics that is different from the first set of audio characteristics. 1247, 1252). In some embodiments, an indication (e.g., a focus selector, highlight, visual emphasis) is displayed indicating that either the first audio sample or the second audio sample is currently selected (e.g., in FIG. 12R, toggle 1257-1 for version 1 is bolded to indicate that it is selected). In some embodiments, the first and second audio samples are the same audio sample but have different audio characteristics.For example, the first audio sample may be a speech or music audio sample, and the second audio sample may be the same speech or music audio sample with different values ​​for at least one of amplification, balance, speech intelligibility, and brightness.

[0344] While displaying (1308) (in some embodiments, subsequent to displaying) an audio preference interface (e.g., 1255 (e.g., 1255-1, 1255-2, 1255-3), 1247, 1252), the computer system (e.g., 1200) may, via the audio generation component (e.g., 1245), generate at least a portion of a first audio sample (e.g., 1260-1 in interface 1255-1 (e.g., FIG. 12U)) (e.g., 1260-3 in interface 1255-2 (e.g., FIG. 12X)) (e.g., For example, the computer system outputs 1310 audio sample 1260-3 (e.g., FIG. 12AA) in interface 1255-3 (e.g., and / or at least a portion of the second audio sample), and the computer system receives 1312 one or more sets of user inputs (e.g., 1266, 1268, 1272, 1273, 1274, 1275-1, 1275-2, 1276, 1277, 1278, 1283, 1285) via one or more input devices (e.g., 1202) (after outputting at least a portion of the first and / or second audio sample). Outputting at least a portion of the first audio sample while displaying the audio preferences interface provides feedback that allows the user to more quickly and easily associate the output audio with selections made using the audio preferences interface. Providing improved feedback improves the usability of the device and makes the user device interface more efficient (e.g., by helping the user make appropriate inputs and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by allowing the user to use the device more quickly and efficiently.

[0345] At 1314 of method 1300, after receiving a set of one or more inputs (e.g., 1266, 1268, 1272, 1273, 1274, 1275-1, 1275-2, 1276, 1277, 1278, 1283, 1285), the computer system (e.g., 1200) selects a first audio sample as a preferred sample (e.g., input 1266 results in the selection of the audio sample represented by waveform 1260-1 in interface 1255-1 (e.g., FIG. 12R)) (e.g., input 1268 results in the selection of the audio sample represented by waveform 1260-1 in interface 1255-2 (e.g., FIG. 12S)) (e.g., input 1276 also results in the selection of the audio sample represented by waveform 1260-3 in interface 1255-2 (e.g., FIG. 12S)) 12Z) (e.g., input 1285 results in the selection of the audio sample represented by waveform 1260-5 in interface 1280 (e.g., FIGS. 12AC and 12AD)) or the selection of a second audio sample as a preferred sample (e.g., as a selected sample) (e.g., input 1273 results in the selection of the audio sample represented by waveform 1260-2 in interface 1255-1 (e.g., FIG. 12V)) (e.g., input 1278 results in the selection of the audio sample represented by waveform 1260-4 in interface 1255-3 (e.g., FIG. 12AB)). Record (1316) (e.g., store (e.g., locally and / or on a server)) (e.g., in response to receiving a set of one or more user inputs). In some embodiments, the set of one or more user inputs includes an input corresponding to a representation of the first audio sample (e.g., input 1274) or the second audio sample (e.g., input 1277).In some embodiments, the set of one or more user inputs includes an input on a selection affordance (e.g., an input on a continuation affordance 1278) received while an indicator (e.g., a focus selector, a bold outline) is displayed indicating that the first audio sample is currently selected or that the second audio sample is currently selected, and recording the selection includes recording the selection of the audio sample currently indicated as the selected audio sample as the preferred sample.

[0346] After receiving one or more inputs (e.g., 1266, 1268, 1272, 1273, 1274, 1275-1, 1275-2, 1276, 1277, 1278, 1283, 1285), the computer system (e.g., 1200) outputs (1318) first audio data (e.g., audio generated at headphone device 1245 (e.g., represented in some embodiments by the presence of sound graphic 1245-1)) (e.g., audio media (e.g., music, sound recording, audio component of audiovisual media)) via the audio generation component (e.g., 1245).

[0347] In accordance with the first audio sample (e.g., 1260-1 in interface 1255-1 (e.g., FIG. 12U)) (e.g., 1260-3 in interface 1255-2 (e.g., FIG. 12X)) (e.g., 1260-3 in interface 1255-3 (e.g., FIG. 12AA)) recorded as a preferred sample (e.g., the first audio sample is selected as the preferred sample), output of the first audio data (e.g., current audio playback, future audio playback) is based (1320) on (e.g., generated using) at least one audio characteristic of the first set of audio characteristics (e.g., in FIG. 12AA, the audio generated by headphone device 1245 is based on the audio selected as a result of selecting VERSION 1 toggle 1257-1 and input 1276 in FIG. 12Z) (e.g., selecting one or more values ​​of amplification, balance, speech clarity, and brightness for output of audio playback from the corresponding first values ​​of the first set of audio characteristics).

[0348] In accordance with the second audio sample (e.g., 1260-2 in interface 1255-1 (e.g., FIG. 12V)) (e.g., 1260-2 in interface 1255-2 (e.g., FIG. 12W)) (e.g., 1260-4 in interface 1255-3 (e.g., FIG. 12AB)) recorded as the preferred sample (e.g., the second audio sample is selected as the preferred sample), output of the first audio data (e.g., current audio playback, future audio playback) is based (1322) on (e.g., generated using) at least one audio characteristic of the set of second audio characteristics (e.g., in FIG. 12W, the audio generated by headphone device 1245 is based on the audio selected as a result of selecting version 2 toggle 1257-2 and input 1273 in FIG. 12V) (e.g., selecting one or more values ​​of amplification, balance, speech clarity, and brightness for output of audio playback from corresponding second values ​​of the set of second audio characteristics).

[0349] In some embodiments, after recording the selection of a first audio sample (e.g., 1260-1 in interface 1255-1 (e.g., FIG. 12U)) (e.g., 1260-3 in interface 1255-2 (e.g., FIG. 12X)) (e.g., 1260-3 in interface 1255-3 (e.g., FIG. 12AA)) as a preferred sample, or the selection of a second audio sample (e.g., 1260-2 in interface 1255-1 (e.g., FIG. 12V)) (e.g., 1260-2 in interface 1255-2 (e.g., FIG. 12W)) (e.g., 1260-4 in interface 1255-3 (e.g., FIG. 12AB)) as a preferred sample, the computer system (e.g., 1200) may select a display generation component (e.g., 12 12A)) and a representation (e.g., 1257-2 in a subsequent interface (e.g., 1255-2, 1255-3)) of a third audio sample (e.g., 1260-3 in interface 1255-2 (e.g., FIG. 12X)) (e.g., 1260-3 in interface 1255-3 (e.g., FIG. 12AA)) having a third set of audio characteristics. In some embodiments, at least one of the third audio sample or the fourth audio sample is based on (e.g., selected according to) a recorded selection of the first audio sample or the second audio sample as a preferred sample. In some embodiments, the representations of the first and second audio samples form a first audio sample comparison in a series of audio sample comparisons, and after the first or second audio sample is selected, the display generation component stops displaying the first audio sample comparison (e.g., the representation of the first and second audio samples) and displays a subsequent audio sample comparison including representations of the third and fourth audio samples.

[0350] In some embodiments, the third audio sample is the first audio sample (e.g., 1260-3 in interface 1255-2 (e.g., FIG. 12X)) (e.g., 1260-3 in interface 1255-3 (e.g., FIG. 12AA)) or the second audio sample (e.g., 1260-2 in interface 1255-2 (e.g., FIG. 12W)) (e.g., 1260-4 in interface 1255-3 (e.g., FIG. 12AB)). In some embodiments, one of the audio samples in the subsequent audio sample comparison is an audio sample in the previous audio sample comparison. For example, if the first audio sample is selected as the preferred audio sample, one of the audio samples in the next audio sample comparison is the first audio sample. Conversely, if the second audio sample is selected as the preferred audio sample, one of the audio samples in the next audio sample comparison is the second audio sample.

[0351] In some embodiments, a representation of a first audio sample (e.g., 1257-1), when selected while the first audio sample is not being output (see, e.g., FIG. 12W), causes output of at least a second portion of the first audio sample (e.g., a portion of the first audio sample that is the same as or different from the portion of the first audio sample) via an audio generation component (e.g., 1245) (e.g., in FIG. 12W, input 1274 at version 1 toggle 1257-1 causes audio output at headphone device 1245 to switch to the audio associated with toggle 1257-1, as represented by the transition from waveform 1260-2 in FIG. 12W to waveform 1260-3 in FIG. 12X). In some embodiments, a representation of the second audio sample (e.g., 1257-2), when selected while the second audio sample is not being output (e.g., see FIG. 12AA), causes output of at least a portion of the second audio sample via the audio generation component (e.g., in FIG. 12AA, input 1277 at version 2 toggle 1257-2 causes audio output at headphone device 1245 to switch to the audio associated with toggle 1257-2, as represented by the transition from waveform 1260-3 in FIG. 12AA to waveform 1260-4 in FIG. 12AB). In some embodiments, displaying an audio preference interface (e.g., 1255-1, 1255-2, 1255-3) includes displaying a selectable volume control user interface object (e.g., 1258) configured to adjust the volume of audio being output while the selectable volume control user interface object is displayed (e.g., in response to a set of one or more user inputs).Displaying an audio preference interface with a selectable volume control user interface object allows a user to more quickly and easily compare and adjust the audio being generated without having to display a separate interface for accessing volume control, thereby reducing the number of inputs required to perform volume adjustments and compare audio samples. Reducing the number of inputs required to perform actions enhances device usability, makes the user device interface more efficient (e.g., by helping the user make appropriate inputs when operating / interacting with the device and reducing user errors), and also reduces device power usage and improves battery life by allowing the user to use the device more quickly and efficiently. In some embodiments, the audio preference interface is used to toggle between selecting a first audio sample or a second audio sample, and the volume control user interface object is used to adjust the volume of the selected first or second audio sample (see, e.g., FIGS. 12X-12Z). For example, if the first audio sample is selected, adjusting the volume control interface object increases or decreases the output volume of the first audio sample being played (e.g., using an audio generation component). Alternatively, if the second audio sample is selected, adjusting the volume control interface object increases or decreases the output volume of the second audio sample being played.

[0352] In some embodiments, the first audio sample (e.g., audio associated with toggle 1257-1 for version 1) and the second audio sample (e.g., audio associated with toggle 1257-2 for version 2) are both based on second audio data (e.g., audio generated by headphone device 1245 in FIG. 12V or FIG. 12W) (e.g., audio media (e.g., music, sound recording, audio component of audiovisual media)) (e.g., the first audio sample and the second audio sample are samples of the same audio media having a playback time (e.g., playback duration) but a different set of audio characteristics). In some embodiments, the second audio data is the first audio data. In some embodiments, while the computer system (e.g., 1200) outputs the second audio data as part of a first audio sample or as part of a second audio sample at a first point in time (e.g., a timestamp, a particular time within the overall playback time) within the playback time of the second audio data (e.g., while outputting the second audio data based on the first set of audio characteristics or the second set of audio characteristics), the computer system receives a second set of one or more user inputs (e.g., input 1272, input 1275) via one or more input devices. In some embodiments, the second audio data is output as a loop playback such that when the end of the playback time is reached, the audio resumes from the beginning of the playback time (e.g., without interruption).In some embodiments, in response to receiving a second set of one or more user inputs, in accordance with determining that the second audio data is being output as part of the first audio sample and determining that the set of one or more user inputs includes a selection of a representation of the second audio sample, the computer system continues to output the second audio data from the first time point (e.g., substantially from the first time point) and transitions to outputting the second audio data as part of the second audio sample (e.g., changing playback of the second audio data based on the first set of audio characteristics to the second set of audio characteristics while continuing to play the second audio data from the same time point) (e.g., in FIGS. 12U and 12V , in response to input 1272, audio continues to play on headphone device 1245 and switches from audio characteristics associated with VERSION 1 toggle 1257-1 to audio characteristics associated with VERSION 2 toggle 1257-2). In some embodiments, in response to receiving a second set of one or more user inputs, in accordance with determining that the second audio data is being output as part of the second audio sample and determining that the set of one or more user inputs includes a selection of a representation of the first audio sample, the computer system continues to output the second audio data from the first time point and transitions to outputting the second audio data as part of the first audio sample (e.g., changing playback of the second audio data based on the set of second audio characteristics to the first set of audio characteristics while continuing to play the second audio data from the same time point) (e.g., in FIGS. 12W and 12X, in response to input 1274, audio continues to play on headphone device 1245 and switches from audio characteristics associated with VERSION 2 toggle 1257-2 to audio characteristics associated with VERSION 1 toggle 1257-1).Transitioning the output of the second audio data based on the selection of a representation of the audio sample allows a user to compare and contrast different audio samples without having to initiate audio playback for each comparison while continuing to output the second audio data, thereby reducing the number of inputs required to perform the audio comparisons. Reducing the number of inputs required to perform operations enhances device usability, makes the user device interface more efficient (e.g., by assisting the user in making appropriate inputs when operating / interacting with the device and reducing user errors), and also reduces device power usage and improves battery life by allowing the user to use the device more quickly and efficiently. In some embodiments, audio is output in a loop while the user selects a representation of the first audio sample or a representation of the second audio sample. As the user toggles between selecting a representation of the first audio sample and a representation of the second audio sample, the output audio toggles between the first audio sample (having a first set of audio characteristics) and the second audio sample (having a second set of audio characteristics).

[0353] In some embodiments, at least one of the first audio sample or the second audio sample includes a speech audio sample (e.g., audio including a recorded human speech). In some embodiments, the audio preference interface includes a volume control interface when one or more of the audio samples includes a speech audio recording. In some embodiments, the audio preference interface does not include a volume control interface when one or more of the audio samples includes a speech audio recording.

[0354] In some embodiments, after recording the selection of the first audio sample as the preferred audio sample or after selecting the second audio sample as the preferred audio sample (and, in some embodiments, before outputting the first audio data), the computer system (e.g., 1200) displays, via the display generation component (e.g., 1202), a recommended audio adjustment interface (e.g., 1270, 1280) that includes simultaneously displaying a first audio preview interface object (e.g., 1282-1) corresponding to a recommended set of audio characteristics (in some embodiments, the set of recommended audio characteristics is selected based on at least the preferred audio sample recorded in response to the set of one or more inputs) and a second audio preview interface object (e.g., 1282-2) corresponding to a fifth set of audio characteristics that is different from the set of recommended audio characteristics (e.g., the recommended audio adjustments are based at least in part on the recorded selection of the first or second audio sample as the preferred audio sample). In some embodiments, the fifth set of audio characteristics is a pre-defined set of audio characteristics (e.g., default or standard audio characteristics) that is not based on a selection recorded using the audio preferences interface. In some embodiments, the computer system receives a third set of one or more inputs (eg, inputs on 1282-1, 1283, 1285) via one or more input devices.In some embodiments, in response to receiving a third set of one or more inputs, and in accordance with determining that the third set of one or more inputs includes a selection of a first audio preview interface object (e.g., an input on 1282-1, input 1285), the computer system outputs third audio data (e.g., audio represented by waveform 1260-5) (e.g., a preview of the output audio) based on (e.g., using) the set of recommended audio characteristics (e.g., the preview of the output audio includes the recommended audio adjustments, the preview of the output audio has customized audio settings applied thereto) (in some embodiments, if output is already occurring based on the set of recommended audio characteristics, the output continues). In some embodiments, in response to receiving a third set of one or more inputs and in accordance with determining that the third set of one or more inputs includes a selection of a second audio preview interface object (e.g., 1283), the computer system outputs third audio data based on (using) the fifth set of audio characteristics (e.g., the audio represented by waveform 1260-6) (e.g., the preview of the output audio does not include the recommended audio adjustments, the preview of the output audio has standard audio settings applied thereto). (In some embodiments, if output is already occurring based on the fifth set of audio characteristics, the output continues.) Outputting the third audio data based on the recommended set of audio characteristics or the fifth set of audio characteristics in response to selection of the first or second audio preview interface object allows a user to compare and contrast audio settings based on the recommended set of audio characteristics or the fifth set of audio settings without accepting, rejecting, or modifying the audio settings to compare playback of audio with different characteristics, thereby reducing the number of inputs required to set audio settings.Reducing the number of inputs required to perform actions enhances device usability, makes the user device interface more efficient (e.g., by assisting the user in making appropriate inputs when operating / interacting with the device and reducing user errors), and reduces device power usage and improves battery life by allowing the user to use the device more quickly and efficiently. In some embodiments, the recommended audio adjustment interface allows the user to preview output audio with enabled or disabled recommended / customized audio settings. In some embodiments, the recommended audio adjustment interface further includes a recommendation interface object that, when selected, sets the recommended set of audio features as the set of audio features for subsequent playback of audio data of at least a first type (e.g., audio media such as music or video). In some embodiments, the recommended audio adjustment interface further includes an interface object that, when selected, sets a fifth set of audio features as the set of audio features for subsequent playback of audio data of at least a first type (e.g., audio media such as music or video). In some embodiments, the recommended audio adjustment interface includes an indication that audio adjustments are recommended or not required (e.g., the fifth set of audio features will be used for subsequent playback).

[0355] In some embodiments, a computer system (e.g., 1200) displays selectable ambient sound amplification controls (e.g., 1286, 1289) via a display generation component (e.g., 1202). In some embodiments, the computer system receives inputs (e.g., 1287, 1289-1, 1291-1, 1291-2, 1291-3, 1292, 1293) corresponding to the selectable ambient sound amplification controls. In some embodiments, in response to the inputs corresponding to the selectable ambient sound amplification controls, the computer system adjusts audio characteristics (e.g., 1286-1, 1286-2, 1286-3, 1290-1, 1290-2, 1290-3, noise control function) (e.g., volume, balance, speech clarity, brightness) of the computer system's ambient sound amplification function (e.g., changing settings that affect future operation of the sound amplification function). In some embodiments, the audio generation component is a set of headphones (e.g., 1245) (e.g., outer ear or in-ear headphones), and the computer system is configured to communicate with a microphone (e.g., built into the headphones) for detecting ambient sound and to amplify the detected ambient sound using the audio generation component. In some embodiments, amplifying the ambient noise can allow a user to better hear the ambient sounds of their environment (e.g., without having to remove the headphones). In some embodiments, the audio characteristics of the ambient sound amplification function of the computer system are selected from the group consisting of amplification, balance, brightness, and combinations thereof.

[0356] In some embodiments, the computer system (e.g., 1200) displays, via the display generation component (e.g., 1202), a representation (e.g., 1233-1, 1233-2, 1215-4) of an existing audio profile (e.g., an audiogram, a recording generated by a previous hearing test) (e.g., before or after displaying the audio preference interface (e.g., 1255)). In some embodiments, the audiogram was provided by a medical institution. In some embodiments, the process of modifying the output of the audio playback based on the existing audio profile includes customizing audio settings based on the existing audio profile. In some embodiments, this includes displaying one or more representations of the previous audiogram test, receiving a selection of one of the representations of the previous audiogram test, and applying recommended audio settings based on the audiogram test results associated with the selected representation of the previous audiogram test. In some embodiments, the computer system receives a set of one or more inputs including an input (e.g., a selection) corresponding to a representation of the existing audio profile. In some embodiments, in response to a set of one or more inputs including inputs corresponding to a representation of an existing audio profile, the computer system initiates a process for configuring one or more audio characteristics for audio playback (e.g., future audio playback of audio data) based on the existing audio profile. Initiating a process for configuring one or more audio characteristics for audio playback based on the existing audio profile allows a user to select a custom audio setting that is optimized based on the user's hearing ability without having to initiate a custom audio setup process, thereby reducing the number of inputs required to create a custom audio setting.Reducing the number of inputs required to perform an action enhances the usability of the device, makes the user device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and also reduces the device's power usage and improves battery life by allowing the user to use the device more quickly and efficiently.

[0357] In some embodiments, the audio generation component (e.g., 1245) is a first external audio output device (e.g., a first set of headphones 1245). In some embodiments, after receiving one or more sets of user inputs, the computer system (e.g., 1200) generates a first audio setting profile (e.g., the custom audio setting shown in FIG. 12AF) based at least on the recorded selections. In some embodiments, after the audio setting profile is created, it is associated with the first external audio output device such that the cus...

Claims

1. a first electronic device including a display device; displaying via the display device a first user interface including a graphical object that changes appearance based on a noise level; receiving first noise level data corresponding to a first noise level below a threshold noise level; responsive to receiving the first noise level data, displaying the graphical object in a first color having an active portion of a first size based on the first noise data; receiving second noise level data corresponding to a second noise level different from the first noise level while maintaining the display of the first user interface; in response to receiving the second noise level data; displaying the active portion at a second size based on the second noise level, the second size being different from the first size; displaying the active portion in a second color different from the first color in response to determining that the second noise level exceeds the threshold noise level; maintaining the display of the graphical object in the first color in accordance with a determination that the second noise level does not exceed the threshold noise level; A method comprising:

2. receiving third noise level data corresponding to a third noise level below the threshold noise level while displaying the graphical object having the active portion at the second size and the second color; In response to receiving the third noise level data, displaying the active portion in the first color and a third size based on the third noise level data, the third size being smaller than the second size; The method of claim 1 further comprising:

3. the graphical object changes based on a noise level over a first period of time; 3. The method of claim 1, wherein the first user interface further comprises a second graphical object whose appearance changes based on a noise level over a second period of time that is different from the first period of time.

4. Displaying the first user interface includes: displaying a first affordance that, when selected, displays a second user interface in accordance with determining that the current noise level is below a second threshold noise level; and displaying a second affordance different from the first affordance that, when selected, displays a third user interface in accordance with a determination that the current noise level exceeds the second threshold noise level.

5. 5. The method of claim 1, wherein the electronic device includes one or more noise sensors, and the first noise level data and the second noise level data are received from the one or more noise sensors.

6. The method of any one of claims 1 to 5, wherein the first noise level data and the second noise level data are received from a second electronic device different from the first electronic device.

7. In accordance with determining that a set of noise notification criteria are satisfied at a first time prior to displaying the first user interface, the noise notification criteria include a criterion that is satisfied when a current noise level over a third time period exceeds a third threshold noise level; an indication of the current noise level over the third period of time; and a third affordance; and receiving a user input corresponding to the third affordance while displaying the third affordance; displaying the first user interface in response to receiving the user input corresponding to the third affordance; The method of any one of claims 1 to 6, further comprising:

8. The method of claim 7 , wherein the set of noise notification criteria is not met when a second noise notification level is displayed within a predetermined time period prior to the first time point.

9. The noise level notification further includes a fourth affordance associated with a second predetermined time period, and the method further comprises: receiving an input corresponding to the fourth affordance; and refraining from displaying further instances of a noise level notification for the second predetermined period in response to receiving the input corresponding to the fourth affordance.

10. sampling noise level data at a first sampling rate while the first user interface is displayed; sampling noise level data at a second sampling rate different from the first sampling rate while the first user interface is not displayed; The method of any one of claims 1 to 9, further comprising:

11. 11. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device including a display device, the one or more programs comprising instructions for performing the method of any one of claims 1 to 10.

12. A display device; one or more processors; a memory storing one or more programs configured to be executed by said one or more processors, said one or more programs comprising instructions for carrying out the method of any one of claims 1 to 10; , an electronic device.

13. A display device; means for carrying out the method according to any one of claims 1 to 10; An electronic device comprising:

14. 1. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device including a display device, the one or more programs comprising: displaying via the display device a first user interface including a graphical object that changes appearance based on the noise level; receiving first noise level data corresponding to a first noise level below a threshold noise level; responsive to receiving the first noise level data, displaying a graphical object in a first color having an active portion of a first size based on the first noise data; receiving second noise level data corresponding to a second noise level different from the first noise level while maintaining the display of the first user interface; in response to receiving the second noise level data; displaying the active portion at a second size based on the second noise level, the second size being different from the first size; displaying the active portion in a second color different from the first color in response to determining that the second noise level exceeds the threshold noise level; A non-transitory computer-readable storage medium comprising instructions for maintaining the display of the graphical object in the first color in accordance with a determination that the second noise level does not exceed the threshold noise level.

15. A display device; one or more processors; An electronic device comprising: a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising: displaying via the display device a first user interface including a graphical object that changes appearance based on the noise level; receiving first noise level data corresponding to a first noise level below a threshold noise level; responsive to receiving the first noise level data, displaying the graphical object in a first color having an active portion of a first size based on the first noise data; receiving second noise level data corresponding to a second noise level different from the first noise level while maintaining the display of the first user interface; in response to receiving the second noise level data; displaying the active portion at a second size based on the second noise level, the second size being different from the first size; displaying the active portion in a second color different from the first color in response to determining that the second noise level exceeds the threshold noise level; pursuant to a determination that the second noise level does not exceed the threshold noise level, maintaining the display of the graphical object in the first color.

16. A display device; means for displaying, via the display device, a first user interface including a graphical object whose appearance changes based on the noise level; means for receiving first noise level data corresponding to a first noise level below a threshold noise level; means for displaying the graphical object in a first color, the graphical object having an active portion of a first size based on the first noise level data, in response to receiving the first noise level data; means for receiving second noise level data corresponding to a second noise level different from the first noise level while maintaining display of the first user interface; in response to receiving the second noise level data; displaying the active portion at a second size based on the second noise level, the second size being different from the first size; displaying the active portion in a second color different from the first color in response to determining that the second noise level exceeds the threshold noise level; means for maintaining the display of the graphical object in the first color in accordance with a determination that the second noise level does not exceed the threshold noise level; An electronic device comprising:

17. In an electronic device including a display device and a touch-sensitive surface, receiving first noise level data attributable to a first device type; receiving second noise level data attributable to a second device type different from the first device type; displaying a first user interface via the display device, the first user interface comprising: a first representation of received noise level data based on the first noise level data and the second noise level data; a first device type data filtering affordance; Detecting a first user input corresponding to a selection of the first device type data filtering affordance while displaying the first user interface; displaying a second representation of received noise level data based on the second noise level data and not based on the first noise level data in response to detecting the first user input; A method comprising:

18. Displaying the second representation of received noise level data 18. The method of claim 17, comprising maintaining a display of a first representation of received noise level data, wherein the second representation of received noise level data is visually distinct from the first representation of received noise level data.

19. The method of any one of claims 17 to 18, wherein the second noise level data corresponds to noise level data attributable to a single device.

20. The method of any one of claims 17 to 19, wherein the first noise level data corresponds to noise level data resulting from a plurality of devices.

21. the second noise level data includes third noise level data attributable to a third device type; the first user interface includes a second device type filtering affordance corresponding to the third noise level data; The method further comprises: Detecting user input corresponding to a selection of the second device type filtering affordance while displaying the first user interface; displaying a third representation of the third noise level data in response to detecting the user input corresponding to a selection of the second device type filtering affordance; and 21. The method of claim 20, comprising:

22. 22. The method of claim 17, wherein the first user interface includes an average noise exposure level indicator that indicates an average noise exposure level corresponding to the first noise level data and the second noise level data for a first period of time before detecting the first user input.

23. in response to detecting the user input corresponding to a selection of the first device type filtering affordance; updating the average noise exposure level indicator to indicate an average noise level corresponding to the second noise level data; 23. The method of claim 22, further comprising:

24. 24. The method of any one of claims 17 to 23, wherein the second noise level data is based at least in part on one or more signals transmitted from the electronic device to one or more devices of the second type.

25. A method according to any one of claims 17 to 24, wherein the first representation of received noise level data comprises an indication of a maximum value of the noise level data and a minimum value of the noise level data for a second period of time.

26. 26. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device including a display device and a touch-sensitive surface, the one or more programs comprising instructions for performing the method of any one of claims 17 to 25.

27. A display device; a touch-sensitive surface; and one or more processors; a memory storing one or more programs configured to be executed by said one or more processors, said one or more programs comprising instructions for carrying out the method of any one of claims 17 to 25; , an electronic device.

28. A display device; a touch-sensitive surface; and means for carrying out the method according to any one of claims 17 to 25; An electronic device comprising:

29. 1. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device including a display device and a touch-sensitive surface, the one or more programs comprising: first noise level data attributable to a first device type; receiving second noise level data attributable to a second device type different from the first device type; displaying a first user interface via the display device, the first user interface comprising: a first representation of received noise level data based on the first noise level data and the second noise level data; a first device type data filtering affordance; Detecting a first user input corresponding to a selection of the first device type data filtering affordance while displaying the first user interface; and in response to detecting the first user input, displaying a second representation of received noise level data based on the second noise level data and not based on the first noise level data.

30. A display device; a touch-sensitive surface; and one or more processors; An electronic device comprising: a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising: first noise level data attributable to a first device type; receiving second noise level data attributable to a second device type different from the first device type; displaying a first user interface via the display device, the first user interface comprising: a first representation of received noise level data based on the first noise level data and the second noise level data; a first device type data filtering affordance; Detecting a first user input corresponding to a selection of the first device type data filtering affordance while displaying the first user interface; and in response to detecting the first user input, displaying a second representation of the received noise level data based on the second noise level data and not based on the first noise level data.

31. A display device; a touch-sensitive surface; and An electronic device comprising: A receiving means, first noise level data attributable to a first device type; second noise level data attributable to a second device type different from the first device type; means for displaying a first user interface via the display device, the first user interface comprising: a first representation of received noise level data based on the first noise level data and the second noise level data; a first device type data filtering affordance; and means for detecting, while displaying the first user interface, a first user input corresponding to a selection of the first device type data filtering affordance; means for displaying a second representation of received noise level data based on the second noise level data and not based on the first noise level data in response to detecting the first user input.

32. 1. A computer system in communication with a display generating component, an audio generating component, and one or more input devices, comprising: via said display generation component, a representation of a first audio sample, the first audio sample having a first set of audio characteristics; displaying an audio preference interface, the audio preference interface including simultaneously displaying a representation of a second audio sample, the second audio sample having a second set of audio characteristics different from the first set of audio characteristics; While displaying the audio preferences interface, outputting at least a portion of the first audio sample via the audio generation component; receiving a set of one or more user inputs via the one or more input devices; after receiving the set of one or more inputs; recording the first audio sample selection as a preferred sample or the second audio sample selection as a preferred sample; outputting first audio data via the audio generation component; According to the first audio sample recorded as the preferred sample, the output of the first audio data is based on at least one audio characteristic of the first set of audio characteristics; outputting the first audio data according to the second audio sample recorded as the preferred sample, wherein the output is based on at least one audio characteristic of the second set of audio characteristics; A method comprising:

33. after recording the selection of the first audio sample as a preferred sample or after recording the selection of the second audio sample as a preferred sample, via the display generation component; a representation of a third audio sample, the third audio sample having a third set of audio characteristics; and and a representation of a fourth audio sample, the fourth audio sample having a fourth set of audio characteristics different from the third set of audio characteristics; at least one of the third audio sample or the fourth audio sample is based on the recorded selection of the first audio sample or the second audio sample as a preferred sample; 33. The method of claim 32, further comprising:

34. causing output of at least a second portion of the first audio sample via the audio generation component when the representation of the first audio sample is selected while the first audio sample is not being output; causing output of at least a portion of the second audio sample via the audio generation component when the representation of the second audio sample is selected while the second audio sample is not being output; displaying the audio preference interface includes displaying a selectable volume control user interface object configured to adjust a volume of audio being output while the selectable volume control user interface object is displayed; The method of any one of claims 32 to 33, comprising:

35. The first audio sample and the second audio sample are both based on second audio data having a playback time, and the method further comprises: receiving, while outputting the second audio data, a second set of one or more user inputs via the one or more input devices at a first point in time in the playback time of the second audio data, either as part of the first audio sample or as part of the second audio sample; in response to receiving a second set of the one or more user inputs; continuing to output the second audio data from the first time point in accordance with a determination that the second audio data is being output as part of the first audio sample and in accordance with a determination that the set of one or more user inputs includes a selection of the representation of the second audio sample, and transitioning to outputting the second audio data as part of the second audio sample; 35. The method of claim 32, further comprising: continuing to output the second audio data from the first time point and transitioning to outputting the second audio data as part of the first audio sample in accordance with a determination that the second audio data is being output as part of the second audio sample and in accordance with a determination that the set of one or more user inputs includes a selection of the representation of the first audio sample.

36. after recording the selection of the first audio sample as a preferred audio sample or after recording the selection of the second audio sample as the preferred audio sample, via the display generation component; a first audio preview interface object corresponding to a set of recommended audio characteristics; and a second audio preview interface object corresponding to a fifth set of audio characteristics different from the set of recommended audio characteristics. receiving a third set of one or more inputs via the one or more input devices; in response to detecting the third set of one or more inputs; outputting third audio data based on the set of recommended audio characteristics in accordance with determining that the third set of one or more inputs includes a selection of the first audio preview interface object; and outputting the third audio data based on the fifth set of audio characteristics in response to determining that the third set of one or more inputs includes a selection of the second audio preview interface object; and The method of any one of claims 32 to 35, further comprising:

37. displaying, via said display generation component, a representation of an existing audio profile; receiving a set of one or more inputs including inputs corresponding to the representation of the existing audio profile; initiating a process for configuring one or more audio characteristics of audio playback based on the existing audio profile in response to the set of one or more inputs including an input corresponding to the representation of the existing audio profile; The method of any one of claims 32 to 36, further comprising:

38. the audio generating component is a first external audio output device, the method further comprising: generating a first audio setting profile based at least on the recorded selections after receiving the set of one or more user inputs; detecting communication with a second external audio output device different from the first external audio output device; and in response to detecting communication with the second audio output device, displaying via the display generation component a user interface object that, when selected, initiates a process for associating the first audio setting profile with the second external audio output device.

39. displaying, via the display generation component, a set of one or more audio type controls; receiving a set of one or more inputs including inputs directed to the set of one or more audio type controls; in response to receiving the set of one or more inputs including inputs directed to the set of one or more audio type controls; configuring one or more audio characteristics for audio playback of a first type of audio in accordance with determining that the set of one or more inputs, including inputs directed to the set of one or more audio type controls, includes a first input; configure one or more audio characteristics of audio reproduction of a second type of audio different from the first type of audio without configuring one or more audio characteristics of audio reproduction of the first type of audio in accordance with a determination that the set of one or more inputs including the input directed to the set of one or more audio type controls includes a second input different from the first input; The method of any one of claims 32 to 38, further comprising:

40. 40. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system having a display generation component, an audio generation component, and one or more input devices, the one or more programs comprising instructions for performing the method of any one of claims 32 to 39.

41. a display generation component; an audio generation component; one or more input devices; one or more processors; A computer system comprising: and a memory storing one or more programs configured to be executed by said one or more processors, said one or more programs including instructions for carrying out the method of any one of claims 32 to 39.

42. a display generation component; an audio generation component; one or more input devices; means for carrying out the method according to any one of claims 32 to 39; A computer system comprising:

43. 1. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system having a display generating component, an audio generating component, and one or more input devices, the one or more programs comprising: via said display generation component, a representation of a first audio sample, the first audio sample having a first set of audio characteristics; and a representation of a second audio sample, the second audio sample having a second set of audio characteristics that is different from the first set of audio characteristics; and While displaying the audio preferences interface, outputting at least a portion of the first audio sample via the audio generation component; receiving one or more sets of user inputs via the one or more input devices; after receiving the set of one or more inputs; recording the first audio sample selection as a preferred sample or the second audio sample selection as a preferred sample; outputting first audio data via the audio generation component; According to the first audio sample recorded as the preferred sample, the output of the first audio data is based on at least one audio characteristic of the first set of audio characteristics; a non-transitory computer-readable storage medium comprising instructions for outputting, in accordance with the second audio sample recorded as the preferred sample, the output of the first audio data being based on at least one audio characteristic of the second set of audio characteristics;

44. a display generation component; an audio generation component; one or more input devices; one or more processors; A computer system comprising: a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising: via said display generation component, a representation of a first audio sample, the first audio sample having a first set of audio characteristics; displaying an audio preference interface, the audio preference interface including simultaneously displaying a representation of a second audio sample, the second audio sample having a second set of audio characteristics different from the first set of audio characteristics; While displaying the audio preferences interface, outputting at least a portion of the first audio sample via the audio generation component; receiving a set of one or more user inputs via the one or more input devices; after receiving the set of one or more inputs; recording the first audio sample selection as a preferred sample or the second audio sample selection as a preferred sample; outputting first audio data via the audio generation component; According to the first audio sample recorded as the preferred sample, the output of the first audio data is based on at least one audio characteristic of the first set of audio characteristics; and outputting the first audio data in accordance with the second audio sample recorded as the preferred sample, the output being based on at least one audio characteristic of the second set of audio characteristics.

45. a display generation component; an audio generation component; one or more input devices; A computer system comprising: via said display generation component, a representation of a first audio sample, the first audio sample having a first set of audio characteristics; and a representation of a second audio sample, the second audio sample having a second set of audio characteristics that is different from the first set of audio characteristics; and While displaying the audio preferences interface, means for outputting at least a portion of the first audio sample via the audio generation component; means for receiving one or more sets of user inputs via the one or more input devices; after receiving the set of one or more inputs; means for recording the first audio sample selection as a preferred sample or the second audio sample selection as a preferred sample; means for outputting first audio data via the audio generation component, According to the first audio sample recorded as the preferred sample, the output of the first audio data is based on at least one audio characteristic of the first set of audio characteristics; and means for outputting the first audio data according to the second audio sample recorded as the preferred sample, the outputting being based on at least one audio characteristic of the second set of audio characteristics.

46. 1. A computer system in communication with an audio generating component, comprising: Detecting that an audio exposure threshold criterion has been met while causing output of audio data at a first volume via the audio generation component; in response to detecting that the audio exposure threshold criterion has been met; reducing the volume of the output of audio data to a second volume lower than the first volume while continuing to produce the output of audio data; A method comprising:

47. 47. The method of claim 46, wherein the audio exposure threshold criterion is met when the output of audio data at the first volume exceeds an instantaneous sound pressure value.

48. A method according to any one of claims 46 to 47, wherein the audio exposure threshold criterion is met when the aggregate sound pressure value of the output of audio data exceeds a threshold for a duration measured over a predetermined period of time.

49. 49. A method according to any one of claims 46 to 48, wherein reducing the volume of output of audio data to the second volume comprises gradually reducing the volume from the first volume to the second volume.

50. the computer system being in communication with a display generation component, the method further comprising: in response to detecting that the audio exposure threshold criterion has been met; A method according to any one of claims 46 to 49, comprising displaying via said display generation component a representation of the volume of an output of audio data.

51. and in response to detecting that the audio exposure threshold criterion has been met, causing, via the audio generating component, the output of an audible indication that the volume of output of audio data has been reduced; 51. The method of any one of claims 46 to 50, further comprising:

52. outputting an alert indicating that the volume of output of audio data has been reduced; 52. The method of any one of claims 46 to 51, further comprising:

53. the audio data is generated from an application running on the computer system; the alert is generated from a system control component of the computer system; 53. The method of claim 52.

54. the computer system being in communication with a display generation component, the method further comprising: receiving, at the computer system, an input directed to the alert; and displaying, via said display generating component, a volume limiting control corresponding to controlling output of audio data after receiving said input directed to said alert.

55. 55. The method of claim 54, wherein the volume limit control includes an affordance that, when selected, toggles the state of a process for reducing the predicted output volume of an output audio signal that exceeds a selectable threshold.

56. displaying the volume limit control, Notification of aggregate sound pressure limits, A method according to any one of claims 54 to 55, further comprising displaying at least one of: a notification of the instantaneous sound pressure limit;

57. displaying the volume limit control, 57. The method of any one of claims 54 to 56, further comprising displaying an affordance that, when selected, initiates a process for classifying the audio-generating component as an audio-generating component other than headphones.

58. A method according to any one of claims 54 to 57, wherein the volume limit control includes an affordance that, when selected, initiates a process for adjusting the audio exposure threshold criteria.

59. the computer system being in communication with a second audio generating component, the method further comprising: outputting third audio data at a fifth volume via the second audio generating component; continuing to output audio data at the fifth volume according to the second audio generating component, the second audio generating component being a first type of audio generating component; in response to the second audio generating component being a second type of audio generating component, and in response to a determination that the audio exposure threshold criterion is met, reducing the volume of the output of audio data to a sixth volume lower than the fifth volume while continuing to produce the output of the third audio data; and outputting a third alert indicating that the volume of output of audio data has been reduced.

60. the computer system includes an audio input device, and the method further comprises:

60. The method of claim 59, comprising detecting an audio generating component type for the second audio generating component based on input received at the audio input device while the computer system is causing output of audio data via the second audio generating component.

61. Detecting a first input while the computer system is in communication with the second audio generating component, the first input corresponding to a request to display an audio settings interface; displaying the audio settings interface in response to detecting the first input, the audio settings interface including an affordance that, when selected, initiates a process for classifying the second audio generation component as the first type of audio generation component; detecting a second input corresponding to a request to display the audio settings interface while the computer system is not in communication with the second audio generating component; displaying the audio settings interface in response to detecting the second input, the audio settings interface not including an affordance that, when selected, initiates a process for classifying the second audio generation component as an audio generation component of the first type; 61. The method of any one of claims 59 to 60, further comprising:

62. prompting a user of the computer system to indicate whether the second audio generating component is an audio generating component of the second type in accordance with a determination that the second audio generating component has not been identified as an audio generating component of the second type; 60. The method of claim 59, further comprising:

63. the audio exposure threshold criteria include criteria that are met when the audio generating component is a headphone device; the headphone device is configured to have an output volume limit that is less than a maximum output volume of the headphone device.

63. The method of any one of claims 46 to 62.

64. receiving an input corresponding to a request to increase the volume of the output of audio data while causing the output of audio data at the second volume; increasing the volume of the output of audio data to a seventh volume greater than the second volume in response to receiving the input corresponding to the request to increase the volume of the output of audio data; 64. The method of any one of claims 46 to 63, further comprising:

65. the computer system being in communication with a display generation component, the method further comprising:

65. A method according to any one of claims 46 to 64, comprising displaying, via the display generation component, an audio control user interface while causing output of audio data, the audio control user interface including an audio exposure indicator that indicates an audio exposure level associated with a current volume of the output of audio data.

66. displaying the audio control user interface, displaying the audio exposure indicator having a first color in accordance with determining that the current volume of output of audio data does not exceed a first volume threshold; displaying the audio exposure indicator having a second color different from the first color in response to a determination that the current volume of output of audio data exceeds the first volume threshold but does not exceed a second volume threshold greater than the first volume threshold; 66. The method of claim 65, comprising: displaying the audio exposure indicator having a third color different from the first color and the second color in accordance with a determination that the current volume of output of audio data exceeds the second volume threshold.

67. Detecting an input directed to the audio exposure indicator; displaying, via the display generation component, an audio exposure user interface in response to detecting the input directed at the audio exposure indicator, the audio exposure user interface including a measurement of audio exposure data associated with an output of audio data; 67. The method of any one of claims 65 to 66, further comprising:

68. 68. A non-transitory computer readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with an audio generation component, the one or more programs comprising instructions for performing the method of any one of claims 46 to 67.

69. 1. A computer system in communication with an audio generation component, comprising: one or more processors; and a memory storing one or more programs configured to be executed by said one or more processors, said one or more programs including instructions for carrying out the method of any one of claims 46 to 67.

70. 1. A computer system in communication with an audio generation component, comprising: and means for carrying out the method of any one of claims 46 to 67.

71. 1. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with an audio generation component, the one or more programs comprising: Detecting that an audio exposure threshold criterion has been met while causing output of audio data at a first volume via the audio generation component; in response to detecting that the audio exposure threshold criterion has been met; A non-transitory computer-readable storage medium comprising instructions for reducing the volume of the output of audio data to a second volume lower than the first volume while continuing to produce the output of audio data.

72. 1. A computer system in communication with an audio generation component, comprising: one or more processors; a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising: Detecting that an audio exposure threshold criterion has been met while causing output of audio data at a first volume via the audio generation component; in response to detecting that the audio exposure threshold criterion has been met; 1. A computer system comprising instructions for reducing the volume of output of audio data to a second volume lower than the first volume while continuing to produce output of audio data.

73. a display generation component; an audio generation component; one or more input devices; A computer system comprising: means for detecting that an audio exposure threshold criterion has been met while causing output of audio data at a first volume via said audio generating component; in response to detecting that the audio exposure threshold criterion has been met; means for reducing the volume of the output of audio data to a second volume lower than the first volume while continuing to produce the output of audio data.

74. 1. A computer system in communication with an audio generating component, comprising: receiving output audio data associated with output audio generated using the audio generation component, the output audio including a first audio signal and a second audio signal, the output audio data including a first predicted output audio volume of the first audio signal and a second predicted output audio volume of the second audio signal; In accordance with determining that the output audio data satisfies a first set of criteria, the first set of criteria is satisfied when the first predicted output audio volume for the first audio signal exceeds an output audio volume threshold; causing output of the first audio signal at a reduced output audio volume that is below the first predicted output audio volume; causing output of the second audio signal at the second predicted output audio volume; upon determining that the output audio data does not satisfy the first set of criteria, causing output of the first audio signal at the first predicted output audio volume; causing output of the second audio signal at the second predicted output audio volume; A method comprising:

75. In accordance with determining that the output audio data satisfies a second set of criteria, the second set of criteria is satisfied when the second predicted output audio volume for the second audio signal exceeds the output audio volume threshold; causing output of the first audio signal at the first predicted output audio volume; causing output of the second audio signal at a reduced output audio volume that is below the second predicted output audio volume; 75. The method of claim 74, further comprising:

76. the computer system including a display generating component and one or more input devices, the method further comprising: displaying, via the display generation component, a volume control interface object representing a threshold range for the output audio volume threshold; detecting input corresponding to the volume control interface object via the one or more input devices; adjusting the output audio volume threshold to a second threshold different from the first threshold in response to detecting the input corresponding to the volume control interface object; receiving the output audio data including a third predicted output audio volume for a third audio signal and a fourth predicted output audio volume for a fourth audio signal; In accordance with determining that the output audio data satisfies a third set of criteria, the third set of criteria is satisfied when the third predicted output audio volume for the third audio signal exceeds the second one of the output audio volume thresholds; causing output of the third audio signal at a second reduced output audio volume that is below the third predicted output audio volume; causing output of the fourth audio signal at the fourth predicted output audio volume.

77. displaying a non-numeric text description of the first threshold value while displaying the volume control interface object representing the output audio volume threshold value having the first threshold value; displaying a non-numeric text description of the second threshold value after adjusting the output audio volume threshold from the first threshold value to the second threshold value; 77. The method of claim 76, further comprising:

78. The first set of criteria further includes a first criterion that is met when a volume control setting is enabled, and the method further comprises: upon determining that the output audio data satisfies the first set of criteria, refraining from outputting an alert indicating that the output audio volume of the first audio signal has exceeded the output audio volume threshold; In accordance with determining that the output audio data satisfies a fourth set of criteria, the fourth set of criteria is met when the first predicted output audio volume for the first audio signal exceeds an output audio volume threshold and the volume control setting is disabled; causing output of the first audio signal at the first predicted output audio volume; causing output of the second audio signal at the second predicted output audio volume; and outputting the alert indicating that the output audio volume of the first audio signal has exceeded the output audio volume threshold.

79. the output audio further comprises a fifth audio signal, the output audio data further comprises a fifth predicted output audio volume for the fifth audio signal, and the method further comprises: upon determining that the output audio data satisfies the first set of criteria, and causing output of the fifth audio signal at an increased output audio volume that is greater than the fifth predicted output audio volume.

80. the output audio volume threshold corresponds to a volume control setting associated with a user account; the volume control settings are applied to the computer system and to external computer systems associated with the user account.

80. The method of any one of claims 74 to 79.

81. the computer system is associated with a first user account; the output audio volume threshold is determined by a second user account associated with an external computer system and authorized to enable the output audio volume threshold on the computer system; 81. The method of any one of claims 74 to 80.

82. A method according to any one of claims 74 to 81, wherein the first set of criteria comprises criteria that are met when the output audio is media playback.

83. the output audio volume threshold is a first value, and the output audio data satisfies the first set of criteria, the method further comprising: after causing output of the first audio signal at the reduced output audio volume and causing output of the second audio signal at the second predicted output audio volume; receiving an input corresponding to a request to reduce the output audio volume threshold; in response to receiving the input corresponding to a request to reduce the output audio volume threshold, reducing the output audio volume threshold from the first value to a second value less than the first value; receiving output audio data associated with the output audio generated using the audio generation component, the output audio data including the first predicted output audio volume of the first audio signal and the second predicted output audio volume of the second audio signal; upon determining that the output audio data satisfies the first set of criteria, causing output of the first audio signal at a second reduced output audio volume that is below the first predicted output audio volume; causing output of the second audio signal at a second reduced output audio volume that is below the second predicted output audio volume.

84. the output audio volume threshold is a third value, and the output audio data satisfies the first set of criteria, the method further comprising: after causing output of the first audio signal at the reduced output audio volume and causing output of the second audio signal at the second predicted output audio volume; receiving an input corresponding to a request to increase the output audio volume threshold; increasing the output audio volume threshold from the third value to a fourth value greater than the third value in response to receiving the input corresponding to a request to increase the output audio volume threshold; receiving output audio data associated with the output audio generated using the audio generation component, the output audio data including the first predicted output audio volume of the first audio signal and the second predicted output audio volume of the second audio signal; in response to determining that the output audio data does not satisfy the first set of criteria; causing output of the first audio signal at the first predicted output audio volume; causing output of the second audio signal at the second predicted output audio volume.

85. 85. A non-transitory computer readable storage medium storing one or more programs configured to be executed by one or more processors of a computer in communication with an audio generation component, the one or more programs comprising instructions for performing the method of any one of claims 74 to 84.

86. 1. A computer system in communication with an audio generation component, comprising: one or more processors; and a memory storing one or more programs configured to be executed by said one or more processors, said one or more programs comprising instructions for carrying out the method of any one of claims 74 to 84.

87. 1. A computer system in communication with an audio generation component, comprising: and means for carrying out the method of any one of claims 74 to 84.

88. 1. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with an audio generation component, the one or more programs comprising: receiving output audio data associated with output audio generated using the audio generation component, the output audio including a first audio signal and a second audio signal, the output audio data including a first predicted output audio volume of the first audio signal and a second predicted output audio volume of the second audio signal; In accordance with determining that the output audio data satisfies a first set of criteria, the first set of criteria is satisfied when the first predicted output audio volume for the first audio signal exceeds an output audio volume threshold; causing output of the first audio signal at a reduced output audio volume that is below the first predicted output audio volume; causing output of the second audio signal at the second predicted output audio volume; upon determining that the output audio data does not satisfy the first set of criteria, causing output of the first audio signal at the first predicted output audio volume; and causing output of the second audio signal at the second predicted output audio volume.

89. 1. A computer system in communication with an audio generation component, comprising: one or more processors; a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising: receiving output audio data associated with output audio generated using the audio generation component, the output audio including a first audio signal and a second audio signal, the output audio data including a first predicted output audio volume of the first audio signal and a second predicted output audio volume of the second audio signal; In accordance with determining that the output audio data satisfies a first set of criteria, the first set of criteria is satisfied when the first predicted output audio volume for the first audio signal exceeds an output audio volume threshold; causing output of the first audio signal at a reduced output audio volume that is below the first predicted output audio volume; causing output of the second audio signal at the second predicted output audio volume; upon determining that the output audio data does not satisfy the first set of criteria, causing output of the first audio signal at the first predicted output audio volume; and causing output of the second audio signal at the second predicted output audio volume.

90. 1. A computer system in communication with an audio generation component, comprising: means for receiving output audio data associated with output audio generated using the audio generation component, the output audio including a first audio signal and a second audio signal, the output audio data including a first predicted output audio volume of the first audio signal and a second predicted output audio volume of the second audio signal; In accordance with determining that the output audio data satisfies a first set of criteria, the first set of criteria is satisfied when the first predicted output audio volume for the first audio signal exceeds an output audio volume threshold; means for causing output of the first audio signal at a reduced output audio volume that is below the first predicted output audio volume; means for causing output of the second audio signal at the second predicted output audio volume; upon determining that the output audio data does not satisfy the first set of criteria, means for causing output of the first audio signal at the first predicted output audio volume; means for causing output of the second audio signal at the second predicted output audio volume.

Images