User interface for managing audio exposure

Abstract

To provide an electronic device with faster and more efficient methods and interfaces for managing audio exposure.SOLUTION: An electronic device displays a graphical indication of a noise exposure level over a first period of time with an area of the graphical indication colored to represent the noise exposure level. The color of the area transitions from a first color to a second color when the noise exposure level exceeds a first threshold. The electronic device also displays noise exposure level attributable to a first output device type and a second output device type and, in response to selecting a filtering affordance, visually distinguishes a set of noise exposure levels attributable to the second output device type.SELECTED DRAWING: Figure 6A

Description

Cross - Reference to Related Applications

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

Technical Field

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

Background Art

[0003] Electronic devices can be used to manage the amount of audio to which a user of the electronic device is exposed. Information regarding 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 an electronic device are generally cumbersome and inefficient. For example, some existing techniques use complex and time-consuming user interfaces that may involve multiple key presses or keystrokes. Existing techniques require more time than necessary and waste the user's time and the device's energy. The latter problem is particularly significant in battery-operated devices.

[0005] Accordingly, the present technology provides an electronic device with a faster and more efficient method and interface for managing audio exposure. Such a method and interface optionally complement or replace other methods for managing audio exposure. Such a method and interface reduce the cognitive burden on the user and create a more efficient human-machine interface. In the case of battery-operated computing devices, such a method and interface conserve power and extend the battery charging interval.

[0006] According to some embodiments, a method is described that is executed on an electronic device including a display device. The method includes 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; in response to receiving the first noise level data, displaying, in a first color, a graphical object having an active portion of a first size based on the first noise data; while maintaining the display of the first user interface, receiving second noise level data corresponding to a second noise level different from the first noise level; in response to receiving the second noise level data, displaying the active portion in a second size based on the second noise level different from the first size; 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; and in accordance with 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.

[0007] 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. The one or more programs cause, via the display device, a first user interface including a graphical object whose appearance changes based on a noise level to be displayed, receive first noise level data corresponding to a first noise level below a threshold noise level, in response to the reception of the first noise level data, display a graphical object having an active portion of a first size based on the first noise level data in a first color, while maintaining the display of the first user interface, receive second noise level data corresponding to a second noise level different from the first noise level, in response to the reception of the second noise level data, display the active portion in a second size based on the second noise level different from the first size, display the active portion in a second color different from the first color according to a determination that the second noise level exceeds the threshold noise level, and maintain the display of the graphical object in the first color according to a determination that the second noise level does not exceed the threshold noise level.

[0008] 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. The one or more programs cause the display device to display a first user interface including a graphical object whose appearance changes based on a noise level, receive first noise level data corresponding to a first noise level below a threshold noise level, in response to the reception of the first noise level data, display a graphical object having an active portion of a first size based on the first noise level data in a first color, while maintaining the display of the first user interface, receive second noise level data corresponding to a second noise level different from the first noise level, in response to the reception of the second noise level data, display the active portion in a second size based on the second noise level different from the first size, display the active portion in a second color different from the first color according to a determination that the second noise level exceeds the threshold noise level, and maintain the display of the graphical object in the first color according to a determination that the second noise level does not exceed the threshold noise level.

[0009] According to some embodiments, an electronic device is described. The electronic device includes 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 cause the display device to display a first user interface including a graphical object whose appearance changes based on a noise level, receive first noise level data corresponding to a first noise level below a threshold noise level, in response to the reception of the first noise level data, display a graphical object having an active portion of a first size based on the first noise level data in a first color, while maintaining the display of the first user interface, receive second noise level data corresponding to a second noise level different from the first noise level, in response to the reception of the second noise level data, display the active portion in a second size based on the second noise level different from the first size, display the active portion in a second color different from the first color according to a determination that the second noise level exceeds the threshold noise level, and maintain the display of the graphical object in the first color according to a determination that the second noise level does not exceed the threshold noise level.

[0010] According to some embodiments, an electronic device is described. The electronic device includes a display device and means for displaying, via the display device, a first user interface including a graphical object whose appearance changes 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, in response to the reception of the first noise level data, a graphical object having an active portion of a first size based on the first noise data in a first color, means for 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, means for displaying, in response to the reception of the second noise level data, the active portion in a second size based on the second noise level different from the first size, and for displaying the active portion in a second color different from the first color according to a determination that the second noise level exceeds the threshold noise level, and means for maintaining the display of the graphical object in the first color according to a determination that the second noise level does not exceed the threshold noise level.

[0011] According to some embodiments, a method is described that is executed in an electronic device including a display device and a touch sensing surface. The method includes receiving first noise level data resulting from a first device type and second noise level data resulting from a second device type different from the first device type, displaying, via the display device, a first user interface including a first representation of 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 corresponding to a selection of the first device type data filtering affordance while the first user interface is being displayed, and displaying, in response to the detection of 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.

[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 comprising a display device and a touch sensing surface is described. The one or more programs receive first noise level data resulting from a first device type and second noise level data resulting from a second device type different from the first device type, and via the display device, display a first user interface that includes a first representation of 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; while the first user interface is being displayed, detect a first user input corresponding to a selection of the first device type data filtering affordance; and in response to the detection of the first user input, display 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.

[0013] 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 comprising a display device and a touch-sensing surface is described. The one or more programs receive first noise level data resulting from a first device type and second noise level data resulting from a second device type different from the first device type, and via the display device, display a first user interface that includes a first representation of 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; while the first user interface is being displayed, detect a first user input corresponding to a selection of the first device type data filtering affordance; and in response to the detection of the first user input, display 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.

[0014] According to some embodiments, an electronic device is described. The electronic device includes a display device, a touch sensing surface, 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 are configured to receive first noise level data resulting from a first device type and second noise level data resulting from a second device type different from the first device type, and via the display device, display a first user interface including a first representation of 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, detect a first user input corresponding to a selection of the first device type data filtering affordance while the first user interface is being displayed, and in response to the detection of the first user input, display 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. The electronic device includes a display device, a touch sensing surface, means for receiving first noise level data resulting from a first device type and second noise level data resulting from a second device type different from the first device type, means for displaying, via the display device, a first user interface including a first representation of 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 a first user input corresponding to a selection of the first device type data filtering affordance while the first user interface is being displayed, and means for displaying, in response to the detection of 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 in a computer system that communicates with a display generation component, an audio generation component, and one or more input devices. The method includes displaying an audio preference interface that, via the display generation component, simultaneously displays a representation of a first audio sample having a first set of audio characteristics and a representation of a second audio sample having a second set of audio characteristics different from the first set of audio characteristics; while the audio preference interface is being displayed, outputting at least a portion of the first audio sample via the audio generation component; receiving, via the one or more input devices, a set of one or more user inputs; after receiving the set of inputs, recording a selection of the first audio sample as the preferred sample or selecting the second audio sample as the preferred sample; and outputting first audio data via the audio generation component, the output of the first audio data being based on at least one audio characteristic of the first set of audio characteristics if the first audio sample is recorded as the preferred sample, and the output of the first audio data being based on at least one audio characteristic of the second set of audio characteristics if the second audio sample is 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 that communicates with a display generation component, an audio generation component, and one or more input devices is described. The one or more programs include displaying an audio preference interface that includes simultaneously displaying, via the display generation component, a representation of a first audio sample having a first set of audio characteristics and a representation of a second audio sample having a second set of audio characteristics different from the first set of audio characteristics; outputting at least a portion of the first audio sample via the audio generation component while the audio preference interface is being displayed; receiving, via the one or more input devices, a set of one or more user inputs; after receiving the set of one or more inputs, recording a selection of the first audio sample as a preferred sample or selecting the second audio sample as a preferred sample; and outputting 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 if the first audio sample is 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 if the second audio sample is recorded as the preferred sample.

[0018] 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 that communicates with a display generation component, an audio generation component, and one or more input devices is described. The one or more programs include displaying, via the display generation component, a representation of a first audio sample having a first set of audio characteristics and a representation of a second audio sample having a second set of audio characteristics different from the first set of audio characteristics, simultaneously, in an audio preference interface; outputting, via the audio generation component, at least a portion of the first audio sample while the audio preference interface is being displayed; receiving, via the one or more input devices, a set of one or more user inputs; after receiving the set of one or more inputs, recording a selection of the first audio sample as the preferred sample or selecting the second audio sample as the preferred sample; and outputting, via the audio generation component, 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 if the first audio sample is 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 if the second audio sample is recorded as the preferred sample.

[0019] According to some embodiments, a computer system that communicates with a display generation component, an audio generation component, and one or more input devices is described. The computer system that communicates with the display generation component, the audio generation component, and one or more input devices includes means for displaying an audio preference interface that includes, via the display generation component, simultaneously displaying a representation of a first audio sample having a first set of audio characteristics and a representation of a second audio sample having a second set of audio characteristics different from the first set of audio characteristics; means for outputting at least a portion of the first audio sample via the audio generation component and receiving a set of one or more user inputs via one or more input devices while the audio preference interface is being displayed; and means for, after receiving the set of one or more inputs, recording a selection of the first audio sample as the preferred sample or selecting the second audio sample as the preferred sample and outputting 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 if the first audio sample is 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 if the second audio sample is recorded as the preferred sample.

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

[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 that communicates with an audio generation component is described. The one or more programs, while causing an output of audio data at a first volume via the audio generation component, detect that an audio exposure threshold criterion has been met, and in response to the detection that the audio exposure threshold criterion has been met, reduce the volume of the output of the audio data to a second volume that is lower than the first volume while continuing to cause the output of the audio data.

[0022] 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 that communicates with an audio generation component is described. The one or more programs, while causing an output of audio data at a first volume via the audio generation component, detect that an audio exposure threshold criterion has been met, and in response to the detection that the audio exposure threshold criterion has been met, reduce the volume of the output of the audio data to a second volume that is lower than the first volume while continuing to cause the output of the audio data.

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

[0024] According to some embodiments, a computer system is described. The computer system 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 the 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 that is lower than the first volume while continuing to cause the output of the audio data in response to the detection that the audio exposure threshold criterion has been met.

[0025] According to some embodiments, a method is described that is executed in a computer system that communicates with a display generation component and one or more input devices. The method includes receiving, via one or more input devices, an input corresponding to a request to display audio exposure data, and in response to receiving the input corresponding to the request to display audio exposure data, displaying, via the display generation component, an indication of the audio exposure data over a first 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, simultaneously, in an audio exposure interface, wherein the first visual representation of the first alert includes an indication of the time at which 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 that communicates with a display generation component and one or more input devices is described. The one or more programs include instructions for receiving, via one or more input devices, an input corresponding to a request to display audio exposure data, and in response to receiving the input corresponding to the request to display audio exposure data, displaying, via the display generation component, an indication of the audio exposure data over a first 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, simultaneously, in an audio exposure interface, wherein the first visual representation of the first alert includes an indication of the time at which the first alert was provided.

[0027] 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 that communicates with a display generation component and one or more input devices is described. The one or more programs include receiving, via the one or more input devices, an input corresponding to a request to display audio exposure data; and in response to receiving the input corresponding to the request to display audio exposure data, displaying, via the display generation component, an audio exposure interface that includes simultaneously displaying an indication of audio exposure data over a first period and a first visual display of a first alert provided as a result of a first audio exposure value exceeding an audio exposure threshold, wherein the first visual display of the first alert includes an indication of the time at which the first alert was provided.

[0028] According to some embodiments, a computer system that communicates with a display generation component and one or more input devices is described. The computer system that communicates with the display generation component and one or more input devices 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 receiving, via the one or more input devices, an input corresponding to a request to display audio exposure data; and in response to receiving the input corresponding to the request to display audio exposure data, displaying, via the display generation component, an audio exposure interface that includes simultaneously displaying an indication of audio exposure data over a first period and a first visual display of a first alert provided as a result of a first audio exposure value exceeding an audio exposure threshold, wherein the first visual display of the first alert includes an indication of the time at which the first alert was provided.

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

[0030] According to some embodiments, a method executed in a computer system that communicates 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, causing the output of the first audio signal at a reduced output audio volume lower than the first predicted output audio volume when the first predicted output audio volume of the first audio signal exceeds an output audio volume threshold according to a determination that the output audio data meets a first set of criteria, causing the output of the second audio signal at the second predicted output audio volume, causing the output of the first audio signal at the first predicted output audio volume and causing the output of the second audio signal at the second predicted output audio volume according to a determination that the output audio data does not meet the first set of criteria.

[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 that communicates with an audio generation component is described. The one or more programs include 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; causing the output of the first audio signal to occur at a reduced output audio volume lower than the first predicted output audio volume when the first predicted output audio volume of the first audio signal exceeds an output audio volume threshold according to a determination that the output audio data meets a first set of criteria, the first set of criteria being met when the first predicted output audio volume exceeds the output audio volume threshold; causing the output of the second audio signal to occur at the second predicted output audio volume; causing the output of the first audio signal to occur at the first predicted output audio volume and causing the output of the second audio signal to occur at the second predicted output audio volume according to a determination that the output audio data does not meet the first set of criteria.

[0032] 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 that communicates with an audio generation component is described. The one or more programs include 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; causing the output of the first audio signal to occur at a reduced output audio volume lower than the first predicted output audio volume when the first predicted output audio volume of the first audio signal exceeds an output audio volume threshold according to a determination that the output audio data meets a first set of criteria, and causing the output of the second audio signal to occur at the second predicted output audio volume; causing the output of the first audio signal to occur at the first predicted output audio volume and causing the output of the second audio signal to occur at the second predicted output audio volume according to a determination that the output audio data does not meet the first set of criteria.

[0033] According to some embodiments, a computer system that communicates with an audio generation component is described. The computer system that communicates with the audio generation component 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 receiving output audio data associated with output audio generated using the audio generation component, wherein the output audio includes a first audio signal and a second audio signal, and the output audio data includes a first predicted output audio volume of the first audio signal and a second predicted output audio volume of the second audio signal; causing the output of the first audio signal to occur at a reduced output audio volume lower than the first predicted output audio volume when the first predicted output audio volume of the first audio signal exceeds an output audio volume threshold according to a determination that the output audio data meets a first set of criteria, and causing the output of the second audio signal to occur at the second predicted output audio volume; causing the output of the first audio signal to occur at the first predicted output audio volume and causing the output of the second audio signal to occur at the second predicted output audio volume according to a determination that the output audio data does not meet the first set of criteria.

[0034] According to some embodiments, a computer system that communicates with an audio generation component is described. The computer system that communicates with the audio generation component is 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 causing the output of the first audio signal to occur at a reduced output audio volume lower than the first predicted output audio volume and causing the output of the second audio signal to occur at the second predicted output audio volume when it is determined that the output audio data meets a first set of criteria, 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 causing the output of the first audio signal to occur at the first predicted output audio volume and causing the output of the second audio signal to occur at the second predicted output audio volume when it is determined that the output audio data does not meet the first set of criteria.

[0035] The executable instructions for performing these functions are optionally included within a non-transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors. The executable instructions for performing these functions are optionally included within a transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors.

[0036] Thus, a faster and more efficient method and interface for managing audio exposure are provided to the device, thereby increasing the effectiveness, efficiency, and user satisfaction of such a device. Such a method and interface may complement or replace other methods for managing audio exposure. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] To better understand the various embodiments described below, reference should be made to the following "Detailed Description of the Invention" in conjunction with the accompanying drawings, and like reference numerals refer to corresponding parts throughout the following figures.

[0038]

Figure 1A

[0039]

Figure 1B

[0040]

Figure 2

[0041]

Figure 3

[0042]

Figure 4A

[0043]

Figure 4B

[0044]

Figure 5A

[0045]

Figure 5B

[0046]

Figure 5C

Figure 5D

[0047]

Figure 5E

Figure 5F

Figure 5G

Figure 5H

[0048]

Figure 6A

Figure 6B

Figure 6C

Figure 6D

Figure 6E

Figure 6F

Figure 6G

Figure 6H

Figure 6I

Figure 6J

Figure 6K

Figure 6L

Figure 6M

Figure 6N

Figure 6O

Figure 6P

Figure 6Q

Figure 6R

Figure 6S

Figure 6T

Figure 6U

Figure 6V

Figure 6W

Figure 6X

Figure 6Y

Figure 6Z

Figure 6AA

Figure 6AB

Figure 6AC

Figure 6AD

Figure 6AE

Figure 6AF

Figure 6AG

Figure 6AH

Figure 6AI

Figure 6AJ

Figure 6AK

Figure 6AL

[0049]

Figure 7A

Figure 7B

[0050]

Figure 8A

Figure 8B

Figure 8C

Figure 8D

Figure 8E

Figure 8F

Figure 8G

Figure 8H

Figure 8I

Figure 8J

Figure 8K

Figure 8L

[0051]

Figure 9A

Figure 9B

Figure 9C

Figure 9D

Figure 9E

Figure 9F

Figure 9G

[0052]

Figure 10

[0053]

Figure 11A

Figure 11B

Figure 11C

Figure 11D

Figure 11E

Figure 11F

Figure 11G

Figure 11H

Figure 11I

Figure 11J

Figure 11K

Figure 11L

[0054]

Figure 12A

Figure 12B

Figure 12C

Figure 12D

Figure 12E

Figure 12F

Figure 12G

Figure 12H

Figure 12I

Figure 12J

Figure 12K

Figure 12L

Figure 12M

Figure 12N

Figure 12O

Figure 12P

Figure 12Q

Figure 12R

Figure 12S

Figure 12T

Figure 12U

Figure 12V

Figure 12W

Figure 12X

Figure 12Y

Figure 12Z

Figure 12AA

Figure 12AB

Figure 12AC

Figure 12AD

Figure 12AE

Figure 12AF

Figure 12AG

Figure 12AH

Figure 12AI

Figure 12AJ

Figure 12AK

Figure 12AL

Figure 12AM

Figure 12AN

[0055]

Figure 13

[0056]

Figure 14A

Figure 14B

Figure 14C

Figure 14D

Figure 14E

Figure 14F

Figure 14G

Figure 14H

Figure 14I

Figure 14J

Figure 14K

Figure 14L

Figure 14M

Figure 14N

Figure 14O

Figure 14P

Figure 14Q

Figure 14R

Figure 14S

Figure 14T

Figure 14U

Figure 14V

Figure 14W

Figure 14X

Figure 14Y

Figure 14Z

Figure 14AA

Figure 14AB

Figure 14AC

Figure 14AD

Figure 14AE

Figure 14AF

Figure 14AG

Figure 14AH

Figure 14AI

Figure 14AJ

Figure 14AK

[0057]

Figure 15

[0058]

Figure 16

[0059]

Figure 17A

Figure 17B

Figure 17C

Figure 17D

Figure 17E

Figure 17F

Figure 17G

Figure 17H

Figure 17I

Figure 17J

Figure 17K

Figure 17L

Figure 17M

Figure 17N

Figure 17O

Figure 17P

Figure 17Q

Figure 17R

Figure 17S

Figure 17T

Figure 17U

Figure 17V

[0060]

Figure 18

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

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

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

[0064] The terms used in the description of the various embodiments described herein are for the purpose of describing particular embodiments only and are not intended to be limiting. In the description of the various embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural as well, unless the context clearly dictates otherwise. Also, as used herein, the term "and / or" refers to any and all combinations of one or more of the associated listed items and is to be construed as including them. The terms "includes," "including," "comprises," and / or "comprising," when used herein, specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0065] The term "if" is optionally interpreted, depending on the context, to mean "when" or "upon", or "in response to determining" or "in response to detecting". Similarly, the phrases "if it is determined" or "if [a stated condition or event] is detected" are optionally interpreted, 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 related processes for using such devices are described. In some embodiments, the device is a portable communication device such as a cellular phone that also includes other functions such as PDA functionality and / or music player functionality. Exemplary embodiments of portable multifunctional devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Optionally, other portable electronic devices such as laptop or tablet computers having a touch-sensitive surface (e.g., a touch screen display and / or a touch pad) are also used. Also, in some embodiments, it should be understood that the device is not a portable communication device but a desktop computer having a touch-sensitive surface (e.g., a touch screen display and / or a touch pad). In some embodiments, the electronic device is a computer system that communicates (e.g., via wired communication or via wireless 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 causing content (e.g., video data rendered or decoded by a display controller 156) to be displayed by transmitting data (e.g., image data or video data) via a wired or wireless connection to an integrated or external display generation component for visually generating the content.

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

[0068] The device typically supports various applications such as one or more of a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a game 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] The various applications executed on the device optionally use at least one common physical user interface device such as a touch sensing surface. One or more functions of the touch sensing surface, as well as the corresponding information displayed on the device, are optionally adjusted and / or changed for each application and / or within each respective application. Thus, the common physical architecture of the device (such as the touch sensing surface) optionally supports various applications with a user interface that is intuitive and transparent to the user.

[0070] Attention is now directed to an embodiment of a portable device equipped with a touch-sensing display. FIG. 1A is a block diagram showing a portable multifunctional device 100 having a touch-sensing display system 112 according to some embodiments. The touch-sensing display 112 may be referred to as a "touch screen" for convenience and may be known or referred to as a "touch-sensing display system". The device 100 includes a memory 102 (optionally including one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. The device 100 optionally includes one or more light sensors 164. The device 100 optionally includes one or more contact intensity sensors 165 (e.g., a touch-sensing surface such as the touch-sensing display system 112 of the device 100) for detecting the intensity of contact on the device 100. The device 100 optionally includes one or more haptic output generators 167 for generating haptic output on the device 100 (e.g., generating haptic output on a touch-sensing surface such as the touch-sensing display system 112 of the device 100 or the touch pad 355 of the device 300). These components communicate, optionally, via one or more communication buses or signal lines 103.

[0071] As used in this specification and the claims, the term "intensity" of a contact on a touch-sensing surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensing surface, or a proxy for the force or pressure of the contact on the touch-sensing surface. The intensity of the contact has a range of values that includes at least four distinct values, and more typically, hundreds (e.g., at least 256) of distinct values. The intensity of the contact is optionally determined (or measured) using a variety of techniques and a variety of sensors or combinations of sensors. For example, one or more force sensors under or adjacent to the touch-sensing surface are optionally used to measure the force at various points on the touch-sensing surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted averaged) to determine the 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-sensing surface. Alternatively, the size and / or change in size of the contact area detected on the touch-sensing surface, the capacitance and / or change in capacitance of the touch-sensing surface proximate to the contact, and / or the resistance and / or change in resistance of the touch-sensing surface proximate to the contact are optionally used as an alternative to the force or pressure of the contact on the touch-sensing surface. In some implementations, an alternative measurement of the force or pressure of the contact is used directly to determine whether it exceeds an intensity threshold (e.g., the intensity threshold is described in units corresponding to the alternative measurement). In some implementations, the proxy measurement of the contact force or pressure is converted to an estimated value of the force or pressure, and the estimated value of the force or pressure is used to determine whether it exceeds an intensity threshold (e.g., the intensity threshold is a pressure threshold measured in units of pressure). By using the intensity of the contact as an attribute of a user input, a user can access additional device functions that may otherwise be inaccessible to the user on a reduced-size device with a limited implementation area for displaying affordances (e.g., on a touch-sensing display), and / or receive user input (e.g., via a touch-sensing display, a touch-sensing surface, or a physical / mechanical control such as a knob or button).

[0072] As used in this specification and the claims, the term "haptic output" refers to a physical displacement of the device relative to its previous position, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., the housing), or a displacement of a component relative to the center of mass of the device, which is to be detected by the user's sense of touch. For example, in a situation where the device or a component of the device is in contact with a touch-sensitive surface of the user (e.g., the finger, palm, or other part of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical characteristics of the device or the component of the device. For example, the movement of a touch-sensitive surface (e.g., a touch-sensitive display or a trackpad) may optionally be interpreted by the user as a "down click" or "up click" of a physical actuator button. In some cases, the user may feel a tactile sensation such as a "down click" or "up click" even when there is no movement of the physical actuator button associated with the touch-sensitive surface physically pushed (e.g., displaced) by the user's action. As another example, the movement of a touch-sensitive surface may optionally be interpreted or perceived by the user as the "roughness" of the touch-sensitive surface even if there is no change in the smoothness of the touch-sensitive surface. Such interpretation of touch by the user depends on the user's individual sensory perception, but there are many sensory perceptions of touch that are common to a majority of users. Therefore, when a haptic output is described as corresponding to a particular sensory perception of the user (e.g., "up click", "down click", "roughness"), unless otherwise specified, the generated haptic output corresponds to a physical displacement of a device or a component of the device that generates the described sensory perception of a typical (or average) user.

[0073] Device 100 is merely an example of a portable multifunctional device, and it should be understood that Device 100 may optionally have more or fewer components than those shown, may optionally combine two or more components, or may optionally have different configurations or arrangements of those components. The various components shown in FIG. 1A are implemented in a combination of hardware, software, or 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 also 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 can be used to couple the input and output peripheral devices 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 for device 100 and process data. 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] The RF (radio frequency) circuit 108 transmits and receives RF signals, also called electromagnetic signals. The RF circuit 108 converts electrical signals into electromagnetic signals or vice versa and communicates with a communication network and other communication devices via electromagnetic signals. The RF circuit 108 optionally includes well-known circuits for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and the like. The RF circuit 108 optionally communicates wirelessly with a network such as the Internet, also called the World Wide Web (WWW), an intranet, and / or a wireless network such as a cellular telephone network, a wireless local area network (LAN), and / or a metropolitan area network (MAN), as well as with other devices. The RF circuit 108 optionally includes well-known circuits for detecting a near field communication (NFC) field by means of a short-range communication radio or the like. Wireless communication optionally includes, but is not limited to, Global System for Mobile Communications (GSM) for mobile communication, Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), Long Termevolution, LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE802.11a, IEEE802.11b, IEEE802.11g, IEEE802.11n, and / or IEEE802.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 (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol including communication protocols not yet developed as of the filing date of this specification.

[0077] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between the user and the device 100. The audio circuit 110 receives audio data from the peripheral device interface 118, converts this audio data into an electrical signal, and transmits this electrical signal to the speaker 111. The speaker 111 converts the electrical signal into human audible sound waves. Also, the audio circuit 110 receives the electrical signal converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signal into audio data and transmits this audio data to the peripheral device interface 118 for processing. The audio data is optionally obtained from and / or transmitted to the memory 102 and / or the RF circuit 108 by the peripheral device interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., 212 of FIG. 2). The headset jack provides an interface between the audio circuit 110 and a detachable audio input / output peripheral device such as an output-only headset or a headset with both output (e.g., mono or stereo headphones) and input (e.g., microphone).

[0078] The I / O subsystem 106 couples input / output peripheral devices on the device 100, such as the touch screen 112 and other input control devices 116, to the peripheral device interface 118. The I / O subsystem 106 optionally includes a display controller 156, a light sensor controller 158, a depth camera controller 169, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input devices or control devices. The one or more input controllers 160 receive electrical signals from other input control devices 116 and / or transmit electrical signals to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons), dials, slider switches, joysticks, click wheels, and the like. In some embodiments, the input controller(s) 160 are optionally coupled to (or not coupled to any of) a pointer device such as a keyboard, an infrared port, a USB port, and a mouse. One or more buttons (e.g., 208 in FIG. 2) optionally include up / down buttons for volume control of the speaker 111 and / or the microphone 113. One or more buttons optionally include push buttons (e.g., 206 in FIG. 2). In some embodiments, the electronic device is a computer system that communicates with one or more input devices (e.g., via wired communication or via wireless communication). In some embodiments, the one or more input devices include a touch sensing surface (e.g., a trackpad as part of a touch sensing 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) for tracking a user's gesture (e.g., a hand gesture) as an 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", and U.S. Patent No. 7,657,849, which are hereby incorporated by reference in their entirety, a quick press of a push button optionally unlocks the touch screen 112 or, optionally, initiates a process of unlocking the device using gestures on the touch screen. A longer press of a push button (e.g., 206) optionally turns the power to the device 100 on or off. The functionality of one or more of the buttons can optionally be customized by the user. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

[0080] The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from and / or transmits electrical signals to the touch screen 112. The touch screen 112 displays visual output to the user. This visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.

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

[0082] The touch screen 112 optionally uses LCD (Liquid Crystal Display) technology, LPD (Light Emitting Polymer Display) technology, or LED (Light Emitting Diode) technology, although in other embodiments other display technologies are also used. The touch screen 112 and the display controller 156 optionally use any of a plurality of touch sensing technologies, now known or hereafter developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen 112, to detect contact and any movement or interruption thereof. In an exemplary embodiment, projection type mutual capacitance sensing technology such as that found in the iPhone (registered trademark) and iPod Touch (registered trademark) from Apple Inc. of Cupertino, California is used.

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

[0084] Touch sensing displays in some embodiments of the touch screen 112 are described in the following applications: (1) U.S. Patent Application No. 11 / 381,313, filed May 2, 2006, "Multipoint Touch Surface Controller"; (2) U.S. Patent Application No. 10 / 840,862, filed May 6, 2004, "Multipoint Touchscreen"; (3) U.S. Patent Application No. 10 / 903,964, filed Jul. 30, 2004, "Gestures For Touch Sensitive Input Devices"; (4) U.S. Patent Application No. 11 / 048,264, filed Jan. 31, 2005, "Gestures For Touch Sensitive Input Devices"; (5) U.S. Patent Application No. 11 / 038,590, filed Jan. 18, 2005, "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices"; (6) U.S. Patent Application No. 11 / 228,758, filed Sep. 16, 2005, "Virtual Input Device Placement On A Touch Screen User Interface"; (7) U.S. Patent Application No. 11 / 228,700, filed Sep. 16, 2005, "Operation Of A Computer With A Touch Screen Interface"; (8) U.S. Patent Application No. 11 / 228,737, filed Sep. 16, 2005, "Activating Virtual Keys Of A Touch-Screen Virtual Keyboard"; and (9) U.S. Patent Application No. 11 / 367,749, filed Mar. 3, 2006, "Multi-Functional Hand-Held Device". All of these applications are hereby incorporated by reference in their entirety.

[0085] The touch screen 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally touches the touch screen 112 using any suitable object or appendage such as a stylus, finger, etc. In some embodiments, the user interface is designed to operate primarily using finger-based contact and gestures, although this may not be as accurate as stylus-based input due to the larger contact area of the finger on the touch screen. In some embodiments, the device converts rough input by the finger into an accurate pointer / cursor position or command for performing the action desired by the user.

[0086] In some embodiments, in addition to the touch screen, the device 100 optionally includes a touch pad for activating or deactivating certain functions. In some embodiments, the touch pad, unlike the touch screen, is a touch-sensitive area of the device that does not display a visual output. The touch pad is optionally a separate touch-sensitive surface from the touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

[0087] The device 100 also includes a power system 162 that powers various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharge system, a power outage detection circuit, a power converter or inverter, a power status indicator (e.g., light-emitting diode (LED)), and any other components associated with the generation, management, and distribution of power within a portable device.

[0088] In addition, device 100 optionally includes one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to an optical sensor controller 158 within I / O subsystem 106. Optical sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Optical sensor 164 receives light from the environment projected through one or more lenses and converts that light into data representing an image. Optical sensor 164 cooperates with imaging module 143 (also referred to as a camera module) to optionally capture a still image or video. In some embodiments, the optical sensor is located on the back surface of device 100 opposite touch screen display 112 on the front of the device, and thus the touch screen display can be used as a viewfinder for acquiring still images and / or video. In some embodiments, the optical sensor is disposed on the front of the device such that an image of the user is optionally obtained for a video conference while the user is viewing other video conference participants on the touch screen display. In some embodiments, the position of optical sensor 164 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), and thus a single optical sensor 164 can be used with the touch screen display for both video conferencing and for acquiring still images and / or video.

[0089] Device 100 optionally also includes one or more depth camera sensors 175. FIG. 1A shows a depth camera sensor coupled to a depth camera controller 169 within I / O subsystem 106. The depth camera sensor 175 receives data from the environment and creates a three-dimensional model of an object (e.g., a face) within 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), the depth camera sensor 175 is optionally used to determine depth maps of different portions of an image captured by imaging module 143. In some embodiments, while a user views other video conference participants on a touch screen display, an image of the user with depth information is optionally acquired for video conferencing, and a depth map data self-portrait image is captured, by having a depth camera sensor disposed on the front face of device 100. In some embodiments, the depth camera sensor 175 is disposed 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), such that the depth camera sensor 175 is used with the touch screen display for both video conferencing and for acquisition of still images and / or videos.

[0090] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to an intensity sensor controller 159 within I / O subsystem 106. The contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electro-force sensors, piezoelectric force sensors, optical force sensors, capacitive touch sensing surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of contact on a touch sensing surface). The 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, a touch sensing surface (e.g., touch sensing display system 112). In some embodiments, at least one contact intensity sensor is disposed on the back of device 100, opposite a touch screen display 112 disposed on the front of device 100.

[0091] Device 100 also optionally includes one or more proximity sensors 166. FIG. 1A shows a proximity sensor 166 coupled to the peripheral device interface 118. Alternatively, the proximity sensor 166 is optionally coupled to an input controller 160 within the I / O subsystem 106. The proximity sensor 166 functions as described, optionally, in U.S. Patent Application 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 hereby incorporated by reference in their entirety. In some embodiments, when a multifunctional device is placed near the user's ear (e.g., when the user is on a call), the proximity sensor turns off and disables the touch screen 112.

[0092] Device 100 also optionally includes one or more haptic output generators 167. FIG. 1A shows a haptic output generator coupled to a haptic feedback controller 161 within I / O subsystem 106. The haptic output generator 167 optionally includes one or more electroacoustic devices, such as speakers or other audio components, and / or electromechanical devices that convert energy into linear movement, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components that convert an electrical signal into a haptic output) on the device. The contact intensity sensor 165 receives haptic feedback generation instructions from the haptic feedback module 133 and generates a haptic output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one haptic output generator is juxtaposed with or proximate to a touch sensing surface (e.g., touch sensing display system 112) and optionally generates a haptic output by moving the touch sensing surface in a vertical direction (e.g., in / out of the surface of device 100) or a horizontal direction (e.g., back and forth within the same plane as the surface of device 100). In some embodiments, at least one haptic output generator sensor is disposed on the back of device 100, which is opposite the touch screen display 112 disposed on the front of device 100.

[0093] In addition, device 100 optionally includes one or more accelerometers 168. FIG. 1A shows an accelerometer 168 coupled to the peripheral device interface 118. Alternatively, the accelerometer 168 is optionally coupled to an input controller 160 within the I / O subsystem 106. The accelerometer 168 functions optionally as described in both 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", which are hereby incorporated by reference in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait or landscape display based on analysis of data received from one or more accelerometers. In addition to the accelerometer(s) 168, device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information regarding the position and orientation (e.g., portrait or landscape orientation) of device 100.

[0094] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a touch / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and an application (or instruction set) 136. Further, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) stores a device / global internal state 157 as shown in FIGS. 1A and 3. The device / global internal state 157 includes an active application state indicating which application is active if there is a currently active application, a display state indicating which application, view, or other information occupies various regions of the touch screen display 112, a sensor state including information obtained from various sensors and input control devices 116 of the device, and one or more of position information regarding the position and / or orientation of the device.

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

[0096] The communication 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 the RF circuit 108 and / or the external port 124. The external ports 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) are adapted to couple to other devices either directly or indirectly via a network (e.g., the Internet, a wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as or similar to and / or compatible with the 30-pin connector used on iPod (registered trademark) devices (a trademark of Apple Inc.).

[0097] The contact / motion module 130 optionally detects contact with the touch screen 112 and other touch sensing devices (e.g., touch pads or physical click wheels) (in cooperation with the display controller 156). The contact / motion module 130 includes various software components for performing various operations related to the detection of contact, such as determining whether contact has occurred (e.g., detecting a finger down event), determining the intensity of the contact (e.g., the force or pressure of the contact, or an alternative to the force or pressure of the contact), determining whether there is movement of the contact, tracking movement across the touch sensing surface (e.g., detecting one or more events of dragging a finger), and determining whether the contact has stopped (e.g., detecting a finger up event or an interruption of the contact). The contact / motion module 130 receives contact data from the touch sensing surface. Determining the movement of the contact point, represented by a 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 operations are optionally applied to a single contact (e.g., contact with one finger) or multiple simultaneous contacts (e.g., "multi-touch" / contact with multiple fingers). In some embodiments, the contact / motion module 130 and the display controller 156 detect contact on the touch pad.

[0098] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by the user (e.g., to determine whether the user has "clicked" on an icon). In some embodiments, at least one subset of the intensity thresholds is determined according to software parameters (e.g., the intensity thresholds can be adjusted without changing the physical hardware of the device 100, rather than being determined by the activation threshold of a particular physical actuator). For example, the mouse "click" threshold of a trackpad or touch screen display can be set to any of a wide range of default thresholds without changing the trackpad or touch screen display hardware. Additionally, in some implementations, the user of the device is provided with software settings 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 according to a system-level click "intensity" parameter).

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

[0100] The graphic module 132 includes various known software components that render and display graphics on the touch screen 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, but is not limited to, any object that can be displayed to a user, including letters, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, and the like.

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

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

[0103] The text input module 134 is optionally a component of the graphic 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 that requires 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 phone 138 for location-based dialing, to camera 143 as picture / video metadata, and to applications providing location-based services such as a weather widget, a local yellow pages widget, and a map / navigation widget).

[0105] Application 136 optionally includes the following modules (or sets of instructions) or subsets or supersets thereof. ● Contact module 137 (sometimes referred to as an address book or contact list), ● Phone module 138, ● Video conferencing module 139, ● Email client module 140, ● Instant messaging (IM) module 141, ● Training support module 142, ● Camera module 143 for still images and / or videos, ● Image management module 144, ● Video player module, ● Music player module, ● Browser module 147, ● Calendar module 148, ● Optionally, a widget module 149 including one or more of weather widget 149-1, stock widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widget 149-6, ● Widget creator module 150 for creating user-created widget 149-6, ● Search module 151, ● A video and music player module 152 that integrates a video player module and a music player module, ● A memo module 153, ● A map module 154, and / or ● An online video module 155.

[0106] Examples of other applications 136 that are optionally stored in the memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, Java-compatible applications, encryption, digital rights management, voice recognition, and voice replication.

[0107] The contact module 137 is used in cooperation with the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, and the text input module 134 to optionally manage an address book or a contact list (for example, store it in the application internal state 192 of the contact module 137 in the memory 102 or the memory 370). Management by the contact module 137 includes adding a name to the address book, deleting a name from the address book, associating a phone number, an email address, a physical address, or other information with a name, associating an image with a name, classifying and sorting names, providing a phone number or an email address to initiate and / or facilitate communication by the phone 138, the video conferencing module 139, the email 140, or the IM 141, and so on.

[0108] The telephone module 138 cooperates with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, and the text input module 134, and is optionally used for the input of a character sequence corresponding to a telephone number, access to one or more telephone numbers in the contact module 137, modification of the input telephone number, dialing of each telephone number, execution of a call, and disconnection and call hold at the end of a call. As described above, wireless communication optionally uses any of a plurality of communication standards, protocols, and technologies.

[0109] The video conferencing module 139 cooperates with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the light sensor 164, the light sensor controller 158, the contact / motion module 130, the graphic module 132, the text input module 134, the contact module 137, and the telephone module 138, and includes executable instructions for starting, executing, and ending a video conference between the user and one or more other participants according to the user's instructions.

[0110] The email client module 140 cooperates with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, and the text input module 134, and includes executable instructions for creating, sending, receiving, and managing emails according to the user's instructions. In cooperation with the image management module 144, the email client module 140 makes it very easy to create and send emails with still or moving images captured by the camera module 143.

[0111] The instant messaging module 141 cooperates with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, and text input module 134 to include executable instructions for inputting a character sequence corresponding to an instant message, correcting previously input characters, (e.g., using the Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for instant messages based on telephone communication, or XMPP, SIMPLE, or IMPS for instant messages based on the Internet) transmitting each instant message, receiving instant messages, and viewing received instant messages. In some embodiments, the instant messages transmitted and / or received optionally include graphics, photos, audio files, video files, and / or other attached files as supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephone communication-based messages (e.g., messages transmitted using SMS or MMS) and Internet-based messages (e.g., messages transmitted using XMPP, SIMPLE, or IMPS).

[0112] The training support module 142, in cooperation with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, GPS module 135, map module 154, and music player module, creates training (e.g., having time, distance, and / or calorie burn goals), communicates with a training sensor (sports device), receives training sensor data, calibrates sensors used to monitor the training, selects and plays music for the training, and includes executable instructions for displaying, storing, and transmitting training data.

[0113] The camera module 143, in cooperation with the touch screen 112, display controller 156, light sensor 164, light sensor controller 158, contact / motion module 130, graphic module 132, and image management module 144, includes executable instructions for capturing still images or videos (including video streams) and storing them in the memory 102, modifying the characteristics of still images or videos, or deleting still images or videos from the memory 102.

[0114] The image management module 144, in cooperation with the touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, and camera module 143, includes executable instructions for arranging, modifying (e.g., editing), or otherwise operating on still images and / or videos, labeling, deleting, presenting (e.g., in a digital slide show or album), and storing them.

[0115] The browser module 147 includes executable instructions for browsing the Internet according to user instructions, including searching for, linking to, receiving, and displaying a web page or a portion thereof, as well as attached files and other files linked to the web page, in cooperation with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, and the text input module 134.

[0116] The calendar module 148 includes executable instructions for creating, displaying, modifying, and storing a calendar and data associated with the calendar (e.g., calendar items, to-do lists, etc.) according to user instructions, in cooperation with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, the text input module 134, the email client module 140, and the browser module 147.

[0117] The widget module 149, in cooperation with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, the text input module 134, and the browser module 147, is optionally a mini-application (e.g., weather widget 149-1, stock widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) that is downloaded and used by a user, or a mini-application (e.g., user-created widget 149-6) created by the user. In some embodiments, the widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, the widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! widget).

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

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

[0120] The video and music player module 152, in cooperation with the touch screen 112, display controller 156, contact / motion module 130, graphic module 132, audio circuit 110, speaker 111, RF circuit 108, and browser module 147, includes executable instructions that enable a user to download and play recorded music and other sound files stored in one or more file formats such as MP3 or AAC files, and executable instructions for displaying, presenting, or otherwise playing videos (e.g., on the touch screen 112 or on an external display connected via the external port 124). In some embodiments, the device 100 optionally includes the functionality of an MP3 player such as an iPod (a trademark of Apple Inc.).

[0121] The memo module 153, in cooperation with the touch screen 112, display controller 156, contact / motion module 130, graphic module 132, and text input module 134, includes executable instructions for creating and managing memos, to-do lists, etc. according to user instructions.

[0122] The map module 154, in cooperation with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, GPS module 135, and browser module 147, is optionally used to receive, display, modify, and store maps and data associated with the maps (e.g., driving routes, data about stores and other attractions near a particular location or in its vicinity, and other location-based data) according to user instructions.

[0123] The online video module 155 cooperates with the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132, the audio circuit 110, the speaker 111, the RF circuit 108, the text input module 134, the email client module 140, and the browser module 147 to enable a user to access a particular online video, browse a particular online video, receive it (e.g., by streaming and / or downloading), play it (e.g., on the touch screen or on an external display connected via the external port 124), send an email having a link to a particular online video, and perform other management of online videos in one or more file formats such as H.264. In some embodiments, instead of the email client module 140, the instant messaging module 141 is used to send a link to a particular online video. For additional explanation of the online video application, see U.S. Provisional Patent Application No. 60 / 936,562, filed Jun. 20, 2007, "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," and U.S. Patent Application No. 11 / 968,067, filed Dec. 31, 2007, "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," the entire contents of which are incorporated herein by reference.

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

[0125] In some embodiments, the device 100 is a device in which the operation of a set of default functions in the device is performed only via a touch screen and / or a touch pad. By using the touch screen and / or the touch pad as the main input control device for the device 100 to operate, optionally, the number of physical input control devices (push buttons, dials, etc.) on the device 100 is reduced.

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

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

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

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

[0130] Event monitor 171 receives event information from peripheral device interface 118. The event information includes information regarding sub-events (e.g., a user touch as part of a multi-touch gesture on touch-sensitive display 112). Peripheral device interface 118 transmits information received from sensors such as I / O subsystem 106, or proximity sensor 166, accelerometer(s) 168, and / or microphone 113 (via audio circuit 110). Information that peripheral device 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 transmits requests to peripheral device interface 118 at predetermined intervals. In response, peripheral device interface 118 transmits event information. In other embodiments, peripheral device interface 118 transmits event information only when there is an important event (e.g., receipt of an input that exceeds a predetermined noise threshold and / or a predetermined duration).

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

[0133] The hit view determination module 172 provides a software procedure for determining where in one or more views a sub - event occurs when the touch - sensitive display 112 is displaying two or more views. A view is composed of control devices and other elements that a user can view on the display.

[0134] Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch - based gestures occur. The application views (for each application) in which touches are detected optionally correspond to program levels within the program hierarchy or view hierarchy of the application. For example, the lowest - level view in which a touch is detected is optionally called the hit view, and the set of events recognized as appropriate input is optionally determined at least in part based on the hit view of the initial touch that initiates a touch - based gesture.

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

[0136] The active event recognition unit determination module 173 determines which view(s) within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, the active event recognition unit determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, the active event recognition unit determination module 173 determines that all views including the physical location of the sub-event are views that are actively involved, and thus determines that all views that are actively involved should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely limited to an area associated with one particular view, the upper-level views within the hierarchy will still continue to be views that are actively involved.

[0137] The event dispatcher module 174 dispatches event information to the event recognition unit (e.g., event recognition unit 180). In embodiments including the active event recognition unit determination module 173, the event dispatcher module 174 dispatches event information to the event recognition unit determined by the active event recognition unit determination module 173. In some embodiments, the event dispatcher module 174 stores the event information obtained by each event receiver 182 in the event queue.

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

[0139] In some embodiments, application 136-1 includes a plurality of event processing units 190 and one or more application views 191, each including instructions for processing touch events that occur within respective views of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognition units 180. Typically, each application view 191 includes a plurality of event recognition units 180. In other embodiments, one or more of the event recognition units 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 processing unit 190 includes one or more of event data 179 received from data update unit 176, object update unit 177, GUI update unit 178, and / or event sorter 170. The event processing unit 190 optionally utilizes or invokes the data update unit 176, object update unit 177, or GUI update unit 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event processing units 190. Also, in some embodiments, one or more of the data update unit 176, object update unit 177, and GUI update unit 178 are included in respective application views 191.

[0140] Each event recognition unit 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. The event recognition unit 180 includes an event receiving unit 182 and an event comparing unit 184. In some embodiments, the event recognition unit 180 also includes at least a subset of metadata 183 and event distribution instructions 188 (optionally including sub-event distribution instructions).

[0141] The event receiving unit 182 receives event information from the event sorter 170. The event information includes sub-events, for example, information about 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 is related to the 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 referred to as the posture of the device).

[0142] The event comparison unit 184 compares the event information with the definition of a defined event or sub-event, and based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, the event comparison unit 184 includes an event definition 186. The event definition 186 includes definitions of events (e.g., a sequence of predefined sub-events) such as event 1 (187-1) and event 2 (187-2). In some embodiments, the sub-events within an event (187) include, for example, a touch start, a touch end, a touch movement, a touch cancellation, and multiple touches. In one example, the definition of event 1 (187-1) is a double-tap on a displayed object. The double-tap includes, for example, a first touch (touch start) on the displayed object for a predetermined stage, a first lift-off (touch end) for the predetermined stage, a second touch (touch start) on the displayed object for the predetermined stage, and a second lift-off (touch end) for the predetermined stage. In another example, the definition of event 2 (187-2) is a drag on a displayed object. The drag includes, for example, a touch (or contact) on the displayed object for 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 processing units 190.

[0143] In some embodiments, the event definition 187 includes the definition of events for each user interface object. In some embodiments, the event comparison unit 184 performs a hit test to determine which user interface object is associated with the sub - event. For example, within an application view where three user interface objects are displayed on the touch - sensitive display 112, when a touch is detected on the touch - sensitive display 112, the event comparison unit 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 processing unit 190, the event comparison unit determines which event processing unit 190 should be activated using the result of the hit test. For example, the event comparison unit 184 selects the event processing unit associated with the sub - event and object that triggered the hit test.

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

[0145] If each event recognition unit 180 determines that a series of sub - events does not match any of the events in the event definition 186, each event recognition unit 180 enters a state of event impossible, event failure, or event end, and then ignores the next sub - event of the touch - based gesture. In this situation, if there are other event recognition units that remain active for the hit view, that event recognition unit continues to track and process the sub - events of the ongoing touch - based gesture.

[0146] In some embodiments, each event recognition unit 180 includes metadata 183 having configurable properties, flags, and / or lists indicating how the event delivery system should actively participate in executing sub-event delivery for the event recognition unit. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists indicating how event recognition units interact with each other or how they can interact with each other. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists indicating whether sub-events are delivered to various levels in the view hierarchy or program hierarchy.

[0147] In some embodiments, each event recognition unit 180 activates the event processing unit 190 associated with the event when one or more specific sub-events of the event are recognized. In some embodiments, each event recognition unit 180 delivers event information associated with the event to the event processing unit 190. Activating the event processing unit 190 is separate from sending (and deferring sending) sub-events to each hit view. In some embodiments, the event recognition unit 180 sets a flag associated with the recognized event, and the event processing unit 190 associated with that flag catches the flag and executes a predefined process.

[0148] In some embodiments, the event delivery command 188 includes a sub-event delivery command that delivers event information about sub-events without activating the event processing unit. Instead, the sub-event delivery command delivers event information to an event processing unit associated with a series of sub-events or to a view actively involved. The event processing unit associated with the series of sub-events or the view actively involved receives the event information and executes a predetermined process.

[0149] In some embodiments, data update unit 176 creates and updates data used by application 136-1. For example, data update unit 176 updates the phone numbers used by contact module 137 or stores video files used by the video player module. In some embodiments, object update unit 177 creates and updates objects used by application 136-1. For example, object update unit 177 creates a new user interface object or updates the position of a user interface object. GUI update unit 178 updates the GUI. For example, GUI update unit 178 prepares display information and sends the display information to graphic module 132 for display on the touch-sensitive display.

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

[0151] The foregoing description regarding event processing of a user's touch on the touch-sensitive display also applies to other forms of user input for operating multifunctional device 100 using an input device, but it should be understood that not all of them are initiated on the touch screen. For example, movement of a mouse and pressing of a mouse button, movement of a contact such as a tap, drag, scroll on a touch pad, pen stylus input, movement of the device, verbal commands, detected eye movements, biometric input, and / or any combination thereof, optionally in association with single or multiple presses or holds of a keyboard, are utilized as input corresponding to sub-events that define events to be optionally recognized.

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

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

[0154] In some embodiments, device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device on / off and locking the device, volume adjustment buttons 208, a subscriber identity module (SIM) card slot 210, a headset jack 212, and a docking / charging external port 124. The push button 206 is optionally used to turn the device on / off by pressing the button and holding it down for a predefined period, lock the device by pressing the button and releasing it before a predefined time has elapsed, and / or unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input via a microphone 113 to activate or deactivate some functions. Device 100 optionally also includes one or more contact intensity sensors 165 for detecting the intensity of contact on the touch screen 112 and / or one or more haptic output generators 167 for generating haptic output to the user of device 100.

[0155] Figure 3 is a block diagram of an exemplary multifunctional device having a display and a touch sensing 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 industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more networks 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 communications between system components. Device 300 includes an input / output (I / O) interface 330 that includes a display 340, which is typically a touch screen display. I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350, a touch pad 355, a touch output generator 357 that generates haptic output on device 300 (e.g., similar to haptic output generator 167 described above with reference to FIG. 1A), and sensors 359 (e.g., light, acceleration, proximity, touch sensing, and / or haptic intensity sensors similar to haptic 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 the CPU(s) 310.In some embodiments, the memory 370 stores programs, modules, and data structures similar to, or a subset of, the programs, modules, and data structures stored in the memory 102 of the portable multifunctional device 100 (FIG. 1A). Further, the memory 370 optionally stores additional programs, modules, and data structures that do not exist in the memory 102 of the portable multifunctional device 100. For example, the memory 370 of the device 300 optionally stores a drawing module 380, a presentation module 382, a word processing module 384, a website creation module 386, a disk authoring module 388, and / or a spreadsheet module 390, whereas the memory 102 of the portable multifunctional device 100 (FIG. 1A) optionally does not store these modules.

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

[0157] Next, optionally direct attention to an embodiment of a user interface, for example, implemented on the portable multifunctional device 100.

[0158] Figure 4A shows an exemplary user interface of a menu of an application on a portable multifunctional device 100 according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, the user interface 400 includes the following elements, or a subset or superset thereof. ● One or more signal strength indicators (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 having icons of frequently used applications such as the following ○ An icon 416 of the phone module 138 labeled "Phone", optionally including an indicator 414 of the number of missed calls or voice mail messages, ○ An icon 418 of the email client module 140 labeled "Mail", optionally including an indicator 410 of the number of unread emails, ○ An icon 420 of the browser module 147 labeled "Browser", and ○ An icon 422 for the video and music player module 152, also referred to as the iPod (trademark of Apple Inc.) module 152, labeled "iPod", and ● Icons of other applications such as the following, ○ An icon 424 of the IM module 141 labeled "Message", ○ An icon 426 of the calendar module 148 labeled "Calendar", ○ An icon 428 of the image management module 144 labeled "Photos", ○ An icon 430 of the camera module 143 labeled "Camera", ○ An icon 432 of the online video module 155 labeled "Online Video", ○ The icon 434 of the stock widget 149-2, labeled with "Stock price", ○ The icon 436 of the map module 154, labeled with "Map", ○ The icon 438 of the weather widget 149-1, labeled with "Weather", ○ The icon 440 of the alarm clock widget 149-4, labeled with "Clock", ○ The icon 442 of the training support module 142, labeled with "Training support", ○ The icon 444 of the memo module 153, labeled with "Memo", and ○ The icon 446 of the settings application or module, labeled with "Settings", which provides access to the settings of the device 100 and its various applications 136.

[0159] Note that the icon labels shown in FIG. 4A are merely illustrative. For example, other labels, such as "Music" or "Music player", which are labeled for the icon 422 of the video and music player module 152, are optionally used for various application icons. In some embodiments, the label for each application icon includes the name of the application corresponding to that 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] FIG. 4B shows an exemplary user interface on a device (e.g., device 300 of FIG. 3) having a touch sensing surface 451 (e.g., tablet or touch pad 355 of FIG. 3) separate from a display 450 (e.g., touch screen display 112). The device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) that detect the intensity of contact on the touch sensing surface 451, and / or one or more haptic output generators 357 that generate haptic output to the user of the device 300.

[0161] Some of the following examples are given with reference to inputs on a touch screen display 112 (where the touch sensing surface and the display are combined), but in some embodiments, the device detects inputs on a touch sensing surface separate from the display, as shown in FIG. 4B. In some embodiments, the touch sensing surface (e.g., 451 of FIG. 4B) has a primary axis (e.g., 452 of FIG. 4B) corresponding to a primary axis (e.g., 453 of FIG. 4B) on the display (e.g., 450). According to these embodiments, the device detects contact (e.g., 460 and 462 of FIG. 4B) with the touch sensing surface 451 at positions (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470) corresponding to each position on the display. In this way, user inputs (e.g., contacts 460 and 462 and their movements) detected by the device on the touch sensing surface (e.g., 451 of FIG. 4B) are used by the device to operate the user interface on the display (e.g., 450 of FIG. 4B) of the multifunctional device when the touch sensing surface is separate from the display. It should be understood that a similar method is optionally used for other user interfaces described herein.

[0162] In addition, while the following examples are given primarily with reference to finger inputs (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 may be replaced with inputs from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture may optionally be a mouse click (e.g., instead of a contact), followed by a mouse click that involves movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture may optionally be replaced by a mouse click while the cursor is positioned over the location of the tap gesture (e.g., instead of detecting a contact and then ceasing to detect the contact). Similarly, it should be understood that when multiple user inputs are detected simultaneously, multiple computer mice may optionally be used simultaneously, or mouse and finger contacts may optionally be used simultaneously.

[0163] FIG. 5A shows an exemplary personal electronic device 500. The device 500 includes a body 502. In some embodiments, the 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, the device 500 has a touch-sensitive display screen 504, hereinafter touch screen 504. Alternatively, or in addition to the touch screen 504, the device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, the touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors that detect the intensity of an applied contact (e.g., a touch). One or more intensity sensors of the touch screen 504 (or touch-sensitive surface) can provide output data representative of the intensity of the touch. The user interface of the device 500 can respond to the touch(es) based on its intensity, which means that touches of different intensities can invoke different user interface operations on the device 500.

[0164] Exemplary techniques for detecting and processing touch intensity are described, for example, in International Patent Application No. PCT / US2013 / 040061, filed May 8, 2013, published as International Publication No. WO / 2013 / 169849, "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application", and International Patent Application No. PCT / US2013 / 069483, filed Nov. 11, 2013, published as International Publication No. WO / 2014 / 105276, "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships", each of which is hereby incorporated 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, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can enable device 500 to be attached, for example, to hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watch bands, chains, pants, belts, shoes, wallets, backpacks, and the like. These attachment mechanisms enable a user to wear device 500.

[0166] FIG. 5B shows 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. The I / O section 514 can be connected to a display 504, and the display 504 can have a touch sensing component 522 and optionally an intensity sensor 524 (e.g., a contact intensity sensor). Additionally, the 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. The device 500 can include an input mechanism 506 and / or 508. The input mechanism 506 can optionally be, for example, a rotatable input device or a depressible and rotatable input device. In some examples, the input mechanism 508 can optionally be a button.

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

[0168] When the memory 518 of the personal electronic device 500 is executed by one or more computer processors 516, it can include, for example, one or more non-transitory computer-readable storage media for storing computer-executable instructions that cause a computer processor to execute the techniques described below, including processes 700, 1000, 1300, 1500, 1600, and 1800 (FIGS. 7A-7B, FIG. 10, FIG. 13, FIG. 15, FIG. 16, and FIG. 18). A computer-readable storage media can be any media that can tangibly contain or store computer-executable instructions used by or related to an instruction execution system, apparatus, or device. In some embodiments, the storage media is a transitory computer-readable storage media. In some embodiments, the storage media is a non-transitory computer-readable storage media. Non-transitory computer-readable storage media can 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 persistent solid-state memories such as flash, solid-state drives, and the like. The personal electronic device 500 is not limited to the components and configurations of FIG. 5B and can include other or additional components in multiple configurations.

[0169] As used herein, the term "affordance" optionally refers to a user-interaction graphical user interface object displayed on a display screen of devices 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 part of the user interface with which the user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as the "focus selector," and thus when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., the touchpad 355 of FIG. 3 or the 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 that include a touch screen display (e.g., the touch-sensitive display system 112 of FIG. 1A or the touch screen 112 of FIG. 4A) that enables direct interaction with user interface elements on the touch screen display, the detected contact on the touch screen acts as the "focus selector," and thus when an input (e.g., a press input by contact) is detected at the position of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted according to the detected input. In some implementations, the focus is moved from one region of the user interface to another region of the user interface without movement of the corresponding cursor or movement of contact on the touch screen display (e.g., by using a tab key or arrow keys to move the focus from one button to another button), and in these implementations, the focus selector moves in accordance with the movement of the 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 touch screen display) that is controlled by the user to convey information about the user's intended interaction with the user interface (e.g., by indicating to the device the user interface element through which the user intends to interact).For example, while a press input is detected on a touch sensing surface (e.g., a touch pad or a touch screen), the position of a focus selector (e.g., a cursor, a contact, or a selection box) over the corresponding button indicates that the user intends to activate that corresponding button (as opposed to other user interface elements shown on the device's display).

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

[0172] FIG. 5C shows the detection of multiple contacts 552A-552E on a touch-sensing display screen 504 by a plurality of intensity sensors 524A-524D. FIG. 5C additionally includes an intensity diagram showing the current intensity measurements of intensity sensors 524A-524D in intensity units. In this example, the intensity measurements of intensity sensors 524A and 524D are each 9 intensity units, and the intensity measurements of intensity sensors 524B and 524C are each 7 intensity units. In some implementations, the aggregated intensity is the sum of the intensity measurements of the plurality of intensity sensors 524A-524D, which is 32 intensity units in this example. In some embodiments, each contact is assigned a respective intensity that is a portion of the aggregated intensity. FIG. 5D shows the assignment of the aggregated intensity to contacts 552A-552E based on the distance from the center of force 554. In this example, each of contacts 552A, 552B, and 552E is assigned a contact intensity of 8 intensity units of the aggregated intensity, and each of contacts 552C and 552D is assigned a contact intensity of 4 intensity units of the aggregated intensity. More generally, in some implementations, each contact j is assigned a respective intensity Ij that is a portion of the aggregated intensity A according to a predefined mathematical function Ij = A·(Dj / ΣDi), where Dj is the distance from the center of force to each 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 last). The operations described with reference to FIGS. 5C-5D can be performed using an electronic device similar 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, the intensity sensors are used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). Note that the intensity diagram is included in FIGS. 5C-5D to assist the reader and is not part of the display user interface.

[0173] In some embodiments, for the purpose of determining characteristic intensity, a portion of a gesture is specified. For example, the touch sensing surface optionally receives continuous swipe contacts that transition from a starting position to reach an ending position, where the intensity of the contact is increasing. In this example, the characteristic intensity of the contact at the ending position is optionally based on only a portion of the continuous swipe contact (e.g., only the portion of the swipe contact at the ending position), rather than the entire swipe contact. In some embodiments, optionally, a smoothing algorithm is 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 a non - weighted 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 width of the swipe contact intensity for the purpose of determining characteristic intensity.

[0174] The intensity of a contact on the touch sensing 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 typically corresponds to the intensity at which the device performs an operation associated with clicking a button or trackpad of a physical mouse. In some embodiments, the deep press intensity threshold typically corresponds to the intensity at which the device performs an operation different from the operation associated with clicking a button or trackpad of a physical mouse. In some embodiments, when a contact 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) is detected, the device moves a focus selector in accordance with the movement of the contact on the touch sensing surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise specified, these intensity thresholds are consistent among various sets of user interface values.

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

[0176] In some embodiments described herein, in response to detecting a gesture including each press input, or in response to detecting each press input performed by each contact (or contacts), one or more operations are performed, and each press input is detected at least in part based on detecting an increase in the strength of a contact (or contacts) exceeding a press input strength threshold. In some embodiments, each operation is performed in response to detecting an increase in the strength of each contact exceeding the press input strength threshold (e.g., the "downstroke" of each press input). In some embodiments, the press input includes an increase in the strength of each contact exceeding the press input strength threshold and a subsequent decrease in the strength of the contact below the press input strength threshold, and each operation is performed in response to detecting a subsequent decrease in the strength of each contact below the press input threshold (e.g., the "upstroke" of each press input).

[0177] Figures 5E - 5H show the detection of a gesture including a press - in input corresponding to an increase in the intensity of contact 562 from an intensity below the light press - down intensity threshold of Figure 5E (e.g., "ITL") to an intensity exceeding the deep press - down intensity threshold of Figure 5H (e.g., "ITD"). The gesture executed by contact 562 is detected on the touch - sensing surface 560, and at this time, on the display user interface 570 including application icons 572A - 572D displayed within a predetermined region 574, a cursor 576 is displayed over the application icon 572B corresponding to App 2. In some embodiments, the gesture is detected on the touch - sensing display 504. The intensity sensor detects the intensity of the contact on the touch - sensing surface 560. The device determines that the intensity of contact 562 has reached a peak exceeding the deep press - down intensity threshold (e.g., "ITD"). Contact 562 is maintained on the touch - sensing surface 560. In response to the detection of the gesture, in accordance with contact 562 having an intensity exceeding the deep press - down intensity threshold (e.g., "ITD") during the gesture, as shown in Figures 5F - 5H, reduced - scale representations 578A - 578C (e.g., thumbnails) of the most recently opened documents for App 2 are displayed. In some embodiments, this intensity compared to one or more intensity thresholds is the characteristic intensity of the contact. Note that the intensity diagram for contact 562 is included in Figures 5E - 5H to assist the reader, rather than being part of the display user interface.

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

[0179] In some embodiments, the device employs intensity hysteresis to avoid spurious inputs sometimes referred to as "jitter", and the device defines or selects a hysteresis intensity threshold having a predefined relationship to the depression input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the depression input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the depression input intensity threshold). Thus, in some embodiments, a depression input includes an increase in the intensity of each contact that exceeds the depression input intensity threshold, and a subsequent decrease in the intensity of the contact that falls below the hysteresis intensity threshold corresponding to the depression input intensity threshold, and each operation is performed in response to detecting a subsequent decrease in the intensity of each contact that falls below the hysteresis intensity threshold (e.g., the "upstroke" of each depression input). Similarly, in some embodiments, a depression input is detected only when the device detects an increase in the intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the depression input intensity threshold, and optionally, a subsequent decrease in the intensity of the contact to an intensity below the hysteresis intensity, and each operation is performed in response to detecting the depression input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, depending on the situation).

[0180] For ease of explanation, the description of an operation performed in response to a depression input associated with a depression input intensity threshold, or a gesture including a depression input, is optionally triggered in response to detecting any of an increase in the intensity of a contact that exceeds the depression input intensity threshold, an increase in the intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the depression input intensity threshold, a decrease in the intensity of a contact that falls below the depression input intensity threshold, and / or a decrease in the intensity of a contact that falls below the hysteresis intensity threshold corresponding to the depression input intensity threshold. Further, in examples where an operation is described as being performed in response to detecting a decrease in the intensity of a contact that falls below the depression input intensity threshold, the operation is optionally performed in response to detecting a decrease in the intensity of a contact that corresponds to and falls below a lower hysteresis intensity threshold corresponding to the depression 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 be launched (e.g., opened) on the device. In some embodiments, the downloaded application becomes an installed application by an installation program that extracts program portions from the downloaded package and integrates the extracted portions with the operating system of the computer 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 applications. ● An active application currently displayed on the display screen of the device being used by the application, ● A background application (or background process) for which one or more processes are being processed by one or more processors although not currently displayed, and ● An application in an interrupted or paused state that is not running but is stored in memory (volatile and non-volatile, respectively) and has state information 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 memory of the device). Thus, closing an application includes stopping and / or removing the application process for the application and removing the state information for the application from the memory of the device. Generally, even if a second application is opened within a first application, the first application is not closed. When the second application is being displayed and the display of the first application has ended, the first application becomes a background application.

[0184] Next, attention is directed to embodiments of a user interface ("UI") and related processes implemented on an electronic device such as the portable multifunctional device 100, device 300, or device 500.

[0185] Figures 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 the processes described below, including the processes in Figures 7A - 7B.

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

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

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

[0189] FIG. 6A shows a device 600 that receives a user input 628A (e.g., a tap) on a noise state affordance 620. In response to the detection of the user input 628A, the device 600 displays a user interface 608B as shown in FIG. 6B. The user interface 608B includes an explanation of the functionality of the noise application, an activation affordance 630 for activation (e.g., to initialize the noise application), and a deactivation affordance 632 for deactivation (e.g., to maintain the uninitialized state of the noise application). FIG. 6B shows the device 600 that receives a user input 628B (e.g., a tap) on the activation affordance 630. In response to the reception of the user input 628B, the device 600 displays a user interface 608C (e.g., an interface associated with the noise application) as shown in FIG. 6C.

[0190] As shown in FIG. 6C (and FIGS. 6D - 6G), the user interface 608C includes a display of time 634 (e.g., indicating the current time of 10:09), a noise level indicator 636, a noise meter indicator 638, and a noise state indicator 640. The noise level indicator 636 provides a numerical display of a first noise level value (e.g., 34 dB) (e.g., measured or determined by the device 600 from noise data derived from the microphone 606). The noise state indicator 640 provides a non - numerical display (e.g., an indicator including graphics and / or text) of the first noise level value (e.g., measured or determined by the device 600 from noise data derived from the 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 the noise level based on noise data detected by a sensor (e.g., a 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 a second noise level (e.g., measured by device 600 via 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 second, respectively). The noise meter indicator 638 includes an active portion 638A (e.g., a visually emphasized portion) whose size and / or color varies 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 varies with respect to a second threshold level. In some embodiments, the size includes the number of visually emphasized segments, the relative area occupied by the set of visually emphasized segments, or the position of the rightmost edge of the set of visually emphasized segments relative to a scale. In some embodiments, each emphasized segment within the active portion 638A represents a predetermined number of decibels (e.g., 10 DB). In some embodiments, the first threshold level and the second threshold level are the same level (e.g., 80 DB).

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

[0193] FIG. 6C shows the state of user interface 608C while device 600 is in an environment having a consistent noise level of 34 dB at 10:09 (e.g., device 600 is located in a low-noise environment such as a computer laboratory). Thus, as shown in FIG. 6C, noise level indicator 636 includes the "34 DB" value, and noise status indicator 640 includes an unobtrusive prompt (e.g., a checkmark graphic, "OK", and an explanatory prompt indicating a 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 display of a low, consistent noise level by displaying active portion 638A in a size corresponding to two green segments (e.g., green represented by diagonal hatching). In some embodiments, the two segments may be distinguished in different ways to indicate that there is no problem at the low, consistent noise level.

[0194] FIG. 6D shows the state of user interface 608C in response to a rapid increase in ambient noise (e.g., within 200 milliseconds of a spike) (e.g., a firing alarm sounds inside the computer laboratory). As shown in FIG. 6D, the size of active portion 638A of noise meter indicator 638 increases from two segments to ten segments, and the color transitions from green to yellow (e.g., yellow represented by horizontal hatching). In some embodiments, instead of the color transition from green to yellow, the segments may be distinguished in different ways to indicate that the noise level has transitioned to a level at which the user should take notice. 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 the noise level indicator 636 and the noise state indicator 640 changes according to a first noise level (e.g., a noise level based on a longer 1-second period of noise level data), and the appearance of the 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., instantaneously) than the noise level indicator 636 (and the noise state indicator 640) in response to a rapid change in the ambient noise level. This delay effect is indicated by the difference in the noise levels represented by the noise level indicator 636, the noise state indicator 640, and the noise meter 638. In some embodiments, the slower update facilitates the user's interpretation (e.g., reading) of the displayed noise level, while the faster update behavior of the graphical meter 638 provides more timely (e.g., responsive) visual feedback to the user.

[0196] FIG. 6E shows the state of the user interface 608C after a high noise level has persisted (e.g., the launch alarm continues to sound for one minute). As shown in FIG. 6E, the size and color of the active portion 638A of the noise meter indicator 638 remain unchanged (e.g., compared to the depiction in FIG. 6D). However, the noise level indicator 636 and the noise state indicator 640 are updated to reflect the continuously rising ambient noise level (e.g., the noise level indicator 636 indicates an 113 dB level, and the noise state indicator 640 includes a cautionary (e.g., "large") prompt indicating a noise level exceeding an 80 dB threshold).

[0197] Figure 6F shows the state of user interface 608C in response to a sudden drop in ambient noise level (e.g., the emission alarm suddenly stops). As shown in Figure 6F, the size of the active portion 638A of noise meter indicator 638 decreases from 10 segments to 6 segments, and the color changes from yellow to green (e.g., green represented by diagonal hatching). In some embodiments, instead of a color transition from yellow to green, the segments may be distinguished in different ways to indicate that the noise level has transitioned from a level that requires the user's attention to a normal level with low risk to the user's hearing. As shown, noise level indicator 636 and noise status indicator 640 maintain their previous appearance (e.g., as shown in Figure 6E).

[0198] Figure 6G shows the state of user interface 608C after the reduced noise level has persisted (e.g., over a period longer than 1 second). As shown in Figure 6G, the size and color of the active portion 638A of noise meter indicator 638 remain unchanged (e.g., compared to the depiction in Figure 6F). However, noise level indicator 636 and noise status indicator 640 are updated to reflect the reduced ambient noise level (e.g., noise level indicator 636 shows a level of 78 dB, and noise status indicator 640 includes an inattentive prompt (e.g., "OK") indicating a noise level below an 80 dB threshold.

[0199] In response to a determination 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), the device 600 emits a tactile alert 642 as shown in FIG. 6H. In some embodiments, the noise data used to determine the noise level value is sampled at a first rate, while the device 600 displays a graphical noise meter indicator 620 (e.g., FIGS. 6C-6E), and the noise meter affordance 622 (e.g., FIGS. 6K-6N) is sampled at a second rate (e.g., a lower sampling rate, 20% lower), while the device 600 does not display the graphical noise meter indicator 638 or the noise meter affordance 622 (e.g., FIG. 6H).

[0200] Subsequent to outputting the tactile alert 642, the device 600 displays the noise notification user interface 608D (e.g., a warning notification) of FIG. 6I. As shown in FIG. 6I, the noise notification user interface 608D includes a notification trigger state (e.g., "110 DB for about 3 minutes") and an explanation of the associated risk of hearing loss. FIGS. 6I and 6J show the device 600 that receives user inputs 628C and 628D (e.g., scroll inputs) in a rotatable and depressible mechanism 604. In response to receiving the user input, the device 600 displays an additional portion of the noise notification user interface 608D.

[0201] As shown in FIG. 6K, the noise notification user interface 608D includes a noise app affordance 644 for launching a noise application, a plurality of mute affordances 646 for suppressing the display of subsequent noise notifications (e.g., the display of the user interface 608D) for a specified period (e.g., one hour and the rest of the day), and a dismiss affordance 648. FIG. 6K shows that the device 600 receives a user input 628E (e.g., a tap) corresponding to the dismiss affordance 648. In response to receiving the user input 628E, the device 600 displays (e.g., redisplay) the clock user interface 608A. In some embodiments, selection of the dismiss affordance 648 causes the device 600 to suppress subsequent notifications for a predetermined automatic suppression period (e.g., 30 minutes) (e.g., hold back the display of the notification user interface 608D even though a notification trigger condition is detected by the device 600). In some embodiments, the notification user interface 608D includes a graphical display of the noise exposure level (e.g., the noise meter indicator 638).

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

[0203] Figure 6L shows 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). Thus, as shown in Figure 6L, the noise state affordance 620 includes a "34 decibel" value indicating that the noise level is below a threshold level (e.g., 80 dB) and an unobtrusive prompt (e.g., a checkmark graphic and "OK"). As shown in Figure 6L, the noise meter affordance 622 provides a graphical representation 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 the threshold level (e.g., the above green and yellow). In some embodiments, the indicator of the noise level relative to the threshold level can be a different color or other non-color identification indicator.

[0204] As shown in Figure 6L, the compact noise affordance 624 displays a combination of the information represented by the noise meter affordance 622 and the noise state affordance 620. Specifically, as shown in Figure 6L, the compact noise affordance includes a graphical representation of the low noise level by displaying the active portion 624A in a size corresponding to two segments (out of 11 segments) of green (e.g., green represented by diagonal hatching, indicating that the noise level is below the threshold), the numerical portion 624B includes a value (e.g., 34 dB), and the graphic portion 624C includes an unobtrusive graphic (e.g., a checkmark graphic) corresponding to the value indicated by the noise state affordance 620.

[0205] Figure 6M shows the state of user interface 608A in response to a sharp increase (e.g., spike) in ambient noise at 10:19. As shown in Figure 6M, the size of the active portion 622A of noise meter affordance 622 increases from 4 segments to 17 segments, and the color of the active portion 622A transitions from green to yellow (e.g., the 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 Figure 6M, the size of the 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, numerical portion 624B, and graphic portion 624C maintain their previous appearance (e.g., as shown in Figure 6L).

[0206] Figure 6N shows the state of user interface 608A after a high noise level has persisted (e.g., for 3 minutes). As shown in Figure 6N, the size and color of the active portion 622A of noise meter affordance 622 remain unchanged (e.g., compared to the depiction in Figure 6M). However, noise state affordance 620, numerical portion 624B, and graphic portion 624C are updated to reflect the continuously rising ambient noise level. In particular, immediately after displaying user interface 608A as shown in Figure 6N (e.g., after device 600 detects and displays a continuous noise level of 110 dB for 3 minutes and then detects and displays the aforementioned notification trigger condition), device 600 does not output a tactile alert (e.g., Figure 6H) or display noise notification user interface 608D (e.g., Figure 6I) because a previous notification was rejected within the automatic suppression period (e.g., 30 minutes).

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

[0208] FIGS. 6P - 6U show device 600 displaying an exemplary watch user interface that includes noise application affordances and elements corresponding to those described above in relation to FIGS. 6A - 6O.

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

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

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

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

[0213] Figures 7A - 7B are flow diagrams showing a method for monitoring noise levels using an electronic device, according to some embodiments. Method 700 is executed 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., accelerometer, gyroscope, GPS, heart rate sensor, barometer, microphone, pressure sensor, ambient light sensor, 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, an electronic device (e.g., 100, 300, 500, 600, 601, 800, 900, 1100, 1200, 1400, 1401, and 1700) is a computer system. The computer system optionally includes communication (e.g., wired communication, wireless communication) between a display generation component and one or more input devices. 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. The one or more input devices are configured to receive input, such as a touch-sensing surface for receiving 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) to an integrated or external display generation component via a wired or wireless connection to visually generate content (e.g., using a display device) and can receive input from the one or more input devices via a wired or wireless connection.

[0215] As described below, method 700 provides an intuitive method for managing noise exposure levels. This method reduces the cognitive burden on the user who attempts to monitor the noise levels (e.g., ambient noise levels) experienced during a day of exposure, thereby creating a more efficient human-machine interface. In the case of battery-operated computing devices, it saves power and extends the time between battery charges by enabling the user to more quickly and efficiently monitor noise exposure levels.

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

[0217] In some embodiments, in accordance with a determination that a set of noise notification criteria is satisfied when, at a first point in time before displaying a first user interface (e.g., 608A, 608C), a current noise level over a third period (e.g., an average value of the current noise level over the third 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 three minutes), the electronic device displays (702) a noise level notification (608D) including: an indication of the current noise level over the third period (e.g., text indicating that the current noise level over the third 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 satisfied when the current noise level exceeds the third threshold noise level for at least the third period. In some embodiments, while displaying the third affordance (e.g., 644), the electronic device receives (708) a user input corresponding to the third affordance. In some embodiments, in response to receiving the user input corresponding to the third affordance, the electronic device displays (710) the first user interface (e.g., 608C) (e.g., opens the noise app). Displaying the noise level notification (e.g., automatically) in accordance with a determination that the set of noise notification criteria is satisfied provides the user with quick and easy access to information regarding the current noise exposure level. By performing an operation when a set of conditions is satisfied without requiring further user input, the operability of the device is enhanced, the user-device interface is made more efficient (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), and in addition, by enabling the user to use the device more quickly and efficiently, the power consumption is reduced and the battery life of the device is improved.

[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 a first point in time (e.g., 10:17 as shown in FIG. 6I). In some embodiments, subsequent noise level notifications are suppressed over a period after a previous noise level notification has been issued. Suppressing subsequent noise level notifications over a period after a previous noise level notification has been issued prevents the electronic device from providing unnecessarily redundant notifications, thereby improving the device's operability, making the user device interface more efficient, and in addition, reducing the device's power consumption and improving battery life by enabling the user to use the device more quickly and efficiently. In some embodiments, notifications displayed within a predetermined period after the first point in time are not suppressed if the noise level falls below a threshold over a certain period (e.g., 15 minutes) after the first point in time.

[0219] In some embodiments, the noise level notification (e.g., 608D) further includes a fourth affordance (e.g., 646) associated with a second predetermined period, and 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 holds (e.g., suppresses) the display of a further instance of the noise level notification for the second predetermined period (e.g., 1 hour, 1 / 2 hour, remainder of the day). Providing the fourth affordance within the noise level notification that enables the user to hold the display of a further instance of the noise level notification on the electronic device allows the user to quickly and easily suppress further noise level notifications on the electronic device. By providing additional control options without cluttering the UI with additional displayed controllers, the device's operability is enhanced, the user device interface is made more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and in addition, the power consumption is reduced and the device's battery life is improved by enabling 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 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), such as noise level data corresponding to the first noise level over a first period, an average value over the first period, or a plurality of data points representing the noise level over the first period) (e.g., the noise level "34 DB" in FIG. 6C). In some embodiments, the first noise level data over the first 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., 622A, 638A) of a first size (e.g., the number, length, or area of segments relative to the overall size of an 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 the 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 a display of the first noise level data other than the size of the active portion (e.g., numerical values, positions of points or lines along the axes of a graph). Displaying a graphical object having an active portion of a first size based on the first noise data and the first color provides the user with noise exposure level information that is readily recognizable and understandable. By providing improved visual feedback to the user, the operability of the device is enhanced, (e.g., assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), making the user device interface more efficient, and in addition, reducing power consumption and improving the battery life of the device by enabling 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 different from the first noise level (e.g., the second noise level is either lower than or higher than the first noise level) (e.g., the noise level "113 DB" in FIG. 6E).

[0223] In response to receiving the second noise level data (720), the electronic device displays an active portion in a second size (722) based on a second noise level that is different from the first size (e.g., the active portion grows or shrinks in response to the difference between the first noise level and the second noise level) (e.g., 638A of FIG. 6D). Displaying an active portion of a second size based on the second noise level in response to receiving the second noise level data enables the user to quickly and easily visually distinguish between the noise exposure level information corresponding to the first noise level data and the second noise level data. By providing improved visual feedback to the user, the operability of the device is improved, (e.g., assisting the user to provide appropriate input when operating the device / interacting with the device and reducing user errors), making the user device interface more efficient, and in addition, reducing power consumption and improving the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0224] In response to receiving the second noise level data (720), according to 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 the active portion (e.g., 638A of FIG. 6D) in a second color that is different from the first color (e.g., a change from green to yellow) (724). Displaying the active portion in a second color that is different from the first color according to 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 specific threshold. By providing improved visual feedback to the user, the operability of the device is improved, (e.g., assisting the user to provide appropriate input when operating the device / interacting with the device and reducing user errors), making the user device interface more efficient, and in addition, reducing power consumption and improving the battery life of the device by enabling the user to use the device more quickly and efficiently.

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

[0226] In some embodiments, while displaying a graphical object having an active portion in a second size and a second color (for example, yellow), the electronic device receives third noise level data corresponding to a third noise level that is below the threshold noise level (728) (for example, the noise level is decreasing until it is below the 80 dB threshold). In some embodiments, in response to receiving the third noise level data, the electronic device displays the active portion in the first color in a third size based on the third noise level data that is smaller than the second size (730) (for example, the active portion shrinks corresponding to the difference between the second noise level and the third noise level and changes from yellow to green) (for example, 638A in FIG. 6F). Displaying the active portion in a third second size based on the third noise level in response to receiving the third noise level data enables the user to quickly and easily visually distinguish between the noise exposure level information corresponding to the first noise level data and the second noise level data and the noise exposure level information corresponding to the third noise level data. By providing improved visual feedback to the user, the operability of the device is improved, (for example, by assisting the user to provide appropriate inputs when operating / interacting with the device and reducing user errors), making the user device interface more efficient, and in addition, by enabling the user to use the device more quickly and efficiently, reducing power consumption and improving the battery life of the device.

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

[0228] In some embodiments, displaying the first user interface, when selected, includes displaying a first affordance to display a second user interface (e.g., an interface having information regarding a threshold noise level) (e.g., 640) according to a determination that the current noise level (e.g., based on the noise data of the first period or the second period) is below a second threshold noise level (e.g., a threshold selected by the user). 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, when selected, includes displaying a second affordance different from the first affordance to display a third user interface (e.g., the same as the second user interface; different from the first user interface and having information regarding a threshold noise level) (e.g., without displaying the first affordance) according 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 mark) when the noise level is 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 a 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 the 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 that is 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 being 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 the first rate). In some embodiments, while the first user interface is not being displayed (e.g., 608B, 608D, and generally as shown 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 being displayed, the 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. In contrast to when the first user interface is being displayed, when the first user interface is not being displayed, by automatically sampling the noise level data at a second sampling rate that is different from the first sampling rate, the electronic device reduces power usage and thus improves the battery life of the device.

[0233] Note that the details of the processes described above with respect to method 700 (e.g., FIGS. 7A - 7B) are also applicable in a similar manner to the methods described below. For example, method 1000 optionally includes one or more of the characteristics of the various methods described above with reference to method 700. For example, information regarding the noise exposure level corresponding to one or more of the output devices described in method 1000 can be presented or provided to the user using the graphical display (e.g., graphical object) described above whose appearance changes based on the noise exposure level. For the sake of brevity, these details are not repeated below.

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

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

[0236] Figures 8C - 8I show various techniques for displaying and manipulating environmental noise data stored via the user interface 808C. As shown in Figures 8C - 8I, the user interface 808C 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 was exposed) over a selectable period (e.g., day, week, month, year).

[0237] As shown in FIGS. 8C - 8D, environmental noise exposure data associated with a particular period (e.g., 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 regarding the selected environmental noise exposure data (e.g., detailed affordance 812). In response to the selection, the device also displays data overlay 810 at the location on chart 805 corresponding to the selected environmental noise exposure data to provide a visual representation of data corresponding to the information displayed by detailed affordance 812.

[0238] As shown in FIGS. 8C - 8I, the 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 the chart 805. As shown in FIGS. 8D - 8E, in response to receiving a user input 806D in the average affordance 814, the device 800 displays an average overlay 810B (e.g., a visual reference for the average environmental noise exposure level calculated over the displayed period). As shown in FIGS. 8E - 8F, in response to detecting a selection of the average overlay 810B (e.g., user input 806E), the device 800 displays an average detail affordance 818. As shown in FIGS. 8F - 8G, in response to detecting a selection of the average overlay 810B (e.g., user input 806E), the device 800 displays an average detail affordance 818. As shown by FIGS. 8F - 8G, in response to receiving a user input 806F in the daily average affordance 820, the device 800 displays a daily average overlay 810C (e.g., a visual reference for the daily - calculated average environmental noise exposure level). In some embodiments, the device 800 displays a noise classification affordance 816 (as shown in FIG. 8E) in response to a determination that the average noise exposure level (e.g., as shown by the average overlay 810B) exceeds a threshold level (e.g., 80 DB). In some embodiments, in response to a determination that the average noise exposure level (e.g., as shown by the average overlay 810B) is below a threshold level (e.g., 80 DB), the device displays a noise classification affordance 816 having a different appearance (e.g., the affordance behaves similar to the noise state affordance 620 or the noise state indicator 640 described above with respect to FIGS. 6A - 6O).

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

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

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

[0242] FIGS. 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 of these figures are used to illustrate the processes described below, including the process of FIG. 10.

[0243] FIG. 9A shows a device 900 that displays a user interface 904A on a display 902. As shown in FIG. 9A, the user interface 904A includes a chart 906 that shows a set of daily audio amplitude values over a seven-day period (e.g., corresponding to the range of sound levels experienced by a user of the device 900 due to the use of a connected audio output device). In some embodiments, the audio amplitude values are determined based on the output volume settings 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 the use of the device) are estimated or extrapolated based on known output device responses (e.g., sensitivity, frequency response). As shown in FIG. 9A, the chart 905 includes a maximum display 908 and a minimum display 910 that represent the highest and lowest audio amplitude levels experienced by a user of the device 900 due to the use of a connected audio output device.

[0244] As shown in FIG. 9A, the average affordance 914 is displayed in a selected state (e.g., previously selected via user input or selected by default when the user interface 904A is displayed). The average affordance 914 includes a value that indicates the average audio level over 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 the average affordance 914 (e.g., overlay 912). In some embodiments, the average audio level is not the average of the displayed data, but rather the time-axis average of the underlying data (e.g., an average based on how much 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 the audio amplitude levels to which the device user was exposed over a day or other period (e.g., time, week, year, month). As shown in FIG. 9A, the user interface 904A includes an audio classification indicator 922 that provides a non-numeric indication (e.g., an indication including graphics and / or text) of the average audio level relative to a threshold (e.g., a predetermined 80 DB threshold). As shown in FIG. 9A, the audio classification indicator 922 indicates that the average audio level (e.g., 77 DB) is below the 80 DB threshold with an “OK” and a checkmark graphic.

[0246] As shown in FIG. 9A, the user interface 904A includes a device type filtering affordance (e.g., an affordance associated with a particular type of device) for highlighting data within graph 905 due to each device type (e.g., highlighting 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 an associated range representing the highest audio amplitude level and the lowest audio amplitude level experienced by a user of device 900 by using a device of the respective device type. In some embodiments, the 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] FIG. 9A shows a device 900 that receives a user input 906A (e.g., a tap) on an uncalibrated device affordance 920. In response to receiving the user input 906A, the device 900 displays a user interface 904B. As shown in FIG. 9B, the uncalibrated device affordance 920 is replaced by a Bluetooth earphone affordance 924 and a general headphone affordance 926, respectively corresponding to an audio output device coupled (e.g., wirelessly or physically) to the device 900 (e.g., the audio output device receives analog or digital audio signals generated by the device 1100 and converts them into acoustic outputs).

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

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

[0250] In addition to emphasizing audio data in response to the user input 906C, the device 900 updates the overlay 912 to show an average audio level (e.g., 72 dB) (e.g., the average audio level resulting from the earphone device type) based on the emphasized set of noise amplitude values.

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

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

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

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

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

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

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

[0258] As shown in FIG. 9G, the user interface 904G emphasizes audio level data resulting from one or more output devices associated with the general 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) resulting from devices corresponding to a selected device type filter (e.g., a general headphone type device) is visually distinguished from data not resulting from devices corresponding to the selected device type filter (e.g., by varying visual characteristics such as color, hue, saturation, texture). As shown in FIG. 9G, data resulting from a general headphone type device corresponds to black data points on the chart 905. In addition to displaying the emphasized audio data for different time periods in response to the user input 906F, the device 900 updates the 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 an emphasized set of noise amplitude values within the displayed 24-hour period (e.g., the average audio level resulting from a general headphone device type). For example, the average affordance 914 is updated to indicate a daily average audio level of 68 DB (e.g., compared to the weekly average audio level of 85 DB as shown in FIGS. 9A - 9F).

[0259] FIG. 10 is a flow diagram showing a method for monitoring noise exposure levels using an electronic device, according to some embodiments. Method 1000 is executed 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 sensing 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 a communication (e.g., wired communication, wireless communication) between a display generation component and one or more input devices. 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. The one or more input devices are configured to receive input, such as a touch sensing surface for receiving 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) to an integrated or external display generation component via a wired or wireless connection to visually generate content (e.g., using a display device), and can receive input from the one or more input devices via a wired or wireless connection.

[0261] As described below, method 700 provides an intuitive method for managing noise exposure levels. This method reduces the user's cognitive burden when monitoring noise exposure levels, thereby creating a more efficient human-machine interface. In the case of battery-operated computing devices, enabling the user to monitor noise exposure levels faster and more efficiently saves power and extends the time between battery charges.

[0262] The electronic device receives (1002) first noise level data resulting from a first device type (e.g., an uncalibrated device such as a wired headset or an uncalibrated wireless headset connected to the electronic device via a port (e.g., a headphone jack)). The electronic device receives (1002) second noise level data resulting from a second device type different from the first device type (e.g., a calibrated device such as a calibrated wireless headset). In some embodiments, the electronic device identifies 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 an output device of the first type.

[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 browse the UI of a noise application via a search feature of a health app or a notification discovering a tab of a health app). The first user interface includes (e.g., a graph showing combined data for each of the first and second noise level data or showing separate data simultaneously) (1006) (e.g., 905 in FIG. 9A) a first representation of received noise level data based on first noise level data and second noise level data. The first user interface includes (1008) (e.g., 916) a first device type data filtering affordance. Including, in the first user interface (e.g., as a graph), a first representation of received noise level data based on first noise level data and second noise level data visually informs the user of the noise level data in an easily understandable and recognizable manner. By providing improved visual feedback to the user, the operability of the device is improved, (e.g., assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), making the user device interface more efficient, and in addition, reducing power consumption and improving the battery life of the device by enabling 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 a first user input, the electronic device displays a second representation of received noise level data based on second noise level data and not based on first noise level data (1014) (e.g., a second representation that emphasizes noise level data from a calibrated device as compared to the depiction of the noise level data in the first representation (e.g., a separate graph, a visual emphasis on the first representation)) (e.g., 905 of FIGS. 9C - 9D, FIGS. 9F, and 9G). Displaying, in response to detecting the first user input, a second representation of received noise level data based on second noise level data and not based on first noise level data (e.g., as a separate graph) enables the user to more easily view information corresponding to the second noise level data. By providing improved visual feedback to the user, the device's operability is improved, (e.g., assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), making the user device interface more efficient, and in addition, reducing power usage and improving the device's battery life by enabling the user to use the device more quickly and efficiently.

[0266] In some embodiments, as part of displaying a second representation of the received noise level data, the electronic device maintains a first representation of the received noise level data (1016) (e.g., 905 of FIGS. 9C and 9D - 9G). In some embodiments, the second representation of the received noise level data is visually distinct from the first representation of the received noise level data (e.g., 905 of FIGS. 9C and 9D - 9G). In some embodiments, visually differentiating data (e.g., a set of exposure levels resulting from a second output device type) includes suppressing the noise exposure level resulting from the first device type data by varying one or more visual characteristics (e.g., luminance, opacity, color, contrast, hue, saturation) (e.g., 905 of FIGS. 9C and 9D - 9G). In some embodiments, visually differentiating data includes emphasizing the noise exposure level resulting from the second device type by varying one or more visual characteristics (e.g., luminance, opacity, color, contrast, hue, saturation) (e.g., 905 of FIGS. 9C and 9D - 9G).

[0267] In some embodiments, the second noise level data corresponds to noise level data resulting from a single device. In some embodiments, the single device includes 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 a plurality of devices (e.g., a set of a plurality of linked devices (e.g., a pair of linked wireless headphones)).

[0269] In some embodiments, the second noise level data includes third noise level data resulting from 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 corresponding to the third noise level data (e.g., an additional calibrated device affordance added to the first calibrated device affordance) (e.g., 918). In some embodiments, while displaying the first user interface (e.g., 904C), the electronic device detects a user input corresponding to a selection of the second device type filtering affordance (e.g., 906C). In some embodiments, in response to detecting a user input corresponding to a selection of the second device type filtering affordance, the electronic device displays a third representation of the third noise level data (e.g., 905 in FIG. 6D). Displaying the third representation of the third noise level data enables the user to more easily view and understand information corresponding to the third noise level data. By providing improved visual feedback to the user, the operability of the device is improved, (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), making the user device interface more efficient, and in addition, reducing power usage and improving the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0270] In some embodiments, before detecting a first user input, the first user interface includes (1010) an average noise exposure level indicator (e.g., 912, 914) that indicates an average noise exposure level corresponding to first noise level data and second noise level data for a first period (e.g., day, week). In some embodiments, the average noise level indicator includes a checkmark or exclamation mark, "large" 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 that indicates an average noise exposure level provides the user with a simple and easily recognizable metric for understanding the overall noise exposure level. By providing improved visual feedback to the user, the operability of the device is improved, (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), making the user device interface more efficient, and in addition, reducing power usage and improving the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0271] In some embodiments, in response to detecting a user input corresponding to the selection of a 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 a second device type) (e.g., 912 in FIGS. 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 the 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., 87 dB headphones of the first type output at 100% for a particular signal being played).

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

[0274] Note that the details of the process (e.g., FIG. 10) described above with respect to method 1000 are also applicable in a similar manner to the methods described above. For example, method 700 optionally includes one or more of the characteristics 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) whose appearance changes based on the noise exposure level can be used to display noise exposure level information corresponding to one or more output devices. For the sake of brevity, these details are not repeated below.

[0275] Figures 11A - 11F show a user interface (e.g., 1104A - 1104F) for accessing and displaying audiogram data (e.g., a set of data representing hearing 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 input by the device user (e.g., via a series of user inputs detected by device 1100). For example, FIGS. 11A and 11B show a user interface within a health application for accessing audiogram noise data. FIGS. 11C - 11D show techniques for displaying audiogram data and selecting or visually emphasizing portions of the data (e.g., portions associated with the left or right side).

[0276] Figures 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 via a device associated with device 1100 such as a connected headset, integrated headset or speaker, external speaker, and other media playback devices). For example, FIG. 11H shows a technique for creating an auditory profile via an A - B test process auditory test supplemented by stored audiogram data. In some embodiments, using the audiogram data shortens the process of creating an auditory profile or improves the profile accuracy compared to an adjustment process that does not utilize the audiogram data.

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

[0278] Figures 12A - 12AN illustrate a device 1200 that displays a user interface on a display 1202 (e.g., a display device or a 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] Figures 12A - 12C each illustrate an exemplary user interface for accessing a headphone audio settings interface 1205 of Figure 12C in response to detection of inputs 1204 and 1206 of Figures 12A and 12B.

[0280] In Figure 12C, device 1200 displays, via display 1202, a headphone audio settings interface 1205 presented with selected standard audio setting options 1208. Accordingly, device 1200 currently applies a standard (e.g., uncustomized) audio setting to one or more connected headphone devices. The headphone audio settings interface 1205 also includes custom audio setting options 1210 and custom audio setup options 1212. The custom audio setting options 1210 are selectable to manually set custom audio settings for the connected headphone device, and the custom audio setup options 1212 are selectable to initiate a guided process for configuring a customized audio setting.

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

[0282] In FIG. 12D, the customization options 1214 include a set 1215 of audio options that can be selected and, in some embodiments, are individually adjusted (e.g., customized) using the slider 1216 to select a boost level for each respective 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 the slider 1216. In some embodiments, the audio options 1215 can include options corresponding to the customized audio setting based on the results of an audiometry test (e.g., an audiogram). In such embodiments, the audiogram settings cannot be changed using the customization options 1214 and, as a result, the slider 1216 is not displayed when the audiogram option is selected. The audiogram options are described in more detail below.

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

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

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

[0286] In FIG. 12F, device 1200 displays the selected brightness option 1215-3 (in response to input 1220 in FIG. 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, slider 1216 can have an appearance different from that shown in the headset audio settings interface 1205. For example, slider 1216 can have additional setting positions such as "none", "very slight", or "very strong", or intermediate positions between "slight" and "moderate", and between "moderate" and "strong". In some embodiments, slider 1216 can be modified to include the ability to set a range of values. For example, slider 1216 can have two notches for setting the upper end of the range and the lower end of the range. Additionally, in some embodiments, slider 1216 can be replaced or supplemented with other user interface objects to indicate boost settings, such as a field for entering a range of values (e.g., a numerical range) or a range of values (e.g., numerical values).

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

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

[0290] Referring now to FIG. 12G, device 1200, in response to input 1228, displays an introduction interface 1229. Introduction interface 1229 indicates that the customization process can be used to customize headset audio settings for calls, media, and ambient audio, and that the customization process can incorporate audiogram results. In some embodiments, introduction interface 1229 is not displayed in response to input 1228. For example, in some embodiments, device 1200 displays introduction interface 1229 only at a first time when the user selects custom audio setup option 1212. In such embodiments, device 1200 instead displays the interface shown in FIG. 12H or FIG. 12K in response to the 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 in the user account associated with device 1200. For example, in FIG. 12G, the user's account includes audiogram 1233-1 from an audiometry test conducted on February 19, 2019, and audiogram 1233-2 from an audiometry test conducted on March 23, 2020. The user can select the audiogram that the user wants to use to customize the 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 healthcare provider. In some embodiments, if the user account does not include any audiograms, audiogram interface 1232 is not displayed. In such embodiments, device 1200 instead displays the interface shown in FIG. 12K (e.g., in response to input 1228 or input 1230).

[0292] The hearing diagram interface 1232 includes an option 1234 to select to use the hearing diagram selected to customize the audio settings and an option 1236 to select not to use the hearing diagram to customize the audio settings. In FIG. 12H, the device 1200 detects an input 1238 on the option 1234 and uses the hearing diagram 1233-2 selected to customize the audio settings. In response to the detection of the input 1238, the device 1200, as shown in FIG. 12I, ends the custom audio setup process, applies the custom audio settings based on the selected hearing diagram, and displays the headphone audio settings interface 1205. In some embodiments, before displaying the interface of FIG. 12I, the device 1200 displays the user interface shown in FIG. 12AE to enable the user to customize the ambient audio settings. In some embodiments, before displaying the interface of FIG. 12I, the device 1200 includes options for comparing the standard audio settings with the audio settings based on the hearing diagram, as described in more detail below in connection with FIGS. 12AC and 12AD, and instead displays an interface similar to the recommended interface 1280, including an option to select the standard audio settings or an option to select the settings customized based on the hearing diagram.

[0293] In FIG. 12I, the audio option 1215 is updated and shown by the selected hearing diagram list option 1215-4. Since the hearing diagram option 1215-4 is selected, the device 1200 customizes the audio settings that cannot be configured by the user (e.g., using the headphone audio settings interface 1205). Accordingly, the slider 1216 is not displayed. In some embodiments, the audio option 1215 includes the hearing diagram option 1215-4 when the hearing diagram is available to customize the audio settings, and otherwise the hearing diagram option 1215-4 is not displayed.

[0294] In FIG. 12J, device 1200 shows an embodiment where an audiogram is not used to customize audio settings, and instead the device follows a custom audio setup process in response to input 1240 on option 1236.

[0295] In FIG. 12K, device 1200 displays an instruction interface 1242 that includes a continuous affordance 1242-1 that is shown as unavailable for current selection because a headphone device is not currently connected to device 1200.

[0296] In FIG. 12L, device 1200 is coupled (e.g., paired, connected, communicating, or actively exchanging data) to a headphone device 1245 (e.g., via a wireless connection), and the continuous affordance 1242-1 is shown as available for selection. Device 1200 detects an input 1244 on the continuous 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 at what volume the user can listen. In some embodiments, device 1200 uses the tone adjustment stage to determine which audio tones are preferred by the user. In some embodiments, device 1200 recommends one or more adjustments to the 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 can recommend improving the tone balance slightly, moderately, or strongly. As another example, device 1200 can recommend enhancing the speech clarity slightly, moderately, or strongly. As yet another example, device 1200 can recommend boosting the brightness slightly, moderately, or strongly. In some embodiments, device 1200 can recommend adjustments to any combination of tone balance, speech clarity, and brightness. In some embodiments, the tone adjustment stage determines whether adjustments are recommended for tone balance, speech clarity, and / or brightness based on the user's preferences. In some embodiments, the results of the amplification stage affect 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 FIGS. 12M and 12N, device 1200 shows the interface of the amplification stage of the custom audio setup process. During the amplification stage, device 1200 generates audio output at different volumes to determine which volume can be heard by the user. In some embodiments, the audio is a looped playback of the audio announcement "Hello". In the embodiments shown in FIGS. 12M - 12AN, sound graphic 1245-1 is used to indicate that the audio was generated by the headphone device 1245. In some embodiments, device 1200 displays a waveform (e.g., waveform 1248-1 in FIG. 12M) with movement to indicate to the user that the audio is being played, even if the user cannot hear it.

[0299] In FIG. 12M, device 1200 displays a first amplification comparison interface 1247 and generates audio at a low bass level. Interface 1247 instructs the user as to whether they can hear the audio generated by the 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 in combination with the continuous affordance 1249 whether the user can hear the audio.

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

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

[0302] In FIG. 12N, device 1200 displays a second amplification comparison interface 1252 and generates audio at a media sound level (with the headset device 1245). Interface 1252 indicates to the user whether they can hear audio visually represented by waveform 1248-2 having an amplitude greater than waveform 1248-1. If the user indicates that they can hear the audio, since the user has indicated that they can hear the media sound level, the amplification setting is medium. If the user indicates that they cannot hear the audio, the amplification setting becomes strong.

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

[0304] In some embodiments, the setting of toggle selector 1246 persists until changed by the selection of an unselected toggle. For example, in FIG. 12M, when toggle 1246-2 is not selected and the second amplification comparison interface 1252 is displayed in FIG. 12N, it remains selected. However, in some embodiments, the setting of 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 shows the interface for the tone adjustment stage of a custom audio setup process. During the tone adjustment stage, device 1200 generates a set of audio comparisons. Each comparison features two audio samples of the same sound (e.g., looped playback of music), where each sample has different audio characteristics from the other sample. For each comparison, device 1200 instructs the user to select which audio sample they prefer, and based on those selections, instructs to recommend 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 selections and, as a result, ends the tone adjustment stage after two comparisons. Such embodiments are shown in FIGS. 12P - 12T.

[0306] In response to the detection of input 1254 in FIG. 12O, device 1200 displays a first comparison interface 1255-1, as shown in FIG. 12P, and generates music with headphone device 1245. Interface 1255-1 instructs the user to indicate whether they prefer a first version of the audio or a second version of the audio. Interface 1255-1 includes a 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, the music is played on headphone device 1245 having audio characteristics corresponding to the first version of the audio. Similarly, when the second version of the audio is selected, the music is played on headphone device 1245 having audio characteristics corresponding to the second version of the audio. While the music continues to play, the user can toggle between the first and second versions and change the audio characteristics of the music based on the selection. For example, the pitch changes when the second version is selected and then returns 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 instructs the user to select the first version if the two version sounds are the same to the user.

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

[0308] Each comparison interface includes a waveform providing a visual representation of the audio samples being generated on the headset 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 FIG. 12P, the device 1200 detects an input 1262 for selecting an option to cancel the custom audio setup process and, in response, displays a confirmation interface 1263 prompting the user to complete the custom audio setup process. In response to the detection of input 1264, the device 1200 returns to the first comparison interface 1255-1 in FIG. 12R.

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

[0311] When device 1200 displays the second comparison interface 1255-2, it continues to generate music with headphones 1245. The second comparison interface 1255-2 is similar to the 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 the first comparison interface 1255-1 as shown by waveform 1260-1. Thus, the music generated with the headphones remains unchanged when transitioning from the first comparison interface 1255-1 to the second comparison interface 1255-2.

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

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

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

[0315] FIGS. 12U-12AD show exemplary embodiments where the tone adjustment phase is complete and custom audio settings are recommended based on the user's selected preferences.

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

[0317] In FIG. 12V, device 1200 detects an input 1273 on the continuous affordance that indicates the user's preference for the second version of the audio - i.e., the second audio sample in the first comparison. In response to the detection of input 1273, device 1200 displays a second comparison interface 1255-2 as shown in FIG. 12W.

[0318] In FIG. 12W, device 1200 continues to play music on the headset device 1245. The music played on the headset device 1245 currently has audio characteristics associated with the second version of the audio selected in the first comparison interface 1255-1 as shown by waveform 1260-2. In other words, the second comparison interface 1255-2 features a comparison of audio samples different from those provided in the first comparison interface 1255-1, but one of the characteristic audio samples in the second comparison (second version) is the audio sample selected from the 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 within the first comparison interface, but at least one of the first or second versions of the audio in the second comparison is influenced by the version of the audio selected within the first comparison interface.

[0319] In some embodiments, the setting of the toggle selector 1257 persists across different comparison interfaces. For example, in the embodiment shown in FIG. 12W, the toggle 1257-2 of version 2 remains selected (after input 1273), and the set of audio characteristics selected from the first comparison interface 1255-1 (the second version of the audio in the first comparison) remains associated with the toggle 1257-2 of version 2. However, in some embodiments, the setting of the toggle selector 1257 is reset to have the selected version 1 toggle 1257-2 when a new comparison interface is displayed. According to such embodiments, the second comparison interface of FIG. 12W is shown with the selected version 1 toggle 1257-1, and the audio characteristics associated with the second version of the audio within 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 back to FIG. 12W, device 1200 detects input 1274 on toggle 1257-1 of version 1 and, in response, changes the music in headphone device 1245 based on audio characteristics associated with a first version of the audio samples within second comparison interface 1255-2. The first version of the audio in second comparison interface 1255-2 is different from both the first and second versions of the audio within the first comparison interface (and the second version of the audio in the second comparison), as shown by waveform 1260-3 of FIG. 12X. Further still, in the embodiment shown in FIG. 12X, the first version of the audio signal (e.g., waveform 1260-3) characterized by second comparison interface 1255-2 is different from the audio signal (e.g., waveform 1260-1) characterized by second comparison interface 1255-2 of FIG. 12S. This is because the selection of the preferred audio samples affects the audio samples used in subsequent comparisons, and the selection in the embodiment illustrated in FIG. 12S is different from the selection in the embodiment shown 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 of FIG. 12Y.

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

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

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

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

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

[0327] The recommended interface 1280 includes a recommended toggle selector 1282 that includes a custom toggle 1282-1 and a standard toggle 1282-2. When the custom toggle 1282-1 is selected, device 1200 generates audio with the recommended audio adjustments on a headset device 1245 as shown in FIG. 12AC. In the embodiment of FIG. 12AC, waveform 1260-5 represents the audio on a headset device 1245 with customized audio settings. In some embodiments, waveform 1260-5 corresponds to a preferred audio sample (e.g., waveform 1260-4) selected at a third comparison interface 1255-3. In some embodiments, waveform 1260-5 is different from the preferred audio sample selected at 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 with a headphone device 1245 having standard audio settings. In the embodiment of FIG. 12AD, waveform 1260-6 represents the audio in headphone device 1245 having standard audio settings. In some embodiments, waveform 1260-6 corresponds to waveform 1260-1 of the first comparison interface 1255-1. In some embodiments, waveform 1260-6 incorporates an amplification setting determined from the amplification stage of a custom audio setup process. In some embodiments, waveform 1260-6 does not incorporate an amplification setting determined from the amplification stage of a custom audio setup process.

[0329] The recommended toggle selector 1282 enables the user to toggle between custom audio settings and standard audio settings, enables the user to listen to a preview of the audio characterized by the custom settings or the standard settings, and enables the user to more efficiently determine whether to apply the recommended customized audio settings or instead use the standard audio settings.

[0330] The recommended interface 1280 further includes custom setting affordances 1284-1 and standard setting affordances 1284-2. The custom setting affordances 1284-1 are selectable to apply recommended custom audio settings and, in some embodiments, create a custom audio setting profile that can be used to apply the custom audio settings to other connected headset devices. The standard setting affordances 1284-2 are selectable to apply standard audio settings. In FIG. 12AD, device 1200 detects an input 1285 on the custom setting affordance 1284-1 and, in response, applies the custom audio settings and optionally displays a transparency mode interface 1286 as shown in FIG. 12AE.

[0331] Referring now to FIG. 12AE, in some embodiments, device 1200 optionally displays the transparency mode interface 1286 when ambient audio settings are supported by the headset device 1245. Otherwise, device 1200 displays a headset audio settings interface 1205 as shown in FIG. 12AF. The 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 the audio settings of the features of the headset 1245 for amplifying ambient sound, as described in more detail below with respect to FIG. 12AH. In some embodiments, the headset device 1245 generates ambient audio as indicated by a sound graphic 1245-1 when displaying the transparency mode interface 1286. For example, the headset 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 the physical environment while wearing the headset.

[0332] The pass-through mode interface 1286 also includes an option 1286-4 for applying any setting changes made using the sliders 1286-1, 1286-2, and 1286-3. In FIG. 12AE, the device 1200 detects an input 1287 on the option 1286-5 and, in response, displays the headphone audio setting interface 1205 without applying any pass-through mode setting changes, as shown in FIG. 12AF.

[0333] Referring now to FIG. 12AF, the device 1200 displays an audio setting interface 1205 with updated audio settings based on the results of a custom audio setup process. For example, the brightness option 1215-3 is selected and shown to have a medium boost 1216-2 as indicated by the slider 1216 (based on the results of a custom audio setup process). In some embodiments, the user can further adjust any of the audio options 1215 (other than the audiogram option 1215-4) by selecting the respective audio option and adjustment slider 1216. In some embodiments, if the custom audio settings are not set or have not been 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 the device 1200, as described in more detail below.

[0334] In FIG. 12AF, since the transparency mode setting 1226 has not been changed from the transparency mode setting in FIG. 12AE, it is shown with the standard setting. In some embodiments, when these settings are changed and option 1286-4 is selected, the transparency mode setting 1226 displays "Custom" in FIG. 12AF. The device 1200 detects the input 1288 on the transparency mode setting 1226 and, in response, displays a transparency mode setting interface 1289 similar to the transparency mode interface 1286 in FIG. 12AE.

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

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

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

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

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

[0340] FIG. 13 is a flowchart showing a method for customizing audio settings based on user preferences using a computer system according to some embodiments. Method 1300 is executed on a computer system (e.g., smartphone, smartwatch) (e.g., devices 100, 300, 500, 600, 601, 800, 900, 1100, 1200, 1400, 1401, 1700) that communicates with a display generation component (e.g., display 1202) (e.g., display controller, touch - sensitive display system), an audio generation component (e.g., headset device 1245) (e.g., audio circuit, speaker), and one or more input devices (e.g., 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, an electronic device (e.g., 100, 300, 500, 600, 601, 800, 900, 1100, 1200, 1400, 1401, and 1700) is a computer system. The computer system optionally is a communication (e.g., wired communication, wireless communication) between a display generation component and one or more input devices. 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. 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) to an integrated or external display generation component via a wired or wireless connection to visually generate content (e.g., using a display device) and can receive input from the one or more input devices via a wired or wireless connection.

[0342] Method 1300 provides an intuitive way to customize audio settings based on user preferences. This method reduces the user's cognitive burden for customizing audio settings based on the user's preferences, thereby creating a more efficient human-machine interface. In the case of a battery-operated computing device, power is conserved and the battery charging interval is lengthened by enabling the user to customize audio settings more quickly and efficiently.

[0343] In method 1300, a computer system (e.g., 1200) simultaneously displays (1304) a representation (e.g., 1257-1) of a first audio sample (e.g., via a display generation component (e.g., 1202)), where the representation is of an interface object (e.g., a selectable user interface object (e.g., an affordance)) (e.g., 1260-1 within interface 1255-1 (e.g., FIG. 12U)) (e.g., 1260-3 within interface 1255-2 (e.g., FIG. 12X)) (e.g., 1260-3 within interface 1255-3 (e.g., FIG. 12AA)), and the first audio sample has a first set of audio characteristics (e.g., a first value for one or more of amplification, balance, speech clarity, brightness) (e.g., the first affordance is selectable to change the audio characteristics of the audio sample to the first set of audio characteristics), and simultaneously displays (1306) a representation (e.g., 1257-2) of a second audio sample (e.g., a second affordance) (e.g., 1260-2 within interface 1255-1 (e.g., FIG. 12V)) (e.g., 1260-2 within interface 1255-2 (e.g., FIG. 12W)) (e.g., 1260-4 within interface 1255-3 (e.g., FIG. 12AB)), where the second audio sample has a second set of audio characteristics different from the first set of audio characteristics, to display (1302) an audio preference interface (e.g., 1255 (e.g., 1255-1, 1255-2, 1255-3), 1247, 1252). In some embodiments, a display (e.g., a focus selector, a highlight, a visual emphasis) indicating whether the first audio sample or the second audio sample is currently selected is displayed (e.g., in FIG. 12R, version 1 of toggle 1257-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 is an audio sample of speech or music, and the second audio sample is an audio sample of the same speech or music having different values for at least one of amplification, balance, speech intelligibility, and brightness.

[0344] (In some embodiments, following the display) while an audio preference interface (e.g., 1255 (e.g., 1255-1, 1255-2, 1255-3), 1247, 1252) is being displayed (1308), a computer system (e.g., 1200) outputs (1310) at least a portion of the first audio sample (e.g., 1260-1 within interface 1255-1 (e.g., FIG. 12U)) (e.g., 1260-3 within interface 1255-2 (e.g., FIG. 12X)) (e.g., 1260-3 within interface 1255-3 (e.g., FIG. 12AA)) (e.g., and / or at least a portion of the second audio sample) via an audio generation component (e.g., 1245), and the computer system receives (1312) a set of one or more 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 the audio preference interface is being displayed provides feedback that enables the user to more quickly and easily associate the output audio with selections made using the audio preference interface. By providing improved feedback, the operability of the device is enhanced, (e.g., by assisting the user in making appropriate inputs and reducing user errors when operating / interacting with the device) making the user-device interface more efficient, which in turn enables the user to use the device more quickly and efficiently, reducing power usage and improving the battery life of the device.

[0345] In 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 an audio sample represented by waveform 1260-1 in interface 1255-1 (e.g., FIG. 12R)) (e.g., input 1268 results in the selection of an audio sample represented by waveform 1260-1 in interface 1255-2 (e.g., FIG. 12S)) (e.g., input 1276 results in the selection of an audio sample represented by waveform 1260-3 in interface 1255-2 (e.g., FIG. 12Z)) (e.g., input 1285 results in the selection of an audio sample represented by waveform 1260-5 in interface 1280 (e.g., FIGS. 12AC and 12AD)) or selects a second audio sample as a preferred sample (e.g., as the selected sample) (e.g., input 1273 results in the selection of an audio sample represented by waveform 1260-2 in interface 1255-1 (e.g., FIG. 12V)) (e.g., input 1278 results in the selection of an audio sample represented by waveform 1260-4 in interface 1255-3 (e.g., FIG. 12AB)) and records it (1316) (e.g., stores it 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 the representation of a first audio sample (e.g., input 1274) or a 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 1278 on a continuous affordance) received while an indicator (e.g., a focus selector, a bold outline) indicating that the first audio sample is currently selected or the second audio sample is currently selected is displayed, and recording the selection includes recording the selection of the audio sample currently shown as the selected audio sample as a 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), a computer system (e.g., 1200) outputs (1318), via an audio generation component (e.g., 1245), first audio data (e.g., audio generated at a headphone device 1245 (e.g., in some embodiments, represented by the presence of a sound graphic 1245-1)) (e.g., audio media (e.g., music, recordings, the audio component of audio-visual media)).

[0347] The output of the first audio data (e.g., current audio playback, future audio playback) is based on at least one audio characteristic of the first set of audio characteristics (1320) (e.g., used to generate) (e.g., in FIG. 12AA, the audio generated by the headphone device 1245 is based on the audio selected as a result of the selection of toggle 1257-1 of version 1 and input 1276 in FIG. 12Z) (e.g., for the output of audio playback, select one or more values from the corresponding first values of the first set of audio characteristics, such as amplification, balance, audibility, and brightness), according to the first audio sample recorded as a preferred sample (e.g., the first audio sample is selected as a preferred 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)).

[0348] The output of the first audio data (e.g., current audio playback, future audio playback) is based on at least one audio characteristic of the second set of audio characteristics (1322) (e.g., used to generate) (e.g., in FIG. 12W, the audio generated by the headphone device 1245 is based on the audio selected as a result of the selection of toggle 1257-2 of version 2 and input 1273 in FIG. 12V) (e.g., for the output of audio playback, select one or more values from the corresponding second values of the second set of audio characteristics, such as amplification, balance, audibility, and brightness), according to the second audio sample recorded as a preferred sample (e.g., the second audio sample is selected as a preferred 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)).

[0349] In some embodiments, after recording the selection of a first audio sample as a preferred sample (e.g., 1260-1 within interface 1255-1 (e.g., FIG. 12U)) (e.g., 1260-3 within interface 1255-2 (e.g., FIG. 12X)) (e.g., 1260-3 within interface 1255-3 (e.g., FIG. 12AA)), or the selection of a second audio sample as a preferred sample (e.g., 1260-2 within interface 1255-1 (e.g., FIG. 12V)) (e.g., 1260-2 within interface 1255-2 (e.g., FIG. 12W)) (e.g., 1260-4 within interface 1255-3 (e.g., FIG. 12AB)), the computer system (e.g., 1200) simultaneously displays, via a display generation component (e.g., 1202), a representation of a third audio sample having a third set of audio characteristics (e.g., 1260-3 within interface 1255-2 (e.g., FIG. 12X)) (e.g., 1260-3 within interface 1255-3 (e.g., FIG. 12AA)) (e.g., 1257-1 within subsequent interfaces (e.g., 1255-2, 1255-3)) and a representation of a fourth audio sample having a fourth set of audio characteristics different from the third set of audio characteristics (e.g., 1260-2 within interface 1255-2 (e.g., FIG. 12W)) (e.g., 1260-4 within interface 1255-3 (e.g., FIG. 12AB)) (e.g., 1257-2 within subsequent interfaces (e.g., 1255-2, 1255-3)). In some embodiments, at least one of the third audio sample or the fourth audio sample is selected as a preferred sample based on (e.g., selected in accordance with) the recorded selection of the first audio sample or the second audio 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 representations of the first and second audio samples) and displays a subsequent audio sample comparison including the 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 for subsequent audio sample comparisons is an audio sample from a 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, the representation of a first audio sample (e.g., 1257-1) causes, via an audio generation component (e.g., 1245), the output of at least a second portion of the first audio sample (e.g., a portion that is the same as or different from the portion of the first audio sample of the first audio sample), when the representation is selected while the first audio sample is not being output (e.g., see FIG. 12W). (e.g., in FIG. 12W, input 1274 at toggle 1257-1 of version 1 causes an audio output in 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, the representation of a second audio sample (e.g., 1257-2) causes, via the audio generation component, the output of at least a portion of the second audio sample when the representation is selected while the second audio sample is not being output (e.g., see FIG. 12AA). (e.g., in FIG. 12AA, input 1277 at toggle 1257-2 of version 2 causes an audio output in 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 the audio output while a selectable volume control user interface object is being 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 enables the user to more quickly and easily compare and adjust the audio being generated without the need to display a separate interface for accessing volume control, thereby reducing the number of inputs required to perform volume adjustment and allowing audio samples to be compared. Reducing the number of inputs required to perform an operation increases the operability of the device, 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 in addition, by enabling the user to use the device more quickly and efficiently, power usage of the device is reduced and battery life is improved. 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, a first audio sample (e.g., the audio associated with toggle 1257-1 of version 1) and a second audio sample (e.g., the audio associated with toggle 1257-2 of version 2) are both based on second audio data (e.g., in FIGS. 12V or 12W, the audio generated by headphone device 1245) (e.g., audio media (e.g., music, recordings, the audio components of audio-visual 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 having different sets of audio characteristics). In some embodiments, the second audio data is the first audio data. In some embodiments, while a computer system (e.g., 1200) outputs the second audio data at a first point in time (e.g., a timestamp, a particular time within the total playback time) within the playback time of the second audio data as part of the first audio sample or as part of the second audio sample (e.g., while outputting the second audio data based on a first set of audio characteristics or a second set of audio characteristics), the computer system receives, via one or more input devices, a second set of one or more user inputs (e.g., input 1272, input 1275). In some embodiments, the second audio data is output as looped playback such that when the end of the playback time is reached, the audio resumes from the start 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 a determination that second audio data is being output as part of a first audio sample and a determination that the set of one or more user inputs includes a selection of a representation of a second audio sample, the computer system continues to output the second audio data from a first point in time (e.g., substantially from the first point in time), and transitions to outputting the second audio data as part of a second audio sample (e.g., while continuing to play the second audio data from the same point in time, changing the playback of the second audio data based on a first set of audio characteristics to a second set of audio characteristics) (e.g., in FIGS. 12U and 12V, in response to input 1272, audio continues to play on the headset device 1245 and switches from the audio characteristics associated with toggle 1257-1 of version 1 to the audio characteristics associated with toggle 1257-2 of version 2). In some embodiments, in response to receiving a second set of one or more user inputs, in accordance with a determination that second audio data is being output as part of a second audio sample and a determination that the set of one or more user inputs includes a selection of a representation of a first audio sample, the computer system continues to output the second audio data from a first point in time and transitions to outputting the second audio data as part of a first audio sample (e.g., while continuing to play the second audio data from the same point in time, changing the playback of the second audio data based on a second set of audio characteristics to a first set of audio characteristics) (e.g., in FIGS. 12W and 12X, in response to input 1274, audio continues to play on the headset device 1245 and switches from the audio characteristics associated with toggle 1257-2 of version 2 to the audio characteristics associated with toggle 1257-1 of version 1).Transitioning the output of the second audio data based on the selection of the representation of the audio sample allows the user to compare and contrast different audio samples without the need to start the playback of the audio for each comparison while the second audio data is being output continuously, thereby reducing the number of inputs required to perform the audio comparison. By reducing the number of inputs required to perform the operation, the operability of the device is enhanced, the user device interface is made more efficient (e.g., by assisting the user in making appropriate inputs when operating the device / interacting with the device and reducing user errors), and in addition, the power consumption of the device is suppressed and the battery life is improved by enabling the user to use the device more quickly and efficiently. In some embodiments, the audio is output in loop playback while the user is selecting the representation of the first audio sample or the representation of the second audio sample. When the user toggles between selecting the representation of the first audio sample and selecting the 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 spoken audio sample (e.g., audio including recorded utterances of a person). In some embodiments, the audio preference interface includes a volume control interface when one or more of the audio samples include a spoken audio recording. In some embodiments, the audio preference interface does not include a volume control interface when one or more of the audio samples include a spoken audio recording.

[0354] In some embodiments, after selecting the first audio sample and recording it as a preferred audio sample, or after selecting the second audio sample as a preferred audio sample (in some embodiments, before outputting the first audio data), the computer system (e.g., 1200) displays, via a display generation component (e.g., 1202), 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 samples recorded in response to one or more sets of 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, simultaneously, including a recommended audio adjustment interface (e.g., 1270, 1280) (e.g., the recommended audio adjustment is based at least in part on the selection of the first or second audio sample recorded as a preferred sample). In some embodiments, the fifth set of audio characteristics is a set of default audio characteristics (e.g., default or standard audio characteristics) that is not based on a selection recorded using an audio preference interface. In some embodiments, the computer system receives, via one or more input devices, a third set of one or more inputs (e.g., inputs on 1282-1, 1283, 1285).In some embodiments, in response to receiving a third set of one or more inputs and in accordance with a determination that the one or more third sets of inputs include a selection of a first audio preview interface object (e.g., an input on 1282-1, input 1285), the computer system outputs (e.g., uses) third audio data (e.g., audio represented by waveform 1260-5) (e.g., a preview of the output audio) based on a set of recommended audio characteristics (e.g., the preview of the output audio includes recommended audio adjustments and the preview of the output audio has customized audio settings applied thereto) (in some embodiments, if an output has already occurred 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 a determination that the one or more third sets of inputs include a selection of a second audio preview interface object (e.g., 1283), the computer system outputs third audio data based on (uses) a fifth set of audio characteristics (e.g., audio represented by waveform 1260-6) (e.g., the preview of the output audio does not include recommended audio adjustments and the preview of the output audio has standard audio settings applied thereto) (in some embodiments, if an output has already occurred based on the fifth set of audio characteristics, the output continues). Outputting third audio data based on a set of recommended audio characteristics or a fifth set of audio characteristics in response to a selection of a first or second audio preview interface object enables the user to compare audio settings based on a recommended set of audio settings or a fifth set without accepting, rejecting, or changing the audio settings in order to compare the playback of audio with different characteristics, thereby reducing the number of inputs required to set the audio settings.Reducing the number of inputs required to perform an operation enhances the device's operability, makes the user-device interface more efficient (e.g., by assisting the user in making appropriate inputs when operating the device / interacting with the device and reducing user errors), and in addition, by enabling the user to use the device more quickly and efficiently, the device's power consumption is reduced and the battery life is improved. In some embodiments, the recommended audio adjustment interface enables the user to preview output audio having enabled / disabled recommended / customized audio settings. In some embodiments, the recommended audio adjustment interface further includes a recommendation interface object that, when selected, sets a set of recommended audio characteristics as a set of audio characteristics for playback after 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 characteristics as a set of audio characteristics for playback after 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 as to whether audio adjustment is recommended or not required (e.g., the fifth set of audio characteristics is 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, ...

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 a determination that the second noise level exceeds the threshold noise level; maintaining a 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 in a third size based on the third noise level data, the third size being less than the second size; The method of claim 1 further comprising:

3. the graphical object varies 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 a determination 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. The method of any one of claims 1 to 4, wherein the electronic device comprises 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 a determination that a set of noise notification criteria are satisfied at a first time prior to displaying the first user interface, the noise notification criteria including 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; and 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 point in time.

9. The noise level notification further includes a fourth affordance associated with a second predetermined time period, the method further comprising: Receiving an input corresponding to the fourth affordance; and 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. 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 including instructions for performing the method of any one of claims 1 to 10.

12. A display device; 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 according to any one of claims 1 to 10; 2. An electronic device comprising:

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 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 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 a determination that the second noise level exceeds the threshold noise level; 11. A non-transitory computer-readable storage medium comprising instructions for: maintaining a 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: and 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 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 a determination that the second noise level exceeds the threshold noise level; maintain a 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.

16. 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, in response to receiving the first noise level data, the graphical object having an active portion of a first size based on the first noise data in a first color; means for 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; 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 a determination that the second noise level exceeds the threshold noise level; means for maintaining the display of the graphical object in the first color in response to 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, via the display device, a first user interface, 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; and 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.

20. 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. A method according to any one of claims 17 to 18, wherein the second noise level data corresponds to noise level data attributable to a single device.

20. A method according to 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, while displaying the first user interface, a user input corresponding to a selection of the second device type filtering affordance; 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 indicating 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. A method according to 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 including 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; 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 according to any one of claims 17 to 25; 2. An electronic device comprising:

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, via the display device, a first user interface, 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; and 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: and 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, via the display device, a first user interface, 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; and 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.

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; means for receiving 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; and 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; and 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 generating 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, the output of the first audio data is based on at least one audio characteristic of the first set of audio characteristics according to the first audio sample recorded as the preferred sample; outputting the first audio data according to 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; A method comprising:

33. after recording a selection of the first audio sample as a preferred sample or after recording a 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 comprises displaying a selectable volume control user interface object configured to adjust a volume of audio that is output while the selectable volume control user interface object is displayed; The method according to 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 play 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, either as part of the first audio sample or as part of the second audio sample, at a first point in time in the playback time of the second audio data; 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 response to a determination that the second audio data is being output as part of the first audio sample and in response to a determination that the set of one or more user inputs includes a selection of the representation of the second audio sample, 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 response to a determination 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 a determination 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 being 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 a determination 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; configuring one or more audio characteristics of audio playback of a second type of audio different from the first type of audio without configuring one or more audio characteristics of audio playback of the first type of audio in accordance with a determination that the set of one or more inputs including an 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 including instructions for performing the method of any one of claims 32 to 39.

41. a display generating 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 generating 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 generating 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 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 a selection of the first audio sample as a preferred sample or a selection of the second audio sample as a preferred sample; outputting first audio data via the audio generation component, the output of the first audio data is based on at least one audio characteristic of the first set of audio characteristics according to the first audio sample recorded as the preferred sample; 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 generating 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 the one or more processors, the one or more programs comprising: via said display generating 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, the output of the first audio data is based on at least one audio characteristic of the first set of audio characteristics according to the first audio sample recorded as the preferred sample; 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 generating component; an audio generation component; one or more input devices; A computer system comprising: via said display generating 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 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 a set of one or more user inputs via the one or more input devices; After receiving the set of one or more inputs, means for recording a selection of said first audio samples as a preferred sample or a selection of said second audio samples as a preferred sample; a means for outputting first audio data via the audio generation component, the means comprising: the output of the first audio data is based on at least one audio characteristic of the first set of audio characteristics according to the first audio sample recorded as the preferred sample; and means 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.

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 at a first volume of audio data 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 an 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 an 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 the 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, an output of an audible indication that the volume of output of audio data has been reduced; 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; 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 limiting control includes an affordance that, when selected, toggles a state of a process for reducing a 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 a headphone.

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 including an audio input device, the method further comprising:

60. The method of claim 59, further 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 an audio generation component of the first type; 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 the second type of audio generating component in response to a determination that the second audio generating component has not been identified as the second type of audio generating component; 60. The method of claim 59, further comprising:

63. the audio exposure threshold criterion includes a criterion that is 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 according to any one of claims 46 to 62.

64. receiving an input corresponding to a request to increase the volume of output of audio data while causing 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; 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: 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 indicating 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 response to 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; and displaying the audio exposure indicator having a third color distinct 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 to 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. 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 a method according to 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: A computer system comprising: means for executing the method according to 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 the first volume of audio data via the audio generation component; in response to detecting that the audio exposure threshold criterion has been met; 11. A non-transitory computer-readable storage medium 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.

72. 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 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 the first volume of audio data via the audio generation component; in response to detecting that the audio exposure threshold criterion has been met; 11. 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 generating 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 a first volume of audio data 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. pursuant to 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 includes a display generating component and one or more input devices, and the method further comprises: displaying via the display generation component a volume control interface object representing a threshold range for the output audio volume threshold; detecting an input via the one or more input devices corresponding to the volume control interface object; 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 a determination 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 textual 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; and 77. The method of claim 76, further comprising:

78. The first set of criteria further includes a first criterion that is satisfied when a volume control setting is enabled, the method further comprising: 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 being 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, A method according to any one of claims 74 to 78, comprising 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 any 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 external computer system; 81. The method according to 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 being a first value and the output audio data satisfying 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; and 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; in response to receiving the 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; 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. 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 a method according to 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 including 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: A computer system comprising: means for executing the method according to 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; and 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; 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; and means for causing output of the second audio signal at the second predicted output audio volume.

Images