SYSTEMS, METHOD AND USER INTERFACES FOR HEADPHONE SETUP AND AUDIO OUTPUT CONTROL

Description

TECHNICAL FIELD

[0001] This relates generally to audio output devices such as wearable audio output devices, including but not limited to wearable audio output devices where the fit of the wearable audio output devices in a user's ears is adjustable, and where audio output control can be performed using inputs at the wearable audio output devices.BACKGROUND

[0002] Audio output devices, including wearable audio output devices such as earbuds and earphones, are widely used to provide audio outputs to a user. But conventional methods of providing audio outputs using audio output devices are cumbersome, inefficient, and limited. In some cases, conventional methods fail to ensure that wearable audio output devices are properly calibrated and fitted to a user's ears (e.g., so as to enable effective active noise control) and that information about the fit of the wearable audio output devices is effectively conveyed to the user. In some cases, conventional methods fail to ensure that the wearable audio output devices continue to be fitted to the user's ears as the user performs various activities over time. In some cases, limited control over audio outputs is given to inputs provided at the wearable audio output devices; for example, an input may be limited to having control over a single predefined feature of audio output, such as increasing output volume or toggling a feature on or off. In some cases, this limited control over audio outputs interferes with a user's ability to control the amount of sound that the user is able to hear from the surrounding physical environment while wearing the earbuds or earphones. In other cases, the control over audio outputs given to inputs provided at the wearable audio output devices results in undesired acoustic effects when the wearable audio output devices are not placed in both ears. Moreover, in some cases, it would be beneficial to automatically change the manner in which audio outputs are provided in response to certain types of events occurring relative to the wearable audio output devices, but conventional methods provide audio outputs in a static manner irrespective of events occurring relative to the wearable audio output devices. In some cases, user interfaces for controlling audio output settings provide too few controls, for example by providing controls for only one audio output device, thus requiring a user to provide numerous inputs and navigate through different menus or user interfaces to perform a particular operation, or provide too many controls, thus cluttering the user interface and increasing the likelihood that the user will mistakenly interact with the wrong control, particularly for implementations where display area is limited. In addition, conventional methods take longer and require more user interaction than necessary to calibrate the wearable audio output devices and control audio outputs, thereby wasting energy. This latter consideration is particularly important in battery-operated devices.

[0003] US 2014 / 016803 A1 describes an electronic device coupled to an accessory such as a pair of earphones, where the earphones have ear presence sensor structures that determine whether or not the ears of a user are present in the vicinity of the earphones, and the earphones contain first and second speakers. When both the first and second speakers are located in the ears of the user, the electronic device may perform functions such as playing audio content. When one of the speakers has been removed from the ears of the user while the other of the speakers remains in the ears of the user, the electronic device can take actions such as pausing the playback of audio content, switching from stereo to monophonic playback, or stopping the playback of content. Suitable actions such as increasing audio drive strength may be taken when both speakers have been removed from the ears. US 2017 / 150246 A1 describes an earpiece including a feed-forward microphone coupled to the environment outside the headphones, a feedback microphone coupled to an ear canal of a user when the earpiece is in use, a speaker coupled to the ear canal of the user when the earpiece is in use, a digital signal processor implementing feed-forward and feedback noise compensation filters between the respective microphones and the speaker, and a memory storing an ordered sequence of sets of filters for use by the digital signal processor. US 2014 / 126733 A1 describes an active noise reducing headphone that has an active noise-cancelling mode and an active hear-through mode, and changes between the noise-cancelling mode and the hear-through mode based on detection of a user touching a housing of the headphone or based on a command signal received from an external device. The headphone may be configured to activate the hear-through mode whenever music playback is paused.SUMMARY

[0004] Accordingly, there is a need for wearable audio output devices and associated computer systems with improved methods and interfaces for determining and adjusting the fit of the wearable audio output devices and for controlling audio outputs using inputs at the wearable audio output devices. Such methods and interfaces optionally complement or replace conventional methods of calibrating audio output devices and controlling audio outputs. Such methods and interfaces reduce the number, extent, and / or nature of the inputs from a user and produce a more efficient human-machine interface. For battery-operated systems and devices, such methods and interfaces conserve power and increase the time between battery charges.

[0005] The above deficiencies and other problems associated with calibrating audio output devices and controlling audio outputs are reduced or eliminated by the disclosed computer systems and wearable audio output devices. In some embodiments, the computer system includes a desktop computer. In some embodiments, the computer system is portable (e.g., a notebook computer, tablet computer, or handheld device). In some embodiments, the computer system includes a personal electronic device (e.g., a wearable electronic device, such as a watch). In some embodiments, the computer system includes (and / or is in communication with) the wearable audio output devices (e.g., in-ear earphones, earbuds, over-ear headphones, etc.). In some embodiments, the computer system has (and / or is in communication with) a touch-sensitive surface (also known as a "touchpad"). In some embodiments, the computer system has (and / or is in communication with) a display device, which in some embodiments is a touch-sensitive display (also known as a "touch screen" or "touch-screen display"). In some embodiments, the computer system has a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through stylus and / or finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functions optionally include image editing, drawing, presenting, word processing, spreadsheet making, game playing, telephoning, video conferencing, e-mailing, instant messaging, workout support, digital photographing, digital videoing, web browsing, audio output device pairing and calibration, digital music / audio playing, note taking, and / or digital video playing. Executable instructions for performing these functions are, optionally, included in a non-transitory computer readable storage medium or other computer program product configured for execution by one or more processors.

[0006] In accordance with some embodiments, a method is performed at a computer system that includes a display device and a touch-sensitive surface. The method includes establishing a wireless connection with a pair of wearable audio output devices that includes: a first wearable audio output device with one or more first microphones; and a second wearable audio output device with one or more second microphones. The method includes detecting that the first wearable audio output device has been placed in an ear of a user; and detecting that the second wearable audio output device has been placed in an ear of the user. The method includes, after detecting that the first wearable audio output device has been placed in an ear of the user and that the second wearable audio output device has been placed in an ear of the user: outputting a first calibration tone via the first wearable audio output device and the second wearable audio output device; detecting first audio via the one or more first microphones of the first wearable audio output device; and detecting second audio via the one or more second microphones of the second wearable audio output device. The method includes, in accordance with a determination that the detected first audio does not satisfy device fit criteria associated with the first calibration tone, displaying, via the display device, an alert prompting the user to perform an adjustment of the first wearable audio output device; and, in accordance with a determination that the detected second audio does not satisfy the device fit criteria associated with the first calibration tone, displaying, via the display device, an alert prompting the user to perform an adjustment of the second wearable audio output device.

[0007] In accordance with some embodiments, a method is performed at a computer system that includes a display device and that is in communication with one or more wearable audio output devices. The computer system is configured to execute a plurality of applications, and the one or more wearable audio output devices include one or more sensors for detecting placement of the one or more wearable audio output devices and one or more microphones. The method includes, while the one or more wearable audio output devices are in one or more respective positions relative to a user's ears, and while a media presentation application on the computer system is being used to play media via the one or more wearable audio output devices without displaying a settings user interface for configuring a fit of the one or more wearable audio output devices: providing, via the one or more wearable audio output devices, audio output based on media from the media presentation application, wherein the media presentation application is separate from the settings user interface; determining, based on the audio output based on the media from the media presentation application, that the one or more wearable audio output devices have ceased to satisfy device fit criteria; and, in response to determining that the one or more wearable audio output devices have ceased to satisfy the device fit criteria, displaying, on the display device, an alert corresponding to information about a fit of the one or more wearable audio output devices.

[0008] In accordance with some embodiments, a method is performed at a wearable audio output device that includes an input device and one or more microphones and that is in a physical environment. The method includes, while ambient sound from the physical environment is being detected by the one or more microphones: while the wearable audio output device is in a first audio output mode, providing a first audio output based at least in part on the ambient sound from the physical environment, wherein the first audio output includes one or more pass-through audio components selected so as to increase audio pass-through of the ambient sound from the physical environment; detecting a first input via the input device, and in response to detecting the first input, and in accordance with a determination that the first input is a first type of gesture, transitioning the wearable audio output device from the first audio output mode to a second audio output mode. The method includes, while the wearable audio output device is in the second audio output mode, providing a second audio output based at least in part on the ambient sound from the physical environment, wherein the second audio output includes one or more cancellation audio components selected so as to increase audio cancellation of the ambient sound from the physical environment.

[0009] In accordance with some embodiments, a method is performed at a computer system that includes a wearable audio output device, where the wearable audio output device is in a physical environment, and one or more input devices. The method includes operating the wearable audio output device in a first audio output mode; and while operating the wearable audio output device in the first audio output mode, receiving, via the one or more input devices, a first input corresponding to a request to transition the wearable audio output device from the first audio output mode to a noise-cancellation mode. While the wearable audio output device is in the noise-cancellation mode, audio outputs that are provided via the wearable audio output device include one or more cancellation audio components selected so as to at least partially cancel ambient sound from the physical environment. The method includes, in response to receiving the first input: in accordance with a determination that a first wearable audio output component of the wearable audio output device is in an in-ear position relative to a first ear of a user and that a second wearable audio output component of the wearable audio output device is in an in-ear position relative to a second ear of the user, transitioning the wearable audio output device from the first audio output mode to the noise-cancellation mode; and in accordance with a determination that one of the first wearable audio output component or the second wearable audio output component is not in an in-ear position relative to a respective ear of the user, forgoing transitioning the wearable audio output device from the first audio output mode to the noise-cancellation mode.

[0010] In accordance with some embodiments, a method is performed at a computer system that includes a wearable audio output device in a physical environment. The method includes, while a first wearable audio output component of the wearable audio output device is in a first position relative to a first ear of a user and a second wearable audio output component of the wearable audio output device is in the first position relative to a second ear of the user, operating the wearable audio output device in a first audio output mode, and, while operating the wearable audio output device in the first audio output mode, detecting a change in position of the first wearable audio output component from the first position relative to the first ear of the user to a second position relative to the first ear of the user. The method includes, in response to detecting the change in position of the first wearable audio output component from the first position relative to the first ear of the user to the second position relative to the first ear of the user, while the second wearable audio output component is maintained in the first position relative to the second ear of the user: transitioning the wearable audio output device from the first audio output mode to a second audio output mode that is a pass-through audio output mode that is different from the first audio output mode. While the wearable audio output device is in the pass-through audio output mode, audio outputs that are provided via the wearable audio output device include one or more pass-through audio components that include at least a portion of ambient sound from the physical environment.

[0011] In accordance with some embodiments, a method is performed at a computer system that includes a display device and a wearable audio output device. The wearable audio output device includes a first wearable audio output component and a second wearable audio output component. The method includes detecting an occurrence of a respective event; and, in response to detecting the occurrence of the respective event, in accordance with a determination that the first wearable audio output component is at least partially in a first ear of the user and that the second wearable audio output component is at least partially in a second ear of the user, displaying acoustic seal information for the wearable audio output device, including concurrently displaying, via the display device: a first indication of a quality of a first acoustic seal between the first wearable audio output component and the first ear of the user; and a second indication, distinct from the first indication, of a quality of a second acoustic seal between the second wearable audio output component and the second ear of the user.

[0012] In accordance with some embodiments, a method is performed at a computer system that includes a display device and that is in communication with one or more sets of wearable audio output devices. The method includes receiving a first input that corresponds to a request to display an audio output settings user interface; and, in response to receiving the first input, displaying the audio output settings user interface. In accordance with a determination that the computer system is in communication with at least a first set of one or more wearable audio output devices and a second set of one or more wearable audio output devices, the audio output settings user interface includes: a first set of audio output controls corresponding to the first set of wearable audio output devices, including a first volume control indicating a current output volume level of the first set of wearable audio output devices, and a representation of a first audio output mode that is a current audio output mode of a first plurality of audio output modes available at the first set of wearable audio output devices, where the representation of the first audio output mode is visually associated with the first volume control; and a second set of audio output controls corresponding to the second set of wearable audio output devices, including a second volume control indicating a current output volume level of the second set of wearable audio output devices.

[0013] In accordance with some embodiments, a method is performed at a wearable audio output device with a rotatable input mechanism. The method includes outputting, via the wearable audio output device, first audio that is based on first media. The method includes, while outputting the first audio, receiving a first input via the rotatable input mechanism. The method includes, in response to receiving the first input: in accordance with a determination that the first input is a first type of input to the rotatable input mechanism that includes rotation of the rotatable input mechanism, changing an audio output volume of the first audio based on the rotation of the rotatable input mechanism while continuing to output the first audio; and, in accordance with a determination that the first input is a second type of input to the rotatable input mechanism, where the second type of input is different from the first type of input, ceasing to output the first audio.

[0014] In accordance with some embodiments, a computer system includes or is in communication with one or more wearable audio output devices, a display device, optionally a touch-sensitive surface, one or more processors, and memory storing one or more programs; the one or more programs are configured to be executed by the one or more processors and the one or more programs include instructions for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, a computer readable storage medium has stored therein instructions that, when executed by a computer system as described herein, cause the computer system to perform or cause performance of the operations of any of the methods described herein. In accordance with some embodiments, a graphical user interface (e.g., on an electronic device) in a computer system as described herein includes one or more of the elements displayed in any of the methods described herein, which are updated in response to inputs, as described in any of the methods described herein. In accordance with some embodiments, a computer system as described herein includes means for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, an information processing apparatus, for use in a computer system as described herein, includes means for performing or causing performance of the operations of any of the methods described herein.

[0015] In accordance with some embodiments, a wearable audio output device as described herein includes one or more microphones, optionally an input device (e.g., which may be pressure-sensitive and / or touch-sensitive), optionally one or more attachments (e.g., in-ear eartips), optionally one or more sensors for detecting placement of the wearable audio output device, one or more processors, and memory storing one or more programs; the one or more programs are configured to be executed by the one or more processors and the one or more programs include instructions for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, a computer readable storage medium has stored therein instructions that, when executed by a wearable audio output device as described herein, cause the wearable audio output device to perform or cause performance of the operations of any of the methods described herein. In accordance with some embodiments, a wearable audio output device as described herein includes means for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, an information processing apparatus, for use in a wearable audio output device as described herein, includes means for performing or causing performance of the operations of any of the methods described herein.

[0016] Thus, computer systems that include or are in communication with one or more wearable audio output devices, a display device, and optionally a touch-sensitive surface, and wearable audio output devices that include one or more microphones, optionally an input device (e.g., which may be pressure-sensitive and / or touch-sensitive), optionally one or more attachments (e.g., in-ear eartips), and optionally one or more sensors for detecting placement of the wearable audio output device, are provided with improved methods and interfaces for adjusting the fit of the wearable audio output devices and for controlling audio outputs using inputs at the wearable audio output devices, thereby increasing the effectiveness, efficiency, and user satisfaction with such systems and devices. Such methods and interfaces may complement or replace conventional methods for calibrating audio output devices and controlling audio outputs.

[0017] The invention is set out in the appended set of claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0018] For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures. Figure 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments. Figure 1B is a block diagram illustrating example components for event handling in accordance with some embodiments. Figure 2 illustrates a portable multifunction device having a touch screen in accordance with some embodiments. Figure 3A is a block diagram of an example multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. Figure 3B is a block diagram of an example wearable audio output device in accordance with some embodiments. Figures 3C-3D illustrate example audio control by a wearable audio output device in accordance with some embodiments. Figure 4A illustrates an example user interface for a menu of applications on a portable multifunction device in accordance with some embodiments. Figure 4B illustrates an example user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments. Figures 5A-5V illustrate example user interfaces for pairing and calibrating wearable audio output devices in accordance with some embodiments. Figures 6A-6O illustrate example user interfaces for alerting a user when wearable audio output devices no longer satisfy fit criteria during use in accordance with some embodiments. Figures 7A-7Q illustrate example user interfaces and user interactions for changing the audio output mode of a wearable audio output device in accordance with some embodiments. Figures 8A-8J illustrate example user interactions with wearable audio output devices to control audio outputs in accordance with some embodiments. Figures 9A-9C illustrate an example settings user interface for controlling various features associated with wearable audio output devices and examples of controlling audio output mode in accordance with some embodiments. Figures 10A-10H are flow diagrams of a process for pairing and calibrating wearable audio output devices in accordance with some embodiments. Figures 11A-11D are flow diagrams of a process for monitoring the fit of wearable audio output devices during use in accordance with some embodiments. Figures 12A-12E are flow diagrams of a process for controlling audio outputs using inputs at a wearable audio output device in accordance with some embodiments. Figures 13A-13D illustrate example user interfaces for pairing wearable audio output devices in accordance with some embodiments. Figures 14A-14Z illustrate example user interfaces and user interactions for changing the audio output mode of wearable audio output devices in accordance with some embodiments. Figures 15A-15E illustrate an example settings user interface for controlling various features associated with wearable audio output devices and examples of controlling audio output mode in accordance with some embodiments. Figures 16A-16G illustrate example user interfaces for calibrating and displaying information about acoustic seal quality of wearable audio output devices in accordance with some embodiments. Figures 17A-17J illustrate example user interfaces and user interactions for selecting an audio output device, such as a wearable audio output device, and changing the audio output mode of the selected audio output device via a wearable electronic device in accordance with some embodiments. Figures 18A-18H are flow diagrams of a process for controlling audio output mode of a wearable audio output device in accordance with some embodiments. Figures 19A-19C are flow diagrams of a process for transitioning audio output mode of a wearable audio output device in response to detected events in accordance with some embodiments. Figures 20A-20B are flow diagrams of a process for displaying information about acoustic seal quality of a wearable audio output device in accordance with some embodiments. Figures 21A-21J illustrate example user interfaces and user interactions for changing the audio output mode of wearable audio output devices in accordance with some embodiments. Figures 22A-22D illustrate example user interfaces and user interactions for accessing a settings user interface for controlling various features associated with wearable audio output devices in accordance with some embodiments. Figures 23A-23AA illustrate example user interfaces and user interactions for controlling audio output settings for multiple wearable audio output devices using a single settings user interface in accordance with some embodiments. Figures 24A-24D are flow diagrams of a process for controlling audio output settings for multiple wearable audio output devices using a single settings user interface in accordance with some embodiments. Figures 25A-25G illustrate example user interactions for controlling audio outputs from a wearable audio output device and example audio and visual alerts responsive to such user interactions in accordance with some embodiments. Figures 26A-26D are flow diagrams of a process for controlling audio outputs from a wearable audio output device in accordance with some embodiments. DESCRIPTION OF EMBODIMENTS

[0019] As noted above, audio output devices such as wearable audio output devices are widely used to provide audio outputs to a user. Many computer systems that include or are in communication with wearable audio output devices fail to ensure that the wearable audio output devices are properly calibrated and remain fitted to a user's ears, or give a user only limited control over audio outputs in response to inputs at the wearable audio output devices, or provide user interfaces with too few or too many audio output controls. The methods, systems, and user interfaces / interactions described herein improve how audio outputs are provided in multiple ways. For example, embodiments disclosed herein describe improved ways to determine and adjust the fit of the wearable audio output devices, to control audio outputs using inputs at the wearable audio output devices, and to provide improved user interfaces for controlling audio output settings.

[0020] Below, Figures 1A-1B, 2, and 3A-3D provide a description of example devices and examples of their operation. Figures 4A-4B illustrate example user interface for example devices on which the embodiments disclosed herein are implemented. Figures 5A-5V illustrate example user interfaces for pairing and calibrating wearable audio output devices. Figures 6A-6O illustrate example user interfaces for alerting a user when wearable audio output devices no longer satisfy fit criteria during use. Figures 7A-7Q illustrate example user interfaces and user interactions for changing the audio output mode of a wearable audio output device. Figures 8A-8J illustrate example user interactions with wearable audio output devices to control audio outputs. Figures 9A-9C illustrate an example settings user interface for controlling various features associated with wearable audio output devices and examples of controlling audio output mode. Figures 10A-10H are flow diagrams of a process for pairing and calibrating wearable audio output devices. Figures 11A-11D are flow diagrams of a process for monitoring the fit of wearable audio output devices during use. Figures 12A-12E are flow diagrams of a process for controlling audio outputs using inputs at a wearable audio output device. Figures 13A-13D illustrate example user interfaces for pairing wearable audio output devices. Figures 14A-14Z illustrate example user interfaces and user interactions for changing the audio output mode of wearable audio output devices. Figures 15A-15E illustrate an example settings user interface for controlling various features associated with wearable audio output devices and examples of controlling audio output mode. Figures 16A-16G illustrate example user interfaces for calibrating and displaying information about acoustic seal quality of wearable audio output devices. Figures 17A-17J illustrate example user interfaces and user interactions for selecting an audio output device, such as a wearable audio output device, and changing the audio output mode of the selected audio output device via (e.g., using) a wearable electronic device. Figures 21A-21J illustrate example user interfaces and user interactions for changing the audio output mode of wearable audio output devices. Figures 22A-22D illustrate example user interfaces and user interactions for accessing a settings user interface for controlling various features associated with wearable audio output devices. Figures 23A-23AA illustrate example user interfaces and user interactions for controlling audio output settings for multiple wearable audio output devices using a single settings user interface. Figures 25A-25G illustrate example user interactions for controlling audio outputs from a wearable audio output device and example audio and visual alerts responsive to such user interactions. The user interfaces and user interactions in Figures 5A-5V, 6A-6O, 7A-7Q, 8A-8J, 9A-9C, 13A-13D, 14A-14Z, 15A-15E, 16A-16G, 17A-17J, 21A-21J, 22A-22D, 23A-23AA, and 25A-25G are used to illustrate the processes in Figures 10A-10H, 11A-11D, 12A-12E, 18A-18H, 19A-19C, 20A-20B, 24A-24D, and 26A-26D.EXAMPLE DEVICES

[0021] Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various described embodiments. However, it will be apparent to one of ordinary skill in the art that the various described embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.

[0022] It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first audio output could be termed a second audio output, and, similarly, a second audio output could be termed a first audio output, without departing from the scope of the various described embodiments. The first audio output and the second audio output are both audio outputs, but they are not the same audio output, unless the context clearly indicates otherwise.

[0023] The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "includes," "including," "comprises," and / or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0024] As used herein, the term "if" is, optionally, construed to mean "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrase "if it is determined" or "if [a stated condition or event] is detected" is, optionally, construed to mean "upon determining" or "in response to determining" or "upon detecting [the stated condition or event]" or "in response to detecting [the stated condition or event]," depending on the context.

[0025] Embodiments of computer systems that include or are in communication with wearable audio output devices, user interfaces for such systems, and associated processes for using such systems and devices are described. In some embodiments, the computer system includes a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and / or music player functions. Example embodiments of portable multifunction devices include, without limitation, the iPhone ®< , iPod Touch ®< , and iPad ®< devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch-screen displays and / or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the computer system includes not a portable communications device, but a desktop computer with a touch-sensitive surface (e.g., a touch-screen display and / or a touchpad).

[0026] In the discussion that follows, a computer system that includes an electronic device with a display device and a touch-sensitive surface is described. It should be understood, however, that the computer system optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse and / or a joystick.

[0027] The computer system typically supports a variety of applications, such as one or more of the following: a note taking application, a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and / or a digital video player application.

[0028] The various applications that are executed on the computer system optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the computer system are, optionally, adjusted and / or varied from one application to the next and / or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the computer system optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.

[0029] Attention is now directed toward embodiments of portable devices with touch-sensitive displays. Figure 1A is a block diagram illustrating portable multifunction device 100 with touch-sensitive display system 112 in accordance with some embodiments. Touch-sensitive display system 112 is sometimes called a "touch screen" for convenience, and is sometimes simply called a touch-sensitive display. Device 100 includes memory 102 (which optionally includes one or more computer readable storage mediums), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input / output (I / O) subsystem 106, other input or control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more intensity sensors 165 for detecting intensities of contacts on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile outputs on device 100 (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.

[0030] As used in the specification and claims, the term "tactile output" refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a "down click" or "up click" of a physical actuator button. In some cases, a user will feel a tactile sensation such as an "down click" or "up click" even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as "roughness" of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an "up click," a "down click," "roughness"), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user. Using tactile outputs to provide haptic feedback to a user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating / interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0031] In some embodiments, a tactile output pattern specifies characteristics of a tactile output, such as the amplitude of the tactile output, the shape of a movement waveform of the tactile output, the frequency of the tactile output, and / or the duration of the tactile output.

[0032] When tactile outputs with different tactile output patterns are generated by a device (e.g., via one or more tactile output generators that move a moveable mass to generate tactile outputs), the tactile outputs may invoke different haptic sensations in a user holding or touching the device. While the sensation of the user is based on the user's perception of the tactile output, most users will be able to identify changes in waveform, frequency, and amplitude of tactile outputs generated by the device. Thus, the waveform, frequency and amplitude can be adjusted to indicate to the user that different operations have been performed. As such, tactile outputs with tactile output patterns that are designed, selected, and / or engineered to simulate characteristics (e.g., size, material, weight, stiffness, smoothness, etc.); behaviors (e.g., oscillation, displacement, acceleration, rotation, expansion, etc.); and / or interactions (e.g., collision, adhesion, repulsion, attraction, friction, etc.) of objects in a given environment (e.g., a user interface that includes graphical features and objects, a simulated physical environment with virtual boundaries and virtual objects, a real physical environment with physical boundaries and physical objects, and / or a combination of any of the above) will, in some circumstances, provide helpful feedback to users that reduces input errors and increases the efficiency of the user's operation of the device. Additionally, tactile outputs are, optionally, generated to correspond to feedback that is unrelated to a simulated physical characteristic, such as an input threshold or a selection of an object. Such tactile outputs will, in some circumstances, provide helpful feedback to users that reduces input errors and increases the efficiency of the user's operation of the device.

[0033] In some embodiments, a tactile output with a suitable tactile output pattern serves as a cue for the occurrence of an event of interest in a user interface or behind the scenes in a device. Examples of the events of interest include activation of an affordance (e.g., a real or virtual button, or toggle switch) provided on the device or in a user interface, success or failure of a requested operation, reaching or crossing a boundary in a user interface, entry into a new state, switching of input focus between objects, activation of a new mode, reaching or crossing an input threshold, detection or recognition of a type of input or gesture, etc. In some embodiments, tactile outputs are provided to serve as a warning or an alert for an impending event or outcome that would occur unless a redirection or interruption input is timely detected. Tactile outputs are also used in other contexts to enrich the user experience, improve the accessibility of the device to users with visual or motor difficulties or other accessibility needs, and / or improve efficiency and functionality of the user interface and / or the device. Tactile outputs are optionally accompanied with audio outputs and / or visible user interface changes, which further enhance a user's experience when the user interacts with a user interface and / or the device, and facilitate better conveyance of information regarding the state of the user interface and / or the device, and which reduce input errors and increase the efficiency of the user's operation of the device.

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

[0035] Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100, such as CPU(s) 120 and the peripherals interface 118, is, optionally, controlled by memory controller 122.

[0036] Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU(s) 120 and memory 102. The one or more processors 120 run or execute various software programs and / or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data.

[0037] In some embodiments, peripherals interface 118, CPU(s) 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.

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

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

[0040] I / O subsystem 106 couples input / output peripherals on device 100, such as touch-sensitive display system 112 and other input or control devices 116, with peripherals interface 118. I / O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / send electrical signals from / to other input or control devices 116. The other input or control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled with any (or none) of the following: a keyboard, infrared port, USB port, stylus, and / or a pointer device such as a mouse. The one or more buttons (e.g., 208, Figure 2) optionally include an up / down button (e.g., or an up button and a separate down button) for volume control of speaker 111 and / or microphone 113. The one or more buttons optionally include a push button (e.g., 206, Figure 2).

[0041] Touch-sensitive display system 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and / or sends electrical signals from / to touch-sensitive display system 112. In some embodiments, touch-sensitive display system 112 or display controller 156, or a combination of touch-sensitive display 112 and display controller 156, are referred to as a display generation component of device 100. Touch-sensitive display system 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed "graphics"). In some embodiments, some or all of the visual output corresponds to user interface objects. As used herein, the term "affordance" refers to a user-interactive graphical user interface object (e.g., a graphical user interface object that is configured to respond to inputs directed toward the graphical user interface object). Examples of user-interactive graphical user interface objects include, without limitation, a button, slider, icon, selectable menu item, switch, hyperlink, or other user interface control.

[0042] Touch-sensitive display system 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and / or tactile contact. Touch-sensitive display system 112 and display controller 156 (along with any associated modules and / or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch-sensitive display system 112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on touch-sensitive display system 112. In some embodiments, a point of contact between touch-sensitive display system 112 and the user corresponds to a finger of the user or a stylus.

[0043] Touch-sensitive display system 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch-sensitive display system 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch-sensitive display system 112. In some embodiments, projected mutual capacitance sensing technology is used, such as that found in the iPhone ®< , iPod Touch ®< , and iPad ®< from Apple Inc. of Cupertino, California.

[0044] Touch-sensitive display system 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen video resolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater). The user optionally makes contact with touch-sensitive display system 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer / cursor position or command for performing the actions desired by the user.

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

[0046] Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.

[0047] Device 100 optionally also includes one or more optical sensors 164. Figure 1A shows an optical sensor coupled with optical sensor controller 158 in I / O subsystem 106. Optical sensor(s) 164 optionally include charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor(s) 164 receive light from the environment, projected through one or more lens, and converts the light to data representing an image. In conjunction with imaging module 143 (also called a camera module), optical sensor(s) 164 optionally capture still images and / or video. In some embodiments, an optical sensor is located on the back of device 100, opposite touch-sensitive display system 112 on the front of the device, so that the touch screen is enabled for use as a viewfinder for still and / or video image acquisition. In some embodiments, another optical sensor is located on the front of the device so that the user's image is obtained (e.g., for selfies, for videoconferencing while the user views the other video conference participants on the touch screen, etc.).

[0048] Device 100 optionally also includes one or more contact intensity sensors 165. Figure 1A shows a contact intensity sensor coupled with intensity sensor controller 159 in I / O subsystem 106. Contact intensity sensor(s) 165 optionally include one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor(s) 165 receive 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 collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touch-screen display system 112 which is located on the front of device 100.

[0049] Device 100 optionally also includes one or more proximity sensors 166. Figure 1A shows proximity sensor 166 coupled with peripherals interface 118. Alternately, proximity sensor 166 is coupled with input controller 160 in I / O subsystem 106. In some embodiments, the proximity sensor turns off and disables touch-sensitive display system 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

[0050] Device 100 optionally also includes one or more tactile output generators 167. Figure 1A shows a tactile output generator coupled with haptic feedback controller 161 in I / O subsystem 106. In some embodiments, tactile output generator(s) 167 include one or more electroacoustic devices such as speakers or other audio components and / or electromechanical devices that convert energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts electrical signals into tactile outputs on the device). Tactile output generator(s) 167 receive tactile feedback generation instructions from haptic feedback module 133 and generates tactile outputs on device 100 that are capable of being sensed by a user of device 100. In some embodiments, at least one tactile output generator is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 112) and, optionally, generates a tactile output by moving the touch-sensitive surface vertically (e.g., in / out of a surface of device 100) or laterally (e.g., back and forth in the same plane as a surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touch-sensitive display system 112, which is located on the front of device 100.

[0051] Device 100 optionally also includes one or more accelerometers 168. Figure 1A shows accelerometer 168 coupled with peripherals interface 118. Alternately, accelerometer 168 is, optionally, coupled with an input controller 160 in I / O subsystem 106. In some embodiments, information is displayed on the touch-screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. Device 100 optionally includes, in addition to accelerometer(s) 168, a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device 100.

[0052] In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact / motion module (or set of instructions) 130, graphics module (or set of instructions) 132, haptic feedback module (or set of instructions) 133, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 stores device / global internal state 157, as shown in Figures 1A and 3. Device / global internal state 157 includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch-sensitive display system 112; sensor state, including information obtained from the device's various sensors and other input or control devices 116; and location and / or positional information concerning the device's location and / or attitude.

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

[0054] Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and / or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and / or compatible with the 30-pin connector used in some iPhone ®< , iPod Touch ®< , and iPad ®< devices from Apple Inc. of Cupertino, California. In some embodiments, the external port is a Lightning connector that is the same as, or similar to and / or compatible with the Lightning connector used in some iPhone ®< , iPod Touch ®< , and iPad ®< devices from Apple Inc. of Cupertino, California.

[0055] Contact / motion module 130 optionally detects contact with touch-sensitive display system 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact / motion module 130 includes various software components for performing various operations related to detection of contact (e.g., by a finger or by a stylus), such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact / motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and / or an acceleration (a change in magnitude and / or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts or stylus contacts) or to multiple simultaneous contacts (e.g., "multitouch" / multiple finger contacts). In some embodiments, contact / motion module 130 and display controller 156 detect contact on a touchpad.

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

[0057] In some embodiments, detecting a finger tap gesture depends on the length of time between detecting the finger-down event and the finger-up event, but is independent of the intensity of the finger contact between detecting the finger-down event and the finger-up event. In some embodiments, a tap gesture is detected in accordance with a determination that the length of time between the finger-down event and the finger-up event is less than a predetermined value (e.g., less than 0.1, 0.2, 0.3, 0.4 or 0.5 seconds), independent of whether the intensity of the finger contact during the tap meets a given intensity threshold (greater than a nominal contact-detection intensity threshold), such as a light press or deep press intensity threshold. Thus, a finger tap gesture can satisfy particular input criteria that do not require that the characteristic intensity of a contact satisfy a given intensity threshold in order for the particular input criteria to be met. For clarity, the finger contact in a tap gesture typically needs to satisfy a nominal contact-detection intensity threshold, below which the contact is not detected, in order for the finger-down event to be detected. A similar analysis applies to detecting a tap gesture by a stylus or other contact. In cases where the device is capable of detecting a finger or stylus contact hovering over a touch sensitive surface, the nominal contact-detection intensity threshold optionally does not correspond to physical contact between the finger or stylus and the touch sensitive surface.

[0058] The same concepts apply in an analogous manner to other types of gestures. For example, a swipe gesture, a pinch gesture, a depinch gesture, and / or a long press gesture are optionally detected based on the satisfaction of criteria that are either independent of intensities of contacts included in the gesture, or do not require that contact(s) that perform the gesture reach intensity thresholds in order to be recognized. For example., a swipe gesture is detected based on an amount of movement of one or more contacts; a pinch gesture is detected based on movement of two or more contacts towards each other; a depinch gesture is detected based on movement of two or more contacts away from each other; and a long press gesture is detected based on a duration of the contact on the touch-sensitive surface with less than a threshold amount of movement. As such, the statement that particular gesture recognition criteria do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met means that the particular gesture recognition criteria are capable of being satisfied if the contact(s) in the gesture do not reach the respective intensity threshold, and are also capable of being satisfied in circumstances where one or more of the contacts in the gesture do reach or exceed the respective intensity threshold. In some embodiments, a tap gesture is detected based on a determination that the finger-down and finger-up event are detected within a predefined time period, without regard to whether the contact is above or below the respective intensity threshold during the predefined time period, and a swipe gesture is detected based on a determination that the contact movement is greater than a predefined magnitude, even if the contact is above the respective intensity threshold at the end of the contact movement. Even in implementations where detection of a gesture is influenced by the intensity of contacts performing the gesture (e.g., the device detects a long press more quickly when the intensity of the contact is above an intensity threshold or delays detection of a tap input when the intensity of the contact is higher), the detection of those gestures does not require that the contacts reach a particular intensity threshold so long as the criteria for recognizing the gesture can be met in circumstances where the contact does not reach the particular intensity threshold (e.g., even if the amount of time that it takes to recognize the gesture changes).

[0059] Contact intensity thresholds, duration thresholds, and movement thresholds are, in some circumstances, combined in a variety of different combinations in order to create heuristics for distinguishing two or more different gestures directed to the same input element or region so that multiple different interactions with the same input element are enabled to provide a richer set of user interactions and responses. The statement that a particular set of gesture recognition criteria do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met does not preclude the concurrent evaluation of other intensity-dependent gesture recognition criteria to identify other gestures that do have a criteria that is met when a gesture includes a contact with an intensity above the respective intensity threshold. For example, in some circumstances, first gesture recognition criteria for a first gesture - which do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the first gesture recognition criteria to be met - are in competition with second gesture recognition criteria for a second gesture - which are dependent on the contact(s) reaching the respective intensity threshold. In such competitions, the gesture is, optionally, not recognized as meeting the first gesture recognition criteria for the first gesture if the second gesture recognition criteria for the second gesture are met first. For example, if a contact reaches the respective intensity threshold before the contact moves by a predefined amount of movement, a deep press gesture is detected rather than a swipe gesture. Conversely, if the contact moves by the predefined amount of movement before the contact reaches the respective intensity threshold, a swipe gesture is detected rather than a deep press gesture. Even in such circumstances, the first gesture recognition criteria for the first gesture still do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the first gesture recognition criteria to be met because if the contact stayed below the respective intensity threshold until an end of the gesture (e.g., a swipe gesture with a contact that does not increase to an intensity above the respective intensity threshold), the gesture would have been recognized by the first gesture recognition criteria as a swipe gesture. As such, particular gesture recognition criteria that do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met will (A) in some circumstances ignore the intensity of the contact with respect to the intensity threshold (e.g. for a tap gesture) and / or (B) in some circumstances still be dependent on the intensity of the contact with respect to the intensity threshold in the sense that the particular gesture recognition criteria (e.g., for a long press gesture) will fail if a competing set of intensity-dependent gesture recognition criteria (e.g., for a deep press gesture) recognize an input as corresponding to an intensity-dependent gesture before the particular gesture recognition criteria recognize a gesture corresponding to the input (e.g., for a long press gesture that is competing with a deep press gesture for recognition).

[0060] Graphics module 132 includes various known software components for rendering and displaying graphics on touch-sensitive display system 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast or other visual property) of graphics that are displayed. As used herein, the term "graphics" includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.

[0061] In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.

[0062] Haptic feedback module 133 includes various software components for generating instructions (e.g., instructions used by haptic feedback controller 161) to produce tactile outputs using tactile output generator(s) 167 at one or more locations on device 100 in response to user interactions with device 100.

[0063] Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).

[0064] GPS module 135 determines the location of the computer system and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing, to camera 143 as picture / video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map / navigation widgets).

[0065] Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof: contacts module 137 (sometimes called an address book or contact list); telephone module 138; video conferencing module 139; e-mail client module 140; instant messaging (IM) module 141; workout support module 142; camera module 143 for still and / or video images; image management module 144; browser module 147; calendar module 148; widget modules 149, which optionally include one or more of: weather widget 149-1, stocks 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 widgets 149-6; widget creator module 150 for making user-created widgets 149-6; search module 151; video and music player module 152, which is, optionally, made up of a video player module and a music player module; notes module 153; map module 154; and / or online video module 155.

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

[0067] In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 includes executable instructions to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers and / or e-mail addresses to initiate and / or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.

[0068] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 includes executable instructions to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in address book 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols and technologies.

[0069] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, videoconferencing module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.

[0070] In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.

[0071] In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, Apple Push Notification Service (APNs) or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and / or received instant messages optionally include graphics, photos, audio files, video files and / or other attachments as are supported in an MMS and / or an Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).

[0072] In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and video and music player module 152, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and / or calorie burning goals); communicate with workout sensors (in sports devices and smart watches); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store and transmit workout data.

[0073] In conjunction with touch-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, and / or delete a still image or video from memory 102.

[0074] In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and / or video images.

[0075] In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0076] In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.) in accordance with user instructions.

[0077] In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).

[0078] In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 includes executable instructions to create widgets (e.g., turning a user-specified portion of a web page into a widget).

[0079] In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and / or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

[0080] In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present or otherwise play back videos (e.g., on touch-sensitive display system 112, or on an external display connected wirelessly or via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).

[0081] In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to do lists, and the like in accordance with user instructions.

[0082] In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 includes executable instructions to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.

[0083] In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes executable instructions that allow the user to access, browse, receive (e.g., by streaming and / or download), play back (e.g., on the touch screen 112, or on an external display connected wirelessly or via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video.

[0084] Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.

[0085] In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and / or a touchpad. By using a touch screen and / or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.

[0086] The predefined set of functions that are performed exclusively through a touch screen and / or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a "menu button" is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.

[0087] Figure 1B is a block diagram illustrating example components for event handling in accordance with some embodiments. In some embodiments, memory 102 (in Figures 1A) or 370 (Figure 3) includes event sorter 170 (e.g., in operating system 126) and a respective application 136-1 (e.g., any of the aforementioned applications 136, 137-155, 380-390).

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

[0089] In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo / undo queue of previous actions taken by the user.

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

[0091] In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripheral interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and / or for more than a predetermined duration).

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

[0093] Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views, when touch-sensitive display system 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.

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

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

[0096] Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.

[0097] Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver module 182.

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

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

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

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

[0102] Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event 187 include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first lift-off (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second lift-off (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display system 112, and lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

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

[0104] In some embodiments, the definition for a respective event 187 also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.

[0105] When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.

[0106] In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and / or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.

[0107] In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.

[0108] In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.

[0109] In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video and music player module 152. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.

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

[0111] It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input-devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and / or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.

[0112] Figure 2 illustrates a portable multifunction device 100 having a touch screen (e.g., touch-sensitive display system 112, Figure 1A) in accordance with some embodiments. The touch screen optionally displays one or more graphics within user interface (UI) 200. In these embodiments, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and / or downward) and / or a rolling of a finger (from right to left, left to right, upward and / or downward) that has made contact with device 100. In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

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

[0114] In some embodiments, device 100 includes the touch-screen display, menu button 204 (sometimes called home button 204), push button 206 for powering the device on / off and locking the device, volume adjustment button(s) 208, Subscriber Identity Module (SIM) card slot 210, head set jack 212, and docking / charging external port 124. Push button 206 is, optionally, used to turn the power on / off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and / or to unlock the device or initiate an unlock process. In some embodiments, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensities of contacts on touch-sensitive display system 112 and / or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.

[0115] Figure 3A is a block diagram of an example multifunction device with a display and a touch-sensitive surface in accordance with 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 (CPU's) 310, one or more network or other communications interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. Communication buses 320 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device 300 includes input / output (I / O) interface 330 comprising display 340, which is typically a touch-screen display. In some embodiments, display 340 is referred to as a display generation component. I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350 and touchpad 355, tactile output generator 357 for generating tactile outputs on device 300 (e.g., similar to tactile output generator(s) 167 described above with reference to Figure 1A), sensors 359 (e.g., optical, acceleration, proximity, touch-sensitive, and / or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to Figure 1A). In some embodiments, device 300 includes a wireless interface 311 for communication with one or more wearable audio output devices 301.

[0116] 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 remotely located from CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (Figure 1A), or a subset thereof. Furthermore, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, word processing module 384, website creation module 386, disk authoring module 388, and / or spreadsheet module 390, while memory 102 of portable multifunction device 100 (Figure 1A) optionally does not store these modules.

[0117] Each of the above identified elements in Figure 3A are, optionally, stored in one or more of the previously mentioned memory devices. Each of the above identified modules corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 370 optionally stores additional modules and data structures not described above.

[0118] Figure 3B is a block diagram of an example wearable audio output device 301 in accordance with some embodiments. In some embodiments, wearable audio output device 301 is one or more in-ear earphone(s), earbud(s), over-ear headphone(s), or the like. In some examples, wearable audio output device 301 is a single earphone or earbud. In some examples, wearable audio output device 301 includes a pair of earphones or earbuds (e.g., one for each of a user's ears). In some examples, wearable audio output device 301 includes over-ear headphones (e.g., headphones with two over-ear earcups to be placed over a user's ears and optionally connected by a headband). In some embodiments, wearable audio output device 301 includes one or more speakers 306 for providing audio output (e.g., to a user's ear). In some embodiments, wearable audio output device 301 includes one or more placement sensors 304 to detect positioning or placement of wearable audio output device 301 relative to a user's ear, such as to detect placement of wearable audio output device 301 in a user's ear. In some embodiments, wearable audio output device 301 conditionally outputs audio based on whether wearable audio output device 301 is in or near a user's ear (e.g., wearable audio output device 301 forgoes outputting audio when not in a user's ear, so as to reduce power usage). In some embodiments where wearable audio output device 301 includes multiple (e.g., a pair) of wearable audio output components (e.g., earphones, earbuds, or earcups), each component includes one or more respective placement sensors, and wearable audio output device 301 conditionally outputs audio based on whether one or both components is in or near a user's ear, as described herein. In some embodiments, wearable audio output device 301 includes audio I / O logic 312, which determines the positioning or placement of wearable audio output device 301 relative to a user's ear based on information received from placement sensor(s) 304, and, in some embodiments, audio I / O logic 312 controls the resulting conditional outputting of audio. In some embodiments, wearable audio output device 301 includes a wireless interface 315 for communication with a multifunction device, such as device 100 (Figure 1A) or device 300 (Figure 3A). In some embodiments, interface 315 is a wired interface for connection with a multifunction device, such as device 100 (Figure 1A) or device 300 (Figure 3A) (e.g., via a headphone jack or other audio port). In some embodiments, a user can interact with and provide inputs (e.g., remotely) to wearable audio output device 301 via interface 315.

[0119] In some embodiments, wearable audio output device 301 includes one or more microphones 302 for receiving audio input. In some embodiments, microphone(s) 302 detect speech from a user wearing wearable audio output device 301 and / or ambient noise around wearable audio output device 301. In some embodiments, as described in more detail herein with reference to Figure 3C, multiple microphones of microphones 302 are positioned at different locations on wearable audio output device 301 to measure speech and / or ambient noise at different locations around wearable audio output device 301. In some embodiments where wearable audio output device 301 includes multiple (e.g., a pair) of wearable audio output components (e.g., earphones or earbuds), each component includes one or more respective microphones. In some embodiments, audio I / O logic 312 detects or recognizes speech or ambient noise based on information received from microphone(s) 302.

[0120] In some embodiments, wearable audio output device 301 includes one or more input devices 308. In some embodiments where wearable audio output device 301 includes multiple (e.g., a pair) of wearable audio output components (e.g., earphones, earbuds, or earcups), each component includes one or more respective input devices. In some embodiments, input device(s) 308 includes a pressure-sensitive (e.g., intensity-sensitive) input device, which in some embodiments is located within a portion of wearable audio output device 301, sometimes called a "stem," that physically extends from a portion of wearable audio output device 301 that is configured to be inserted in a user's ear (e.g., stem 305 as shown in Figure 3C). In some embodiments, the pressure-sensitive input device detects inputs from a user in response to the user squeezing the input device (e.g., by pinching the stem of wearable audio output device 301 between two fingers). In some embodiments, input device(s) 308 include a touch-sensitive surface (for detecting touch inputs), accelerometer(s) and / or attitude sensor(s) (for determining an attitude of wearable audio output device 301 relative to a physical environment and / or changes in attitude of the device, and / or other input device by which a user can interact with and provide inputs to wearable audio output device 301. In some embodiments, input device(s) 308 include one or more volume control hardware elements (e.g., an up / down button for volume control, or an up button and a separate down button, as described herein with reference to Figure 1A) for volume control (e.g., locally) of wearable audio output device 301. In some embodiments, inputs provided via input device(s) 308 are processed by audio I / O logic 312. In some embodiments, audio I / O logic 312 is in communication with a separate device (e.g., device 100, Figure 1A, or device 300, Figure 3A) that provides instructions or content for audio output, and that optionally receives and processes inputs (or information about inputs) provided via microphone(s) 302, placement sensor(s) 304, and / or input device(s) 308, or via one or more input devices of the separate device. In some embodiments, audio I / O logic 312 is located in device 100 (e.g., as part of peripherals interface 118, Figure 1A) or device 300 (e.g., as part of I / O interface 330, Figure 3A), instead of device 301, or alternatively is located in part in device 100 and in part in device 301, or in part in device 300 and in part in device 301.

[0121] Figure 3C illustrates example audio control by a wearable audio output device in accordance with some embodiments. In some embodiments, when a wearable audio output device having earbuds to which interchangeable eartips may be attached are worn in a user's ears, the earbuds and eartips together act as physical barriers that block at least some ambient sound from the surrounding physical environment from reaching the user's ear. For example, in Figure 3C, wearable audio output device 301 is worn by a user such that earbud 303 and eartip 314 are in the user's left ear. Eartip 314 extends at least partially into the user's ear canal. Preferably, when earbud 303 and eartip 314 are inserted into the user's ear, a seal is formed between eartip 314 and the user's ear so as to isolate the user's ear canal from the surrounding physical environment. However, in some circumstances, earbud 303 and eartip 314 together block some, but not necessarily all, of the ambient sound in the surrounding physical environment from reaching the user's ear. Accordingly, in some embodiments, a first microphone (or, in some embodiments, a first set of one or more microphones) 302-1 (e.g., of microphones 302, Figure 3B) is located on wearable audio output device 301 so as to detect ambient sound, represented by waveform 322, in region 316 of a physical environment surrounding (e.g., outside of) earbud 303. In some embodiments, a second microphone (or, in some embodiments, a second set of one or more microphones) 302-2 (e.g., of microphones 302, Figure 3B) is located on wearable audio output device 301 so as to detect any ambient sound, represented by waveform 324, that is not completely blocked by earbud 303 and eartip 314 and that can be heard in region 318 inside the user's ear canal. Accordingly, in some circumstances in which wearable audio output device 301 is not producing a noise-cancelling (also called "antiphase") audio signal to cancel (e.g., attenuate) ambient sound from the surrounding physical environment, as indicated by waveform 326-1, ambient sound waveform 324 is perceivable by the user, as indicated by waveform 328-1. In some circumstances in which wearable audio output device 301 is producing an antiphase audio signal to cancel ambient sound, as indicated by waveform 326-2, ambient sound waveform 324 is not perceivable by the user, as indicated by waveform 328-2.

[0122] In some embodiments, ambient sound waveform 322 is compared to attenuated ambient sound waveform 324 (e.g., by wearable audio output device 301 or a component of wearable audio output device 301, such as audio I / O logic 312, or by an electronic device that is in communication with wearable audio output device 301) to determine the passive attenuation provided by wearable audio output device 301. In some embodiments, the amount of passive attenuation provided by wearable audio output device 301 is taken into account when providing the antiphase audio signal to cancel ambient sound from the surrounding physical environment. For example, antiphase audio signal waveform 326-2 is configured to cancel attenuated ambient sound waveform 324 rather than unattenuated ambient sound waveform 322.

[0123] In some embodiments, wearable audio output device 301 is configured to operate in one of a plurality of available audio output modes, such as an active noise control audio output mode, an active pass-through audio output mode, and a bypass audio output mode (also sometimes called a noise control off audio output mode). In the active noise control mode (also called "ANC"), wearable audio output device 301 outputs one or more audio-cancelling audio components (e.g., one or more antiphase audio signals, also called "audio-cancellation audio components") to at least partially cancel ambient sound from the surrounding physical environment that would otherwise be perceivable to the user. In the active pass-through audio output mode, wearable audio output device 301 outputs one or more pass-through audio components (e.g., plays at least a portion of the ambient sound from outside the user's ear, received by microphone 302-1, for example) so that the user can hear a greater amount of ambient sound from the surrounding physical environment than would otherwise be perceivable to the user (e.g., a greater amount of ambient sound than would be audible with the passive attenuation of wearable audio output device 301 placed in the user's ear). In the bypass mode, active noise management is turned off, such that wearable audio output device 301 outputs neither any audio-cancelling audio components nor any pass-through audio components (e.g., such that any amount of ambient sound that the user perceives is due to physical attenuation by wearable audio output device 301). In some embodiments, in response to particular types of inputs, such as click-and-hold gestures, at stem 305 of the wearable audio output device 301, wearable audio output device 301 cycles through one or more of the above-discussed audio output modes, as described in further detail herein, for example with reference to Figures 8A-8J and 9A-9C.

[0124] Figure 3D is similar to Figure 3C, except that Figure 3D illustrates wearable audio output device 301b as a set of headphones with over-ear earcups worn over a user's ear, rather than one or more earbuds worn in the user's ears. In the example in Figure 3D, the earcups of wearable audio output device 301b, such as earcup 332 worn over the user's left ear (and typically a second earcup to be worn over the user's right ear), act as the physical barriers that block at least some ambient sound from the surrounding physical environment from reaching the user's ear. Microphones 302-1 and 302-2 located on earcup 332 detect, respectively, ambient sound in region 316 of the physical environment (represented by waveform 322) and ambient sound that is not completely blocked by earcup 332 (represented by waveform 324) and that can be heard in region 318 inside earcup 332, as described in more detail herein with reference to Figure 3C. Figure 3D also shows generated antiphase waveforms 326-1 and 326-2 and resulting perceived ambient sound waveforms 328-1 and 328-2, respectively, also as described in more detail herein with reference to Figure 3C.

[0125] In addition, in the example in Figure 3D, wearable audio output device 301b includes dial 334 and button 336 (e.g., as part of input device(s) 308, Figure 3B). In some embodiments, rotation of dial 334 controls one or more aspects of audio output (e.g., cycles through a set of possible values for the aspect(s) of audio output), such as an audio output volume level or a degree of noise cancellation. For example, rotation of dial 334 controls audio output volume (e.g., rotation in one direction, such as clockwise, increases the volume, and rotation in the other direction, such as counterclockwise, decreases the volume). In some embodiments, dial 334 is configured to receive inputs other than rotational inputs. For example, dial 334 also is a push-button switch or includes a touch-sensitive and / or input intensity-sensitive surface, and is used by a user to provide touch, press, or click inputs to wearable audio output device 301b, as described in more detail herein with reference to Figures 25A-25D.

[0126] In some embodiments, button 336 is a push-button switch or includes a touch-sensitive and / or input intensity-sensitive surface, and controls a respective aspect of audio output (optionally, a different aspect from the one(s) controlled using dial 334). In some embodiments, pressing (or tapping, actuating, etc.) button 336 transitions wearable audio output device 301b between different audio output modes, as described in more detail herein with reference to Figure 9C (e.g., a press input on button 336 on a set of over-ear headphones performs operations analogous to one or more of the operations described herein that are performed in response to detecting a click-and-hold gesture on a stem of an earbud).

[0127] Attention is now directed towards embodiments of user interfaces ("UI") that are, optionally, implemented on portable multifunction device 100.

[0128] Figure 4A illustrates an example user interface for a menu of applications on portable multifunction device 100 in accordance with some embodiments. Similar user interfaces are, optionally, implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof: Signal strength indicator(s) for wireless communication(s), such as cellular and Wi-Fi signals; Time; a Bluetooth indicator; a Battery status indicator; Tray 408 with icons for frequently used applications, such as: ∘ Icon 416 for telephone module 138, labeled "Phone," which optionally includes an indicator 414 of the number of missed calls or voicemail messages; ∘ Icon 418 for e-mail client module 140, labeled "Mail," which optionally includes an indicator 410 of the number of unread e-mails; ∘ Icon 420 for browser module 147, labeled "Browser;" and ∘ Icon 422 for video and music player module 152, labeled "Music;" and Icons for other applications, such as: ∘ Icon 424 for IM module 141, labeled "Messages;" ∘ Icon 426 for calendar module 148, labeled "Calendar;" ∘ Icon 428 for image management module 144, labeled "Photos;" ∘ Icon 430 for camera module 143, labeled "Camera;" ∘ Icon 432 for online video module 155, labeled "Online Video;" ∘ Icon 434 for stocks widget 149-2, labeled "Stocks;" ∘ Icon 436 for map module 154, labeled "Maps;" ∘ Icon 438 for weather widget 149-1, labeled "Weather;" ∘ Icon 440 for alarm clock widget 149-4, labeled "Clock;" ∘ Icon 442 for workout support module 142, labeled "Workout Support;" ∘ Icon 444 for notes module 153, labeled "Notes;" and ∘ Icon 446 for a settings application or module, which provides access to settings for device 100 and its various applications 136.

[0129] It should be noted that the icon labels illustrated in Figure 4A are merely examples. For example, other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon.

[0130] Figure 4B illustrates an example user interface on a device (e.g., device 300, Figure 3) with a touch-sensitive surface 451 (e.g., a tablet or touchpad 355, Figure 3) that is separate from the display 450. Although in some examples, inputs may be received on touch screen display 112 (where the touch sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in FIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 in Figure 4B) has a primary axis (e.g., 452 in Figure 4B) that corresponds to a primary axis (e.g., 453 in Figure 4B) on the display (e.g., 450). In accordance with these embodiments, the device detects contacts (e.g., 460 and 462 in Figure 4B) with the touch-sensitive surface 451 at locations that correspond to respective locations on the display (e.g., in Figure 4B, 460 corresponds to 468 and 462 corresponds to 470). In this way, user inputs (e.g., contacts 460 and 462, and movements thereof) detected by the device on the touch-sensitive surface (e.g., 451 in Figure 4B) are used by the device to manipulate the user interface on the display (e.g., 450 in Figure 4B) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are, optionally, used for other user interfaces described herein.USER INTERFACES AND ASSOCIATED PROCESSES

[0131] Attention is now directed towards embodiments of user interfaces ("UI") and associated processes that may be implemented on a computer system (e.g., that includes an electronic device such as portable multifunction device 100, Figure 1A, or device 300, Figure 3A) with a display device (e.g., touch-sensitive display system 112, Figure 1A, or display 340, Figure 3A) and a touch-sensitive surface (e.g., touch-sensitive display system 112, Figure 1A, or touchpad 355, Figure 3A), and that includes or is in communication with one or more wearable audio output devices (e.g., one or more wearable audio output devices 301).

[0132] Figures 5A-5V illustrate example user interfaces for pairing and calibrating wearable audio output devices in accordance with some embodiments. Figures 6A-6O illustrate example user interfaces for alerting a user when earbuds no longer satisfy fit criteria during use in accordance with some embodiments. Figures 7A-7Q illustrate example user interfaces and user interactions for changing the audio output mode of a wearable audio output device in accordance with some embodiments. Figures 8A-8H illustrate example user interactions with wearable audio output devices to control audio outputs in accordance with some embodiments. Figures 9A-9C illustrate an example settings user interface for controlling various features associated with wearable audio output devices and examples of controlling audio output mode in accordance with some embodiments. Figures 13A-13D illustrate example user interfaces for pairing wearable audio output devices in accordance with some embodiments. Figures 14A-14Z illustrate example user interfaces and user interactions for changing the audio output mode of wearable audio output devices in accordance with some embodiments. Figures 15A-15E illustrate an example settings user interface for controlling various features associated with wearable audio output devices and examples of controlling audio output mode in accordance with some embodiments. Figures 16A-16G illustrate example user interfaces for calibrating and displaying information about acoustic seal quality of wearable audio output devices in accordance with some embodiments. Figures 17A-17J illustrate example user interfaces and user interactions for selecting an audio output device, such as a wearable audio output device, and changing the audio output mode of the selected audio output device via (e.g., using) a wearable electronic device in accordance with some embodiments. Figures 21A-21J illustrate example user interfaces and user interactions for changing the audio output mode of wearable audio output devices. Figures 22A-22D illustrate example user interfaces and user interactions for accessing a settings user interface for controlling various features associated with wearable audio output devices. Figures 23A-23AA illustrate example user interfaces and user interactions for controlling audio output settings for multiple wearable audio output devices using a single settings user interface. Figures 25A-25G illustrate example user interactions for controlling audio outputs from a wearable audio output device and example audio and visual alerts responsive to such user interactions. The user interfaces, inputs, and audio outputs in these figures are used to illustrate the processes described below, including the processes in Figures 10A-10H, 11A-11D, 12A-12E, 18A-18H, 19A-19C, 20A-20B, 24A-24D, and 26A-26D. For convenience of explanation, some of the embodiments will be discussed with reference to operations performed using a wearable audio output device that is worn by a user and that is in communication with and separate from a computer system having a touch-sensitive display system 112 or display 340 that is separate from a touch-sensitive input device such as touchpad 355. In some embodiments, the operations are performed in response to instructions received by the wearable audio output device from the electronic device, based on processing performed at the electronic device. In some embodiments, the operations are performed by the wearable audio output device based on processing performed at the wearable audio output device. However, in some cases, analogous operations are optionally performed using audio output devices that are part of a device having a display generation component and / or touch-sensitive input device (e.g., a wearable device, such as headphones or a headset, that integrates the one or more audio output devices with a display and / or touch-sensitive input device).

[0133] Figures 5A-5V illustrate example user interfaces for pairing and calibrating wearable audio output devices in accordance with some embodiments.

[0134] Figure 5A illustrates an example user interface on display 112 of device 100. While displaying the user interface, device 100 periodically and repeatedly listens for wireless broadcast signals (e.g., pairing requests) from one or more peripherals (e.g., earbuds 502-1 and 502-2 as well as earbud case 502-3) to pair the peripheral(s) with device 100. In one embodiment, as illustrated throughout Figures 5A-5D, device 100 can detect pairing requests from peripherals when the peripheral is within threshold distance 508 of device 100 and cannot detect pairing requests from peripherals when the peripheral is outside of threshold distance 508. For example, at the bottom of Figure 5A, Figure 5A illustrates an example spatial relationship (e.g., physical distance) between device 100 and earbuds 502-1 and 502-2 as well as earbud case 502-3, where earbuds 502-1 and 502-2 as well as earbud case 502-3 are outside of threshold distance 508 of device 100. In contrast, Figure 5B illustrates when earbud 502-1, earbud 502-2, and earbud case 502-3 (illustrated and hereinafter referred to collectively as earbud set 503) are within threshold distance 508 of device 100, where the device is capable of detecting pairing requests from the peripherals.

[0135] Figure 5B illustrates an example user interface, displayed subsequent to the user interface in Figure 5A, and in some embodiments in response to detecting movement of a peripheral (e.g., earbud 502-1) or set of peripherals (e.g., earbud set 503), from outside of threshold distance 508 to within threshold distance 508, for initiating pairing of device 100 with the peripheral (e.g. earbud 502-1) or set of peripherals (e.g., earbud set 503). In Figure 5B, device 100 detects a pairing request from a peripheral (e.g., earbud 502-1, which is shown in Figure 5A and part of earbud set 503 in Figure 5B) within threshold distance 508. In some embodiments, in response to detecting the pairing request from earbud 502-1, device 100 determines whether earbud 502-1 meets coupling criteria. In the example shown in Figure 5B, coupling criteria is met when an earbud (e.g., earbud 502-1) is placed within and / or is electrically coupled to an earbud case (e.g., earbud case 502-3) (e.g., to form earbud set 503). After device 100 determines that earbud 502-1 meets coupling criteria (e.g., in response to device 100 determining that earbud 502-1 meets the coupling criteria), device 100 displays window 520-1 overlaid on the user interface of Figure 5A. Window 520-1 includes a representation of earbud set 503 and button 522-1 (labeled "Connect"), which, when activated by a user input, initiates pairing of device 100 with the peripherals (e.g., earbuds 502-1 and 502-2 and earbud case 502-3 shown in Figure 5A) of earbud set 503. In some embodiments, the user interface(s) shown in window 520-1 are instead displayed on the entirety (or substantially all, e.g., greater than 95%, 96%, 97%, 98%, or 99%) of touch screen 112. Device 100 also displays an exit button 524-1 that, when activated by a user input, such as a tap gesture, causes window 520-1 to cease to be displayed so that the user can perform other operations on device 100. Where exit button 524-1 accompanies another user interface described herein (e.g., a user interface that is part of the pairing process or fit test), exit button 524-1, when activated by a user input, causes that user interface to cease to be displayed.

[0136] Figures 5C-5D illustrate transitions from Figure 5B. In particular, Figure 5C shows input 540 (e.g., a tap gesture) on button 522-1 in window 520-1. In response to detecting input 540, device 100 initiates pairing of device 100 with the peripherals of earbud set 503. In Figure 5D, after device 100 has paired with the peripherals of earbud set 503, device 100 displays an indication 523-1 (labeled "Connected") in window 520-2 to indicate that device 100 is paired with (e.g., connected to) earbud set 503. In some embodiments, device 100 displays, in window 520-2, a button that, when activated, causes device 100 to proceed from the pairing process to a fit test for determining and optimizing the fit of earbuds 502-1 and 502-2 in a user's ears.

[0137] Figure 5E illustrates example user interface 521-1 for initiating a fit test to determine and optimize the fit of earbud 502-1 and earbud 502-2 in the user's ears. In some embodiments, instead of being displayed in a window as shown in Figures 5E-5V, user interface 521 is displayed on the entirety (or substantially all, e.g., greater than 95%, 96%, 97%, 98%, or 99%) of touch screen 112. In some embodiments, user interface 521-1 is displayed in response to a user input on a button displayed in an immediately preceding user interface (e.g., a button displayed in window 520-2, Figure 5D, for proceeding from the pairing process to the fit test). Figure 5E shows button 525-1 (labeled "Begin Test"), which, when activated, initiates the fit test. Figure 5E also shows input 526-1 (e.g., a tap gesture) on button 525-1 to activate button 525-1 and begin the fit test. As described in further detail below, during the fit test, earbud 502-1 and earbud 502-2 obtain audio data (e.g., based on audio detected using a microphone configured to detect in-ear audio and audio detected using a microphone configured to detect ambient audio), and, based at least in part on the obtained audio data, device 100 displays suggestions to the user to improve the fit of earbud 502-1 and / or earbud 502-2 in the user's ears.

[0138] Figure 5F illustrates a transition from Figure 5E. In particular, Figure 5F illustrates example user interface 521-2 displayed in response to a user input (e.g., on button 525-1, Figure 5E) to begin the fit test. Figure 5F also illustrates earbud 502-1 and earbud 502-2 in relation to ears 528-1 and 528-2 of the user. In particular, Figure 5F shows that earbud 502-1 and earbud 502-2 are not placed in ears 528-1 and 528-2 of the user. As illustrated in Figure 5F, earbuds 502-1 and 502-2 are coupled to eartips 527-1 and 527-2 (e.g., attachments to the earbuds, which may be made of rubber or a rubber-like material such as silicone to help create a seal between a respective earbud and a respective ear in which the earbud is placed). Eartips 527-1 and 527-2 can be removed, and swapped for different eartips, by the user. User interface 521-2 in Figure 5F includes instructions to the user to place earbuds 502 in his or her ears, in the form of the text "Please place earbuds in ears" and two representations of ears, each associated with a respective representation of an earbud. User interface 521-2 also includes indicators 529-1 and 529-2, displayed underneath the representations of the ears, indicating with gray circles that the earbuds are not placed in the ears of the user (or that device 100 is unable to detect that the earbuds have been placed in the user's ears). The letter 'R' in indicator 529-1 indicates that indicator 529-1 represents (e.g., a state of) an earbud for right ear 528-1, which in this example is earbud 502-1. The letter 'L' in indicator 529-2 indicates that indicator 529-2 represents (e.g., a state of) an earbud for left ear 528-2, which in this example is earbud 502-2. Although some embodiments (e.g., as shown in the example in Figure 5F) use gray circles to indicate that earbuds 502-1 and 502-2 have not been detected as being in the user's ears, one of ordinary skill in the art will recognize that other forms of status indicator can be used instead.

[0139] Figure 5G illustrates a transition from Figure 5F. In particular, Figure 5G shows earbud 502-1 placed in ear 528-1 of the user, and earbud 502-2 placed in ear 528-2 of the user. Accordingly, indicators 529-1 and 529-2 have changed from gray circles, which indicate that earbuds 502-1 and 202-2 are not in the user's ears, to black circles, which indicate that earbuds 502-1 and 202-2 have been detected as being placed in the user's ears and that a next step of the fit test has not yet been performed. Although some embodiments (e.g., as shown in the example in Figure 5G) use black circles to indicate that earbuds 502-1 and 502-2 have been placed in the user's ears (e.g., prior to performing a next step of the fit test, such as a calibration step), one of ordinary skill in the art will recognize that other forms of status indicator can be used instead.

[0140] Figure 5H illustrates a transition from Figure 5G. In particular, Figure 5H shows example user interface 521-4, which includes one or more indications that the fit test is in progress, such as animation 530 and the text "Fit test in progress" as shown in Figure 5H. In some embodiments, user interface 521-4 is displayed in response to device 100 detecting that both earbuds 502-1 and 502-2 have been placed in the user's ears. In some embodiments, user interface 521-4 is displayed in response to a user input activating a button displayed in user interfaces 521-2 (Figure 5F) and 521-3 (Figure 5G) for continuing with the fit test after earbuds 502-1 and 502-2 have been placed in the user's ears (and optionally, in some embodiments, the button is displayed for the first time, or becomes activatable after having been displayed as non-activatable (e.g., grayed out), in response to detecting placement of earbuds 502-1 and 502-2 in the user's ears). In some embodiments, performing the fit test includes outputting a calibration tone via earbuds 502 (e.g., using speaker(s) 306, Figure 3B), detecting audio via earbud 502-1 and 502-2 (e.g., using one or more microphones on each earbud, such as microphone 302-2 in Figure 3B), and determining whether the detected audio indicates that earbuds 502 satisfy device fit criteria (e.g., by comparing the detected audio to the calibration tone to determine whether and how much ambient audio is included in the detected audio; if the detected audio includes greater than a threshold amount of ambient audio, the device fit criteria is not satisfied).

[0141] Additionally, in Figure 5H, indicator 529-1 has changed to a green circle with a checkmark, which indicates that earbud 502-1 has met fit criteria (also called "device fit criteria") assessed by the fit test. In contrast, indicator 529-2 has not changed in appearance. Although the example in Figure 5J illustrates that indicator 529-1 has been updated during the fit test to reflect whether earbud 502-1 meets the fit criteria separately from (e.g., here, prior to) updating indicator 529-2 to reflect whether earbud 502-2 meets the fit criteria, one of ordinary skill will recognize that, in some embodiments, the indicators are updated concurrently, and optionally after the end of the fit test (e.g., such that indicator 529-1 would continue to have the same appearance in Figure 5H as in Figure 5G, similarly to indicator 529-2).

[0142] Figure 5I illustrates a transition from Figure 5H. In particular, Figure 5I shows example user interface 521-5, which is displayed after the fit test has been performed and which presents results of the fit test. Indicators 529-1 and 529-2 in user interface 521-5 show the status of earbuds 502-1 and 502-2, respectively. In particular, indicator 529-2 in Figure 5I is displayed in a different color (e.g., yellow), which is represented by the changed fill pattern, signifying that the fit test has been performed and that earbud 502-2 does not satisfy the fit criteria (e.g., because earbud 502-2 was not placed in the ear of the user correctly). Furthermore, user interface 521-5 includes instruction 531-1 prompting the user to adjust the placement of left earbud 502-2 in the user's left ear. Below instruction 531-1, button 532-1 (labeled "Continue") is displayed for continuing the fit test. In some embodiments, button 532-1 is non-activatable (e.g., grayed out) until device 100 determines that the user has complied with instruction 531-1 (e.g., by detecting or receiving information indicating that earbud 502-2 has been removed from and replaced in an ear (e.g., ear 528-2)), after which button 532-1 becomes activatable.

[0143] Figure 5J shows the same user interface 521-5 as Figure 5I. Figure 5J also shows earbud 502-2 now properly aligned in ear 528-2 (e.g., in response to instruction 531-1), and input 533 received at user interface 521-5, specifically at button 532-1, to continue the fit test (e.g., repeat the fit test as a result of left earbud 502-2 failing the fit test). Although Figure 5J shows indicator 529-2 with the same appearance as in Figure 5I, prior to the adjustment of left earbud 502-2, in some embodiments indicator 529-2 is changed to a gray circle in response to earbud 502-2 being removed (e.g., while earbud 502-2 is not detected as being placed in an ear of the user) and changed to a black circle in response to earbud 502-2 being replaced in the user's ear (e.g., to indicate that earbud 502-2 has been detected as being placed in an ear of the user and that a next step of the fit test has not yet been performed).

[0144] Figure 5K shows example user interface 521-6, displayed in response to input 533 (Figure 5J). User interface 521-6 includes one or more indications that the fit test is in progress (e.g., in this case, for a second time), such as animation 530 and the text "Fit test in progress." In Figure 5K, user interface 521-6 continues to indicate that left earbud 502-2 does not satisfy the fit criteria, as indicated by the patterned fill of indicator 529-2. As explained above with reference to Figure 5H, in some embodiments, the appearance of indicator 529-2 is not updated during the fit test, but rather is updated after the fit test has been performed, based on results of the fit test (e.g., the appearance of indicator 529-2 is the same in Figure 5J as in Figure 5K).

[0145] Figure 5L illustrates example user interface 521-7, which is displayed after the fit test has been performed (e.g., in response to completion of the fit test) and which presents results of the fit test. Indicators 529-1 and 529-2 in user interface 521-7 show the status of earbuds 502-1 and 502-2, respectively. In particular, indicator 529-2 indicates that earbud 502-2 still does not satisfy the fit criteria, while indicator 529-1 indicates that earbud 502-1 continues to satisfy the fit criteria. Furthermore, user interface 521-7 includes instruction 531-2 prompting the user to replace eartip 527-2 on earbud 502-2 for a better fit and to subsequently re-insert the earbud with the new eartip in ear 528-2. Below instruction 531-2, button 532-2 is displayed for continuing the fit test. In some embodiments, button 532-2 is non-activatable (e.g., grayed out) until device 100 determines that the user has complied with instruction 531-2 (e.g., by detecting or receiving information indicating that earbud 502-2 has been removed from and replaced in an ear, or, in some embodiments where device 100 is able to identify which eartip is attached to a particular earbud, by detecting that the eartip attached to earbud 502-2 has been changed), after which button 532-2 becomes activatable. For example, in some embodiments button 532-2 is non-activatable prior to detecting that earbud 502-2 has been replaced in an ear of the user (Figure 5O).

[0146] Figures 5M-5N illustrate changing of the eartip attached to earbud 502-2. Figures 5M-5N show the same user interface 521-7 as Figure 5L, except that Figures 5M-5N show that earbud 502-2 has been removed from ear 528-2. Accordingly, indicator 529-2 has changed to a gray circle to indicate that earbud 502-2 is no longer in an ear of the user. In addition, Figures 5M-5N illustrate eartip 527-2 being exchanged for a different eartip 527-3 (e.g., a larger eartip to accommodate a larger ear).

[0147] Figure 5O shows that earbud 502-2, now with eartip 527-3 attached, has been replaced (e.g., placed back) in ear 528-2. In response to the user replacing left earbud 502-2 back in ear 528-2, indicator 529-2 changes from a gray circle to a black circle, which indicates that earbud 502-2 has been detected as being placed in an ear of the user and that a next step of the fit test has not yet been performed. Figure 5O also illustrates input 534 received at button 532-2 (labeled "Continue") to continue the fit test.

[0148] Figure 5P illustrates a transition from Figure 5O. In particular, Figure 5P shows example user interface 521-8, which is displayed in response to input 534 at button 532-2, and which includes one or more indications that the fit test is in progress (e.g., in this case, for a third time), such as animation 530 and the text "Fit test is in progress." In the example shown in Figure 5P, indicators 529-1 and 529-2 have the same appearance during the fit test (e.g., as shown in Figure 5P) as before performing the fit test (e.g., as shown in Figure 5O).

[0149] Figure 5Q illustrates an example user interface 521-9, which is displayed after the fit test has been performed (e.g., in response to completion of the fit test) and which presents results of the fit test. Indicators 529-1 and 529-2 in user interface 521-9 show the status of earbuds 502-1 and 502-2, respectively. In particular, indicator 529-1 (e.g., a green circle with a checkmark) indicates that earbud 502-1 (e.g., still) satisfies the fit criteria assessed by the fit test. Indicator 529-2 has been updated to a different color (e.g., yellow), which is represented by the changed fill pattern, signifying that earbud 502-2 (e.g., still) does not satisfy the fit criteria (e.g., because earbud 502-2 is still not properly aligned in ear 528-2). Furthermore, user interface 521-9 includes instruction 531-3 prompting the user to adjust the placement of left earbud 502-2 in the user's left ear. Below instruction 531-3, button 532-3 (labeled "Continue") is displayed for continuing the fit test. In some embodiments, button 532-3 is non-activatable (e.g., grayed out) until device 100 determines that the user has complied with instruction 531-3 (e.g., by detecting or receiving information indicating that earbud 502-2 has been removed from and replaced in an ear (e.g., ear 528-2)), after which button 532-3 becomes activatable.

[0150] Figure 5R shows earbud 502-2 with eartip 527-3 now properly aligned in ear 528-2 (e.g., in response to instruction 531-3). In addition, Figure 5R shows the same user interface 521-9 as Figure 5Q, except that indicator 529-2 in Figure 5R has been changed to a black circle in response to earbud 502-2 being replaced in the user's ear, optionally after having been changed to a gray circle in response to earbud 502-2 being removed. Figure 5R also shows input 535 at button 532-3 to continue the fit test.

[0151] Figure 5S shows example user interface 521-10, displayed in response to input 535 (Figure 5R). User interface 521-10 includes one or more indications that the fit test is in progress (e.g., in this case, for a fourth time), such as animation 530 and the text "Fit test in progress." In the example shown in Figure 5S, indicators 529-1 and 529-2 have the same appearance during the fit test (e.g., as shown in Figure 5S) as before performing the fit test (e.g., as shown in Figure 5R).

[0152] Figure 5T illustrates example user interface 521-11, which is displayed after the fit test has been performed (e.g., in response to completion of the fit test) and which presents results of the fit test. Indicators 529-1 and 529-2 in user interface 521-11 show the status of earbuds 502-1 and 502-2, respectively. In particular, indicator 529-1 (e.g., a green circle with a checkmark) indicates that earbud 502-1 (e.g., still) satisfies the fit criteria assessed by the fit test. Indicator 529-2 has been updated to a different color (e.g., yellow), which is represented by the changed fill pattern, signifying that earbud 502-2 (e.g., still) does not satisfy the fit criteria. Furthermore, user interface 521-11 includes instruction 531-4 notifying the user that the fit test did not achieve desired thresholds (e.g., for the amount of ambient audio and / or calibration tone detected during the fit test). User interface 521-11 also includes an identification of the eartip that produced the best fit test results (e.g., "the first eartip"). In some embodiments, user interface 521-11 is displayed based at least partially on a determination that fit test attempts were performed using a plurality of eartips, where none of the fit test attempts succeeded (e.g., none of the eartips satisfied the fit criteria during any of the fit test attempts). Below instruction 531-4, two buttons are shown: button 536 (labeled "Finish") and button 537 (labeled "Restart Test"). "Finish" button 536, when selected, exits the fit test user interfaces, regardless of the outcome of the test. "Restart Test" button 537, when selected, will restart the fit test sequence (e.g., by redisplaying a user interface similar to user interface 521-2 in Figure 5F (or, alternatively, user interface 521-4 in Figure 5H) and repeating the fit test process, as described herein with reference to Figures 5F-5S.

[0153] Figures 5U-5V illustrate conclusion of the fit test. In particular, Figure 5U illustrates the same user interface 521-11 as Figure 5T and input 538 at "Finish" button 536. Figure 5V illustrates example user interface 521-12, displayed in response to input 538. User interface 521-12 indicates that the fit test has been completed and can be subsequently accessed via the settings menu. Example user interfaces for a settings menu are shown in Figures 9A-9B. In some embodiments, as in the example shown in Figure 5V, user interface 521-12 includes a visual indicator to signify that the test is complete (e.g., a single green checkmark).

[0154] Figures 6A-6O illustrate example user interfaces for alerting a user when the user's earbuds no longer satisfy fit criteria during use in accordance with some embodiments. Figure 6A illustrates a portable multifunction device 100 that is paired to earbuds 502-1 and 502-2. Unlike Figure 5A-5V, the notifications (also called "alerts") in Figures 6A-6O are triggered during use of earbuds 502 outside of pairing and calibration using a setup menu, and optionally while using earbuds 502 to listen to media content (e.g., music, audio tracks for movies and TV shows, etc.). In some embodiments, where one or more portions of the audio being played via earbuds 502 is similar to the calibration tone used for the fit test (e.g., as described herein with reference to Figure 5H), device 100 performs the fit test using a respective such portion of the audio (e.g., so that the fit test can be performed without playing the calibration tone, which would likely interfere with the media content being played). In this way, the fit test can be performed, and notifications about earbud fit can thereby be provided (e.g., notifications 610, 615, 617, 618, and 619 as described herein with reference to Figures 6A-6O), while the user is using the earbuds outside of the earbud setup process.

[0155] In Figure 6A, earbuds 502 have been placed in ears 528-1 and 528-2 of the user, and, as indicated by status indicators 602 and 603 (e.g., two green circles with checkmarks), the fit of earbud 502-1 in ear 528-1 and the fit of earbud 502-2 in ear 528-2 satisfy the fit criteria. Figure 6A also illustrates example user interface 601-1 for a fitness application that is associated with a current activity of the user (e.g., running) and that is being used to play media content (e.g., music) via earbuds 502, which are (e.g., wired or wirelessly) in communication with device 100. Although the examples in Figures 6A-6O are based on a fitness application, one of ordinary skill will recognize that the notifications described in Figures 6A-6O may be presented while the user is using a different application (e.g., so long as the application is distinct from an earbud settings application for managing earbud settings and performing earbud setup and, optionally, while the application in use is being used to play media content via earbuds 502). In some embodiments, the notifications described in Figures 6A-6O are displayed over at least a portion of a user interface of the application that the user is using. In some embodiments, the notifications described in Figures 6A-6O are triggered while touch screen 112 of device 100 is turned off, causing touch screen 112 to be turned on, such that the notifications are displayed on a lock screen of device 100. In the example shown in Figure 6A, media content (e.g., a song or track) from album 604 (titled "Album") is being played. User interface 601-1 also includes audio playback controls such as previous button 606 for moving to the previous track or rewinding the audio being played, play / pause button 607 for toggling audio playback between on and off, and next button 608 for moving to the next track or fast forwarding through the audio being played. Volume control 605 is also displayed below the audio playback controls.

[0156] Figure 6B illustrates that earbud 502-2 in ear 528-1 has become misaligned. Accordingly, status indicator 603 has changed (e.g., to a yellow circle with the letter 'L') to indicate that earbud 502-2 no longer meets the fit criteria. In addition, notification 610 is displayed to alert the user of issue(s) with the fit of earbuds 502 and to prompt the user to check the fit of earbuds 502 in the user's ears. Although notification 610 and other notifications in Figures 6A-6O are shown as banner-style notifications (e.g., overlaid over a portion of a user interface of an application such as the fitness application), a respective notification may also or alternatively be shown on a lock screen of device 100 and / or in a notifications user interface. In some embodiments, an audio output that corresponds to notification 610 is played (e.g., via earbuds 502) and / or a tactile output that corresponds to notification 610 is provided. One of ordinary skill in the art will recognize that any combination of alerts (e.g., visual, audio, and / or tactile, etc.) may be used to alert the user that one or more earbuds no longer meets the fit criteria.

[0157] Figures 6C-6E illustrate an example user response to notification 610 alerting the user of the issue(s) with the fit of earbuds 502. In particular, Figure 6C illustrates input 611 received at notification 610 to launch the fit test user interface. Figure 6D illustrates that, in response to input 611 at notification 610, fit test user interface 612-1 (e.g., which is similar to user interface 521-3 shown in Figure 5G) is displayed. User interface 612-1 includes indicators 629-1 and 629-2 that indicate the status of right earbud 502-1 and left earbud 502-2, respectively, and that correspond to status indicators 602 and 603, respectively. In addition, user interface 612-1 includes button 613, which can be activated to begin a fit test, and input 614 received at button 613 to begin the fit test. Figure 6E shows user interface 612-2, which replaces user interface 612-1 of Figure 6D, in response to input 614 being received at button 613 to begin the fit test. User interface 612-2 includes one or more indications that the fit test is being performed (e.g., in progress), such as animation 530 and the text "Fit test in progress." It is noted that in the example shown in Figures 6D-6E, user interface 612 is displayed in a window. In some embodiments, instead of being displayed in a window, user interface 612 is displayed on the entirety (or substantially all, e.g., greater than 95%, 96%, 97%, 98%, or 99%) of touch screen 112.

[0158] Figure 6F illustrates alerting a user while the user is engaged in a particular activity when the user's earbuds no longer satisfy fit criteria during use. Status indicators 602 and 603 indicate that earbuds 502 do not meet the fit criteria (e.g., as indicated by the patterned fill of status indicators 602 and 603, representing a yellow color). Accordingly, notification 615 is displayed to prompt the user to change the eartips attached to earbuds 502 to larger eartips based on the user's current activity (e.g., based on the fact that the user is running, to achieve a better earbud fit during running). In some embodiments, device 100 (e.g., automatically) detects the current activity of the user. In some embodiments, the user indicates his or her current activity to device 100 (e.g., by launching the fitness application). In some embodiments, monitoring of the fit of earbuds 502 is performed during particular activities, such as exercise (e.g., running).

[0159] Figures 6G-6H show earbuds 502-1 and 502-2 removed from ears 528-1 and 528-2 of the user, as indicated by status indicators 602 and 603 having changed to solid gray circles. Figures 6G also illustrates the currently-attached eartips 616-1 and 616-2 being exchanged for larger eartips 616-3 and 616-4, respectively. Notably, eartip 616-4 is in poor condition (e.g., having some debris (e.g., earwax) or damage (e.g., a tear in the eartip)). Figure 6H shows earbuds 502-1 and 502-2 no longer coupled to eartips 616-1 and 616-2, respectively, and instead now coupled with eartips 616-3 and 616-4, respectively. In some embodiments, as in the example shown in Figures 6G-6H, notification 615 ceases to be displayed in response to the user at least partially complying with the prompt in notification 615 (e.g., by removing earbuds 502). Optionally, in some embodiments, notification 615 continues to be displayed after earbuds 502 are removed. In addition, in some embodiments, as in the example shown in Figures 6G-6H, device 100 continues to play audio while earbuds 502 are removed from the user's ears.

[0160] Figure 6I illustrates earbuds 502-1 and 502-2 placed back in ears 528-1 and 528-2 of the user, respectively. Indicator 602 indicates that right earbud 502-1 and eartip 616-3 placed in right ear 528-1 meet fit criteria, while indicator 603 indicates that left earbud 502-2 and eartip 616-4 placed in left ear 528-2 do not meet fit criteria (e.g., as indicated by the patterned fill of status indicator 603, which represents a yellow color). In this example situation, earbud 502-2 and eartip 616-4 do not meet the fit criteria because eartip 616-4 is in poor condition (e.g., damaged or dirty) and is not creating a seal (or a sufficient seal) within ear 528-2. In accordance with eartip 616-4 attached to earbud 502-2 being in poor condition (e.g., damaged or dirty), notification 617 is displayed to notify the user that the earbud 502-2 and eartip 616-4 should be cleaned and / or eartip 616-4 replaced.

[0161] Figure 6J shows earbud 502-2 removed from ear 528-2, as indicated by status indicator 603 having changed to a solid gray circle. Figure 6J also illustrates eartip 616-4 being cleaned. In some embodiments, as in the example shown in Figure 6J, notification 617 ceases to be displayed in response to the user at least partially complying with the prompt in notification 617 (e.g., by removing earbud 502-2). Optionally, in some embodiments, notification 617 continues to be displayed after earbud 502-2 is removed.

[0162] Figure 6K illustrates earbud 502-2 placed back in ear 528-2 after being cleaned. However, earbud 502-2 has not been correctly placed in ear 528-2 and thus does not meet the fit criteria, as indicated by status indicator 603 (e.g., with a patterned fill representing a yellow color). Accordingly, device 100 displays notification 618 to prompt the user to correct the placement of left earbud 502-2 in left ear 528-2.

[0163] Figure 6L illustrates earbud 502-2 properly aligned in ear 528-2 (e.g., after being repositioned in response to notification 618, Figure 6K). However, earbud 502-2 (e.g., still) does not meet the fit criteria, as indicated by status indicator 603 (e.g., with the patterned fill representing the yellow color). Accordingly, device 100 displays notification 619 to prompt the user to change the current eartip 616-4 to a different size (e.g., smaller) eartip to try to improve the earbud fit.

[0164] Figures 6M-6N illustrate earbud 502-2 removed from ear 528-2, as indicated by status indicator 603 having changed to a solid gray circle. Figure 6M also illustrates eartip 616-4, the eartip currently attached to earbud 502-2, being exchanged for smaller eartip 616-5. Figure 6N earbud 502-2 no longer coupled to eartip 616-4 and instead now coupled to smaller eartip 616-5. The currently attached eartip 616-4 is then placed next to the smaller eartip 616-5.

[0165] Figure 6O illustrates earbud 502-2, now with eartip 616-5 attached, placed back in ear 528-2 of the user. Status indicator 603 indicates that earbud 502-2 is now properly fitted in ear 528-2. In some embodiments, device 100 displays an indication that earbud 502-2 is now properly fitted in an ear of the user (e.g., an indication that both earbuds 502 are now properly fitted in the user's ears) (e.g., after repeating the fit test after earbud 502-2, with eartip 616-5 attached, has been replaced in ear 528-2, and in accordance with a determination that earbud 502-2 meets the fit criteria).

[0166] Figures 7A-7Q illustrate example user interfaces and user interactions for changing the audio output mode of a wearable audio output device in accordance with some embodiments.

[0167] Figure 7A illustrates example user interface 700, which is similar to user interface 601-1 as shown in and described with reference to Figure 6A. User interface 700 is a user interface of a fitness application that is associated with a current activity of the user (e.g., running) and that is being used to play media content (e.g., music) via earbuds 502. Additionally, Figure 7A shows swipe gesture 701 beginning from an initial position 701-1 in the upper right corner of touch screen 112 and moving downward across touch screen 112.

[0168] Figure 7B illustrates that in response to a first portion of swipe gesture 701 from initial position 701-1 to second position 701-2, device 100 displays a first portion of a settings user interface 702 (sometimes also called a control panel user interface) over at least a portion of user interface 700.

[0169] Figure 7C illustrates settings user interface 702 displayed over the entirety (or substantially all, e.g., greater than 95%, 96%, 97%, 98%, or 99%) of user interface 700 (e.g., in response to ceasing to detect swipe gesture 701, optionally after further downward movement of swipe gesture 701 across touch screen 112). In some embodiments, user interface 700 is at least partially obscured or blurred behind settings user interface 702 such that distinct features of user interface 700 are not discernible. Settings user interface 702 includes a plurality of controls for various features of device 100. Notably, settings user interface 702 includes volume control 703. Upward and downward swipe inputs on volume control 703 may be provided to increase or decrease, respectively, the volume of audio outputs from device 100 (e.g., via earbuds 502).

[0170] Figure 7D illustrates input 704 (e.g., a press gesture that meets an intensity threshold that is above a nominal contact detection intensity threshold, or a long press gesture that is maintained on touch screen 112 for at least a threshold amount of time) at volume control slider.

[0171] Figure 7E illustrates a transition from Figure 7D. In particular, Figure 7E shows enhanced volume control user interface 705, which is displayed in response to input 704 on volume control 703 (Figure 7D). Enhanced volume control user interface 705 includes volume control 706, which is an enlarged version of volume control 703 (Figure 7D) is enlarged, and which allows for finer (e.g., more granular) volume control. Additionally, user interface 705 includes noise management control 707-1 that indicates the audio output mode in which earbuds 502 are currently operating. As shown in Figure 7E, earbuds 502 are operating in an active pass-through audio output mode in which one or more pass-through audio components are output so that the user can hear a greater amount of ambient sound from the surrounding physical environment than would otherwise be perceivable to the user (e.g., as described herein with reference to Figure 3C), which is indicated by pass-through icon 711 within noise management control 707-1. Figure 7E also shows input 708 (e.g., a tap gesture) at noise management control 707-1.

[0172] Figure 7F shows expanded noise management control 707-2, which includes representations of three available audio output modes for earbuds 502, each of which is associated with a different audio output mode available for earbuds 502. In particular, expanded noise management control 707-2 includes pass-through icon 711, bypass icon 710, and active noise control icon 709. Active noise control icon 709 represents an active noise control ("ANC") audio output mode in which one or more audio-cancelling audio components are output to at least partially cancel ambient sound from the surrounding physical environment that would otherwise be perceivable to the user. Bypass icon 710 represents a bypass audio output mode in which neither audio-cancelling audio components nor pass-through audio components are provided (e.g., any amount of ambient sound that the user perceives is due to physical attenuation by the earbuds 502 (and any attached eartips) in the user's ears). Selection indicator 713 displayed over pass-through icon 711 (e.g., and not displayed over either bypass icon 710 or active noise control icon 709) indicates that the audio pass-through mode represented by pass-through icon 711 is the mode in which earbuds 502 are currently operating.

[0173] Figure 7G illustrates input 712 (e.g., a tap gesture) at active noise control icon 709. Figure 7H illustrates that, in response to detecting input 712 at active noise control icon 709, selection indicator 713 ceases to be displayed over pass-through icon 711 and is instead displayed over active noise control icon 709. In addition, the audio output mode of earbuds 502 is changed from the audio pass-through mode represented by pass-through icon 711 to the active noise control mode represented by active noise control icon 709. In some embodiments, an audible tone is output to indicate that the audio output mode has been changed.

[0174] Figure 7I illustrates that expanded noise management control 707-2 has been collapsed to noise management control 707-1, which indicates (e.g., only) the audio output mode in which earbuds 502 are currently operating (e.g., the active noise control mode represented by active noise control icon 709) without displaying representations of any other audio output modes (e.g., without displaying bypass icon 710 or pass-through icon 711).

[0175] Figures 7J-7Q illustrate automatic switching of audio output mode in response to different types of inputs. In particular, Figures 7J-7K illustrate behavior in response to a user removing an earbud from his or her ear. Some aspects in Figures 7J-7Q are not according to the invention and are presented for illustration purposes only.

[0176] Figure 7J illustrates earbud 502-2 removed from ear 528-2 of the user. In response to the removal of earbud 502-2, earbuds 502-1 and 502-2 switch from the active noise control mode to the pass-through mode, as indicated by pass-through icon 711 now displayed in noise management control 707-1. In some embodiments, as illustrated in Figure 7J, both earbuds 502 switch to the pass-through mode in response to either earbud 502-1 or 502-2 being removed from an ear of the user (e.g., based on an assumption that that the user removed an earbud to hear ambient audio better). Pausing media content being played to the user via earbuds 502, as indicated by play button 714 being displayed instead of a pause button as shown in Figure 7I, is not according to the invention and is presented for illustration purposes only.

[0177] Figure 7K illustrates earbud 502-2 placed back in ear 528-2. In response to earbud 502-2 being replaced in ear 528-2, earbuds 502-1 and 502-2 switch from the pass-through mode back to the previous mode, which in this case is the active noise control mode as indicated by active noise control icon 709. Resuming by device 100 media playback, as indicated by pause button 715 being displayed instead of play button 714 as shown in Figure 7J, is not according to the invention and is presented for illustration purposes only.

[0178] Figures 7L-7Q illustrate changes in audio output mode in response to detecting particular types of speech. Figure 7L is an example transition from Figure 7K or Figure 7I. In Figure 7L, user 716, who is wearing earbuds 502-1 and 502-2, is engaged in a conversation with a second individual 717. Figure 7L shows user 716 speaking (e.g., in the form of speech 718). In response to detecting speech 718 by user 716, earbuds 502 switch from the active noise control mode (e.g., as indicated by active noise control icon 709 shown in Figure 7K and Figure 7I) to the pass-through mode, as indicated by pass-through icon 711 in noise management control 707-1. Optionally, as in the example shown in Figure 7L, which is not according to the invention and is present for illustration purposes only, media content playback is paused in response to detecting speech 718, as indicated by play button 714 being displayed instead of pause button 715 (Figure 7K). In some embodiments, in response to detecting speech 718, media content playback is not paused (e.g., continues to be played), although optionally in some embodiments, the volume at which the media content is played is lowered.

[0179] Figure 7M illustrates that earbuds 502 remain in the pass-through mode as the conversation between user 716 and individual 717 continues with response (e.g., speech) 719 from 717. In some embodiments, earbuds 502 remain in the pass-through mode for a predetermined amount of time since detecting speech (e.g., speech 718 by user 716, Figure 7L). In some embodiments, earbuds 502 remain in the pass-through mode (or transition back to the pass-through mode) in response to detecting that user 716 is being spoken to (e.g., in the form of response 719) for the predetermined amount of time.

[0180] Figure 7N shows user 716 and individual 717 no longer engaging in conversation. As a result, earbuds 502 have reverted (e.g., upon a predetermined amount of time elapsing since speech was last detected) to the previous mode, which in this example was the active noise control mode, as indicated by active noise control icon 709 in noise management control 707-1. Optionally, as in the example shown in Figure 7N, which is not according to the invention and is presented for illustration purposes only, where media content playback was paused in response to detecting speech by user 716 (e.g., speech 718, Figure 7L), media content playback is resumed after the conversation ends (e.g., upon a predetermined amount of time elapsing since speech was last detected), as indicated by pause button 715 being displayed in Figure 7N instead of play button 714 (Figure 7M). In some embodiments where media content was not paused in response to detecting speech (e.g., speech 718, Figure 7L), media content playback continues to be played during the conversation as well as after the conversation ends, although optionally in some embodiments where the volume at which the media content is played was lowered (e.g., to a level above zero), the volume is restored (e.g., raised to the same level as before the speech was detected).

[0181] Figure 7O illustrates individual 717 reinitiating conversation with user 716 in the form of speech 720, which begins with user 716's name (e.g., "Delilah"). In response to detecting user 716's name spoken, earbuds 502 switch to the pass-through mode, as indicated by pass-through icon 711 in noise management control 707-1. Optionally, as in the example shown in Figure 7O, which is not according to the invention and is presented for illustration purposes only, media content playback is paused in response to detecting speech 720, as indicated by play button 714 being displayed instead of pause button 715 (Figure 7N).

[0182] Figure 7P illustrates user 716's response 721 to individual 717, while earbuds 502 remain in the pass-through mode (e.g., to make it easier for user 716 to hear and respond to individual 717), as indicated by pass-through icon 711 in noise management control 707-1.

[0183] Figure 7Q shows user 716 and individual 717 no longer engaging in conversation. As a result, earbuds 502 have reverted (e.g., upon a predetermined amount of time elapsing since speech was last detected) to the previous mode, which in this example was the active noise control mode, as indicated by active noise control icon 709 in noise management control 707-1. Optionally, as described herein with reference to Figure 7N, which is not according to the invention and is presented for illustration purposes only, media playback is resumed, as indicated by pause button 715 being displayed in Figure 7Q instead of play button 714 (Figure 7P) or alternatively, media playback volume is restored after having been lowered.

[0184] Figures 8A-8J illustrate example user interactions with earbuds to control audio outputs in accordance with some embodiments. In some embodiments, the earbuds each include a stem (e.g., that extends from the portion of the earbud that is inserted in a user's ear) that the user can use to provide inputs to the earbuds. As shown in Figure 8A, earbud 502-2 includes stem 801. In some embodiments, stem 801 is or includes a pressure-sensitive input device that responds to press inputs applied to stem 801 when held and squeezed between two fingers of hand 802 as illustrated in Figure 8A. Although only one earbud with a stem (e.g., earbud 502-2 with stem 801) is shown, one of ordinary skill will recognize that earbud 502-1 can have an analogous structure with a corresponding stem, and that the same functionality described herein with reference to earbud 502-2 and stem 801 may be available using earbud 502-1 and its corresponding stem as well. Figure 8A also illustrates input 803 received at stem 801 (e.g., a long squeeze gesture that includes a squeeze of stem 801 that is maintained for at least a threshold amount of time) while the current audio output mode of earbuds 502 is the active noise control mode, as indicated by active noise control icon 709 in noise management control 707-1. In some embodiments, an audible tone is output to indicate a "down click," which occurs when intensity of an input received at stem 801 has met or exceeded an input intensity threshold (e.g., associated with squeeze gestures). In some embodiments, an audible tone (e.g., the same or different from the "down click" audible tone) is output to indicate an "up click," which occurs when an input whose intensity has met or exceeded the input intensity threshold has been released so that the input intensity decreases to or below the input intensity threshold. In some embodiments, setting the "down click" intensity threshold to be higher than the "up click" intensity threshold provides hysteresis so that inadvertent fluctuations in input intensity (e.g., due to unsteadiness of a user's fingers when applying pressure to the input device) do not result in the wearable audio output device inadvertently detecting release of the input. In some embodiments, wearable audio output device 301 includes one or more tactile output generators, optionally located in stem 801. In some such embodiments, an activation tactile output is output to indicate a "down click," and / or a release tactile output is output to indicate an "up click." In some embodiments, the activation tactile output is the same (e.g., has the same tactile output amplitude, frequency, and pattern) as the release tactile output. In some embodiments, the activation tactile output is different (e.g., in amplitude, frequency and / or pattern) from the release tactile output (e.g., so the user can differentiate between detection of activation and detection of release).

[0185] Figure 8B illustrates a transition from Figure 8A in response to input 803. In response to input 803 (e.g., and in accordance with a determination that input 803 is a long squeeze gesture), earbuds 502 switch from the active noise control mode to the next audio output mode in a predefined order of audio output modes, which in this example is the bypass mode, as indicated by bypass icon 710 in noise management control 707-1 in Figure 8B. In some embodiments, the predefined order of audio output modes is configurable using a settings menu (e.g., as described herein with reference to Figures 9A-9C). In combination with changing audio output mode, earbuds 502 output an audible tone 806-1 to indicate that the audio output mode has been changed. In some embodiments, the audible tone to indicate that the audio output mode has been changed is different from the audible tone that is output to indicate a "down click" and from the audible tone that is output to indicate an "up click," so that the user can distinguish between different types of operations performed in response to an input. Figure 8B also illustrates a subsequent input 804 (e.g., another long squeeze gesture) at stem 801.

[0186] Figure 8C illustrates a transition from Figure 8B in response to input 804. In response to input 804 (e.g., and in accordance with a determination that input 804 is a long squeeze gesture), earbuds 502 switch from the bypass mode to the next audio output mode in the predefined order, which in this example is the pass-through mode, as indicated by pass-through icon 711 in noise management control 707-1 in Figure 8C. in combination with changing output mode, earbuds 502 output audible tone 806-2 to indicate that the audio output mode has been changed. Figure 8C also illustrates a subsequent input 805 (e.g., another long squeeze gesture) at stem 801.

[0187] Figure 8D illustrates a transition from Figure 8C in response to input 805. In response to input 805 (e.g., and in accordance with a determination that input 805 is a long squeeze gesture), earbuds 502 switch from the pass-through mode to the next audio output mode in the predefined order. In the example shown in Figures 8A-8D, the pass-through mode is the last audio output mode in the predefined order (e.g., the predefined order includes the active noise control mode, followed by the bypass mode, followed by the pass-through mode). Accordingly, earbuds 502 cycle back to the active noise control mode (e.g., in which earbuds 502 were operating as shown in Figure 8A), as indicated by active noise control icon 709 in noise management control 707-1. In addition, Figure 8D illustrates an upward swipe gesture 808 from the bottom of touch screen 112 to dismiss enhanced volume control user interface 705.

[0188] Figure 8E illustrates user interface 700 redisplayed after enhanced volume control user interface 705 is dismissed. User interface 700 is being used to play media content (e.g., music) from album 812 via earbuds 502, as indicated by pause button 715. Figure 8E also shows input 810 at stem 801 of earbud 502-2 (e.g., a short, single squeeze gesture that includes a squeeze of stem 801 that is released within the threshold amount of time (e.g., the same threshold amount of time described with reference to the long squeeze gesture in Figure 8A)).

[0189] Figure 8F illustrates a transition from Figure 8E in response to input 810. In response to input 810 (e.g., and in accordance with a determination that input 810 is a single squeeze gesture), playback of the media content from album 812 is paused, as indicated by play button 714 being displayed in Figure 8F instead of pause button 715 (Figure 8E). Figure 8F also shows a subsequent input 811 (e.g., another single squeeze gesture) at stem 801.

[0190] Figure 8G illustrates a transition from Figure 8F in response to input 811. In response to input 811 (e.g., and in accordance with a determination that input 811 is a single squeeze gesture) playback of the media content from album 812 is resumed, as indicated by pause button 715 being redisplayed in Figure 8G instead of play button 714 (Figure 8F). Figure 8G also shows a subsequent input 813 (e.g., a double squeeze gesture that includes two single squeeze gestures made within a threshold amount of time of each other) at stem 801.

[0191] Figure 8H illustrates a transition from Figure 8G in response to input 813. In response to input 813 (e.g., and in accordance with a determination that input 813 is a double squeeze gesture), device 100 ceases playing the media content from album 812 and skips ahead to the next audio track, which is from album 814 (titled "Album 2"). Functionally, the double squeeze gesture is analogous to a tap gesture on next button 815.

[0192] Figure 8I illustrates the same user interface as Figure 8H, and also shows an input 816 (e.g., a triple squeeze gesture) made by two fingers of hand 802 at the stem 801 of the earbud 502-2.

[0193] Figure 8J illustrates a transition from Figure 8I in response to input 816. In response to input 816 (e.g., and in accordance with a determination that input 816 is a triple squeeze gesture), device 100 ceases playing the media content from album 814 and returns to the previous track, which is from album 812 (titled "Album"). Functionally, the triple squeeze gesture is analogous to a tap gesture on previous button 817.

[0194] Figures 9A-9C illustrate settings user interface 900 for controlling various features associated with earbuds (e.g., earbuds 502) and examples of controlling audio output mode in accordance with some embodiments. In particular, Figure 9A shows settings user interface 900-1, which includes a plurality of activatable control options, such as the following, or a subset or superset thereof: Control option 901, labeled "Disconnect," for disconnecting the earbuds from device 100; Control option 902, labeled "Forget This Device," for dissociating (e.g., unpairing) the earbuds from device 100; Control option 903, labeled "Name," for assigning a name to the earbuds (e.g., "Delilah's Earbuds" in the example shown in Figure 9A); Control option 904, labeled "Click," for assigning a type of operation (e.g., currently the "Play / Pause" operation type) to be performed in response to receiving single click (e.g., herein also called "single squeeze") gestures at an earbud (e.g., using a stem of the earbud); Control option 905, labeled "Double Click," for assigning a type of operation (e.g., currently the "Next Track" operation type) to be performed in response to receiving double click (e.g., herein also called "double squeeze") gestures at an earbud (e.g., using a stem of the earbud); Control option 906, labeled "Click & Hold," for assigning a type of operation (e.g., currently the "Noise Management" operation type) to be performed in response to receiving click-and-hold (e.g., herein also called "long squeeze") gestures at an earbud (e.g., using a stem of the earbud); and Control option 907, labeled "Automatic switching of modes," for controlling automatic switching (e.g., by the earbuds) between different audio output modes.

[0195] In addition, Figure 9A shows input 908 (e.g., a tap gesture) received at control option 906.

[0196] Figure 9B illustrates user interface 900-2 (e.g., a sub-menu of settings user interface 900-1) displayed in response to input 908 (e.g., replacing display of settings user interface 900-1). User interface 900-2 allows the user to select a type of operation to be performed in response to click-and-hold gestures (e.g., on stem 801 or other input device 308 (Figure 3B) of an earbud 502). The options for the type of operation to be performed include the following, or a subset or superset thereof: Option 909, labeled "Siri," selection of which causes click-and-hold gestures to invoke a virtual assistant; Option 910, labeled "Play / Pause," selection of which causes click-and-hold gestures to toggle playback of media content (e.g., music, audio tracks for TV shows or movies, etc.); Option 911, labeled "Next Track," selection of which causes click-and-hold gestures to switch to playing a next audio track (e.g., in a list of audio tracks, such as a playlist or album list); Option 912, labeled "Previous Track," selection of which causes click-and-hold gestures to switch to playing a previous audio track (e.g., in the list of audio tracks); and Option 913, labeled "Noise Management," selection of which causes click-and-hold gestures to switch between selected options for audio output mode listed under option 913, such as: ∘ Active noise control mode option 914, labeled "Active Noise Control," in which the earbuds output one or more audio-cancelling audio components to at least partially cancel ambient sound; ∘ Bypass mode option 915, labeled "Bypass (Off)," in which the earbuds output neither audio-cancelling audio components nor pass-through audio components; and ∘ Pass-through mode option 916, labeled "Active Pass-through," in which the earbuds output one or more pass-through audio components so that the user can hear a greater amount of ambient sound (e.g., a greater amount of ambient sound than would be audible with the passive attenuation of the earbuds placed in the ears).

[0197] In some embodiments, selecting an option above assigns the selected type of operation to the operation of both earbuds in a pair of earbuds (e.g., both earbud 502-1 and 502-2 of earbuds 502). In some embodiments, the two earbuds in a pair of earbuds can be configured (e.g., via settings user interface 900) to perform different operations in response to a particular input gesture.

[0198] Figure 9B shows that option 913 (e.g., "Noise Management") is selected as the type of operation to be performed in response to click-and-hold gestures. Under option 913, all three audio output mode options (e.g., "Active Noise Control," "Bypass (Off)," and "Active Pass-through") are selected. Accordingly, in response to click-and-hold gestures, the audio output mode of the earbuds will cycle through the active noise control mode, the bypass mode, and the active pass-through mode, then looping back to the active noise control mode, etc. In addition, mode options 914, 915, and 916 may be reordered (e.g., by an input on touch screen 112 that includes a long press at a respective option followed by movement of the input to a different position in the list of mode options 914, 915, and 916. For example, the user may reorder the list of mode options such that the bypass mode option precedes the active noise control mode option, which in turn is followed by the active pass-through mode option. In such an example, in response to click-and-hold gestures, the audio output mode of the earbuds will cycle through the bypass mode, the active noise control mode, and the active pass-through mode, then looping back to the bypass mode, etc.

[0199] Additionally, the user can deselect one or more of the mode options 914, 915, and 916 to remove the deselected mode options from the cycle, as described in more detail with reference to Figure 9C as follows.

[0200] Figure 9C illustrates transitions through different audio output modes in response to multiple inputs of a particular type (e.g., click-and-hold gestures in accordance with click-and-hold gestures being configured to control audio output mode (e.g., by being assigned to option 913 as described herein with reference to Figure 9B)) while different combinations of audio output mode options are selected (e.g., one or more of mode options 914 (e.g., "Active Noise Control"), 915 (e.g., "Bypass (Off)"), and 916 (e.g., "Active Pass-through") under option 913 (e.g., "Noise Management") as described herein with reference to Figure 9B). Although only one earbud with a stem (e.g., earbud 502-2 with stem 801) is shown, one of ordinary skill will recognize that earbud 502-1 can have an analogous structure with a corresponding stem, and that the same functionality described herein with reference to earbud 502-2 and stem 801 may be available using earbud 502-1 and its corresponding stem as well. One of ordinary skill will recognize that, alternatively or in addition, some inputs may be received at one earbud, and some inputs may be received at the other earbud. In some embodiments, analogous functionality is available using inputs such as button presses on a designated noise control button (e.g., button 336, Figure 3D) on a wearable audio output device (e.g., a set of headphones such as wearable audio output device 301b, Figure 3D). In some embodiments, each time the audio output mode is changed from one mode to the next, an audible tone 917 is played through earbud 502-1 and / or earbud 502-2 (or through one or both earcups 332 of the headphones, Figure 3D).

[0201] Figure 9C shows four rows and four columns. Each row represents one of four distinct sets of audio output mode selections, labeled "Selections #1" 942, "Selections #2" 943, "Selections #3" 944, and "Selections #4" 945, respectively (e.g., through which earbuds 502 will cycle in response to click-and-hold gestures, also called long squeeze gestures). The selected mode option(s) in a respective set are indicated by checkmarks next to the mode name(s). The first column, labeled "Mode #1" 938 and positioned to the right of initial state indicator 918, indicates the initial audio output mode of earbuds 502. The remaining columns, labeled "Mode #2" 939, "Mode #3" 940, and "Mode #4" 941, indicate the sequence of audio output modes to which earbuds 502 transition after (e.g., in response to) three distinct inputs-first squeeze gesture 919, second squeeze gesture 920, and third squeeze gesture 921 (e.g., click-and-hold gestures)-respectively, each input being associated with the respective column to the right of the respective input. Although a few combinations are shown, one of ordinary skill will recognize that many other combinations of audio output mode selections are possible (e.g., by changing which mode options are selected, how many mode options are selected, and / or the order of the mode options).

[0202] Moving to the first row, labeled "Selections #1" 942, the user has selected all three mode options: the active noise control mode option, the bypass mode option, and the pass-through mode option. Before receiving first squeeze gesture 919, earbuds 502 are in "Mode #1" 938, which in this example is active noise control mode 922. In response to receiving first squeeze gesture 919, earbuds 502 transition from "Mode #1" 938 to "Mode #2" 939-namely, from active noise control mode 922 to bypass mode 923. In response to receiving second squeeze gesture 920, earbuds 502 transition from "Mode #2" 939 to "Mode #3" 940-namely, from bypass mode 923 to pass-through mode 924. In response to receiving third squeeze gesture 921, earbuds 502 transition from "Mode #3" 940 to "Mode #4" 941-namely, from pass-through mode 924 back to active noise control mode 922. Thus, the user has cycled through all three selected mode options.

[0203] Similarly, in embodiments where a set of over-ear headphones (e.g., wearable audio output device 301b, Figure 3D) includes a button for noise control (e.g., button 336, Figure 3D), pressing (or tapping, actuating, etc.) the button transitions the headphones between all three mode options shown in the first row, labeled "Selections #1" 942, of Figure 9C. For example, while the headphones are in "Mode #1" 938 (e.g., active noise control mode 922 in this example), a first button press transitions the headphones from "Mode #1" 938 to "Mode #2" 939 (here, from active noise control mode 922 to bypass mode 923). In response to receiving a second button press, the headphones transition from "Mode #2" 939 to "Mode #3" 940 (here, from bypass mode 923 to pass-through mode 924). In response to receiving a third button press, the headphones transition from "Mode #3" 940 to "Mode #4" 941 (here, from pass-through mode 924 back to active noise control mode 922). Thus, the user has cycled through all three selected mode options.

[0204] Moving to the second row, labeled "Selections #2" 943, the user has selected only two of the three mode options: the active noise control mode option and the bypass mode option (e.g., and not the pass-through mode option). Before receiving first squeeze gesture 919, earbuds 502 are in "Mode #1" 938, which in this example is active noise control mode 926. In response to receiving first squeeze gesture 919, earbuds 502 transition from "Mode #1" 938 to "Mode #2" 939-namely, from active noise control mode 926 to bypass mode 927. In response to receiving second squeeze gesture 920, earbuds 502 transition from "Mode #2" 939 to "Mode #3" 940-namely, from bypass mode 927 back to active noise control mode 926. In response to receiving third squeeze gesture 921, earbuds 502 transition from "Mode #3" 940 to "Mode #4" 941-namely, from active noise control mode 926 back to bypass mode 927. Thus, the user has cycled through both of the selected mode options. Similarly, in embodiments where a set of over-ear headphones (e.g., wearable audio output device 301b, Figure 3D) includes a button for noise control (e.g., button 336, Figure 3D), pressing the button transitions the headphones alternately between the two selected mode options shown in the second row, labeled "Selections #2" 943, of Figure 9C. For example, while the headphones are in "Mode #1" 938 (e.g., active noise control mode 926 in this example), a first button press transitions the headphones from "Mode #1" 938 to "Mode #2" 939 (here, from active noise control mode 926 to bypass mode 927). In response to receiving a second button press, the headphones transition from "Mode #2" 939 to "Mode #3" 940 (here, from bypass mode 927 back to active noise control mode 926). In response to receiving a third button press, the headphones transition from "Mode #3" 940 to "Mode #4" 941 (here, from active noise control mode 926 back to bypass mode 927).

[0205] Moving to the third row, labeled "Selections #3" 944, the user has selected a different two of the three mode options: the active noise control mode option and the pass-through mode option (e.g., and not the bypass mode option). Before receiving first squeeze gesture 919, earbuds 502 are in "Mode #1" 938, which in this example is active noise control mode 930. In response to receiving first squeeze gesture 919, earbuds 502 transition from "Mode #1" 938 to "Mode #2" 939-namely, from active noise control mode 930 to pass-through mode 931. In response to receiving second squeeze gesture 920, earbuds 502 transition from "Mode #2" 939 to "Mode #3" 940-namely, from pass-through mode 931 back to active noise control mode 930. In response to receiving third squeeze gesture 921, earbuds 502 transition from "Mode #3" 940 to "Mode #4" 941-namely, from active noise control mode 930 back to pass-through mode 931. Thus, the user has cycled through both of the selected mode options. Similarly, in embodiments where a set of over-ear headphones (e.g., wearable audio output device 301b, Figure 3D) includes a button for noise control (e.g., button 336, Figure 3D), pressing the button transitions the headphones alternately between the two selected mode options shown in the third row, labeled "Selections #3" 944, of Figure 9C. For example, while the headphones are in "Mode #1" 938 (e.g., active noise control mode 930 in this example), a first button press transitions the headphones from "Mode #1" 938 to "Mode #2" 939 (here, from active noise control mode 930 to pass-through mode 931). In response to receiving a second button press, the headphones transition from "Mode #2" 939 to "Mode #3" 940 (here, from pass-through mode 931 back to active noise control mode 930). In response to receiving a third button press, the headphones transition from "Mode #3" 940 to "Mode #4" 941 (here, from active noise control mode 930 back to pass-through mode 931).

[0206] Finally, moving to the fourth row, labeled "Selections #4" 945, the user has selected only one of the three mode options: the bypass mode option. Before receiving first squeeze gesture 919, earbuds 502 are in "Mode #1" 938, which in this example is bypass mode 934. In response to receiving first squeeze gesture 919, because only one mode option has been selected, earbuds 502 remain in bypass mode 934 (e.g., "Mode #1" 938 and "Mode #2" 939 are the same). Similarly, in response to receiving second squeeze gesture 920, earbuds 502 remain in bypass mode 934 (e.g., "Mode #2" 939 and "Mode #3" 940 are also the same). Likewise, in response to receiving third squeeze gesture 921, earbuds 502 remain in bypass mode 934 (e.g., "Mode #3" 940 and "Mode #4" 941 are the same). Thus, so long as only one audio output mode option is selected, the squeeze gestures do not change the audio output mode in which earbuds 502 operate. Similarly, in embodiments where a set of over-ear headphones (e.g., wearable audio output device 301b, Figure 3D) includes a button for noise control (e.g., button 336, Figure 3D), if only one audio output mode has been selected (e.g., bypass mode 934), the headphones operate in the selected audio output mode, and pressing the button does not change the audio output mode in which the headphones operate.

[0207] Figures 10A-10H are flow diagrams illustrating method 1000 of pairing and calibrating wearable audio output devices in accordance with some embodiments. Method 1000 is performed at a computer system (e.g., portable multifunction device 100 in Figure 1A, or device 300 in Figure 3A) that includes a display device (e.g., touch-sensitive display system 112 in Figure 1A or display 340 in Figure 3A) and a touch-sensitive surface (e.g., touch-sensitive display system 112 in Figure 1A or touchpad 355 in Figure 3A). Some operations in method 1000 are, optionally, combined and / or the order of some operations is, optionally, changed.

[0208] As described below, method 1000 provides an improved interface for pairing and calibrating wearable audio output devices (e.g., headphones) to a display device (e.g., a smartphone, tablet, or personal computer) in a computer system, so as to optimize the fit and thereby optimize the audio experience of the wearable audio output devices. During the pairing and calibration process, a user is prompted to place the wearable audio output devices in his or her ears, a calibration tone is output via the wearable audio output devices, and a fit of the wearable audio output devices is determined based on whether audio that is detected while outputting the calibration tone meets particular criteria. If the detected audio does not meet the particular criteria, the user is prompted to adjust (e.g., one or both of) the wearable audio output devices. Displaying, on the display device, prompts related to placement and adjustment of the wearable audio output devices guides the user through the pairing and calibration process and provides the user at various points during the process with visual feedback as to actions to perform, whether the process is being performed properly, and / or whether the wearable audio output devices are properly fitted. Providing improved feedback to the user enhances the operability of the computer system and associated devices (e.g., the wearable audio output devices and / or the display device) and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently. In addition, improving the fit of the wearable audio output devices improves the seal between the wearable audio output devices and the user's ears, which enables audio to be played at a lower volume to produce the same effective audio volume perceived by the user (e.g., relative to when the wearable audio output devices are not properly fitted, in which case hearing some ambient noise may cause the user to increase the audio output volume), thereby further reducing power usage and improving battery life of the devices.

[0209] The method includes, establishing 1004 a wireless connection with a pair of wearable audio output devices that includes: a first wearable audio output device (e.g., an earbud or earphone that in some embodiments is one of a pair (e.g., earbuds 502-1 and 502-2 in Figure 5A) with one or more first microphones, and a second wearable audio output device (e.g., an earbud or earphone that in some embodiments is one of a pair) with one or more second microphones. In some embodiments, the first wearable audio output device includes one or more first sensors for detecting placement of the first wearable audio output device; and in some embodiments, the second wearable audio output device includes one or more second sensors for detecting placement of the second wearable audio output device (e.g., microphones 302-1 and 302-2 in Figure 3C).

[0210] In some embodiments, after establishing (1006) the wireless connection with the pair of wearable audio output devices, displaying, via the display device, a user interface object that prompts the user to place the first wearable audio output device in an ear of the user and to place the second wearable audio output device in an ear of the user. In some embodiments, the display device may display a visual indicator that the audio output devices are not placed in the ears of the user, as shown by status indicators 529-1 and 529-2 in Figures 5F-5U.

[0211] Displaying, on the display device, a prompt to the user to place the wearable audio output devices in his or her ears provides the user with visual feedback as to an action to perform to advance the pairing and calibration process. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

[0212] The method 1000 includes, detecting (1008) (e.g., via the one or more first sensors) that the first wearable audio output device has been placed in an ear of a user. In some embodiments, the user (e.g., the wearer of the wearable audio output device(s)) is a user of the computer system, as shown in Figures 7L-7Q. The method 1000 further includes, detecting 1010 (e.g., via the one or more second sensors) that the second wearable audio output device has been placed in an ear of the user.

[0213] The method 1000 includes, after (e.g., in response to) detecting 1012 that the first wearable audio output device has been placed in an ear of the user and that the second wearable audio output device has been placed in an ear of the user: In some embodiments, the operations that follow are performed in response to detecting that the first wearable audio output device has been placed in an ear of the user and that the second wearable audio output device has been placed in an ear of the user. In some embodiments, the operations that follow are performed after detecting that the first wearable audio output device has been placed in an ear of the user and that the second wearable audio output device has been placed in an ear of the user, and in response to an intervening trigger or input (e.g., a user input indicating that the user wants to proceed with calibration of the first and second wearable audio output devices, as shown in Figure 5E where the user provides an input 526-1 over the button to begin the test 525-1).

[0214] Figure 10B illustrates the method 1000 continuing from section B in Figure 10A. The method 1000 includes outputting 1014 a first calibration tone via the first wearable audio output device and the second wearable audio output device. In some embodiments, the outputting 1016 of the calibration tone via the first wearable audio output device and the second wearable audio output device occurs (e.g., automatically) in response to detecting that the first wearable audio output device has been placed in an ear of the user and that the second wearable audio output device has been placed in an ear of the user. In some embodiments, the automatic output of the calibration tone occurs each time both wearable audio output devices are placed in the ears of the user during setup (e.g., as illustrated by animation 530 in Figure 5P).

[0215] Outputting the calibration tone in response to detecting placement of the wearable audio output devices in the user's ears progresses the calibration process without requiring the user to provide further input. Performing an operation (e.g., automatically) when a set of conditions has been met without requiring further user input reduces the number of inputs needed to perform the operation, which enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

[0216] In some embodiments, a length of the calibration tone is determined (e.g., adjusted) based on whether the detected first and second audio satisfy the device fit criteria associated with the calibration tone 1018. In some embodiments, audio is detected (e.g., sampled) via the microphones of the first and second wearable audio output devices one or more times during the calibration tone. In some embodiments, the calibration tone continues to be output until the amount of audio other than the calibration tone in a respective detected audio sample is less than a threshold amount (e.g., as described herein with reference to operation 1024 of method 1000). In some embodiments, the calibration tone continues to be output until the amount of audio other than the calibration tone in the detected audio converges or plateaus (e.g., is less than a threshold amount for at least a threshold number of times). In some embodiments, the length of the calibration tone may be determined based on the number of attempts that have been made to satisfy the device fit criteria.

[0217] Dynamically varying the length of the calibration tone based on how long it takes to determine whether the detected audio meets particular criteria indicating that the wearable audio output devices are properly fitted reduces the number of times that the calibration needs to be repeated due to inconclusive test results during a fixed-length calibration. Reducing the number of inputs needed to perform an operation enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

[0218] The method includes detecting 1020 first audio via the one or more first microphones of the first wearable audio output device (e.g., while outputting the first calibration tone, as illustrated by the animation 530 in Figure 5H). The method also includes, detecting 1022 second audio via the one or more second microphones of the second wearable audio output device (e.g., while outputting the first calibration tone, as illustrated by the animation 530 in Figure 5H).

[0219] The method of claim 1000 includes, in accordance with a determination that the detected first audio does not satisfy device fit criteria (e.g., criteria associated with a quality of a seal formed by the device with the user's ear, which is shown in the sequence of Figures 5I to 5V where the user performs multiple adjustments in response to not satisfying the fit test) associated with the first calibration tone, displaying, via the display device, an alert prompting the user to perform an adjustment of the first wearable audio output device; and in accordance with a determination that the detected second audio does not satisfy the device fit criteria associated with the first calibration tone, displaying, via the display device, an alert prompting the user to perform an adjustment of the second wearable audio output device 1024.

[0220] In some embodiments, determining whether respective detected audio meets device fit criteria includes comparing the detected audio to the calibration tone and determining that the detected audio includes less than a threshold amount of audio (e.g., 50dB, 40dB, 30dB, 25dB, or 20dB) other than the calibration tone. In some embodiments, in accordance with a determination that the detected first audio does not satisfy the device fit criteria and / or the detected second audio does not satisfy the device fit criteria (e.g., in accordance with a determination that at least one of the pair of wearable audio output devices does not satisfy the device fit criteria), an alert is displayed prompting the user to perform an adjustment to the pair of wearable audio output devices (e.g., to both the first wearable audio output device and the second wearable audio output device, without identifying a particular device to which to perform the adjustment, which is illustrated as instruction 610 in Figure 6B). In some embodiments, the user is prompted to perform different actions for different wearable audio output devices of the pair (e.g., Figures 5I-5V where the user is prompted to fix only the earbud 502-2 in the ear of the user 528-2. In some embodiments, the user is prompted to reposition a respective wearable audio output device in an ear of the user and / or change a respective attachment that is coupled to the respective wearable audio output device to a different attachment (e.g., Figure 5M-5N where the user switches the eartip 527-2 to a larger eartip 527-3). In some embodiments, in accordance with a determination that a respective wearable audio output device satisfies the device fit criteria, the computer system forgoes displaying an alert prompting the user to perform an adjustment (e.g., changing attachment or repositioning) to the wearable audio output device. (e.g., as shown in Figure 6A)

[0221] In some embodiments after displaying the alert(s) prompting the user to perform adjustment(s) of the wearable audio output device(s), the computer system detects that the user has performed the adjustment(s), for example by detecting that the wearable audio output device(s) have been placed (e.g., removed and subsequently replaced) in the user's ear(s). In some embodiments, for a respective wearable audio output device that has been replaced in an ear of the user, the computer system detects that the user has performed the adjustment by detecting that an attachment to the respective wearable audio output device has been changed (e.g., from a previously-detected attachment to a currently-detected attachment).

[0222] Figure 10C continues from method flow block 1012. In some embodiments, displaying 1026, via the display device, a status indicator, wherein the status indicator indicates whether detecting placement of the first wearable audio output device in an ear of the user and placement of the second wearable audio output device in an ear of the user (e.g., in-ear detection of the wearable audio output devices) (e.g., by the computer system) is enabled. In some embodiments, the user has the option to turn off (e.g., disable) the in-ear-detection, in which case the computer system will not detect whether the first and second wearable audio devices are placed in the ears of the user, and, in some such cases, the first and second wearable audio output devices continue to operate in the same manner (e.g., perform the same functions) regardless of whether or not the first and second wearable audio output devices are placed in the ears of the user (e.g., Figures 9A-9C, where the user can select which modes to enable or disable).

[0223] Displaying, on the display device, a status indicator that indicates whether detection of placement of the wearable audio output devices in respective ears of the user (sometimes called "in-ear detection") is enabled provides visual feedback to the user indicating a relevant state of the computer system during the pairing and calibration process. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

[0224] In some embodiments, after (e.g., in response to) detecting 1028 that the first wearable audio output device has been placed in an ear of the user and that the second wearable audio output device has been placed in an ear of the user, displaying, via the display device, a user interface object for initiating a fit test. The fit test optimizes (e.g., or assists the user in optimizing) a fit of the first wearable audio output device in an ear of the user and a fit of the second wearable audio output device in an ear of the user.

[0225] Displaying, on the display device, a user interface object that is selectable to initiate a fit test (e.g., to proceed with calibration following pairing) of the wearable audio output devices after or in response to detecting that the wearable audio output devices have been placed in the user's ears provides visual feedback to the user acknowledging the placement of the wearable audio output devices in the user's ears and facilitating performance of the next action in the calibration process. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently. In addition, improving the fit of the wearable audio output devices improves the seal between the wearable audio output devices and the user's ears, which enables audio to be played at a lower volume to produce the same effective audio volume perceived by the user (e.g., relative to when the wearable audio output devices are not properly fitted, in which case hearing some ambient noise may cause the user to increase the audio output volume), thereby further reducing power usage and improving battery life of the devices.

[0226] In some embodiments, the method 1000 includes displaying (1030), via the display device: a first indication that the first wearable audio output device has been placed in an ear of the user (e.g., in response to detecting that the first wearable audio output device has been placed in an ear of the user (e.g., status indicator 529-1 in Figures 5I-5V)); and a second indication that the second wearable audio output device has been placed in an ear of the user (e.g., in response to detecting that the first wearable audio output device has been placed in an ear of the user(e.g., status indicator 529-2 in Figures 5I-5V)).

[0227] In some embodiments displaying a respective indication that a respective wearable audio output device has been placed in an ear of the user includes displaying a user interface object that indicates that the respective wearable audio output device has been placed in an ear of the user. In some embodiments, displaying the respective indication includes changing an appearance of a respective user interface object (e.g., that is already displayed) that represents the respective wearable audio output device, wherein the change in appearance indicates the placement of the respective wearable audio output device in an ear of the user. In some embodiments, the user interface object is a colored indicator (e.g., a black or yellow circle, as shown in Figures 5I as status indicators 529-1 and 529-2). In some embodiments, the change in appearance of the user interface object includes a change in color (e.g., from gray to black, as shown in Figures 5F-5G) of the user interface object. In some embodiments, the user interface object includes an indication as to which wearable audio output device the user interface object represents (e.g., a user interface object for a left earbud includes the letter 'L', whereas a user interface object for a right earbud includes the letter 'R', as shown in Figure 5F). In some embodiments, the user interface object also signifies whether the fit criteria was satisfied. In such an embodiment, when the fit criteria is satisfied, a different visual indicator is displayed (e.g., an appearance of the visual indicator is changed) (e.g., a green circle or a green circle with a checkmark within it, wherein the checkmark indicates that the wearable audio output device is in an ear of the user, as shown in Figure 5J). If a user removes the audio device from their ear, a third visual indicator (e.g., a gray circle, as shown in Figure 5M) is shown to indicate that the audio device has been removed from the user's ear.) Furthermore, in some embodiments, when a use has initially placed the wearable audio output device in the ear of the user, but before the electronic device determines if the fit criteria have been satisfied, the visual indicator will be black, and only once the device fit criteria has begun to be analyzed and / or has finished analyzing will the circles change to a yellow and / or green color.

[0228] Displaying indications that the wearable audio output devices have been placed in the user's ears provides visual feedback to the user indicating that the placement of the wearable audio output devices in the user's ears has been detected and acknowledged. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

[0229] In some embodiments, after detecting 1032 that the first wearable audio output device has been placed in an ear of the user and that the second wearable audio output device has been placed in an ear of the user, displaying, via the display device, a user interface illustrating that the calibration tone is being played.

[0230] Transitioning to a next screen in the pairing and calibration process when the wearable audio output devices have been placed in the user's ears progresses the calibration process without requiring the user to provide further input. Performing an operation (e.g., automatically) when a set of conditions has been met without requiring further user input reduces the number of inputs needed to perform the operation, which enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

[0231] Figures 10D and 10E both depend from method flow block 1024 in Figure 10B. The method 1000 includes, in some embodiments that the adjustment of a respective wearable audio output device includes repositioning 1034 the respective wearable audio output device in an ear of the user. In some embodiments, repositioning of a respective wearable audio output device is detected via one or more placement sensors on the respective wearable audio output device (e.g., as shown in Figures 5G-5I where the earbud 502-2 is not aligned in the ear, but corrected after the user has been alerted to its misalignment). In some embodiments, the attachment is a grommet that attaches to the wearable audio output device (e.g., a silicone ear-tip attachment on a pair of earbuds for creating a seal around the user's ear, which is illustrated in Figure 5M-5N when the user swaps out the eartips).

[0232] Prompting the user to reposition the wearable audio output devices in his or her ears provides the user with visual feedback as to an action to perform to advance the pairing and calibration process and improve the fit of the wearable audio output devices. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently. In addition, improving the fit of the wearable audio output devices improves the seal between the wearable audio output devices and the user's ears, which enables audio to be played at a lower volume to produce the same effective audio volume perceived by the user (e.g., relative to when the wearable audio output devices are not properly fitted, in which case hearing some ambient noise may cause the user to increase the audio output volume), thereby further reducing power usage and improving battery life of the devices.

[0233] In some embodiments, the first wearable audio output device is coupled to a first attachment (e.g., a first eartip), and the second wearable audio output device is coupled to a second attachment (e.g., a second eartip), and the method further includes: after (e.g., in response to) detecting repositioning of the first wearable audio output device and the second wearable audio output device: outputting a second calibration tone via the first wearable audio output device and the second wearable audio output device; detecting third audio via the one or more first microphones of the first wearable audio output device; detecting fourth audio via the one or more second microphones of the second wearable audio output device; in accordance with a determination that the detected third audio does not satisfy device fit criteria associated with the second calibration tone, displaying, via the display device, an alert prompting the user to change the first attachment that is coupled to the first wearable audio output device to a third attachment ; and in accordance with a determination that the detected fourth audio does not satisfy the device fit criteria associated with the second calibration tone, displaying, via the display device, an alert prompting the user to change the second attachment that is coupled to the second wearable audio output device to a fourth attachment. In some embodiments, the reposition prompt is displayed before any attachment is added or removed from the audio output devices, as shown in Figure 5I.

[0234] Prompting the user first to reposition the wearable audio output devices before prompting the user to change attachments, such as the eartips, on the wearable audio output devices provides the user with visual feedback as to a preferred order in which actions that are part of the pairing and calibration process should be performed to improve the fit of the wearable audio output devices. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently. In addition, improving the fit of the wearable audio output devices improves the seal between the wearable audio output devices and the user's ears, which enables audio to be played at a lower volume to produce the same effective audio volume perceived by the user (e.g., relative to when the wearable audio output devices are not properly fitted, in which case hearing some ambient noise may cause the user to increase the audio output volume), thereby further reducing power usage and improving battery life of the devices.

[0235] In some embodiments of method 1000, the adjustment of a respective wearable audio output device includes changing 1038 a respective attachment that is coupled to the respective wearable audio output device to a different attachment. (e.g., an ear-tip to seal the earphone or earbud with the user's ear, which may help to maintain the placement of the earphone or earbud within the user's ear during movement, which is illustrated in Figures 5M-5N where the portable electronic device prompts the user to move to a larger eartip size.)

[0236] Prompting the user to change attachments, such as the eartips, on the wearable audio output devices provides the user with visual feedback as to an action to perform to advance the pairing and calibration process and improve the fit of the wearable audio output devices. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently. In addition, improving the fit of the wearable audio output devices improves the seal between the wearable audio output devices and the user's ears, which enables audio to be played at a lower volume to produce the same effective audio volume perceived by the user (e.g., relative to when the wearable audio output devices are not properly fitted, in which case hearing some ambient noise may cause the user to increase the audio output volume), thereby further reducing power usage and improving battery life of the devices.

[0237] In some embodiments the method determines whether the adjustment of a respective wearable audio output device includes changing 1040 a respective attachment that is coupled to the respective wearable audio output device with a different attachment or repositioning the respective wearable audio output device in an ear of the user is based on a manner in which the respective detected audio does not satisfy the device fit criteria. In some embodiments, the attachment is a grommet that attaches to the wearable audio output device (e.g., a silicone ear-tip attachment on a pair of earbuds for creating a seal around the user's ear, as shown in eartip 527-2 and 527-3 in Figures 5M-5N).

[0238] Determining whether to suggest repositioning of the wearable audio output devices or changing attachments based on the results of the calibration test reduces the number of adjustments that the user needs to perform, thereby helping the user progress through the pairing and calibration process and achieve a good fit of the wearable audio output devices more quickly. Providing improved feedback to the user and reducing the number of inputs needed and time spent performing the pairing and calibration process enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently. In addition, improving the fit of the wearable audio output devices improves the seal between the wearable audio output devices and the user's ears, which enables audio to be played at a lower volume to produce the same effective audio volume perceived by the user (e.g., relative to when the wearable audio output devices are not properly fitted, in which case hearing some ambient noise may cause the user to increase the audio output volume), thereby further reducing power usage and improving battery life of the devices.

[0239] The method 1000 includes, in some embodiments, determining whether the adjustment of a respective wearable audio output device includes replacing 1042 a respective attachment that is coupled to the respective wearable audio output device with a larger attachment or a smaller attachment (e.g., than the respective attachment) is based on a manner in which the respective detected audio (e.g., detected via the one or more microphones of the respective wearable audio output device, as shown by microphones in Figure 3C) does not satisfy the device fit criteria.

[0240] Determining whether to suggest changing attachments to the wearable audio output devices to larger or smaller size attachments based on the results of the calibration test reduces the number of adjustments that the user needs to perform, thereby helping the user progress through the pairing and calibration process and achieve a good fit of the wearable audio output devices more quickly. Providing improved feedback to the user and reducing the number of inputs needed and time spent performing the pairing and calibration process enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently. In addition, improving the fit of the wearable audio output devices improves the seal between the wearable audio output devices and the user's ears, which enables audio to be played at a lower volume to produce the same effective audio volume perceived by the user (e.g., relative to when the wearable audio output devices are not properly fitted, in which case hearing some ambient noise may cause the user to increase the audio output volume), thereby further reducing power usage and improving battery life of the devices.

[0241] Transitioning to Figure 10F, which flows from block 1024, in some embodiments, includes that in accordance with a determination that the detected first audio satisfies the device fit criteria associated with the calibration tone, displaying 1044, via the display device, an indication that the first wearable audio output device is fitted to an ear of the user; and in accordance with a determination that the detected second audio satisfies the device fit criteria associated with the calibration tone, displaying, via the display device, an indication that the second wearable audio output device is fitted to an ear of the user.

[0242] In some embodiments, displaying a respective indication that a respective wearable audio output device has been placed in an ear of the user includes displaying a user interface object that indicates that the respective wearable audio output device has been placed in an ear of the user (e.g., Figure 5F showing status indicators 529-1 and 529-2 in the gray color indicating that earbuds are not placed in the ears, and Figure 5G showing the status indicators 529-1 and 529-2 in the black color denoting that they have been placed in the ears of the user). In some embodiments, displaying the respective indication includes changing an appearance of a respective user interface object (e.g., that is already displayed) that represents the respective wearable audio output device, wherein the change in appearance indicates the placement of the respective wearable audio output device in an ear of the user. In some embodiments, the user interface object is a colored indicator (e.g., Figure 5F showing status indicators 529-1 and 529-2 in the gray color indicating that earbuds are not placed in the ears, and Figure 5G showing the status indicators 529-1 and 529-2 in the black color denoting that they have been placed in the ears of the user). In some embodiments, the change in appearance of the user interface object includes a change in color (e.g., from gray to black, as shown in Figures 5F-5G) of the user interface object. In some embodiments, the user interface object includes an indication as to which wearable audio output device the user interface object represents (e.g., a user interface object for a left earbud includes the letter 'L', whereas a user interface object for a right earbud includes the letter 'R,' which is shown in Figures 5F-5G). In some embodiments, the user interface object also signifies whether the fit criteria was satisfied. In such an embodiment, when the fit criteria is satisfied, a different visual indicator is displayed (e.g., an appearance of the visual indicator is changed) (e.g., a green circle or a green circle with a checkmark within it, wherein the checkmark indicates that the wearable audio output device is in an ear of the user, as shown in Figure 5H by status indicator 529-1). If a user removes the audio device from their ear, a third visual indicator (e.g., a gray circle, as shown by 529-2 in Figure 5M being a gray color when the user removes the earbud 502-2 to change out the eartips) is shown to indicate that the audio device has been removed from the user's ear.) Furthermore, In some embodiments, when a user has initially placed the wearable audio output device in the ear of the user, but before the electronic device determines if the fit criteria have been satisfied, the visual indicator will be black, and only once the device fit criteria has begun to be analyzed and / or has finished analyzing will the circles change to a yellow and / or green color (e.g., Figures 5H-5I where status indicator 529-2 transitions from a solid back background to a hashed background (or a yellow background).

[0243] Displaying, on the display device, an indication that the wearable audio output devices are fitted to the user's ears provides visual feedback to the user about the fit of the wearable audio output devices and indicating that the pairing and calibration process has been successfully completed. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently. In addition, when the wearable audio output devices are fitted to the user's ears, the seal between the wearable audio output devices and the user's ears enables audio to be played at a lower volume to produce the same effective audio volume perceived by the user (e.g., relative to when the wearable audio output devices are not properly fitted, in which case hearing some ambient noise may cause the user to increase the audio output volume), thereby further reducing power usage and improving battery life of the devices.

[0244] In some embodiments, method 1000 includes displaying 1046 the alert prompting the user to perform an adjustment of the first wearable audio output device (e.g., in accordance with the determination that the detected first audio does not satisfy the device fit criteria) is performed independently of whether the detected second audio satisfies the device fit criteria; and displaying the alert prompting the user to perform an adjustment of the second wearable audio output device (e.g., in accordance with the determination that the detected second audio does not satisfy the device fit criteria) is performed independently of whether the detected first audio satisfies the device fit criteria.

[0245] In some embodiments the prompted adjustment of the first wearable audio output device is a first type of adjustment (e.g., repositioning in the user's ear), and no adjustment is prompted for the second wearable audio output device or the type of adjustment prompted for the second wearable audio output device is a different type of adjustment from the first adjustment (e.g., the type of adjustment prompted for the second wearable audio output device is a second type of adjustment, such as changing an attachment such as an eartip for the second wearable audio output device). In some embodiments, a status indicator (e.g., a green circle with a checkmark indicating that the fit test criteria was met) is presented for one of the wearable audio output devices, and a different status indicator (e.g., a yellow circle with a checkmark indicating that the fit test criteria was met) is presented for the other wearable audio output device as shown in Figure 5I-5J.

[0246] Determining whether adjustment is needed and prompting the user to perform an adjustment for one of the wearable audio output devices separately from the other wearable audio output device (e.g., for a pair of wearable audio output devices) provides visual feedback to the user indicating which wearable audio output device(s) in particular need adjustment, which may reduce the number of adjustments that the user needs to perform, thereby helping the user progress through the pairing and calibration process and achieve a good fit of the wearable audio output devices more quickly. Providing improved feedback to the user and reducing the number of inputs needed and time spent performing the pairing and calibration process enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently. In addition, improving the fit of the wearable audio output devices improves the seal between the wearable audio output devices and the user's ears, which enables audio to be played at a lower volume to produce the same effective audio volume perceived by the user (e.g., relative to when the wearable audio output devices are not properly fitted, in which case hearing some ambient noise may cause the user to increase the audio output volume), thereby further reducing power usage and improving battery life of the devices.

[0247] Figure 10G includes additional optional method features stemming from flow box 1038 in Figure 10D. In some embodiments, the first wearable audio output device is coupled to a first attachment (e.g., a first eartip) while detecting 1048 the first audio, and the second wearable audio output device is coupled to a second attachment (e.g., a second eartip) while detecting the second audio, and the method further includes: in accordance with the determination that the detected first audio does not satisfy the device fit criteria and in accordance with the determination that the detected second audio does not satisfy the device fit criteria: after (e.g., in response to) detecting that the first attachment coupled to the first wearable audio output device is changed to a third attachment and that the second attachment coupled to the second wearable audio output device is changed to a fourth attachment: outputting a second calibration tone via the first wearable audio output device and the second wearable audio output device; detecting third audio via the one or more first microphones of the first wearable audio output device; detecting fourth audio via the one or more second microphones of the second wearable audio output device; in accordance with a determination that the detected third audio does not satisfy device fit criteria associated with the second calibration tone: determining whether the detected first audio or the detected third audio came closer to satisfying the device fit criteria; and displaying, via the display device, an alert prompting the user to use a respective attachment of the first attachment and the third attachment that came closer to satisfying the device fit criteria; in accordance with a determination that the detected fourth audio does not satisfy the device fit criteria associated with the second calibration tone: determining whether the detected second audio or the detected fourth audio came closer to satisfying the device fit criteria; and displaying, via the display device, an alert prompting the user to use a respective attachment of the second attachment and the fourth attachment that came closer to satisfying the device fit criteria. In some embodiments, the computer system uses data retrieved from the first attempt to satisfy the device fit criteria (e.g., the calibration attempt while using the first and second attachments).

[0248] When calibration has been attempted with multiple attachments (e.g., eartips), prompting the user to use the attachments that came closest to satisfying the device fit criteria provides visual feedback to the user indicating which attachments will provide the best possible audio experience even when none of the attachments outright satisfy the device fit criteria. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently. In addition, improving the fit of the wearable audio output devices improves the seal between the wearable audio output devices and the user's ears, which enables audio to be played at a lower volume to produce the same effective audio volume perceived by the user (e.g., relative to when the wearable audio output devices are not properly fitted, in which case hearing some ambient noise may cause the user to increase the audio output volume), thereby further reducing power usage and improving battery life of the devices.

[0249] Figure 10H includes additional optional method features stemming from flow box 1038 in Figure 10D. In some embodiments, after detecting that the first wearable audio output device has been replaced in (e.g., after being removed from) an ear of the user, and that the second wearable audio output device has been replaced in (e.g., after being removed from) an ear of the user, displaying, via the display device, a user interface that includes a user interface object that, when selected, causes the computer system to: output a second calibration tone via the first wearable audio output device and the second wearable audio output device; detect third audio via the one or more first microphones of the first wearable audio output device; detect fourth audio via the one or more second microphones of the second wearable audio output device; in accordance with a determination that the detected second audio does not satisfy device fit criteria (e.g., criteria associated with a quality of a seal formed by the device with the user's ear) associated with the second calibration tone, display, via the display device, an alert prompting the user to perform an adjustment of the first wearable audio output device; and in accordance with a determination that the detected third audio does not satisfy the device fit criteria associated with the second calibration tone, display, via the display device, an alert prompting the user to perform an adjustment of the second wearable audio output device.

[0250] In some embodiments, determining whether respective detected audio meets device fit criteria includes comparing the detected audio to the calibration tone and determining that the detected audio includes less than a threshold amount of audio (e.g., 50dB, 40dB, 30dB, 25dB, or 20dB) other than the calibration tone. In some embodiments, when the user selects the second user interface object, the device will use previously detected audio to satisfy the device fit criteria.

[0251] After detecting that the wearable audio output devices have been replaced in the user's ears, providing a user interface object to re-output the calibration tone and repeat the calibration process provides the user with visual feedback as to a next action to be performed as part of the pairing and calibration process and reduces the number of inputs needed for the user to perform this next action. Providing improved feedback to the user and reducing the number of inputs needed to perform an operation enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

[0252] It should be understood that the particular order in which the operations in Figures 10A-10H have been described is merely an example and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., methods 1100, 1200, 1800, 1900, 2000, 2400, and 2600) are also applicable in an analogous manner to method 1000 described above with respect to Figures 10A-10H. For example, the devices, user interfaces, audio outputs, audio output modes, alerts, adjustments, and attachments described above with reference to method 1000 optionally have one or more of the characteristics of the devices, user interfaces, audio outputs, audio output modes, alerts, adjustments, and attachments described herein with reference to other methods described herein (e.g., methods 1100, 1200, 1800, 1900, 2000, 2400, and 2600). For brevity, these details are not repeated here.

[0253] Figures 11A-11D are flow diagrams illustrating method 1100 of monitoring the fit of wearable audio output devices during use (e.g., outside of a setup user interface) in accordance with some embodiments. Method 1000 is performed a computer system (e.g., portable multifunction device 100 in Figure 1A, or device 300 in Figure 3A) that includes a display device (e.g., touch-sensitive display system 112 in Figure 1A or display 340 in Figure 3A) and that is in communication with one or more wearable audio output devices (e.g., wearable audio output device 301, Figure 3B), wherein the computer system is configured to execute a plurality of applications (e.g., applications 136 in Figure 1A), and the one or more wearable audio output devices include one or more sensors for detecting placement of the one or more wearable audio output devices (e.g., placement sensor(s) 304, Figure 3B) and one or more microphones (e.g., microphone(s) 302, Figure 3B). Some operations in method 1100 are, optionally, combined and / or the order of some operations is, optionally, changed.

[0254] As described below, method 1100 provides an improved interface for optimizing the audio experience by intelligently suggesting adjustments to the wearable audio output devices (e.g., headphones) while the user is using the wearable audio output devices (e.g., outside of a pairing and calibration process) in response to detecting that the wearable audio devices no longer satisfy device fit criteria, which provides visual feedback to the user indicating that issues with the wearable audio output devices that may affect the audio experience have been detected and helping the user to improve the fit of the wearable audio output devices. Providing improved feedback to the user enhances the operability of the computer system and associated devices (e.g., the wearable audio output devices and / or the display device) and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently. In addition, improving the fit of the wearable audio output devices improves the seal between the wearable audio output devices and the user's ears, which enables audio to be played at a lower volume to produce the same effective audio volume perceived by the user (e.g., relative to when the wearable audio output devices are not properly fitted, in which case hearing some ambient noise may cause the user to increase the audio output volume), thereby further reducing power usage and improving battery life of the devices.

[0255] The method 1100 includes, while the one or more wearable audio output devices are in one or more respective positions relative to a user's ears, and while a media presentation application on the computer system is being used to play media via the one or more wearable audio output devices without displaying a settings user interface for configuring a fit of the one or more wearable audio output devices 1104.

[0256] The method 1100 also includes providing 1106, via the one or more wearable audio output devices, audio output based on media from the media presentation application, wherein the media presentation application is separate from the settings user interface; In some embodiments, the computer system also monitors (e.g., continually or at repeated intervals) audio detected via one or more microphones (e.g., as shown by microphones 302 in Figure 3C) on the one or more wearable audio output devices to determine whether the one or more wearable audio output devices satisfy the device fit criteria.

[0257] Furthermore, the method 1100 includes, determining 1108, based on the audio output based on the media from the media presentation application, that the one or more wearable audio output devices have ceased to satisfy device fit criteria; and in response to determining that the one or more wearable audio output devices have ceased to satisfy the device fit criteria, displaying 1110, on the display device, an alert corresponding to (e.g., including) information about a fit of the one or more wearable audio output devices. In some embodiments, in accordance with a determination that the user is not in a respective predefined context (e.g., the user is in a context other than one or more predefined contexts in which device fit is monitored, such as a workout application shown in Figures 6A-6L), the computer system does not display, on the display device (e.g., as shown in Figure 6A), an alert to prompt the user to perform an adjustment of the one or more wearable audio output devices despite determining, based on the audio output based on the media from the media presentation application, that the one or more wearable audio output devices have ceased to satisfy the device fit criteria.

[0258] Referring to Figure 11B, which stems from method block 1106 in Figure 11A, optionally, one or more audio properties of the audio output based on the media from the media presentation application are the same as one or more audio properties of a calibration tone that is used for configuring the fit of the one or more wearable audio output devices (e.g., via the settings user interface as shown in Figure 9A-9B). Stated another way, in some embodiments the audio output based on the media from the media presentation application has, for at least a short period of time, a similar sound profile (e.g., frequency profile) to the calibration tone. Alternatively, the audio output based on the media has, for at least the short period of time, sufficient energy in an audio frequency band corresponding to that of the calibration tone, to be used as the equivalent of the calibration tone.

[0259] Performing calibration while a user is using the wearable audio output devices to listen to audio (e.g., outside of the pairing and calibration process) efficiently monitors the fit of the wearable audio output devices and enables providing the user with feedback about the fit without interrupting the audio experience, and without requiring the user to separately navigate to the settings user interface to initiate the calibration process. Providing improved feedback and reducing the number of inputs needed to monitor device fit enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

[0260] Now moving to Figure 11C, which stems from method block 1108 in Figure 11, in some embodiments optionally includes the feature of determining 1114 that the one or more wearable audio output devices have ceased to satisfy the device fit criteria is performed in accordance with a determination that the user is in a respective context of one or more predefined contexts.

[0261] In some embodiments the user is in a respective context of one or more predefined contexts when the user is performing a particular activity of one or more predefined activities (e.g., exercising, such as running, walking, swimming, etc. as shown in the workout application in Figures 6A-6L). The one or more predefined activities may be specified by the user or may be defined by the computer system (e.g., by default). Whether the user is in a respective context can be specified by the user (e.g., by launching an exercise application, as shown in Figures 6A-6L), or can be automatically detected by the computer system and / or the one or more wearable audio output devices (e.g., using one or more motion sensors, accelerometers, and / or gyroscopes, etc.). In some embodiments, in accordance with a determination that the user is not in a respective context of the one or more predefined contexts, the computer system forgoes determining whether the one or more wearable audio output devices have ceased to satisfy the device fit criteria while the media presentation application on the computer system is being used to play media without displaying the settings user interface.

[0262] Monitoring for device fit during particular contexts (e.g., during particular activities) enables providing the user with feedback about the fit of the wearable audio output devices when relevant or desired, without requiring the user to separately navigate to the settings user interface to initiate the calibration process. Providing improved feedback to the user and performing an operation (e.g., automatically) when a set of conditions has been met without requiring further user input reduces the number of inputs needed to perform the operation (e.g., monitoring device fit), which enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

[0263] Moving to Figure 11D, which stems from method block 1110 in Figure 11A optionally includes additional features. The method 1100 optionally includes, after displaying 1116, on the display device, the alert corresponding to the information about the fit of the one or more wearable audio output devices, detecting an input corresponding to the alert (e.g., a tap input on a touch-sensitive surface of the computer system at a location on the touch-sensitive surface that corresponds to the displayed alert). In some embodiments, the alert is a notification displayed over at least a portion of a currently displayed user interface, as shown Figures 6B-1 to 6B-3. In some such embodiments, a corresponding alert is shown in a notification user interface. In some embodiments, the corresponding alert is an audio alert played at one or more of the audio output devices in response to detecting the input corresponding to the alert: displaying the settings user interface. In some embodiments, the settings user interface is an audio output-specific user interface (e.g., a settings user interface shown in Figures 9A-9B). In some embodiments, where the computer system is displaying a particular user interface, such as media application user interface (e.g., the workout application shown in Figures 6A-6L, when the input is detected the computer system ceases to display the particular user interface in combination with displaying the settings user interface (e.g., the settings user interface replaces the particular displayed user interface).

[0264] Displaying a settings user interface in response to an input corresponding to an alert with information about the fit of the wearable audio output devices provides the user with access to additional control options without requiring the user to separately navigate to the settings user interface. Reducing the number of inputs needed to access additional control options enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

[0265] In some embodiments, the alert corresponding 1118 to information about the fit of the one or more wearable audio output devices includes a prompt to perform an adjustment of the one or more wearable audio output devices. For example, in some embodiments, the alert can suggest that the user recalibrate the audio output devices (e.g., via the settings user interface for configuring the fit of the one or more wearable audio output devices, as shown in Figures 5U, 6B-1 to 6B-3). In some embodiments, the alert can suggest that the user reposition the one or more audio output devices in the user's ear(s) (e.g., the banner 618 in Figure 6H prompting the user to correct the placement of the earbud 502-2.

[0266] Prompting a user to perform an adjustment of the wearable audio output devices as part of an alert with information about the fit of the wearable audio output devices provides visual feedback to the user indicating a way in which issues with the fit of the wearable audio output devices can be resolved. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently. In addition, improving the fit of the wearable audio output devices improves the seal between the wearable audio output devices and the user's ears, which enables audio to be played at a lower volume to produce the same effective audio volume perceived by the user (e.g., relative to when the wearable audio output devices are not properly fitted, in which case hearing some ambient noise may cause the user to increase the audio output volume), thereby further reducing power usage and improving battery life of the devices.

[0267] In some embodiments, the method 1000 optionally includes determining 1120 that the one or more wearable audio output devices have ceased to satisfy the device fit criteria is performed in accordance with a determination that the user is in a respective context of one or more predefined contexts; and the alert corresponding to information about the fit of the one or more wearable audio output devices includes a prompt to the user to change a first set of attachments coupled to the one or more wearable audio output devices to a second set of attachments based on the respective context. In some embodiments, the alert includes prompting the user to change an attachment (e.g., a silicone ear-tip attachment on a pair of earbuds for creating a seal around the user's ear, as displayed in Figure 6D-6E) from one size (e.g., a small) to another size (e.g., a larger size to ensure a seal during an activity, as shown in Figure 6D-6E).

[0268] Prompting the user to change to a particular set of attachments based on a current context (e.g., a current activity) of the user as part of an alert with information about the fit of the wearable audio output devices provides visual feedback to the user indicating a way in which issues with the fit of the wearable audio output devices can be resolved. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently. In addition, improving the fit of the wearable audio output devices improves the seal between the wearable audio output devices and the user's ears, which enables audio to be played at a lower volume to produce the same effective audio volume perceived by the user (e.g., relative to when the wearable audio output devices are not properly fitted, in which case hearing some ambient noise may cause the user to increase the audio output volume), thereby further reducing power usage and improving battery life of the devices.

[0269] In some embodiments, the alert corresponding 1122 to information about a fit of the one or more wearable audio output devices includes information about a condition of the wearable audio output devices. In some embodiments, the condition is the physical condition of an attachment (e.g., an ear-tip), or a clogged attachment (e.g., an ear-tip clogged with earwax, which is illustrated in Figures 6D-6G where the eartip 616-4 is dirty and needs to be cleaned).

[0270] Providing information about a condition of the wearable audio output devices or of attachments to the devices (e.g., whether the devices or attachments are clogged, worn, or torn) as part of an alert with information about the fit of the wearable audio output devices provides visual feedback to the user indicating a way in which issues with the fit or condition of the wearable audio output devices can be resolved. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently. In addition, improving the fit or condition of the wearable audio output devices improves the seal between the wearable audio output devices and the user's ears, which enables audio to be played at a lower volume to produce the same effective audio volume perceived by the user (e.g., relative to when the wearable audio output devices are not properly fitted, in which case hearing some ambient noise may cause the user to increase the audio output volume), thereby further reducing power usage and improving battery life of the devices.

[0271] It should be understood that the particular order in which the operations in Figures 11A-11D have been described is merely an example and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., methods 1000, 1200, 1800, 1900, 2000, 2400, and 2600) are also applicable in an analogous manner to method 1100 described above with respect to Figures 11A-11D. For example, the devices, user interfaces, audio outputs, audio output modes, alerts, adjustments, and attachments described above with reference to method 1100 optionally have one or more of the characteristics of the devices, user interfaces, audio outputs, audio output modes, alerts, adjustments, and attachments described herein with reference to other methods described herein (e.g., methods 1000, 1200, 1800, 1900, 2000, 2400, and 2600). For brevity, these details are not repeated here.

[0272] Figures 12A-12E are flow diagrams illustrating method 1200 of controlling audio outputs using inputs at a wearable audio output device in accordance with some embodiments. Method 1200 is performed at a wearable audio output device (e.g., wearable audio output device 301, Figure 3B) that includes an input device (e.g., input device 308, Figure 3B) and one or more microphones (e.g., microphone(s) 302, Figure 3B) and that is in a physical environment. In some embodiments, the input device is pressure-sensitive (also called "intensity-sensitive"). For example, the input device responds to squeeze inputs (e.g., inputs where intensity (also called pressure) is applied to the input device when held and pinched between two fingers) that satisfy an intensity threshold, which in some embodiments is greater than a nominal contact detection intensity threshold that would be used for touch inputs. In some embodiments, the input device is touch-sensitive (e.g., the input device responds to touch inputs, such as by a finger or stylus, that satisfy a nominal contact detection intensity threshold). Some operations in method 1200 are, optionally, combined and / or the order of some operations is, optionally, changed.

[0273] As described below, method 1200 provides an improved interface for controlling audio outputs by changing the audio output mode of an audio output device, such as a wearable device, between audio pass-through and audio cancellation in response to a particular type of gesture. Providing additional control options for controlling audio outputs, such as changing the audio output mode, without cluttering the user interface with additional displayed controls, as well as reducing the number of inputs needed to perform the additional control options, enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the device), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0274] While ambient sound from the physical environment is being detected by the one or more microphones (1202): while the wearable audio output device is in a first audio output mode (1204) (e.g., a pass-through audio output mode, as shown in Figure 8C, corresponding for example to pass-through mode 924, Figure 9C, and described herein with reference to Figure 3C), the wearable audio output device provides a first audio output based at least in part on the ambient sound from the physical environment. The first audio output includes one or more pass-through audio components selected so as to increase audio pass-through of the ambient sound from the physical environment (e.g., as described herein with reference to Figure 3C).

[0275] The wearable audio output device detects (1206) a first input via the input device (e.g., input 805, Figure 8C).

[0276] In response to detecting the first input (1208), and in accordance with a determination that the first input is a first type of gesture (e.g., the input satisfies first gesture criteria, such as long squeeze gesture criteria that require application, to the input device, of a squeeze input (e.g., above an intensity threshold) for at least a threshold amount of time), the wearable audio output device transitions from the first audio output mode (e.g., the pass-through mode) to a second audio output mode (e.g., an active noise control audio output mode, as shown in Figure 8D, corresponding for example to active noise control mode 922, Figure 9C, and described herein with reference to Figure 3C). The first type of gesture is sometimes herein called a long squeeze gesture, click-and-hold input or click-and-hold gesture.

[0277] While the wearable audio output device is in the second audio output mode, the wearable audio output device provides (1210) a second audio output based at least in part on the ambient sound from the physical environment. The second audio output includes one or more cancellation audio components (e.g., one or more antiphase signals such as those indicated by waveform 326-2, Figure 3C) selected so as to increase audio cancellation of the ambient sound from the physical environment. In some embodiments, the first audio output mode corresponds to a pass-through audio output mode (e.g., in which audio pass-through is in effect), and the second audio output mode corresponds to a noise-cancelling audio output mode (e.g., in which active noise control is in effect), and the first input that is a first type of gesture transitions the wearable audio output device directly from the pass-through mode to the noise-cancelling mode (or vice versa) without first transitioning the wearable audio output device through an intervening mode (e.g., a bypass mode, also called an "off" mode) in which active noise management is disabled such that neither pass-through nor active noise control are in effect.

[0278] In some embodiments, the first audio output includes (1212): the one or more pass-through audio components (e.g., corresponding to ambient sound that is actively being passed through from the physical environment) at a first ambient-sound audio level; and the one or more cancellation audio components (e.g., noise-cancelling audio, also called "antiphase" audio) at a first audio-cancelling audio level. In some embodiments, when ambient sound from the physical environment is being actively passed through (e.g., the first ambient-sound audio level is non-zero), noise-cancellation is disabled (e.g., the first audio-cancelling audio level is zero). In some embodiments, when noise-cancellation is enabled (e.g., the first audio-cancelling audio level is non-zero), no ambient sound from the physical environment is actively passed through (e.g., the first ambient-sound audio level is zero). In some embodiments, the second audio output includes: the one or more pass-through audio components at a second ambient-sound audio level that is different from the first ambient-sound audio level; and the one or more cancellation audio components at a second audio-cancelling audio level that is different from the first audio-cancelling audio level. In some embodiments, in accordance with the first audio output being selected or configured so as to increase audio pass-through of the ambient sound from the physical environment, the first ambient-sound audio level of the first audio output is greater than the second ambient-sound audio level of the second audio output. In some embodiments, in accordance with the second audio output being selected or configured to as to increase audio cancellation of the ambient sound from the physical environment, the second audio-cancelling audio level is greater than the first audio-cancelling audio level.

[0279] Using different respective levels of pass-through audio components and cancellation audio components in different audio output modes provides the user with flexibility between different levels of audio immersion (via ambient audio cancellation) or audio transparency (via ambient audio pass-through) that can be achieved with a single gesture. Providing this flexibility without cluttering the user interface with additional displayed controls, as well as reducing the number of inputs needed to access this flexibility, enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the device), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0280] In some embodiments, the wearable audio output device is (1214) in communication (e.g., via a wireless connection, via a wired connection, or integrated) with an electronic device (e.g., portable multifunction device 100, Figure 1A or device 300, Figure 3). In some embodiments, in accordance with a determination that the first input is a second type of gesture (e.g., the input satisfies second gesture criteria, such as single squeeze gesture criteria that require that, after intensity applied by the input to the input device satisfies the intensity threshold, the intensity applied by the input to the input device decreases below the intensity threshold (e.g., due to the input ceasing to remain in contact with the input device) within a threshold amount of time since the input intensity satisfied the intensity threshold, or, alternatively, since initial detection of the input via the input device), the wearable audio output device toggles playing, via the wearable audio output device, a first media audio component that is based on first media (e.g., from the electronic device) that is independent of the ambient sound from the physical environment (e.g., music or video). The second type of gesture is sometimes herein called a single squeeze gesture, click input, or click gesture. In some embodiments, the second type of gesture toggles playback of a respective media audio component (e.g., that is independent of ambient sound from the physical environment, and that is based on media content from or obtained by the electronic device). For example, as shown in and described with reference to Figures 8E-8G, if the respective media audio component is being played when the input that is the second type of gesture (e.g., single squeeze gesture input 810, Figure 8E) is detected, playing of the respective media audio component is paused (e.g., as indicated by play button 714 being displayed in Figure 8F instead of pause button 715 (Figure 8E)); if the respective media audio component is paused when the input that is the second type of gesture (e.g., single squeeze gesture input 811, Figure 8F) is detected, playing of the respective media audio component is resumed (e.g., as indicated by pause button 715 being redisplayed in Figure 8G instead of play button 714 (Figure 8F)). In some embodiments, the media audio component is combined with one or more pass-through audio components (e.g., if the device is operating in the first mode) or one or more audio-cancellation audio components (e.g., if the device is operating in the second mode).

[0281] Toggling playback of media (e.g., that is independent of ambient sound) in response to a particular type of gesture, where the particular type of gesture is different from the gesture associated with changing audio output mode, provides the user with additional control over audio outputs that can be achieved with a single, unique gesture. Providing additional control options for controlling audio outputs without cluttering the user interface with additional displayed controls, as well as reducing the number of inputs needed to perform the additional control options, enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the device), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0282] In some embodiments, in accordance with a determination that the first input is a third type of gesture (e.g., the input satisfies third gesture criteria, such as double squeeze gesture criteria that require two single squeeze gestures performed within a threshold amount of time of each other) (1216): in accordance with a determination that the first input is detected while playing, via the wearable audio output device, the first media audio component that is based on the first media (e.g., in combination with providing the one or more pass-through audio components (e.g., if the device is operating in the first mode) or the one or more cancellation audio components (e.g., if the device is operating in the second mode)), the wearable audio output device ceases to play the first media audio component that is based on the first media; and the wearable audio output device plays, via the wearable audio output device, a second media audio component that is based on second media (e.g., from the electronic device) that is independent of the ambient sound from the physical environment and that is different from the first media (e.g., music or video). In some embodiments, the media audio component is combined with one or more pass through audio components (e.g., if the device is operating in the first mode) or one or more cancellation audio components (e.g., if the device is operating in the second mode). In some embodiments, detecting the third type of gesture while providing a respective media audio component (e.g., a first audio track from the electronic device) skips any remaining portion of the respective media audio component and instead plays a different respective audio component (e.g., a second, next audio track from the electronic device). For example, as shown in and described with reference to Figures 8G-8H, in response to double squeeze input 813, device 100 skips ahead to the next audio track.

[0283] Changing the media being played (e.g., from a first audio track to a second audio track) in response to a particular type of gesture, where the particular type of gesture is different from both the gesture associated with changing audio output mode and the gesture associated with toggling playback of media, provides the user with additional control over audio outputs that can be achieved with a single, unique gesture. Providing additional control options for controlling audio outputs without cluttering the user interface with additional displayed controls, as well as reducing the number of inputs needed to perform the additional control options, enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the device), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0284] In some embodiments, an operation associated with the first type of gesture is (1218) configurable using a settings user interface (e.g., displayed on a display of an electronic device that is in communication with the wearable audio output device) and selected from a first set of operations that includes transitioning a respective audio output mode of the wearable audio output device; an operation associated with the second type of gesture is configurable using the settings user interface and selected from a second set of operations that includes toggling playing a respective media audio component; an operation associated with the third type of gesture is configurable using the settings user interface and selected from a third set of operations that includes ceasing to play a first respective media audio component in combination with playing a second respective media audio component. For example, as shown in and described with reference to Figure 9A-9B, the respective operations to be performed in response to click, double click, and click-and-hold gestures are configurable via settings user interface 900; wherein the set of available operations for click gestures includes the currently-assigned "Play / Pause" operation type, the set of available operations for double click gestures includes the currently-assigned "Next Track" operation type, and the set of available operations for click-and-hold gestures includes the currently-assigned "Noise Management" operation type.

[0285] Allowing a user to configure the operation that is performed in response to a particular type of gesture (or, conversely, allowing a user to configure the type of gesture that causes performance of a particular operation) provides the user with flexibility to customize his or her interactions with the audio output device (e.g., so that particular operation(s), such as those that the user performs more often, can be performed using a gesture via the audio output device without requiring the user to navigate through complex settings menu hierarchies on a separate device, and so that the interactions are more intuitive for the user). Providing flexible and more intuitive user interactions for performing audio output control operations, and reducing the number of inputs needed to perform those operations, enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the device), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0286] In some embodiments, the electronic device includes a display (e.g., touch-sensitive display system 112 in Figure 1A or display 340 in Figure 3A) and a second input device (e.g., a touch-sensitive surface, such as touch-sensitive display system 112 in Figure 1A or touchpad 355 in Figure 3A), and detects (1220) a second input via the second input device (e.g., input 701 via touch screen 112 of device 100, Figures 7A-7B). In some embodiments, in response to detecting the second input, the electronic device displays, on the display, a settings user interface, and displays, in the settings user interface, an output-mode affordance for controlling an audio output mode of the wearable audio output device. In some embodiments, the settings user interface includes a volume affordance, and in response to activation of the volume affordance (e.g., by a hard press or long press, on the second input device, where the second input device includes a touch-sensitive surface such as touch screen 112 in Figure 7D), the electronic device updates the settings user interface (or, stated another way, replaces display of the (e.g., first) settings user interface with display of a second settings user interface) to include the output-mode affordance. For example, as described herein with reference to Figures 7D-7E, settings user interface 702 includes volume control 703, and in response to activation of volume control 703 by input 704 (Figure 7D), device 100 displays enhanced volume control user interface 705, which includes noise management control 707-1 that indicates the audio output mode in which earbuds 502 are currently operating (Figure 7E).

[0287] Providing control options for audio output mode in a settings user interface provides the user with quick access to additional control over audio outputs without requiring the user to navigate through complex settings menu hierarchies. Reducing the number of inputs needed to access the control options enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the device), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0288] In some embodiments, the output-mode affordance is (1222) displayed in the settings user interface in accordance with a determination that the wearable audio output device is in communication with the electronic device. In some embodiments, the output-mode affordance is displayed in the settings user interface in accordance with a determination that the wearable audio output device is in communication with the electronic device and that the wearable audio output device is in use (e.g., by playing audio or being prepared to play audio). For example, noise management control 707-1 in Figure 7E is displayed in accordance with a determination that earbuds 502 are paired to device 100 (and, optionally, in accordance with a determination that earbuds 502 are being used to play audio as indicated by pause button 715, Figure 7E). In some embodiments, while the wearable audio output device is not in communication with the electronic device, the output-mode affordance is not displayed in the settings user interface (e.g., noise management control 707-1 is not displayed in enhanced volume control user interface 705 if earbuds 502 are not connected to device 100).

[0289] Conditionally displaying control options for audio output mode (e.g., an audio output mode control) in a settings user interface based on whether the audio output device and the device on which the settings user interface is displayed are in communication with each other, such that the control options are only displayed when the two devices are in communication, provides the user with quick access to the control options when relevant (e.g., while the two devices are in communication) but not when those control options would be ineffectual (e.g., while the devices are not in communication). Providing additional control options without unnecessarily cluttering the user interface with additional displayed controls enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the device), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0290] In some embodiments, the output-mode affordance includes (1224) a representation of a first respective audio output mode that is a current audio output mode of the wearable audio output device without including representations of any other audio output modes of the wearable audio output device. For example, the output-mode affordance includes a representation of the first audio output mode if the audio output device is operating in the first mode (e.g., without including a representation of the second audio output mode or any other output modes), or a representation of the second audio output mode if the audio output device is operating in the second mode (e.g., without including a representation of the first audio output mode or any other output modes). For example, as described herein with reference to Figures 7E, noise management control 707-1 includes pass-through icon 711 representing the pass-through audio output mode to indicate that earbuds 502 are in the pass-through audio output mode. Alternatively, noise management control 707-1 includes active noise control icon 709 if earbuds 502 are in the active noise control audio output mode, and bypass icon 710 if earbuds 502 are in the bypass audio output mode.

[0291] Displaying an indication of the current audio output mode of the audio output device in an audio output mode control provides visual feedback to the user clearly indicating in which audio output mode the audio output device is currently operating, without displaying other audio output mode options that may distract or mislead the user. Providing improved feedback to the user without unnecessarily cluttering the user interface with additional displayed controls enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the device), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0292] In some embodiments, the electronic device detects (1226), via the second input device, a third input that corresponds to the output-mode affordance; and, in response to detecting the third input, the electronic device displays respective representations of a plurality of audio output modes of the wearable audio output device (e.g., including the representation of the first respective audio output mode that is the current audio output mode). For example, as described herein with reference to Figures 7E-7F, in response to detecting input 708 at noise management control 707-1, device 100 displays expanded noise management control 707-2, which includes pass-through icon 711 representing the pass-through mode, bypass icon 710 representing the bypass mode, and active noise control icon 709 representing the active noise control mode. In some embodiments, (e.g., while displaying the representations of the plurality of audio output modes), a selection indicator (e.g., selection indicator 713, Figure 7F) is displayed on or over the representation of the first respective audio output mode (or the representation of the first respective audio output mode is otherwise visually distinguished from the other representations of available audio output modes) to indicate that the first respective audio output mode is the current audio output mode of the wearable audio output device. In some embodiments, the electronic device detects, via the second input device, a fourth input that corresponds to a representation of a second respective audio output mode that is distinct from the first respective audio output mode; and, in response to detecting the fourth input: the wearable audio output device transitions from the first respective audio output mode to the second respective audio output mode (e.g., making the second respective audio output mode the current audio output mode). For example, as described herein with reference to Figures 7G-7H, in response to input 712 at active noise control icon 709, the audio output mode of earbuds 502 is changed from the pass-through mode to the active noise control mode. In some embodiments, in response to detecting the fourth input, the electronic device ceases to display representations of audio output modes other than the second respective audio output mode (e.g., as described herein with reference Figure 7I, regarding collapsing expanded noise management control 707-2). In some embodiments, (e.g., where the electronic device continues to display representations of the other audio output modes), in response to detecting the fourth input, the selection indicator is displayed on or over the representation of the second respective audio output mode instead of the first respective audio output mode (or the representation of the second respective audio output mode is otherwise visually distinguished, and the representation of the first respective audio output mode ceases to be visually distinguished, from the other representations of available audio output modes) to indicate that the second respective audio output mode is now the current audio output mode of the wearable audio output device. For example, as described herein with reference to Figures 7G-7H, in response to selection of active noise control icon 709 by input 712 (Figure 7G), selection indicator 713 ceases to be displayed over pass-through icon 711 and is instead displayed over active noise control icon 709 (Figure 7H).

[0293] Displaying additional options for audio output mode in response to selection of the audio output mode control, and then transitioning the audio output mode of the audio output device in response to selection of a different audio output mode option, provides the user with access to additional audio output modes when requested, without prematurely displaying the other audio output mode options, which may be distracting or misleading to the user. Providing additional control options without unnecessarily cluttering the user interface with additional displayed controls enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the device), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0294] In some embodiments, the first respective audio output mode is (1228) distinct from a third audio output mode in which the wearable audio output device provides audio outputs independently of the ambient sound from the physical environment (e.g., an audio output mode in which the wearable audio output device provides neither pass-through audio components nor cancellation audio components, such as the bypass mode represented by bypass icon 710, Figure 7G), and the second respective audio output mode is distinct from the third audio output mode.

[0295] Allowing the user to change the audio output mode of an audio output device between two different audio output modes (e.g., between an audio pass-through mode and an audio cancellation mode or vice versa), neither of which is independent of ambient sound from the physical environment, provides the user with flexibility between different levels of audio immersion or audio transparency that can be achieved with a single input, rather than requiring the user to toggle audio immersion on or off separately from toggling audio transparency on or off. Providing this flexibility while reducing the number of inputs needed to access this flexibility enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating / interacting with the device), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0296] In some embodiments, detecting the first input includes (1230) detecting an increase in intensity that satisfies an activation intensity threshold, and the wearable audio output device: in response to detecting the increase in intensity that satisfies the activation intensity threshold (e.g., an increase in intensity to or above the activation intensity threshold), provides an activation audio output; detects a decrease in intensity that satisfies a release intensity threshold; and, in response to detecting the decrease in intensity that satisfies the release intensity threshold (e.g., a decrease in intensity to or below the release intensity threshold), provides a release audio output. In some embodiments, the activation intensity threshold is the same as the release intensity threshold. In some embodiments, the activation intensity threshold is differe...

Claims

1. A method for providing wearable audio output, comprising: at a computer system that includes a wearable audio output device in a physical environment: while a first wearable audio output component of the wearable audio output device is in a first position relative to a first ear of a user and a second wearable audio output component of the wearable audio output device is in the first position relative to a second ear of the user, operating (1902) the wearable audio output device in a first audio output mode, wherein the first position comprises a position in which a respective wearable audio output component is worn in or worn over a respective ear of the user; while operating the wearable audio output device in the first audio output mode, detecting (1904) a change in position of the first wearable audio output component from the first position relative to the first ear of the user to a second position relative to the first ear of the user, wherein the change in position of the first wearable audio output component corresponds to removal of the first wearable audio output component from the first ear of the user, and the second position relative to the first ear of the user is away from the first ear of the user; and in response (1906) to detecting the change in position of the first wearable audio output component from the first position relative to the first ear of the user to the second position relative to the first ear of the user, while the second wearable audio output component is maintained in the first position relative to the second ear of the user: transitioning (1908) the wearable audio output device from the first audio output mode to a second audio output mode; characterized in that the second audio output mode is a pass-through audio output mode that is different from the first audio output mode, wherein, while the wearable audio output device is in the pass-through audio output mode, audio outputs that are provided via the wearable audio output device include one or more pass-through audio components that include at least a portion of ambient sound from the physical environment; and after detecting the change (1914) in position of the first wearable audio output component from the first position relative to the first ear of the user to the second position relative to the first ear of the user, in response to detecting a change in position of the first wearable audio output component from the second position relative to the first ear of the user back to the first position relative to the first ear of the user, while the second wearable audio output component is maintained in the first position relative to the first ear of the user: transitioning the wearable audio output device from the second audio output mode to the first audio output mode; including, while operating the wearable audio output device in the first audio output mode, outputting respective audio content, providing media content, via the wearable audio output device, and after transitioning (1908) the wearable audio output device from the first audio output mode to the second audio output mode, continuing to output the respective audio content, while operating the wearable audio output device in the second audio output mode.

2. The method of claim 1, wherein a respective wearable audio output component being in the first position relative to a respective ear of the user includes the respective wearable audio output component being placed at least partially within the respective ear.

3. The method of claim 2, including: in response (1912) to detecting a change in position of the second wearable audio output component from the first position relative to the second ear of the user to the second position relative to the second ear of the user, while the first wearable audio output component is maintained in the second position relative to the first ear of the user: transitioning the wearable audio output device from the second audio output mode to a third audio output mode that is a noise control off mode, wherein, while the wearable audio output device is in the noise control off mode, audio outputs that are provided via the wearable audio output device do not include one or more pass-through audio components that include at least a portion of ambient sound from the physical environment and do not include one or more cancellation audio components selected so as to at least partially cancel ambient sound from the physical environment.

4. The method of any of claims 1-3, including: while operating (1920) the wearable audio output device in a respective audio output mode, receiving an alert of an incoming phone call; detecting an input that corresponds to a request to answer the incoming phone call; and in response to detecting the input corresponding to the request to answer the incoming phone call: transitioning the wearable audio output device from the respective audio output mode to the second audio output mode.

5. The method of claim 4, including: detecting (1922) termination of the phone call; and in response to detecting the termination of the phone call: transitioning the wearable audio output device from the second audio output mode to the respective audio output mode.

6. A computer system, comprising: a wearable audio output device in a physical environment; one or more processors; and memory storing one or more programs, wherein the one or more programs are configured to be executed by the one or more processors, the one or more programs including instructions for: while a first wearable audio output component of the wearable audio output device is in a first position relative to a first ear of a user and a second wearable audio output component of the wearable audio output device is in the first position relative to a second ear of the user, operating the wearable audio output device in a first audio output mode, wherein the first position comprises a position in which a respective wearable audio output component is worn in or worn over a respective ear of the user; while operating the wearable audio output device in the first audio output mode, detecting a change in position of the first wearable audio output component from the first position relative to the first ear of the user to a second position relative to the first ear of the user, wherein the change in position of the first wearable audio output component corresponds to removal of the first wearable audio output component from the first ear of the user, and the second position relative to the first ear of the user is away from the first ear of the user; and in response to detecting the change in position of the first wearable audio output component from the first position relative to the first ear of the user to the second position relative to the first ear of the user, while the second wearable audio output component is maintained in the first position relative to the second ear of the user: transitioning the wearable audio output device from the first audio output mode to a second audio output mode; characterized in that the second audio output mode is a pass-through audio output mode that is different from the first audio output mode, wherein, while the wearable audio output device is in the pass-through audio output mode, audio outputs that are provided via the wearable audio output device include one or more pass-through audio components that include at least a portion of ambient sound from the physical environment; and after detecting the change (1914) in position of the first wearable audio output component from the first position relative to the first ear of the user to the second position relative to the first ear of the user, in response to detecting a change in position of the first wearable audio output component from the second position relative to the first ear of the user back to the first position relative to the first ear of the user, while the second wearable audio output component is maintained in the first position relative to the first ear of the user: transitioning the wearable audio output device from the second audio output mode to the first audio output mode; including, while operating the wearable audio output device in the first audio output mode, outputting respective audio content, providing media content, via the wearable audio output device, and after transitioning (1908) the wearable audio output device from the first audio output mode to the second audio output mode, continuing to output the respective audio content, while operating the wearable audio output device in the second audio output mode.

7. The computer system of claim 6, wherein the one or more programs include instructions for performing the method of any of claims 2-5.

8. A computer readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by a computer system that includes a wearable audio output device in a physical environment, cause the computer system to: while a first wearable audio output component of the wearable audio output device is in a first position relative to a first ear of a user and a second wearable audio output component of the wearable audio output device is in the first position relative to a second ear of the user, operate the wearable audio output device in a first audio output mode, wherein the first position comprises a position in which a respective wearable audio output component is worn in or worn over a respective ear of the user; while operating the wearable audio output device in the first audio output mode, detect a change in position of the first wearable audio output component from the first position relative to the first ear of the user to a second position relative to the first ear of the user, wherein the change in position of the first wearable audio output component corresponds to removal of the first wearable audio output component from the first ear of the user, and the second position relative to the first ear of the user is away from the first ear of the user; and in response to detecting the change in position of the first wearable audio output component from the first position relative to the first ear of the user to the second position relative to the first ear of the user, while the second wearable audio output component is maintained in the first position relative to the second ear of the user: transition the wearable audio output device from the first audio output mode to a second audio output mode; characterized in that the second audio output mode is a pass-through audio output mode that is different from the first audio output mode, wherein, while the wearable audio output device is in the pass-through audio output mode, audio outputs that are provided via the wearable audio output device include one or more pass-through audio components that include at least a portion of ambient sound from the physical environment; and after detecting the change (1914) in position of the first wearable audio output component from the first position relative to the first ear of the user to the second position relative to the first ear of the user, in response to detecting a change in position of the first wearable audio output component from the second position relative to the first ear of the user back to the first position relative to the first ear of the user, while the second wearable audio output component is maintained in the first position relative to the first ear of the user: transition the wearable audio output device from the second audio output mode to the first audio output mode; including, while operating the wearable audio output device in the first audio output mode, outputting respective audio content, providing media content, via the wearable audio output device, and after transitioning (1908) the wearable audio output device from the first audio output mode to the second audio output mode, continuing to output the respective audio content, while operating the wearable audio output device in the second audio output mode.

9. The computer readable storage medium of claim 8, wherein the one or more programs include instructions that, when executed by the computer system, cause the computer system to perform the method of any of claims 2-5.