Device, method and user interface for controlling operation of wireless electronic accessory

Abstract

The invention relates to a device, a method and a user interface for controlling operation of a wireless electronic accessory. A wearable audio output device includes a first portion configured to be inserted into an ear of a user and a second portion extending from the first portion and including one or more input devices. The wearable audio output device detects an input via the one or more input devices. In response to detecting the input and in accordance with a determination that the input is a swipe gesture along the second portion of the wearable audio output device, the wearable audio output device adjusts an output volume of the wearable audio output device based on movement of the swipe gesture along the second portion of the wearable audio output device.

Description

[0001] This application is a divisional application of the invention patent application with application number 202380063905.0, application date September 5, 2023, and name “Device, method and user interface for controlling the operation of wireless electronic accessories”.

[0002] Related patent applications

[0003] This application is a continuation of U.S. patent application No. 18 / 241,778 filed on September 1, 2023, which claims priority to U.S. provisional patent application No. 63 / 404,101 filed on September 6, 2022. Technical Field

[0004] The present invention generally relates to electronic accessories, such as wearable audio output devices and accessory charging cases, including but not limited to systems for controlling a wearable audio output device with an input device, an electronic accessory with a physical tag, and an accessory case with a speaker. Background Art

[0005] Electronic accessories, including wearable audio output devices such as headphones, earbuds, and earphones, as well as charging cases, watches, and styluses, are widely used to receive input from and provide output to users. However, traditional methods of controlling and interacting with such devices are cumbersome, inefficient, and limited.

[0006] In some cases, inputs provided at a wearable audio output device provide limited control of the audio output; for example, the input may be limited to controlling a single predefined characteristic of the audio output, such as toggling power or a feature on or off. In some cases, the limited control over the audio output can affect a user's ability to control the volume of audio content played back by the wearable audio output device and / or control the amount of conversations the user can hear in the surrounding physical environment while wearing the wearable audio output device. In some cases, the user interface for controlling the wearable audio output device and other accessory devices does not provide sufficient information to enable the user to quickly distinguish between multiple devices of the same type, such as multiple sets of earbuds or multiple charging cases.

[0007] In some cases, the user interface for controlling audio output settings provides too few controls, such as providing controls for only one audio output device, thereby requiring the user to provide a lot of input and navigate through different menus or user interfaces to perform specific actions, or provides too many controls, thereby cluttering the user interface and increasing the likelihood that the user will mistakenly interact with the wrong control, particularly for specific implementations where the display area is limited.

[0008] Furthermore, conventional methods take longer than necessary to operate the electronic accessory and require more user interaction, thereby wasting energy. This latter consideration is particularly important in battery-powered devices.

[0009] Furthermore, accessory boxes for electronic accessories are typically configured only to charge and / or store the electronic accessories. While some electronic accessories include output mechanisms (e.g., speakers or displays), accessory boxes traditionally do not include means for providing output (such as audio feedback) to the user. Instead, feedback (if provided at all) is traditionally provided by other devices, such as smartphones, tablets, or computers that are paired with or wirelessly connected to the accessory box. Consequently, traditional means for providing feedback require multiple devices and communication channels. Summary of the Invention

[0010] Therefore, there is a need for electronic accessories (e.g., wearable audio output devices and charging cases) and associated electronic devices with improved methods and interfaces for control and interaction (such as adjusting volume, selecting between different audio output modes, and providing feedback to help users operate such devices). Such methods and interfaces optionally supplement or replace conventional methods for controlling the operation of electronic accessories. Such methods and interfaces reduce the amount, extent, and / or nature of input from the user and produce a more efficient human-computer interface. For battery-powered systems and devices, such methods and interfaces save power and increase the interval between battery charges.

[0011] The computer system and electronic accessories disclosed in the present invention reduce or eliminate the above-mentioned defects and other problems associated with the user interface for electronic devices and accessories. In some embodiments, the computer system includes a desktop computer. In some embodiments, the computer system is portable (e.g., a laptop, 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 a wearable audio output device (e.g., in-ear headphones, earplugs, over-ear headphones, etc.) (and / or communicates with it). In some embodiments, the computer system has a touch-sensitive surface (also referred to as a "touchpad") (and / or communicates with it). In some embodiments, the computer system has a display device, which in some embodiments is a touch-sensitive display (also referred to as a "touch screen" or "touch screen display") (and / or communicates with it). In some embodiments, the computer system has a graphical user interface (GUI), one or more processors, memory and one or more modules, a program or instruction set stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI mainly through stylus and / or finger contact and gestures on the touch-sensitive surface. In some embodiments, these functions optionally include image editing, drawing, presentations, word processing, spreadsheet creation, playing games, making and receiving calls, video conferencing, sending and receiving emails, instant messaging, fitness support, digital photography, digital video recording, web browsing, audio output device pairing and calibration, digital music / audio playback, note taking and / or digital video playback. 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.

[0012] According to some embodiments, a method is performed at a wearable audio output device, the wearable audio output device including a first portion configured to be inserted into an ear of a user and a second portion extending from the first portion of the wearable audio output device, the second portion including one or more input devices. The method includes detecting an input via the one or more input devices; and in response to detecting the input, adjusting an output volume of the wearable audio output device based on movement of the sliding gesture along the second portion of the wearable audio output device in accordance with determining that the input is a sliding gesture along the second portion of the wearable audio output device.

[0013] According to some embodiments, a method is performed at an electronic device that includes a display generation component or communicates with a display generation component. The method includes detecting the occurrence of a corresponding condition associated with an electronic accessory that is different from the electronic device, and the electronic accessory communicates with the electronic device; and in response to detecting the occurrence of the corresponding condition, causing a user interface corresponding to the corresponding condition to be displayed via the display generation component, the user interface including a representation of the electronic accessory. Causing the user interface to be displayed includes, based on determining that the electronic accessory includes a first physical marker, causing the representation of the first physical marker to be displayed in the user interface; and based on determining that the electronic accessory includes a second physical marker that is different from the first physical marker, causing the representation of the second physical marker to be displayed in the user interface.

[0014] According to some embodiments, a method is performed at an accessory charging case that includes a speaker. The method includes detecting a first event that includes a change in an open or closed state of the accessory charging case; and in response to detecting the change in the open or closed state of the accessory charging case, causing the speaker of the accessory charging case to generate an audio notification corresponding to a state of at least one of the accessory charging case and one or more accessories associated with the accessory charging case.

[0015] According to some embodiments, a method is performed at an electronic device that communicates with a display generation component and one or more wearable audio output devices. The method includes causing a user interface to be displayed via the display generation component, the user interface including a volume control element for one or more wearable audio output devices; and detecting an input corresponding to the volume control element. The method also includes adjusting the volume of the audio output of the one or more wearable audio output devices in response to detecting the input and based on determining that the input is a first type of gesture. The method also includes causing a conversation enhancement element to be displayed for the one or more wearable audio output devices in response to detecting the input and based on determining that the input is a second type of gesture, the conversation enhancement element, when selected, initiating a process for adjusting the audio output of the one or more wearable audio output devices to enhance the conversation audio corresponding to the conversation having audio accessible by the one or more wearable audio output devices relative to other audio output by the one or more wearable audio output devices.

[0016] According to some embodiments, an electronic device (e.g., a multifunction device, an electronic accessory, or an electronic accessory box) includes one or more processors and a 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 the execution of the operations of any of the methods described herein. According to some embodiments, a computer-readable storage medium has instructions stored therein that, when executed by an electronic device, cause the device to perform or cause the execution of the operations of any of the methods described herein. According to some embodiments, a graphical user interface on an electronic device having a display, a touch-sensitive surface, a memory, and one or more processors for executing one or more programs stored in the memory includes one or more of the elements displayed in any of the methods described herein, which are updated in response to input, as described in any of the methods described herein. According to some embodiments, an electronic device includes a device for performing or causing the execution of the operations of any of the methods described herein. According to some embodiments, an information processing device for use in an electronic device includes a device for performing or causing the execution of the operations of any of the methods described herein.

[0017] Thus, electronic devices that include or communicate with one or more display devices, one or more input devices, one or more audio output devices, and / or one or more electronic accessories are provided with improved methods and interfaces for controlling the operation of wireless electronic accessories, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces can supplement or replace conventional methods for controlling the operation of wireless electronic accessories. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] For a better understanding of the various described embodiments, reference should be made to the following detailed description taken in conjunction with the following drawings, wherein like reference numerals designate corresponding parts throughout the several views.

[0019] Figure 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display according to some embodiments.

[0020] Figure 1B is a block diagram illustrating example components for event processing according to some embodiments.

[0021] Figure 2 A portable multifunction device with a touch screen according to some embodiments is shown.

[0022] Figure 3A is a block diagram of an example multifunction device with a display and a touch-sensitive surface according to some embodiments.

[0023] Figure 3BPhysical features of an exemplary wearable audio output device are shown according to some embodiments.

[0024] Figure 3C is a block diagram of an exemplary wearable audio output device according to some embodiments.

[0025] Figure 3D Physical features of an example electronic accessory box are shown, according to some embodiments.

[0026] Figure 3E is a block diagram of an exemplary electronic accessory box according to some embodiments.

[0027] Figure 3F Example audio control by a wearable audio output device according to some embodiments is shown.

[0028] Figure 4A An exemplary user interface for an application menu on a portable multifunction device according to some embodiments is shown.

[0029] Figure 4B An exemplary user interface for a multifunction device having a touch-sensitive surface separate from the display is shown according to some embodiments.

[0030] Figure 4C An example interaction between a wearable audio output device and an electronic accessory box is shown according to some embodiments.

[0031] 5A to 5D An exemplary user interface for pairing an electronic accessory according to some embodiments is shown.

[0032] Figures 5E to 5R Example user interfaces and user interactions for adjusting the audio output of a wearable audio output device according to some embodiments are shown.

[0033] Figures 5S to 5BI Exemplary user interfaces and user interactions for various features associated with an electronic accessory box are shown according to some embodiments.

[0034] Figures 5BJ to 5CB Example user interfaces and user interactions for adjusting the audio output of a wearable audio output device according to some embodiments are shown.

[0035] Figures 6A to 6C is a flowchart of a process for adjusting the audio output of one or more wearable audio output devices according to some embodiments.

[0036] 7A to 7C is a flowchart of a process for displaying status information of an electronic accessory according to some embodiments.

[0037] Figures 8A to 8D is a flowchart of a process for presenting status information at an accessory charging case according to some embodiments.

[0038] Figures 9A to 9C is a flowchart of a process for adjusting the audio output of a wearable audio output device according to some embodiments. DETAILED DESCRIPTION

[0039] As described above, electronic accessories including wearable audio output devices (such as headphones, earbuds, and earphones), as well as charging cases, watches, and styluses, are widely used to provide output to users. Many computer systems that include or communicate with wearable audio output devices give users only limited control over output in response to input at the wearable audio output device, or provide too few or too many output controls for the user interface. The methods, systems, and user interfaces / interactions described herein improve how output is provided in a variety of ways. For example, the embodiments disclosed herein describe improved methods of controlling audio output using input at a wearable audio output device and providing an improved user interface for controlling audio output settings.

[0040] As described above, electronic accessory boxes are typically passive devices for storing and / or charging electronic accessories. Although some electronic accessories include output mechanisms (e.g., speakers or displays), accessory boxes traditionally do not include devices for providing output (such as audio feedback) to the user. The methods, systems, and user interfaces / interactions described herein improve the functionality of electronic accessory boxes. For example, the embodiments disclosed herein describe improved ways to provide status information and / or feedback to the user at an electronic accessory box.

[0041] The processes described below enhance the operability of the device and make the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device) through various techniques, including by providing improved visual, auditory, and / or tactile feedback to the user, reducing the number of inputs required to perform an operation, providing control options without cluttering the user interface with additional displayed controls, performing an operation without further user input when a set of conditions have been met, and / or additional techniques. These techniques also reduce power usage and extend the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0042] under, Figure 1A to Figure 1B 、 Figure 2 、 Figures 3A to 3F 、 Figures 4A to 4C An exemplary device is shown. Figures 5A to 5CB Exemplary user interfaces and device interactions for controlling example devices are shown. Figures 6A to 6C A flow chart illustrating a process for adjusting audio output of one or more wearable audio output devices is shown. 7A to 7C A flow chart illustrating a process for displaying status information for an electronic accessory is shown. Figures 8A to 8D A flow chart of a process for presenting status information at an accessory charging case is shown. Figures 9A to 9C A flow chart illustrating a process for adjusting audio output of a wearable audio output device is shown. Figures 5A to 5CB The user interface and device interaction in Figures 6A to 6C , 7A to Figure 7C 、 8A to Figure 8D and 9A to Figure 9C in the process.

[0043] Exemplary devices

[0044] Reference will now be made in detail to the embodiments, examples of which are illustrated in the accompanying drawings. Numerous specific details are set forth in the following detailed description 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 cases, well-known methods, processes, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure various aspects of the embodiments.

[0045] It will also be understood that, although in some cases, the terms "first," "second," etc., are used herein to describe various elements, these elements should not be limited by these terms. These terms are simply used to distinguish one element from another. For example, a first contact can be named a second contact, and similarly, a second contact can be named a first contact without departing from the scope of the various described embodiments. Both a first contact and a second contact are contacts, but they are not the same contact unless the context clearly indicates otherwise.

[0046] The terms used in the description of the various described embodiments herein are only for the purpose of describing specific embodiments and are not intended to be limiting. As used in the description of the various described embodiments and in the appended claims, the singular forms "a" and "the" are intended to also include the plural forms, unless the context clearly indicates otherwise. It will also be understood that the terms "and / or" used herein refer to and encompass any and all possible combinations of one or more of the associated listed items. It will also be understood that the terms "comprises" and / or "comprising" when used in this specification specify the presence of stated features, integers, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or their groupings.

[0047] As used herein, the term "if" is optionally interpreted to mean "when" followed by "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined that" or "if [stated condition or event] is detected" are optionally interpreted to mean "upon determining" or "in response to determining" or "upon detecting [stated condition or event]" or "in response to detecting [stated condition or event]," depending on the context.

[0048] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functionality, such as a PDA and / or music player functionality. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple Watch from Apple Inc., Cupertino, California. iPod and Device. Other portable electronic devices, such as laptop computers or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or trackpads), are optionally used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or trackpads).

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

[0050] The device typically supports a variety of applications, such as one or more of the following applications: a note-taking application, a drawing application, a presentation application, a word processing application, a website creation application, a disk editing application, a spreadsheet application, a gaming application, a telephony application, a video conferencing application, an email application, an instant messaging application, a fitness 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.

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

[0052] Attention is now turned to embodiments of portable devices having touch-sensitive displays. Figure 1A 1 is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display system 112 is sometimes referred to as a "touch screen" for convenience, and sometimes simply as a touch-sensitive display. The device 100 includes memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input or control devices 116, and external ports 124. The device 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more intensity sensors 165 for detecting intensity of contact on the device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of the device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile output on device 100 (e.g., generating tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touch pad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0053] As used in this specification and claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of a device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device that will be detected by a user using the user's sense of touch. For example, when a device or a component of the device is in contact with a surface that is touch-sensitive to a user (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation that corresponds to a perceived change in a physical property of the device or 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 "press click" or "release click" on a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or "release click," even when the physical actuation button associated with the touch-sensitive surface that was physically pressed (e.g., displaced) by the user's movement does not move. As another example, even when the smoothness of the touch-sensitive surface does not change, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface. While such a user's interpretation of touch will be limited by the user's individualized sensory perceptions, many sensory perceptions of touch are common to most users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "press click," "release click," "roughness"), unless otherwise stated, the tactile output generated corresponds to a physical displacement of the device or a component thereof that would generate that sensory perception for a typical (or average) user. Providing tactile feedback to the user using tactile output enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which further reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

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

[0055] When a device (e.g., one or more tactile output generators that generate tactile output via movement of a movable mass) generates tactile output with different tactile output patterns, the tactile output can produce different tactile sensations in a user holding or touching the device. While a user's senses are based on their perception of the tactile output, most users will be able to discern changes in the waveform, frequency, and amplitude of the tactile output generated by the device. Therefore, the waveform, frequency, and amplitude can be adjusted to indicate to the user that different operations have been performed. Thus, tactile output with tactile output patterns designed, selected, and / or arranged to simulate the characteristics (e.g., size, material, weight, stiffness, smoothness, etc.); behavior (e.g., oscillation, displacement, acceleration, rotation, extension, etc.); and / or interaction (e.g., collision, adhesion, repulsion, attraction, friction, etc.) of objects in a given environment (e.g., a user interface including 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 any combination of the foregoing) can, in some cases, provide helpful feedback to the user, reducing input errors and improving the user's efficiency in operating the device. In addition, tactile output is optionally generated to correspond to feedback that is unrelated to the simulated physical properties (such as input threshold or object selection). Such tactile output will provide helpful feedback to the user in some cases, which reduces input errors and improves the efficiency of the user's operation of the device.

[0056] In some embodiments, a tactile output with a suitable tactile output pattern serves as a prompt for an event of interest in the user interface or behind the screen in the device. Examples of events of interest include activation of an affordance (e.g., a real or virtual button or toggle switch) provided on the device or in the user interface, the success or failure of a requested operation, reaching or crossing a boundary in the user interface, entering a new state, switching input focus between objects, activating a new mode, reaching or crossing an input threshold, detecting or recognizing a type of input or gesture, and the like. In some embodiments, a tactile output is provided to serve as a warning or prompt for an upcoming event or result that would otherwise occur unless a change in direction or interrupt input is detected in a timely manner. Tactile output is also used in other contexts to enrich the user experience, improve the accessibility of the device for users with visual or motor difficulties or other accessibility needs, and / or improve the efficiency and functionality of the user interface and / or device. Optionally, the tactile output is compared with audio input and / or visual user interface changes, which further enhances the user's experience when the user interacts with the user interface and / or device, and facilitates better transmission of information about the state of the user interface and / or device, and reduces input errors and improves the efficiency of the user's operation of the device.

[0057] It should be understood that device 100 is merely 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. Figure 1A The various components shown are implemented in hardware, software, firmware, or any combination thereof, including one or more signal processing circuits and / or application specific integrated circuits.

[0058] 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 120 and peripheral device interface 118) is optionally controlled by memory controller 122.

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

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

[0061] RF (radio frequency) circuitry 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuitry 108 converts electrical signals into / from electromagnetic signals and communicates with a communication network and other communication 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 the like. RF circuitry 108 optionally communicates with networks and other devices via wireless communications, such as the Internet (also known 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)). The wireless communication optionally uses any of a variety of communication standards, protocols and technologies, including, but not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolution-Data Only (EV-DO), HSPA, HSPA+, Dual 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, email protocols (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 Utilizing 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 on the date of filing of this document.

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

[0063] The I / O subsystem 106 couples input / output peripherals on the device 100, such as a touch-sensitive display system 112 and other input or control devices 116, to a peripherals interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, an intensity sensor controller 159, a tactile 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 control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, etc. In some alternative embodiments, the one or more input controllers 160 are optionally coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, a stylus, and / or a pointer device such as a mouse. The one or more buttons (e.g., Figure 2 208) optionally includes up / down buttons for volume control of the speaker 111 and / or microphone 113. The one or more buttons optionally include a push button (e.g., Figure 2 206 in the ).

[0064] The touch-sensitive display system 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch-sensitive display system 112 and / or sends electrical signals to the touch-sensitive display system. The touch-sensitive display system 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, videos, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some visual outputs or all of the visual outputs correspond to user interface objects. As used herein, the term "indicator" refers to a user-interactive graphical user interface object (e.g., a graphical user interface object that is configured to respond to input directed to a graphical user interface object). Examples of user-interactive graphical user interface objects include, but are not limited to, buttons, sliders, icons, selectable menu items, switches, hyperlinks, or other user interface controls.

[0065] The touch-sensitive display system 112 has a touch-sensitive surface, sensor, or sensor group that accepts input from the user based on tactile and / or haptic contact. The touch-sensitive display system 112 and the display controller 156 (together with any associated modules and / or instruction sets in the memory 102) detect contact (and any movement or interruption of that contact) on the touch-sensitive display system 112 and convert the detected contact into interaction with a user interface object (e.g., one or more soft keys, icons, web pages, or images) displayed on the touch-sensitive display system 112. In some embodiments, the point of contact between the touch-sensitive display system 112 and the user corresponds to the user's finger or stylus.

[0066] The 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. The touch-sensitive display system 112 and display controller 156 optionally use any of a variety 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 the touch-sensitive display system 112 to detect contact and any movement or interruption thereof. In some embodiments, projected mutual capacitance sensing technology is used, such as the ATmega 2000 from Apple Inc. (Cupertino, California). iPod and Technology found in.

[0067] The touch-sensitive display system 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touch screen video resolution exceeds 400 dpi (e.g., 500 dpi, 800 dpi, or greater). The user optionally uses any suitable object or appendage, such as a stylus, finger, or the like, to contact the touch-sensitive display system 112. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of ​​a finger on the touch screen. In some embodiments, the device converts rough finger-based input into precise pointer / cursor positioning or commands for performing the action desired by the user.

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

[0069] Device 100 also includes a power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, power fault detection circuitry, 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 a portable device.

[0070] Device 100 optionally also includes one or more optical sensors 164 (eg, as part of one or more cameras). Figure 1A An optical sensor coupled to the optical sensor controller 158 in the I / O subsystem 106 is shown. One or more optical sensors 164 optionally include a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. The one or more optical sensors 164 receive light projected from the environment through one or more lenses and convert the light into data representing an image. In conjunction with the imaging module 143 (also called a camera module), the one or more optical sensors 164 optionally capture still images and / or video. In some embodiments, the optical sensor is located on the rear portion of the device 100 opposite the touch-sensitive display system 112 on the front of the device, so that the touch screen can be used as a viewfinder for still image and / or video image acquisition. In some embodiments, another optical sensor is located on the front of the device to obtain an image of the user (e.g., for selfies, for video conferencing when the user views other video conference participants on the touch screen, etc.).

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

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

[0073] Device 100 optionally also includes one or more tactile output generators 167 . Figure 1AA tactile output generator is shown coupled to the tactile feedback controller 161 in the I / O subsystem 106. In some embodiments, the tactile output generator 167 includes one or more electroacoustic devices such as speakers or other audio components; and / or electromechanical devices for converting energy into linear motion such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generation components (e.g., components for converting electrical signals into tactile outputs on the device). The tactile output generator 167 receives tactile feedback generation instructions from the tactile feedback module 133 and generates tactile outputs on the device 100 that can be felt by the user of the device 100. In some embodiments, at least one tactile output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112) and optionally generates tactile outputs by moving the touch-sensitive surface vertically (e.g., inward / outward toward the surface of the device 100) or laterally (e.g., back and forth in the same plane as the surface of the device 100). In some embodiments, at least one tactile output generator sensor is located on the back of the device 100 opposite the touch-sensitive display system 112 located on the front of the device 100.

[0074] Device 100 optionally also includes one or more accelerometers 168 . Figure 1A An accelerometer 168 is shown coupled to the peripherals interface 118. Alternatively, the accelerometer 168 is optionally coupled to the input controller 160 in the 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. The device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver in addition to the accelerometer 168 for obtaining information about the position and orientation (e.g., portrait or landscape) of the device 100.

[0075] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a tactile feedback module (or instruction set) 133, a text input module (or instruction set) 134, a global positioning system (GPS) module (or instruction set) 135, and applications (or instruction sets) 136. In addition, in some embodiments, memory 102 stores a device / global internal state 157, as shown in Figures 1A and 3. The device / global internal state 157 includes one or more of the following: an active application state, which indicates which applications (if any) are currently active; a display state, which indicates what applications, views, or other information occupy various areas of the touch-sensitive display system 112; a sensor state, which includes information obtained from various sensors and other input or control devices 116 of the device; and position and / or location information about the position and / or posture of the device.

[0076] The 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.

[0077] The communication module 128 facilitates communication with other devices via one or more external ports 124 and also includes various software components for processing data received by the RF circuitry 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are suitable for coupling directly to other devices or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external ports are compatible with some of the Apple Inc. (Cupertino, California) iPod and 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 Apple Inc. (Cupertino, California) iPod and In some embodiments, the external port is a USB Type-C connector that is the same as, similar to, and / or compatible with the Lightning connector used in some electronic devices from Apple Inc. (Cupertino, California).

[0078] The contact / motion module 130 optionally detects contact with the touch-sensitive display system 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). The contact / motion module 130 includes various software components for performing various operations related to contact detection (e.g., by a finger or stylus), such as determining whether contact has occurred (e.g., detecting a finger press event), determining the strength of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there has been movement of the contact and tracking movement across the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has ceased (e.g., detecting a finger lift event or contact break). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of a contact point optionally includes determining a rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of which is represented by a series of contact data. These operations are optionally applied to a single point of contact (e.g., a single finger contact or stylus contact) or multiple points of simultaneous contact (e.g., "multi-touch" / multi-finger contact). In some embodiments, contact / motion module 130 and display controller 156 detect contact on a touchpad.

[0079] The contact / motion module 130 optionally detects gesture input by the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and / or intensities of the detected contacts). Therefore, gestures are optionally detected by detecting specific contact patterns. For example, detecting a single-finger tap gesture includes detecting a finger press event and then detecting a finger lift (lift-off) event at the same location (or substantially the same location) as the finger press event (e.g., at an icon location). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and then detecting a finger lift (lift-off) event. Similarly, taps, swipes, drags, and other gestures of the stylus are optionally detected by detecting a specific contact pattern of the stylus.

[0080] In some embodiments, detecting a finger tap gesture depends on detecting the length of time between a finger press event and a finger lift event, but is independent of detecting the intensity of the finger contact between the finger press event and the finger lift event. In some embodiments, a tap gesture is detected based on determining that the length of time between the finger press event and the finger lift event is less than a predetermined value (e.g., less than 0.1 seconds, 0.2 seconds, 0.3 seconds, 0.4 seconds, or 0.5 seconds), regardless of whether the intensity of the finger contact during the tap reaches 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 meet a specific input criterion that does not require the characteristic intensity of the contact to meet a given intensity threshold to meet the specific input criterion. For clarity, the finger contact in a tap gesture is generally required to meet a nominal contact detection intensity threshold to detect a finger press event, below which the contact is not 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 contact by a finger or stylus hovering over the 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.

[0081] The same concepts apply in a similar manner to other types of gestures. For example, a swipe gesture, a pinch gesture, an expand gesture, and / or a long press gesture may be optionally detected based on satisfying criteria that are independent of the intensity of the contacts included in the gesture or that do not require one or more contacts performing the gesture to reach an intensity threshold in order to be recognized. For example, a swipe gesture is detected based on the amount of movement of one or more contacts; a pinch gesture is detected based on movement of two or more contacts toward each other; an expand gesture is detected based on movement of two or more contacts away from each other; and a long press gesture is detected based on the duration of a contact on the touch-sensitive surface having less than a threshold amount of movement. Thus, the statement that a particular gesture recognition criterion does not require the intensity of the contacts to meet the corresponding intensity threshold in order to satisfy the particular gesture recognition criterion means that the particular gesture recognition criterion can be satisfied when the contacts in the gesture do not reach the corresponding intensity threshold, and can also be satisfied when one or more contacts in the gesture reaches or exceeds the corresponding intensity threshold. In some embodiments, a tap gesture is detected based on determining that a finger down event and a finger up event are detected within a predefined time period, regardless of whether the contact is above or below a corresponding intensity threshold during the predefined time period, and a swipe gesture is detected based on determining that the contact moves by more than a predefined amount, even if the contact is above the corresponding intensity threshold at the end of the contact movement. Even in specific implementations where detection of gestures is affected by the intensity of the contact 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 the device delays detection of a tap input when the intensity of the contact is higher), detection of these gestures does not require the contact to reach a particular intensity threshold (e.g., even if the amount of time required to recognize the gesture varies), as long as the criteria for recognizing the gesture can be met without the contact reaching the particular intensity threshold.

[0082] In some cases, contact intensity thresholds, duration thresholds, and movement thresholds are combined in various combinations to create heuristic algorithms that distinguish between two or more different gestures directed to the same input element or area, enabling multiple different interactions with the same input element to provide a richer set of user interactions and responses. A statement that a particular set of gesture recognition criteria does not require the intensity of one or more contacts to meet the corresponding intensity threshold in order to meet the particular gesture recognition criteria does not preclude the simultaneous evaluation of other intensity-related gesture recognition criteria to identify other gestures whose criteria are met when the gesture includes a contact with an intensity above the corresponding intensity threshold. For example, in some cases, a first gesture recognition criterion for a first gesture (which does not require the intensity of the contact to meet the corresponding intensity threshold to meet the first gesture recognition criterion) competes with a second gesture recognition criterion for a second gesture (which depends on the contact meeting the corresponding intensity threshold). In such a competition, if the second gesture recognition criterion for the second gesture is met first, the gesture is optionally not recognized as meeting the first gesture recognition criterion for the first gesture. For example, if the contact reaches the corresponding intensity threshold before the contact moves a predefined amount, a deep press gesture is detected instead of a swipe gesture. Conversely, if the contact moves a predefined amount before the contact reaches the corresponding intensity threshold, a swipe gesture is detected instead of a deep press gesture. Even in such cases, the first gesture recognition criterion for the first gesture still does not require the intensity of the contact to meet the corresponding intensity threshold in order to satisfy the first gesture recognition criterion because, if the contact remains below the corresponding intensity threshold until the gesture ends (e.g., a swipe gesture with an intensity that does not increase above the corresponding intensity threshold), the gesture will be recognized as a swipe gesture by the first gesture recognition criterion. Thus, a particular gesture recognition criterion that does not require the intensity of the contact to meet the corresponding intensity threshold in order to satisfy the particular gesture recognition criterion may (A) in some cases ignore the intensity of the contact relative to the intensity threshold (e.g., for a tap gesture) and / or (B) in some cases fail to satisfy the particular gesture recognition criterion (e.g., for a long press gesture) if a set of competing intensity-related gesture recognition criteria (e.g., for a deep press gesture) recognizes the input as corresponding to an intensity-related gesture before the particular gesture recognition criterion recognizes the gesture corresponding to the input, and in this sense still depends on the intensity of the contact relative to the intensity threshold (e.g., for a long press gesture competing with a deep press gesture for recognition).

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

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

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

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

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

[0088] Application 136 optionally includes the following modules (or instruction sets), or a subset or superset thereof:

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

[0090] Telephone module 138;

[0091] Video conferencing module 139;

[0092] Email client module 140;

[0093] Instant messaging (IM) module 141;

[0094] Fitness support module 142;

[0095] A camera module 143 for still and / or video images;

[0096] Image management module 144;

[0097] Browser module 147;

[0098] Calendar module 148;

[0099] Widget module 149, which optionally includes one or more of the following: weather widget 149-1, stock market widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets acquired by the user, and user-created widgets 149-6;

[0100] A widget creator module 150 for forming a user-created widget 149 - 6 ;

[0101] Search module 151;

[0102] A video and music player module 152, optionally consisting of a video player module and a music player module;

[0103] Note module 153;

[0104] Map module 154; and / or

[0105] Online video module 155.

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

[0107] In combination with the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, and the text input module 134, the contacts module 137 includes executable instructions for managing an address book or contact list (e.g., stored in the application internal state 192 of the contacts module 137 in memory 102 or memory 370), including: adding names to the address book; deleting names from the address book; associating phone numbers, email addresses, physical addresses, or other information with names; associating images with names; categorizing and classifying names; providing phone numbers and / or email addresses to initiate and / or facilitate communications via the phone module 138, video conferencing 139, email 140, or IM 141; etc.

[0108] 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, phone module 138 includes executable instructions for entering a character sequence corresponding to a phone number, accessing one or more phone numbers in address book 137, modifying an entered phone number, dialing the corresponding phone number, conducting a conversation, and disconnecting or hanging up when the conversation is complete. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

[0109] In combination with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, one or more optical sensors 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephony module 138, video conferencing module 139 includes executable instructions for initiating, conducting, and terminating a video conference between a user and one or more other participants in accordance with user instructions.

[0110] 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, email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to user instructions. In conjunction with image management module 144, email client module 140 makes it very easy to create and send emails with still images or video images captured by camera module 143.

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

[0112] In combination with the RF circuitry 108, the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154, and the video and music player module 152, the fitness support module 142 includes executable instructions for creating a workout (e.g., with time, distance, and / or calorie burn goals); communicating with fitness sensors (in sports equipment and smart watches); receiving fitness sensor data; calibrating sensors for monitoring a workout; selecting and playing music for a workout; and displaying, storing, and transmitting fitness data.

[0113] In conjunction with touch-sensitive display system 112, display controller 156, one or more optical sensors 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions for capturing still images or videos (including video streams) and storing them in memory 102, modifying characteristics of still images or videos, and / or deleting still images or videos from memory 102.

[0114] 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 for arranging, modifying (e.g., editing), or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slideshow or album), and storing still images and / or video images.

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

[0116] In combination with the RF circuit 108, the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, the text input module 134, the email client module 140 and the browser module 147, the calendar module 148 includes executable instructions for creating, displaying, modifying and storing calendars and data associated with the calendars (e.g., calendar entries, to-do items, etc.) in accordance with user instructions.

[0117] In conjunction with the RF circuitry 108, the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, the text input module 134, and the browser module 147, the widget module 149 is a mini-application that is optionally downloaded and used by a user (e.g., a weather widget 149-1, a stock market widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, and a dictionary widget 149-5) or a mini-application created by a user (e.g., a 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., a Yahoo! widget).

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

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

[0120] In conjunction with touch-sensitive display system 112, display 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 a 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), as well as executable instructions for displaying, presenting, or otherwise playing back video (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.).

[0121] In conjunction with the touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the note module 153 includes executable instructions for creating and managing notes, to-do lists, etc. according to user instructions.

[0122] In combination 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, and browser module 147, map module 154 includes executable instructions for receiving, displaying, modifying, and storing maps and data associated with the maps (e.g., driving directions; data about stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.

[0123] In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes executable instructions that allow a user to access, browse, receive (e.g., by streaming and / or downloading), play back (e.g., on touch-sensitive display system 112 or on an external display connected wirelessly or via external port 124), send an email 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 is used instead of email client module 140 to send a link to a particular online video.

[0124] Each module and application program identified above corresponds to a set of executable instructions for performing one or more functions and methods described in the present application (e.g., computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) do not have to be implemented as independent software programs, processes, or modules, so various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the above-mentioned modules and data structures. In addition, memory 102 optionally stores other modules and data structures not described above.

[0125] 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 operating device 100, the number of physical input control devices (e.g., push buttons, dials, etc.) on device 100 is optionally reduced.

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

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

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

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

[0130] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about sub-events (e.g., a user touch 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 sensors such as proximity sensor 166, one or more accelerometers 168, and / or microphone 113 (through audio circuit 110). The information received by peripherals interface 118 from I / O subsystem 106 includes information from touch-sensitive display system 112 or a touch-sensitive surface.

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

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

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

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

[0135] Hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy where the sub-events should be processed. In most cases, the hit view is the lowest-level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events that form an event or potential event) occurs. Once a 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.

[0136] Active event recognizer determination module 173 determines which view or views within the 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 the sub-event are actively participating views, and therefore determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to an area associated with one particular view, views higher in the hierarchy will still remain actively participating views.

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

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

[0139] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a corresponding view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a corresponding application view 191 includes multiple event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface toolkit or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, a corresponding event handler 190 includes one or more of the following: a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from an event classifier 170. Event 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 in the application view 191 include one or more corresponding event handlers 190. In addition, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in the corresponding application view 191.

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

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

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

[0143] In some embodiments, event definition 187 includes definitions of events for corresponding user interface objects. 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 displaying three user interface objects 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 corresponding event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler that is associated with the sub-event and the object that triggered the hit test.

[0144] In some embodiments, the definition of the corresponding event 187 also includes delay actions that delay the delivery of the event information until after it has been determined that the sub-event sequence does or does not correspond to the event type of the event identifier.

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

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

[0147] In some embodiments, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates an event handler 190 associated with the event. In some embodiments, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating an event handler 190 is different from sending (and deferred sending) sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a flag associated with the identified event, and the event handler 190 associated with the flag retrieves the flag and performs a predefined process.

[0148] 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 the event information to an event handler associated with the sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or the actively participating view receives the event information and executes a predetermined process.

[0149] In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates phone numbers used in contact module 137 or stores video files used in video or 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 new user interface objects or updates the positioning of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends the display information to graphics module 132 for display on a touch-sensitive display.

[0150] In some embodiments, event handler 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 the corresponding application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0151] It should be understood that the above discussion of event handling for user touches on a touch-sensitive display also applies to other forms of user input utilizing input devices to operate the multifunction device 100, and not all user input is initiated on a touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or holddowns; contact movement on a touchpad, such as taps, drags, scrolls, etc.; stylus input; movement of the device; spoken commands; detected eye movement; biometric input; and / or any combination thereof, are optionally used as input corresponding to sub-events defining the event to be recognized.

[0152] Figure 2 A device with a touch screen (e.g., Figure 1AIn some embodiments, the portable multifunction device 100 includes a touch-sensitive display system 112 (e.g., a touch screen). The touch screen optionally displays one or more graphics within a user interface (UI) 200. In these embodiments, and in other embodiments described below, a user can select one or more of the graphics by, for example, making gestures on the graphics using one or more fingers 202 (not drawn to scale in the figures) or one or more styluses 203 (not drawn to scale in the figures). In some embodiments, selection of the 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, from right to left, up and / or down), and / or rolling of a finger that has made contact with the device 100 (from right to left, from left to right, up and / or down). In some implementations or in some cases, 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.

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

[0154] In some embodiments, the device 100 includes a touch screen display, a menu button 204 (sometimes referred to as a home button 204), a push button 206 for powering the device on / off and for locking the device, volume adjustment buttons 208, a subscriber identity module (SIM) card slot 210, a headset jack 212, and a docking / charging external port 124. The push button 206 is optionally used to turn the device on / off by pressing the button and holding the button in the pressed state for a predefined time interval; to lock the device by pressing the button and releasing the button before the predefined time interval has passed; and / or to unlock the device or initiate an unlocking process. In some embodiments, the device 100 also accepts voice input for activating or deactivating certain functions through the microphone 113. The device 100 also optionally includes one or more contact force sensors 165 for detecting the intensity of contact on the touch-sensitive display system 112, and / or one or more tactile output generators 167 for generating tactile output for the user of the device 100.

[0155] Figure 3A3 is a block diagram of an example multifunction device with a display and a touch-sensitive surface according to some embodiments. The device 300 does not have to be portable. In some embodiments, the 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 children's learning toy), a gaming system, or a control device (e.g., a home controller or an industrial controller). The device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, a memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuits (sometimes referred to as a chipset) that interconnect system components and control communications between system components. The device 300 includes an input / output (I / O) interface 330 having a display 340, which is typically a touch screen display. The I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 for generating tactile output on the device 300 (e.g., similar to the above referenced embodiments). Figure 1A The one or more tactile output generators 167 described above), sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch sensors, and / or sensors similar to those described above) Figure 1A In some embodiments, the device 300 includes a wireless interface 311 (e.g., a wireless interface 312) for communicating with one or more wearable audio output devices 301 and / or electronic accessory box 342. Figure 3E In some embodiments, device 300 includes a network communication interface 360 ​​for communicating with remote devices (eg, in conjunction with communication module 128).

[0156] Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU 310. In some embodiments, memory 370 stores data related to portable multifunction device 100 ( Figure 1A), or a subset thereof. In addition, 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 a drawing module 380, a presentation module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while portable multifunction device 100( Figure 1A )'s memory 102 optionally does not store these modules.

[0157] Figure 3A Each element in the above-mentioned identified element is optionally stored in one or more memory devices in the previously mentioned memory device.Each module in the above-mentioned identified module corresponds to the instruction set for performing the above-mentioned functions.The above-mentioned identified module or program (that is, instruction set) need not be implemented as independent software program, process or module, so the various subsets of these modules are optionally combined or otherwise rearranged in various embodiments.In some embodiments, memory 370 optionally stores the subset of above-mentioned modules and data structure.In addition, memory 370 optionally stores additional modules and data structure not described above.

[0158] Figure 3B Figure 2 shows the physical features of an exemplary wearable audio output device 301 according to some embodiments. In some embodiments, the wearable audio output device 301 is one or more in-ear headphones, earbuds, over-ear headphones, etc. Figure 3B In the example of FIG, wearable audio output device 301 is an earbud. In some embodiments, wearable audio output device 301 includes a head portion 303 and a handle portion 305. In some embodiments, head portion 303 is configured to be inserted into a user's ear. In some embodiments, handle portion 305 physically extends from head portion 303 (e.g., is an elongated portion extending from head portion 303). For example, when head portion 303 is inserted into a user's ear, head portion 303 physically extends downward, in front of the user's earlobe, and / or past the user's earlobe.

[0159] In some embodiments, the wearable audio output device 301 includes one or more audio speakers 306 (e.g., in the head portion 303) for providing audio output (e.g., to the user's ears). In some embodiments, the wearable audio output device 301 includes one or more placement sensors 304 (e.g., placement sensors 304-1 and 304-2 in the head portion 303) to detect the positioning or placement of the wearable audio output device 301 relative to the user's ears, such as detecting the placement of the wearable audio output device 301 in the user's ears.

[0160] In some embodiments, the wearable audio output device 301 includes one or more microphones 302 for receiving audio input. In some embodiments, one or more microphones 302 (e.g., microphone 302-1) are included in the head portion 303. In some embodiments, one or more microphones 302 (e.g., microphone 302-2) are included in the handle portion 305. In some embodiments, the microphone 302 detects the voice of the user wearing the wearable audio output device 301 and / or the ambient noise around the wearable audio output device 301. In some embodiments, multiple microphones of the microphone 302 are positioned at different locations on the wearable audio output device 301 to measure the voice and / or ambient noise at different locations around the wearable audio output device 301.

[0161] In some embodiments, the wearable audio output device 301 includes one or more input devices 308 (e.g., in the handle portion 305). In some embodiments, the input device 308 includes a pressure-sensitive (e.g., intensity-sensitive) input device. In some embodiments, the pressure-sensitive input device detects input from the user in response to the user squeezing the input device (e.g., by pinching the handle portion 305 of the wearable audio output device 301 between two fingers). In some embodiments, the input device 308 includes a touch-sensitive surface (e.g., a capacitive sensor) for detecting touch input, an accelerometer and / or a posture sensor (e.g., for determining the posture of the wearable audio output device 301 relative to the physical environment and / or changes in the device posture) and / or other input devices through which the user can interact with the wearable audio output device 301 and provide input to the wearable audio output device. In some embodiments, the input device 308 includes one or more capacitive sensors, one or more force sensors, one or more motion sensors, and / or one or more orientation sensors. Figure 3BInput devices 308 are shown at locations within the handle portion 305, however, in some embodiments, one or more of the input devices 308 are located elsewhere within the wearable audio output device 301 (e.g., elsewhere within the handle portion 305 and / or head portion 303). In some embodiments, the wearable audio output device 301 includes a housing having one or more physical distinguishing portions 307 at locations corresponding to the input devices 308 (e.g., to assist the user in locating and / or interacting with the input devices 308). In some embodiments, the physical distinguishing portions 307 include indentations, raised portions, and / or portions with different textures. In some embodiments, the physical distinguishing portions 307 include a single distinguishing portion that spans multiple input devices 308. For example, the input devices 308 include a set of touch sensors configured to detect a swipe gesture, and a single distinguishing portion (e.g., a depression or groove) spans the set of touch sensors. In some embodiments, the physical distinguishing portion 307 includes a corresponding distinguishing portion for each input device 308.

[0162] Figure 3Cis a block diagram of an exemplary wearable audio output device 301 according to some embodiments. In some embodiments, the wearable audio output device 301 is one or more in-ear headphones, earbuds, over-ear headphones, etc. In some examples, the wearable audio output device 301 includes a pair of headphones or earbuds (e.g., one headphone or earbud for each of the user's ears). In some examples, the wearable audio output device 301 includes over-ear headphones (e.g., headphones with two over-ear ear cups to be placed over the user's ears and optionally connected by a headband). In some embodiments, the wearable audio output device 301 includes one or more audio speakers 306 for providing audio output (e.g., to the user's ears). In some embodiments, the wearable audio output device 301 includes one or more placement sensors 304 to detect the positioning or placement of the wearable audio output device 301 relative to the user's ears, such as detecting the placement of the wearable audio output device 301 in the user's ears. In some embodiments, the wearable audio output device 301 conditionally outputs audio based on whether the wearable audio output device 301 is in the user's ear or near the user's ear (e.g., forgoing outputting audio when the wearable audio output device 301 is not in the user's ear to reduce power usage). In some embodiments where the wearable audio output device 301 includes multiple (e.g., a pair) of wearable audio output components (e.g., headphones, earbuds, or earmuffs), each component includes one or more corresponding placement sensors, and the wearable audio output device 301 conditionally outputs audio based on whether one or both components are in the user's ear or near the user's ear, as described herein. In some embodiments, the wearable audio output device 301 also includes an internal rechargeable battery 309 for providing power to the various components of the wearable audio output device 301.

[0163] In some embodiments, the wearable audio output device 301 includes audio I / O logic 312 that determines the positioning or placement of the wearable audio output device 301 relative to the user's ear based on information received from the placement sensor 304, and in some embodiments, the audio I / O logic 312 controls the resulting conditional audio output. In some embodiments, the wearable audio output device 301 includes a device for communicating with one or more multi-function devices such as device 100 ( Figure 1A ) or device 300( Figure 3A ) and electronic accessory box 342 (see Figure 3E ) wireless interface 315 for communicating with a multifunction device such as device 100 ( Figure 1A ) or device 300( Figure 3A) connection (e.g., via a headphone jack or other audio port). In some embodiments, a user can interact with and provide input to the wearable audio output device 301 via interface 315 (e.g., remotely). In some embodiments, the wearable audio output device 301 communicates with multiple devices (e.g., multiple multi-function devices and / or audio output device housings), and the audio I / O logic component 312 determines from which of the multi-function devices to accept instructions for outputting audio.

[0164] In some embodiments, the wearable audio output device 301 includes one or more microphones 302 for receiving audio input. In some embodiments where the wearable audio output device 301 includes multiple (e.g., a pair) wearable audio output components (e.g., headphones or earbuds), each component includes one or more corresponding microphones. In some embodiments, the audio I / O logic component 312 detects or recognizes speech or ambient noise based on information received from the microphones 302.

[0165] In some embodiments, the wearable audio output device 301 includes one or more input devices 308. In some embodiments where the wearable audio output device 301 includes multiple (e.g., a pair of) wearable audio output components (e.g., headphones, earbuds, or earmuffs), each component includes one or more corresponding input devices. In some embodiments, the input device 308 includes one or more volume control hardware elements for (e.g., local) volume control of the wearable audio output device 301 (e.g., an up / down button for volume control, or as described herein with reference to a volume control hardware element). Figure 1A In some embodiments, the input provided via one or more input devices 308 is processed by the audio I / O logic component 312. In some embodiments, the audio I / O logic component 312 is connected to a separate device (e.g., Figure 1A device 100 or Figure 3A 300) that provides instructions or content for audio output and optionally receives and processes input (or information about input) provided via microphone 302, placement sensor 304, and / or input device 308, or via one or more input devices of a separate device. In some embodiments, audio I / O logic 312 is located on device 100 (e.g., as a Figure 1A ) or device 300 (e.g., as part of the peripheral device interface 118 of Figure 3A 301), or alternatively is located partially in device 100 and partially in device 301, or is located partially in device 300 and partially in device 301.

[0166] Figure 3D Physical features of an example electronic accessory box 342 according to some embodiments are shown. In some embodiments, the electronic accessory box 342 includes a lid 367 and a container 369. In some embodiments, the electronic accessory box 342 includes one or more sensors to detect whether the lid 367 is opened, closed, and / or moved. In some embodiments, the electronic accessory box 342 is configured to hold and / or charge one or more electronic accessories, such as headphones, a smartwatch, an electronic stylus, a fitness tracker, and / or earbuds. In some embodiments, the electronic accessory box 342 includes one or more audio output devices (e.g., speakers 345) (e.g., to provide status and / or event information to the user). In some embodiments, the electronic accessory box 342 includes one or more input devices.

[0167] Figure 3E is a block diagram illustrating an electronic accessory case 342 according to some embodiments. In some embodiments, the electronic accessory case 342 is an earphone case (e.g., a wireless earphone case). In some embodiments, the electronic accessory case 342 is an accessory charging case configured to charge one or more accessories when the accessory is positioned (e.g., mounted, inserted, and / or attached) in the accessory charging case. The electronic accessory case 342 includes a memory 349 (optionally including one or more computer-readable storage media), one or more processing units (CPUs) 343, and a peripheral device interface 344. In some embodiments, the peripheral device interface 344 includes one or more speakers 345, one or more input devices 346 (e.g., one or more buttons, switches, and / or joysticks), and one or more communication components 348 (e.g., wireless interfaces) for communicating with devices such as one or more wearable audio output devices 301 and one or more electronic devices such as smartphones, tablets, computers, etc. In some embodiments, the peripheral device interface 344 includes a set of LEDs and / or display elements capable of displaying icons and / or other visual information. In some embodiments, the peripheral device interface 344 includes one or more tactile output generators 347 for generating tactile output (also known as tactile feedback), for example, via an external housing 362 (also known as a shell) of the electronic accessory box 342.

[0168] According to some embodiments, the electronic accessory box 342 includes an internal battery 309 (eg, a battery pack 309 for providing power to the various components of the electronic accessory box 342 and for powering one or more wearable audio output devices 301). Figure 3B) to charge an internal rechargeable battery 363. In some embodiments, the electronic accessory box 342 includes a battery charger 364 for charging the internal battery 363 when the battery charger 364 is connected to an external power source via a power connection port 365. In some embodiments, the internal battery 363 and / or the battery charger 364 are configured to charge the internal battery 309 (e.g., headphones or earbuds) of an audio output device (e.g., headphones or earbuds) when the audio output device is connected to (e.g., properly positioned in) the accessory charger 366. Figure 3B ) for charging. These components optionally communicate via one or more communication buses or signal lines 341.

[0169] In some embodiments, the outer housing 362, when closed (e.g., see Figure 4C ) has a range between 1.5 inches and 3 inches in a first dimension (e.g., width or height), a range between 1 inch and 2.5 inches in a second dimension (e.g., height or width), and a range between 0.5 inches and 1 inch in a third dimension (e.g., depth).

[0170] In some embodiments, the software components stored in memory 349 include an operating system 351 (or BIOS), a communication module (or instruction set) 352, an input module (or instruction set) 353, a graphics module (or instruction set) 354, a haptic feedback module (or instruction set) 356, and a headset control module 358. Additionally, in some embodiments, memory 349 stores a device / global internal state 361, which includes one or more of the following: an active application state, which indicates which applications (if any) are currently active; and a sensor state, which includes information obtained from various sensors and other input devices 346 of the device.

[0171] Figure 3F Exemplary audio control by a wearable audio output device 301 is shown in accordance with some embodiments. Although the following examples are explained with respect to a specific implementation of a wearable audio output device including an earbud with an attached replaceable eartip (sometimes referred to as a silicon eartip or silicon seal), the methods, devices, and user interfaces described herein are equally applicable to specific implementations in which the wearable audio output device does not have an eartip, but instead each has a portion of a body shaped for insertion into a user's ear. In some embodiments, when the wearable audio output device with an earbud capable of attaching a replaceable eartip is worn in the user's ear, the earbud and eartip together act as a physical barrier, blocking at least some ambient sound from the surrounding physical environment from reaching the user's ear. For example, in Figure 3F, a user wears the wearable audio output device 301 so that the head portion 303 and the ear tip 314 are in the user's left ear. The ear tip 314 extends at least partially into the user's ear canal. Preferably, when the head portion 303 and the ear tip 314 are inserted into the user's ear, a seal is formed between the ear tip 314 and the user's ear so as to isolate the user's ear canal from the surrounding physical environment. However, in some embodiments, the head portion 303 and the ear tip 314 together block some, but not necessarily all, ambient sounds in the surrounding physical environment from reaching the user's ear. Therefore, in some embodiments, a first microphone (or, in some embodiments, a first group of one or more microphones) 302-1 (and an optional third microphone 302-3) are located on the wearable audio output device 301 to detect ambient sounds in an area 316 of the physical environment surrounding the head portion 303 (e.g., outside the earbud), represented by a waveform 322. In some embodiments, (e.g., Figure 3C A second microphone (or, in some embodiments, a second set of one or more microphones) 302-2 of the microphone 302 is located on the wearable audio output device 301 to detect any ambient sound that is not completely blocked by the head portion 303 and the ear tip 314 and can be heard in the area 318 within the user's ear canal, as represented by the waveform 324. Thus, in some cases where the wearable audio output device 301 does not generate a noise-canceling (also known as "inverted") audio signal to cancel (e.g., attenuate) ambient sound from the surrounding physical environment (as indicated by waveform 326-1), the ambient sound waveform 324 can be perceived by the user (as indicated by waveform 328-1). In some cases where the wearable audio output device 301 generates an inverted audio signal to cancel ambient sound (as indicated by waveform 326-2), the ambient sound waveform 324 cannot be perceived by the user (as shown by waveform 328-2).

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

[0173] In some embodiments, the 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 (sometimes also referred to as a noise control off audio output mode). In the active noise control mode (also referred to as "ANC"), the wearable audio output device 301 outputs one or more audio cancellation audio components (e.g., one or more inverted phase audio signals, also referred to as "audio cancellation audio components") to at least partially cancel ambient sound from the surrounding physical environment that would otherwise be perceived by the user. In the active pass-through audio output mode, the wearable audio output device 301 outputs one or more pass-through audio components (e.g., playing at least a portion of the ambient sound from outside the user's ear received by, for example, microphone 302-1) so that the user can hear a greater amount of ambient sound from the surrounding physical environment than would otherwise be perceived by the user (e.g., a greater amount of ambient sound than would be heard using passive attenuation of the wearable audio output device 301 placed in the user's ear). In bypass mode, active noise management is turned off such that the wearable audio output device 301 outputs neither any audio-cancelled audio component nor any pass-through audio component (e.g., such that any amount of ambient sound perceived by the user is due to the physical attenuation of the wearable audio output device 301).

[0174] Attention is now turned to an embodiment of a user interface (“UI”) that is optionally implemented on portable multifunction device 100 .

[0175] Figure 4A An exemplary user interface for an application menu on portable multifunction device 100 is shown according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

[0176] One or more signal strength indicators of one or more wireless communications, such as cellular signals and Wi-Fi signals;

[0177] ·time;

[0178] Bluetooth indicator;

[0179] Battery status indicator;

[0180] A tray 408 with icons for commonly used applications, such as:

[0181] o An icon 416 labeled "Phone" for the phone module 138, which optionally includes an indicator 414 of the number of missed calls or voicemails;

[0182] o An icon 418 of the email client module 140 labeled "Mail," which optionally includes an indicator 410 of the number of unread emails;

[0183] o An icon 420 labeled "Browser" for the browser module 147; and

[0184] o An icon 422 labeled “Music” of the video and music player module 152;

[0185] as well as

[0186] Icons for other apps, such as:

[0187] o Icon 424 labeled "Messages" of the IM module 141;

[0188] o An icon 426 labeled “Calendar” of the calendar module 148;

[0189] o Icon 428 labeled "Photos" of the image management module 144;

[0190] o An icon 430 labeled “Camera” of the camera module 143;

[0191] ○ An icon 432 labeled “Online Video” of the online video module 155;

[0192] ○ Icon 434 labeled “Stock Market” of the Stock Market widget 149-2;

[0193] o An icon 436 labeled “Map” of the map module 154;

[0194] ○ Icon 438 labeled “Weather” of weather widget 149-1;

[0195] ○ Icon 440 labeled “Clock” of the alarm clock widget 149-4;

[0196] o An icon 442 labeled “Fitness Support” of the fitness support module 142;

[0197] o An icon 444 labeled "Notes" for the notes module 153; and

[0198] o An icon 446 for a settings application or module that provides access to settings for the device 100 and its various applications 136 .

[0199] It should be noted that Figure 4AThe icon labels shown in the are merely exemplary. For example, other labels are optionally used for various application icons. In some embodiments, the label of a respective application icon includes the name of the application corresponding to the respective application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

[0200] Figure 4B An exemplary user interface is shown on a device (e.g., device 300 in FIG. 3 ) having a touch-sensitive surface 451 (e.g., tablet or trackpad 355 in FIG. 3 ) that is separate from a display 450. Although many of the examples that follow will be given with reference to input on a touch-sensitive display system 112 (in which the touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, such as Figure 4B In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a main axis (e.g., Figure 4B 453) corresponding to the main axis (for example, Figure 4B According to these embodiments, the device detects contact with the touch-sensitive surface 451 at a location that corresponds to a corresponding location on the display (e.g., Figure 4B 460 and 462 in (e.g., in Figure 4B , 460 corresponds to 468 and 462 corresponds to 470). Thus, on a touch-sensitive surface (e.g., Figure 4B 451) and a display of a multi-function device (e.g., Figure 4B When the user interface 450 in the embodiment of the present invention is separated, the user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

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

[0202] In some embodiments, the device's response to an input detected by the device depends on criteria based on the intensity of the contact during the input. For example, for some "light press" inputs, the intensity of the contact exceeding a first intensity threshold during the input triggers a first response. In some embodiments, the device's response to an input detected by the device depends on criteria that include both the intensity of the contact during the input and a time-based criterion. For example, for some "deep press" inputs, the intensity of the contact exceeding a second intensity threshold, which is greater than the first intensity threshold for a light press, during the input triggers a second response, as long as a delay time elapses between the first intensity threshold being met and the second intensity threshold being met. The duration of this delay time is typically less than 200 ms (milliseconds) (e.g., 40 ms, 100 ms, or 120 ms, depending on the magnitude of the second intensity threshold, where the delay time increases as the second intensity threshold increases). This delay time helps avoid accidentally identifying a deep press input. As another example, for some "deep press" inputs, a period of reduced sensitivity occurs after the first intensity threshold is reached. During this period of reduced sensitivity, the second intensity threshold increases. This temporary increase in the second intensity threshold also helps avoid accidental deep press inputs.For other deep press inputs, the response to detecting the deep press input does not depend on time-based criteria.

[0203] In some embodiments, one or more of the input intensity thresholds and / or corresponding outputs vary based on one or more factors, such as user settings, contact motion, input timing, application running, rate at which intensity is applied, number of simultaneous inputs, user history, environmental factors (e.g., ambient noise), focus selector position, etc. Example factors are described in U.S. patent applications 14 / 399,606 and 14 / 624,296, which are incorporated herein by reference in their entireties.

[0204] Figure 4C An example wireless accessory case 480 (eg, an electronic accessory case such as a wireless accessory case) is shown that includes physical indicia 482 (eg, engraved, embossed, and / or printed, painted, or otherwise applied indicia). Figure 3E The physical characteristics of the electronic accessory box 342). Figure 3D and Figure 3E The description provided is applicable to the wireless accessory box 480 described herein. The wireless accessory box 480 wirelessly communicates (e.g., pairs) with the wearable audio output devices 301-1 and 301-2, the audio source, and / or the display device (e.g., the multifunction device 100). According to some embodiments, Figure 4CIn some embodiments, the wearable audio output device 301 includes physical markers 484 (e.g., physical marker 484-1 on wearable audio output device 301-1 and physical marker 484-2 on wearable audio output device 301-2). In some embodiments, the wireless accessory box 480 is configured to charge the wearable audio output device 301 (e.g., charge its internal battery) when the wearable audio output device 301 is positioned inside the wireless accessory box 480. In some embodiments, the wireless accessory box 480 includes a battery (e.g., battery 363, Figure 3E ), for charging the internal battery of the wearable audio output device 301 (e.g., battery 309, Figure 3C ) and is used to power the functions of wireless accessory box 480 when wireless accessory box 480 is not connected to an external power source. In some embodiments, such as Figure 4C , the wireless accessory case 480 has a hinged lid 486 to enclose the wearable audio output devices 301 while they are inside the wireless accessory case 480 and / or charging. According to some embodiments, the front of the accessory case 480 includes a hole for the speaker 345, the input device 346, a physical indicia 482, and an indentation 488 for facilitating opening and closing the hinged lid 486. In some embodiments, one or more of the speaker 345, the input device 346, the physical indicia 482 are located on different portions of the wireless accessory case 480 (e.g., on the back, top, and / or bottom). Additionally, while Figure 4C The wearable audio output device 301 is shown positioned within the wireless accessory case 480 with the corresponding EarTips facing away from each other (e.g., facing outward), but in some embodiments, the wearable audio output device 301 is positioned (e.g., mounted and / or coupled) differently within the wireless accessory case 480 (e.g., with the EarTips facing each other). For example, the wireless accessory case 480 optionally only charges the wearable audio output device 301 when the wearable audio output device 301 is positioned within the wireless accessory case 480 in a particular orientation.

[0205] User interface and associated processes

[0206] Attention now turns to embodiments of a user interface ("UI") and associated processes that may be implemented on an electronic device, such as portable multifunction device 100, device 300, wearable audio output device 301, electronic accessory box 342, and / or wireless accessory box 480.

[0207] 5A to 5D An exemplary user interface for pairing an electronic accessory according to some embodiments is shown. Figures 5E to 5RExample user interfaces and user interactions for adjusting the audio output of a wearable audio output device according to some embodiments are shown. Figures 5S to 5BI Exemplary user interfaces and user interactions for various features associated with an electronic accessory box are shown according to some embodiments. Figures 5BJ to 5CB Figures 1 and 2 illustrate exemplary user interfaces and user interactions for adjusting the audio output of a wearable audio output device according to some embodiments. The user interfaces and device interactions in these figures are used to illustrate the processes described below, including Figures 6A to 6C 、 7A to 7C 、 Figures 8A to 8D and Figures 9A to 9C For ease of explanation, some embodiments in the implementation scheme will be discussed with reference to operations performed on a device having a touch-sensitive display system 112. In such embodiments, the focus selector is optionally: a corresponding finger or stylus contact, a representative point corresponding to the finger or stylus contact (e.g., the center of gravity of the corresponding contact or a point associated with the corresponding contact), or the center of gravity of two or more contacts detected on the touch-sensitive display system 112. However, in response to detecting a contact on the touch-sensitive surface 451 when the user interface shown in the figures is displayed on the display 450 together with the focus selector, similar operations are optionally performed on a device having a display 450 and a separate touch-sensitive surface 451. Additionally, similar operations are optionally performed on a device that communicates with a display generating component that is separate from the device (e.g., a wireless display device).

[0208] 5A to 5D An exemplary user interface for pairing an electronic accessory according to some embodiments is shown.

[0209] Figure 5A 4 shows a user interface 400 on the touch-sensitive display system 112 of the device 100. In some embodiments, (e.g., while displaying the user interface 400) the device 100 periodically and repeatedly listens for wireless broadcast signals (e.g., pairing requests) from one or more peripheral devices (e.g., wearable audio output devices 301-1 and 301-2 and wireless accessory box 480) for pairing the peripheral devices with the device 100. In some embodiments, as 5A to 5D As shown in , device 100 is able to detect a pairing request from a peripheral device when the peripheral device is within a threshold distance 502 of device 100, and is unable to detect a pairing request from the peripheral device when the peripheral device is outside the threshold distance 502. Figure 5A At the bottom of Figure 5A5 shows an exemplary spatial relationship (e.g., physical distance) between device 100 and wearable audio output devices 301-1 and 301-2 and wireless accessory box 480, where wearable audio output devices 301-1 and 301-2 and wireless accessory box 480 are outside a threshold distance 502 of device 100. In contrast, Figure 5B Wearable audio output devices 301-1 and 301-2 and wireless accessory case 480 (shown and hereinafter collectively referred to as earbud set 503) are shown within a threshold distance 502 of device 100, where the device is able to detect pairing requests from these peripheral devices.

[0210] Figure 5B Shown in Figure 5A An exemplary user interface 504 (e.g., a window) for initiating pairing of the device 100 with the peripheral device (e.g., the wearable audio output device 301-1) or the group of peripheral devices (e.g., the earbud group 503) is displayed after the user interface 400 in and in some embodiments in response to detecting movement of the peripheral device (e.g., the wearable audio output device 301-1) or the group of peripheral devices (e.g., the earbud group 503) from outside the threshold distance 502 to within the threshold distance 502. Figure 5B , the device 100 detects a signal from a peripheral device (e.g., Figure 5A The wearable audio output device 301-1 and Figure 5B In some embodiments, in response to detecting the pairing request from the wearable audio output device 301-1, the device 100 determines whether the wearable audio output device 301-1 meets the coupling criteria. Figure 5B In the example shown, the coupling criteria are met when the earbud (e.g., wearable audio output device 301-1) is placed in an earbud case (e.g., wireless accessory case 480) and / or is electrically coupled to the earbud case (e.g., forming earbud set 503). After the device 100 determines that the wearable audio output device 301-1 meets the coupling criteria (e.g., in response to the device 100 determining that the wearable audio output device 301-1 meets the coupling criteria), the device 100 displays the window 504-1 overlying the Figure 5A 4. Window 504-1 includes a representation 505 of an earbud group 503 and a button 507 (labeled "Connect") that, when activated by user input, initiates a connection between the device 100 and a peripheral device (e.g., Figure 5A4 and 50). Window 504-1 also includes a representation 506 of the physical indicia 482 on the wireless accessory box 480. In some embodiments, the user interface shown in window 504-1 is instead displayed on the entirety (or substantially all, e.g., greater than 95%, 96%, 97%, 98%, or 99%) of the touch-sensitive display system 112. Device 100 also displays an exit button 508 that, when activated by user input such as a tap gesture, causes window 504-1 to cease display, allowing the user to perform other operations on device 100. In some embodiments, where exit button 508 accompanies another user interface described herein (e.g., a user interface that is part of a usage tutorial), exit button 508, when activated by user input, causes that user interface to cease display.

[0211] Figures 5C to 5D Shown from Figure 5B Specifically, Figure 5C An input 510 (e.g., a tap gesture) on button 507 in window 504-1 is shown. In response to detecting input 510, device 100 initiates pairing of device 100 with the peripheral device of earbud set 503. Figure 5D , after the device 100 has paired with the peripheral device of the earbud set 503, the device 100 displays an indication 512 (labeled "Connected") in the window 504-2 to indicate that the device 100 is paired with (e.g., communicatively connected to) the earbud set 503. In some embodiments, the device 100 displays a button in the window 504-2 that, when activated, causes the device 100 to proceed from the pairing process to a usage tutorial for the wearable audio output device 301.

[0212] Figures 5E to 5R Example user interfaces and user interactions for adjusting the audio output of a wearable audio output device according to some embodiments are shown. Figure 5E and Figure 5F An exemplary user interface 514 is shown illustrating available user interactions of the wearable audio output device 301. Specifically, Figure 5E User interface 514-1 is shown having a representation 513 of the wearable audio output device and a user gesture 517 for decreasing the volume of the audio output at the wearable audio output device 301 (e.g., sliding along the handle portion 305 away from the head portion 303, see Figure 3B ) icon. Figure 5FUser interface 514-2 is shown having a representation 513 of the wearable audio output device and an illustration of a user gesture 519 (e.g., sliding along the handle portion 305 toward the head portion 303) for increasing the volume of the audio output at the wearable audio output device 301. Figure 5E and Figure 5F In the example of FIG, the representation 513 of the wearable audio output device includes a physical marker 484 on the wearable audio output device 301 (e.g., Figure 4C ) means 515.

[0213] Figure 5G to Figure 5R An exemplary user interaction with a wearable audio output device 301 for controlling audio output is shown according to some embodiments. Figure 5G Wearable audio output devices 301-1 and 301-2 are shown inserted into respective ears 516-1 and 516-2 of a user and having respective output volume levels 518-1 and 518-2. For example, the wearable audio output device 301 is configured to output audio via respective speakers 306 (e.g., Figure 3B ) plays back audio content at an output volume level of 518.

[0214] In some embodiments, each wearable audio output device 301 includes a handle portion 305 (e.g., see FIG. 1 ) that a user can use to provide input to the wearable audio output device. Figure 3B In some embodiments, the handle portion 305 is or includes an input device (e.g., input device 308) that responds to user input applied to the handle portion 305. In some embodiments, the input device includes a touch input (such as a Figure 5H In some embodiments, the input device includes a pressure-sensitive input device that responds to a pressure input applied to the handle portion 305 when the handle portion 305 is held between two fingers and squeezed, such as Figure 5O As shown. Although Figure 5H Only one wearable audio output device is shown in the figure, but a person of ordinary skill in the art will recognize that the wearable audio output device 301-1 can have a similar structure with a corresponding handle, and the same functionality described herein with reference to the wearable audio output device 301-2 can also be obtained using the wearable audio output device 301-1 and its corresponding handle.

[0215] Figures 5H to 5I5. Input 520 received at the handle portion 305 of the wearable audio output device 301-2 is shown. The input 520 has an initial position 520-a and an end position 520-b. For example, the input 520 is a swipe gesture toward the head portion 303 detected based on determining that the user's finger contact movement is greater than a predefined magnitude. In some embodiments, the handle portion 305 includes a set of capacitive sensors arranged to detect movement of a contact along the length of the handle portion 305. In some embodiments, the handle portion 305 includes a housing having one or more physically distinguished portions at positions corresponding to the set of capacitive sensors (e.g., to guide the user's finger during movement). In some embodiments, a user's finger contact movement that is less than a predefined magnitude does not change the volume of the audio output; for example, if the amount of the user's finger contact movement is less than the predefined magnitude, the user's finger contact movement is ignored.

[0216] Figure 5J In response to input 520, Figure 5G In response to input 520 (e.g., and based on determining that input 520 is a sliding gesture moving toward head portion 303), wearable audio output device 301 adjusts the volume of the audio output to corresponding output levels 522-1 and 522-2. In some embodiments, when the volume of the audio output is adjusted, audio feedback 524 is provided at each wearable audio output device 301 (e.g., an audible tone is output to indicate an increase in the volume level). In some embodiments, audio feedback 524 is adjusted based on one or more characteristics of input 520 (e.g., the speed of the sliding gesture and / or the distance of the sliding gesture). In some embodiments, audio feedback 524 includes an amount of tone corresponding to the amount of volume change due to input 520 (e.g., a tone for each increment of volume level change). In some embodiments, audio feedback (e.g., the same as or different from audio feedback 524) is provided to indicate to the user that the output volume is at a maximum or minimum level (e.g., as defined in the software of the wearable audio output device 301). In some embodiments, the wearable audio output device 301 includes one or more tactile output generators, optionally located in the handle portion 305. In some such embodiments, the output activates a tactile output to indicate that the input 520 is detected.

[0217] Figures 5K to 5L 301-1. Input 526 is received at handle portion 305 of wearable audio output device 301-1. Input 526 has an initial position 526-a and an end position 526-b. For example, input 526 is a swipe gesture detected away from head portion 303 based on determining that the user's finger contact has moved by more than a predefined magnitude.

[0218] Figure 5M In response to input 526, Figure 5J In response to input 526 (e.g., and based on determining that input 526 is a sliding gesture moving away from head portion 303), wearable audio output device 301 adjusts the volume of the audio output to corresponding output levels 528-1 and 528-2. In some embodiments, audio feedback 530 is provided at each wearable audio output device 301 (e.g., an audible tone is output to indicate a decrease in volume level). In some embodiments, audio feedback 530 includes an amount of tone corresponding to the amount of volume change due to input 526 (e.g., a tone for each increment of volume level change). In some embodiments, audio feedback 530 is different from audio feedback 524 (e.g., so that the user can distinguish between a volume increase and a volume decrease).

[0219] Figure 5N The wearable audio output devices 301 - 1 and 301 - 2 are shown inserted into respective ears 516 - 1 and 516 - 2 of a user. For example, the wearable audio output device 301 is configured to play back audio content via respective speakers 306 . Figure 5N Also shown is an exemplary user interface 532 that includes a representation of an album 531 (e.g., an album with audio content) and audio playback controls, such as a previous button for moving to the previous track or rewinding the audio being played, a play / pause button 533 for toggling audio playback on and off, and a next button for moving to the next track or fast-forwarding through the audio being played. In some embodiments, a volume control is also displayed concurrently with (e.g., below) the audio playback controls. Figure 5N , playback of media content from album 531 is paused, as indicated by the display of play button 533. In some embodiments, user interface 532 is presented at an electronic device (e.g., multifunction device 100 or device 300) that is communicatively coupled to wearable audio output device 301. In some embodiments, functionality associated with user interface 532 is available to the user via input and / or gestures at wearable audio output device 301 (e.g., whether or not user interface 532 is presented to the user).

[0220] Figure 5O Input 534 is shown as received at handle portion 305 of wearable audio output device 301-1. Input 534 is a different type of input than input 526, for example, a non-slide gesture such as a tap (e.g., an input with a contact duration less than a threshold duration), a press (e.g., an input with a contact intensity less than a threshold intensity), and / or a squeeze gesture. Figure 5P Shown in response to input 534 from Figure 5NIn response to input 534 (e.g., and based on determining that input 534 is a single squeeze gesture), playback of media content from album 531 is active (e.g., unpaused and playing), as indicated by Figure 5P A pause button 535 is displayed instead of a play button 533 ( Figure 5N ) indicated by . In some embodiments, audio feedback 536 is provided at the wearable audio output device 301-1. For example, audio feedback 536 is provided at the wearable audio output device that detects input 534, but not at another wearable audio output device. In some embodiments, audio feedback 536 includes one or more words (e.g., the terms "unpause" or "play"). In some embodiments, audio feedback 536 includes one or more tones and / or beeps. In some embodiments, audio feedback 536 is different from audio feedback 530 and audio feedback 524 (e.g., so that the user can distinguish between volume changes and playback changes).

[0221] Figure 5Q 305 of the wearable audio output device 301-1 is shown as input 538. Input 538 is a different type of input than input 534, for example, a long press input (e.g., an input with a contact duration greater than a threshold duration), a deep press input (e.g., an input with a contact intensity greater than a threshold intensity), and / or a long (and / or deep) squeeze input (e.g., a squeeze gesture that includes maintaining a squeeze of the handle portion 305 for at least a threshold amount of time).

[0222] Figure 5R In response to input 538, Figure 5P In response to input 538 (e.g., and based on determining that input 538 is a long press and / or long squeeze gesture), the wearable audio output device 301 enables (e.g., switches to or activates) active pass-through mode (sometimes also referred to as transparent mode). In active pass-through audio output mode, the wearable audio output device 301 outputs one or more pass-through audio components (e.g., plays at least a portion of ambient sound from outside the user's ear received by, for example, microphone 302-1), so that the user can hear a greater amount of ambient sound from the surrounding physical environment than would otherwise be perceptible to the user (e.g., a greater amount of ambient sound than would be heard using passive attenuation of the wearable audio output device 301 placed in the user's ear). In some embodiments, a squeeze gesture is a gesture that involves pressing something (e.g., handle portion 305) between two or more fingers. In some embodiments, the squeeze is maintained for less than a threshold amount of time (e.g., 0.5 seconds, 1 second, 1.5 seconds, or 2 seconds). In some embodiments, a long squeeze gesture is a squeeze gesture that is maintained for at least a threshold amount of time.

[0223] In some embodiments, in conjunction with changing the output mode, the wearable audio output device 301-1 outputs an audible tone and / or one or more words (e.g., audio feedback 540) to indicate that the audio output mode has changed. In some embodiments, the wearable audio output device 301 transitions from bypass mode or ANC (active noise cancellation) mode to active pass-through mode in response to input 538. In some embodiments, the wearable audio output device 301 transitions between modes in a predefined order to the next audio output mode, which in this example is active pass-through mode, as indicated by audio feedback 540. In some embodiments, the predefined order of the audio output modes is configurable using a settings menu.

[0224] In some embodiments, the wearable audio output device 301 includes one or more tactile output generators, optionally located in the handle portion 305. In some such embodiments, a tactile output is output to indicate detection of a user input and / or activation of a function of the wearable audio output device 301, e.g., in addition to or in lieu of providing audio feedback. In some embodiments, the tactile output for different functions and / or user inputs has different tactile output amplitudes, frequencies, and / or patterns (e.g., so that a user can distinguish between detection of different user inputs and / or activation of different functions).

[0225] Figures 5S to 5BI Exemplary user interfaces and user interactions for various features associated with an electronic accessory box are shown according to some embodiments.

[0226] Figure 5S An exemplary spatial relationship (e.g., physical distance) between device 100 and wireless accessory boxes 480-1, 480-2, and 480-3 is shown, where wireless accessory boxes 480-1, 480-2, and 480-3 are within a threshold distance 502 of device 100, e.g., where device 100 is able to detect pairing requests from peripherals and other devices. Figure 5S In the example, wireless accessory box 480-1 includes physical indicia 482-1, wireless accessory box 480-2 includes physical indicia 482-2 that is different from physical indicia 482-1, and wireless accessory box 480-3 does not include physical indicia (e.g., personalized physical indicia such as digital engraving and / or embossing).

[0227] Figure 5T For example, Figure 5A An exemplary user interface is shown following user interface 400 in FIG. 1 and in some embodiments in response to detecting a pairing request from wireless accessory box 480-1 to initiate pairing of device 100 with wireless accessory box 480-1. Figure 5T, device 100 detects a pairing request from wireless accessory box 480-1 when within threshold distance 502. Device 100 displays an overlay on Figure 5A 4. Window 504-1 on user interface 400 of wireless accessory box 480-1. Window 504-1 includes a representation 542-1 of wireless accessory box 480-1 and a button 507 (labeled "Connect"). Window 504-1 also includes a representation 544-1 of a physical marker 482-1 on wireless accessory box 480-1. In some embodiments, representation 542-1 is a three-dimensional representation of wireless accessory box 480-1. In some embodiments, representation 542-1 includes one or more animated movements (e.g., rotation, shifting, and / or lateral movement) as indicated by arrow 543. In some embodiments, representation 542-1 is capable of being moved by a user (e.g., in response to detecting a swipe or drag gesture at window 504-1).

[0228] Figure 5U For example, Figure 5A 4. An exemplary user interface is shown following user interface 400 in FIG. 4 and in some embodiments in response to detecting a pairing request from wireless accessory box 480-2 to initiate pairing of device 100 with wireless accessory box 480-2. Figure 5U , device 100 detects a pairing request from wireless accessory box 480-2 when within threshold distance 502. Device 100 displays an overlay on Figure 5A 4. Window 504-1 is shown on user interface 400 of wireless accessory box 480-2. Window 504-1 includes a representation 542-2 of wireless accessory box 480-2 and button 507. Window 504-1 also includes a representation 544-2 of the physical marking 482-2 on wireless accessory box 480-2. In this manner, representations 544-1 and 544-2 enable or assist a user in distinguishing between wireless accessory box 480-1 and wireless accessory box 480-2.

[0229] Figure 5V For example, Figure 5A An exemplary user interface is shown following user interface 400 in FIG. 1 and in some embodiments in response to detecting a pairing request from wireless accessory box 480 - 3 to initiate pairing of device 100 with wireless accessory box 480 - 3 . Figure 5V , device 100 detects a pairing request from wireless accessory box 480-3 when within threshold distance 502. Device 100 displays an overlay on Figure 5A Window 504-1 on user interface 400 of FIG. Window 504-1 includes representation 542-3 of wireless accessory box 480-3 and button 507. Wireless accessory box 480-3 does not include physical indicia 482, and therefore, window 504-1 does not include representation 544 of the physical indicia.

[0230] Figure 5W An exemplary user interface 550 for adding a physical tag to an electronic accessory (e.g., wireless accessory case 480) is shown. In some embodiments, the electronic accessory is a set of headphones, a smartwatch, a discoverable electronic device, a stylus, or an accessory case. In some embodiments, the physical tag is or includes an engraved, embossed, and / or printed, painted, or otherwise applied tag. In some embodiments, the user interface 550 is presented to the user as part of the purchase (or update) process for the electronic accessory. The user interface 550 includes a representation 552 of the electronic accessory including a preview 554 of the physical tag selected (e.g., entered or accepted) by the user. The user interface 550 also includes: an input portion 556 for accepting user input, such as input 558 (e.g., text and / or selections from portion 560 (e.g., emoticons and / or symbols)); a button 562 (labeled "Save"), which, when activated by user input, saves and / or confirms input 558 as a physical indicia of the electronic attachment; and a button 564 (labeled "Cancel"), which, when activated by user input, removes input 558 and / or closes the user interface 550 (e.g., returns to the previous user interface or advances to a new or next user interface). In some embodiments, the user interface 550 includes an option (e.g., a button or other affordance) that, when activated by the user, changes the font of the text input. In some embodiments, the user interface 550 includes an option (e.g., a button or other affordance) that, when activated by the user, allows the user to enter handwritten input (e.g., a signature, handwritten text, and / or a drawing).

[0231] Figure 5X Wireless accessory box 480 and associated wearable audio output device 301 are shown within a threshold distance of device 100 . Figure 5X The wireless accessory box 480 in includes the speaker 345 (e.g., and associated holes) and the physical indicia 574. The device 100 includes a user interface 570 (e.g., a lock and / or login screen). Figure 5X , wireless accessory case 480 is open (eg, lid 367 is upward), and wearable audio output device 301 is inserted into case 480.

[0232] Figure 5Y 480 in response to the occurrence of a condition associated with the wireless accessory box 480 (e.g., the closing of the lid 367). Figure 5XIn response to closing of the lid 367, the wearable audio output device 301 begins charging, audio feedback 585 is optionally provided via the speaker 345 to indicate to the user that the wearable audio output device 301 is charging, and a user interface 576 is presented on the device 100 (e.g., optionally displayed on a portion of another user interface (such as the user interface 570)). In some embodiments, the wearable audio output device 301 begins charging in response to being inserted (e.g., installed and / or secured) within the wireless accessory box 480. In some embodiments, the audio feedback 585 includes one or more tones and / or one or more spoken terms. The user interface 576 includes a representation 578 of the wireless accessory box 480 (including a representation 579 of the physical indicia 574) and a representation 580 of the wearable audio output device 301. The user interface 576 also includes an indication 582 of the charging status of the wearable audio output device 301. In Figure 5Y In the example shown, the wearable audio output device 301 has a charge level of 20%. The user interface 576 also includes an indication 584 of the charging status of the case 480. Figure 5Y In the example shown, the cartridge 480 is 50% charged.

[0233] In addition, Figure 5Y In the example shown, optimization of charging of the wearable audio output device 301 is enabled, as indicated by an indication 586 (e.g., the text "Charging Optimization") below the representation 580 of the wearable audio output device 301. In some embodiments, charging of the wearable audio output device 301 by the case 480 is performed under the control of the device 100 (e.g., when the device 100 is in communication with the case 480 and / or the wearable audio output device 301). For example, the device 100 sends an instruction to the case 480 and / or the wearable audio output device 301 to initiate charging of the wearable audio output device 301 by the case 480, and optionally limits charging to a threshold charge level in accordance with enabled optimized charging, or alternatively allows full charging (e.g., to the full storage capacity of the wearable audio output device 301) in accordance with disabled optimized charging. The user interface 576 also includes an optimize charging override button 588 (e.g., labeled "Fully Charge Now") that, when activated, disables optimization of charging of the wearable audio output device 301 and initiates charging of the wearable audio output device 301 to a fully charged state if other charging criteria are met. Figure 5Y In the example shown, optimized charging for the case 480 is not enabled (e.g., unavailable or disabled), so no optimized charging indication is displayed for the case 480, nor is any optimized charging overlay button displayed (compared to optimized charging for the wearable audio output device 301).

[0234] Figure 5Z 1 is shown with wireless accessory box 480 and associated wearable audio output device 301-1 within a threshold distance of device 100. Figure 5Z , the wireless accessory box 480 is open (eg, with the lid 367 facing upward), and one wearable audio output device 301 (wearable audio output device 301 - 1 ) is inserted into the box 480 .

[0235] Figure 5AA 480 in response to the occurrence of a condition associated with the wireless accessory box 480 (e.g., the closing of the lid 367). Figure 5Z In response to closing of lid 367, audio feedback 587 is provided via speaker 345, indicating to the user that only one wearable audio output device 301 is within case 480, and user interface 590 is presented on device 100 (e.g., optionally displayed on a portion of another user interface such as user interface 570 (see FIG. Figure 5X )). In some embodiments, audio feedback 587 includes one or more tones and / or one or more spoken terms. In some embodiments, audio feedback 587 is different from audio feedback 585 (e.g., includes different tones, words, and / or frequencies) so that the user can distinguish between these conditions. User interface 590 includes a representation 592 of wireless accessory box 480 (including a representation 594 of physical mark 574) and a representation 596 of wearable audio output device 301-1. User interface 576 also includes a notification 598 that box 480 only includes one wearable audio output device 301.

[0236] Figure 5AB A wireless accessory box 480 and associated wearable audio output device 301 are shown within a threshold distance of device 100. Figure 5AB , the wireless accessory case 480 is closed (e.g., lid 367 is down), and the wearable audio output device 301 is inserted into the case 480. Figure 5AB In the example of FIG. 5 , wearable audio output device 301 includes physical indicia 575 , and wireless accessory box 480 includes physical indicia 574 .

[0237] Figure 5AC 480 in response to the occurrence of a condition associated with the wireless accessory box 480 (e.g., the opening of the cover 367). Figure 5ABIn response to opening the lid 367, audio feedback 5001 is provided via the speaker 345, thereby indicating to the user the charging status of the wearable audio output device 301, and a user interface 5002 is presented on the device 100 (e.g., optionally displayed on a portion of another user interface (such as the user interface 570)). In some embodiments, the audio feedback 5001 includes one or more tones and / or one or more spoken terms. In some embodiments, the audio feedback 5001 is different from at least one of the audio feedback 585 and 587 (e.g., includes different tones, words, and / or frequencies) so that the user can distinguish between these conditions. The user interface 5002 includes a representation 5012 of the wireless accessory box 480 (including a representation 5014 of the physical marker 575) and a representation 5006 of the wearable audio output device 301 (including a representation 5008 of the physical marker 574). The user interface 5002 also includes an indication 5004 of the charging status of the wearable audio output device 301. In Figure 5AC In the example shown, the wearable audio output device 301 has a charge level of 40%. The user interface 5002 also includes an indication 5010 of the charging status of the case 480. Figure 5AC In the example shown, the cartridge 480 is at 10% charge.

[0238] Figure 5AD The transitions are shown in response to the occurrence of a condition associated with the wireless accessory box 480 (e.g., the opening of the lid 367). Figure 5AD In the example shown, wireless accessory box 480 is empty (e.g., does not contain any wearable audio output device). In response to opening lid 367, audio feedback 5018 is provided via speaker 345 to indicate to the user the charge status of wireless accessory box 480 (e.g., 15% charge). For example, when box 480 is open and a wearable audio output device is inside, audio feedback indicating the charge status of the wearable audio output device is provided. In this example, when box 480 is open but empty (e.g., no wearable audio output device is inside), audio feedback indicating the charge status of the box is provided. In some embodiments, audio feedback 5018 includes one or more tones and / or one or more spoken terms (e.g., recorded and / or simulated sound output). In some embodiments, audio feedback 5018 is different from at least one of audio feedback 585, 587, and 5001 (e.g., includes a different tone, word, and / or frequency) so that the user can distinguish between these conditions.

[0239] Figure 5AE1 is a diagram illustrating a transition that occurs in response to the occurrence of a condition associated with wireless accessory box 480 (e.g., insertion of wearable audio output device 301-1). In response to the insertion of wearable audio output device 301-1, audio feedback 5020 is provided via speaker 345, thereby indicating to the user that wearable audio output device 301-1 has been properly inserted (e.g., electrically coupled to wireless accessory box 480). In some embodiments, audio feedback 5020 includes one or more tones and / or one or more spoken terms. In some embodiments, audio feedback 5020 is different from at least one of audio feedback 585, 587, 5001, and 5018 (e.g., includes a different tone, word, and / or frequency) so that the user can distinguish between the conditions.

[0240] Figure 5AF Wireless accessory box 480 is shown including speaker 345 (eg, and associated aperture), input device 346 , and physical indicia 574 . Figure 5AF Also shown is user input 5024 (eg, a tap or press input) at input device 346 . Figure 5AG Shown in response to detecting user input 5024 from Figure 5AF In response to detecting user input 5024, audio feedback 5026 is provided via speaker 345, thereby indicating to the user that wireless accessory case 480 (and optionally a wearable audio output device inserted into case 480) is pairing with an electronic device (e.g., device 100).

[0241] Figure 5AG Also shown is audio feedback 5028 provided via speaker 345, indicating to the user that wireless accessory case 480 (and optionally a wearable audio output device inserted into case 480) has completed pairing with the electronic device (e.g., in response to user activation of the Figure 5B In some embodiments, audio feedback 5026 and / or 5028 includes one or more tones and / or one or more spoken terms. In some embodiments, audio feedback 5028 is different from 5026 (e.g., includes a different tone, word, and / or frequency) so that the user can distinguish between the conditions.

[0242] Figure 5AHAudio feedback 5029 is shown provided via speaker 345 to indicate to the user that wireless accessory box 480 has failed to pair with the electronic device (e.g., due to device mismatch, permission settings, and / or connection issues). In some embodiments, audio feedback 5029 includes one or more tones and / or one or more spoken terms. In some embodiments, audio feedback 5029 is different from at least one of audio feedback 5026 and 5028 (e.g., includes a different tone, word, and / or frequency) so that the user can distinguish between these conditions.

[0243] Figure 5AI Wireless accessory box 480 is shown including speaker 345 (eg, and associated aperture), input device 346 , and physical indicia 574 . Figure 5AI Also shown is user input 5030 (e.g., a long and / or deep press input) at input device 346. In some embodiments, Figure 5AF User input 5024 in is a first type of input, and user input 5030 is a second type of input different from the first type. Figure 5AI Also shown is the process of resetting the system from the factory in response to detecting user input 5030 (e.g., initiation of a factory reset). Figure 5AF In response to detecting user input 5030, audio feedback 5032 is provided via speaker 345, thereby indicating to the user that wireless accessory box 480 (and optionally a wearable audio output device inserted into box 480) is initiating a factory reset. In some embodiments, wireless accessory box 480 provides additional audio feedback (e.g., different from audio feedback 5032) upon completion of the factory reset.

[0244] Figure 5AJ The device 100 and wireless accessory box 480 are shown according to some embodiments. The device 100 is shown, for example, in Figure 5A 400 and, in some embodiments, in response to activation of an accessory location user interface element (e.g., an icon or button), a user interface 5035 is displayed. User interface 5035 corresponds to wireless accessory case 480 and includes a label 5036 ("Max's Charging Case") and a button 5038 that, when activated by a user, causes a sound to be output at wireless accessory case 480.

[0245] Figure 5AK5040 and a corresponding audio output 5042 at the wireless accessory box 480 are shown. In some embodiments, in response to detecting the user input 5040 at a location corresponding to the button 5038, the wireless accessory box 480 provides the audio output 5042 via the speaker 345. In some embodiments, the audio output 5042 includes one or more tones and / or one or more spoken terms. In some embodiments, the wireless accessory box 480 generates the audio output 5042 multiple times. For example, activation of the button 5038 toggles the audio output 5042, and the process repeats until the user activates the button 5038 again (or the user activates another affordance to disable the audio output 5042, or another predefined user input is detected at the wireless accessory box 480, such as a button press or lid movement). In some embodiments, the wireless accessory box 480 generates the audio output 5042 a preset number of times (e.g., 5, 10, or 20) in response to activation of the button 5038.

[0246] Figure 5AL Wireless accessory box 480 is shown with wearable audio output devices 5046 and 5050 inserted therein. Figure 5AL The wireless accessory box 480 in FIG. 5 includes a speaker 345 (e.g., and associated holes), an input device 346, and a physical marker 574. The wearable audio output device 5046 includes a physical marker 5048 (e.g., the same as or similar to the physical marker 574), and the wearable audio output device 5050 includes a physical marker 5052 that is different from the physical marker 5048. Figure 5AL , wireless accessory box 480 is open (eg, lid 367 is upward).

[0247] Figure 5AM 480 in response to the occurrence of a condition associated with the wireless accessory box 480 (e.g., the closing of the lid 367). Figure 5ALIn response to closing lid 367, one or more warning alerts are generated, such as providing audio feedback 5054 via speaker 345 to indicate to the user that wearable audio output device 301 is mismatched, and / or a user interface 5056 is presented on device 100 (e.g., optionally displayed on a portion of another user interface, such as user interface 570). In some embodiments, audio feedback 5054 includes one or more tones and / or one or more spoken terms. In some embodiments, audio feedback 5054 includes information about the type of mismatch (e.g., different owner and / or different version) and / or information about which wearable audio output device is different. User interface 5056 includes a representation 5058 of wireless accessory case 480 (including a representation 5060 of physical indicia 5048), a representation 5062 of wearable audio output device 5046 (including a representation 5064 of physical indicia 574), and a representation 5063 of wearable audio output device 5050 (including a representation 5065 of physical indicia 5052). The user interface 5056 also includes a notification 5057 that the wearable audio output device 5046 has a different owner (e.g., as indicated by the physical indicia 5052) than the wearable audio output device 5050 and / or the wireless accessory case 480. In some embodiments, the owner of the device is based on the account to which the device is linked or associated (e.g., devices linked to the same account are considered to have the same owner). In some embodiments, the owner of the device is based on the identity of the person who purchased the device.

[0248] Figure 5AN and Figure 5AO Similar to Figure 5AL and Figure 5AM , the difference is Figure 5AN and Figure 5AO In some embodiments, wearable audio output devices 5046 and 5050 do not include physical markings (e.g., physical markings 5048 and 5052) to distinguish them from each other. In some embodiments, wearable audio output devices 5046 and 5050 do not include personalized physical markings (e.g., markings set, selected, and / or accepted by a user). In some embodiments, user interface 5056 includes an indication 5086 of which wearable audio output device is associated with an owner other than wireless accessory box 480. In some embodiments, notification 5057 indicates which wearable audio output device is associated with an owner other than wireless accessory box 480.

[0249] Figure 5AP Wireless accessory box 480 is shown with wearable audio output devices 5046 and 5070 inserted therein. Figure 5APThe wireless accessory box 480 in FIG. 5 includes a speaker 345 (e.g., and associated holes), an input device 346, and a physical marker 574. The wearable audio output device 5046 includes a physical marker 5048 (e.g., the same as or similar to the physical marker 574), and the wearable audio output device 5070 includes a physical marker 5072 (e.g., the same as the physical marker 5048). Figure 5AP , wireless accessory box 480 is open (eg, lid 367 is upward).

[0250] Figure 5AQ 480 in response to the occurrence of a condition associated with the wireless accessory box 480 (e.g., the closing of the lid 367). Figure 5AP In response to closing the lid 367, audio feedback 5074 is provided via the speaker 345, thereby indicating to the user that the wearable audio output device 301 is mismatched, and a user interface 5076 is presented on the device 100 (e.g., optionally displayed on a portion of another user interface (such as the user interface 570)). In some embodiments, the audio feedback 5074 includes one or more tones and / or one or more spoken terms. In some embodiments, the audio feedback 5074 includes information about the type of mismatch (e.g., different owner and / or different version) and / or information about which wearable audio output device is different. The user interface 5076 includes a representation 5078 of the wireless accessory box 480 (including a representation 5080 of the physical indicia 5048), a representation 5082 of the wearable audio output device 5046 (including a representation 5084 of the physical indicia 574), and a representation 5083 of the wearable audio output device 5070 (including a representation 5085 of the physical indicia 5072). User interface 5056 also includes notification 5077 that wearable audio output device 5046 has a different version (e.g., a different hardware and / or software version) than wearable audio output device 5070 and / or wireless accessory box 480. In some embodiments, user interface 5056 includes an indication 5087 of the version associated with one or both of wearable audio output devices 5046 and 5070 in wireless accessory box 480. In some embodiments, the wearable audio output devices having different versions are due to the wearable audio output devices being different generations of devices.

[0251] Figure 5AR The device 100 and wireless accessory box 480 are shown according to some embodiments. The device 100 is shown, for example, in Figure 5A400 and in some embodiments in response to activation of an accessory user interface element (e.g., an icon or button). User interface 5090 corresponds to wireless accessory case 480 (labeled "Max's Charging Case") and includes a volume control element 5091 that adjusts the volume of the audio output of speaker 345 upon user interaction. Wireless accessory device 480 is within a threshold communication distance of device 100 and has a Figure 5AR The volume level indicated by volume level 5094 in the user interface 5090, where volume level 5094 corresponds to volume level indicator 5092 in the user interface 5090. Figure 5AS User input 5095 is shown detected at volume control element 5091. Input 5095 is as follows Figure 5AS , indicated by the downward-pointing arrow in the .

[0252] Figure 5AT shows the response to input 5095 from Figure 5AR In response to input 5095 (e.g., and based on determining that input 5095 is a swipe gesture moving in a direction toward a lower volume (e.g., a downward swipe)), wireless accessory box 480 adjusts the volume of the audio output to volume level 5097 (e.g., a volume level lower than volume level 5094), which corresponds to volume level indicator 5096 in user interface 5090. Figure 5AU User input 5098 is shown detected at volume control element 5091. In some embodiments, input 5098 is a tap or press input.

[0253] Figure 5AV Shown in response to input 5098 from Figure 5AT In response to input 5098 (e.g., and based on determining that input 5098 is a tap gesture at a location corresponding to a zero volume level on volume control element 5091), wireless accessory box 480 disables audio output from speaker 345, as indicated by volume indicator 5100 corresponding to volume level indicator 5099 of user interface 5090. In some embodiments, input 5098 (e.g., a tap or press gesture) causes wireless accessory box 480 to switch audio output from speaker 345 (e.g., regardless of the location of input 5098 on volume control element 5091). In some embodiments, input 5098 is a press gesture, and the volume level of wireless accessory box 480 is adjusted based on the location and / or duration of the press gesture.

[0254] Figure 5AW Device 100 is shown including volume buttons 5104 (eg, volume up button 5104 - 1 and volume down button 5104 - 2 ) and ringer switch 5102 . Figure 5AW Also shown is a wireless accessory device 480 that is within a threshold communication range of device 100 . Figure 5AW Also shown are an indicator 5106 of the ring status of device 100 and an indicator 5108 of the volume level of wireless accessory device 480 .

[0255] Figure 5AX Shown from Figure 5AW Specifically, Figure 5AX Device 100 is shown with a user's hand providing input 5110 at volume down button 5104-2 (e.g., to disable the ringer of device 100). Figure 5AX Input 5110 is shown provided at volume down button 5104-2, but input 5110 may similarly be provided at ringer switch 5102 (eg, to toggle the state of the ringer between enabled and disabled).

[0256] Figure 5AY Shown from Figure 5AX Specifically, Figure 5AY It is shown that in response to input 5110 at volume down button 5104 - 2 , the ringer of device 100 is disabled (eg, device 100 is set to a silent state), as shown by ringer state indicator 5112 . Figure 5AY Also shown is that the audio output of wireless accessory box 480 is disabled (eg, the volume level of speaker 345 is set to zero), as indicated by volume indicator 5114 .

[0257] Figure 5AZ Shown are device 100 and wireless accessory box 480 according to some embodiments. Figure 5AZ Wireless accessory box 480 in is beyond communication threshold distance 5119 (eg, not actively communicating with device 100 ) and has a non-zero volume level, as indicated by volume level indicator 5108 .

[0258] Figure 5AZ A setup user interface 5117 is shown, for example, displayed on Figure 5A In some embodiments, the user interface shown in FIG is displayed on the entire user interface (or substantially all, such as greater than 95%, 96%, 97%, 98%, or 99%) (e.g., in response to detecting a slide gesture or activation of a button or icon). Figure 5A The user interface 400 is at least partially obscured or blurred behind the settings user interface 5117, so that Figure 5A The different features of the user interface 400 are not identifiable. The settings user interface 5117 includes a number of controls for various features of the device 100. Notably, the settings user interface 5117 includes a focus mode control 5118.

[0259] Figure 5BA Input 5120 at the focus mode control 5118 is shown (e.g., a press gesture that satisfies an intensity threshold above the nominal contact detection intensity threshold, or a long press gesture maintained on the touch-sensitive display system 112 for at least a threshold amount of time).

[0260] Figure 5BB Shown from Figure 5BA Specifically, Figure 5BB Focus mode user interface 5121 is shown displayed in response to input 5120 (e.g., in place of or overlapping user interface 5117). Focus mode user interface 5121 includes controls for two or more focus modes, such as a do not disturb control 5126, personal controls 5128, and sleep controls 5130. The do not disturb control 5126, when activated by the user, mutes at least a subset of incoming calls and / or notifications at device 100. In some embodiments, the do not disturb control is user-customizable (e.g., the user can set which types of incoming calls and / or notifications are muted). The personal controls 5128, when activated by the user, mutes at least a subset of incoming calls and / or notifications at device 100 (e.g., the same or a different subset as the do not disturb control 5126). The sleep controls 5130, when activated by the user, mutes at least a subset of incoming calls and / or notifications at device 100 (e.g., the same or a different subset as the do not disturb control 5126 and / or personal controls 5128). For example, the personal control 5128 sets notification and ringtone settings during the user's personal time, and the sleep control 5130 sets notification and ringtone settings during the user's sleep time.

[0261] Figure 5BC Input 5132 is shown at the do not disturb control 5126 (e.g., a press gesture that satisfies an intensity threshold above the nominal contact detection intensity threshold, or a long press gesture maintained on the touch-sensitive display system 112 for at least a threshold amount of time).

[0262] Figure 5BD Shown from Figure 5BC Specifically, Figure 5BD Do not disturb mode is shown enabled in response to input 5132 as shown by indicator 5136. Figure 5BD Also shown is a wireless accessory device 480 beyond the threshold distance 5119 and having a non-zero volume level as indicated by volume level indicator 5108 (eg, wireless accessory device 480 is not affected by the do not disturb mode enabled at device 100).

[0263] Figure 5BE Shown from Figure 5BD Specifically, Figure 5BEThe wireless accessory device 480 is shown within a threshold distance 5119, and the audio output of the wireless accessory box 480 is disabled (e.g., the volume level of the speaker 345 is set to zero), as indicated by the volume indicator 5138. In some embodiments, based on moving within the threshold distance 5119, the wireless accessory box 480 establishes a communication connection with the device 100. In some embodiments, after establishing the communication connection, the wireless accessory box 480 receives information about the do not disturb mode enabled at the device 100 and disables the audio output in response to the received information.

[0264] Figure 5BF Shown from Figure 5BE Specifically, Figure 5BF The wireless accessory device 480 is shown beyond a threshold distance 5119, and the audio output of the wireless accessory box 480 is disabled (e.g., the volume level of the speaker 345 is set to zero), as indicated by the volume indicator 5138. In some embodiments, upon movement beyond the threshold distance 5119, the wireless accessory box 480 maintains the audio settings (e.g., does not adjust the volume of the audio output). In some embodiments, upon movement beyond the threshold distance 5119, the wireless accessory box 480 maintains the audio settings established when the wireless accessory box 480 communicated with the device 100.

[0265] Figure 5BG Shown from Figure 5BE Specifically, Figure 5BG The wireless accessory device 480 is shown beyond a threshold distance 5119, and the audio output of the wireless accessory box 480 is enabled (e.g., the volume level of the speaker 345 is set to a non-zero value), as indicated by the volume level indicator 5108. In some embodiments, the wireless accessory box 480 enables the audio output (e.g., enables the audio output at a volume level that was established before the audio output was disabled) based on the movement beyond the threshold distance 5119. In some embodiments, the wireless accessory box 480 enables the audio output based on a user setting (e.g., a user preference regarding whether to maintain a silent setting when not communicating with the electronic device).

[0266] Figure 5BH Shown from Figure 5BC Specifically, Figure 5BH Do not disturb mode is shown enabled in response to input 5132 as shown by indicator 5136. Figure 5BH Also shown are wireless accessory device 480 and wearable audio output device 5142 in communication with each other and beyond a threshold distance 5119 . Figure 5BHAlso shown is a wireless accessory device 480 having a non-zero volume level as indicated by volume level indicator 5108 (eg, wireless accessory device 480 is not affected by the do not disturb mode enabled at device 100 ).

[0267] Figure 5BI Shown from Figure 5BH Specifically, Figure 5BI Wearable audio output device 5142 is shown within threshold distance 5119 while communicating with wireless accessory box 480 that is beyond threshold distance 5119. Figure 5BI Also shown is that the audio output of the wireless accessory box 480 is disabled (e.g., the volume level of the speaker 345 is set to zero), as indicated by the volume indicator 5150. In some embodiments, based on the wearable audio output device 5142 moving within the threshold distance 5119, the wearable audio output device 5142 establishes a communication connection with the device 100. In some embodiments, after establishing the communication connection, the wearable audio output device 5142 receives information about the Do Not Disturb mode enabled at the device 100. In some embodiments, the wearable audio output device 5142 transmits the information about the Do Not Disturb mode to the wireless accessory box 480 after receiving the information about the Do Not Disturb mode. In some embodiments, in response to the wireless accessory box 480 receiving the information about the Do Not Disturb mode enabled at the device 100, the wireless accessory box 480 disables the audio output. Thus, Figures 5AR to 5BI Various ways of adjusting the volume of the audio output at wireless accessory box 480 (eg, increasing the volume, decreasing the volume, disabling the audio output, and / or enabling the audio output) are shown.

[0268] Figures 5BJ to 5CB Example user interfaces and user interactions for adjusting the audio output of a wearable audio output device according to some embodiments are shown.

[0269] Figure 5BJ An exemplary user interface 5158 is shown, which is similar to the reference Figure 4A shown and described and also Figure 5A In addition, Figure 5BJ A swipe gesture 5160 is shown starting from an initial position in the upper right corner of the touch-sensitive display system 112 and moving downward across the touch-sensitive display system 112 . Figure 5BK Shows the response from Figure 5BJ The initial position in Figure 5BK , device 100 displays a first portion of a settings user interface 5164 (sometimes also referred to as a control panel user interface) over at least a portion of user interface 5158 .

[0270] Figure 5BL The settings user interface 5164 is shown displayed over all (or substantially all, e.g., greater than 95%, 96%, 97%, 98%, or 99%) of the user interface 5158 (e.g., in response to ceasing to detect the swipe gesture 5160, optionally after the swipe gesture 5160 moves further downward across the touch-sensitive display system 112). In some embodiments, in response to the user activating the settings icon (e.g., Figure 4A 446 shown in the figure). In some embodiments, the user interface 5158 is at least partially obscured or obscured behind the settings user interface 5164, so that different features of the user interface 5158 are not discernible. The settings user interface 5164 includes a plurality of controls for various features of the device 100. Notably, the settings user interface 5164 includes a volume control 5166. Up and down swipe inputs on the volume control 5166 can be provided to increase or decrease the volume of the audio output from the device 100 (e.g., via the wearable audio output device 301), respectively.

[0271] Figure 5BM User input 5168 is shown detected at volume control 5166. Input 5168 is as follows Figure 5BM , indicated by the upward arrow in the . Figure 5BN Shown in response to input 5168 from Figure 5BM In response to input 5168 (e.g., and based on determining that input 5168 is a swipe gesture moving in a direction toward a higher volume (e.g., an upward swipe)), the volume of the audio output at wearable audio output device 301 increases to volume level 5180. Figure 5BO User input 5182 (e.g., a different type of input than input 5168) is shown detected at volume control 5166. In some embodiments, input 5182 is a tap, press, long press, and / or deep press input.

[0272] Figure 5BP Shown from Figure 5BO Specifically, Figure 5BP An audio control user interface 5184 is shown displayed in response to input 5182 (e.g., in place of or overlapping user interface 5164). Audio control user interface 5184 includes a volume control 5196 that is an enlarged version of volume control 5166 ( Figure 5BN ) and allows finer (e.g., more granular) volume control. User interface 5164 also includes noise controls 5194, spatial audio controls 5192, and dialogue enhancement controls 5190. Figure 5BPThe wearable audio output device 301 is shown operating with the spatial audio mode disabled and the conversation mode disabled, as indicated by indicator 5191. Additionally, as shown Figure 5BP As indicated by indicator 5195 in FIG, the wearable audio output device 301 operates in a transparent (e.g., active pass-through) audio output mode, wherein one or more pass-through audio components are output such that a user can hear a greater amount of ambient sound from the surrounding physical environment than would otherwise be perceived by the user (e.g., as described herein with reference to FIG). Figure 3F described above).

[0273] Figure 5BQ User input 5198 is shown detected at the conversation enhancement control 5190. In some embodiments, the input 5198 is a tap, press, long press, and / or deep press input. Figure 5BR Shown from Figure 5BQ Specifically, Figure 5BR An audio control user interface 5200 is shown in which display of the noise control 5194, spatial audio control 5192, and dialogue enhancement control 5190 is replaced by display of a dialogue enhancement adjustment control 5206 and an enhancement level indicator 5204. In response to input 5198 (e.g., and based on a determination that input 5198 is a tap or press gesture at dialogue enhancement control 5190 or otherwise satisfies predefined input activation criteria), the noise control 5194, spatial audio control 5192, and dialogue enhancement control 5190 cease to be displayed, and the dialogue enhancement adjustment control 5206 and the enhancement level indicator 5204 are displayed. In some embodiments, in response to input 5198, the dialogue enhancement adjustment control 5206 and the enhancement level indicator 5204 are displayed simultaneously with the noise control 5194 and / or spatial audio control 5192. In some embodiments, the conversation enhancement adjustment control 5206, when adjusted by the user (e.g., by performing a drag gesture relative to the enhancement level indicator 5204), adjusts the enhancement level (e.g., amplifies) of conversation audio picked up by one or more microphones of the wearable audio output device (e.g., microphone 302), conversation audio picked up by one or more microphones of the electronic device (e.g., microphone 113), or conversation audio picked up by one or more external microphones.

[0274] Figure 5BS A user input 5210 is shown detected at the noise control 5194 in the audio control user interface 5184. In some embodiments, the input 5210 is a tap, press, long press, and / or deep press input. Figure 5BS The wearable audio output device 301 is also shown operating with conversation enhancement enabled, as shown by indicator 5209 in the user interface 5184. Figure 5BT Shown from Figure 5BSSpecifically, Figure 5BT An audio control user interface 5201 is shown in which the display of noise controls 5194, spatial audio controls 5192, and dialogue enhancement controls 5190 is replaced by the display of expanded noise management controls 5211, which include representations of a plurality of available audio output modes (e.g., three available audio output modes) for the wearable audio output device 301, each of which is associated with a different audio output mode available for the wearable audio output device 301. Specifically, the expanded noise management controls 5211 include a pass-through icon 5216, a bypass icon 5214, and an active noise control icon 5212. The active noise control icon 5212 represents an active noise control ("ANC") audio output mode in which one or more audio cancellation audio components are output to at least partially cancel ambient sounds from the surrounding physical environment that would otherwise be perceived by the user. The bypass icon 5214 represents a bypass audio output mode in which neither an audio cancellation audio component nor a pass-through audio component is provided (e.g., any amount of ambient sound perceived by the user is due to the physical attenuation of the wearable audio output device 301 (and any attached ear tips) in the user's ears). A selection indicator 5217 displayed above the pass-through icon 5216 (e.g., and not displayed above the bypass icon 5214 or the active noise control icon 5212) indicates that the audio pass-through mode represented by the pass-through icon 5216 is the mode in which the wearable audio output device 301 is currently operating. In response to input 5210 (e.g., and based on determining Figure 5BS The input 5210 shown is a tap or press gesture at the noise control 5194), the noise control 5194, the spatial audio control 5192, and the conversation enhancement control 5190 cease to be displayed, and the expanded noise management control 5211 is displayed. In some embodiments, in response to the input 5210, the expanded noise management control 5211 is displayed simultaneously with the spatial audio control 5192 and / or the conversation enhancement control 5190.

[0275] Figure 5BU User input 5218 is shown detected at the active noise control icon 5212 in the audio control user interface 5201. In some embodiments, the input 5218 is a tap, press, long press, and / or deep press input. Figure 5BV Shown from Figure 5BU Specifically, Figure 5BV The audio control user interface 5184 is shown displayed in response to the input 5218. Figure 5BV , the noise control 5194 is set to ANC (e.g., based on detecting user input 5218 at the active noise cancellation icon 5212). Figure 5BVAlso shown is that spatial audio is disabled, as indicated by spatial audio control 5192, and that dialogue enhancement mode is enabled (but inactive), as indicated by dialogue enhancement control 5190 and indicator 5219. In some embodiments, dialogue enhancement mode is disabled when ANC is active. In some embodiments, dialogue enhancement mode is enabled only when pass-through mode is enabled.

[0276] Figure 5BW A settings user interface 5164 is shown that includes a hearing control 5222 and a user input 5224 detected at the hearing control 5222. In some embodiments, the input 5224 is a tap, press, long press, and / or deep press input. Figure 5BX Shown from Figure 5BW Specifically, Figure 5BX A hearing user interface 5230 is shown that includes a plurality of activatable control options for the wearable audio output device 301, such as the following options, or a subset or superset thereof:

[0277] Background sound control 5232, which, when activated, initiates a process for producing background sound at the wearable audio output device 301;

[0278] A live listening control 5234 , which, when activated, initiates a process for providing audio data at the wearable audio output device 301 , where the audio data is captured via a microphone at the device 100 ;

[0279] • Decrease loud control 5235, which, when activated, initiates a process for decreasing the volume of sound that meets one or more criteria;

[0280] Ambient noise control 5236, which is used to set the audio output mode available for the wearable audio output device 301 (e.g., active noise cancellation mode, bypass mode, and / or pass-through mode);

[0281] Conversation enhancement control 5242, which, when activated, initiates a process for adjusting the audio output of wearable audio output device 301 to enhance conversational audio;

[0282] A real-time listening control 5244 for switching the real-time listening mode on and off;

[0283] Background sound control 5246, which is used to toggle background sound mode on and off; and

[0284] • Conversation enhancement control 5248, which is used to toggle conversation enhancement mode on and off.

[0285] exist Figure 5BXIn the example shown in FIG5 , the wearable audio output device 301 operates in pass-through mode, as indicated by the ambient noise control 5236. In some embodiments, selecting an option to activate a control option in the settings user interface 5164 assigns the selected type of operation to the operation of both wearable audio output devices 301.

[0286] Figure 5BY User input 5250 is shown detected at conversation enhancement icon 5248. In some embodiments, input 5250 is a tap, press, long press, and / or deep press input. Figure 5BZ Shown from Figure 5BY Specifically, Figure 5BZ Hearing user interface 5252 is shown with background sound control 5232 deactivated, conversation enhancement mode enabled, as indicated by conversation enhancement control 5242 and conversation enhancement icon 5248, and displayed with conversation enhancement adjustment control 5256. In response to input 5250 (e.g., and based on a determination that input 5250 is a tap or press gesture at conversation enhancement icon 5248), background sound control 5232 deactivated (e.g., to provide space to display conversation enhancement adjustment control 5256) and displayed with conversation enhancement adjustment control 5256. In some embodiments, in response to input 5250, conversation enhancement adjustment control 5256 is displayed concurrently with background sound control 5232 (e.g., by deactivating different controls from hearing user interface 5230 and / or adjusting the size / spacing of controls to display conversation enhancement adjustment control 5256 concurrently with controls of user interface 5230).

[0287] Figure 5CA User input 5260 is shown detected at the reduce loud control 5235. In some embodiments, the input 5260 is a tap, press, long press, and / or deep press input. Figure 5CB Shown from Figure 5CA Specifically, Figure 5CBHearing user interface 5262 is shown in which conversation enhancement control 5242 (and conversation enhancement adjustment control 5256) have ceased to be displayed (e.g., but conversation enhancement mode is still enabled, as indicated by conversation enhancement icon 5248), louder mode is enabled, as indicated by louder control 5235, and louder adjustment control 5268 and associated information 5266 are displayed. In response to input 5260 (e.g., and based on determining that input 5260 is a tap or press gesture at louder control 5235), conversation enhancement control 5242 ceases to be displayed (e.g., to provide space to display louder adjustment control 5268), and louder adjustment control 5268 is displayed. In some embodiments, louder adjustment control 5268 adjusts the maximum audio output level (e.g., maximum output decibel level) of wearable audio output device 301 when adjusted by the user (e.g., by performing a drag gesture). For example, when louder mode is enabled, wearable audio output device 301 reduces any sound that would otherwise be above the maximum audio output level.

[0288] Figures 6A to 6C 6 is a flow chart illustrating a method 600 for adjusting the audio output of one or more wearable audio output devices according to some embodiments. Figures 3B to 3C Method 600 is performed at a wearable audio output device 301, the wearable audio output device comprising a first portion (e.g., head portion 303) configured to be inserted into the ear of a user of the wearable audio output device and a second portion (e.g., handle portion 305) extending from the first portion and comprising one or more input devices (e.g., input device 308). In some embodiments, the first portion comprises a speaker (e.g., speaker 306) or other audio output device and, optionally, one or more elements to enable the speaker to be positioned in a corresponding physical arrangement relative to the ear of a person using the wearable audio output device. In some embodiments, the second portion comprises a handle or other elongated portion extending from the first portion. In some embodiments, the wearable audio output device comprises a housing having one or more physically distinct portions. In some embodiments, the wearable audio output device comprises one or more audio output devices (e.g., speaker 306). In some embodiments, the wearable audio output device comprises one or more placement sensors (e.g., sensor 304). Some operations in method 600 may optionally be combined, and / or the order of some operations may optionally be changed.

[0289] As described below, method 600 provides an improved interface for controlling audio output by changing the output volume of an audio output device (such as a wearable device) in response to specific types of gestures. Providing additional control options for controlling audio output (such as changing the audio output mode, interacting with a digital assistant, or adjusting audio playback) reduces power usage and extends battery life (e.g., by alleviating the need to power a display or power a communication circuit to communicate with a remote display), and allows users to avoid having to switch between multiple devices to interact with the audio output device (e.g., the user does not need to find / switch to another electronic device (e.g., a smartphone or tablet) to control the audio output), and reduces the number of inputs required for the user to control the audio output, and enhances the operability of the audio output device and makes the user device interface more efficient (e.g., by helping the user achieve the desired results and reducing user errors when operating / interacting with the audio output device). In addition, this reduces power usage and extends the battery life of the audio output device by enabling the user to use the audio output device more quickly and efficiently.

[0290] The wearable audio output device detects (602) input via one or more input devices (e.g., input device 308). In some embodiments, the one or more input devices include one or more capacitive sensors, one or more force sensors, one or more motion sensors, and / or one or more device orientation sensors.

[0291] In some embodiments, the one or more input devices include (604) a series of capacitive sensors arranged to detect user gestures. In some embodiments, the series of capacitive sensors are arranged in columns or rows along the length of the second portion. In some cases, capacitive sensors consume less power and / or provide improved detection of user touch gestures compared to other types of sensors (e.g., force or pressure sensors).

[0292] In some embodiments, the wearable audio output device includes (606) one or more physically distinct (e.g., concave, convex, and / or differently textured) portions (e.g., physically distinct portion 307, such as Figure 3BIn some embodiments, the one or more physical distinctions include a single groove spanning the series of capacitive sensors, a corresponding groove for each capacitive sensor, and / or other configurations of grooves spanning the capacitive sensor locations. Providing physical distinctions at locations corresponding to the capacitive sensors allows the user to quickly and efficiently locate and interact with the sensors (e.g., without requiring the user to visually locate the sensors), which enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user achieve desired results and reducing user errors when operating / interacting with the device), thereby further reducing power usage and extending the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0293] In response to detecting the input, in accordance with determining that the input is a swipe gesture along the second portion of the wearable audio output device, the wearable audio output device adjusts (608) an output volume of the wearable audio output device based on movement of the swipe gesture along the second portion of the wearable audio output device. For example, Figures 5H to 5I A sliding gesture along the handle portion 305 is shown, and Figure 5J The corresponding change in volume of the audio output is shown. In some embodiments, the sliding gesture includes movement of one or more fingers, or pinching for stability and then sliding to adjust, or another finger input. In some embodiments, the sliding gesture is a pinch-slide gesture that includes two fingers that are simultaneously in contact with a second portion of the wearable audio output device (e.g., the two fingers are the thumb and a second finger that is different from the thumb). For example, the user's thumb contacts the wearable audio output device to maintain stability while the user's second finger performs a sliding gesture (e.g., as shown in FIG. Figure 5H In some embodiments, the output volume of the wearable audio output device is adjusted in response to detecting the input and based on a determination that: (i) the input is a swipe gesture along the second portion of the wearable audio output device, and (ii) the first portion of the wearable audio output device is inserted into the user's ear (e.g., based on data from placement sensor 304).

[0294] In some embodiments, the second portion is (610) a handle of the wearable audio output device (e.g., handle portion 305), and the sliding gesture includes movement of one or more fingers along the length of the handle (e.g., as shown in FIG. Figures 5H to 5I and Figures 5K to 5L Providing the elongated handle portion with a sensor for detecting user input allows a user to quickly and efficiently locate and interact with the sensor (e.g., without requiring the user to visually locate the sensor), which enhances the operability of the device and makes the user-device interface more efficient.

[0295] In some embodiments, the first portion of the wearable audio output device includes (612) an audio output device (e.g., speaker 306) configured to be inserted into the user's ear and one or more positioning elements (e.g., Figure 3F 314 as shown), and the second portion of the wearable audio output device is an elongated portion extending from the first portion (e.g., handle portion 305). In some embodiments, when the first portion is inserted into the user's ear, the second portion extends in a downward direction. In some embodiments, when the first portion is inserted into the user's ear, the second portion extends in front of (e.g., past) the user's earlobe (e.g., as shown in FIG. Figure 5G As shown). Improving the fit of the wearable audio output device via the positioning element improves the seal between the wearable audio output device and the user's ear, which enables audio to be played at a lower volume to produce the same effective audio volume as perceived by the user (e.g., relative to when the wearable audio output device is 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 extending the battery life of the device. In some cases, positioning the sensor in the elongated portion extending from the first portion improves the user-device interface by allowing the user to stabilize the device with a pinch gesture when performing input gestures and allowing the user to perform gestures away from the portion of the device that is inserted into the user's ear (e.g., to avoid interfering with the fit between the wearable audio output device and the user's ear).

[0296] In some embodiments, the wearable audio output device (614) communicates with a second wearable audio output device (e.g., wearable audio output device 301-1 communicates with wearable audio output device 301-2) to form a pair of wearable audio output devices, and adjusting the output volume of the wearable audio output device includes adjusting the output volume of both the wearable audio output device and the second wearable audio output device (e.g., as Figure 5G The corresponding output volume levels 518-1 and 518-2 and Figure 5J Adjusting the output volume of both wearable audio output devices in response to a single gesture reduces the number of required inputs, which enhances device operability and makes the user-device interface more efficient (e.g., by helping the user achieve intended results and reducing user errors when operating / interacting with the device), which further reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0297] In some embodiments, the wearable audio output device detects (616) a second input via an input device of the second wearable audio output device, and in response to detecting the second input, based on determining that the second input is a swipe gesture along a second portion of the second wearable audio output device, the wearable audio output device adjusts the output volume of both the wearable audio output device and the second wearable audio output device. For example, Figures 5H to 5I A slide gesture at the wearable audio output device 301-2 is shown, and Figure 5J The corresponding changes in volume at each of the wearable audio output devices 301-1 and 301-2 are shown. Figures 5K to 5L A slide gesture at the wearable audio output device 301-1 is shown, and Figure 5M The corresponding changes in volume at each of the wearable audio output devices 301-1 and 301-2 are shown. Adjusting the output volume of both wearable audio output devices in response to a single gesture at either wearable audio output device enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user achieve intended results and reducing user errors when operating / interacting with the device), which further reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0298] In some embodiments, in conjunction with adjusting the volume of the audio output of the wearable audio output device, the wearable audio output device provides (618) audio feedback (e.g., audio feedback 530) of the volume adjustment to the user via the audio output device of the wearable audio output device (e.g., speaker 306). In some embodiments, the feedback is provided via a speaker in the first portion of the wearable audio output device and / or in the second portion of the wearable audio output device. Providing audio feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user achieve expected results and reducing user errors when operating / interacting with the device), which further reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0299] In some embodiments, providing audio feedback of the volume adjustment includes (620) providing audio feedback of the volume adjustment at both the wearable audio output device and the second wearable audio output device (e.g., audio feedback 530-1 and 530-2). In some embodiments, the audio feedback corresponds to an increase or decrease in volume, and / or the volume reaching a maximum or minimum endpoint. Providing audio feedback to the user at each wearable audio output device enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user achieve expected results and reducing user errors when operating / interacting with the device), which further reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0300] In some embodiments, in response to detecting the input, based on determining that the input is a non-swipe gesture, the wearable audio output device activates (622) a function of the wearable audio output device, wherein the function is different from adjusting the output volume. For example, Figure 5O A non-swipe gesture is shown, while Figure 5P , a corresponding activation of the playback function is shown. In some embodiments, the non-slide gesture is a tap gesture, a double-tap gesture, a squeeze gesture, or other finger input. In some embodiments, the input satisfies a second gesture criterion, such as a single squeeze gesture criterion, which requires that after the intensity applied by the input to the input device satisfies an intensity threshold (e.g., a predefined 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 maintain contact with the input device) within a threshold amount of time since the intensity of the input satisfied the intensity threshold or, alternatively, since the input was first detected via the input device. In some embodiments, the first wearable audio output device and the second wearable audio device have different behaviors. For example, a first wearable audio output device may have a different set of assignments between types of input gestures and operations performed in response than a second wearable audio output device (e.g., a long squeeze gesture via the first wearable audio output device changes the audio output mode of the wearable audio output device or both wearable audio output devices, while a different gesture, such as a short squeeze (e.g., a single squeeze) gesture via the second wearable audio output device changes the audio output mode of the second wearable audio output device or both wearable audio output devices, and / or a different operation, such as toggling playback of media content rather than changing the audio output mode, is performed via the long squeeze gesture via the second wearable audio output device).

[0301] Detecting and responding to different types of gestures in different ways enhances the operability of the device (e.g., providing flexibility without requiring a graphical user interface and / or cluttering the graphical user interface with additional display controls, and reducing the number of inputs required to access that flexibility) and makes the user-device interface more efficient.

[0302] In some embodiments, the function of the wearable audio output device that is activated in response to detecting the input is (624) an audio playback function (e.g., a play, pause, or skip function). In some embodiments, the audio playback function switches playback of the corresponding media audio component (e.g., independent of ambient sounds from the physical environment and based on media content from or obtained by the electronic device). For example, if the corresponding media audio component is playing when the audio playback function is activated, then the playback of the corresponding media audio component is paused; if the corresponding media audio component is paused when the audio playback function is activated, then the playback of the corresponding media audio component is resumed (e.g., as Figure 5P As shown). In some embodiments, the media audio component is combined with one or more pass-through audio components (e.g., where the device is operating in transparent mode) or one or more cancellation audio components (e.g., where the device is operating in noise cancellation mode). In some embodiments, activation of the audio playback functionality skips any remaining portion of the corresponding media audio component and instead plays a different corresponding audio component (e.g., the second, next audio track from the electronic device). Adjusting the audio playback functionality in response to gestures at the wearable audio output device enhances the operability of the device (e.g., providing flexibility without requiring a graphical user interface and / or cluttering the user interface with additional display controls, and reducing the number of inputs required to access that flexibility) and makes the user device interface more efficient.

[0303] In some embodiments, the function of the wearable audio output device activated in response to detecting the input is (626) an ambient noise adjustment function (e.g., active noise cancellation that adjusts ambient noise, transparency of ambient noise, and / or other ambient sound functions). For example, Figures 5Q to 5RA transparent mode is shown enabled in response to user input at the handle portion 305 of the wearable audio output device 301-1. In some embodiments, when ambient sound from the physical environment is actively passing through (e.g., the first ambient sound audio level is non-zero), noise cancellation is disabled (e.g., the audio cancellation audio level is zero). In some embodiments, the ambient noise adjustment function activates a pass-through mode (or transparent mode or non-noise cancellation mode) that allows the user to hear unassisted audio (e.g., normal speech) from the user's environment. In some embodiments, when noise cancellation is enabled (e.g., the audio cancellation audio level is non-zero), no ambient sound from the physical environment is actively passing through (e.g., the first ambient sound audio level is zero). In some embodiments, the ambient noise adjustment function activates an active noise control mode (ANC), and the wearable audio output device outputs one or more audio cancellation audio components (e.g., one or more inverted audio signals, also referred to as "audio cancellation audio components") to at least partially cancel ambient sound from the surrounding physical environment that would otherwise be perceived by the user. In some embodiments, an ambient sound waveform is detected by one or more microphones of the wearable audio output device, and an inverted (or partially inverted) audio signal waveform is generated by the wearable audio output device to at least partially cancel the ambient sound waveform.

[0304] Adjusting the ambient noise control in response to a gesture at the wearable audio output device enhances the operability of the device (e.g., providing flexibility without requiring a graphical user interface and / or cluttering the user interface with additional display controls, and reducing the number of inputs required to access that flexibility) and makes the user device interface more efficient. Additionally, using different levels of passthrough 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 passthrough) that can be achieved with a gesture (e.g., a gesture detected at an input device of one of the wearable audio output devices).

[0305] In some embodiments, the function of the wearable audio output device that is activated in response to detecting the input is (628) a digital assistant function (e.g., invoking a digital assistant, interacting with a digital assistant, or turning off a digital assistant). In some embodiments, the digital assistant includes functionality for performing operations on the device in response to user input (e.g., audio and / or text input, such as spoken or typed commands). In some embodiments, invoking the digital assistant causes the digital assistant to respond to user input (gestures, phrases, and / or commands). In some embodiments, turning off (and / or disabling) the digital assistant causes the digital assistant to not respond to user input. In some embodiments, the functionality causes a digital assistant invocation command to be sent to a network-connected device (e.g., device 100), and the network-connected device invokes the digital assistant and provides corresponding audio to the wearable audio output device, for example, via wireless communication.

[0306] Invoking, interacting with, and / or closing a digital assistant in response to gestures at a wearable audio output device enhances the operability of the device (e.g., providing flexibility without requiring a graphical user interface and / or cluttering the user interface with additional display controls, and reducing the number of inputs required to access that flexibility) and makes the user-device interface more efficient.

[0307] In some embodiments, the wearable audio output device provides (630) audio feedback (e.g., audio feedback 540) of activating the function via the audio output device (e.g., in the first portion and / or the second portion) in conjunction with activating (622) the function of the wearable audio output device, and forgoes providing audio feedback at the second wearable audio output device in the pair of wearable audio output devices. For example, Figure 5R 5. The embodiment of the invention provides audio feedback 540 at the wearable audio output device 301-1 and does not provide audio feedback at the wearable audio output device 301-2. Providing audio feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user achieve the desired results and reducing user errors when operating / interacting with the device), which further reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0308] In some embodiments, the wearable audio output device detects (632) a third input via one or more input devices, and in response to detecting the third input: (i) based on determining that the third input is a swipe gesture along the second portion of the wearable audio output device and determining that the first portion of the wearable audio output device is inserted into the user's ear, the wearable audio output device adjusts the output volume of the wearable audio output device; and (ii) based on determining that the third input is a swipe gesture along the second portion of the wearable audio output device and determining that the first portion of the wearable audio output device is not inserted into the user's ear, the wearable audio output device forgoes adjusting the output volume of the wearable audio output device. In some embodiments, the wearable audio output device 301 is configured to adjust the volume level in response to the user swipe input only when the wearable audio output device 301 is inserted into the user's ear (e.g., determined based on data from the placement sensor 304). Forgoing the need to adjust the volume when the wearable audio output device is not plugged into the user's ear enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user achieve intended results and reducing user errors when operating / interacting with the device), which further reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0309] In some embodiments, one or more input devices include (634) a first type of sensor (e.g., a touch sensor) and a second type of sensor (e.g., a force sensor), the input is detected via the first type of sensor, the device detects a fourth input via the second type of sensor, and in response to detecting the fourth input, the wearable audio output device activates a function of the wearable audio output device other than adjusting the output volume (e.g., sensor types may include capacitive sensors, force sensors, motion sensors (e.g., accelerometers), and orientation sensors). In some embodiments, one or more input devices include pressure-sensitive (sometimes also referred to as "intensity-sensitive") input devices. For example, the input device responds to a squeeze input (e.g., an input that applies intensity (also referred to as pressure) to the input device when held between two fingers and squeezed) that meets an intensity threshold, which in some embodiments is greater than a nominal contact detection intensity threshold that would be used for touch input. In some embodiments, one or more input devices include a touch-sensitive input device (e.g., the input device responds to touch input, such as input by a finger or stylus that meets a nominal contact detection intensity threshold). Including multiple types of sensors in a device expands the number and / or types of gestures that can be detected at the device. Expanding the number and / or types of detectable gestures enhances the operability of the device (e.g., providing flexibility without requiring a graphical user interface and / or cluttering the user interface with additional display controls, and reducing the number of inputs required to access that flexibility) and makes the user device interface more efficient.

[0310] In some embodiments, the wearable audio output device establishes (636) a connection between the electronic device and the wearable audio output device (e.g., pairs the devices, or adds the wearable audio output device to a user account associated with the electronic device), and after establishing the connection (e.g., in response to establishing the connection), the electronic device causes display of a user interface (e.g., user interfaces 514-1 and / or 514-2) showing the simulated swipe gesture and the corresponding output volume adjustment. For example, the user interface is displayed as part of a usage tutorial that is shown in conjunction with pairing the wearable audio output device, adding the wearable audio output device to a user account (e.g., via a QR code), or activating the wearable audio output device for the first time when connected to the electronic device.

[0311] Displaying simulated gestures and corresponding functions and / or adjustments provides visual feedback to the user by indicating the operation and status of the device. Providing improved feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user achieve intended results and reducing user errors when operating / interacting with the device), which further reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0312] It should be understood that Figures 6A to 6C The specific order in which the operations are described in the description is merely an example and is not intended to indicate that the order is the only order in which the operations may be performed. A person skilled in the art will recognize various ways to reorder the operations described herein. In addition, it should be noted that the details of other processes described herein in conjunction with other methods described herein (e.g., methods 700, 800, and 900) are also applicable in a similar manner to the details of the processes described above in conjunction with Figures 6A-6C Method 600 is described. For example, the inputs, gestures, functions, and feedback described above with reference to method 600 may optionally have one or more of the features of the inputs, gestures, functions, and feedback described herein with reference to other methods described herein (e.g., methods 700, 800, and 900). For the sake of brevity, these details are not repeated here.

[0313] 7A to 7C 3 is a flowchart illustrating a method 700 for displaying status information of an electronic accessory according to some embodiments. The method 700 is performed on an electronic device (e.g., device 300 of FIG. 3 , or FIG. 4 ) that includes a display generating component and an optional touch-sensitive surface or communicates with the display generating component and the optional touch-sensitive surface. Figure 1A The method 700 is performed at a portable multifunction device 100. In some embodiments, the display generating component is a touch screen display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations in method 700 are optionally combined, and / or the order of some operations is optionally changed.

[0314] As described below, method 700 provides an improved interface for presenting information about an electronic accessory (e.g., a headphone or earbud case) at an electronic device in communication with the electronic accessory in response to detecting the occurrence of a corresponding condition associated with the electronic accessory, the information being presented along with a representation of the electronic accessory that includes a representation of a physical marker on the electronic accessory. Providing a user with a representation of the electronic accessory with a representation of the physical marker enhances recognizability (e.g., distinguishing between multiple electronic accessories of the same type) and security (e.g., distinguishing between electronic accessories owned by a user and electronic accessories owned by other users) and makes the user-device interface more efficient (e.g., by helping the user interact with the desired electronic accessory), and, in addition, reduces power usage and extends the battery life of the device by enabling the user to control the device more quickly and efficiently.

[0315] The electronic device detects (702) the occurrence of a corresponding condition associated with an electronic accessory (e.g., wireless accessory case 480) that is different from the electronic device and that communicates (e.g., wired or wirelessly) with the electronic device. In some embodiments, the electronic device is a smartphone or tablet. In some embodiments, the electronic accessory is a set of headphones, a smartwatch, a discoverable electronic device, a stylus, or an earbud case.

[0316] In some embodiments, the occurrence of the corresponding condition includes (704) a wireless coupling event (e.g., pairing and / or handshake) between the electronic device and the electronic accessory. 5A to 5D A pairing event between the device 100 and the earbud set 503 is shown. In some embodiments, the wireless coupling event includes detecting a pairing request from an electronic accessory. In some embodiments, the wireless coupling event includes detecting a broadcast signal from the electronic accessory and / or sending a pairing request to the electronic accessory. In some embodiments, the wireless coupling event includes completing a pairing process between the electronic device and the electronic accessory (e.g., establishing a communication channel between the electronic device and the electronic accessory and / or storing connection information to facilitate future connections with the electronic accessory). In some embodiments, the wireless coupling event includes detecting the presence of a previously paired electronic accessory. In some embodiments, the wireless coupling event includes a disconnection and / or separation between the electronic device and the electronic accessory (e.g., in response to a "forget this device" command). Providing a representation of an electronic accessory with a physically marked representation in response to a wireless coupling event provides improved security and privacy by distinguishing multiple electronic accessories that would otherwise be indistinguishable or more difficult to distinguish in the user interface of the wireless coupling event, particularly where the electronic accessories are associated with different users and / or user accounts.

[0317] In some embodiments, the occurrence of the corresponding condition includes (706) proximity-based communication between the electronic device and the electronic accessory. For example, Figure 5TProximity-based communication between wireless accessory box 480-1 and device 100 is shown. In some embodiments, the occurrence of the corresponding condition includes the electronic device and the electronic accessory satisfying one or more proximity criteria (e.g., close enough to communicate wirelessly with each other, and / or within a predefined physical distance of each other). In some embodiments, the one or more proximity criteria include one or more communication quality criteria (e.g., signal strength and / or stability requirements). In some embodiments, proximity-based communication includes wireless coupling communication (e.g., advertising, pairing, and / or handshake communication). Providing a representation of an electronic accessory with a physically marked representation in response to proximity-based communication provides improved security and privacy by distinguishing multiple electronic accessories that would otherwise be indistinguishable or more difficult to distinguish in a user interface for proximity-based communication, particularly where the electronic accessories are associated with different users and / or user accounts.

[0318] In some embodiments, the occurrence of the corresponding condition includes (708) a state change event at the electronic accessory, and the user interface corresponding to the corresponding condition includes state information corresponding to the state change event. For example, Figure 5D The earbud set 503 is shown communicatively connected to the device 100 and the user interface 504-2 includes an indication of the connection 512. Providing a representation of an electronic accessory with a physically marked representation in response to a state change event provides improved security and privacy by differentiating multiple electronic accessories that would otherwise be indistinguishable or more difficult to distinguish in the user interface of the state change event, particularly where the electronic accessories are associated with different users and / or user accounts.

[0319] In some embodiments, the state change event includes (710) a change in the open or closed state of the electronic accessory. For example, Figure 5X to Figure 5Y The lid 367 of the wireless accessory case 480 is shown closed and a corresponding user interface 576 is displayed on the device 100. In some embodiments, the electronic accessory is a charging case, and the state change event involves the user opening and / or closing the charging case. For example, in response to the user closing the charging case, the user interface shows a representation of the charging case and information about the current charge level of the charging case (e.g., Figure 5AC As another example, in response to a user opening a charging case, the user interface displays a representation of the charging case (e.g., representation 5012) and representations of one or more accessories within the charging case (e.g., representation 5006) (e.g., with information about the current charge levels of the one or more accessories within the charging case). Providing a representation of an electronic accessory with a physically marked representation in response to a change in the open or closed state of the electronic accessory provides improved security and privacy by distinguishing multiple electronic accessories that would otherwise be indistinguishable or more difficult to distinguish in the user interface of a state change event, and provides enhanced feedback about the status of the electronic accessory.

[0320] In some embodiments, the state change event includes (712) a charging event at the electronic accessory (e.g., Figure 5Y or Figure 5AC For example, a charging event involves a user connecting an electronic accessory to a power source (e.g., an outlet, a charging station, and / or a charging case), and in response, the user interface displays a representation of the electronic accessory and information indicating that it is currently charging (e.g., Figure 5AC In another example, a charging event may involve a user disconnecting an electronic accessory from a power source, and in response, the user interface displays a representation of the electronic accessory and information indicating the current charge level of the electronic accessory. Providing a physically marked representation of the electronic accessory in response to a charging event provides improved security and privacy by distinguishing between multiple electronic accessories that would otherwise be indistinguishable or more difficult to distinguish in the user interface for the charging event, and provides enhanced feedback regarding the status of the electronic accessory.

[0321] In some embodiments, the occurrence of the corresponding condition includes (714) an error event (e.g., Figure 5AM In some embodiments, the error event involves the electronic accessory failing to establish a connection (e.g., a Bluetooth and / or Wi-Fi connection) with the electronic device, and the error information includes information about the failure (e.g., and information about how to correct the failure). For example, the electronic accessory is a wearable audio output device, and the error event is a failure to pair with the electronic device. In this example, the error information includes instructions to reset the wearable audio output device. In some embodiments, the error event involves the electronic accessory failing to charge when connected to a power source, and the error information includes a notification of the failure (e.g., and information about how to correct the failure). In some embodiments, the error event involves a software error, such as a failure of firmware, operating system, and / or application to execute. Providing a representation of the electronic accessory with a physically marked representation in response to an error event provides improved security and privacy by distinguishing multiple electronic accessories that would otherwise be indistinguishable or more difficult to distinguish in the user interface of the error event, particularly where the electronic accessories are associated with different users and / or user accounts.

[0322] In response to detecting the occurrence of the corresponding condition, the electronic device causes (716) a user interface corresponding to the corresponding condition (e.g., user interface 5056) to be displayed via a display generating component (e.g., touch-sensitive display system 112), which user interface includes a representation of the electronic accessory (e.g., representation 5058 of wireless accessory box 480).

[0323] Causing display of a user interface includes (718): (i) based on determining that the electronic accessory includes a first physical mark (e.g., an engraved, embossed, and / or printed, painted, or otherwise applied mark), causing a representation of the first physical mark (e.g., representation 544-1 of physical mark 482-1) to be displayed in the user interface (e.g., without including a representation of another second physical mark included in a different electronic accessory); and (ii) based on determining that the electronic accessory includes a second physical mark that is different from the first physical mark, causing a representation of the second physical mark to be displayed in the user interface (e.g., representation 544-2 of physical mark 482-2), without including a representation of the first physical mark.

[0324] In some embodiments, the first physical token is provided by the user when purchasing the electronic accessory (e.g., via Figure 5W The first physical marker is specified or selected (720) using the user interface 550 shown in FIG. For example, the first physical marker is a personalized marker accepted by the user, a marker selected from a set of markers, or a marker suggested by a computer system (such as an electronic device). Providing the user with a physical marker specified or selected by the user provides improved security and privacy by distinguishing between multiple electronic accessories that would otherwise be indistinguishable or more difficult to distinguish, particularly where the electronic accessories are associated with different users and / or user accounts.

[0325] In some embodiments, based on determining that the electronic accessory does not include the first physical marker, the electronic device causes (722) a user interface including a representation of the electronic accessory to be displayed without the representation of the first physical marker. For example, wireless accessory box 480-3 ( Figure 5S ) does not include physical marker 482, and user interface 504-1 is displayed with representation 542-3 of wireless accessory box 480-3 without any representation 544 of physical marker 482, e.g., Figure 5V Providing a representation of an electronic accessory without a physical marker distinguishes the electronic accessory from other electronic accessories that include a physical marker. Distinguishing between multiple electronic accessories when interacting with one of the multiple electronic accessories via a user interface improves the security and privacy of the interaction.

[0326] In some embodiments, the representation of the electronic accessory is a three-dimensional representation of the electronic accessory (724). For example, the electronic accessory is a wireless accessory box, and the representation is a three-dimensional model of the wireless accessory box. Providing a three-dimensional representation of the electronic accessory improves security and privacy by distinguishing between multiple electronic accessories that would be indistinguishable or more difficult to distinguish using a two-dimensional representation.

[0327] In some embodiments, the user interface includes (726) one or more animated movements (e.g., rotation, shifting, and / or lateral movement) of a representation of the electronic accessory. For example, Figure 5TArrow 543 in user interface 504-1 is shown indicating movement of representation 542-1 of wireless accessory box 480-1. Providing representations of electronic accessories with animated movement improves security and privacy by differentiating between multiple electronic accessories that would be indistinguishable or more difficult to distinguish using static representations (e.g., representations of physical tags that are not fully visible in the static representation).

[0328] In some embodiments, the electronic device detects (728) an occurrence of a corresponding condition associated with a second electronic accessory (e.g., wireless accessory box 480-2) that is different from the electronic device (e.g., device 100) and the electronic accessory (e.g., wireless accessory box 480-1), the second electronic accessory communicating with the electronic device and having the same device type as the electronic accessory (e.g., wireless accessory box), and in response to detecting the occurrence of the corresponding condition associated with the second electronic accessory, based on determining that the second electronic accessory does not include the first physical marker, the electronic device causes a second user interface corresponding to the corresponding condition to be displayed via the display generation component, wherein the second user interface includes a representation of the second electronic accessory without a representation of the first physical marker. For example, if the second electronic accessory includes a third physical marker, the second user interface includes a representation of the second electronic accessory with a representation of the third physical marker; if the second electronic accessory does not include a personalized physical marker, the second user interface includes a representation of the second electronic accessory without a representation of the personalized physical marker. In accordance with some embodiments, the user interface previously described with respect to the electronic accessory is displayed in response to the occurrence of the corresponding condition associated with the second electronic accessory, and the user interface includes a representation of the second electronic accessory (e.g., in addition to or as a replacement for the representation of the electronic accessory). Providing a representation of the electronic accessory without a representation of the physical marker distinguishes the electronic accessory from other electronic accessories that include the physical marker. Distinguishing between multiple electronic accessories when interacting with one of the multiple electronic accessories via a user interface improves the security and privacy of the interaction.

[0329] In some embodiments, the second electronic accessory includes (730) a third physical marker that is different from the first physical marker, and the second user interface includes a representation of the second electronic accessory with a representation of the third physical marker. In some embodiments, the occurrence of the corresponding condition associated with the second electronic accessory is also associated with the electronic accessory, and the user interface includes a representation of the electronic accessory with a representation of the first physical marker and a representation of the second electronic accessory with a representation of the third physical marker. For example, Figure 5AMA user interface 5056 is shown having a representation 5062 of wearable audio output device 5050 including a representation 5064 of physical marker 5052 and a representation 5063 of wearable audio output device 5046 including a representation 5065 of physical marker 5048. Providing a representation of a second electronic accessory with a representation of a third physical marker distinguishes the second electronic accessory from other electronic accessories (e.g., a first electronic device with the first physical marker). Distinguishing between multiple electronic accessories when interacting with one of the multiple electronic accessories via the user interface improves the security and privacy of the interaction.

[0330] In some embodiments, while the user interface is being displayed, the electronic device detects (732) a user input corresponding to a user interface element on the user interface, wherein the user interface element corresponds to a function of the electronic accessory, and in response to the user input, the electronic device activates the function of the electronic accessory. For example, the occurrence of the corresponding condition includes a pairing request from the electronic accessory, and the user interface element includes a selectable connection element (e.g., button 507, such as Figures 5B to 5C As shown), which corresponds to a pairing function for initiating (or continuing, or confirming) pairing between an electronic device and an electronic accessory. In this example, the user input corresponds to a selectable connection element and activates the pairing function. For another example, the occurrence of the corresponding condition is an error event, and the user interface includes a selectable fault diagnosis element corresponding to the fault diagnosis function. In this example, the user input corresponds to a selectable fault diagnosis element and activates the fault diagnosis function. Providing a representation of the second electronic accessory with a representation of a third physical mark distinguishes the second electronic accessory from other electronic accessories (e.g., a first electronic device with a first physical mark). Distinguishing between multiple electronic accessories when interacting with one of the multiple electronic accessories via the user interface improves the security and privacy of the interaction. In addition, providing a distinguishing feature for the user interface element reduces the number of inputs required to identify / verify the electronic accessory before interacting (e.g., via activating the function corresponding to the user interface element).

[0331] It should be understood that 7A to 7C The specific order in which the operations are described in the description is merely exemplary and is not intended to indicate that the order is the only order in which the operations may be performed. A person of ordinary skill in the art will recognize various ways to reorder the operations described herein. In addition, it should be noted that the details of other processes described herein in conjunction with other methods described herein (e.g., methods 600, 800, and 900) are also applicable in a similar manner to the details of the processes described above in conjunction with 7A to 7CMethod 700 is described. For example, the inputs, gestures, functions, and feedback described above with reference to method 700 may optionally have one or more of the features of the inputs, gestures, functions, and feedback described herein with reference to other methods described herein (e.g., methods 600, 800, and 900). For the sake of brevity, these details are not repeated here.

[0332] Figures 8A to 8D 800 is a flow chart illustrating a method 800 for presenting status information at an accessory charging case according to some embodiments. The method 800 is performed at an accessory charging case (e.g., electronic accessory case 342, Figures 3D to 3E ). In some embodiments, the accessory charging case includes a cover (e.g., cover 367 or hinged cover 486). In some embodiments, the accessory charging case includes one or more input devices (e.g., input device 346). In some embodiments, the accessory charging case is a charging case for a wireless accessory to another device, the wireless accessory including one or more of a smartwatch, one or more earbuds, wireless headphones, a stylus, or a fitness tracker. Some operations in method 800 are optionally combined, and / or the order of some operations is optionally changed.

[0333] As described below, method 800 provides an improved interface for presenting status notifications at an accessory charging case. Providing audio notifications at the charging case reduces power usage and extends battery life (e.g., by alleviating the need to power a display or power a communication circuit to communicate with a remote display), and allows a user to avoid having to switch between multiple devices to interact with the charging case and / or associated accessories (e.g., the user does not need to find / switch to other electronic devices (e.g., smartphones or tablets) to receive status notifications), and reduces the number of inputs required for the user to receive notifications, and enhances the operability of the charging case and makes the user device interface more efficient (e.g., by helping the user achieve desired results and reducing user errors when operating / interacting with the charging case). In addition, this reduces power usage and extends the battery life of the charging case by enabling the user to use the charging case more quickly and efficiently.

[0334] The accessory charging case detects (802) a first event that includes a change in the open or closed state of the accessory charging case. For example, Figure 5X to Figure 5Y A closing event (eg, lid closure) of the wireless accessory device 480 is shown. As another example, Figures 5AB to 5AC An opening event (eg, lid open) of the wireless accessory device 480 is shown.

[0335] In response to detecting a change in the open or closed state of the accessory charging case, the case causes (804) a speaker of the accessory charging case (e.g., speaker 345) to generate an audio notification (e.g., audio feedback 5001) corresponding to a state of the accessory charging case and at least one of one or more accessories associated with the accessory charging case (e.g., communicatively coupled to the accessory charging case and / or linked to the same user account as the accessory charging case). In some embodiments, the speaker of the accessory charging case generates an audio notification corresponding to the state of the accessory charging case and an audio notification corresponding to the state of one or more accessories associated with the accessory charging case. In some embodiments, the speaker of the accessory charging case generates an audio notification corresponding to the state of the accessory charging case without generating an audio notification corresponding to the state of the one or more accessories. In some embodiments, the speaker of the accessory charging case generates an audio notification corresponding to the state of the one or more accessories without generating an audio notification corresponding to the state of the accessory charging case.

[0336] In some embodiments, the audio notification includes (806) one or more words describing the status of at least one of the accessory charging case and one or more accessories associated with the accessory charging case. For example, Figure 5AO Audio feedback 5054 is shown including the words "Alert, earbuds do not match." In some embodiments, the audio notification includes one or more sounds (e.g., tones and / or beeps) and does not include any words.

[0337] Providing audio notifications with words describing status provides improved audio feedback to the user by indicating the relevant status of the system, which enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user achieve intended results and reducing user errors when operating / interacting with the device), thereby further reducing power usage and extending the battery life of the device by enabling the user to use the device more quickly and efficiently (e.g., without the need for a display device and / or graphical user interface).

[0338] In some embodiments, the status corresponds to (808) a charging status (e.g., currently charging, charging complete, or charging terminated) of at least one of the one or more accessories associated with the accessory charging case. Figure 5ACAudio feedback 5001 including information about the charging status of the wearable audio output device 301 is shown. In some embodiments, the audio notification for each state of one or more accessories is different (e.g., so the user can distinguish between different states). For example, the audio notification for the charging initiation state includes a beep having a first tone, and the audio notification for the charging completion state includes a beep having a second tone different from the first tone. As another example, the audio notification for the charging initiation state includes a first number of beeps, and the audio notification for the charging completion state includes a second number of beeps different from the first number of beeps. As another example, each audio notification includes one or more words describing the corresponding charging state (e.g., one or more words that distinguish the charging state). Providing audio information about the charging status of at least one of the one or more accessories associated with the accessory charging case improves feedback to the user by indicating the relevant state of the system, which enhances the operability of the device and makes the user-device interface more efficient.

[0339] In some embodiments, the status includes (810) a state of communicative coupling between the accessory charging case and at least one of the one or more accessories associated with the accessory charging case (e.g., pairing initiated, in progress, completed, or failed). In some embodiments, the audio notification is different for each state of communicative coupling between the accessory charging case and at least one of the one or more accessories associated with the accessory charging case (e.g., so a user can distinguish between different states). Providing audio information about the state of communicative coupling improves feedback to the user by indicating the relevant state of the system, which enhances the operability of the device and makes the user-device interface more efficient.

[0340] In some embodiments, the accessory charging case is configured (812) to simultaneously accommodate multiple accessories (e.g., wearable audio output devices 301-1 and 301-2), the first event comprises closing of the accessory charging case, and the state corresponds to determining that the accessory charging case contains only a subset of the multiple accessories. For example, Figures 5Z to 5AA A closed wireless accessory case 480 is shown with only wearable audio output device 301-1 inside and corresponding audio feedback 587. Providing audio information about a charging case that includes only a subset of accessories improves feedback to the user by indicating relevant status of the system, which enhances device operability and makes the user-device interface more efficient.

[0341] In some embodiments, the state corresponds to (814) a reset event (e.g., a soft reset, a hard reset, and / or a factory reset event) of the accessory charging case. For example, Figure 5AIAn input 5030 at input device 346 is shown, along with corresponding audio feedback 5032, for initiating a factory reset. Examples of soft reset events include closing an executing application, clearing data in volatile memory, and / or powering off the accessory charging case. Examples of hard reset events include clearing memory associated with the accessory charging case's hardware and / or updating the hardware's drivers (e.g., using stable drivers from the hardware manufacturer). An example of a factory reset includes restoring and / or restoring the accessory charging case's settings, firmware, and / or software to the same state as when the accessory charging case was shipped from the factory. An example of a factory reset includes removing user data, user-applied settings, and / or user-installed applications. For example, a factory reset event includes resetting (e.g., deleting and / or removing) wireless connection information (e.g., pairing information and / or Wi-Fi network information). Providing audio information regarding the reset event improves feedback to the user by indicating the relevant state of the system, which enhances device operability and makes the user-device interface more efficient.

[0342] In some embodiments, the status includes (815) the charging state of the accessory charging case not meeting one or more preset criteria (e.g., determining that the charging state of the accessory charging case is insufficient to fully charge an accessory associated with the charging case, or the charging state is below a preset threshold (e.g., below 50%, 30%, or 20%)). For example, Figure 5AD Audio feedback 5018 is shown indicating that the wireless accessory case 480 has only 15% of its charge. In some embodiments, one or more preset criteria are static criteria and correspond to the amount of charge required to fully charge one or more accessories associated with the accessory charging case from any charge state (e.g., the amount of charge required to fully charge one or more accessories from a completely depleted state). In some embodiments, one or more preset criteria are dynamic criteria and correspond to the amount of charge required to fully charge one or more accessories associated with the accessory charging case from a current charge state. For example, one or more accessories are wearable audio output devices that are currently at a charge state of 40% of a full charge, and the one or more preset criteria correspond to the amount of charge required to fully charge the wearable audio output device from a 40% charge state. Providing audio information about the charging state of the accessory charging case improves feedback to the user by indicating the relevant state of the system, which enhances device operability and makes the user-device interface more efficient.

[0343] In some embodiments, the state corresponds to (818) determining that the accessory charging case contains a plurality of accessory devices and determining that the plurality of accessory devices do not match. For example, Figures 5AL to 5AMShown is a closed wireless accessory case 480 with unmatched wearable audio output devices 5046 and 5050 inside and corresponding audio feedback 5054. Providing audio information about unmatched accessory devices improves feedback to the user by indicating relevant status of the system, which enhances device operability and makes the user-device interface more efficient.

[0344] In some embodiments, the first event includes (820) opening the accessory charging case. For example, Figure 5AD Shown is an open wireless accessory box 480 and corresponding audio feedback 5018. Providing audio information when the wireless accessory box is opened improves feedback to the user by indicating relevant status of the system, which enhances device operability and makes the user-device interface more efficient.

[0345] In some embodiments, the accessory charging case (822) communicates with the display generation component, and the case causes a user interface to be displayed via the display generation component, the user interface including the mismatch notification. For example, Figure 5AM Shown is a closed wireless accessory case 480 with unmatched wearable audio output devices 5046 and 5050 inside and a corresponding user interface 5056 with a notification 5057. Providing visual information about unmatched accessory devices improves feedback to the user by indicating the relevant status of the system, which enhances device operability and makes the user-device interface more efficient.

[0346] In some embodiments, the user interface also includes (824) a representation of the accessory charging case (e.g., representation 5058) and corresponding representations of multiple accessory devices (e.g., representations 5062 and 5063, as shown in FIG. Figure 5AM Providing visual representations of accessory devices and accessory charging cases improves feedback to the user by indicating relevant status of the system, which enhances device operability and makes the user-device interface more efficient.

[0347] In some embodiments, determining that the plurality of accessory devices are not matched includes (826) determining that each of the plurality of accessory devices has a different owner (e.g., is linked to or associated with a different user account), and the user interface also includes ownership information for the plurality of accessory devices (e.g., Figure 5AM For example, the ownership information includes the name or identifier of each accessory owner and / or an indication of which accessories have ownership that differs from the ownership of the accessory charging case. Providing audio information regarding mismatched ownership of an accessory device improves feedback to the user by indicating the relevant state of the system, which enhances device operability and makes the user-device interface more efficient. Additionally, providing audio information regarding mismatched ownership improves security / privacy by identifying devices associated with other users and / or user accounts.

[0348] In some embodiments, determining that the plurality of accessory devices do not match includes (828) determining that each of the plurality of accessory devices has a different hardware and / or software version, and the user interface also includes version information for the plurality of accessory devices (e.g., the version information includes a version number or identifier for each of the plurality of accessory devices). For example, Figure 5AP to Figure 5AQ Shown is a closed wireless accessory case 480 with mismatched wearable audio output devices 5046 and 5070 inside and a corresponding displayed indication 5087 of the versions associated with the wearable audio output devices 5046 and 5070 in the wireless accessory case 480. Providing version information regarding the mismatched versions of the accessory devices improves feedback to the user by indicating the relevant status of the system, which enhances device operability and makes the user-device interface more efficient.

[0349] In some embodiments, the case detects (830) a second event, the second event comprising a change in the charging state of at least one of the accessory charging case and one or more accessories associated with the accessory charging case, and in response to detecting the second event, the case causes the speaker to generate a second audio notification that is different from the audio notification and corresponds to the change in charging state. For example, a second audio notification may be generated via the speaker in response to detecting a change in the charging state of the wearable audio output device 301 or the accessory charging case 480. Figure 5AC 5001. Providing audio information about changes in the charging status of at least one of the accessory charging case and one or more accessories associated with the accessory charging case improves feedback to the user by indicating the relevant status of the system, which enhances the operability of the device and makes the user-device interface more efficient.

[0350] In some embodiments, the change in charging state includes (832) initiating or terminating charging of at least one of the one or more accessories associated with the accessory charging case. For example, Figures 5X to 5AY A closed wireless accessory case 480 is shown, along with the initiation of charging of a wearable audio output device 301 and corresponding audio feedback 585. Providing audio information regarding the initiation or termination of charging of at least one of one or more accessories associated with the accessory charging case improves feedback to the user by indicating the relevant status of the system, which enhances device operability and makes the user-device interface more efficient.

[0351] In some embodiments, in response to a user request to locate the accessory charging case (e.g., or an accessory associated with the charging case), the case causes (834) the speaker to generate a third audio notification corresponding to the user request, wherein the third audio notification is different from the audio notification (e.g., of operation 804) (e.g., and optionally has an audio waveform different from the audio waveform of the audio notification). For example, Figures 5AJ to 5AK 5040 is shown as being detected at button 5038, which, when activated by the user, causes audio output 5042 to be output at wireless accessory case 480. In some embodiments, the user request is to locate an accessory device other than the accessory charging case (e.g., an accessory device that is inside, paired with, or associated with the charging case), and in response, the accessory device generates an audio notification (e.g., based on determining that the accessory is inside or in communication with the charging case). Providing an audio notification in response to a user request to locate the accessory charging case or the accessory device inside the charging case improves security / privacy by helping the user quickly locate a lost or stolen accessory charging case and / or accessory device.

[0352] In some embodiments, the case detects (836) a third event including a change in state of the accessory charging case, and in response to detecting the third event: (i) based on determining that the sound setting of the accessory charging case is in an enabled state, the case causes the speaker to generate a fourth audio notification; and (ii) based on determining that the sound setting of the accessory charging case is in a disabled state, the case forgoes causing the generation of the fourth audio notification. For example, Figure 5AV A wireless accessory case 480 is shown with its audio output disabled (e.g., as indicated by volume indicator 5100). In some embodiments, in response to an event when the wireless accessory case 480 has disabled its audio output, the wireless accessory case 480 forgoes generating an audio notification. In some embodiments, a user input is detected at the accessory charging case (e.g., via a hardware or software button), and in response to the user input, the sound setting is set to a disabled state (or off). Forgoing providing audio notifications based on the disabled sound setting improves safety / privacy by preventing unwanted audio notifications (e.g., when the user is in a crowded / public place). Additionally, forgoing unwanted audio notifications reduces power usage and extends the battery life of the device.

[0353] In some embodiments, an electronic device other than the accessory charging case (e.g., electronic device 100) causes (838) displaying a user interface (e.g., user interface 5090) via a display generation component, the user interface including a control element for a sound setting of the accessory charging case (e.g., volume control element 5091), detecting an input corresponding to the control element (e.g., user input 5098), and in response to detecting the input, causing the sound setting of the accessory charging case to be set to a disabled state (e.g., as Figure 5AV5099 in the figure). In some embodiments, in response to detecting an input, the electronic device causes the sound setting of the accessory charging box to switch from a previous state to a new state. For example, when the sound setting is in a disabled state, the accessory charging box abandons generating an audio notification (e.g., abandons generating an audio notification in response to detecting an event occurring at the accessory charging box and / or an event involving the accessory charging box). In some embodiments, the condition for generating an audio notification via the speaker is that the sound setting is set to an enabled state. In some embodiments, the accessory charging box includes a tactile output device, and in response to an event occurring at the accessory charging box and / or an event involving the accessory charging box, the tactile output device generates tactile feedback (e.g., in addition to or instead of generating an audio notification). Displaying a user interface with control elements for the sound setting reduces the number of inputs required to set the sound setting of the accessory charging box to a disabled state.

[0354] In some embodiments, after setting the sound setting of the accessory charging case to a disabled state, the case detects (840) a fourth event including a change in the open or closed state of the accessory charging case, and in response to detecting the fourth event and based on the sound setting being in the disabled state, the case forgoes causing the speaker to generate an audio notification associated with the state of the accessory charging case and / or one or more accessories associated with the accessory charging case (e.g., forgoes generating audio feedback 5018 and / or 5020). In some embodiments, causing the speaker to generate an audio notification associated with the state of at least one of the accessory charging case and one or more accessories associated with the accessory charging case is based on determining that the sound setting is set to an enabled state. Forgoing providing audio notifications based on the sound setting being in the disabled state improves safety / privacy by preventing unwanted audio notifications (e.g., when the user is in a crowded / public place). Additionally, forgoing unwanted audio notifications reduces power usage and extends the battery life of the device.

[0355] In some embodiments, the case sets (842) the sound setting to a disabled state (e.g., as shown in FIG. 1 ) based on an audio output mute setting (e.g., a ring mute setting and / or an audio notification mute setting) enabled at an electronic device communicatively coupled to the accessory charging case. Figures 5AX to 5AY). In some embodiments, a user input corresponding to a ring mute setting is detected at a companion device (e.g., at the electronic device 100, e.g., via hardware or software affordance); and in response to the user input, the ring mute setting is enabled (or turned on). In some embodiments, when the audio output mute setting is enabled, the electronic device forgoes generating audio notifications in response to incoming calls, text messages, voicemails, emails, and / or calendar events. In some embodiments, the electronic device includes a hardware switch configured to switch the audio output mute setting between an enabled state and a disabled state. In some embodiments, the electronic device includes a hardware volume button, and a first type of user input at the hardware volume button causes the audio output mute setting to be enabled. In some embodiments, the electronic device causes an audio control user interface to be displayed, and the audio control user interface includes a selectable mute element that, when selected, causes the audio output mute setting to be enabled. Alternatively, the audio control user interface of the electronic device includes a volume control element that enables the user to set the audio output volume to zero. Configuring the sound settings of the accessory box based on the audio output mute setting or volume control setting of the electronic device avoids requiring the user to separately configure the sound settings of the device and the accessory box, which reduces the number of inputs required to perform operations.

[0356] In some embodiments, the case sets (844) the sound setting to a disabled state based on a focus mode activated at an electronic device communicatively coupled to the accessory charging case. For example, Figures 5BB to 5BE Activation of a focus mode (e.g., Do Not Disturb mode) is shown, along with the corresponding muting of the wireless accessory device 480 as indicated by volume indicator 5138. Configuring the sound settings of the accessory box based on the focus mode of the device avoids requiring the user to configure the sound settings of the device and the accessory box separately, which reduces the number of inputs required to perform operations.

[0357] In some embodiments, the sound setting of the accessory charging case is set (846) to a disabled state based on the electronic device being communicatively coupled to at least one of the one or more accessories associated with the accessory charging case. For example, Figures 5BH to 5BIA wearable audio output device 5142 is shown moving within a threshold distance 5119 while communicating with the electronic device 100 and the wireless accessory case 480, and the corresponding muting of the wireless accessory device 480 as indicated by the volume indicator 5150. Configuring the sound settings of the accessory case based on the settings of the device communicating with one or more accessories associated with the accessory charging case avoids requiring the user to separately configure the sound settings of the device and the accessory case, which reduces the number of inputs required to perform operations. Additionally, configuring the sound settings of the accessory case based on the settings of the device communicating with one or more accessories associated with the accessory charging case avoids requiring the user to directly connect the accessory charging case and the device, which reduces the number of inputs / user interactions required to perform operations.

[0358] In some embodiments, the enabled state (848) of the sound setting is stored at the accessory charging case (e.g., in memory 349). In some embodiments, the setting state is synchronized with the electronic device (or a server system or other device associated with the same user account) based on a communication coupling established between the electronic device and the accessory charging device. For example, based on the charging state of the accessory that is paired or connected to a first user device (e.g., a phone, laptop, or other electronic device), the accessory charging case obtains sound setting information from the first user device (e.g., based on the mute setting of the first user device), in which case the sound setting is set to an enabled state. Furthermore, the accessory charging case maintains the setting internally until the first user device or another user device changes the setting. Continuing with this example, the accessory charging case is subsequently paired or connected to a second user device and obtains second sound setting information from the second user device. In this example, the second sound setting information causes the sound setting to be set to a disabled state (e.g., based on the second user device enabling the audio output mute setting). Saving the enabled state of the sound setting and reusing the same enabled state avoids requiring the user to reconfigure the enabled state of the sound setting when subsequently interacting with the accessory case, which reduces the number of inputs required to perform an operation.

[0359] It should be understood that Figures 8A to 8D The specific order in which the operations are described in the description is merely an example and is not intended to indicate that the order is the only order in which the operations may be performed. A person of ordinary skill in the art will recognize various ways to reorder the operations described herein. In addition, it should be noted that the details of other processes described herein in conjunction with other methods described herein (e.g., methods 600, 700, and 900) are also applicable in a similar manner to the details of the processes described above in conjunction with Figures 8A to 8DMethod 800 is described. For example, the inputs, gestures, functions, and feedback described above with reference to method 800 may optionally have one or more of the features of the inputs, gestures, functions, and feedback described herein with reference to other methods described herein (e.g., methods 600, 700, and 900). For the sake of brevity, these details are not repeated here.

[0360] Figures 9A to 9C 3 is a flow chart illustrating a method 900 for adjusting audio output of a wearable audio output device according to some embodiments. The method 900 is performed on an electronic device (e.g., device 300 of FIG. 3 , or FIG. 4 ) that includes or communicates with a display generation component and an optional touch-sensitive surface. Figure 1A The method 900 is performed at a portable multifunction device 100. In some embodiments, the electronic device is a desktop computer, laptop computer, tablet computer, smartphone, smartwatch, or other computing device. In some embodiments, the display generating component is a touch screen display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations in method 900 are optionally combined, and / or the order of some operations is optionally changed.

[0361] As described below, method 900 provides an improved interface for controlling audio output by changing the audio output mode of an audio output device (such as a wearable device) between audio passthrough and conversation enhancement in response to specific types of gestures. Providing additional control options for controlling audio output (such as changing the audio output mode in response to specific gestures) reduces clutter on the user interface, reduces the number of inputs required to execute control options, enhances the operability of the electronic device, and makes the user-device interface more efficient (e.g., by helping the user achieve desired results and reducing user errors when operating / interacting with the electronic device), thereby further reducing power usage and extending the battery life of the electronic device by enabling the user to use the electronic device more quickly and efficiently.

[0362] The electronic device causes (902) display of a user interface (e.g., user interface 5164) including volume control elements (e.g., Figures 5BL to 5BO Volume control 5166 shown).

[0363] The electronic device detects ( 904 ) an input corresponding to a volume control element (eg, via a touch screen, a motion sensor, a rotatable input element, a button, etc.).

[0364] In response to detecting an input: (i) based on determining that the input is a first type of gesture (e.g., the input satisfies a first gesture criterion, such as a slide gesture criterion requiring application of touch input and movement of touch input), the electronic device adjusts (906) the volume of an audio output of one or more wearable audio output devices; and (ii) based on determining that the input is a second type of gesture (e.g., a tap, double-tap, or long press), the electronic device causes display of a conversation enhancement element for the one or more wearable audio output devices that, when selected, initiates a process for adjusting the audio output of the one or more wearable audio output devices to enhance conversation audio corresponding to a conversation having audio accessible by the one or more wearable audio output devices relative to other audio output by the one or more wearable audio output devices. For example, Figure 5BM User input 5168 is shown (e.g., a swipe or drag gesture), and Figure 5BN The corresponding change in volume of the audio output is shown. To further illustrate this example, Figure 5BO User input 5182 is shown (e.g., a tap or press gesture), and Figure 5BP A corresponding user interface 5184 is shown with a conversation enhancement control 5190. In some embodiments, the electronic device simultaneously displays a volume control element and a conversation enhancement element (e.g., as shown in user interface 5184, as shown in FIG. Figure 5BP ). In some embodiments, the first type of gesture is a swipe, drag, rotate, and / or air gesture. In some embodiments, the conversation audio includes conversation audio picked up by one or more microphones of the wearable audio output device, conversation audio picked up by one or more microphones of the electronic device, and / or conversation audio picked up by one or more external microphones. In some embodiments, the second type of gesture is a double-tap gesture that satisfies one or more gesture criteria, which require that two single-tap gestures be performed within a threshold amount of time of each other and within a threshold distance of each other. In some embodiments, in response to activating a volume control element (e.g., by pressing hard or long on an input device (touch-sensitive surface or mechanical button)), the electronic device updates the user interface (or replaces the display of the (e.g., first) user interface with the display of a second user interface) to include a conversation enhancement element. In some embodiments, the conversation enhancement element is conditionally displayed (at least in part) based on determining that one or more wearable audio output devices are in communication with the electronic device and that the one or more wearable audio output devices are in use (e.g., by playing audio or being inserted into the user's ears). In some embodiments, the conversation enhancement element is not displayed when the one or more wearable audio output devices are not in communication with the electronic device and / or are not in use.

[0365] In some embodiments, selection of the conversation enhancement element initiates (908) a process for adjusting the audio output of one or more wearable audio output devices to enhance the conversation audio while disabling active noise cancellation for ambient noise at the one or more wearable audio output devices. For example, when in noise cancellation mode (e.g., as Figure 5BV In some embodiments, selection of the conversation enhancement element initiates a process for adjusting the audio output of one or more wearable audio output devices to enhance conversation audio while enabling transparency of ambient sound (e.g., greater than zero or another preset threshold) at the one or more wearable audio output devices. The audio output is adjusted to enhance the operability of the conversation audio enhancement device and reduce power usage and extend the battery life of the device only when ANC is disabled.

[0366] In some embodiments, the first type of gesture is (910) a sliding gesture at a location corresponding to a volume control element, and the volume is adjusted according to the movement of the sliding gesture (e.g., as Figures 5BM to 5BN ), and the second type of gesture is a press gesture at a location corresponding to a volume control element (e.g., as Figure 5BO Detecting and responding to different types of gestures in different ways enhances the operability of the device (e.g., providing flexibility without cluttering the user interface with additional display controls and reducing the number of inputs required to access that flexibility) and makes the user-device interface more efficient.

[0367] In some embodiments, in response to detecting the input, based on determining that the input is a third type of gesture, the electronic device activates (912) an audio functionality other than the display of the volume adjustment and conversation enhancement elements (e.g., the functionality changes an audio setting or mode of the wearable audio output device). For example, the third type of gesture is a long press and / or a deep press, and the audio functionality changes the audio mode (e.g., a noise control mode). Detecting and responding to different types of gestures in different ways enhances the operability of the device (e.g., providing flexibility without cluttering the user interface with additional display controls, and reducing the number of inputs required to access that flexibility) and makes the user-device interface more efficient.

[0368] In some embodiments, based on determining that the input is a second type of gesture, the electronic device causes (914) display of an audio control user interface (e.g., Figure 5BP5184), the audio control user interface including multiple elements for operation of one or more wearable audio output devices (e.g., noise control 5194, spatial audio control 5192, and conversation enhancement control 5190), wherein the multiple elements include a conversation enhancement element (e.g., conversation enhancement control 5190). Displaying the audio control user interface in response to specific types of gestures enhances the operability of the electronic device (e.g., providing flexibility without cluttering the user interface with additional displayed controls and reducing the number of inputs required to access that flexibility) and makes the user device interface more efficient.

[0369] In some embodiments, the plurality of elements includes (916) an ambient noise control element (e.g., a noise control 5194) and one or more spatial audio control elements (e.g., a spatial audio control 5192). For example, the spatial audio control settings include a balance setting, a stereo setting, and / or an amplification setting. In some embodiments, the ambient noise control element, when selected, causes activation of an ambient noise adjustment function. In some embodiments, the ambient noise control element, when selected, adjusts active noise cancellation of ambient noise, transparency of ambient sound, and / or other ambient sound functions. For example, increasing transparency of ambient sound includes capturing audio using an external microphone at one or more wearable audio output devices and playing the audio via one or more speakers at one or more wearable audio output devices. In some embodiments, the electronic device or one or more wearable audio output devices includes one or more pass-through audio components (e.g., active when the device or one or more wearable audio output devices are operating in a transparent mode) and one or more cancellation audio components (e.g., active when the device or one or more wearable audio output devices are operating in a noise cancellation mode). Presenting the ambient noise control element and the conversation enhancement element enhances the operability of the device (e.g., provides flexibility by reducing the number of required inputs) and makes the user device interface more efficient.

[0370] In some embodiments, the plurality of elements includes (920) a real-time listening element (e.g., Figure 5BX), which initiates a process for providing audio data at one or more wearable audio output devices when selected, wherein the audio data is captured via a microphone at the electronic device. In some embodiments, the selection of the real-time listening element enables a real-time listening mode (e.g., the selection of the real-time listening element switches the real-time listening mode). In some embodiments, when the real-time listening mode is enabled, audio data is captured via one or more microphones at the electronic device and transmitted to a remote audio output device (e.g., a headset, earplugs, or a device including a speaker component) for playback to the user. For example, audio data captured via one or more microphones is transmitted to a paired headset (or one or more wearable audio output devices) worn by the user, so that playback of sounds occurring around the electronic device is provided to the user. Presenting the real-time listening element and the conversation enhancement element enhances the operability of the device (e.g., providing flexibility by reducing the number of required inputs) and makes the user device interface more efficient.

[0371] In some embodiments, the plurality of elements includes (922) a background sound element (e.g., Figure 5BX ), which, when selected, initiates a process for generating background sound at one or more wearable audio output devices (e.g., generating white noise, water sounds (e.g., ocean or rain sounds), or other sounds intended to mask ambient noise). Presenting the background sound element and the conversation enhancement element enhances the operability of the device (e.g., providing flexibility by reducing the number of required inputs) and makes the user-device interface more efficient.

[0372] In some embodiments, the plurality of elements includes an element (e.g., 924) that, when selected, initiates a process of reducing the volume of sounds that meet one or more criteria (e.g., the one or more criteria include a maximum decibel threshold set by the electronic device and / or the user). Figure 5BX In some embodiments, the maximum decibel slider is displayed with (or in response to selection of) an element for decreasing loudness, e.g., as shown in FIG. Figure 5CB Presenting the loudness reduction element and the conversation enhancement element enhances the operability of the device (e.g., providing flexibility by reducing the number of required inputs) and makes the user-device interface more efficient.

[0373] In some embodiments, the electronic device detects (926) a second input corresponding to the volume control element and, in response to the second input: (i) displays the second input in accordance with a determination that the second input is a gesture of the second type and at least one of the one or more wearable audio output devices is operating in a transparent mode (e.g., Figure 5BQIn some embodiments, based on the active ANC mode, conversation enhancement control 5190 is not displayed in user interface 5184. Forgoing display of the conversation enhancement element when the device is not operating in transparent mode enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user achieve intended results and reducing user errors when operating / interacting with the device), which further reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0374] In some embodiments, when a conversation enhancement element is displayed, the electronic device detects (928) a third input corresponding to the conversation enhancement element (e.g., a tap, double-click, or long press gesture), and in response to detecting the third input, the electronic device causes the conversation enhancement adjustment control to be displayed, for example, Figures 5BR to 5BQ In addition, when the dialogue enhancement adjustment control is displayed, the electronic device detects a fourth input corresponding to the dialogue enhancement adjustment control, and in response to detecting the fourth input, the electronic device adjusts the adjustment amount applied to the dialogue audio according to the fourth input. For example, Figure 5BQ Input 5198 at the conversation enhancement control 5190 is shown, and Figure 5BRDisplay of a conversation enhancement adjustment control 5206 in response to input 5198 is shown. For example, the fourth input is a swipe, drag, rotation, or air gesture, and the adjustment is based on the movement and / or direction of the gesture. In some embodiments, the display of the conversation enhancement slider replaces the display of the conversation enhancement element. In some embodiments, the conversation enhancement slider is displayed adjacent to the conversation enhancement element (e.g., the conversation enhancement slider replaces one or more other elements in the user interface, such as control elements for transparency and / or spatial audio). Alternatively, in some embodiments, the conversation enhancement slider is (automatically) displayed in response to detecting the first input, or in response to detecting the first input and meeting additional criteria (e.g., at least a predefined amount of time passes while continuing to display the (settings) user interface). In some embodiments, the adjustment amount and / or adjustment direction (e.g., increase or decrease) corresponds to the movement, direction, position, duration, force, and / or pressure of the fourth input. In some embodiments, the fourth input is a particular type of input (e.g., a tap), and the adjustment amount is preset for the particular type of input (e.g., each tap increases by 5%, 10%, 20%, 25%, 40%, or 50% or 5, 10, 25, 50, or 100 units (e.g., dB)). Displaying the conversation enhancement adjustment control and adjusting the adjustment amount applied to the conversation audio based on the input at the conversation enhancement adjustment control enhances the operability of the device (e.g., providing flexibility without cluttering the user interface with additional displayed controls, and reducing the number of inputs required to access that flexibility) and makes the user device interface more efficient.

[0375] In some embodiments, electronic device detection (930) includes accessibility user interface elements (e.g., Figure 5BW A series of one or more inputs corresponding to a fifth input (e.g., a tap, a double-tap, or a long press gesture) of the hearing control 5222) of the electronic device, and in response to detecting the fifth input, the electronic device causes display of an accessibility user interface (e.g., Figure 5BX5242). For example, the accessibility user interface element is displayed within a control center UI or settings menu of one or more wearable audio output devices. In some embodiments, the series of one or more inputs includes one or more of the following: an input corresponding to an accessibility element in the settings user interface (e.g., that, when selected, causes the accessibility user interface to be displayed), an input corresponding to an audio element in the accessibility user interface (e.g., that, when selected, causes the audio accessibility user interface to be displayed), and an input corresponding to a wearable audio output device accommodation element in the audio accessibility user interface (e.g., that, when selected, causes the wearable audio output device accommodation user interface to be displayed). In some embodiments, the series of one or more inputs includes an input corresponding to a control center element in the settings user interface (e.g., that, when selected, causes the control center user interface to be displayed), and / or an input corresponding to a hearing element in the control center user interface (e.g., that, when selected, causes the hearing user interface to be displayed). In some embodiments, the series of one or more inputs includes one or more of the following: an input corresponding to an audio control center element in the control center interface (e.g., which, when selected, causes display of an audio control center user interface), an input corresponding to a wearable audio output device accommodation element in the audio control center user interface (e.g., which, when selected, causes display of a wearable audio output device accommodation user interface), and an input corresponding to an ambient noise control element in the wearable audio output device accommodation user interface. Displaying the accessibility user interface in response to the series of one or more inputs enhances the operability of the device (e.g., provides flexibility without cluttering the user interface with additional display controls) and makes the user device interface more efficient.

[0376] It should be understood that Figures 9A to 9C The specific order in which the operations have been described is merely exemplary and is not intended to indicate that the order is the only order in which the operations may be performed. A person skilled in the art will recognize various ways to reorder the operations described herein. In addition, it should be noted that the details of other processes described herein in conjunction with other methods described herein (e.g., methods 600, 700, and 800) are also applicable in a similar manner to the details of the processes described above in conjunction with Figures 9A-9C Method 900 is described. For example, the inputs, gestures, functions, and feedback described above with reference to method 900 may optionally have one or more of the features of the inputs, gestures, functions, and feedback described herein with reference to other methods described herein (e.g., methods 600, 700, and 800). For the sake of brevity, these details are not repeated here.

[0377] References Figures 6A to 6C 、 7A to 7C 、 Figures 8A to 8D as well as Figures 9A to 9C The described operations are optionally performed by Figure 1A to Figure 1B 、 Figure 3C and Figure 3E 1. The components depicted are implemented. For example, the detection operation 904, the adjustment operation 906, and the activation operation 912 are optionally implemented by the event classifier 170, the event recognizer 180, and the event handler 190. The event monitor 171 in the event classifier 170 detects contact on the touch-sensitive display system 112, and the event distributor module 174 delivers the event information to the application 136-1. The corresponding event recognizer 180 of the application 136-1 compares the event information with the corresponding event definition 186 and determines whether the first contact at the first position on the touch-sensitive surface (or whether the rotation of the device) corresponds to a predefined event or sub-event, such as the selection of an object on the user interface, or the rotation of the device from one orientation to another orientation. When the corresponding predefined event or sub-event is detected, the event recognizer 180 activates the event handler 190 associated with the detection of the event or sub-event. The event handler 190 optionally uses or calls the data updater 176 or the object updater 177 to update the application internal state 192. In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application. Similarly, those skilled in the art will clearly understand that based on the Figure 1A to Figure 1B 、 Figure 3C and Figure 3E How the components depicted in FIG. 1 can implement other processes.

[0378] In addition, in the method described herein where one or more steps depend on having met one or more conditions, it should be understood that the method can be repeated in multiple repetitions so that in the process of repetition, all conditions of the steps in the method of determining the method have been met in different repetitions of the method. For example, if the method needs to perform the first step (if the condition is met), and perform the second step (if the condition is not met), then those of ordinary skill will know that the steps stated are repeated until both the condition is met and the condition is not met (in no particular order). Therefore, the method described as having one or more steps depending on having met one or more conditions can be rewritten as a method of repeating until each condition described in the method is met. However, this does not require a system or computer-readable medium to declare that the system or computer-readable medium includes instructions for performing a contingent operation based on the satisfaction of the corresponding one or more conditions, and is therefore able to determine whether a possible situation has been met without explicitly repeating the steps of the method until all conditions of the steps in the method of determining the method have been met. Those of ordinary skill in the art will also understand that, similar to the method with a contingent step, a system or computer-readable storage medium can repeat the steps of the method as needed multiple times to ensure that all contingent steps have been performed.

[0379] For purposes of explanation, the foregoing description has been described with reference to specific embodiments. However, the illustrative discussion above is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Numerous modifications and variations are possible in light of the above teachings. The embodiments have been chosen and described in order to best illustrate the principles of the invention and its practical application so as to enable others skilled in the art to best utilize the invention and the various described embodiments with various modifications suitable for the particular application contemplated.

Claims

1. A method comprising: At a wearable audio output device, the wearable audio output device includes a first portion configured to be inserted into an ear of a user and an elongated portion extending from the first portion of the wearable audio output device, the elongated portion including one or more input devices arranged along a length of the elongated portion, and a housing including a physically distinct portion spanning the one or more input devices, wherein the physically distinct portion includes a recessed, raised, or differently textured portion: detecting an input at the physically distinct portion via the one or more input devices; as well as In response to detecting the input, in accordance with determining that the input is a swipe gesture along the physically distinct portion of the wearable audio output device, adjusting an output volume of the wearable audio output device based on movement of the swipe gesture along the physically distinct portion of the wearable audio output device.

2. The method according to claim 1, wherein: The sliding gesture comprises movement of one or more fingers along the length of the elongated portion.

3. The method according to claim 1, wherein: The first portion includes an audio output device configured to be inserted into the user's ear and one or more positioning elements configured to retain the audio output device in the user's ear after insertion.

4. A method according to any one of claims 1 to 3, wherein the one or more input devices comprises a series of capacitive sensors arranged to detect user gestures.

5. The method according to any one of claims 1 to 4, wherein: The wearable audio output device communicates with a second wearable audio output device to form a pair of wearable audio output devices; and Adjusting the output volume of the wearable audio output device includes adjusting the output volume of both the wearable audio output device and the second wearable audio output device.

6. The method according to claim 5, further comprising: detecting a second input via an input device of the second wearable audio output device; as well as In response to detecting the second input, based on determining that the second input is a swipe gesture along a second portion of the second wearable audio output device, adjusting output volumes of both the wearable audio output device and the second wearable audio output device.

7. The method according to any one of claims 5 to 6, further comprising providing audio feedback of the volume adjustment to a user of the wearable audio output device via an audio output device of the wearable audio output device in conjunction with adjusting the output volume of the wearable audio output device. 8 . The method of claim 7 , wherein providing the audio feedback of the volume adjustment comprises providing the audio feedback of the volume adjustment at both the wearable audio output device and the second wearable audio output device.

9. The method of any one of claims 7 to 8, further comprising, in response to detecting the input, activating a function of the wearable audio output device based on determining that the input is a non-slide gesture, wherein the function is different from adjusting the output volume.

10. The method of claim 9, further comprising, in conjunction with activating the function of the wearable audio output device, providing audio feedback of the activation of the function via the audio output device, and forgoing providing the audio feedback at the second wearable audio output device in the pair of wearable audio output devices.

11. The method according to any one of claims 9 to 10, wherein the functionality of the wearable audio output device comprises an audio playback functionality.

12. The method according to any one of claims 9 to 10, wherein the functionality of the wearable audio output device comprises an ambient noise adjustment functionality.

13. The method of any one of claims 9 to 10, wherein the functionality of the wearable audio output device comprises a digital assistant functionality.

14. The method according to any one of claims 1 to 13, further comprising: detecting a third input via the one or more input devices; as well as In response to detecting the third input: adjusting the output volume of the wearable audio output device based on determining that the third input is a swipe gesture along the physically distinct portion of the wearable audio output device and determining that the first portion of the wearable audio output device is inserted into an ear of a user of the wearable audio output device; as well as Based on determining that the third input is the swipe gesture along the physically distinct portion of the wearable audio output device and determining that the first portion of the wearable audio output device is not inserted into an ear of the user of the wearable audio output device, adjusting the output volume of the wearable audio output device is foregone.

15. The method of any one of claims 1 to 14, wherein the one or more input devices include a first type of sensor and a second type of sensor; wherein the input is detected via a sensor of the first type; as well as The method further comprises: detecting a fourth input via the second type of sensor; as well as In response to detecting the fourth input, activating a function of the wearable audio output device other than adjusting the output volume.

16. The method according to any one of claims 1 to 15, further comprising: At an electronic device distinct from the wearable audio output device, the electronic device communicates with a display generation component: establishing a connection between the electronic device and the wearable audio output device; as well as After establishing the connection, a user interface is caused to be displayed via the display generating component, the user interface showing a simulated sliding gesture and a corresponding output volume adjustment.

17. A wearable audio output device, comprising: a first portion configured to be inserted into an ear of a user; an elongated portion extending from the first portion and comprising one or more input devices disposed along a length of the elongated portion and a housing comprising a physically distinct portion spanning the one or more input devices, wherein the physically distinct portion comprises a recessed, raised, or differently textured portion; one or more processors; as well as a 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 performing the following operations: detecting an input at the physically distinct portion via the one or more input devices; as well as In response to detecting the input, in accordance with determining that the input is a swipe gesture along the physically distinct portion of the wearable audio output device, adjusting an output volume of the wearable audio output device based on movement of the swipe gesture along the physically distinct portion of the wearable audio output device.

18. The wearable audio output device of claim 17, wherein the one or more programs include instructions for performing any one of the methods of claims 2 to 16.

19. A computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by a wearable audio output device comprising a first portion configured to be inserted into an ear of a user and one or more input devices extending from the first portion and arranged along a length of an elongated portion, and a housing comprising a physically distinct portion spanning the one or more input devices, wherein the physically distinct portion comprises a concave, convex, or differently textured portion, causes the wearable audio output device to: detecting input at the physically distinct portion via the one or more input devices; and In response to detecting the input, in accordance with determining that the input is a swipe gesture along the physically distinct portion of the wearable audio output device, adjusting an output volume of the wearable audio output device based on movement of the swipe gesture along the physically distinct portion of the wearable audio output device.

20. The computer-readable storage medium of claim 19, wherein the one or more programs include instructions that, when executed by the wearable audio output device, cause the wearable audio output device to perform any one of the methods of claims 2 to 16.

Images